-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected parsing behavior of readr (returns 0 rows) #944
Comments
Thanks, this should now be fixed. There was a bug in how quoted strings were handled during the skip parsing. The 'GSE14308_series_matrix' file had
in line 14, and because the single quote in Should now be fixed however, thank you for opening the issue! |
Thanks, @jimhester, for the quick diagnosis and fix. Will this be coming out in a bug-fix release anytime soon? I'd rather not rely on having folks install from github when using GEOquery, but that decision will be driven by timing of release. |
Single quotes used as apostrophes caused the similar problems to #944, even if the line was skipped. The skipping logic is now rewritten to hopefully be more clear and easier to maintain. It is also more robust to these sorts of problems, we no longer try to ignore content within single quotes, only double quotes. Fixes #945
@jimhester thanks for the quick fix. I'm also interested in this getting into a release. Are there any estimates for this? |
I also ran into this issue. @jimhester seems to have quickly tracked it down to terminating single quotes during skip lines. Just for future reference in case someone else runs across this with
Thanks @jimhester for getting a bug fix version |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
This is a report related to seandavi/GEOquery#78. Here, I am comparing the parsing behavior of
read.table
andread_tsv
. In particular,read_tsv
returns a tibble <0x0>. Interestingly, if one replaces theGSE14308
withGSE14309
, I get the expected behavior.I have not tried this with a prior readr version yet, but I can if that is helpful.
Created on 2018-12-13 by the reprex package (v0.2.1)
The text was updated successfully, but these errors were encountered: