crossbario / crossbario/autobahn-python
Exceptions thrown in Future callbacks are not handled
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
They are neither logged nor does the caller gets feedback if e.g an INVOCATION message was sent. This leads to situations where caller simply hang up if they haven't any timeout specified without any feedback to why this occurs. See https://github.com/tavendo/AutobahnPython/issues/484 for an example of such a situation.
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
Start by reading issue #484 and tracing how Future callbacks handle exceptions after an INVOCATION message is sent. Identify the callback and caller paths involved, then verify that exceptions are logged and that the caller receives feedback instead of hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100