Worker: priortise messages in the socket
Open
Nobody has claimed this yet.
DevX
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Design to follow
When there are lots of log events in the queue, we may want to prioritise run:complete step:complete etc to make sure they get sent first, and that logs get sent later
That may be levers we can flick in the pheonix socket to help with this
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 tracing the worker's socket queue and how log events and run:complete or step:complete messages are sent. Investigate the possible Phoenix socket levers mentioned in the issue. Done should be defined by a decided prioritisation design and a demonstrated way to send completion messages ahead of queued logs.
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
- 25/100