Open philipp-brosig opened 2 years ago
Jamesking56
commented
2 years ago I have a similar problem, I released a new update to my Composer package and Repman hasn't picked it up. I've been waiting for several hours and I've clicked on 'Rescan' and 'Update' actions in the UI.
I get the feeling that the repman website's queue system has stopped processing anything at all
Jarzebowsky
commented
2 years ago We have a replay of what happened last week. #565
@akondas any help on reviewing the queue?
gaetan-hexadog
commented
2 years ago Same here :'(
Can't sync since 2 days and my new versions are not showing up anymore after a release.
akondas
commented
2 years ago Sorry again, disk run out of space, I increased the instance, the queue started to work just now, pleas give it some time to consume all task in queue.
gaetan-hexadog
commented
2 years ago It's fixed. Thanks
gaetan-hexadog
commented
2 years ago It's fixed. Thanks
New error now. See #568
paulgibbs
commented
2 years ago I'm seeing this for one of my packages. Is there a backlog?
eluvitie
commented
1 year ago I just ran into this problem yesterday and the problem still exists today, that the package is stuck in the "Synchronizing" state. Creating a new organisation or try a different package does not work. @akondas might this be the same problem as you replied here on Feb 20, 2022?
Thanks for you help
eluvitie
commented
1 year ago As of today the syncing works again :)
when i want to sync my packages from gitlab or add new packages the sync gets stuck. Unfortunately I can't cancel the synchronization because there are no actions listed under "Actions". I don't have any logs either, because the packages are managed in your public instance. The last successful synchro took place about 7 days ago. Since then, I have not changed anything in my packages in terms of access.
What can I do to fix the problem ?
I know that there was a similar issue #73 but I don't host it myself, so I cant dig further into it.