Lex Berezhny
8304102136
move <!channel> out of markdown converter
2021-07-27 11:54:08 -04:00
Lex Berezhny
3381aefcfa
notify channel of slack message
2021-07-27 11:39:35 -04:00
Lex Berezhny
279a365cb1
v0.101.1
2021-07-27 11:12:06 -04:00
Lex Berezhny
2c9e00da56
revert version
2021-07-27 11:10:16 -04:00
Lex Berezhny
f7cae69704
switch to using a custom GITHUB_TOKEN for doing releases
2021-07-27 11:07:25 -04:00
Lex Berezhny
b7d58bcdbc
v0.101.1
2021-07-26 17:01:25 -04:00
Lex Berezhny
13a856b843
revert version
2021-07-26 17:00:32 -04:00
Lex Berezhny
8da38985c3
debugging for release
2021-07-26 16:58:11 -04:00
Lex Berezhny
60cf6c6b97
v0.101.1
2021-07-26 16:02:28 -04:00
Lex Berezhny
35c2b34564
Merge pull request #3372 from lbryio/release_process_fixup
...
github release process fixes
2021-07-26 15:58:10 -04:00
Lex Berezhny
ef2e048efc
fixes for release process
2021-07-26 15:57:45 -04:00
Lex Berezhny
6b3261aa33
Merge pull request #3373 from lbryio/fix_typo
...
fix typo in kwargs key
2021-07-26 15:29:29 -04:00
Victor Shyba
1849c02cb6
fix typo in kwargs key
2021-07-26 16:02:48 -03:00
Lex Berezhny
1ec74a89e2
Merge pull request #3367 from belikor/fix-search-claim-id
...
fix error when using `--claim_id` with `lbrynet claim search`
2021-07-23 10:08:57 -04:00
Victor Shyba
c591792de9
has_source is a special case
2021-07-22 16:25:55 -03:00
Victor Shyba
3108543ae5
3 missing fields
2021-07-22 16:25:55 -03:00
Victor Shyba
1eb221c743
translate reposted, signature_valid and normalized
2021-07-22 16:25:55 -03:00
Alex Grin
bebf6bc2e7
Update constants.py
2021-07-22 16:25:55 -03:00
Alex Grin
9e91cc2138
Update constants.py
2021-07-22 16:25:55 -03:00
Victor Shyba
c5b939cfb7
fix tests
2021-07-22 16:25:55 -03:00
Victor Shyba
5bd411ca27
filtering hash->id
2021-07-22 16:25:55 -03:00
Victor Shyba
a533cda6f0
ES: all _hash to _id
2021-07-22 16:25:55 -03:00
Lex Berezhny
fe4b07b8ae
v0.101.0
2021-07-21 12:35:16 -04:00
Lex Berezhny
f9f2ccd904
revert version
2021-07-21 12:28:41 -04:00
Lex Berezhny
d9e87d7c32
publish after uploading release artifacts
2021-07-21 12:27:04 -04:00
Lex Berezhny
a0092c0770
remove docker steps from github action build
2021-07-21 12:14:49 -04:00
Lex Berezhny
3100131125
checkout code in release job
2021-07-21 11:33:41 -04:00
Lex Berezhny
988880cf83
update set_build script to work on github
2021-07-21 11:32:37 -04:00
Lex Berezhny
c3fb9672c4
re-enable skipping failing DHT unit test
2021-07-21 11:25:44 -04:00
Lex Berezhny
0a2d94e425
updated set_build to use GITHUB_ env vars
2021-07-21 09:19:58 -04:00
Lex Berezhny
8d9073cd31
v0.101.0
2021-07-20 22:52:44 -04:00
Lex Berezhny
d075961ffa
removed .gitlab-ci.yml
2021-07-20 22:52:05 -04:00
Lex Berezhny
7a72409b61
fix dht node test
2021-07-20 22:43:57 -04:00
Lex Berezhny
34fc530fba
cleanup github actions to be able to drop gitlab
2021-07-20 22:43:57 -04:00
Jack Robison
f257ff2f97
Merge pull request #3369 from lbryio/fix-hanging-tx-notification
...
fix stuck transaction notification due to race in mempool when advancing a block
2021-07-20 18:54:22 -04:00
Jack Robison
7ad5822c5b
fix test
2021-07-20 16:03:34 -04:00
Jack Robison
9a8f9f0a94
fix stuck notification due to mempool/notification race
2021-07-20 15:14:10 -04:00
belikor
6421cecafb
daemon: fix --claim_id with lbrynet claim search
...
For some reason, when using `claim_search`
with `--claim_id`, the arguments dictionary will also
contain `claim_ids` with an empty list, even if we didn't specify it.
```
lbrynet claim search --claim_id=8945573bcfcb7f8276187dfbb93545eac4ebf71a
```
Using both `claim_id` and `claim_ids` will raise a `ValueError`
exception so the daemon won't return a valid result
even if the claim ID is in fact valid.
So if `claim_id` exists, we need to discard `claim_ids`
if it is empty, before proceeding with the rest of the code.
On the other hand, if `claim_ids` is used, and `claim_id` is absent,
there will be no problem as `claim_id` won't be added to the dictionary.
```
lbrynet claim search --claim_ids=8945573bcfcb7f8276187dfbb93545eac4ebf71a
```
2021-07-19 22:24:43 -05:00
Alex Grin
be544d6d89
Merge pull request #3358 from belikor/improve-install-md
2021-07-19 14:20:44 -04:00
Alex Grin
3c89ecafdd
Merge branch 'master' into improve-install-md
2021-07-19 14:20:39 -04:00
Alex Grin
35ec4eec52
Update INSTALL.md
2021-07-19 14:20:15 -04:00
Alex Grin
e47f737a2f
Update INSTALL.md
2021-07-19 14:15:21 -04:00
Alex Grin
ac671a065b
Merge pull request #3356 from lbryio/propagate_external_ip_change
2021-07-19 14:12:26 -04:00
Alex Grin
74116cc550
Merge branch 'master' into propagate_external_ip_change
2021-07-19 14:12:19 -04:00
Alex Grin
406070a5c3
Merge pull request #3354 from belikor/note-download-blob-peer
2021-07-19 14:10:13 -04:00
Victor Shyba
0ccafd5b53
make get_or_create_usable_address respect the generator lock
2021-07-19 14:09:52 -04:00
Alex Grin
940f517aa3
Merge branch 'master' into note-download-blob-peer
2021-07-19 14:09:51 -04:00
Alex Grin
216e5f65ad
Merge pull request #3363 from lbryio/troubleshoot_p2p_script
...
add script with web endpoints that can troubleshoot p2p/dht
2021-07-19 14:04:28 -04:00
Victor Shyba
a74685d66d
add script to troubleshoot p2p/dht
2021-07-19 15:01:37 -03:00
belikor
b7791d2845
exchange_rate_manager: raise exception if 'error' is in json_response
...
If the error is not handled, the running daemon will continuously
print the following error message:
```
Traceback (most recent call last):
File "lbry/extras/daemon/exchange_rate_manager.py", line 77, in get_rate
File "lbry/extras/daemon/exchange_rate_manager.py", line 189, in get_rate_from_response
KeyError: 0
```
This started happening when the UPBit exchange decided to delist
the LBC coin.
Normally `json_response` should be a dictionary, not a list,
so `json_response[0]` causes an error.
By checking for the `'error'` key, we can raise the proper exception.
Once this is done, the message will be a warning, not a traceback.
```
WARNING lbry.extras.daemon.exchange_rate_manager:92:
Failed to get exchange rate from UPbit: result not found
```
2021-07-19 13:41:49 -04:00
