Unhandled resource exception on pure IO action about tasty-bench HOT 6 CLOSED

You don't need env (evaluate (force (a, m)), a simple env (pure (a, m)) would suffice, because env forces the resource internally:

(It seems the documentation of env is misleading, it can use a fix)

tasty-bench defers resource management to tasty. Is it possible to reproduce the issue with tasty itself?

from tasty-bench.

Thank you for your prompt reply! I changed the code to use just pure but the same issue, remains.

tasty-bench defers resource management to tasty. Is it possible to reproduce the issue with tasty itself?

What do you mean, tasty does not have any env function, only withResource which has a very different type signature. How can I try to reproduce the issue with tasty, given that I believe the issue is in env ?

from tasty-bench.

env is a thin wrapper over withResource. If you inline env and underlying envWithCleanup, you'll obtain a reproducer via withResource. You can further simplify your example replacing bench with a simpler test ingredient, say testCase.

from tasty-bench.

Thank you! Yes I tried that and still get the same problem. I inlined everything up to withResource and used something other than bench, but no success

from tasty-bench.

So if it's not tasty-bench specific, could you forward the issue to tasty issue tracker?

from tasty-bench.

Please see this comment: UnkindPartition/tasty#401 (comment)

from tasty-bench.