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.

Sign up for GitHub

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

Jump to bottom

npmjs.com repo is not updating #110

Closed
adomasven opened this issue May 17, 2021 · 3 comments · Fixed by #111
Closed

npmjs.com repo is not updating #110

adomasven opened this issue May 17, 2021 · 3 comments · Fixed by #111
Labels
A-ci Area: continuous integration A-wasm Area: wasm package on npm I-bug Something isn't working

Comments

@adomasven
Copy link
Member

Seems like the latest commit on npmjs is 0164b40 from mid-April. Would be great to restore those.
@cormacrelf
Copy link
Collaborator

Hm, I think this is a timeout from wasm-opt being too slow on CI machines. I think this is because I switched to -O4 instead of whatever it was before. I should have caught it but assumed it was another unnecessary part of that pipeline failing, sorry.

@stakats
Copy link
Member

stakats commented May 17, 2021

Thank you. This is currently blocking us.

@cormacrelf cormacrelf mentioned this issue May 19, 2021
Merged
@cormacrelf
Copy link
Collaborator

Alright, 0.0.0-canary-73165a0 deployed, update away.

@cormacrelf cormacrelf added A-wasm Area: wasm package on npm I-bug Something isn't working A-ci Area: continuous integration and removed I-bug Something isn't working labels Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-ci Area: continuous integration A-wasm Area: wasm package on npm I-bug Something isn't working
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix npm publishing breakage due to wasm-opt segfault zotero/citeproc-rs
3 participants
@stakats @cormacrelf @adomasven