cerc-io/delete-me
10
0
Fork 0
Code Issues 4 Pull Requests 1 Packages Projects Releases Wiki Activity

Status of this CLI / known bugs #17

New Issue
Closed
opened 2023-01-12 23:08:07 +00:00 by zramsay · 7 comments
zramsay commented 2023-01-12 23:08:07 +00:00
Member
Copy Link

Queries by and large work (didn't test them all).

The only write/transaction I was able to make is laconic cns bond create --type aphoton --quantity 1000000000 --gas 200000 --fees 200000aphoton which worked and returned the bondID.

Publishing a record failed with the following error (second last line):

$ ./bin/laconic cns record publish --filename watcher.yml --bond-id c181cc901a0f020162846f77fa66a916bc0c064d0b423af0e2689974acbff3d1 --gas 200000 --fees 200000aphoton

github.com/cosmos/cosmos-sdk/x/auth/tx.DefaultTxDecoder.func1
	github.com/cosmos/cosmos-sdk@v0.46.7/x/auth/tx/decoder.go:42
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).runTx
	github.com/cosmos/cosmos-sdk@v0.46.7/baseapp/baseapp.go:660
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).CheckTx
	github.com/cosmos/cosmos-sdk@v0.46.7/baseapp/abci.go:244
github.com/tendermint/tendermint/abci/client.(*localClient).CheckTxAsync
	github.com/tendermint/tendermint@v0.34.24/abci/client/local_client.go:104
github.com/tendermint/tendermint/proxy.(*appConnMempool).CheckTxAsync
	github.com/tendermint/tendermint@v0.34.24/proxy/app_conn.go:126
github.com/tendermint/tendermint/mempool/v0.(*CListMempool).CheckTx
	github.com/tendermint/tendermint@v0.34.24/mempool/v0/clist_mempool.go:254
github.com/tendermint/tendermint/rpc/core.BroadcastTxCommit
	github.com/tendermint/tendermint@v0.34.24/rpc/core/mempool.go:91
github.com/tendermint/tendermint/rpc/client/local.(*Local).BroadcastTxCommit
	github.com/tendermint/tendermint@v0.34.24/rpc/client/local/local.go:91
github.com/cosmos/cosmos-sdk/client.Context.BroadcastTxCommit
	github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:97
github.com/cosmos/cosmos-sdk/client.Context.BroadcastTx
	github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:32
github.com/cosmos/cosmos-sdk/client.TxServiceBroadcast
	github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:157
github.com/cosmos/cosmos-sdk/client.Context.Invoke
	github.com/cosmos/cosmos-sdk@v0.46.7/client/grpc_query.go:51
github.com/cosmos/cosmos-sdk/types/tx.(*serviceClient).BroadcastTx
	github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.go:855
github.com/cosmos/cosmos-sdk/types/tx.request_Service_BroadcastTx_0
	github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.gw.go:136
github.com/cosmos/cosmos-sdk/types/tx.RegisterServiceHandlerClient.func3
	github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.gw.go:477
github.com/grpc-ecosystem/grpc-gateway/runtime.(*ServeMux).ServeHTTP
	github.com/grpc-ecosystem/grpc-gateway@v1.16.0/runtime/mux.go:240
github.com/gorilla/mux.(*Router).ServeHTTP
	github.com/gorilla/mux@v1.8.0/mux.go:210
github.com/tendermint/tendermint/rpc/jsonrpc/server.maxBytesHandler.ServeHTTP
	github.com/tendermint/tendermint@v0.34.24/rpc/jsonrpc/server/http_server.go:256
github.com/tendermint/tendermint/rpc/jsonrpc/server.RecoverAndLogHandler.func1
	github.com/tendermint/tendermint@v0.34.24/rpc/jsonrpc/server/http_server.go:229
net/http.HandlerFunc.ServeHTTP
	net/http/server.go:2109
net/http.serverHandler.ServeHTTP
	net/http/server.go:2947
net/http.(*conn).serve
	net/http/server.go:1991
unable to resolve type URL /vulcanize.nameservice.v1beta1.MsgSetRecord: tx parse error
laconic cns record publish

