workflow | 易学教程

Launch a subdag with variable parallel tasks in airflow

阅读更多关于 Launch a subdag with variable parallel tasks in airflow

问题 I have an airflow workflow that I'd like to modify (see illustration at the bottom). However, I couldn't find a way to do that in the docs. I've looked at subdags, branching and xcoms without luck. There doesn't seem to be a way to specify how many tasks should run in parallel in a subdag based on a return from an operator. To add to the problem, each task in the subdag receives a different parameter (an element from the list returned by the previous operator) This is an illustration of what

Contributing using git

阅读更多关于 Contributing using git

So I have cloned a project at github and fixed a patch. Since this is the first time Im working in git Im trying to figure out the best way to put it online. Upon checking out my own (cloned) repository on github there was only one branch: master . I created a branch, myfix , which now holds one commit, which is the fix for the bug. Should I now push everything to my cloned project on github? I assume that this would create the branch myfix on my github project containing that single fix commit. Should I merge myfix into the master branch, remove myfix and then push everything? When searching

SharePoint list item permissions

阅读更多关于 SharePoint list item permissions

问题 I want to programmatically make it so that users can see only particuar items on the list. Basically in an workflow that runs when an item is created I'm going to do some stuff and notify some people about this item. I also want it to change the permissions on the item so that only particular users (looked up on runtime based on the items contents) can read the item. The rest of the users that have access to the list will only see particular items but not all of them. The list item might not

viewflow.io: implementing a queue task

阅读更多关于 viewflow.io: implementing a queue task

问题 I would like to implement the following use case with the ViewFlow library: Problem Processes of a particular Flow, started by a user, must wait in a queue before executing a celery job. Each user has a queue of these processes. Based on a schedule, or triggered manually, the next process in the queue is allowed to proceed. Example A node within my flow enters a named queue. Other logic within the application determines, for each queue, when to allow the next task to proceed. The next task in

WorkFlow Unit Testing

阅读更多关于 WorkFlow Unit Testing

问题 How to unit test the windows workflows? 回答1: K. Scott Allen has posted this, which provides an approach to unit testing custom activities (although he says that he is not satisfied). A similar approach is presented by Ron Jacobs here and here. Another approach is presented by Maurice here and here (he uses TypeMock as Will already mentioned). 回答2: Microsoft.Activities.UnitTesting. A library of helper classes and activities designed to make unit testing of workflows easier. Looks like there's

在Serverless Kubernetes集群中轻松运行Argo Workflow

阅读更多关于在Serverless Kubernetes集群中轻松运行Argo Workflow

导读 Argo是一个基于kubernetes实现的一个Workflow(工作流)开源工具，基于kubernetes的调度能力实现了工作流的控制和任务的运行。目前阿里云容器服务ACK集群中已经支持工作流的部署和调度，这里我们介绍如果在ASK(Serverless Kubernetes)集群中使用Argo，无需预留节点资源池，即可灵活动态的运行工作流任务，并最大化节省用户的计算成本。前置条件：创建ASK集群 https://cs.console.aliyun.com/#/k8s/cluster/create/serverless 因为argo创建的pod往往需要大规格cpu和mem资源，因此建议创建多可用区ASK集群，当一个可用区库存不足时，后台会在其他可用区尝试创建pod，以缓解单可用区库存不足的情况。下载ags命令行，可参考 https://help.aliyun.com/document_detail/121342.html 部署argo workflow controller # ags install # kubectl -n argo get pod NAME READY STATUS RESTARTS AGE argo-ui-5c5dbd7d75-hxqfd 1/1 Running 0 60s workflow-controller-848cf55b64

Rehosted Microsoft Workflow Designer UI

阅读更多关于 Rehosted Microsoft Workflow Designer UI

I have recently created a rehosted Workflow Designer application and noticed that the UI looks outdated when compared with how it looks in Visual Studio. Does anyone know which could be the problem? No matter what version of .NET I'm using (for example 4.6 or 4.7), the UI still doesn't update. I have also followed the next article to enable Workflow 4.5 features, but without any success on the UI side. (WF4.5) Enabling new .Net framework 4.5 features in your rehosted designer application https://blogs.msdn.microsoft.com/tilovell/2012/06/04/wf4-5-enabling-new-net-framework-4-5-features-in-your

git-svn and a remote git repo sync

阅读更多关于 git-svn and a remote git repo sync

问题 At my workplace we use SVN for version control. I switched to git-svn when I found out about it, and recently I decided to sync some of my private branches to another remote git repo. The workflow, then, consists of rebasing from and pushing to the SVN repo via git-svn, while working on separate private feature branches that are pushed to the remote git repo so I can work on them at home if necessary. Now, every time I rebase from git-svn, my remote git repo asks to be pulled first. Sometimes

Please confirm: Is Windows Workflow Foundation a good horse to be backing right now?

阅读更多关于 Please confirm: Is Windows Workflow Foundation a good horse to be backing right now?

问题 We are in the process of selecting a workflow solution for a company that uses Microsoft products end to end. Given the news on WF4, in that it seems to be essentially a rewrite of previous versions, is it a wise move to back the current version or should we be looking elsewhere? Ie - is the current version so bad that we would not be wise to try and use it? 回答1: Haiving just launched a project which .NET 3.5 and workflow I'd say that the current release of WF is good enough to use and run

How do I fix a bug in a previous release version via mercurial?

阅读更多关于 How do I fix a bug in a previous release version via mercurial?

We are using mercurial in a single repository. We have a master branch and a develop branch (as well as feature branches, but they aren't germane to the issue at hand). We tag the master branch with releases (5.1.0.102, etc). We do our development on develop . But now we want to fix a bug in a previous version. There are a lot of questions here on SO about this issue, but none of them seem to explain what I want to do. What I want to do is this: Update to the point where we released (say 6.1.1) Fix a number of bugs in that release Label that resulting code state as (6.1.2) Do a build of this