FurcyPin

Thank you for your quick response! Maybe I can fix my first issue by using `from_env` instead of `setenv` ? I will give it a try... > Dynaconf 3+ changed...

I confirm, using `from_env` instead of `setenv` solved my first issue like a charm.

I don't know, `from_env` uses a cache called `_env_cache`, so reloading an environment that has already been loaded costs nothing. On the other hand, `setenv` doesn't seem to use that...

Hi @mmarmol. The cache issue I mentioned was minor, simply values are cached twice. Being able to update the yaml on-the-file is a great idea. However I'm not sure I...

@mmarmol You need to create a `Parser parser = new CachingParser()` instead of a `Parser parser = new Parser()` for the cache to be enabled. Internally, the CachingParser uses a...

**About Caching:** this makes perfectly sense, sorry I didn't see you were using the same cache for all 3 entries **About Concurrency issue:** You may still have a concurrency issue...

Seems good. About the caching issue, I agree locking the cache might not be ideal. The only simple solution I see right now would be to modify your `Parser.parse()` method...

not on my side

Same here. I manage to find a solution [there](https://gist.github.com/andypetrella/6f3df40034aad48591d7f28d1c7697ff): ``` def ref_scala_object(object_name): clazz = jvm.java.lang.Class.forName(object_name+"$") ff = clazz.getDeclaredField("MODULE$") o = ff.get(None) return o ``` will return the associated object of...

I don't know if this is related, but I encountered the same error message while using duckdb-wasm on a table with index. I made a minimal working example to showcase...