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
While debugging a brand new free trial plan with @nicolasvienot we noticed that Meilisearch couldn't start due to an empty VERSION file. It's very strange as it seems quite rare. However, it doesn't seem impossible as writing to this file is not as enforced as when we use LMDB. We could have missed a disk sync or something.
The VERSION file was never populated with anything as the issue appeared at creation time.
Meilisearch version:
We don't know the impacted version but at least before v1.7.4.
Additional context
It was running on the cloud, more specifically on Digital Ocean in a Kubernetes and Docker container.
The text was updated successfully, but these errors were encountered:
I rewrote this thing with the VERSION file in v0.30; there were some issues with it, which were fixed by patch releases.
And then, no one ever modified it, as far as I know.
So I’m pretty confident that all the versions since the v1.0 are impacted 😬
While debugging a brand new free trial plan with @nicolasvienot we noticed that Meilisearch couldn't start due to an empty VERSION file. It's very strange as it seems quite rare. However, it doesn't seem impossible as writing to this file is not as enforced as when we use LMDB. We could have missed a disk sync or something.
The VERSION file was never populated with anything as the issue appeared at creation time.
Meilisearch version:
We don't know the impacted version but at least before v1.7.4.
Additional context
It was running on the cloud, more specifically on Digital Ocean in a Kubernetes and Docker container.
The text was updated successfully, but these errors were encountered: