Some code in my package is generating the below warning. (Actually I think it’s probably 10-20 places). Presumably this is how I’m supposed to learn that I have to update my code. How do I get a list of the problematic call sites? (meaning, which lines in my package are causing these warnings, a…

@Lilith posted a trick to do this here by turning those warnings into errors: [image] Warning stack trace General Usage Julia doesn’t store stack traces for warnings. However, warning messages are typically written to the stderr stream, so you can turn such warnings to err…

Warning stack trace redirect_stderr(open(touch(tempname()), "r")) This is potentially a “neat” trick. Unfortunately, I have some @info statement elsewhere in the code that trigger first. I guess I’m back to grep. :frowning:

You could Pkg.develop ModelingToolkit and change the deprecation to emit an error instead of a warning.

Don’t do this in production or in a package, but you can disable all @info statements with @eval Base.CoreLogging macro info(args...) end

You can probably define a custom logger that prints the stack trace or throws an error on warning.

You can use LoggingExtras with a filter, this should allow you to modify the warning by adding a stacktrace

Not about warnings in general, but deprecation warnings are specifically about API, so if the deprecated call is really not written in a dependency (in which case it’s their fault, not yours), then a plain text search of "ODEProblem(" can identify the files and line numbers with your calls and you c…

These are all nice ideas, but I would love to help future Julia users. I would like to add a feature request somewhere so that warnings do something a little smarter (like a global option to show full stacktrade, and the short version hints at it.) I don’t even know where to ask? Is this Julia bas…

I believe these are from the base @deprecate macro. There are two open issues relevant to this thread: depwarn warnings should show location of the problem · Issue #19686 · JuliaLang/julia · GitHub Deprecation warnings that warn only when the deprecated call is directly "your fault" · Issue #49583…

[image] orebas: I would like to add a feature request somewhere so that warnings do something a little smarter (like a global option to show full stacktrade, and the short version hints at it.) I don’t even know where to ask? Is this Julia base? Is it in MTK? Julia already has --depwarn=error,…

How to find which code is generating a warning?

New to Julia

mkitti July 7, 2025, 7:25pm 2

@Lilith posted a trick to do this here by turning those warnings into errors:

Topic		Replies	Views
Warning stack trace General Usage	1	768	December 1, 2022
Parser deprecation warning Internals & Design	4	428	August 23, 2020
Help with deprecation warnings in tests New to Julia	1	780	November 12, 2020
Terminate after warning is thrown - global setting General Usage warning , control-flow	6	1114	April 10, 2025
Strange warning in 0.7 General Usage	6	895	August 18, 2018

How to find which code is generating a warning?

Related topics