cancervariants / cancervariants/gene-normalization
Catch unrecognized/non-existing Dynamo table
Open
enhancement
priority:low
- Dominant language
- Python
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
boto spits out a "resource not found" error or something to that effect but we could probably catch it and give more information
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the code that accesses the Dynamo table and inspect how boto reports an unrecognized or missing table. Define the additional context the error should provide, then add coverage for the missing-table case and verify the resulting message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100