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

Assert errors when starting Butler without any New Relic accounts specified in config file #598

Closed
mountaindude opened this issue Dec 2, 2022 · 0 comments · Fixed by #601
Assignees
Labels

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

8.6.0

What version of Node.js are you using? Not applicable if you use the standalone version of Butler.

18

What command did you use to start Butler?

node butler.js

What operating system are you using?

macOS

What CPU architecture are you using?

x86_64

What Qlik Sense versions are you using?

2022-Aug

Describe the Bug

When the config file doesn't include any entries in the Butler.thirdPartyToolsCredentials.newRelic array there will be errors on startup:

2022-12-02T07:41:48.501Z error: ASSERT CONFIG NEW RELIC: TypeError: Cannot read properties of null (reading 'findIndex')
2022-12-02T07:41:48.502Z error: ASSERT CONFIG NEW RELIC: TypeError: Cannot read properties of null (reading 'findIndex')
2022-12-02T07:41:48.505Z error: ASSERT CONFIG NEW RELIC: TypeError: Cannot read properties of null (reading 'findIndex')
2022-12-02T07:41:48.506Z error: ASSERT CONFIG NEW RELIC: TypeError: Cannot read properties of null (reading 'findIndex')

Expected Behavior

Should be possible to have zero or more New Relic accounts specified in the config file.

To Reproduce

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment