#stuck at pending after pushing
1 messages · Page 1 of 1 (latest)
uploading now
I got the same problem except mine didn't even start
I got the same problem, it took around 1h before it's start building. Honestly infuriating.
same issue!!
it's not anymore now, but I recreated the endpoint though @remote garnet
i got another one again
chat am i cooked
@sudden viper have you tried recreating the endpoint?
it works for me
😭
you should start seeing better progress in few mins, i have raised number of workers that are handling the queue, in the meantime i will raise this to our ops team and have it tracked better so this doesnt happen again
mans using flex workers on our pushes 😭
we are using our cpu serverless to handle this, bottleneck was our max workers was too low 🙁
same problem🥲
still until now?
The first deploy took about 6 hours and I have no idea when it switched to building state, now the second deploy I did was 15 minutes ago and I'm not sure where it will stay in pending state for so long
Good news, it's starting to build👏🏻
I'm still stuck on a pending loop.
Open a support ticket if it takes very long time
istg if you using flex worker on my serverless, i will cry so bad
ok ngl this seems like a serious problem lol
WHAT DOES THIS MEAN COMPLETE OR ERROR LOL
ok it means complete..
Huh what's the error then? If you don't mind explaining
yooo help me open a ticket?? i got another problem
@sudden viper
The thread has been escalated to Zendesk!
Same issue here as well, two serverless job more than 5 hours of queuing, any reason, it happened like only from last week
I'm having the issue as well
long pending again
Can someone help 🥲 I already submitted a ticket
@wicked forge
its fixed, will share more news on the actual issue
Hey still seeing multi-hour pending build issue :/
i think the issue is not only related with number of worker that assign for building, otherwise it should be last for many days
currently i am trying to resolve this by building my own CICD pipeline and update the template with docker iamge, any other alternatives ?
Can you try now? I think we will have more info later, but it should be functioning normally now.
yea i made a ticket , they said they found the root cause and are working to fix it, they also said As a temporary workaround, some users have found success by pushing their image to Docker Hub and deploying from there.
I personally will just wait, but yea thats a possible solution
just did that, not perfect yet, still need to find a way to optimized CICD to triggger serverless worker to update ...
thank u
Hey, no meaningful updates yet but there's one more problem that's being worked on.
quick update before any announcement goes out, we are resolving it as we go, its less of a bug and more of someone abusing the system since its free
so u mean someone basically abuse the system and push like millions jobs to occupying the whole worker node for building?
Something like this, yes.
seems to be working now, fyi!
@gleaming token @wicked forge NOOOOOOOOOOOOOOOO not this again, create more active workers
Resolved, again - similiar case to this thread it's an abusive user intentionally using up all the capacity