github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

CSV files not being displayed correctly, when field count does not match between header and value lines #7231

New Issue
Closed
opened 2025-11-02 07:20:19 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 07:20:19 -06:00
Owner
Copy Link

Originally created by @nils91 on GitHub (Apr 22, 2021).

Description

CSV files that contain contact information (exported as 'Outlook CSV' from Google) are not being displayed correctly, only the header is shown in the table. Viewing the file as text in Gitea shows the full file. As far as i can tell, those files are regular .csv files (not sure actually, see next sentence), libreoffice for example displays them just fine. The problem seems to be that Google adds an extra comma to the end of each value line, which is not present in the header.

Screenshots

csv_contact_table_ng
csv_contact_table

Originally created by @nils91 on GitHub (Apr 22, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.13.6 and 1.15.0+dev-172-g445e47b69 - Git version: 2.7.4 - Operating system: Ubuntu 16.04, running gitea from binary (as service), downloaded <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: https://try.gitea.io/nils91/csv_file_display_test/src/branch/master/csv_contact_uploaded.csv (CSV contact) https://try.gitea.io/nils91/csv_file_display_test/src/branch/master/csv_extra_comma_value.csv (extra comma in value line, cause) - [ ] No ## Description CSV files that contain contact information (exported as 'Outlook CSV' from Google) are not being displayed correctly, only the header is shown in the table. Viewing the file as text in Gitea shows the full file. As far as i can tell, those files are regular .csv files (not sure actually, see next sentence), libreoffice for example displays them just fine. **The problem seems to be that Google adds an extra comma to the end of each value line, which is not present in the header.** ## Screenshots ![csv_contact_table_ng](https://user-images.githubusercontent.com/7298243/115710402-9a953100-a372-11eb-9830-13d554fef38d.PNG) ![csv_contact_table](https://user-images.githubusercontent.com/7298243/115708645-8ea86f80-a370-11eb-8c79-aceb44404953.PNG)
GiteaMirror added the issue/not-a-bug label 2025-11-02 07:20:19 -06:00
GiteaMirror commented 2025-11-02 07:20:20 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 22, 2021):

First line has 88 columns but second has 89 columns on csv_contact_uploaded.csv

@lunny commented on GitHub (Apr 22, 2021): First line has 88 columns but second has 89 columns on `csv_contact_uploaded.csv`
GiteaMirror commented 2025-11-02 07:20:20 -06:00
Author
Owner
Copy Link

@nils91 commented on GitHub (Apr 22, 2021):

For reference, heres RFC 4180 on CSV:

  1. Within the header and each record, there may be one or more
    fields, separated by commas. Each line should contain the same
    number of fields throughout the file. Spaces are considered part
    of a field and should not be ignored. The last field in the
    record must not be followed by a comma.

It seems the exported file is not following CSV as outlined by RFC 4180.

@nils91 commented on GitHub (Apr 22, 2021): For reference, heres [RFC 4180](https://tools.ietf.org/html/rfc4180#section-2) on CSV: > 4. Within the header and each record, there may be one or more fields, separated by commas. Each line should contain the same number of fields throughout the file. Spaces are considered part of a field and should not be ignored. The last field in the record must not be followed by a comma. It seems the exported file is not following CSV as outlined by RFC 4180.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7231
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?