-
Notifications
You must be signed in to change notification settings - Fork 219
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
Console logging of sampling broken #1875
Comments
I can't reproduce this issue, it works fine for me with the most recent versions. As far as I know, there were no recent changes in Turing (which actually does only forward the However, ┌ LogLevel(-1): Sampling indicates that you might be missing a backend for ProgressLogging (such as e.g. TerminalLoggers, Juno, or VSCode). Maybe you (accidentally?) changed your Julia environment or REPL setup? |
Thanks @devmotion Interesting. Never had to do any of those manually. Is there a something specific you need to do to support terminal logging? A "using" or something like that? The vscode one seems to work fine. |
AbstractMCMC should take care of loading the backends if no progress-logging capable logging backend is available (https://github.com/TuringLang/AbstractMCMC.jl/blob/a9ba4d3b1c0314393532dbd792befa55750d9a0f/src/logging.jl#L39-L48). ConsoleProgressMonitor is deprecated but a while ago it worked better on Windows (with older Julia versions at least) and IJulia, hence we use it - if nothing else is present - on these setups. Maybe before you used (automatically) TerminalLoggers and now you use (automatically) ConsoleProgressMonitor (maybe because IJulia is loaded?)? Could you try loading TerminalLoggers explicitly and check if progress logging works fine then? |
Or, of course, maybe it's the other way around and before you used ConsoleProgressMonitor but now AbstractMCMC selects TerminalLoggers for you. |
No idea. This is just using the "readme" code in https://turing.ml/v0.21/docs/using-turing/quick-start with the most recent packages I can find, so I am not sure what else I could have messed up in my setup. The terminal is on windows if that helps. Julia 1.7.3 Alas, the TerminalLoggers didn't help. I tried to add a |
And loading ConsoleProgressMonitor explicitly didn't help either? These (ConsoleProgressMonitor and TerminalLoggers) are the automatic choices if a user does not set a progress logger explicitly, and the heuristic for this choice and the implementation of the log messages in Turing/AbstractMCMC has not been changed for quite some time. |
OK, I am going to close the issue. Looks like this may be a general issue with logging. Maybe new julia version or something like that. I will figure it out separately. Sorry to point my finger at Turing! |
@jlperla I noticed that TerminalLoggers holds back some dependencies on my system: JuliaLogging/TerminalLoggers.jl#43 I assume it's not related to your problem but nevertheless you could try to see if the PR helps. |
Using
[fce5fe82] Turing v0.21.6
and[366bfd00] DynamicPPL v0.19.3
or the most recent ones of those as well, I am seeing issues with console output of the logging. If I copy in the https://turing.ml/v0.21/docs/using-turing/quick-start example then I get output that looks likeetc. It doesn't overwriting the existing display like it used to in previous versions.
The text was updated successfully, but these errors were encountered: