invakid404
invakid404•2mo ago

Weird error in flow lockfile generation

We're getting this weird error when trying to run wmill flow generate-locks: 
Error: Failed to generate lockfile. Status was: Internal Server Error, reading response failed, LockfileGenerationError: Failed to generate lockfile: execution error:
Error: invalid type: floating point `1.5`, expected u16 at line 1 column 223 @worker_lockfiles.rs:868:13
    at updateFlow (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/metadata.js:283:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async generateFlowLockInternal (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/metadata.js:95:27)
    at async Command.generateLocks [as actionHandler] (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/flow.js:227:13)
    at async Command.execute (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/deps/jsr.io/@windmill-labs/cliffy-command/1.0.0-rc.5/command.js:970:13)
    at async Command.parseCommand (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/deps/jsr.io/@windmill-labs/cliffy-command/1.0.0-rc.5/command.js:852:20)
    at async main (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/main.js:142:9)
Error: Failed to generate lockfile. Status was: Internal Server Error, reading response failed, LockfileGenerationError: Failed to generate lockfile: execution error:
Error: invalid type: floating point `1.5`, expected u16 at line 1 column 223 @worker_lockfiles.rs:868:13
    at updateFlow (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/metadata.js:283:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async generateFlowLockInternal (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/metadata.js:95:27)
    at async Command.generateLocks [as actionHandler] (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/flow.js:227:13)
    at async Command.execute (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/deps/jsr.io/@windmill-labs/cliffy-command/1.0.0-rc.5/command.js:970:13)
    at async Command.parseCommand (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/deps/jsr.io/@windmill-labs/cliffy-command/1.0.0-rc.5/command.js:852:20)
    at async main (file:///node_modules/.pnpm/windmill-cli@1.478.1/node_modules/windmill-cli/esm/main.js:142:9)
When I open the Windmill UI and look at the Deps runs to try and learn more, it doesn't even load the task. Instead, the devtools console just fills up with ApiError: Internal Server Error and a bunch of 500 status codes from /api/w/mandel/jobs_u/get/<job_id>?no_logs=true with the same exact error. Running v1.479.3 all around (instance and CLI)
1 Reply
invakid404
invakid404OP•2mo ago
Deploying from the UI results in the same error as well, so it does not appear to be CLI-related OK, I figured it out, it is related to retry.exponential.multiplier I had it to set to 1.5, the UI never complained, so I always assumed it's valid?

Did you find this page helpful?