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

Output XLSX files sometimes have a random NULL_BYTE in the xml output #168

Open
fchorney opened this issue Mar 25, 2021 · 2 comments
Open

Comments

@fchorney
Copy link
Contributor

Hi, I have an issue I wanted to bring up here. I'm not sure if the issue is here, or in EzXML (libxml2?) but wanted to open up a discussion.

So I currently can't reproduce the issue, but I am using XLSX.jl to generate some XLSX files and every once and again we end up with a NULL_BYTE in the xl/worksheets/sheets1.xml file. There doesn't seem to be any pattern in where it shows up.

For instance in this example a closing bracket > was replaced with a NULL_BYTE (I am representing it with NULL_BYTE but it's actually just a null byte 0x00).

... <c r="BQ8" t="s"><v>90</v></c><c r="BR8" t="s"><v«NULL_BYTE»90</v></c><c r="BS8" t="s"><v>90</v></c> ...

In another instance it replaced an equals symbol = with a NULL_BYTE

... <c r="BG8" t="s"><v>90</v></c><c r«NULL_BYTE»"BH8" t="s"><v>90</v></c><c r="BI8" t="s"><v>90</v></c> ...

And I have seen a few other various files where other random characters in this XML output are replaced by null strings.

I have no idea if it's even any of these libraries, or if it's somehow a network transfer error, but I speculate its whatever is writing the sheet1.xml file since thats the only file it ever ends up in.

If anybody had any ideas where I can look further I would really appreciate it. Thanks!

@felipenoris
Copy link
Owner

felipenoris commented Mar 31, 2021

Certainly this is not a bug in this repo. Most likely a bug in the dependencies, either EzXML or the zip backend.

@fchorney
Copy link
Contributor Author

Certainly this is not a bug in this repo. Most likely a bug in the dependencies, either EzXML or the zip backend.

Yeah that's kind of what I'm thinking. Thanks for the reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants