aurelienbrabant Posts

aurelienbrabant

•Created by aurelienbrabant on 11/16/2023 in #help

Foreign key issue while attempting to delete workspace

Windmill version: self hosted CE v1.206.0-7 The PG database is the one provided with the docker compose setup (which I didn't update since I first installed windmill though) I attempted to delete a windmill workspace but was greeted with foreign key constraint violation errors. As I was in a hurry I fixed it myself by deleting manually the following rows (where WK_ID is the id of the workspace I wanted to delete) DELETE FROM queue WHERE workspace_id = 'WK_ID' DELETE FROM capture WHERE workspace_id = 'WK_ID' DELETE FROM draft WHERE workspace_id = 'WK_ID' After I ran this queries I was able to proceed with proper deletion of the workspace.

4 replies

WWindmill

•Created by aurelienbrabant on 8/13/2023 in #help

Object destructuring unparsable in main function

export interface ConfigType {
  key: string;
}

export async function main({ key }: ConfigType) {
}

export interface ConfigType {
  key: string;
}

export async function main({ key }: ConfigType) {
}

The following code causes windmill to error since it's unable to parse the main function's signature. This happens because of the object destructuring that's taking place. Probably a rightful wontdo but felt like I should also report this one.

12 replies

WWindmill

•Created by aurelienbrabant on 8/11/2023 in #help

Support for passing variables and resources in shell executor

Hi there, was wondering if there was any plan to support windmill's variable and resource types as script input arguments. Currently using a variable as an argument doesn't expand it, instead it displays the the path of the variable. Also I didn't find a way to specify a type for a resource argument, even using the customize pane. I know bash does not have types but I think expanding either the string value of the variable or the JSON of the resource as a string should be the behaviour. We can always leverage cli tools such as jq to extract the data we want. I'm well aware that it's possible to get specific variables and resources from inside a shell script but I'm truly looking for parametrisation here.

27 replies

WWindmill

•Created by aurelienbrabant on 8/8/2023 in #help

Utilities imported from scripts are not targeted by workspace deploy feature

Hi there, I was using the deploy EE feature that allows one to deploy a flow or scripts from a workspace to another in two clicks and found out that it looks like utility scripts used by deployed scripts are not listed as part of the deployable items. If a script targeted for deployment does contain such an import statement:

import { SomeType, someFunction } from 'f/some_folder/utils.ts'

// main signature and rest of my script making use of the imported items

import { SomeType, someFunction } from 'f/some_folder/utils.ts'

// main signature and rest of my script making use of the imported items

Then the f/some_folder/utils.ts item won't be included in the deployable item list, which eventually will make the deployed item unusable unless deploying the utility manually. I'm not sure it was clear enough and the workaround is easy, but thought it was worth reporting. Windmill version is Windmill EE v1.117.0. Probably very old given windmill's pacing but I don't know if it was noticed so

2 replies

WWindmill

•Created by aurelienbrabant on 7/30/2023 in #help

[CLI] --silent still printing unwanted logs using wmill flow run

I added the --silent flag to my wmill flow run command but it still prints WaitingForPriorSteps a few times on the standard output. It got rid of all the other logs though. The exact command I ran is :

wmill flow run --data '{ "some_id": "f14661818ab7a5cf917eff1c173623de" }' --silent some_flow

wmill flow run --data '{ "some_id": "f14661818ab7a5cf917eff1c173623de" }' --silent some_flow

And the output is:

WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
<ACTUAL_FLOW_RESULT>

WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
WaitingForPriorSteps
<ACTUAL_FLOW_RESULT>

Should it help output of wmill version is

CLI build against v1.138.0
Cannot resolve Backend Version

CLI build against v1.138.0
Cannot resolve Backend Version

2 replies

WWindmill

•Created by aurelienbrabant on 7/30/2023 in #help

[CLI] --debug conflicts with --data in short option form for wmill flow run

wmill flow run some_flow -d '{ "someId": "f14661818ab7a5cf917ff1c17a663de" }'
Debug logging enabled. CLI build against v1.138.0

Usage:   wmill flow run <path>
Version: v1.138.0

Description:

  run a flow by path.

Options:

  -h, --help                 - Show this help.
  --workspace   <workspace>  - Specify the target workspace. This overrides the default workspace.
  -d, --debug                - Show debug logs
  --show-diffs               - Show diff informations when syncing (may show sensitive informations)
  --token       <token>      - Specify an API token. This will override any stored token.
  -d, --data    <data>       - Inputs specified as a JSON string or a file using @<filename> or stdin using @-.
  -s, --silent               - Do not ouput anything other then the final output. Useful for scripting.

  error: Too many arguments: { "someId": "f14661818ab7a5cf917eff1c17a663de" }

wmill flow run some_flow -d '{ "someId": "f14661818ab7a5cf917ff1c17a663de" }'
Debug logging enabled. CLI build against v1.138.0

Usage:   wmill flow run <path>
Version: v1.138.0

Description:

  run a flow by path.

Options:

  -h, --help                 - Show this help.
  --workspace   <workspace>  - Specify the target workspace. This overrides the default workspace.
  -d, --debug                - Show debug logs
  --show-diffs               - Show diff informations when syncing (may show sensitive informations)
  --token       <token>      - Specify an API token. This will override any stored token.
  -d, --data    <data>       - Inputs specified as a JSON string or a file using @<filename> or stdin using @-.
  -s, --silent               - Do not ouput anything other then the final output. Useful for scripting.

  error: Too many arguments: { "someId": "f14661818ab7a5cf917eff1c17a663de" }

According to the displayed help -d maps to both --debug and --data options but practically only applies debug. Should it help output of wmill version is

CLI build against v1.138.0
Cannot resolve Backend Version

CLI build against v1.138.0
Cannot resolve Backend Version

15 replies

WWindmill

•Created by aurelienbrabant on 7/26/2023 in #help

Proper way of adding commands for bash scripts

Hi there ! I was wondering what's the proper way of adding programs so that they become executable from the bash script executor. Are we expected to build a custom worker image with the binaries in it or is there something I'm not aware of? Didn't find anything in the docs. By the way the executor says that pwsh is not found as an executable when getting started with the powershell template. I just upgraded my self hosted instance to CE v1.136.0-13-gcc597a17 if that can help.

10 replies