clockworklabs / clockworklabs/SpacetimeDB
Fix: If a publish fails after publishing a DNS record, future publishes remain broken
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Publishing happens in two steps: updating DNS stuff, and then the actual publishing of the module data.
If something bad happens (e.g. a timeout) after the first step is complete, future publishes return errors (because the DNS stuff is already there)
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
Trace the publish flow described in the issue, starting with the DNS update and continuing through module-data publishing. Reproduce a failure after the DNS step, then verify that a later publish succeeds without treating the existing DNS record as an unrecoverable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100