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

Unhandled exception when getting QSEoW app script log #1274

Closed
mountaindude opened this issue Oct 16, 2024 · 4 comments · Fixed by #1281 or #1273
Closed

Unhandled exception when getting QSEoW app script log #1274

mountaindude opened this issue Oct 16, 2024 · 4 comments · Fixed by #1281 or #1273
Labels

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

13.0.0

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

No response

What command did you use to start Butler?

What operating system are you using?

Windows Server 2019

What CPU architecture are you using?

What Qlik Sense versions are you using?

2024-May IR

Describe the Bug

Possible regression, this worked reliably in pre 13.0 versions.

image

Expected Behavior

No response

To Reproduce

No response

@Chase-Stevison
Copy link

I'm seeing the same behavior in Qlik Sense 2023-Feb running on Windows Server 2019. I also caught this Script Log error when a task failed:

2024-10-20 14:09:02.649: 2024-10-20T14:09:02.652Z �[31merror�[39m: SCRIPTLOG STORE: TypeError: r.scriptLogFull.join is not a function

I'm happy to provide any additional logs that may help. Thanks!

@mountaindude
Copy link
Collaborator Author

Indeed, looks like a regression bug that was introduced in 13.0.
The bug has been fixed and will be included in next release, due out in a day or two.

@mountaindude
Copy link
Collaborator Author

@Chase-Stevison
This issue was fixed in v 13.1 which was release just now.

https://github.com/ptarmiganlabs/butler/releases/tag/butler-v13.1.0

@Chase-Stevison
Copy link

Thanks @mountaindude!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants