Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

Support base64 encoded files as arguments (fixes linux ulimit issues) #937

Open
TrevorJTClarke opened this issue Feb 15, 2022 · 0 comments
Labels
enhancement New feature or request T-dev-tools

Comments

@TrevorJTClarke
Copy link

TrevorJTClarke commented Feb 15, 2022

Is your feature request related to a problem? Please describe.
On linux, submitting long args list using -base64 flag can actually require more bytes than are allowed by system. It is not possible to sign transactions without a different approach (similar to deploying wasm)

Describe the solution you'd like
See the following line:

This could get upgraded to using a similar file read pattern like when deploying:

const actions = <span class="error">[transactions.deployContract(readFileSync(options.wasmFile))]</span>;

So it could be like:

const base64Args = readFileSync(options.base64File);

Describe alternatives you've considered
I have tried to utilize xargs & change the file limits, however it will not work for larger data. (im storing bytes of a smart contract for doing upgrades via DAOs)

Additional context
You can see some CLI commands we're testing:
near-daos/sputnik-dao-contract#111

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request T-dev-tools
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant