-
Notifications
You must be signed in to change notification settings - Fork 18
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
TagBot failed with github.GithubException.UnknownObjectException #81
Comments
Two bugs in one! I thought that a previous check would have guaranteed that the file we're looking for would exist... but apparently something is gone wrong. And the automatic error reporting is somehow misconfigured and all requests return 403. without ever reaching my code 🙃 I'll get right on both of them. |
Your issue should be fixed by 189876a, I'll leave this open until I see it work and I fix the second bit. |
Thanks a lot for super quick fix!
Yeah, I wasn't sure if I should open an issue as I thought it would be opened automatically. |
It kind of started working... See the 20 new issues lol. But the particular error being reported is supposed to be ignored... Lots of work to do. |
Not sure if it is related to the original issue, but here is another strange thing. TagBot says ...while this package is already registered JuliaRegistries/General#10344 and no related release exist yet https://github.com/tkf/SplittablesBase.jl/releases |
Hm, yeah that really shouldn't be happening either. It's picking up the new version when I run it locally, so I'll check what happens when it runs next. Could you set the repo secret |
Here is the log: https://github.com/tkf/SplittablesBase.jl/runs/484463941?check_suite_focus=true#step:3:1 Unfortunately(?), it created the new release, though https://github.com/tkf/SplittablesBase.jl/releases/tag/v0.1.0 |
Well then... My guess is that it was related to #80 but I'm not really sure. Let's just assume it'll keep working... |
Alright 1883573 should take care of the error reporting problems. The initial problem of "no requests are going through" was solved by just redeploying... I guess it's flaky. |
I found this in the error log:
https://github.com/tkf/SplittablesBase.jl/runs/484158558?check_suite_focus=true#step:3:35
The text was updated successfully, but these errors were encountered: