websocat.x86_64-unknown-linux-musl on Ubuntu is seems to end before a message is received? about websocat

[jasondborneman]

The plot thickens. I tried an alternate client (wscat) and.. it's behaving similarly. Ended too fast and doing no output when it runs on GitHub Action runner ubuntu-latest.

Something about running websocket commands from a github action runner must be causing this. Open to any areas to poke into or 💡 ideas of why this might be the case. I know this isn't necessarily a bug in websocat now that I've dug further but sorta at my wit's end 😬

[vi]

Forward finished

What is being fed to stdin in CI scenario? Maybe it's /dev/null or something like that? This should be the difference between interactive run and CI run and can affect both clients.

Are you sending any WebSocket messages or only receiving them? If you want WebSocket to only receive the messages, use something like this:

websocat $websocketUrl -H "Authorization: Bearer $ACCESS_TOKEN" -U -n -v

i.e. "unidirectional-reverse" and "do not sent close message" options.

[jasondborneman]

Forward finished

What is being fed to stdin in CI scenario? Maybe it's /dev/null or something like that? This should be the difference between interactive run and CI run and can affect both clients.

Are you sending any WebSocket messages or only receiving them? If you want WebSocket to only receive the messages, use something like this:

websocat $websocketUrl -H "Authorization: Bearer $ACCESS_TOKEN" -U -n -v

i.e. "unidirectional-reverse" and "do not sent close message" options.

Just receiving messages. I'll try that out, thanks!

[jasondborneman]

I think that did it! Thanks so much for the suggestion. I was tearing my hair out! 😄