-
Notifications
You must be signed in to change notification settings - Fork 1.4k
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
"length" is outside of buffer bounds #2025
Comments
We are observing same issue
As a fix, we decided to downgrade node version (22.4.0 works fine). |
Same issue, not necessary to protobufjs@7.4. The error thrown on my 7.3.3 |
…fer bounds remove call buf.utf8Write(), it will be called in buf.write() ref: protobufjs#2025
…fer bounds since nodejs 22.7 call buf.utf8Write() conditionally, it will be called in buf.write() ref: protobufjs#2025
…fer bounds since nodejs 22.7 call buf.utf8Write() conditionally, it will be called in buf.write() ref: protobufjs#2025
…fer bounds since nodejs 22.7 call buf.utf8Write() conditionally, it will be called in buf.write() ref: protobufjs#2025
## Why is this change needed? CI is broken because there's some issue with proto serialization in node 22.7.0. I used the same version that's in the hub deployment dockerfile. protobufjs/protobuf.js#2025 ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [x] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [ ] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [x] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview This PR updates the Node.js version in the CI workflow to 22.4.1 due to an issue with 22.7.0. It also specifies different Node.js versions for x64 and ARM architectures. ### Detailed summary - Updated Node.js version in CI workflow to 22.4.1 - Added comments about the issue with Node.js 22.7.0 - Specified different Node.js versions for x64 and ARM architectures > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
There's a bug in Node 22.7.0 with protobuf which we're running into: protobufjs/protobuf.js#2025 Once the bug is fixed, we should revert this PR. h/t @lforst for figuring this out; I'm just merging it into develop 😅
Needs to be pinned until nodejs/node#54518 is resolved. Other references: * protobufjs/protobuf.js#2025 * protobufjs/protobuf.js#2026
Needs to be pinned until nodejs/node#54518 is resolved. Other references: * protobufjs/protobuf.js#2025 * protobufjs/protobuf.js#2026
In case you are still experiencing that issues, try these LTS versions:
Everything above looks from my perspective broken and leads to these buffer errors. |
Also fixed in the latest node (v22.8.0) |
test will throw errors if you are using an incompatible node version. On version 22.8 it does work as intended. (a problem with protobufjs: protobufjs/protobuf.js#2025)
@mbrevda thanks, upgrading to v22.8.0 worked for me |
protobuf.js version: 7.4.0
It appears that the latest nodejs version (22.7.0) triggers this error:
RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds
at
The text was updated successfully, but these errors were encountered: