ACU: failed Program Track mode when crossing year end boundary
Open
Nobody has claimed this yet.
agent: acu
bug
needs triage
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
The agent log was simply:
We need to figure out if this was the Agent's fault, or the ACU's. If not fixable in the Agent, work-around should be to avoid scheduling scans across the year end boundary.
Contributor guide
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 reproducing the failure in ACU Program Track mode when a scan crosses the year-end boundary, then inspect the agent log and compare the agent's behavior with the ACU's. Done means identifying which component is responsible and documenting a fix or confirming that avoiding year-end-crossing scans is the required workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100