-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
#9508: Recreating and Handling "Name contains illegal characters" in package.json #9611
Conversation
…ckage.json error.
…ckage.json error.
npm_and_yarn/helpers/test/yarn/fixtures/updater/illegal_character/package.json
Show resolved
Hide resolved
@@ -201,6 +201,8 @@ def run_yarn_top_level_updater(top_level_dependency_updates:) | |||
top_level_dependency_updates | |||
] | |||
) | |||
rescue SharedHelpers::HelperSubprocessFailed => e |
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.
is this the only failure when we run yarn update
; I assume there are other possible failures too and we should only catch the fileNotParseable specifically.
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.
Yes ensured, that we are catching only file not parseable error.
[dependabot-core-dev] ~ $ bin/dry-run.rb npm_and_yarn Sotatek-VanPham/colend-utilities
Original repository will generate helpful error saying file contains illegal character.
I have created new repo with same code base by removing the @ character from the name
[dependabot-core-dev] ~ $ bin/dry-run.rb npm_and_yarn thavaahariharangit/colend-utilities
This works with out any error, and generated new package.json with updates
Our sentry has raised a new error,
"Name contains illegal characters" error was not handled.
This PR