-
Notifications
You must be signed in to change notification settings - Fork 0
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
btcr-service errors #11
Comments
@kulpreet Are you still about? |
These errors are being caused by dependent libraries mismatching what this library expects. For example, |
Hi all,
I'll try to find time today and synch the two repos. At the least I'll
update READMEs of the two to document which branches work together.
Been a while since I looked at these.
…-kp
On Thu, 8 Aug 2019 at 09:44, Yancy Ribbens ***@***.***> wrote:
These errors are being caused by dependent libraries mismatching what this
library expects. For example, github.com/kulpreet/btcr-service as linked
by ***@***.***/btcr-did-method-updates-d0fd14386139
depends on the github repo github.com/kulpreet/btcr-service/decodeTxref.go.
I've looked through the commit history in both repos to see if there was a
past commit where these two libraries where in sync but haven't found any
so far.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11?email_source=notifications&email_token=AAADHIGGUI3ZUESGBHCDWZTQDPFFDA5CNFSM4IKEC7P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32YNXY#issuecomment-519407327>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAADHIGWYXSXUZ7ULUNGJLLQDPFFDANCNFSM4IKEC7PQ>
.
|
Good to hear from you @kulpreet ! |
Hi all,
I updated the btcd instance and started the btcr-service again. So we have
access to it again. Thankfully I hadn't deleted the EBS volume with the
btcd testnet data! [Phew].
https://btcr-service.opdup.com/txref/txtest1:xz35-jzv2-qqs2-9wjt/resolve
There's a small caveat though, btcd is out of date with testnet and is
"slowly" trying to catch up. It is currently around 100,000 blocks behind
and btcd is taking 10-12 seconds to process one block. Slowly but surely.
The good thing is they make the json rpc is available, so the btcr-service
is running now.
@yancy Ribbens <[email protected]> , on my machine I am using the latest
commits on master branches for btcr-service and txref. I did start some
work to get txref inline with the new changes with the extended
specifications, and those are in the extended branch. Though I am not 100%
sure if btcr-service master branch will work with txref extended branch.
Both on master works for now.
Hope this helps.
I am sorry I had to miss this weeks hackathon. Chasing a release here at
work. I _really_ enjoyed the one last year.
Regards
Kulpreet
…On Fri, 9 Aug 2019 at 01:57, Dan Pape ***@***.***> wrote:
Good to hear from you @kulpreet <https://github.com/kulpreet> !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11?email_source=notifications&email_token=AAADHIAD64754IIXS5U5DKTQDSXGXA5CNFSM4IKEC7P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD35GZVI#issuecomment-519728341>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAADHIEUBKP4DRZW34SHELLQDSXGXANCNFSM4IKEC7PQ>
.
|
I get the following build errors when running through the instructions https://github.com/kulpreet/btcr-service
specifically, go build
# github.com/kulpreet/btcr-service src/github.com/kulpreet/btcr-service/decodeTxref.go:40:47: assignment mismatch: 6 variables but util.Decode returns 5 values src/github.com/kulpreet/btcr-service/resolvetodid.go:54:41: assignment mismatch: 6 variables but util.Decode returns 5 values src/github.com/kulpreet/btcr-service/tip.go:51:41: assignment mismatch: 6 variables but util.Decode returns 5 values src/github.com/kulpreet/btcr-service/txref2txid.go:43:41: assignment mismatch: 6 variables but util.Decode returns 5 values The command '/bin/sh -c go get github.com/kulpreet/btcr-service' returned a non-zero code: 2
The text was updated successfully, but these errors were encountered: