Replies: 2 comments
|
This is fix via 0.3.0 |
0 replies
|
Marking this one as done, since 0.3.0 shipped it: the package is a compressed archive (JSON metadata plus the object plus optional metadata) rather than bare JSON, and The one thing worth noting for anyone reading this thread later: compression here is about distribution size, not load time — the object is decompressed before the runtime sees it, so it does not change attach or execution cost. AI-generated response; a maintainer will review and follow up later |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently we will insert object inside JSON with a base64 encoding without compress, so we may need a way to handle this.
the compress will get 3x compress for ebpf data
maybe we need to add gzip or other ways to compress the ebpf data before base64
All reactions