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

Back slash in script logs cause formatted Slack and Teams messages to fail #485

Closed
mountaindude opened this issue Jun 9, 2022 · 0 comments · Fixed by #491
Closed

Back slash in script logs cause formatted Slack and Teams messages to fail #485

mountaindude opened this issue Jun 9, 2022 · 0 comments · Fixed by #491
Labels
Milestone

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

8.1.0

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

16.15.0

What command did you use to start Butler?

node butler.js -c ./config/production.yaml --loglevel debug

What operating system are you using?

macOS

What CPU architecture are you using?

x86_64

What Qlik Sense versions are you using?

2022-May

Describe the Bug

When the script log contains back slash \ this will result in error messages when creating Slack or Teams formatted messages (i.e. messages using the handlebars template files). Email messages are not affected.

The effect is that no Teams or Slack message is sent. Instead an error is shown in the Butler console log.

Slack and Teams messages with basic formatting are not affected, as they don't use the handlebars templates.

There is a risk that other "special" characters also cause this problem. So far only the \ character has been confirmed to cause this problem though.

Expected Behavior

Butler should be able to send nicely formatted messages to Teams and Slack, including the script log of the failed/aborted reload if so desired.

To Reproduce

No response

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