2 pieces of changelog today **AgGrid Infinite Table** New AgGrid component to display an Ag Grid t

2 pieces of changelog today

AgGrid Infinite Table

New AgGrid component to display an Ag Grid table with infinite scrolling and rows display, and a search function

Changelog: https://www.windmill.dev/changelog/aggrid-infinite-table
Docs: https://www.windmill.dev/docs/apps/app_configuration_settings/aggrid_table#aggrid-infinite-table

henri-cOP•4/26/24, 12:21 PM

Jobs Labels

Labels allow to add static or dynamic tags to jobs with property "wm_labels" followed by an array of strings (one or several labels). You can then filter jobs on labels from Runs menu.

Changelog: https://www.windmill.dev/changelog/jobs-labels
Docs: https://www.windmill.dev/docs/core_concepts/monitor_past_and_future_runs#jobs-labels

rubenf•4/28/24, 3:01 PM

Latest CLI and Git Sync have 2 major improvements:
1. Wherever there is a lockfile (in scripts, flows and apps), the lockfile is now stored in a separate file (<same_path_as_script_or_inline_script>.lock) and referenced in the yaml by !inline <path of lock>!inline <path of lock>. We had numerous feedback from EE customers that the lockfile were hard to diff and added lots of boilerplate to otherwise clean yaml files
2. Script in apps (even frontend scripts) are now stored in separate files, similarly than what is the case for flows. Which mean now apps are their own folders:
myapp.yaml -> myapp.app/app.yaml + myapp.app/inline_script1.ts + myapp.app/inline_script1.lock + ....myapp.yaml -> myapp.app/app.yaml + myapp.app/inline_script1.ts + myapp.app/inline_script1.lock + ....

This will improve greatly the ability to use commits/PR to review scripts, flows and apps changes

