Jupyter Lab - Host getting stuck after executing Out-ConsoleGridView
See original GitHub issueDescribe the bug
Basically, executing the cmdlet Out-ConsoleGridView (OCGV) sends the results to where the Jupyter host is running.
You can’t use neither the “sec” key nor the OCGV “F9” key to clear it.
It will only execute the command once, then it get stuck. Select .NET PowerShell notebook, and enter:
dir | ocgv
This works!
Enter a second command:
dir | select name | ocgv
At this time, .NET PowerShell stays “Busy” and won’t process the command.
Did this error occur while using dotnet interactive
?
- [PowerShell] .NET Jupyter Notebook
Screenshots
If applicable, add screenshots to help explain your problem. (See attached Image)
Please complete the following:
Even after the update, I’m getting the same issue: Tool ‘microsoft.dotnet-interactive’ was successfully updated from version ‘1.0.116704’ to version ‘1.0.117001’.
- OS
- Windows 10 PS C:\Users\max_t> $PSVersionTable
Name Value
PSVersion 7.0.0 PSEdition Core GitCommitId 7.0.0 OS Microsoft Windows 10.0.18363 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0 - [ ] macOS - [X] Linux (Please specify distro) : NAME=“Ubuntu” VERSION=“18.04.4 LTS (Bionic Beaver)” ID=ubuntu ID_LIKE=debian PRETTY_NAME=“Ubuntu 18.04.4 LTS” VERSION_ID=“18.04” HOME_URL=“https://www.ubuntu.com/” SUPPORT_URL=“https://help.ubuntu.com/” BUG_REPORT_URL=“https://bugs.launchpad.net/ubuntu/” PRIVACY_POLICY_URL=“https://www.ubuntu.com/legal/terms-and-policies/privacy-policy” VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic - [ ] iOS - [ ] Android
- Browser
- Chrome
- Edge
- Safari
- Frontend
- Jupyter notebook
- Jupyter lab
- nteract
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
We will be investigating an Out-GridView in Jupyter but we can’t use Out-ConsoleGridView for this. It’s a totally different technology stack.
I’m not really sure how .NET Interactive can get around this. It’d be the same behavior if you pop a GUI like with WPF or WinForms (or real
Out-GridView
). Considering the restart kernel is available to unblock users who get into that position, I think we can close this.Plus,
Out-ConsoleGridView
has been fixed to warn you about running it in .NET Interactive.