Better errors

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend, observability

Research direction

The issue names no files, tests, or entry points. Start by tracing the resume-related API call path and identify where failures are currently handled; done means errors are surfaced and repeated API failures produce an actionable alert through a chosen fault-tracking approach.

Written by the indexing model from the issue text.

Description

enhancement Someday

I'm not quite sure what went wrong with resumes this year, but it should have generated an error on our end. We also need to either integrate our own fault tracker or use an existing one so that we get a heads up if a lot of API calls are failing and can start to investigate why.

Dominant language
JavaScript
Stars
6
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hacksu/kenthackenough

All issues in hacksu/kenthackenough

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.