[dispatcharr-ranked-matchups] Bump to 1.15.0 - #201
Merged
dispatcharr-plugins-bot[bot] merged 1 commit intoJul 30, 2026
Merged
Conversation
Plugin Validation ResultsModified plugins: 1 Plugin:
|
| Check | Status | Details |
|---|---|---|
| Required fields | ✅ | All required fields present |
| Release artifact | ✅ | Artifact reachable at resolved URL |
| Maintainers | ✅ | Jacob-Lasky |
| License | ✅ | MIT - MIT License |
| Permission | ✅ | You have permission to modify this plugin |
| Version | ✅ | 1.15.0 |
| Version bump | ✅ | 1.14.2 → 1.15.0 |
View release v1.15.0 on GitHub · Compare v1.14.2...v1.15.0
🎉 All validation checks passed!
This PR modifies 1 plugin(s) and all checks have passed.
dispatcharr-plugins-bot
Bot
merged commit Jul 30, 2026
95e4c48
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
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.
Fixes intermittent login failures around plugin activity on some instances.
Standalone
applywas the last plugin action doing heavy DB work inside the gevent web worker. When it stalled a worker, nginx kept round-robining into it, so login — a multi-request flow — failed for roughly a quarter of attempts, and the3/minutethrottle then locked out the retries. It presented as "I can't log in", not as a slow plugin, and it survived two earlier fixes aimed at the same symptom (shrinking the apply transaction to sub-second, and closing a leaked scheduler DB connection).applynow runs in the same subprocessrefreshandauto_pipelinealready use, so no plugin action does bulk DB work in the web worker. It stays synchronous and still returns the real summary; the only visible difference is one to two extra seconds of child startup.Verified live on a 6588-channel instance: apply confirmed executing in the child, 1.6-2.2s end to end, login answering in ~0.4s while an apply was in flight (versus a 20s timeout recorded on the old code), and an unchanged database result afterwards.
Release: https://github.com/Jacob-Lasky/dispatcharr_ranked_matchups/releases/tag/v1.15.0
Changelog: https://github.com/Jacob-Lasky/dispatcharr_ranked_matchups/blob/main/CHANGELOG.md