-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spurious error message when opening browser on macOS #334
Comments
That's not a real error, that's just Python trying to open browsers one by one until it finds one that works. So you don't have to worry about it. Fil should at least say "please ignore any error messages beyond this point, it's noise", or something. |
And thank you for reporting this! it's useful to know people find this disconcerting. |
Thanks for the update :) I raised this partly because I'm likely to roll this out to a bigger group, and needed to log messages about "ignore that error" as they definitely get worried if they see errors. So yeah as you say, it's benign but disconcerting. |
For now adding a warning. Switching to Rust's https://docs.rs/webbrowser/ is a longer-term solution, since it allows suppressing the noise. |
The workaround will be in v2022.3.0, which I hope to release today or tomorrow. |
Thanks! :) |
I'm getting an error message after running fil-profile in OSX Terminal (bash):
0:94: execution error: File some object wasn’t found. (-43)
As a minimal test case, I can reproduce this by following the getting started demo at https://pythonspeed.com/fil/docs/fil/getting-started.html which produces this result:
The report does open and looks about right according to the demo (this was my first time using Fil so I'm not super sure :))
I reproduced against python 3.10.2 and 3.8.12 (both installed with pyenv). This is on MacOS Big Sur 11.6.4. Don't have a Monterey machine handy to test that.
I saw some references to this perhaps needing a browser environmental variable, but setting that didn't silence the error. Obviously since it does appear to be working this isn't the end of the world, but it would still be nice to figure out how to fix it :)
The text was updated successfully, but these errors were encountered: