Skip to content

fix: Cleanup output channels when restarting server #12470

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 5, 2022

Conversation

Veykril
Copy link
Member

@Veykril Veykril commented Jun 5, 2022

Fixes #12469

@Veykril
Copy link
Member Author

Veykril commented Jun 5, 2022

@bors r+

@bors
Copy link
Contributor

bors commented Jun 5, 2022

📌 Commit fd298b3 has been approved by Veykril

@bors
Copy link
Contributor

bors commented Jun 5, 2022

⌛ Testing commit fd298b3 with merge 6667061...

@bors
Copy link
Contributor

bors commented Jun 5, 2022

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing 6667061 to master...

@bors bors merged commit 6667061 into rust-lang:master Jun 5, 2022
@Veykril Veykril deleted the output-ch branch June 5, 2022 11:34
@bjorn3
Copy link
Member

bjorn3 commented Jun 5, 2022

Does this entirely remove the output channels when restarting? That may lose valuable debugging information. Would reusing the existing output channels be possible?

@Veykril
Copy link
Member Author

Veykril commented Jun 5, 2022

The Rust Analyzer Language Server is being lost and recreated on restart already (though sometimes it sticks), not sure if we can keep this one since VSCode is the one creating that.

The trace we should be able to keep.

bors added a commit that referenced this pull request Jun 5, 2022
internal: Keep output channels across restarts

cc #12470
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Log entries are not cleaned up when using "Restart server"
3 participants