Summary

I expect CLI docs to tell end user differences between argo terminate and argo stop intentions and its expected behavior. I found none.

Diagnostics

What Kubernetes provider are you using?
AWS
What version of Argo Workflows are you running?
2.16

**Message from the

Description

In some places we use uint64 for balance, in other places we use big.Int. Let's standardize all of these into a single type, uint64.

This issue appears in commit hash: e353ccc393eda807411ef001015b2d3e8dabf4fb

See also #2069

We should modify the code in dffml/cli/dataflow.py within the Diagram class to not show operation.inputs which have default values. It makes for giant diagrams sometimes. We should provide an option to show them again

Ideally, we'd take a page from the https://github.com/multiformats/js-multiformats book and support cjs, esm, etc builds via rollup and friends to support multiple platforms/use-cases. Since this is designed to be a light-weight alternative to other ipds-based libraries, it should have a really low barrier to usage out of the box. In fact, moving forward, this should be a pretty critical require