Skip to content
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

Devtooling 843 remove log.fatalf #1294

Merged
merged 4 commits into from
Oct 17, 2024

Conversation

carnellj-genesys
Copy link
Collaborator

No description provided.

…rmat to make it easier to parse and do analysis on
…g log.Fatal. This crashes the provider and does not allow for a clean shutdown of the provider
Copy link
Collaborator Author

@carnellj-genesys carnellj-genesys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the only place where I kept the log.Fatals is in the test cases and then in the provider or exporter where it truly makes sense. We want to make sure that in situations where the provider can not start up we want to crash, but for resource errors we need to handle them as errors and follow standard patterns

@carnellj-genesys carnellj-genesys merged commit 84b0362 into dev Oct 17, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants