clockworklabs / clockworklabs/SpacetimeDB
CI flake: Build and test wasm bindings
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
Build and test wasm bindings
Error:
Error: command ["pnpm", "build"] exited with code 133
2026-08-25T19:03:54.3091382Z
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/32887267720/job/97930843081 (Build and test wasm bindings, attempt 1 -> 2)
Timeout detection:
- none
Context:
- none
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failed GitHub Actions job for “Build and test wasm bindings” and compare the failed attempt with the successful rerun. Inspect the workflow steps around pnpm build, then reproduce the build if possible. Done means the wasm binding job completes reliably without exit code 133.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust, wasm
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100