npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/test_utils/src, branch v1.4.5Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.4.52024-08-28T21:27:19+00:00chore: bump rust-nostr to v0.34.12024-08-28T21:27:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T21:27:19+00:00urn:sha1:23c5aadae9b4dc53f00e58f9b0728048c45843a8
this fixed an efficency thing which meant we needed to increase
a timeout during the update which is reverted int his commit. see:
nostr:nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqg5lfwhruw4qjpnlzq0tct0swnuj9dvavz8gsq8npuyygznstw36882alm
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
feat: set proposal branch prefix to `pr/`2024-08-20T05:25:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T05:25:17+00:00urn:sha1:fedf5166f0c57db14b9e43747121e4b7845b63dd
from `prs/`.
whilst plural reflects usage of `heads` and `tags` in git refs,
singular is shorter and more reflective of usage of branch prefixes
such as `feature/` `fix/`
test(remote): fix first test run2024-08-19T06:43:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-19T06:43:09+00:00urn:sha1:6b46ad9809b42d355c883ff2c75f8ac75d4bd989
if binaries in git-exec-path are copied to
tmp-git-exec-path if the dir doesnt exist
some enties fail to copy which was causing the first test to hang
test: increase rexpect timeout 3s ~> 4s2024-08-08T16:51:27+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:51:27+00:00urn:sha1:091f695c90158f161c54212e1951ba0d48a80b56
to avoid tests intermitantly failing when there is no problem
feat(remote): `push` force push proposal2024-08-08T16:36:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:34:40+00:00urn:sha1:9971f23a184d57600ea9b1962910d32bf6aec185
will issue a proposal revision
test(remote): `push` to existing proposal2024-08-08T14:01:32+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T13:58:29+00:00urn:sha1:b53251925e8cf0393377633ec1012f0613e7c42b
push 2 commits to an existing proposal
there are a lot of asserts in here but if they were split out into
their own tests the suite would take much longer to run as we are
waiting a few seconds in the test to ensure the
timestamps are different
test(remote): helper to run as git remote helper2024-08-08T12:02:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T12:01:21+00:00urn:sha1:8deb88804743c295f756d405afc58313fa3601fd
add a test helper function to enable the git remote helper to be run
as intended (via git) rather than calling it directly
test(git): make drop GitTestRepo optional2024-08-07T14:39:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-07T14:39:28+00:00urn:sha1:62db5899dc60833b013331bfed2cc874628a3297
so that we can inspect the state of a test repo
feat(remote): `list` includes open proposals2024-08-06T09:59:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-06T09:12:26+00:00urn:sha1:f1aa1be738af0dc80eb3b5827249bb537de1e0cd
and filters out other branches in `prs/*` namespace