Skip to content

bug: unable to push a new script in a new directory while local development #7352

@jjangga0214

Description

@jjangga0214

Describe the bug

Cannot push a new script.

To reproduce

  1. From local development, create a new script inside a new directory.
wmill script bootstrap u/<username>/a-new-directory/a-new-script bun
  1. Push it.
wmill script generate-metadata --yes && wmill sync push --yes
  1. An error happens

real example

  windmill git:(main) ✗ (☸|p-m-prod:default) wmill script generate-metadata --yes && wmill sync push --yes

(omitted some messages)

Generating metadata for u/iaesiiyw/gcp/gcs/upload.ts
file:///opt/homebrew/lib/node_modules/windmill-cli/esm/src/utils/metadata.js:181
                throw new LockfileGenerationError(`Failed to generate lockfile: ${response?.["error"]?.["message"]}`);
                      ^

LockfileGenerationError: Failed to generate lockfile: execution error:
Error locking file: Non-zero exit status for bun build: 1

logs:
job=019b0be2-6040-0b73-c36d-3f32cbcc05ac tag=bun worker=wk-default-bbca5781d8d0-IaVIT hostname=bbca5781d8d0
---
WARNING: This job has concurrency limits enabled. Concurrency limits are an EE feature and the setting is ignored.
---
error: Failed to find relative import at http://127.0.0.1:36729/api/w/ambrosia/scripts/raw_unpinned/p/u/iaesiiyw/gcp/gcs/upload/.././index.ts
    at /tmp/windmill/wk-default-bbca5781d8d0-IaVIT/019b0be2-6040-0b73-c36d-3f32cbcc05ac/u/iaesiiyw/gcp/gcs/index.ts.url:0
Failed to build bundle
    at updateScriptLock (file:///opt/homebrew/lib/node_modules/windmill-cli/esm/src/utils/metadata.js:181:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async generateScriptMetadataInternal (file:///opt/homebrew/lib/node_modules/windmill-cli/esm/src/utils/metadata.js:99:13)
    at async Command.generateMetadata [as actionHandler] (file:///opt/homebrew/lib/node_modules/windmill-cli/esm/src/commands/script/script.js:759:13)
    at async Command.execute (file:///opt/homebrew/lib/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:///opt/homebrew/lib/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:///opt/homebrew/lib/node_modules/windmill-cli/esm/src/main.js:145:9)

Node.js v25.2.1
  1. To workaround, create and deploy a new script with the same path from windmill UI.
    And then do the step 2 again.

Expected behavior

It should just create a new script on the remote instance.

Screenshots

No response

Browser information

No response

Application version

No response

Additional Context

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions