[Bug]: last_read_message_id wont be updated when docker stop

[namaiwa]

telegram_media_downloader version or commit

v2.2.4

What OS are you seeing the problem on?

Other Linux Distro

Python Version

No response

What happened?

last_read_message_id wont be updated when docker stop. I think the last_read_message_id and ids_to_retry should be updated
when every item download finished.

Expected Behavior

last_read_message_id should be updated

Current Behavior

last_read_message_id did not be updated when docker stoped.

Possible Solution

No response

Steps to Reproduce

No response

Relevant log output

No response

[viniciusbig]

Same here!

Am I missing something?

It seems the config.yaml file is not being updated with last information.

Specailly the last_read_message_id field.
So everytime docker starts it will run the entire channel again checking for messages.

It could be something with permission to write on that file?

[viniciusbig]

it seems we have a potential fix (and root cause) already in a PR.

this PR was not merged and t seems to address exactly this issue

[Tiande]

same problem