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

Add a utility script to more easily troubleshoot import/export string issues #798

Merged
merged 3 commits into from
Jan 2, 2025

Conversation

rdw-software
Copy link
Member

Very minimal. This is the result of my investigation of #394, which turned out to not be a bug after all.

@rdw-software rdw-software force-pushed the export-string-tools branch 2 times, most recently from eb78189 to 0a51524 Compare January 2, 2025 23:50
It's a utility script and not really a test, anyway.
Should make it a little easier to troubleshoot the broken import strings without having to modify the serialization tests.
The Base64 decoder doesn't return error messages, but both the decompression and the deserialization can fail. In either case, it would be helpful to know why exactly it happened.
@rdw-software rdw-software merged commit 37efd30 into master Jan 2, 2025
6 checks passed
@rdw-software rdw-software deleted the export-string-tools branch January 3, 2025 00:45
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

Successfully merging this pull request may close these issues.

1 participant