-
Notifications
You must be signed in to change notification settings - Fork 9
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
try ... catch
can break telemetry
#24
Comments
This was a fast fix for AWS. Since AWS doesn't allow writing out of the
|
yeah, makes sense. Let's work on a long-term solution. Not urgent, so let's tackle it next week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
there is a
try catch
statement at the end of this fileI'm assuming the purpose is to initialize the configuration at import time to prevent race conditions. However, if this fails, this will cause the
internal
not to exist; hence, all the calls to it will fail.I'm still trying to figure out what the best solution here is.
I think we could have some initialization logic and if this fails, make the telemetry module do not work (make the calls do nothing). Example:
The text was updated successfully, but these errors were encountered: