Martijn Visser

That is strange, this should work. I tried, but cannot reproduce: ```julia using Wflow # modified TOML to have # [input.lateral.subsurface] # ksathorfrac.value = 1.0 config = Wflow.Config("test/sbm_simple.toml") config.input.lateral.subsurface.ksathorfrac.value #...

Oh yes if you use Wflow.run with a config object rather than a path to a TOML file it doesn't create the logging file. This is mentioned in the docstring...

Perhaps it is almost exactly and integer, but not quite since it comes from floating point math. ```julia julia> t = 10 * (0.1 + 0.2) 3.0000000000000004 julia> Int(t) ERROR:...

Can you try `ArchGDAL.gdalbuildvrt`? See also #142. It could be that the file is only written to disk when the finalizer gets called.

That is the signature of the do block syntax, like in https://docs.julialang.org/en/v1/manual/functions/#Do-Block-Syntax-for-Function-Arguments. But I believe the same arguments as you used for the unsafe version are also supported. It just...

Ah you're right there is a difference between the two. Note that it does not take a vector of paths, but a vector of opened datasets. Here are two examples:...

> `gdalbuildvrt` should also be callable without the `do` block Yeah I think so as well. Let's keep this issue open to track that.

Which version of ArchGDAL does this still work on? Or could it be due to the new GDAL 3.6 build that comes with GDAL.jl v1.5, which was released recently?

Ok for this hang it's still useful to know the extra information I asked for, to know whether it's ArchGDAL.jl or the GDAL build we ship.

Can you try GDAL.jl v1.4, and otherwise the previous ArchGDAL release?