Skip to content

fix: handle null bsConfig for instrumentation in init command #111

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

Merged
merged 1 commit into from
Feb 15, 2021

Conversation

SagarGaniga
Copy link
Collaborator

In the case of the init command, usageReporter gets bsConfig as null and fails to send the data with an exception. This errors out the init command.

@suryart suryart merged commit f250d93 into master Feb 15, 2021
@suryart suryart deleted the fix_init_error branch February 15, 2021 06:03
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