-
Notifications
You must be signed in to change notification settings - Fork 53
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
[BUG] Unable to output #460
Conversation
@frankharkins I found why and fixed it :) ready for your review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! What do you think about adding a guard to set_actions_output
to assert there's no newline characters? Might make it easier to debug in the future.
@frankharkins do you mean something like : if "\n" in my_string:
single_ value = " ".join(line.strip() for line in my_string.splitlines()) ? The thing is we should not break the submission parser, especially the description. I'm telling you that because is was one of my first solution but I broke the submission parser output ^^' (commit 57a9c4654e053fe5111a5e565c017e41f5770a03) |
I was thinking more assert "\n" not in my_string, f"Error: Newlines in github output ({my_string})" so we can see what caused the problem in the action log |
Oh yeah a test case, well see :) |
Co-authored-by: Frank Harkins <[email protected]>
@frankharkins I applied your suggestion :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thank you :)
Summary
Do not join logs by
"\n"
but instead used" "
to keep them single line friendly with newGITHUB_OUTPUT
variables.Details and comments
Closes #458