-
Notifications
You must be signed in to change notification settings - Fork 437
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
Improve output (and suppress GaxiosError) on failed push #857
Improve output (and suppress GaxiosError) on failed push #857
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
@googlebot I signed it! |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Is this interesting contribution blocked just because of a failed CLA detection by google bot ?! |
I think I submitted my commit wrong, instead of using @users.noreply.github.com, so GitHub can't associate it with my account. Attempting to fix. @alex-galey - fixed, thanks for pinging me the reminder. |
05b32e6
to
81b498a
Compare
# Conflicts: # package-lock.json # package.json
f1a968b
to
0d034da
Compare
Recommited with merge conflicts properly resolved. Added syntax error output formatting so that file names and line numbers can be parsed by popular IDEs and linked to the source file. Tested in VS Code. |
0d034da
to
33ab685
Compare
Is your PR also aims to solve that behavior of clasp not throwing an error when a Gaxios error happens and concluding with a misleading message "Pushed x files." when it didn't successfully push ? |
Yes, the success message and file list will now only be output when the push succeeds. If it fails due to a syntax error detected by GAS, it will return a single line error message that can be automatically linked to the source file/line in an IDE like VS Code. Any other type of error from GAS will return just the error description instead of dumping everything to the terminal. |
@PopGoesTheWza is there a chance this PR is merged or do you see anything else that should be worked on ? |
450175b
to
0b66274
Compare
Hi @sqrrrl, is there a chance this PR is merged or do you see anything else that should be worked on ? |
@alex-galey thanks for trying to bring attention to this. I had honestly forgotten about this PR. Please share of any additional work should be done. |
@sqrrrl do you have any insight why this PR is not being merged ? |
I need this PR for me too. |
* Fix typo in README: "They" -> "The" (google#975) * Add config-files and esmodules to docs/README (google#986) * Improve output (and suppress GaxiosError) on failed push (google#857) * fix run.md for Google Workspace user (google#898) * chore(deps-dev): bump @babel/traverse from 7.14.2 to 7.23.2 (google#982) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump nanoid and mocha (google#977) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump minimatch, recursive-readdir and mocha (google#976) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump word-wrap from 1.2.3 to 1.2.4 (google#970) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump semver from 5.7.1 to 5.7.2 (google#969) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump json-schema and jsprim (google#943) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump node-forge and google-p12-pem (google#941) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump qs from 6.5.2 to 6.5.3 (google#951) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump json5 from 2.2.0 to 2.2.3 (google#954) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 (google#958) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * [docs] Add clasp run instructions to deploy script as API Executable (google#1004) * Fix typo (google#1002) * update install command for `@types/google-apps-script` (google#999) * rebuild --------- Co-authored-by: Adam Smith <927886+burkybang@users.noreply.github.com> Co-authored-by: Ravi van Rooijen <ravivanrooijen@live.nl> Co-authored-by: Nu11u5 <Nu11u5@users.noreply.github.com> Co-authored-by: Hirokazu Takatama <takatama@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Dan Dascalescu <ddascalescu+github@gmail.com> Co-authored-by: Alejandro Marco <78371908+amalej@users.noreply.github.com> Co-authored-by: Joseph Mearman <joseph@mearman.co.uk>
I'm not experienced with package publishing, auto-versioning, etc. How do we go about prompting the release bot to create another release? Is that something that an admin has to initiate @PopGoesTheWza @sqrrrl? |
Fixes #827, #907
GaxiosError
object dump on failed pusherror.message
is output to the consolestopSpinner()
before outputting to consoleChecklist
npm run test
succeeds.npm run lint
succeeds.