npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror, branch v0.1.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v0.1.12024-01-26T21:32:21+00:00chore: 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.
chore: bump cargo.toml to v0.1.12024-01-26T20:28:40+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-26T20:28:40+00:00urn:sha1:d96c8f6687be8966a0bb25c679995fea3b9f0715
in preparation for issuing to crates.io
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
chore: bump cargo verion to v0.1.02024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:15879248571e2753395ecbeb52e67bd2a9ad9db0chore: bump rexpect2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:bb0b1c6b10f4912150cb3e33e6af8a6fdd9bde44
the branch that was referenced was merged 3 months ago but there hasn't
been a new release so targeting the merge commit
build: temporarily disable clippy in ci2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:d5485791b02e82a70631d6e3dafc77b95e2546a0
because ironically the verision used in the nix setup differs from the
one used in the github action
perhaps a rewrite of the the github to use nix is needed
build: exclude fmt clippy from stable in ci2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:e212d5c62fb8a053c1cde4003845a0212aa3f428
because of formatting rules that are only avaiable in nightly