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

[bugfix] Add additional safeguards and logging for unexpectedly empty Bitpack columns #324

Merged

Conversation

fako1024
Copy link
Collaborator

Closes #323

@fako1024 fako1024 added the bug Something isn't working label May 31, 2024
@fako1024 fako1024 requested a review from els0r May 31, 2024 12:28
@fako1024 fako1024 self-assigned this May 31, 2024
@fako1024 fako1024 linked an issue May 31, 2024 that may be closed by this pull request
@els0r els0r merged commit aaa0638 into main Jun 4, 2024
5 checks passed
@els0r els0r deleted the 323-prevent-panics-in-goquery-if-bitpack-data-is-corrupted branch June 4, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prevent panics in goQuery if bitpack data is corrupted
2 participants