-
Notifications
You must be signed in to change notification settings - Fork 150
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
jose@v4.15.2 not working on Node v21.x #1011
Comments
Hi, i'll take a look. This is unexpected since there are no crypto changes in v21 |
Thanks :) Please let me know if I can support you! |
What changed wrt zlib's inflateRaw/deflateRaw? |
Not sure, maybe this can be related? https://github.com/nodejs/node/pull/50085/files |
Installing v21.0.0-nightly20231009387e2929fe on my local macOS system does not reproduce this issue. I suspect them to be platform related and they seem to be related to The issue is that the test vector is deterministic and therefore expects a specific output, which on these runs was not provided. |
Yes, that's absolutely related. |
I'm compiling from main now. |
Do you have any idea to fix the issue? Unfortunately my knowledge for now is not enough to figure out a proper solution by myself |
I'll compile from main to see if it's platform dependent or not, then we ask for the zlib update to be reverted. |
Awesome, thanks! |
Opened nodejs/node#50138 |
I will mark the test as non-deterministic and release a patch release to unblock citgm. |
@alfonsograziano I've adjusted the test expectation and released v4.15.3, you can close this. |
Awesome, thanks a lot! |
Hi @panva I noticed you're listed as maintainer for jose so I'd like to bring to your attention that jose@v4.15.2 tests have been failing across different systems on v21.x. Feel free to loop in more contributors that you think may help.
Here a failed run for reference:
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3318/testReport/
As you can see on this run jose is failing on five different nodes. Can you please help us to debug the issue? I'm not sure if this is related to the new Node version or something inside the package.
The text was updated successfully, but these errors were encountered: