tensorflow / tensorflow/tensorboard
Use unified error types where appropriate
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
See #2631 for context.
We’ll want to consider both standard 400s (“invalid run/tag”, as in most
plugins) and custom error types (like HParamsError).
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
Read issue #2631 first for the stated context, then survey the plugin paths that produce standard 400 errors such as “invalid run/tag” and custom errors such as HParamsError. Done means deciding and documenting which error types should be unified and applying that decision consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100