fix: CLI fetch inputs

[dprats]

this PR addresses issue with CLI fetching inputs from orchestrator

[github-actions]

Visit the preview URL for this PR (updated for commit 9ad9641):

https://nexus-cli--pr1397-dprats-orchestrator-psottojh.web.app

_{(expires Thu, 27 Feb 2025 19:46:53 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 815ec4c632754f56eccfacfc0919559f5a85a0f1}

[monstertrakk]

Do you debug the CLI before making edits to the code on github?

[dprats]

Do you debug the CLI before making edits to the code on github?

Good question, thank you for asking @monstertrakk. Yes, we test as one would expect (local, across multiple machine/environments). Of course bugs do sneak in...

However, I think the higher level truth is that the bulk of the issues last 48 hours have been with unexpected demand. But team has made significant improvements here through sleepless nights.

I do appreciate the attention on this repo as the open source "face of the network", and unfortunately this client has had to adapt to these. But we do believe they are more stable now.

[ralymov]

Even with this commit - it returns either Invalid proof or buffer underflow (and this by the way is taken as successful sending of the proof, which I doubt).

Are you testing on some other orchestrator URL other than beta?

[monstertrakk]

Do you debug the CLI before making edits to the code on github?

Good question, thank you for asking @monstertrakk. Yes, we test as one would expect (local, across multiple machine/environments). Of course bugs do sneak in...

However, I think the higher level truth is that the bulk of the issues last 48 hours have been with unexpected demand. But team has made significant improvements here through sleepless nights.

I do appreciate the attention on this repo as the open source "face of the network", and unfortunately this client has had to adapt to these. But we do believe they are more stable now.

Update the release so everyone can update if your fix really helps. The command “curl https://cli.nexus.xyz/ | sh” does not put your fix into prover.rs

[monstertrakk]

@dprats
Your fix was manually entered into the .rs files, but that did not work.

root@vmi2408477:~/.nexus/network-api/clients/cli# cargo run --release -- --start --beta
Compiling nexus-network v0.5.3 (/root/.nexus/network-api/clients/cli)
Finished release profile [optimized] target(s) in 2m 40s
Running target/release/nexus-network --start --beta
error: unexpected argument '--start' found

Usage: nexus-network

For more information, try '--help'.

[evaleries]

@dprats Your fix was manually entered into the .rs files, but that did not work.

root@vmi2408477:~/.nexus/network-api/clients/cli# cargo run --release -- --start --beta Compiling nexus-network v0.5.3 (/root/.nexus/network-api/clients/cli) Finished release profile [optimized] target(s) in 2m 40s Running target/release/nexus-network --start --beta error: unexpected argument '--start' found

Usage: nexus-network

For more information, try '--help'.

the latest command should be cargo run --release -- start --env beta

[monstertrakk]

@dprats Will the testnet be extended or will it end on schedule? Please check with the CEO!

[dprats]

Update the release so everyone can update if your fix really helps. The command “curl https://cli.nexus.xyz/ | sh” does not put your fix into prover.rs

yes that is by design. We were still testing things. once i cut the release, it will be live via curl.

[dprats]

Update: This is now merged and part of a new release

[dprats]

Even with this commit - it returns either Invalid proof or buffer underflow (and this by the way is taken as successful sending of the proof, which I doubt).
good catch. that buffer underflow error is not relevant for the attribution of proofs (users still get credit in orchestrator) so that is just noise we removed for now

[monstertrakk]

Update: This is now merged and part of a new release

It's work?