Relay selector doesn't force a blocked state with daita and obfuscation on #7324
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.
Bug repro steps:
Observed behavior:
The app tries to use multihop to connect because no dutch DAITA relays have extra_shadowsocks_addr_in.
Expected behavior:
If the app cannot connect to a DAITA relay due to a constraint that only applies to entry relays, the app should enter the blocked state.
This change is