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

jose@v4.15.2 not working on Node v21.x #1011

Closed
alfonsograziano opened this issue Oct 11, 2023 · 14 comments
Closed

jose@v4.15.2 not working on Node v21.x #1011

alfonsograziano opened this issue Oct 11, 2023 · 14 comments

Comments

@alfonsograziano
Copy link
Contributor

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.

@panva
Copy link
Member

panva commented Oct 11, 2023

Hi, i'll take a look. This is unexpected since there are no crypto changes in v21

@alfonsograziano
Copy link
Contributor Author

Thanks :) Please let me know if I can support you!

@panva
Copy link
Member

panva commented Oct 11, 2023

What changed wrt zlib's inflateRaw/deflateRaw?

@alfonsograziano
Copy link
Contributor Author

Not sure, maybe this can be related? https://github.com/nodejs/node/pull/50085/files
I see that has been merged yesterday and also the jose issue started yesterday

@panva
Copy link
Member

panva commented Oct 11, 2023

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 inflateRaw, and deflateRaw outputs from the node:zlib module.

The issue is that the test vector is deterministic and therefore expects a specific output, which on these runs was not provided.

@panva
Copy link
Member

panva commented Oct 11, 2023

Yes, that's absolutely related.

@panva
Copy link
Member

panva commented Oct 11, 2023

I'm compiling from main now.

@alfonsograziano
Copy link
Contributor Author

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

@panva
Copy link
Member

panva commented Oct 11, 2023

I'll compile from main to see if it's platform dependent or not, then we ask for the zlib update to be reverted.

@alfonsograziano
Copy link
Contributor Author

Awesome, thanks!

@panva
Copy link
Member

panva commented Oct 11, 2023

Opened nodejs/node#50138

@panva
Copy link
Member

panva commented Oct 11, 2023

I will mark the test as non-deterministic and release a patch release to unblock citgm.

@panva
Copy link
Member

panva commented Oct 11, 2023

@alfonsograziano I've adjusted the test expectation and released v4.15.3, you can close this.

@alfonsograziano
Copy link
Contributor Author

Awesome, thanks a lot!

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

2 participants