Closed seedifferently closed 4 months ago
If you have a per-worker throttle which is heavily contended, I can see this happening. Interesting that no one else found this, the code has been stable for 3-4 years now. Working on the fix.
@mperham thanks for jumping on this! Do you have a sense of when you'll cut a release? I'm planning the changes on our side but no rush.
I'm leaving on vacation end of next week so I'll probably ship it this time next week.
Any updates here?
Let's get that release out! 😂 Expect 1.9.1 soon.
1.9.1 is out.
Getting an issue trying to docker pull docker.contribsys.com/contribsys/faktory-ent:1.9.1
-> Error response from daemon: manifest for docker.contribsys.com/contribsys/faktory-ent:1.9.1 not found: manifest unknown: manifest unknown
I spent two hours trying to figure this out. No luck so far but I’m acknowledging that the issue exists. My “docker push” has no errors but the server does not show 1.9.1 on the filesystem.
What a brined 🥒 . Thanks for acknowledgment and I'll keep an eye here for a fix 🤞
It took me two days to figure out that OrbStack had hijacked the local port and was somehow "stealing" the pushes to docker.c.c. 1.9.1 should now be available.
Our Faktory Enterprise process crashed this morning with a
fatal error: concurrent map writes
as we were ramping up a batch of about 30k jobs. We're running 1.8.0 and don't see anything in the 1.9.0 changelog that indicates there's been a bugfix for something like this.Here's a head snippet of the crash log, I can provide the full output if needed: