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

Fix pipeline stacktrace syntax error on CI. #336

Merged
merged 2 commits into from
May 25, 2021

Conversation

lunedis
Copy link
Contributor

@lunedis lunedis commented May 25, 2021

This PR was created to solve the failing CI test here: https://github.com/jvalue/open-data-service/runs/2646300675?check_suite_focus=true

and also here: https://github.com/jvalue/open-data-service/runs/2662359092

I was not able to reproduce the error locally, so I opened this PR in order to run my changes on the CI.

@lunedis
Copy link
Contributor Author

lunedis commented May 25, 2021

Ok! I can now reproduce it locally by updating my node docker image from 14.15.1 to 14.17.0.

This is so much fun!

@lunedis
Copy link
Contributor Author

lunedis commented May 25, 2021

It seems to have to do with nodejs/node#33491 introduced into NodeJS version 14.17.0: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V14.md#2021-05-11-version-14170-fermium-lts-danielleadams

I disabled source maps and now it works? Uhhh...

georg-schwarz
georg-schwarz previously approved these changes May 25, 2021
@georg-schwarz georg-schwarz marked this pull request as ready for review May 25, 2021 11:06
@lunedis lunedis changed the title WIP: Fix pipeline stacktrace syntax error on CI. Fix pipeline stacktrace syntax error on CI. May 25, 2021
@georg-schwarz georg-schwarz merged commit 106ca84 into main May 25, 2021
@georg-schwarz georg-schwarz deleted the fix_pipeline_ci_error branch May 25, 2021 13: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