Worker: add an option to not send `run:log` events
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Run logs are noisy and pressure the websocket and lightning db. It might be useful in some cases to switch them off - if only to compare performance.
A short term solution would be to use an option to disable logs entirely
Another would be to not stream logs - just send all the logs together at the end of a step (or run?). So they do get sent, just not in real-time
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 worker code that emits run:log events and trace how those events reach the websocket and Lightning DB. Decide whether the intended behavior is disabling logs or batching them at step or run completion, then define tests for the selected option and its effect on event delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100