Naillik
Naillik
WWindmill
Created by Naillik on 2/26/2024 in #help
wmill sync push error
Hi, I'm hitting some cryptic errors trying to promote changes made on a staging workspace to a production workspace. I've noticed two problems when I try to push changes that are deployed and functioning on my staging workspace to production: 1. When I run wmill sync push --raw <skip-opts> --include-schedules, it fails with this error:
❯ wmill sync push --raw --skip-resources --skip-variables --skip-secrets --include-schedules

Creating new schedule: f/my_folder/schedule_x_reminder
Not found: script not found at name f/my_folder/x_reminder
❯ wmill sync push --raw --skip-resources --skip-variables --skip-secrets --include-schedules

Creating new schedule: f/my_folder/schedule_x_reminder
Not found: script not found at name f/my_folder/x_reminder
This is despite the fact that a script f/my_folder/x_reminder exists on my local. 2. When I run wmill sync push --raw <skip-opts>, it fails with an error that tells me very little as to what went wrong:
❯ wmill sync push --raw --skip-resources --skip-variables --skip-secrets
...
Applying changes to files ...
error: Uncaught (in promise) Error: No content path given and no content file found.
throw new Error("No content path given and no content file found.");
^
at findContentFile (https://deno.land/x/wmill@v1.242.0/script.ts:254:11)
at eventLoopTick (ext:core/01_core.js:182:7)
at async handleScriptMetadata (https://deno.land/x/wmill@v1.242.0/script.ts:59:25)
at async Command.push [as actionHandler] (https://deno.land/x/wmill@v1.242.0/sync.ts:737:11)
at async Command.execute (https://deno.land/x/cliffy@v1.0.0-rc.2/command/command.ts:1948:7)
at async Command.parseCommand (https://deno.land/x/cliffy@v1.0.0-rc.2/command/command.ts:1780:14)
at async https://deno.land/x/wmill@v1.242.0/main.ts:133:3
❯ wmill sync push --raw --skip-resources --skip-variables --skip-secrets
...
Applying changes to files ...
error: Uncaught (in promise) Error: No content path given and no content file found.
throw new Error("No content path given and no content file found.");
^
at findContentFile (https://deno.land/x/wmill@v1.242.0/script.ts:254:11)
at eventLoopTick (ext:core/01_core.js:182:7)
at async handleScriptMetadata (https://deno.land/x/wmill@v1.242.0/script.ts:59:25)
at async Command.push [as actionHandler] (https://deno.land/x/wmill@v1.242.0/sync.ts:737:11)
at async Command.execute (https://deno.land/x/cliffy@v1.0.0-rc.2/command/command.ts:1948:7)
at async Command.parseCommand (https://deno.land/x/cliffy@v1.0.0-rc.2/command/command.ts:1780:14)
at async https://deno.land/x/wmill@v1.242.0/main.ts:133:3
Here's where the error's coming from: https://deno.land/x/wmill@v1.242.0/script.ts?source=#L247 This error doesn't really tell me anything. Is windmill verifying a referenced <resource/script/variable> exists and preventing pushes if not? If so, which one? Why? Thanks for any help.
1 replies
WWindmill
Created by Naillik on 2/22/2024 in #help
Renaming background runnable IDs?
Is it possible to rename background runnable IDs? Being able to name component IDs is super helpful for organizing, but I can't tell if this is implemented for background runnables.
1 replies
WWindmill
Created by Naillik on 2/15/2024 in #help
Background Runnable not triggering on App start
Hi, I have an App that loads the data it needs using a few background runnables that are configured to trigger on App start / refresh & input changes. However, none of these scripts are running when the app is loaded — I need to manually click the app refresh button to run them for the first time. When I do, they all run as expected without issue. I found this related thread (https://discord.com/channels/930051556043276338/1169575765063520326/1186334618681614396) but it seems that no cause was discovered. Any ideas as to what could be causing this?
22 replies