Closed perj closed 1 year ago
Seems to be coming from Brave. https://fossies.org/linux/brave-core/app/resources/generated_resources_sv.xtb
Unfortunately, we can't control what 3rd party tools print to STDOUT when capturing the STDOUT from okta-aws-cli
with an eval. I'm not certain to xde-open alternatives. However, we are using pkg/browser for popping the browser and I found this comment on the linux driver:
// There are multiple possible providers to open a browser on linux
// One of them is xdg-open, another is x-www-browser, then there's www-browser, etc.
// Look for one that exists and run it
Perhaps x-www-browser
or www-browser
will help, or using a different browser.
It's possible to set where the stdout of the command goes here: https://github.com/pkg/browser/blob/681adbf594b8314eb76d83a271f4a1c152d057d9/browser.go#L16
@perj I'll slip this in on the next release, nice find.
On Linux, when using
eval $(okta-aws-cli -b)
, I assume -b flag makes the tool execxdg-open
. Unfortunately, the output of that command is piped to stdout and become part of the string passed toeval
.For example, on my laptop it prints
which causes the error
The string is printed asynchronously, after xdg-open exits. Presumably it's piped from Chrome somehow, based on the output.