d8e339c4c1 Update build badge to use GitHub badge (dandroid)
Pull request description:
The current build badge using Travis is not working anymore.
This PR uses the badge from GitHub instead.
ACKs for top commit:
afilini:
ACK d8e339c4c1
Tree-SHA512: c08b5dc4b0d6bc0915843d95bfcf84c62317bb8a210f219feca31ce622b2f2b1241ae7987f5c395a980c6b2b3defc48227d43e8491e1adeafadc6e71ecde0db1
3d96644a0f Add raw_call to ElectrumApi (Zoe Faltibà)
Pull request description:
In order to give more flexibility to the users of this library I added a `raw_call` method to the `ElectrumApi` trait that will allow to call any arbitrary electrum API call.
ACKs for top commit:
afilini:
ACK 3d96644a0f
Tree-SHA512: b88ece7bd9ff8121272c3b3528430e9ccb8778661b15cce276c6f67a8797a4dbf4c52a8521191942c21e8b67ebde8187fd75ac49189440b0fbb71274974b4b41
29d77de2f5 doc: s/Satoshi/Bitcoin (zkao)
Pull request description:
Unit was wrong in the docs
ACKs for top commit:
afilini:
ACK 29d77de2f5
Tree-SHA512: a172647cb3c7dc55444f89f9b05832c2b073fc6062c439719bb5c4aecc739be20592ee93111ecee491b0b37e0a0c49f7c3c331a1099bbd6070711d9f5ae0c093
aea9da234b Add `Config::builder` method (志宇)
Pull request description:
The intention is to reduce some confusion on how to manipulate `Config`.
The alternative is to make `Config` fields public.
ACKs for top commit:
afilini:
ACK aea9da234b
Tree-SHA512: 4077e821260c8f6e4bc32a66548e11b1091d384988b392c981102dc3c198a5040831c5feb13b1f7b1a88fd3890d7c44c7516b94f4c2e9cbbc551581c8c72d803
68d2f23306 Upgrade rustls and webpki version (Thomas Eizinger)
Pull request description:
ACKs for top commit:
afilini:
ACK 68d2f23306
Tree-SHA512: 3578954d6629470742fec326525fb34377380c429ff51d5f15e128045161fc6fba4852a22089c2fa9e6bfa7c35ffbaf06eadb0f457fbcb414d15962b9283cd64
Previously, we were logging the retry attempt before we even evaluated
whether or not we are going to retry again. Instead, we now compute
the number of failed attempts and either log and bail from the function
or inform the user that we are going to retry the call.
We also include the name of the failed call and the reason why it failed
in case we are retrying it. Once we have exhausted the the number of
retries, we return all errors anyway so there is no reason to log them.
It is up to the caller to perform error handling.
