Userland Timeout
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
BufferedMessageSocket needs a userland timeout for message dequeueing that can handle cases where the server remains alive but becomes unresponsive. The underlying socket read can't be allowed to time out because it needs to be able to receive asynchronous messages even when the session is otherwise idle.
Note that this is distinct from the query timeout parameter, which is handled in the server.
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
Locate the BufferedMessageSocket entry point and trace message dequeueing separately from the underlying socket read. Verify how asynchronous messages are handled during idle sessions and distinguish this behavior from the server-side query timeout. Done means an unresponsive server can trigger a userland dequeue timeout without preventing asynchronous messages from being received.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, scala
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100