We cut a new release of laconic-sdk to include what ideally would've been the fix ie., this commit

and the error went from:

unable to resolve type URL /vulcanize.nameservice.v1beta1.MsgSetRecord: tx parse error

to

unable to resolve type URL : tx parse error

From discussion, it seems to be that a dependency went from using sha384 -> sha256 (or vice-versa?). The laconic-sdk and its tests were updated for that fix, but this CLI was not.

Queries by and large work (didn't test them all). The only write/transaction I was able to make is `laconic cns bond create --type aphoton --quantity 1000000000 --gas 200000 --fees 200000aphoton` which worked and returned the bondID. Publishing a record failed with the following error (second last line): ``` $ ./bin/laconic cns record publish --filename watcher.yml --bond-id c181cc901a0f020162846f77fa66a916bc0c064d0b423af0e2689974acbff3d1 --gas 200000 --fees 200000aphoton github.com/cosmos/cosmos-sdk/x/auth/tx.DefaultTxDecoder.func1 github.com/cosmos/cosmos-sdk@v0.46.7/x/auth/tx/decoder.go:42 github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).runTx github.com/cosmos/cosmos-sdk@v0.46.7/baseapp/baseapp.go:660 github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).CheckTx github.com/cosmos/cosmos-sdk@v0.46.7/baseapp/abci.go:244 github.com/tendermint/tendermint/abci/client.(*localClient).CheckTxAsync github.com/tendermint/tendermint@v0.34.24/abci/client/local_client.go:104 github.com/tendermint/tendermint/proxy.(*appConnMempool).CheckTxAsync github.com/tendermint/tendermint@v0.34.24/proxy/app_conn.go:126 github.com/tendermint/tendermint/mempool/v0.(*CListMempool).CheckTx github.com/tendermint/tendermint@v0.34.24/mempool/v0/clist_mempool.go:254 github.com/tendermint/tendermint/rpc/core.BroadcastTxCommit github.com/tendermint/tendermint@v0.34.24/rpc/core/mempool.go:91 github.com/tendermint/tendermint/rpc/client/local.(*Local).BroadcastTxCommit github.com/tendermint/tendermint@v0.34.24/rpc/client/local/local.go:91 github.com/cosmos/cosmos-sdk/client.Context.BroadcastTxCommit github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:97 github.com/cosmos/cosmos-sdk/client.Context.BroadcastTx github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:32 github.com/cosmos/cosmos-sdk/client.TxServiceBroadcast github.com/cosmos/cosmos-sdk@v0.46.7/client/broadcast.go:157 github.com/cosmos/cosmos-sdk/client.Context.Invoke github.com/cosmos/cosmos-sdk@v0.46.7/client/grpc_query.go:51 github.com/cosmos/cosmos-sdk/types/tx.(*serviceClient).BroadcastTx github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.go:855 github.com/cosmos/cosmos-sdk/types/tx.request_Service_BroadcastTx_0 github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.gw.go:136 github.com/cosmos/cosmos-sdk/types/tx.RegisterServiceHandlerClient.func3 github.com/cosmos/cosmos-sdk@v0.46.7/types/tx/service.pb.gw.go:477 github.com/grpc-ecosystem/grpc-gateway/runtime.(*ServeMux).ServeHTTP github.com/grpc-ecosystem/grpc-gateway@v1.16.0/runtime/mux.go:240 github.com/gorilla/mux.(*Router).ServeHTTP github.com/gorilla/mux@v1.8.0/mux.go:210 github.com/tendermint/tendermint/rpc/jsonrpc/server.maxBytesHandler.ServeHTTP github.com/tendermint/tendermint@v0.34.24/rpc/jsonrpc/server/http_server.go:256 github.com/tendermint/tendermint/rpc/jsonrpc/server.RecoverAndLogHandler.func1 github.com/tendermint/tendermint@v0.34.24/rpc/jsonrpc/server/http_server.go:229 net/http.HandlerFunc.ServeHTTP net/http/server.go:2109 net/http.serverHandler.ServeHTTP net/http/server.go:2947 net/http.(*conn).serve net/http/server.go:1991 unable to resolve type URL /vulcanize.nameservice.v1beta1.MsgSetRecord: tx parse error laconic cns record publish ``` We cut a new release of `laconic-sdk` to include what ideally would've been the fix ie., [this commit](https://github.com/cerc-io/laconic-sdk/commit/eaafeb910763677cd0ea360cd060a4a018cab59c) and the error went from: ``` unable to resolve type URL /vulcanize.nameservice.v1beta1.MsgSetRecord: tx parse error ``` to ``` unable to resolve type URL : tx parse error ``` From discussion, it seems to be that a dependency went from using sha384 -> sha256 (or vice-versa?). The `laconic-sdk` and its tests were updated for that fix, but this CLI was not.
👀 1
0xmuralik commented 2023-01-13 06:31:18 +00:00 (Migrated from github.com)
Author
Member
Copy Link

This might be using the old version of laconic-sdk repo. Fixed them in this PR https://github.com/cerc-io/laconic-sdk/pull/15.

This might be using the old version of laconic-sdk repo. Fixed them in this PR https://github.com/cerc-io/laconic-sdk/pull/15.
zramsay commented 2023-01-13 14:25:24 +00:00
Author
Member
Copy Link

@0xmuralik the second error unable to resolve type URL : tx parse error is using the 0.1.5 release cut yesterday so it included that PR.

See the last line in my original comment:

From discussion, it seems to be that a dependency went from using sha384 -> sha256 (or vice-versa?). The laconic-sdk and its tests were updated for that fix, but this CLI was not.

@0xmuralik the second error `unable to resolve type URL : tx parse error` is using the [0.1.5 release](https://github.com/cerc-io/laconic-sdk/releases/tag/v0.1.5) cut yesterday so it included that PR. See the last line in my original comment: > From discussion, it seems to be that a dependency went from using sha384 -> sha256 (or vice-versa?). The laconic-sdk and its tests were updated for that fix, but this CLI was not.
i-norden commented 2023-01-13 17:28:13 +00:00
Member
Copy Link

Hey @zramsay stupid question: which version of laconicd are you running this against?

Hey @zramsay stupid question: which version of laconicd are you running this against?
0xmuralik commented 2023-03-01 06:26:14 +00:00 (Migrated from github.com)
Author
Member
Copy Link

This error is due to change in record types support. We only support a few record types See: https://github.com/cerc-io/laconicd/issues/27, https://github.com/cerc-io/laconicd/issues/52 and https://github.com/cerc-io/laconicd/issues/51.
You can get examples for all the supported types from here.

This error is due to change in record types support. We only support a few record types See: https://github.com/cerc-io/laconicd/issues/27, https://github.com/cerc-io/laconicd/issues/52 and https://github.com/cerc-io/laconicd/issues/51. You can get examples for all the supported types from [here](https://github.com/cerc-io/laconicd/tree/main/x/registry/helpers/examples).
zramsay commented 2023-03-01 14:56:04 +00:00
Author
Member
Copy Link

@0xmuralik thanks I will test out locally, however, if i understand correctly, it depends on https://github.com/cerc-io/laconicd/pull/79 and https://github.com/cerc-io/laconic-sdk/pull/27, can you confirm?

@0xmuralik thanks I will test out locally, however, if i understand correctly, it depends on https://github.com/cerc-io/laconicd/pull/79 and https://github.com/cerc-io/laconic-sdk/pull/27, can you confirm?
0xmuralik commented 2023-03-01 15:45:34 +00:00 (Migrated from github.com)
Author
Member
Copy Link

Hi @zramsay, the PRs you mentioned add support for additional record types. But with https://github.com/cerc-io/laconicd/pull/40 the support for the generic record type is removed and only the service provider and website registration records are supported.

Hi @zramsay, the PRs you mentioned add support for additional record types. But with https://github.com/cerc-io/laconicd/pull/40 the support for the generic record type is removed and only the service provider and website registration records are supported.
zramsay commented 2023-03-06 22:54:39 +00:00
Author
Member
Copy Link

#23 and #24 seem to have solved my issues. #26 addresses updates to the README so that this works out of the box

#23 and #24 seem to have solved my issues. #26 addresses updates to the README so that this works out of the box
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/delete-me#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?