Azure / Azure/cyclecloud-scalelib
Node History Problem
- Dominant language
- Python
- Stars
- 10
- Forks
- 16
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
https://github.com/Azure/cyclecloud-scalelib/blob/4efda02a70be0ac93cffc932e9ce5de33d90432d/src/hpc/autoscale/node/nodehistory.py#L154-L161
In `SQLiteNodeHistory.update`, a new node (not in database yet) will be stored in datebase with a fresh `last_match_time`, no matter the `node.required` is true or not. Is it a problem? If an unrequired node can be saved with a fresh `last_match_time`, then what does the `last_match_time` really mean?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/hpc/autoscale/node/nodehistory.py#L154-L161 and inspect SQLiteNodeHistory.update. Trace how new nodes and node.required affect last_match_time, then establish the intended meaning and expected behavior; done means the behavior is documented by regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100