-
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
default root logger output results in a TTY(invalid status, ...)
on 0.4
#28
Comments
…yground")` to .travis.yml. * Fix doesn't support the '_' environment variable used to get the julia path so we resort to calling which julia if '_' isn't set. * Logging.jl currently has an [issue](kmsquire/Logging.jl#28) where it will segfault writing to an invalid TTY occasionally (mostly due to a precompiled reference to STDOUT).
@Rory-Finnegan, sorry not to respond sooner. I working back through older issues in various packages I own/have a stake in. Unfortunately, it's totally unclear to me what it is happening here. I've run the same commands on OSX and don't have any problems. When you get the chance, can you:
|
@kmsquire No worries, I don't think this is a huge issue anyways. Yes, this is being run inside a playground, which changes So, running it with v0.4.3 still produces the same error.
Interestingly, in another playground with the same julia version and same version of Logging.jl installed I don't get the error.
Maybe something weird is happening with precompilation in the one playground...? I know that precompiling IO references like STDOUT can have weird behaviour, which might explain that prior to the segfault the TTY shows |
So I initially came across this problem when I found this.
I can confirm that is isn't related to some other packages I have installed as I tried this with a fresh package directory. Similarly, I've tested that this happens on both v0.4.0 and v0.4.1.
My temporary solution is to specify the output with:
The text was updated successfully, but these errors were encountered: