-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Recent build failures from wasm-bindgen ecosystem #2508
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
Comments
I opened this issue in the I guess the fix here would be to just avoid forking the
|
`syn` < 1.0.66 would consume the `AnyIdent` anyway while trying to parse the `ExprArray`. Now due to a refactoring they did, they (correctly) leave the `ParseBuffer` untouched if the input is not a valid `ExprArray`, so we should avoid forking the input buffer and just use the same for both tries, otherwise the unwanted tokens left in there would make `Punctuated` break soon after. Fixes rustwasm#2508
`syn` < 1.0.66 would consume the `AnyIdent` anyway while trying to parse the `ExprArray`. Now due to a refactoring they did, they (correctly) leave the `ParseBuffer` untouched if the input is not a valid `ExprArray`, so we should avoid forking the input buffer and just use the same for both tries, otherwise the unwanted tokens left in there would make `Punctuated` break soon after. Fixes rustwasm#2508
This reverts commit 7f97358.
* Correctly consume tokens when parsing `js_namespace` `syn` < 1.0.66 would consume the `AnyIdent` anyway while trying to parse the `ExprArray`. Now due to a refactoring they did, they (correctly) leave the `ParseBuffer` untouched if the input is not a valid `ExprArray`, so we should avoid forking the input buffer and just use the same for both tries, otherwise the unwanted tokens left in there would make `Punctuated` break soon after. Fixes #2508 * Update nightly used on CI * Update syn version dependency Co-authored-by: Alex Crichton <alex@alexcrichton.com>
818: Update wasm-bindgen dependencies. r=kvark a=VincentFTS Because of rustwasm/wasm-bindgen#2508 Co-authored-by: Vincent Jousse <contact@ftsoftware.fr>
This is a temporary fix for the CI (and anyone building for wasm) break until `wgpu` can update * `syn` released a version that fixed a bug in how they parsed attributes * `wasm_bindgen` released a version that uses that fix * but we're stuck with old `wasm_bindgen` as `wgpu` uses a fixed version: https://github.com/gfx-rs/wgpu-rs/blob/c5ee9cd98310aee66fb49bc98f4f65590304e4aa/Cargo.toml#L118 So, to fix this, either we update everyone to latest version of `wasm_bindgen` or we keep using old version of `syn`. On Bevy side, it should be faster to fix the version of `syn` to one that works. More details: rustwasm/wasm-bindgen#2510 & rustwasm/wasm-bindgen#2508
This dependency needs to be updated to avoid the following gnarly bug: rustwasm/wasm-bindgen#2508. It's gnarly when it happens, and it's intermittent.
Uh oh!
There was an error while loading. Please reload this page.
Describe the Bug
Our CI started randomly failing today on
wasm-bindgen
projects with no dependency changes. This appears to be a failure with the wasm-bindgen macro. Since our project was a library we didn't have a pinnedCargo.lock
I suspect this isn't the fault of wasm-bindgen but of one of its dependencies, but I wasn't sure were else to report it.UPDATE: We just found that forcing rollback of
syn
from1.0.66
to1.0.65
appears to fix this issue.cargo update -p syn --precise 1.0.65
. Leaving this open for wasm-bindgen to do with as they see fit.Steps to Reproduce
Attempt to run
cargo check
onurbdyn/petgraph-wasm
, commitc4e3db9
withsyn
version1.0.66
.Expected Behavior
cargo check
exits fine.Actual Behavior
Recieve hundreds of errors relating to
#[wasm_bindgen(...)]
andWebAssembly
when attempting to build dependencyjs-sys-0.3.49
incargo check
process.Additional Context
Last successful build was ~5 hours prior to time of filing this issue. No changes to source code since then. Blowing away my local
Cargo.lock
duplicated the issue. Sadly I failed to back it up before hand to diff with new one.Link to last successful build for time reference: https://github.com/urbdyn/petgraph-wasm/actions/runs/696142253
Example from GitHub Actions output, full run viewable at: https://github.com/urbdyn/petgraph-wasm/pull/12/checks?check_run_id=2215306539#step:5:68
The text was updated successfully, but these errors were encountered: