clockworklabs / clockworklabs/SpacetimeDB
FEATURE REQUEST: ScheduleAt::Delay
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
From @SteveBoytsun:
it would be nice to have a
ScheduleAt::Delayoption that works likeScheduleAt::Timebut with relative offset (so we can schedule a one-off timer like soScheduleAt::Delay(Duration::from_secs(secs))instead ofScheduleAt::Time(Timestamp::now().checked_add(Duration::from_secs(secs)).unwrap().into_micros_since_epoch()))
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 by locating the definition of ScheduleAt and the existing ScheduleAt::Time handling, then trace how one-off timers calculate their target time. Confirm how Duration and Timestamp are represented at that entry point. Done means ScheduleAt::Delay accepts a relative Duration and schedules the equivalent one-off timer without requiring callers to compute an absolute timestamp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100