Open prasannavl opened 5 months ago
Workaround: Seems removing --unstable-kv
from the compile step seems to resolve this.
Guess it's just not able to handle this assumption at the moment. Not a critical issue, will leave it open for a bit to document / consider it this is worth fixing.
Hey @prasannavl thanks for the report. I tried to reproduce the problem by running deno task build
and ./emissions-handler-bot
and I'm not enable to reproduce the problem.
Could you try to boil down the reproduction?
My understanding is:
Given:
{
"tasks": {
"compile": "deno compile --unstable-kv main.ts --output out"
}
}
out
binary./out --unstable-kv
-Panic-
I was able to repro this way. I suppose it's because the flag has already been applied in the compiled file.
I'm not sure what the expected behavior should be here though...
I get this issue as well in compile time if I have "unstable": ["kv"]
in the config and --unstable-kv
in the deno compile
call.
Hi @lucacasonato , I'd like to try solving this issue if it's still available. I expect that the approach should be to ignore repetitive occurrences of some unstable feature (e.g. kv, kv) and deal with it as one without panic (kv) while maintaining the support for multiple different unstable features, is that the case?
deno compile
step panic on start.