Errors logs produce verbose log output in Bluefors Agent
Open
Nobody has claimed this yet.
agent: bluefors
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
Errors logs from the Bluefors Software are not always produced. The Bluefors Agent doesn't know how to read these at the moment, and so each time it tries it prints:
The Bluefors Agent cannot process error logs. Not publishing.
to the logs. This can be misleading to users, we should probably print this only once the first time an Errors logfile is encountered. Or implement proper handling the Errors logs...
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
No file or test is named. Start by locating the Bluefors Agent code that reads Errors logfiles and emits “The Bluefors Agent cannot process error logs. Not publishing.”; clarify whether the expected result is one warning per logfile or proper Errors-log handling, then add coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100