cargill / splinter Goto Github PK

Getting this error while trying to run cargo build in the root directory
Installed rustc nightly 1.49.0.still same issue

network-endpoint and advertised-endpoint exists. But the docker-compose file has invalid options.

Brain dump for what contributing could look like

root@79aed5d1044a:# scabbard exec --contract $CONTRACT:$VERSION --inputs $NAMESPACE --outputs $NAMESPACE --key $KEY --url $URL --payload $PAYLOADFILE --service-id $CIRCUIT::$SERVICE

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
Aborted

I do not see abnormal behavior in Splinter logs. This is happening in every run, I have a script to reproduce it always. Code is proprietary, any guidance on debugging this issue?

--node-id is a mandatory parameter for 0.3.16 tagged image. It shall be set in the default compose files (both docker-compose and docker-compose-dockerhub).

Release notes page in Splinter Docs advertises v0.4 is released but RELEASE_NOTES.md in master in Splinter repo is 0.3.18

https://splinter.dev/releases/0.4/ links to https://github.com/Cargill/splinter/blob/master/RELEASE_NOTES.md

This PR looks like it includes the content just doesn't target master #933

I can submit a PR to update one of the sections so the docs and the repo are aligned.

The error_data is always empty [] when using the scabbard exec command. One has to peep into the Splinter daemon logs to know what is printed by the smart contract. The log captured by this client is from the [consensus::consensus::two_phase] when looked into the Splinter daemon logs.

Steps:

pwd
# /c/Users/rossth/git/github.com/Cargill/splinter
git fetch origin
git checkout v0.3.17
docker-compose -f examples/gameroom/docker-compose.yaml up -d
docker logs -f splinterd-node-acme

Output:

psql: could not connect to server: Connection refused
        Is the server running on host "splinterd-db-acme" (23.217.138.110) and accepting
        TCP/IP connections on port 5432?
could not connect to server: Connection refused
        Is the server running on host "splinterd-db-acme" (23.202.231.169) and accepting
        TCP/IP connections on port 5432?
Database is unavailable - sleeping
Successfully applied biome credentials migrations
Writing file: /etc/splinter/certs/generated_ca.pem
Writing file: /etc/splinter/certs/private/generated_ca.key
Writing file: /etc/splinter/certs/client.crt
Writing file: /etc/splinter/certs/private/client.key
Writing file: /etc/splinter/certs/server.crt
Writing file: /etc/splinter/certs/private/server.key
error: Found argument '--rest-api-endpoint' which wasn't expected, or isn't valid in this context

USAGE:
    splinterd --advertised-endpoints <advertised_endpoints>... --config <config> --database <database> --network-endpoints <network_endpoints>... --service-endpoint <service_endpoint> --verbose

For more information try --help

This error does not come for gameroom although the section is missing from database cargo.toml

tried to replicate the basic functionality of gameroom.
getting this error
cargo-deb: cargo (metadata): error: failed to parse manifest at /build/examples/supplychain/database/Cargo.toml

Caused by:
no targets specified in the manifest
either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present

ERROR: Service 'scabbard-cli' failed to build: The command '/bin/sh -c cargo deb --deb-version $REPO_VERSION $CARGO_ARGS' returned a non-zero code: 1

I have provided the cargo.toml for all cli, daemon and database in cli and scabbard of splinter. Still getting this error.

Can someone help me out in regard to this?

get dcobot configured on this repo

The feature defined in the src is exec, however it is referenced as execute in the Cargo.toml file as pointed out in the link.

Some actions, like circuit create will default to the typical bind url, http://127.0.0.1:8085, while others like the one referenced above default to the url http://127.0.0.1:8080.