icipe-official / icipe-official/vectoratlas-software-code
DOI resolver id exhaustion
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 8
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 11
Description
As a [role]
I need [function]
So that [benefit]
Details and Assumptions
- [document what you know]
Acceptance Criteria
Given [some context]
When [certain action is taken]
Then [the outcome of the action is observed]
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
The issue names no files, tests, reproduction, or acceptance criteria. Start by locating the DOI resolver and tracing how IDs are allocated and exhausted; establish a reproducible failure and expected behavior before estimating a fix. Done requires agreed acceptance criteria and regression coverage for the exhaustion case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100