-
Notifications
You must be signed in to change notification settings - Fork 2
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
Unhandled GitHub response #19
Comments
Possibly -- does it work if you revert the composer lock to the previous state and run it again? |
I reverted |
Strange, no rebasing, squahsing etc that might explain it, somehow? I guess it works going forward? |
Nope. It's a pretty plain vanilla chain of commits to master with the occasional minor dev branch merge. I'll follow up where the next time I do an update with whatever the results are. |
Oddly just ran into this problem again:
I was running |
Similar issue with #21 - one quick win would be to simply tolerate these errors. |
Received this output today when running a minor, white-listed
composer update
:Not sure how to interpret it. Is this something I did wrong? And/or is it something
what-changed
could better handle?Running
git log f69bae05..80511b70
on thecxj/validate.address
repository works fine and outputs the expected log messages.git diff f69bae05..80511b70
similarly works as expected.Could this be just a transient error from GitHub's API?
The text was updated successfully, but these errors were encountered: