MediaBrowser / MediaBrowser/plugin.video.emby
[BUG] Race condition when updating the last sync date/time causes automatic updates to be mistaken for user changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 324
- Forks
- 185
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Essentially, this is a race condition that occurs when Emby Next Gen updates its own “last sync date/time.” The date and time are written separately, and the listener thread may read them in between the two writes, resulting in an inconsistent value. It then mistakenly interprets the plugin’s own automatic update as a manual change made by the user, then leads to a full sync!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the code that writes the last sync date/time and the listener that reads it, then reproduce the timing window described in the issue. Done means the listener no longer interprets the plugin’s own automatic update as a user change or triggers a full sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100