clockworklabs / clockworklabs/SpacetimeDB
CI flake: Test spacetimedb-update flow (x86_64-pc-windows-msvc)
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:
Test spacetimedb-update flow (x86_64-pc-windows-msvc)
Error:
Failed to FinalizeArtifact: Received non-retryable error: Failed request: (403) Forbidden: Error from intermediary with HTTP status code 403 "Forbidden"
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more...
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/34251420661/job/102147698778 (Test spacetimedb-update flow (x86_64-pc-windows-msvc), 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 Test spacetimedb-update flow (x86_64-pc-windows-msvc) and inspect the Failed to FinalizeArtifact response and surrounding workflow steps. Determine whether the 403 is reproducible or an intermittent intermediary failure, then validate the result with the same Windows test flow and a successful artifact finalization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100