Closed bgruening closed 2 months ago
What's the link with the sentry issue ? These seem to be different stack traces for different jobs. I also don't see the link with S3 from these issues.
I can't make sense of the traceback in the opening issue. This is the simplest possible pydantic model
class ConcreteObjectStoreModel(BaseModel):
object_store_id: Optional[str] = None
private: bool
name: Optional[str] = None
description: Optional[str] = None
quota: QuotaModel
badges: List[BadgeDict]
device: Optional[str] = None
My best guess is that there was a dependency problem, maybe incompatible pydantic and pydantic-core packages ?
FWIW fail_fast
was added in pydantic 2.8.0 which was released yesterday (https://github.com/pydantic/pydantic/releases/tag/v2.8.0). Is there any chance you accidentally upgraded pydantic but not pydantic core ?
That was wird. Our venv was updated and it shouldn't. Removing the object_store helped because this was the only code-path the new venv triggered the incompatibility.
We only have one test object_store enabled that is not used by default. And all of a sudden all our jobs failed with this error. I assume the S3 was not reachable for some time. Commenting out the S3 config and restart handlers do work for us.
Here is the stack-trace.