[iptv-checker] Bump to 1.26.2201040 - #221
Merged
dispatcharr-plugins-bot[bot] merged 1 commit intoAug 8, 2026
Merged
Conversation
Clearing a stuck progress file no longer clears a check that is actually running. Measured on a live install: two plugin discovery passes clamped a running check to idle mid-run, because the routine assumed nothing could be running when a plugin instance is constructed, which is false across worker processes.
dispatcharr-plugins-bot
Bot
added
the
Plugin Update
Plugin Validation ResultsModified plugins: 1 Plugin:
|
| Check | Status | Details |
|---|---|---|
| Required fields | ✅ | All required fields present |
| Release artifact | ✅ | Artifact reachable at resolved URL |
| Maintainers | ✅ | PiratesIRC |
| License | ✅ | MIT - MIT License |
| Permission | ✅ | You have permission to modify this plugin |
| Version | ✅ | 1.26.2201040 |
| Version bump | ✅ | 1.26.2191412 → 1.26.2201040 |
View release v1.26.2201040 on GitHub · Compare v1.26.2191412...v1.26.2201040
🎉 All validation checks passed!
This PR modifies 1 plugin(s) and all checks have passed.
Other plugins by PiratesIRC in this repository (6)
| Plugin | Slug | Version |
|---|---|---|
| Channel Mapparr | channel-mapparr |
1.26.2170831 |
| EPG Janitor | epg-janitor |
1.26.1791309 |
| Event Channel Managarr | event-channel-managarr |
1.26.1711720 |
| Lineuparr | lineuparr |
1.26.2171315 |
| Newsflasharr | newsflasharr |
1.26.2191208 |
| Stream-Mapparr | stream-mapparr |
1.26.2141957 |
dispatcharr-plugins-bot
Bot
merged commit Aug 8, 2026
d663a41
into
Dispatcharr:main
10 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the listing from 1.26.2191412 to 1.26.2201040. Manifest only; this plugin is listed in external mode, so the archive comes from the release the
source_urlresolves to.Clearing a stuck progress file no longer clears a check that is actually running. Measured on a live install on 2026-08-08: two plugin discovery passes, at 04:24:58 and 04:29:31, each clamped a running check to idle, at 418 of 2691 streams and then 488 of 2691.
The routine exists for a real problem: a container kill bypasses the code that marks a check finished, so the file is left saying "running" forever and every later scheduled fire defers to a check that is not there. Its assumption was the flaw. It ran from the plugin constructor and assumed nothing could be running at that moment, which holds inside one process and does not hold across the several worker processes Dispatcharr runs, because a discovery pass constructs a plugin instance in whichever worker serves it.
It now stamps the container boot token into the progress file on every write and uses it to tell the two situations apart. A file from a previous container cannot belong to a running check. Within one container life the file's modification time decides instead, since a live check rewrites it continuously, with a threshold far above the write cadence: clearing a live run is worse than leaving a dead file for a few more minutes.
Verified before submitting: the resolved
source_urlreturns HTTP 200, and the full test suite (473 tests, 10 of them new and covering both situations) and the linter pass at the tagged commit.