To do a clean update:
update your CLI to latest
do a wmill sync pull and push to your repo
update the CLI used to 1.320.3 in your github actions
Update your git sync script (we've made that easier, just click button and save git settings, as in picture)

rubenf•5/10/24, 9:01 PM

We are releasing in early Beta a way to deploy typescript scripts with any local relative imports as bundles (similar to what lambda/cloud function does) so that it works with complex local codebases, and any imports or setup without having to publish private packages. It will be an enterprise feature at least at first as it require the instance-wide s3 integration which is where the bundle resides. It works with the vscode extension and you can find some succint documentation here: https://www.windmill.dev/docs/core_concepts/codebases_and_bundles Ping us if you have interest of being part of that beta

Codebases & Bundles | Windmill

Codebases is Beta, only work with typescript and is an enterprise feature for the time being

rubenf•5/13/24, 6:38 AM

nativets/REST supports the full wmill api, just use:

import * as wmill from './windmill.ts'

import * as wmill from './windmill.ts'

and use it as you would in Bun/Deno

rubenf•5/13/24, 6:39 AM

Using the wmill.XService directly in the typescript client (e.g: wmill.JobService.listJobs(...)wmill.JobService.listJobs(...)) doesn't require to use setClient prior anymore

rubenf•5/13/24, 6:56 AM

On the latest windmill and docker-compose template, we mount a log volume across every workers and servers. With the new improvements, will allow you to pull the full log even without EE/S3 if the log volume is also mounted on the servers from which you pull from. We still recommend using the S3 log storage on EE as if you're not using docker-compose, doing multi-write on kubernetes is both complex, slow and expensive.

rubenf•5/20/24, 9:35 PM

bun is now the default language on CLI and vscode. Expect some small diffs on latest using wmill sync pullwmill sync pull as a consequence. It's an annoying but necessary last migration.

rubenf•5/20/24, 9:38 PM

with the latest batch of memory usage improvements, workers and servers use less memory than ever. A worker (outside of the job) on the cloud take 22MB RSS and our very busy servers sits at 155MB RSS.

rubenf•5/23/24, 5:26 PM

Retries are now easier to understand in the flow status viewer:
You can see their numbers as well as the detail of the failed jobs at a glance

wendrul•5/27/24, 9:35 AM

New observability features:

You can now see a new graph on the runs page showing the concurrent jobs over time, showing exactly when jobs started and ended.
This will be particularly useful when combined to the also new filter on concurrency keys, to understand concurrency limits better.
https://www.windmill.dev/changelog/concurrency-limit-observability

Concurrency Limit Observability

Obversability around concurrent jobs has been improved from the Runs menu.

Hugo•5/29/24, 3:58 PM

New Feature: PHP Support

We are excited to announce that, after many requests, PHP is now supported on Windmill as a primary language! Just like with TypeScript and Python, you can use resource types as parameters. For package management, simply specify the packages you need in comments, and they will be automatically installed and loaded using Composer.

Changelog: https://www.windmill.dev/changelog/concurrency-limit-observability
Docs: https://www.windmill.dev/docs/getting_started/scripts_quickstart/php

rubenf•6/4/24, 1:12 PM

many nits in one:
- You can now see the full flow/script definition of a job even if it is scheduled in the future (before it would only display when it would be executed)
- The flow status viewer now can show the step definition and not just the step status
- The flow status viewer now take the whole width on the run page detail of a job
- We now display the lockfile in the step detail

wendrul•6/4/24, 4:34 PM

More observability:

We've made some changes to the runs page:
- There is now a warning on jobs that had to wait some time for an executor before starting.
- You can hover the warning to get details about the time spent waiting.

rubenf•6/5/24, 3:56 PM

Git sync commits are now prefixed with [WM]
The windmill-sync-example repo has been updated https://github.com/windmill-labs/windmill-sync-example/blob/main/.github/workflows/push-on-merge-staging.yaml#L28-L38 to solve an issue that could arise when doing quick successive deployments if you had bi-directional sync on. It will now not trigger a push in the other direction if the commit come from Windmill (as detected by the presence of [WM]) avoiding out-of-sync overwrite errors.

GitHub

windmill-sync-example/.github/workflows/push-on-merge-staging.yaml ...

Contribute to windmill-labs/windmill-sync-example development by creating an account on GitHub.

rubenf•6/10/24, 11:36 AM

Tracking relative imports to avoid dependency hell:
- Windmill automatically track relative imports in bun and python such that if you update a common dependency and update its imports, it will now re-trigger deployment and lockfile computation of all the scripts that depend on it (it was working for python but not bun before)
- Windmill can now also track such imports in inline scripts of flows and will surgically update the inline lockfiles of those flows if the relative imports change

rubenf•6/10/24, 11:36 AM

When doing wmill sync pull, the wmill-lock.yaml will now automatically be updated, avoiding re-triggering lockfile computation for all files, only the ones that have changed from last sync

rubenf•6/10/24, 11:37 AM

Flows inline lockfile can now be updated locally using wmill flow generate-lockswmill flow generate-locks, which is the equivalent of wmill script generate-metadata --lock-onlywmill script generate-metadata --lock-only but for flows' inline scripts

Faton•6/13/24, 8:14 AM

UI Customisation

We've improved the UI customisation panel.
You can now:
- Drag & Drop fields to organise your form
- Add placeholders to fields
- Add custom titles, placeholders and description for nested properties.

You can now preview your customisation directly on the left panel.

rubenf•6/13/24, 8:39 PM

We use a new caching layer for bun and in most cases we will be able to skip the install phase for deployed scripts. Expect to gain between 20ms and up to 200ms for your bun scripts resulting in up to 100% improvements in throughput

Faton•6/21/24, 7:38 AM

We added a small indicator on the flow step to show when at least one required input is missing.

FFaton We added a small indicator on the flow step to show when at least one required i...

Tobseb•6/21/24, 8:59 AM

This is a very useful feature! Thank you!

rubenf•6/21/24, 1:37 PM

on latest, the CLI now supports all features on Windows machines

rubenf•6/26/24, 1:16 PM

we have a new recommended way to browse the typescript windmill SDK: https://app.windmill.dev/tsdocs/modules.html, search works great there

rubenf•6/28/24, 2:14 PM

we migrated the cloud to ARM instances, you shouldn't see any changes but let us know if you do

Rrubenf we migrated the cloud to ARM instances, you shouldn't see any changes but let us...

StarDrifter•6/28/24, 9:03 PM

Congrats on the big change, are you seeing performance improvements? or was it mostly a cost thing?

SStarDrifter Congrats on the big change, are you seeing performance improvements? or was it m...

mrl5•6/29/24, 10:30 AM

I'm super curious as well

and congrats on succesfull migration

rubenf•6/29/24, 12:33 PM

3 reasons:
- cost
- performance
- aligning with what we recommend our own customers to do

rubenf•6/29/24, 12:36 PM

One thing we weren't able to do was to make nsjail work with the bottlerocket images and for some reasons we had DNS issues with al2023 so we're still on al2 for the cloud but we migrated our dedicated instances to bottlerocket and can thus also enjoy groupv2 which has a better oom killer wrt to filesystem kernel cache

rubenf•7/2/24, 7:38 PM

The args in the runs page are now directly synced with the url fragment/anchor, meaning you get sharable urls with pre-filled args automatically by just sharing your current URL. e.g:

https://app.windmill.dev/scripts/get/dae90ddc108ce257?workspace=windmill-labs#disable_automatic_renewal=false&send_invoice_directly=true&discount_duration=%221+year%22&discount=0&frequency=%22monthly%22&seats=1&vcpus=2&plan=%22selfhosted_ee%22&stripe_customer_data=%7B%22label%22%3A%22New+stripe+customer%22%2C%22email%22%3A%22%22%2C%22address%22%3A%7B%22line1%22%3A%22%22%2C%22postal_code%22%3A%22adsadas%22%2C%22state%22%3A%22%22%2C%22city%22%3A%22%22%7D%2C%22tax_info%22%3A%7B%22value%22%3A%22%22%7D%7D&is_quote=false&contact_email=%22bar%40acme%22&company_name=%22acme%22

https://app.windmill.dev/scripts/get/dae90ddc108ce257?workspace=windmill-labs#disable_automatic_renewal=false&send_invoice_directly=true&discount_duration=%221+year%22&discount=0&frequency=%22monthly%22&seats=1&vcpus=2&plan=%22selfhosted_ee%22&stripe_customer_data=%7B%22label%22%3A%22New+stripe+customer%22%2C%22email%22%3A%22%22%2C%22address%22%3A%7B%22line1%22%3A%22%22%2C%22postal_code%22%3A%22adsadas%22%2C%22state%22%3A%22%22%2C%22city%22%3A%22%22%7D%2C%22tax_info%22%3A%7B%22value%22%3A%22%22%7D%7D&is_quote=false&contact_email=%22bar%40acme%22&company_name=%22acme%22

It also works well with back/forward and browser history.
We also improved the whole way we dealt with the browser history and back/forward should work better in more places. We also did some nits such that editing a script from a run detail page will now prefill the test args with the jobs args

henri-cOP•7/4/24, 2:22 PM

We have a new type of input: oneOf, that displays an option between multiple objects.

They can be used in TypeScripts, flows and any UI-built schema.

Changelog: https://www.windmill.dev/changelog/oneof-inputs
Docs: https://www.windmill.dev/docs/core_concepts/json_schema_and_parsing#oneof

henri-cOP•7/4/24, 2:30 PM

example of oneOf input in flows

henri-cOP•7/10/24, 3:00 PM

We have a new component on the App Editor: Navbar

It facilitates control over an app by changing its ctx.query, enabling:
- Changing the behavior of the app by manipulating the query arguments and hash of the URL.
- Opening an external URL in a new tab.
- Opening another Windmill app, which allows for creating embedded apps where the user navigates between several of your Windmill apps.

Changelog: https://www.windmill.dev/changelog/navbar
Docs: https://www.windmill.dev/docs/apps/app_configuration_settings/navbar

rubenf•7/14/24, 7:54 AM

Flow status viewer change:
- improved dark mode theme
- you can now pick the iteration to view from directly in the graph
- for branchall, branchone, while loop and forloops, the status of the branch/iteration is now displayed in the top node. For instance, for branchone, it will also allow you to know which branch was picked
- now the colors of the forloop itself corresponds to the entire forloop status and not the iteration. The iteration status is in the "Do one iteration" block
- You can pick the iteration to view the detail of directly in the forloop
- The forloop detail page now list every iteration status, even if you have a thousand one without having to load them all
- The nodes such as forloop and branchall that collect multiple results now show separately the collection of the results of all subflows and the result of the selected branch/iteration

henri-cOP•7/26/24, 2:40 PM

Flows now have versions just like scripts and apps.

We have also introduced:
- Redeploy of Scripts, Flows, Apps from past version.
- Fork Scripts, Flows, Apps from past version.
- Add deployment messages for Scripts and Flows.

Changelog: https://www.windmill.dev/changelog/flow-versioning

deployment_history-bcdb65e32cdebce3b2c877596d588243.png

Capture_decran_2024-07-26_a_16.40.11.png

rubenf•7/26/24, 7:54 PM

Windmill now pre-bundle Typescript (Bun) scripts and cache them on S3 and locally at deployment time. Furthermore, if a bun script is ran while not being pre-bundled, it will be re-bundled.This will improve cold start time and memory usage of all bun scripts, in particular for scripts with many/heavy imports and relative imports. We also did improvements for non-deployed scripts using better caching strategies for the dependency cache. You cannot do any faster than running a pre-bundled script aside from having the script being already running which is what dedicated workers are made for. This makes windmill the fastest platform to run typescript. We have improvements in the work to improve the DX and versatility of dedicated workers as well coming soon.

henri-cOP•7/29/24, 11:00 AM

We have a new helper function within scripts: DynSelect_DynSelect_

Dynamic Select helps you to create a select field with dynamic options:
- Options within the select field can dynamically change based on input arguments.
- Support for TypeScript and Python.
- Conditional logic within the function to filer and sort select options based on specified conditions.

Changelog: https://www.windmill.dev/changelog/dynamic-select

Dynamic Select

Dynamic Select is an helper function within scripts that allows you to create a select field with dynamic options.

rubenf•7/31/24, 9:15 AM

We've made our runtime that we've called "REST" and "nativets" supports npm packages and relative imports! There is now no difference in the syntax of typescript/bun scripts and native scripts. Native scripts still only support a subset of what node support (just the fetch operation) but many npm packages can still be used because that's all they use under the hood (for instance, windmill-client and axios).
How to activate ? Just add //native//native to the head of your script. Windmill will automatically convert between 'nativets' and 'bun' scripts based on the presence of this header so you can always just pick Typescript (bun) and decide at the end if you want to accelerate it with 'native' if possible.

We've also changed the default docker-compose/helm template to go from 4 small native workers with each 1 subworker to 1 bigger native worker with 8 subworkers as it performed better in our benchmarks. If you need more throughput, simply increase the replicas of the native workers, don't increase the number of subworkers past 8 as the interleaving will result in lower throughput.

This is a huge improvement as you can now make our nativenative runtime an implementation details and we can unify everything under the standard "Typescript" language without anything windmill specific. Legacy native/fetch scripts will still work but the new REST button now simply prefill a bun script with a //native//native header.

nativenative runtime is great for scripts that are doing simple fetch and require little compute but are io-bound on the response from the api. You can get parallelization of 8 requests/scripts at a time with a single worker, resulting in 8x better throughput between bun and native scripts at scale.

rubenf•8/14/24, 8:07 AM

We fixed one of the most annoying bug of the frontend code editor of apps, types are no more overly narrowed to their literal types which mean you do not get erroneous squiggly error anymore for comparison and assignments, before vs after:

rubenf•8/14/24, 8:12 AM

container group fields are now mutable internally, so you can start building reusable component groups with more stateful inner logics

rubenf•8/14/24, 3:32 PM

New options for approval/suspend steps: Continue on disapproval/timeouts

Instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a branchone right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an errorerror field which you can use to distinguish between approvals and disapproval/timeouts

rubenf•8/14/24, 4:45 PM

New option for flow error handlers: recover the flow if recover: truerecover: true is returned as part of the error handler result, also we standardized step_id to be in the default template

rubenf•8/26/24, 8:34 PM

We added a vim mode to the code editors

henri-cOP•8/29/24, 10:48 AM

On the app editor, you can now hide left, right and botom panels with special button or shortcuts

https://www.windmill.dev/changelog/hide-show-app-panels

Hide / Show App Editor Panels

Hide panels on App Editor with buttons and shortcuts.

Hugo•8/30/24, 8:31 AM

Scripts and flows can now be triggered by the delivery of an email!
We'll be showing more today at 6 p.m. CET in our first weekly demo.

https://www.windmill.dev/changelog/email-triggers
https://www.windmill.dev/docs/advanced/email_triggers

Hugo•8/30/24, 8:37 AM

rubenf•9/1/24, 6:51 AM

Major: See service logs directly in windmill:
See the logs of any workers or any servers in the service logs of the search modal. Log count is seen in the mini-graph and error count is in red

rubenf•9/2/24, 1:18 PM

you can now edit directly the yaml of flows within the flow editor

rubenf•9/9/24, 12:45 PM

Major: windmill CLI (wmill) installable with npm and nodeJs compatible

We've made the CLI more accessible by being directly installable from npm: npm install -g windmill-clinpm install -g windmill-cli. It is now the recommended setup but the deno way will continue to work for the foreseable future. We updated the git sync examples as well: https://github.com/windmill-labs/windmill-sync-example/blob/main/.github/workflows/push-on-merge.yaml

There are no changes, the command is still wmill, and you will still be able to upgrade it with wmill upgradewmill upgrade (but require to deno uninstall wmill && npm install -g windmill-clideno uninstall wmill && npm install -g windmill-cli first)

One focus of this quarter is to improve the on-boarding experience and reduce the steep curve to learn windmill.

GitHub

windmill-sync-example/.github/workflows/push-on-merge.yaml at main ...

Contribute to windmill-labs/windmill-sync-example development by creating an account on GitHub.

rubenf•9/10/24, 6:32 PM

you can now easily change the id of steps in flows and it will modify every step inputs that depend on it automatically

Similar Threads

Similar Threads

Similar Threads