npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/client.rs, branch v1.7.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.7.22024-09-04T12:30:59+00:00refactor: organise into lib and bin structure2024-09-04T12:30:59+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-04T07:04:48+00:00urn:sha1:949c6459aa7683453a7160423b689ceadb08954b
the make the code more readable
this commit just moves the files, the next commit should fix the imports
chore: bump rust-nostr to v0.34.02024-08-28T15:42:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T13:20:34+00:00urn:sha1:a5216602749bff55c2773acce098c91942cd3920
bump all rust-nostr packages
I'm not sure I'm completely happy with allowing mutable_key_type
but it is just run inside tests
it appears that Event didn't have the Copy trait in v0.33.0 so I'm
not sure why this warning suddenly appeared
the timeout of client.get_events_of needed to be doubled which could
indicate that an ineffiency has been introduced in v0.34.0
the primary motivation for upgrading now was to get this fix:
nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm
as I suspect it is also effecting other repositories
eg nostr-profile-manager
Revert "refactor: fix `stderr` ~> `stdout`"2024-08-01T16:18:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T16:18:53+00:00urn:sha1:2de11e4099a1f841666eac6a1f68389b01c3398b
This reverts commit 3d2e031294b467be725a4ac5f5e65e029d25699a.
refactor: fix `stderr` ~> `stdout`2024-08-01T14:49:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T14:49:47+00:00urn:sha1:3d2e031294b467be725a4ac5f5e65e029d25699a
as `stderr` is being used when it shouldn't be
Revert "clear 'fetching updates..' when done"2024-08-01T14:25:50+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T14:25:50+00:00urn:sha1:2bf7276bef9708f7f4d2c344abc0c8f132199433
This reverts commit 4a38d5f4179114fce60f84c4694284a49f648c64.
clear 'fetching updates..' when done2024-08-01T13:58:34+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-01T13:58:34+00:00urn:sha1:4a38d5f4179114fce60f84c4694284a49f648c64
unless there were errors and detailed report doesnt clear
refactor: add struct `RepoState`2024-07-30T14:24:29+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-30T13:14:59+00:00urn:sha1:0848d57c7654d09c3041022c231dfbbbfac17600
to more easily access state details
feat(fetch): fetch state announcements2024-07-29T07:51:08+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-29T07:51:08+00:00urn:sha1:be70a0f518bb19f38ea4f1705989ec6af8b042ac
if multiple maintainers produce state events with the same
timestamp, the event with the largest event_id will be used
refactor: use nip34 kinds from rust-nostr2024-07-24T15:37:10+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-24T15:37:10+00:00urn:sha1:8638b321fdff94d034ec912ecd0910b6f564ff04
instead of Kind::Custom(u16) as v33 of rust-nostr introduced them
chore: bump rust-nostr to v0.33.02024-07-22T14:26:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-22T14:26:44+00:00urn:sha1:0762d44a9ec3d8a5477e171933428cd9749e0659
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message