npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror, 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-31T12:04:54+00:00chore: bump cargo.toml to v0.1.22024-01-31T12:04:54+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T12:04:54+00:00urn:sha1:4b66c76a5a3ba878b4603d992353327807b8d8e6
in preparation for issuing to crates.io
chore: remove tmp file added in error2024-01-31T12:02:56+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T12:02:56+00:00urn:sha1:9c54080f8c488098ee2c9e94a236c31d71cd31d3
the file was generated during one of the tests runs that got cut short
chore: nix flake update2024-01-31T10:39:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T10:39:38+00:00urn:sha1:24c83d73fe7c828d5ae0599bacbc2901eea7aaa9
update nix dependancies to latest version using default update options
chore: cargo update2024-01-31T10:33:06+00:00DanConwayDevDanConwayDev@protonmail.com2024-01-31T10:33:06+00:00urn:sha1:70538e9cc9ee814a7ff83f3188b2175c226fb284
update dependancies to latest version stated in cargo.toml
test: 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.
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