Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: pass session token to network extension#34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ethanndickson merged 1 commit intomainfromethan/ne-session-token
Jan 30, 2025

Conversation

ethanndickson
Copy link
Member

@ethanndicksonethanndickson commentedJan 30, 2025
edited
Loading

This PR:

With this, the VPN functionality works end-to-end! Once the system extension is enabled, and the app has been logged in, starting the VPN will make the user's workspaces available on<wsname>.coder

@ethanndicksonGraphite App
Copy link
MemberAuthor

This stack of pull requests is managed byGraphite. Learn more aboutstacking.

@@ -0,0 +1,3 @@
--selfrequired log,info,error,debug,critical,fault
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

From thedocs:

In the rare case of functions with@autoclosure arguments, self may be required at the call site, but SwiftFormat is unable to detect this automatically. You can use the --selfrequired command-line option to specify a list of such methods, and the redundantSelf rule will then ignore them.

throw .alreadyRunning
}
running = true
return AsyncStream(
Copy link
MemberAuthor

@ethanndicksonethanndicksonJan 30, 2025
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

messages() is called each timenext() is called on theSpeaker, but it's not possible to mutate therunning variable from within the stream in Swift 6.

Even if it were possible, I don't think this check is of any value. Isn't it usually the case (in general) that iterating over the same (mutating) stream multiple times is just an incorrect use of an API? I think actor re-entrancy means it's possible to do so here.

If we do want to keep the check, I'm open to suggestions on how best to do that.

@ethanndicksonethanndickson marked this pull request as ready for reviewJanuary 30, 2025 03:25
@ethanndicksonethanndickson merged commitf3123f1 intomainJan 30, 2025
4 checks passed
@ethanndicksonethanndickson deleted the ethan/ne-session-token branchJanuary 30, 2025 10:49
@ethanndicksonethanndickson self-assigned thisFeb 12, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@coadlercoadlercoadler approved these changes

@ThomasK33ThomasK33Awaiting requested review from ThomasK33

Assignees

@ethanndicksonethanndickson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@ethanndickson@coadler

[8]ページ先頭

©2009-2025 Movatter.jp