ledgedash / unum Goto Github PK
View Code? Open in Web Editor NEWLicense: Other
License: Other
Having each fan-out initiator create a separate context causes problems for nested fan-outs. It is also unnecessary when the function outputs have unique names that can always identify the writer, particularly in the case of parallel and map fan-outs.
unum-cli: command not found
How can I use this system?
If programmers write unum IR directly, they need to make sure that the unum-template.yaml
has Start: true
under one of the functions. They can optionally add Start: True
into the same function's unum-config.json
, but it's not required. unum-cli build
will use the unum-template.yaml
file to add a Start: True
to the entry function's unum-config.json
if that's not already present. unum-cli build
also validates that only one of the functions of the workflow has Start: True
in its unum-config.json
. If the programmer added Start: True
to multiple functions, either directly or through unum-template.yaml
, unum-cli build
will fail.
Use unum-template.yaml to add Start: True
if Start: true
exists in unum-template.yaml
Go through all functions to make sure there's one and only one function whose unum-config.json has Start: True
.
Mark the start function in the unum config. The start function needs to create a context in the intermediary data store for each invocation of the workflow.
The unum runtime and backend compiler should support more than just one backend platform. It will help to demonstrate the following:
We should aim to have another managed cloud platform (azure) and an on-premise platform (openfaas) to show that unum works under different environments.
Cases where function should pass UnumMetadata forward:
Full Step Functions Choices support.
Do not execute the user function at all when a non-entry function is triggered first.
This scenario can happen when:
Ill-defined workflow: a workflow is deploy with Start: True
in none of its unum-config.json
and therefore no entry function from the unum runtime's perspective.
Client directly invoke a non-entry function in a well-defined workflow.
Either way, the runtime should check if the input payload already has a Session
field or that the function's unum-config.json
has Start: True
.
The default behavior is if entry function, run it and run the rest of the workflow; if non-entry function, fail immediately.
Add a control field in the input payload that change the behavior:
Adding this feature can enable the following capabilities:
Raising exceptions when the unum runtime encounters an error causes Lambda to retry the function. However, the retry is doomed to fail again and therefore pointless. Instead, unum should record runtime errors in the unum data store.
For example, on s3, write runtime errors in session_context/errors/
.
$0: my index
$1: my parent's index (the first OuterLoop
)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.