You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have generated a csv data file in R, and the file displays correctly in R or Excel, but not on OSF: (original link: https://osf.io/zh9rv)
This issue is not new, but before, although nothing wrong appears in the csv file itself, I was able to edit the file directly on OSF to fix the incorrect display. The fix was (oddly) to remove the space between (in this case) the second column and the first (and adding a comma). However, it seems OSF has removed the ability to modify CSV files, so this workaround is no longer possible. I was able to fix it manually but I would still like to report this bug so it can be investigated [edit: not fixed after all, I just messed the file up earlier].
The example data file can be retrieved in the testing repository below. I've attempted to simplify the data frame to have a minimally reproducible example, but I am not able to identify the origin of the bug precisely. Removing some columns removes the bug, and readding them reintroduces the bug, but I don't see any clear pattern in the affected columns. Perhaps this is related to empty rows.
Thanks for reaching out. This is a known bug that Python CSV sniffing doesn't work as expect when there are too many columns. I created a PR two years ago: CenterForOpenScience/modular-file-renderer#362 but sadly it was lost. Your issue has brought this back up to the team and hopefully we will have this one fixed soon. Cc @felliott for transparency.
I have generated a csv data file in R, and the file displays correctly in R or Excel, but not on OSF: (original link: https://osf.io/zh9rv)
This issue is not new, but before, although nothing wrong appears in the csv file itself, I was able to edit the file directly on OSF to fix the incorrect display. The fix was (oddly) to remove the space between (in this case) the second column and the first (and adding a comma). However, it seems OSF has removed the ability to modify CSV files, so this workaround is no longer possible. I was able to fix it manually but I would still like to report this bug so it can be investigated [edit: not fixed after all, I just messed the file up earlier].
The example data file can be retrieved in the testing repository below. I've attempted to simplify the data frame to have a minimally reproducible example, but I am not able to identify the origin of the bug precisely. Removing some columns removes the bug, and readding them reintroduces the bug, but I don't see any clear pattern in the affected columns. Perhaps this is related to empty rows.
https://osf.io/v8b64
Edit: Here another example from a different research team: https://osf.io/4zp9b
The text was updated successfully, but these errors were encountered: