@mederka This was triggering an interesting bug. The error was about --force , but it got removed (replaced with --yes) in isolate 0.12.9 which got released on shark a few days ago. I think it was a symptom of a bug, where somehow our workers install new isolate, but somehow run older code. Wasn't able to figure it out yet...
@mederka This was triggering an interesting bug. The error was about
--force, but it got removed (replaced with--yes) in isolate 0.12.9 which got released on shark a few days ago. I think it was a symptom of a bug, where somehow our workers install new isolate, but somehow run older code. Wasn't able to figure it out yet...