[Feature] Diversion-group to proxy bindings should persist (not silently reset to "current selected")
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- dart
- Domain
- networking
Research direction
Start by tracing where diversion-group bindings are persisted and where global current-server changes or subscription refreshes update them. Verify that bindings to a fixed node, Auto (urltest), and direct survive both operations; done means they no longer silently revert to current selected.
Written by the indexing model from the issue text.
Description
Feature description
A custom diversion group can be bound to a specific target — a fixed node, an Auto (urltest) group, or direct. In our setup a group that had been explicitly bound to Auto (urltest) was later found reverted to "current selected" (following the global server), silently — so the intended auto-select behavior had quietly stopped.
We haven't fully isolated the trigger yet (suspected: changing the global "current server" in the UI, and/or a subscription update, resets per-group bindings). Please treat per-group bindings as durable state that is not reset by switching the global current server or by a subscription refresh — and, if this is a bug, fix the reset.
Use case
Reliability of any per-group routing. If bindings can silently revert to "current selected," any setup relying on a group being on Auto / a fixed node / direct quietly decays — the user believes a service is auto-failing-over (or pinned/direct), but it isn't, and only finds out when the service breaks. Durable, non-resetting bindings are a prerequisite for trustworthy per-service routing and auto-failover.
Target OS
Observed on macOS; likely all platforms.
- Dominant language
- Dart
- Stars
- 16k
- Forks
- 1.3k
- Avg merge
- 19h 39m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from KaringX/karing
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Similar issues
-
documentation good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 72/100
Is0cre/MonkeyThrive#6 ·
-
[Super Keyboard][Android][Bug] - Don't stop Flutter from receiving keyboard height frame changesOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Flutter-Bounty-Hunters/super_editor#3150 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
bia-pain-bache/BPB-VPN#14 ·