Allow a Lost run to be overruled by delayed events
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
One pattern I notice is that after a Run has been marked Lost by Lightning, often the work has all been done and we were just waiting for a message.
Sometimes after Lost, the worker will reconnect and try to send all messages. And they'll be rejected because the run was Lost.
We should consider engineering robustness into Lightning. A run can be Lost, sure, but if more information comes in after this, it should still listen, and the status should be updated.
This may well need support from the Worker. I think we should discuss next year.
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 how a Run becomes Lost and how messages from a reconnecting worker are handled afterward. Clarify the intended state transition and required Worker support with maintainers; done means the behavior for post-Lost messages is agreed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100