Upstream repo, check for updates not working consitently?
Hello, I just updated my upstream repo that my template is using in two services. At first I used the "check for updates" in both services and updated them to latest, I then had a build error and had to push a new fix, however, since that the "check for updates" fails to find ny new commits. What can I do? I have seen this before in other project where it did not work at all when I pushed, but I have some hopes here since it did work the first time just 10 minutes ago. π
Solution:Jump to solution
Anyway, just merged a fix for this so it doesn't use the cache when manually checking. π
14 Replies
Project ID:
f40468c7-29f6-4806-9ec5-30050947b99df40468c7-29f6-4806-9ec5-30050947b99d
the check for updates is cached for 24 hours afaik
cc @fp what would be the reason for such a long cache on that? is it an API intensive check?
Good question. It is intensive + GH API rate limits for public repos aren't great even when authenticated.
am i correct with the 24 hour number?
Yes.
would dropping that down to 12 hours be okay, or would it be worth it to instead purse alterative methods to check for updates?
I think we could make this fetch fresh on click and the automatic fetch can remain 24h.
best of both worlds!
would need a limit per hour or a dead time though, check #π£ο½forum-feed if you wanna know why i say that :kekw:
That sounds good! Thanks! π today I was able to fetch the update
Btw, aren't there some GH hooks that would work the other way around? So you don't have to poll for updates?
This is kinda finicky as these are public repos.
Receiving webhooks only works if the repo owner has given us access to the repo. Us being our GH app.
Solution
Anyway, just merged a fix for this so it doesn't use the cache when manually checking. π
Amazing ! π thank you !!!