Warning in SciMLBase about ContinousClock

Specific Domains Modelling & Simulations
,
1

During precompilation I get this warning. How could I avoid this? I have this version v2.155.1

SciMLBase
│  ┌ Warning: the bare singleton variant syntax `ContinuousClock` is deprecated, write `ContinuousClock()` instead (near C:\Users\User\.julia\packages\SciMLBase\hLfdZ\src\clock.jl:4)
│  │   caller = eval(m::Module, e::Any) at boot.jl:489
│  └ @ Core .\boot.jl:489
└
2

Welcome to the Julia community!

Hopefully, this warning gets fixed soon, but for the time being, it will just work anyway.

3

I registered a backport fix.

I recommend updating to SciMLBase v3 since you’re on very old versions now, but at least the patch to v2 will make the warning go away.

4

There is one more warning we get, which might be related therefore I post it here:

┌ ModelingToolkit
│  [Output was shown above]
└  
┌ ModelingToolkitTearing
│  ┌ Warning: the bare singleton variant syntax `IntegerSequence` is deprecated, write `IntegerSequence()` instead (near C:\Users\ufechner\.julia\packages\ModelingToolkitTearing\GxqLM\src\clock_inference\clock_inference.jl:15)
│  │   caller = eval(m::Module, e::Any) at boot.jl:489
│  └ @ Core .\boot.jl:489
└
5

SciMLBase v2 again?

6

That one’s not SciMLBase it’s ModelingToolkitTearing’s own @data ClockVertex block. Same Moshi deprecation, fixed in ModelingToolkitTearing v1.20.2 (latest is v1.20.3). ]up should clear it. If it doesn’t move, ]st ModelingToolkitTearing and whatever is holding it back is the real culprit.