Open Rich5 opened 10 months ago
Looks similar to https://github.com/long2ice/meilisync/issues/17
My work around (fix?) to this so far is to change line https://github.com/long2ice/meilisync/blob/dev/meilisync/main.py#L75
from:
current_progress = context.obj["current_progress"]
which appears to initialize current_progress to None, to:
current_progress = {}
My best guess is that there is a race condition where the current_progress is not initialized at https://github.com/long2ice/meilisync/blob/dev/meilisync/main.py#L105 before we try to set it https://github.com/long2ice/meilisync/blob/dev/meilisync/main.py#L130
I'm not sure if this break anything other features, but so far it's working for me.
I'm attempting to sync from postgres and I'm consistently getting this error below when running the latest code from this repo. Although I think the sync is still somewhat working because I can see the record count go up in the index and it appears to be matching the offset count of the current running query in postgres.
Looking at where this error is coming from does this mean that some some inserts into Meilisearch are working, but some batches are failing? It's hard to determine if records are missing while the sync is in progress and this database is over 20M records.
The full trace is below.