npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src, 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.
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
build: env specific fallback relays2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:e8ac3b6b49c6ec38cf4694dc4cb08f12c684ed7b
to prevent tests from poluting public relays
feat(pull): check for clean repo2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:4604de9f25afe235678188e42f4e168587d8a3de
before applying changes and bail if not
feat(prs-list): check for clean repo2024-01-23T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-23T00:00:00+00:00urn:sha1:7799b0edd16b0c97eb58ba2de62be27134a76122
before checking out PR branch
add confirm prompt before checking out branch and applying changes
feat(git): apply pgp sig event tag to commit2024-01-22T00:00:00+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-22T00:00:00+00:00urn:sha1:c543b2f25b6893e5dce6111bc12d9812099251ba
to maintain correct commit ids which is required to apply multiple
commits
its noted that no tests are written and the scenario where the author
and committer differ has not been tested
clearly the validate_patch_applied function has code that corrects an
error where the author / committer 'signatures' do not apply correctly.
this will not be fixed under a pgp signed commit scenario.