Vitaly Bogdanov
Vitaly Bogdanov
Expected behavior: `snet-cli` fails when `--group-name` is omitted in `metadata-init` command. Actual behavior: `snet-cli` creates service_metadata.json without payment address: ``` $ snet service metadata-init service_spec example-executable-service --endpoints http://54.203.198.53:7018 --fixed-price 0...
``` # snet organization print-metadata snet error: the following arguments are required: org_id usage: snet organization print-metadata [-h] org_name org_id positional arguments: org_name Organization name org_id Organization Id optional arguments:...
Steps to reproduce: - prepare service metadata without calling `snet metadata-init`, for example print metadata of already published service into `service_metadata.json` and change "model_ipfs_hash" in it. - publish new service...
Example: ``` # snet organization info snet Organization Name: - b'ipfs://QmW2ohpkDzEAiuGiVY6gDhCq4WLWGtowvwezqnmvJd84aD\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' Organization Id: - snet Owner: - 0x592E3C0f3B038A0D673F19a18a773F993d4b2610 Services: - example-service ```
See https://github.com/singnet/snet-daemon/issues/144 for details
After PR https://github.com/singnet/platform-contracts/pull/33 and PR https://github.com/singnet/snet-cli/pull/64 there is no AlphaRegistryContract in latest platform-contract binaries. AlphaRegistry usages should also be removed from dApp code.
In order to parse question2atomeese.sh results automatically by pandas header with fields format should be added to the file manually. This is to add this header automatically and ignore it...
Very similar to #27. I am opening it to ask for help in understanding what exactly doesn't work here. I have a project with the following structure: - Rust library...
This issue started happening frequently on sound-spleeter service instance. It happens about two times per week. In client logs one can see that client first receives "cannot get mutex for...