rubyforgood / rubyforgood/Flaredown
Heroku: Memory leak / overload on flaredown-api dynos
Open
Nobody has claimed this yet.
Hacktoberfest
type:bug
type:infrastructure
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 21
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 16
Description
Logan thinks this is related to a memory leak of some sort. More details to follow.
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 reviewing the Heroku flaredown-api dyno behavior and the issue's promised additional details; establish a reproducible memory leak or overload before changing code. Done means the cause is isolated and a verified fix prevents the dyno memory growth or overload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100