Skip to content
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

read_sas() fails to parse sas7bdat file since v2.2.0 #695

Closed
kforner opened this issue Aug 29, 2022 · 2 comments
Closed

read_sas() fails to parse sas7bdat file since v2.2.0 #695

kforner opened this issue Aug 29, 2022 · 2 comments
Labels
bug an unexpected problem or unintended behavior readstat reprex needs a minimal reproducible example

Comments

@kforner
Copy link

kforner commented Aug 29, 2022

We have a file (from a customer) that can be successfully parsed by haven up to version 2.2.0 (included), and fails starting from version 2.3.0:

> haven::read_sas('/tmp/toto')
Error in df_parse_sas_file(spec_data, spec_cat, encoding = encoding, catalog_encoding = catalog_encoding,  : 
  Failed to parse /tmp/toto: Invalid file, or file has unsupported features.

Unfortunately we can not for now provide a reprex. But in the header there is this string 7.00.00BWIN_95, probably the OS version.
We will try to provide a sample file, but in the meantime, is there any change between those 2 versions (I suppose in readstat) that could explain this error ?

@gorcha
Copy link
Member

gorcha commented Sep 1, 2022

Hi @kforner, thanks for the report. There were a few changes to the SAS reading code in readstat in that release so this is almost certainly related, but there's nothing that screams out on a first glance.

Unfortunately it's not really possible to investigate without a reprex (particularly with SAS files since there's no solid file format specification), so if there is a way you can provide a file to check it would be very much appreciated.

@gorcha gorcha added readstat bug an unexpected problem or unintended behavior reprex needs a minimal reproducible example labels Sep 1, 2022
@hadley
Copy link
Member

hadley commented Oct 31, 2023

I've closed this issue due to lack of requested reprex. If you still care about this bug, please open a new issue with a reprex.

@hadley hadley closed this as completed Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior readstat reprex needs a minimal reproducible example
Projects
None yet
Development

No branches or pull requests

3 participants