Bot releases are visible (Hide)
Published by samuell almost 7 years ago
Published by samuell about 7 years ago
This release adds two big improments:
The audit log feature will now include upstream audit info from tasks that are already finished when running the workflow, by reading in their (existing) audit log files. The field names have also been made shorter and more succinct.
Ports now support connecting multiple upstream ports to in-ports. This makes it much easier to create components for various merge and reduce operations, among other things. Note though that it will require to go-run port.RunMergeInputs() on all input ports, which contains code that will merge from multiple inputs into the ports InChan
channel, which can still be used to do range operations on, for simplicity.
Published by samuell about 7 years ago
This release contains two major new API changes:
NewWorkflow()
now takes a number telling the max number of tasks to run concurrently, so that your computer's CPU is not overbooked. So, now you might want to do e.g. NewWorkflow("some_wf", 4)
, on a computer with 4 CPU cores.
The NewProc()
command, and constructor methods for most tasks now take the workflow as its first parameter (this is not the case if using the workflow.NewProc()
version, which does this automatically anyway).
This is to resolve a very commonly occuring and annoying issue that one too easily forgets to add a component to a workflow, which there is no warning for either (checking this is quite hard to implement without resorting to global variables).
Finally, some bugs were resolved in how ports are connected, especially in some of the components in the components lib, which were not properly updated to use the new multi-send ports, and thus were closing the ports in the wrong way. So, now you can connect one out-port to multiple downstream in-ports without bugs and quirks.
Published by samuell about 7 years ago
This is a first release to start tracking changes using semantically versioned releases, for better clarity.
The current status is that the API seems to be stabilizing, but there might still be breaking changes as we put scipipe into production in the coming week.s