fix: start coder connect on launch after SE is installed #113
Conversation
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
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ethanndickson
commented
Mar 19, 2025
Comment on lines
+82
to
+85
| deinit { | ||
| NotificationCenter.default.removeObserver(self) | ||
| } | ||
|
|
There was a problem hiding this comment.
Drive-by fix: this was on the wrong class, though that wasn't causing any issues.
ethanndickson
commented
Mar 19, 2025
Comment on lines
+110
to
+115
| try Mock( | ||
| url: url.appendingPathComponent("/api/v2/users/me"), | ||
| statusCode: 200, | ||
| data: [.get: Client.encoder.encode(User(id: UUID(), username: "username"))] | ||
| ).register() | ||
|
|
There was a problem hiding this comment.
Drive-by fix: We need to mock this route as the token is validated before the server version.
deansheather
approved these changes
Mar 19, 2025
ThomasK33
approved these changes
Mar 19, 2025
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.
This is a fix for #108. Previously we would start the VPN immediately on launch if the config option was true. This starting of the VPN raced with any concurrent upgrades of the network extension, causing the VPN to be started with a VPN config belonging to the older network extension, and producing a consistent error message:
Instead, we should only start the VPN once we know that the system extension and VPN configuration are installed.