AllenInstitute / AllenInstitute/axonal_connectomics
concurrent.futures Executor should exit on failure
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
subclassing with one that will not wait is preferable.
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
The issue names concurrent.futures.Executor but does not identify a repository file or test. Start by locating Executor usage in the repository and examining failure handling; done means the executor exits without waiting after failure, with tests covering that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100