Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remote Agent log not shown in the Output dropdown #172642

Closed
isidorn opened this issue Jan 27, 2023 · 1 comment · Fixed by #172667
Closed

Remote Agent log not shown in the Output dropdown #172642

isidorn opened this issue Jan 27, 2023 · 1 comment · Fixed by #172667
Assignees
@sandy081
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release log VS Code log issues output Output channel system issues verified Verification succeeded
Milestone
January 2023

Comments

@isidorn
Copy link
Contributor

isidorn commented Jan 27, 2023

  1. macOS, Docker
  2. Reopen folder in Container
  3. Remote Agent log is not visible in the Output dropdown

Screenshot 2023-01-27 at 15 51 33
@isidorn isidorn added the output Output channel system issues label Jan 27, 2023
@sandy081 sandy081 added candidate Issue identified as probable candidate for fixing in the next release bug Issue identified by VS Code Team member as probable bug log VS Code log issues labels Jan 27, 2023
@sandy081 sandy081 added this to the January 2023 milestone Jan 27, 2023
sandy081 added a commit that referenced this issue Jan 27, 2023
@sandy081
fix #172642
a4fb6a7
@sandy081 sandy081 mentioned this issue Jan 27, 2023
Merged
sandy081 added a commit that referenced this issue Jan 30, 2023
@sandy081
fix #172642 (#172667)
47604ee
@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Jan 30, 2023
@sandy081 sandy081 reopened this Jan 30, 2023
@VSCodeTriageBot VSCodeTriageBot removed the unreleased Patch has not yet been released in VS Code Insiders label Jan 30, 2023
sandy081 added a commit that referenced this issue Jan 30, 2023
@sandy081
fix #172642 (#172667)
3771ed7
@sandy081 sandy081 mentioned this issue Jan 30, 2023
Merged
sandy081 added a commit that referenced this issue Jan 30, 2023
@sandy081
Merge pull request #172757 from microsoft/sandy081/voluntary-donkey
71700e7 
fix #172642 (#172667)
@roblourens roblourens added the unreleased Patch has not yet been released in VS Code Insiders label Jan 30, 2023
@VSCodeTriageBot VSCodeTriageBot removed the unreleased Patch has not yet been released in VS Code Insiders label Jan 31, 2023
@VSCodeTriageBot
Copy link
Collaborator

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been releaased

@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Jan 31, 2023
@isidorn isidorn added the verified Verification succeeded label Feb 1, 2023
@VSCodeTriageBot VSCodeTriageBot removed the unreleased Patch has not yet been released in VS Code Insiders label Feb 1, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sandy081 sandy081

Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release log VS Code log issues output Output channel system issues verified Verification succeeded
Projects
None yet
Milestone
January 2023
Development

Successfully merging a pull request may close this issue.

fix #172642 microsoft/vscode
4 participants
@roblourens @isidorn @sandy081 @VSCodeTriageBot