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

Issues Existing Compression Algorithm #18

Open
infinitytmbots opened this issue May 18, 2024 · 0 comments
Open

Issues Existing Compression Algorithm #18

infinitytmbots opened this issue May 18, 2024 · 0 comments

Comments

@infinitytmbots
Copy link
Member

The currently used ZSTD compression has been causing issues parsing insanely large (but essential) data from the web-socket. My bot has a guild with more than 400 channels and complex permission setup. The server data received via guildCreate event triggered on Ready was being trimmed no matter what.

  • I tried raising the read and write limits of the websocket. Didn't resolve the issue
  • Tried switching to accepting zlib encoding and changed the compression to zlib algorithm and this resolved the issue.

Perhaps an option in the gateway.toml to select the compression algorithm? Or a complete switch to zlib? Any of the above, I'll be more than happy to open a pull request with the changes.

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

1 participant