Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qri registry prove prints an error response #1096

Closed
feep opened this issue Feb 6, 2020 · 2 comments · Fixed by #1101
Closed

qri registry prove prints an error response #1096

feep opened this issue Feb 6, 2020 · 2 comments · Fixed by #1101
Labels
bug code that is not behaving as expected CLI command line client issues

Comments

@feep
Copy link
Contributor

feep commented Feb 6, 2020

❯ qri version
0.9.4
❯ qri registry prove --username feep --password applesauce
01:45:30.804 ERROR        lib: prove profile response: &{2020-02-06 08:20:01 +0000 UTC feep feep feepish@gmail.com  https://qri-user-images.storage.googleapis.com/1580977528711.png  rusty kay    QmeCw3GRwWR2gWmX2pMuU5DDUeSeoWwisHBGwUBvW879tP CAASpgIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDdOosgina+tdaDMtF6NqPzG0vyqkYJ1EtxWgno7xbsLkIhu0wK2/Z3WSiIdcmAdHCLR6KUl0CUWQLkjjF4pW3eAqE2UTP0y+LrYCBbPWTwvE89z8w677FsladQpiVlOagJG2g5S8eNNtSJ4kPflaNiej0UE2HFvR1eSirmdB4d9dzqyPlexms95P5rFvqOtgIvR6opsD6GXExGdkWQXvzyaZLTcT3PyYx1eAukprOHxUxFjGOk8qqlk63Mfz076oeuziBFI7cKfzZ1TZjtUccrnon3uNN8z8e0DTGDUGTbhpb8PbRhd0Gq4A9ZueCKeC19UlovgHkGH3D5Q65HCuFFAgMBAAE= TxNL20hqXpQrHu0UEOEV/vnMzjbMShG0j8ZCXKZRcxjHW5yPfDPdTFq5Db0MiJr4Rz+69EeAdLk9Dia5j8rs1vB1W7L7QEHBPqWb2TltVhyorxB9U0EXNAx5OM3GFTFBrAjPIInnCJA1ds+uZDkQcJ3igkeCjGBhQHlOm9iurQDRw+T8IeAUrC38Yk55eR968Th/Ukn4mARsziz1UAdXBVBVtaPNdHp59ONaj8Sz/OJ4GMrhrHkEJR12Rq3Muo9cnSSTlAsHM+Bu7kTcqdXhxa77PBzTek2zudJb6Om1Dvbu03/4lF8KFmdWEyWOvlY4LlOIIsMtMkHJhLXtImPkvQ==} registry.go:59

Arch Linux.

Seems to work correctly otherwise.

@b5 b5 added the bug code that is not behaving as expected label Feb 6, 2020
b5 added a commit that referenced this issue Feb 6, 2020
also added a stderr success printout. logging is still accessible if lib's logging level is debug

closes #1096
@b5 b5 added the CLI command line client issues label Feb 6, 2020
@b5 b5 closed this as completed in #1101 Feb 6, 2020
b5 added a commit that referenced this issue Feb 6, 2020
also added a stderr success printout. logging is still accessible if lib's logging level is debug

closes #1096
@b5
Copy link
Member

b5 commented Feb 6, 2020

Thanks so much for filing this, and for your docs contributions @feep!

PS, another Arch user has kindly offered to help get Qri on AUR. Tracking issue: #1094

@feep
Copy link
Contributor Author

feep commented Feb 7, 2020

Thanks for the fix @b5.

Very well written reply on #1094, I'll add more details.

Frankly, though, I'm aiming for a job with you. With any luck, I won't need an AUR, I'll be building from dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug code that is not behaving as expected CLI command line client issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants