clockworklabs / clockworklabs/SpacetimeDB
[Cleanup] Remove old energy-monitor related code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
As of #2550 , we use the NullEnergyMonitor in both standalone and cloud. Energy computation happens elsewhere. As such, all the machinery in our codebase which interacts with the EnergyMonitor abstraction is useless and should be removed.
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 reviewing #2550 and searching the codebase for EnergyMonitor and NullEnergyMonitor references. Trace the machinery that interacts with the EnergyMonitor abstraction and identify the obsolete paths. Done means the unused energy-monitor code and its interactions are removed without affecting the current standalone and cloud behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100