Dallinger / Dallinger/Dallinger
move failing to the worker dyno
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 123
- Forks
- 44
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 6
Description
From @thomasmorgan on April 13, 2016 19:5
depending on how many objects end up failing it can take a lot of time, better to give it to the worker
Copied from original issue: berkeley-cocosci/Wallace#306
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 no files, tests, or entry points. Trace where failing objects are processed and how the worker dyno is invoked; done means that processing runs in the worker rather than the current dyno and remains observable as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100