Closed 2Abendsegler closed 1 year ago
https://github.com/orgs/community/discussions/46691#discussioncomment-4948308
👋 Hi folks, GitHub engineer here. This was a bug with our caching in some cases - sorry about this! We're working on resolving this and the cache should be back to normal soon.
https://github.com/orgs/community/discussions/46691#discussioncomment-4948987
This should be fixed now, thank you for reporting it. I've purged the cache so your raw files should be back to using
max-age=300
. Please let me know if you're still seeing a longer expiry, and I can take a look.
Scheinbar werden demolierte Branches bzw. Dateien aber nicht automatisch wieder angestoßen. Der Collector ist immer noch auf einem veralteten Stand.
Ein merge in den collector hat nichts gebracht. Scheinbar ist doch noch nicht alles behoben.
Vorgehensweise um Probleme im neuen master zu beheben:
Describe the bug
https://github.com/orgs/community/discussions/46758
Hi,
I can confirm that. I have the same problem.
In the meantime I have deleted my two main branches "master" and "collector" in my repository. Nevertheless, the raw.githubusercontent.com links are still there. This is only the case with these two special branches. With other branches, the file under the raw.githubusercontent.com link is also immediately deleted when deleting the branch. I can create the two branches again from another one, but the raw.githubusercontent.com are not updated.
Some of the raw.githubusercontent.com links are large scripts (1.2 MB). This may have something to do with the problem, because it always takes a while before the merge of a branch is also visible in the raw.githubusercontent.com link.
To Reproduce:
Thanks for helping.
To Reproduce
No response
Expected behavior
No response
OS
Windows
Browser
Firefox
GClh Version
not relevant
Additional context
No response