Any known issues that might be causing a step in a flow to wait for 30±0.2 seconds about 70% of the time before it starts executing? I've added a log on the top of the bun execution and it takes 30 seconds for it to log so I don't think it is because of my code directly.
@paales if you want help you will want to provide a ton more context. Does it happen for all bun jobs, or just that one, can you reproduce on other instances, other worker groups, etc
Is there a way to make it so a script / flow doesn't log its args at all? Trying to point a webhook towards wmill but the webhook pushes 300kbs of data and I would be seeing this thousands of time a day
i would still want to see the job history / logs / return data, just trying to avoid the args
trying to trigger a flow via email but can not connect with smtp because certificate validation fails. windmill is self-hosted on k8s. how do I pass my certificate to it?
Hey Guys, I'm having a little trouble with iterators and viewing progress in the UI. I usually process batches of 100 items and when starting a workflow. It currently agressively limits what information can be shown (showing 20 of 100 items, click to load more). And it doesn't show the first or last item that is currently being processed in the UI. In an ideal scenario I would like to see the last item that has been fully processed as the currently active item in the iterator in the UI.
I'm running a Windmill app in an iframe and using JWT for authentication. The Job logs component renders job output correctly, however the Flow Status UI component isn't working properly. Job updates aren't propagating—the nodes in the flow are completing but the UI isn't updating accordingly. I'm seeing the following error repeatedly in the console:
Bad request: As a non logged in user, you can only see jobs ran by anonymous users
Bad request: As a non logged in user, you can only see jobs ran by anonymous users
I've configured the app to require user login, so I am confident that the JWT auth is working for everything except the flow status UI component.
Windmill version: v1.554.0
also doesn't work on 1.552.1
I've also confirmed this works on v1.500.1
Looks like it has to do with windmill's migration to sse vs polling for job status. At least that's the main difference I can tell between 1.500.1 and 1.552.1 / 1.554.0
Edit: The errors manifest with the Job logs component too if the job runs for > 1 second (wrote a simple script with a sleep(1) to test).
Im new to doing local dev, but if i do wmill script generate-metadata, it should generate stuff in the yaml file for inputs right? I created a basic bash script with two inputs, and there is nothing about them in the yaml file after running the generate-metadata command. It create the yaml file, but its got no values for the proeprties.