anyone can share their experience with sftp on windmill other than going python/bash route? looks li
anyone can share their experience with sftp on windmill other than going python/bash route? looks like bun doesn't support the big sftp libraries
TI do not have such experience, but I'm curious: why not use Python?
PI've moved a windmill instance from one cloud to another, all good, after setting up the roles correctly all is humming along, even logged me in with my existing token, yay, I see everything.
But, none of the users see anything anymore, all the permisisons and groups seems to be there, any ideas why this could be?
But, none of the users see anything anymore, all the permisisons and groups seems to be there, any ideas why this could be?
Rnot using the same usernames ?
Peverything is exactly the same, users, passwords, I dumped the other pg and restored it into the new postgres
PAlso for me everything works fine 
it's just that none of the scripts/flows/apps are visible to users, not even if I create a new app and share that, wonder what I missed
it's just that none of the scripts/flows/apps are visible to users, not even if I create a new app and share that, wonder what I missed
Zno reason, rest of the flow is in js so wanted to keep consistent. ended up just using python after deno/bunjs were a bust
Zalthough, running locally for deno seems to work, it might just be a out-of-date deno on windmill
(local 1.45.1 = no go, local 1.46.1 = go)
(local 1.45.1 = no go, local 1.46.1 = go)
Zah yeah, definitely outdated deno, current deno on wm is 1.45.4
deno 1.46 has this little tidbit:
deno 1.46 has this little tidbit:
R@Antonio Moura you're probably using supabase with a pooler in a mode that is incompatible with windmill
Rskip the pooler and connect directly to it
TOn https://www.windmill.dev/pricing in "Cloud" it says for "Enterprise" both: Audit logs for 60 days and Audit logs unlimited. What is correct?
RAudit logs unlimited
TNice, thank you!
NIs it possible to create Multiple slash slack commands from different workspaces
Where users from different workspaces can create their own Automation/Script/flow to invoke ?
Where users from different workspaces can create their own Automation/Script/flow to invoke ?
TIs my assumption correct, that this commit is related to the issue, that we currently cannot see logs of a selected node in the flows run view? 
https://github.com/windmill-labs/windmill/commit/80189671817f4287da8108f91579d2a006c24083
If yes then we would appreciate a speedy release. 
https://github.com/windmill-labs/windmill/commit/80189671817f4287da8108f91579d2a006c24083
TWait, wrong commit - this is already released.
I ment that one: https://github.com/windmill-labs/windmill/commit/5c82f815ae4c3bf07b7842354c0717fd33ec2f14
Being related to the issue that we currently cannot filter for script paths - we only see deployments somehow?
I ment that one: https://github.com/windmill-labs/windmill/commit/5c82f815ae4c3bf07b7842354c0717fd33ec2f14
Being related to the issue that we currently cannot filter for script paths - we only see deployments somehow?
THmm, only seems like reformatting. :/ Nvm
R@Tobseb what do you mean by:
Being related to the issue that we currently cannot filter for script paths - we only see deployments somehow?
TWell, for whatever reason we only see runs in the flows/script view "Previous runs", but when we filter for exactly the path of the script/flow in the Runs view then we do not see the actual runs, but only deployments of the script/flow.
THowever I did not manage to reproduce it on https://app.windmill.dev/ so not sure what this is caused by. :/
Rwhat version are you on ?
Trn EE v1.385.0
RI don't think there is any issue with 1.385.0 of this nature but could you potentially update?
TYes, will advise to do so. Thank you!
Mhi, is there any progress with that? based on https://www.windmill.dev/docs/core_concepts/worker_groups
to my understanding currently it's not possible to run workers inside aws lambda or cloudflare workers?
Windmill's responsibility is not to spawn the worker itself but to play well with existing service orchestrator such as Kubernetes, ECS, Nomad or Docker Compose, and any IaC.
to my understanding currently it's not possible to run workers inside aws lambda or cloudflare workers?
RCurrently not and it wouldn't be workers but we could indeed have an sdk for python and typescript to be able to complete a job externally. The main issue with it is DX
RPoor man's solution, use a native script to poll a lambda/cf worker
Rthe hard part is making the DX of deployment work well, the sdk itself is easy
RIt's still in our backlog but more priority is to make dedicated workers so flexible and easy that you don't need lambda/cf workers anymore
Rsince they have somewhat superior performance to lambda (cf worker is another story) but right now they lack the ability to run an entire workspace worth of scripts
Rand the whole point of windmill is to run everything on your infra
Mthanks for detailed answer - it makes sense. The usecase that I had in mind was to somehow use windmill as a queue/orchestrator that is able offload worker job to some external service like aws lambda or cf worker
RYes I get it, and it's a vlaid use-case but we think that for the majority of our customers, if dedicated workers was better, they would be better off using dedicated workers directly
Rso we will do it eventually once we're happy with what we offer as what we believe should be the primary way
R(but if someone want to OSS contribute the full implementation to windmill, feel free ;))
Zany chance of a recap of what was discussed in the weekly-demo?
R@humanz demo of service logs, email triggers, refactor of early stop for forloop, while loop, added rust as runtime, some AI work to generate hub scripts