Status of this CLI / known bugs #17
Closed
opened 2023-01-12 23:08:07 +00:00 by zramsay
·
7 comments
No Branch/Tag Specified
main
release-v0.2.10
release-v0.2.8
release-v0.2.7
pm-update-script
release-v0.2.6
release-v0.2.5
release-v0.2.4
release-v0.2.3
release-v0.2.2
release-v0.2.1
release-v0.2.0
laconic-deprecated
telackey/sub
zramsay/patch-1
murali/tests
dboreham/test-ci-on-murali-tests
zach/tests
zramsay-patch-1
rebrand-6
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.13
v0.1.12
v0.1.11
v0.1.10
v0.1.9
v0.1.8
v0.1.7
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
Labels
Clear labels
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
Something isn't working
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Good for newcomers
Extra attention is needed
This doesn't seem right
Further information is requested
This will not be worked on
An issue or PR manually copied from GitHub.
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/laconic-registry-cli#17
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 200000aphotonwhich worked and returned the bondID.Publishing a record failed with the following error (second last line):
We cut a new release of
laconic-sdkto include what ideally would've been the fix ie., this commitand the error went from:
to
From discussion, it seems to be that a dependency went from using sha384 -> sha256 (or vice-versa?). The
laconic-sdkand its tests were updated for that fix, but this CLI was not.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.
@0xmuralik the second error
unable to resolve type URL : tx parse erroris using the 0.1.5 release cut yesterday so it included that PR.See the last line in my original comment:
Hey @zramsay stupid question: which version of laconicd are you running this against?
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.
@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?
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.
#23 and #24 seem to have solved my issues. #26 addresses updates to the README so that this works out of the box