basalt-rs / basalt-rs/basalt-server
Clock state is not persisted...
Open
bug
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points and provides no description. Trace how the competition clock state is managed and persisted, then identify the relevant persistence path and tests. Done means clock state is retained as expected across the relevant restart or reload boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100