You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure you are able to repro it on the latest version
Search the existing issues.
Steps to reproduce
Install the latest 1.0.0-preview.4 AIShell app and the corresponding AIShell module
Use iTerm2
Run Start-AIShell to start the sidecar experience
Observe the agent selection page of AIShell
This is likely a race condition between the rendering and start-aishell adjusting the sidecar pane width.
It doesn't always happen, for example, @StevenBucher98 cannot reproduce this on his macbook.
Usually, it may work fine for the 1st time, becuase AIShell may start up slow for the 1st time, so the rendering happens after the width adjustment is done. But subsequent startup is fast and the width is adjusted while rendering is on going, and the conflict will happen.
Expected behavior
The agent selection page should be rendered correctly.
Actual behavior
The rendering is messed up.
Error details
Environment data
1.0.0-preview.4
Version
1.0.0-preview.4
Visuals
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
Steps to reproduce
AIShell
moduleStart-AIShell
to start the sidecar experienceThis is likely a race condition between the rendering and
start-aishell
adjusting the sidecar pane width.It doesn't always happen, for example, @StevenBucher98 cannot reproduce this on his macbook.
Usually, it may work fine for the 1st time, becuase AIShell may start up slow for the 1st time, so the rendering happens after the width adjustment is done. But subsequent startup is fast and the width is adjusted while rendering is on going, and the conflict will happen.
Expected behavior
The agent selection page should be rendered correctly.
Actual behavior
The rendering is messed up.
Error details
Environment data
Version
1.0.0-preview.4
Visuals
No response
The text was updated successfully, but these errors were encountered: