| Age | Commit message (Collapse) | Author |
|---|
|
it was so much clearer what the problem was after
abstracting reused test code
|
|
into lib which makes reading and maintaining tests easier
|
|
of proposals
this is the same fix applied to `list` tests in
bc1e9e7ff8d2c3747a7dbc3b649930ac5bc6425d but
applied to `push` and `pull`
|
|
into lib which makes reading and maintaining tests easier
|
|
to prevent accidental name conflicts. also moved to prs/* namespace
`pull` and `push` integration tests are intermitantly failing to end
at least for `push` they work when run individually but not
when run together
|
|
when finding repo announcements
add a hint to find naddr on gitworkshop.dev
|
|
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message
|
|
to avoid tests intermitantly failing when there is no problem
|
|
when looking for proposal roots 'pull' was not filtering out
proposal revisions
issue identified in failing test, which it now passes
|
|
as part of a project to use fetch and the stored cache everywhere
|
|
as soon as they are successfully sent to at least one relay
|
|
as part of a project to use fetch and the stored cache everywhere
|
|
the last set of pull integration test fails:
when_latest_event_rebases_branch
we are planning on replacing pull so I'm not sure
whether it is worth fixing
|
|
as part of a project to use `fetch` and the stored cache everywhere
|
|
to proposal which is displayed at the end of the functon
|
|
reworking the tests and test suite as appropriate
|
|
when fetching a user profile from user relays it throw an error
when an existing version of the profile wasn't found
|
|
prevent an infinite loop when a new maintainer is identified
that hasn't issued a repo event yet
make it clear when repo_coordinates must not have relays
|
|
as any profile event was being recorded as a update
|
|
rather than ending the loop without fetching them
|
|
prevent infinite loop when new coordinates are found
|
|
into cache directory rather than config directories
also removed CodeCollaboration from path as this isn't helpful
whilst this is a breaking change, the cache was only introduced
during development of this version so it is not
highlighted as such
|
|
rather than as new profiles
|
|
add a message for the temporary situation where a maintainers.yaml
exists without an identifier listed
|
|
add the ability to fetch more than just the current user from
their user write relays
|
|
which will enable the following`list` test to pass once `fetch`
is intergrated into `list`:
finds_based_on_naddr_on_embeded_relay
|
|
only the profile from the saved user was being fetched.
tests are using cli login parameters and expecting to see the
user's name but it was only showing the npub.
fixed by allowing the explicit request of specfic user profiles.
|
|
set repo.nostr to naddr reflecting the announcement just issued
|
|
fetch automatically gets updates to logged in user profile / relays
fetching without specifying repo pointers will just fetch user
profiles so that can be used during login, if user profile isn't
in cache
login now uses fetch
|
|
just from repository / fallback relays and only if we don't already
have a version in cache
this is because we are only using it for the user's name
|
|
as 'fetching... updates:' feels more like further updates are
being fetched than 'fetching... found'
|
|
so it only counts commits and statues to existing proposals
|
|
to increase the likelihood that all events are found
|
|
im preparation for identifying new inbox relays
|
|
enabler to add simplicity, efficency and offline
capability to other functions
improve repo announcement selection
|
|
show open proposal by defult and include options to filter
by other statuses
there are not tests for this currently as the intention is
to transform 'list' further by adding a 'fetch'
|
|
This reverts commit c6cf49d8349c7078e28a3d0e4a7628f91e0195d9
as crates.io requires all dependancies are published to crates.io
we will need to wait until rust-nostr v33 so we don't use the patched
version of v32 from the forked repo
|
|
changelog:
* add support for NIP-46 remote signer
* login to different npubs for different repositories
* store login details in git config so they can be reused by other clients
* cache profile events
* add NIP-31 alt tags to events
* add euc marker per NIP-34 tweak
* fix: ensure repo events of all maintainers are tagged in proposals
* fix: stop filtering out very large patches
|
|
to reflect changes to gitworkshop url structure
|
|
whilst running clippy takes ~2m and tests take ~5m 10s,
'set up job' can take anywhere from 1s to 2ms
|
|
a typo prevented fetching of saved bunker-uri and therefore ngit
would act as if it wasn't saved
|
|
disable event limits in rust-nostr which cause large patches to be filtered out
|
|
if the maintainers tag is omitted
|
|
instead of just tagging the first maintainer's repo event and each
maintainer with a p tag
This allows for easier discoverability of the proposal when:
* the first maintainer hasn't issued a repo event
* the maintainers change over time and the single tagged repo event
is no listed as a maintainer in anyone elses repo event
|
|
to make room for new one
|
|
applies:
nostr:note14jnggugkcf9vg42tcu6h8c842xlxacsatw7uf889xjjdtqr0ptlsfa5tyh
closes
nostr:note1mm77j27kvmkwvvvvth7w4atgjhxrydafl5jkhh7eztkx4fxq4nqq6fnd6y
|
|
currently using patched version of rust-nostr with function to fetch
nip46 relays from nip05 providers. this patch has been merged so it
will make it into the next rust-nostr release.
|
|
as it is failing intermitantly since it is being run in parellel
|
|
and save details in git config
|
|
as config is now stored using git config and cache is conditionally
stored in local ./git folder under test conditions
|
|
so that nip46 bunker signing can be added
|
|
ensure fresh global cache when under test conditions by conditionally
storing it in local ./git folder
|
|
on machines not used to compile. it produces error:
'cannot execute: required file not found'
|
|
replace ngit yaml file config with:
* nsec / ncryptsec / npub in git config in nostr.* namespace
* sql database cache for metadata and relay events
allow different logins to be used for different git repositories by
storing login in local git config
|
|
when the non-default option correctly sent
|
|
local or global but tests only added for local
|
|
add nostr.einundzwanzig.space as suggested by silberengel
remove poorly performing relays
|
|
based on nip34 update.
see nip repository commit 8fe6e062254b37f77540088cccff60fa8615751
|
|
both nostr and nostr-sdk packages and also in test_utils
fix the many breaking changes
fix: ignore trailing slash when depuplicate relays for send events.
this was picked up as TagStandard::RelayMetadata has started adding
a traling slash.
refactor cli output test function `expect_send_with_progress` so that
relays can succeed / fail in a random order
|
|
bump nostr and nostr-sdk packages and also in test_utils
remove custom ncryptsec implementation and use the newly
added implementation nip49 version in rust-nostr
note a patched v0.30 is used so that log_n is exposed so that
user can be warned it might take a few seconds to decrypt.
this has now been merged into the library.
note that this will no longer decrypt existing ncryptsec values as
it is uses a longer string. this should therefore be bundled with
the upcoming change to storing nsec and ncryptsec in git config.
|
|
to repo announcements, patches and cover letters
|
|
changelog:
*fix `ngit init` support for multiple maintainers
|
|
fixes:
nostr:nevent1qqsz2g7gexkmqgr0x4g5kf9py8vx06p8nyn78v7mhevprasnyfy5swcpp4mhxue69uhkummn9ekx7mqzyr7jprhgeregx7q2j4fgjmjgy0xfm34l63pqvwyf2acsd9q0mynuzdyll0c
|
|
changelog:
* remove unreliable relay.f7z.io from default relay set
* `ngit send --in-reply-to` tag any nostr notes and npubs in proposals
* `ngit send` link to proposal on gitworkshop
|
|
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.
for example an issues or kind 1 threads where the proposal is relevant
the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
|
|
as over the last 2-3 weeks it has consitantly be timing out
|
|
after a new root proposal has been sent
link directly to gitworkshop.dev as well as njump.me until
gitworkshop is added to njump
|
|
remove unused binding
|
|
changelog:
* improve relay timeout behaviour
* fix `ngit init` handling of multiple values eg `clone`
* improve reliability via with dependancy upgrade
* build via nix in ci
|
|
away for github and towards gitworkshop.dev
|
|
update dependancies to latest version stated in cargo.toml
|
|
seperate connection timeout from get_events_of timeout and reduce it to 3s
|
|
whilst fmt is using nightly it doesnt appear that clippy is
previous attempts to update the rustfmt nightly version have resulted
in a large number of errors which needed resolving. the change was
backed out because of other priorities.
It appears now that clippy is not using the nightly version
and there are no regressions
|
|
update nix dependancies to latest version using default update options
|
|
to fix relay.get_events_of timeout
|
|
in line with initial merged nip34 spec
|
|
if relays do not connect and retun events within 3s
they will rarely connect at all
this could be reversed when get_events is used async
|
|
update nix dependancies to latest version using default update options
|
|
update dependancies to latest version stated in cargo.toml
|
|
refactor to address breaking changes in rust-nostr
fix a number of in dependancy which have been upstreamed
|
|
using the same dependancies in ci as in development
|
|
rust-nostr author suggested this might be a false positive
https://github.com/rust-nostr/nostr/pull/375#issuecomment-2022245832
|
|
caused by test proposals with the same timestamp
listed in an inconsistant list order;
by ensuring test proposals have a different timestamps
|
|
yukibtc released a patch to address intermittent problem
fetching events, which caused our integration tests to fail
|
|
as patch accepted into package
|
|
to address send_event_to spurious timeout error
|
|
upgrade from rust-nostr v0.27 ~> v0.28 introduces this panic
presumably get_events attempted to write to the MultiProgress
just after it has been removed
|
|
to suppress the clippy too_many_lines in function warning
|
|
as it has been removed from nostr_sdk
|
|
to reflect changes in rust-nostr
|
|
to reflect new name in rust-nostr
|
|
to reflect new name in rust-nostr
|
|
it had moved from 'prelude' to 'hashes'
|
|
to reflect new name in rust-nostr
|
|
both nostr and nostr-sdk packages and also in test_utils
|
|
update nix dependancies to latest version using default update options
|
|
update dependancies to latest version stated in cargo.toml
|
|
changelog:
* fix stack overflow bug when origin remote doesnt exist
|
|
introduced in 098b0258fdd581c750099cb463adbddb57843388
|
|
changelog:
* `ngit send` - improve proposal commit
|