npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src, branch v0.1.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v0.1.22024-01-31T09:42:23+00:00test: dont print verbose get_events log for tests2024-01-31T09:42:23+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T09:42:23+00:00urn:sha1:76db0732fbc6b7dcdd3350d2387bf7144289a0cd
this temporarily fixes tests that rely on the cli output from fetching
events by not printing verbose messages during tests
when a better solution is implemented for communicating get_events
status, it should be intergrated into the tests
fix: intermittent crashing by removing block_on2024-01-31T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T00:00:00+00:00urn:sha1:45dc04b81bf7c07f249c9539a48516d4c17abdba
a crashing bug was identifed when users ran ngit with large relay sets.
the test suite would also stop at random tests and produce a
...running for over 60 seconds error but only on nix configuration
and not when using rustup. this change fixes this so the ngit must have
been crashing more often when ran with the reduced resources of a nix
shell.
the test suite consistantly runs successfully under nix when this change
is applied to v0.1.0. later changes were made to mitigate this and other
issues as hot fixes which either intentionally broke tests (to rush the
change through as a hotfix) or unintentionally in the case of nostr 0.27
upgrade in fc3f22eac2bb81823f170f61ba9d39baff76b933
changes introduced in e0f543e8adb144f6deff6ff7ea0c412c9fcac5b4,
specifically queuing up relays, are probably not needed so I have
increased the number of relays proccessed at any one time from 5 to 15
fix: stop requesting events from blaster2024-01-27T23:08:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-27T23:08:22+00:00urn:sha1:37b7263a628b7a4fa1022af7a9fe42e36b464e09
hardcoding this relay as we have temporarily added to to all new repo
events, it will never return any results and connecting to many relays
is causing problems
fix(login): stop bailing when no name in metadata2024-01-27T22:12:45+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-27T22:12:45+00:00urn:sha1:4589d06023b21a49a4d82fa24228a3879300cd7f
now falls back to displayName, display_name or npub
test pass when loggined printed to the cli in
e0f543e8adb144f6deff6ff7ea0c412c9fcac5b4 are commented out
chore: upgrade rust-nostr v0.27.02024-01-26T21:32:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T21:32:21+00:00urn:sha1:fc3f22eac2bb81823f170f61ba9d39baff76b933
this is a contribution from jk (sectore) that I rebased and squashed
into this commit.
the tests were broken in the last few commits to rush out some fixes.
this change may introduce more issues because of
Relay.respond_standard_req.
fix: use correct fallback relays2024-01-26T20:10:04+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T20:10:04+00:00urn:sha1:9fb37c8c38f55a33657c824caaabba7f72b09ea4
instead of the `more_fallback_relays`
feat(claim): add blaster to relay list2024-01-26T20:04:20+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T20:04:20+00:00urn:sha1:d5058d11caad038fca493c988ff173d30de07672
this is a temporary fix until we handle relays more effectively
fix(claim): use correct fallback relays2024-01-26T19:47:03+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T19:47:03+00:00urn:sha1:f212788263e39a6473c3a109a5eaf5b0bf8cd034
use fallback relays instead of more fallback relays
fix: fetching messages with many unreliable relays2024-01-26T19:17:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T19:17:48+00:00urn:sha1:e0f543e8adb144f6deff6ff7ea0c412c9fcac5b4
the tool had not been tested with large number of user relays, some of
which are misbehaving. It works well when sending events to relays but
struggles when fetching messages.
it seems to crash when accessing a large number of relays. this change
queues up relays so many are not connected to at the same time.
it also shows more verbose messages about its connection and success
with relays.
many of the tests will fail as a result of this change as I havn't
updated them to expect details of more relay interaction.
further changes are urgently needed to improve the speed of fetching
events.
- relay interaction UI should reflect the smooth approach used for
sending events
- we don't need to fetch user events from every relay
- we could show the user information that we have already collected
and allow them to interact
fix(prs-create): remove d tag from pr event2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:7e1f3a03ea4dea7b6aec39a555ce3caf22b88d8b
this shouldn't be present