You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have disappearing packages but some branches are randomly published or not published when run from github actions - there's no pattern to that. Maybe it's something about download failures of the required metadata, but there's no log/proof of that.
Can confirm that the same happens after using a GitLab webhook to update Satis. Basically, we push 2 branches (support & master) in quick succession (the Satis commands themselves are queued so only 1 runs at a time). After the support push, all branches are published but once master pushes, the dev-support & dev-master branches are missing. If I then run vendor/bin/satis build ..., all branches are back again.
In a follow-up to the comment above, we have since removed some old branches. This seems to "fix" the problem as well. We were at roughly 100 branches before, now sub 50.
We encountered with disappearing packages after sometime, we got no clue when and how it happens, does anyone encountered also?
The text was updated successfully, but these errors were encountered: