Powershell stop receiving inputs after remote interactive connection while using ohmyposh

[HDANILO]

Code of Conduct

• I agree to follow this project's Code of Conduct

What happened?

Hi,

Today I got a little stuck because my terminal would stop completely responding if I used aws command:

aws ecs execute-command --cluster "your_cluster" --command "/bin/sh" --interactive --task "your_task"

To connect to the ecs's task terminal(it should be the same as sshing into the instance).

The connection worked correctly, but then, no keys I press is rendered to the screen(I'm not sure if they are sent to the remote).

Disabling oh-my-posh from my $PROFILE fixed the issue.

Tried changing themes just to be sure, it didn't fix the issue too

Theme

https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/themes/cobalt2.omp.json

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Log output

No way to get the log output because the terminal becomes completely dead after this, ctrl-c doesn't work, neither ctrl-z, I have to quit the terminal completely to be free from it.

[JanDeDobbeleer]

@HDANILO how do you initialise oh-my-posh?

[HDANILO]

oh-my-posh init pwsh --config "https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/themes/cobalt2.omp.json" | Invoke-Expression

first line in my $PROFILE file

[JanDeDobbeleer]

Aha. Yeah well that will always download the file. GitHub doesn't have etags on the objects which doesn't allow us to validate if we should fetch it again. Best to use that file locally instead.

[HDANILO]

Indeed using locally fixed it, I just don't understand why, the oh-my-posh was already loaded by the time I used the aws ecs execute-command, but perhaps it has something to do with the ecs execute-command internal spawning a new child process?

[JanDeDobbeleer]

@HDANILO yes, that could always mess up things.