layer5io / layer5io/getnighthawk
Changes in main.go
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
Currently in the go code of nighthawks main.go we are using log.Fatal() but log.Fatal() terminates the program completely after encountering an error
Desired Behavior
Here in the go program I think we can handle errors more efficiently using log.Error() instead of log.Fatal(). As log.Fatal() terminates the program completely but log.Error() logs the error msg but allows the program to continue execution. This way, even if one error occurs, the program can continue to process the rest of the results, and the error messages will help in troubleshooting.
Resources
Alternatives / Additional Context
Contributor Resources
- See the Contributing to getnighthawk.dev Website
- See the Project Site section of GetNighthawk project doc
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
Start with main.go and locate the log.Fatal calls involved in processing results. Read the surrounding error paths and confirm which logging API is available before changing behavior. Done means an individual error is logged without stopping the remaining results, with a representative run confirming the continued processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100