-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Fatalf call from serveAPI #235
Labels
good first issue
Good for newcomers
help wanted
Requires help from contributors to get done
kind/refactor
Only refactoring changes
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
Exit in a more friendly and graceful way |
This issue is stale because it has been open 60 days with no activity. |
This is still needed |
This issue is stale because it has been open 60 days with no activity. |
Still valid. |
yitsushi
added a commit
that referenced
this issue
May 19, 2023
* #179 not relevant anymore * Closes #233 becasue closer inspection, those errors can happen, but that does not mean the application has serious issues, the next loop can be successful, if it stuck in an error loop, it is visible in logs. * #206, we have an issue to track that, we don't need an extra comment about it. * Closes #235, we can return with an error, and the caller can handle it. Additional changes: * If any of the main processes returns with an error, stop all other processes, for example if `serveAPI` fails, we can stop `runControllers` too. References: * #179 * #233 * #206 * #235 Signed-off-by: Balazs Nadasdi <balazs@weave.works>
yitsushi
added a commit
that referenced
this issue
May 25, 2023
* #179 not relevant anymore * Closes #233 becasue closer inspection, those errors can happen, but that does not mean the application has serious issues, the next loop can be successful, if it stuck in an error loop, it is visible in logs. * #206, we have an issue to track that, we don't need an extra comment about it. * Closes #235, we can return with an error, and the caller can handle it. Additional changes: * If any of the main processes returns with an error, stop all other processes, for example if `serveAPI` fails, we can stop `runControllers` too. References: * #179 * #233 * #206 * #235 Signed-off-by: Balazs Nadasdi <balazs@weave.works>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
help wanted
Requires help from contributors to get done
kind/refactor
Only refactoring changes
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Describe the solution you'd like:
Right now the code has a
TODO
mark, so just resolve it.Why do you want this feature:
No
TODO
comments should live in the code without filed issues to track them.Anything else you would like to add:
https://github.com/weaveworks/flintlock/blob/main/internal/command/run/run.go#L145
The text was updated successfully, but these errors were encountered: