lambdaclass / lambdaclass/throttle
don't setup a scope more than once
Open
Nobody has claimed this yet.
bug
- Dominant language
- Erlang
- Stars
- 45
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
if throttle:setup is called again with the same scope, a new ETS is created but the previous one (and the worker that clears it) still hang around. Either drop the old ones or forbid setting up the same scope again.
Contributor guide
No contributing guide indexed for this repository
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 at the throttle:setup entry point and trace how the scope's ETS table and cleanup worker are created. Decide whether repeated setup should replace the existing resources or reject the duplicate, then verify that the previous ETS table and worker no longer remain active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100