npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/grasp-audit/src/fixtures.rs, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2026-02-26T15:42:09+00:00chore: apply cargo fmt and fix clippy warnings2026-02-26T15:42:09+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-26T15:42:09+00:00urn:sha1:9d86cf15f0275ffeee4519bd054e3b61dc8992ac
Fix pre-existing clippy lints:
- &PathBuf -> &Path in audit_cleanup.rs
- too_many_arguments on process_newly_available_git_data,
process_purgatory_announcements, and HttpService::new
- clone_on_copy for PublicKey (Copy type) in purgatory cleanup loop
add probe subcommand for end-to-end relay health checks2026-02-25T10:50:59+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-25T10:50:59+00:00urn:sha1:cd01c7379f23d9189beef840ddc523a3c90a9a10
Implements grasp-audit probe with full write path (publish events,
poll for repo init, push, verify refs match state) and read-only
fallback (find existing announcement, fetch refs). Supports --nsec
for whitelisted relays, --json output, and --watch for continuous
monitoring.
fix grasp-audit test isolation to prevent cross-spec relay state corruption2026-02-24T14:15:04+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-24T14:15:04+00:00urn:sha1:7f71a2e75a66bcacad9057f5e339e511e689b828
Add Purgatory-prefixed fixture variants (PurgatoryValidRepoSent,
PurgatoryOwnerStateDataPushed) that create independent repos never
shared with the main fixture chain. Purgatory tests that mutate relay
state (replacement announcements, new state events, deletions) now use
these isolated fixtures so they cannot corrupt the repo that
push-authorization tests depend on.
Run purgatory tests before push-auth in the full suite, since push-auth
sends new replaceable state events (kind 30618) for the shared repo_id
that would displace the original served state event.
fix: use unique commit instead of deterministic Owner variant for wrong-commit PR tests2026-02-18T22:12:22+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T22:12:22+00:00urn:sha1:fefb37e040eb3cf91093d597737e1431fed38c81
PRWrongCommitPushedBeforeEvent and test_push_to_nostr_ref_with_wrong_commit_after_event_received_rejected
were calling create_deterministic_commit_with_variant(CommitVariant::Owner) on a clone that already
had test.txt with 'Initial commit\n' content from OwnerStateDataPushed. Writing identical content
staged nothing so git commit failed silently.
Now that ValidRepoServed always depends on OwnerStateDataPushed (git data pushed), the clone is
never empty - use create_commit (unique file) instead since the wrong commit only needs to differ
from PR_TEST_COMMIT_HASH, not be deterministic.
extract OwnerRepoState fixture to make dependency chain explicit2026-02-18T21:56:12+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T21:53:15+00:00urn:sha1:1f0298bcfe125bee5d996e163ad8f3e9c17e3a9e
OwnerStateDataPushed was secretly building and sending the state event
internally, with no corresponding fixture in the chain. Add OwnerRepoState
as the explicit 'state event sent, sitting in purgatory' step so the
dependency chain reads: ValidRepoSent -> OwnerRepoState -> OwnerStateDataPushed -> ValidRepoServed.
OwnerStateDataPushed now reads the state event from the OwnerRepoState cache
rather than rebuilding it, and only owns the git push + purgatory release.
fix: use ValidRepoServed for events that tag repo events2026-02-13T12:31:49+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T12:07:37+00:00urn:sha1:a2a99d5a4137b57e4141cf2840f2f51b38035cfa
PR events, issues, and comments need a queryable repo announcement
to reference. Changed PREvent and PREventGenerated fixtures and
related tests to depend on ValidRepoServed instead of ValidRepoSent.
This ensures tests will fail correctly when announcement purgatory
is implemented - events tagging a repo should require that repo
to be served (not in purgatory).
test: add PR purgatory tests with PREvent2 fixtures2026-02-13T09:24:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T09:24:51+00:00urn:sha1:f4e8e1089ae6e8e78c3576246d9747bb585fdc18
Add new fixtures for testing PR purgatory mechanism:
- PREvent2Generated: PR event with different commit hash
- PREvent2Sent: PR event sent to relay (enters purgatory)
- PREvent2GitDataPushed: Git data pushed after event sent
- PREvent2Served: Full fixture with event served
Add PRTestCommit2 variant for second PR test commit.
Update purgatory tests to use new fixtures for proper PR purgatory testing.
fix: add trailing newlines to deterministic commit content2026-02-13T09:09:59+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-13T09:09:59+00:00urn:sha1:faac6027deaf5f1e121c05df2d8a6336fd6eaf8d
The CommitVariant::file_content() methods were returning strings without
trailing newlines, but the expected hash constants were calculated with
trailing newlines. This caused hash mismatches in tests.
Updated all hash constants to match the actual commit hashes produced
with trailing newlines in the file content.
refactor(grasp-audit): split ValidRepo into Sent/Served, add tolerant purgatory2026-02-12T12:57:44+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-12T12:57:44+00:00urn:sha1:dcaaa0c44c46f963929ab0baa91f63759ec702dc
- Rename ValidRepo to ValidRepoSent (announcement sent, may be in purgatory)
- Add ValidRepoServed (announcement queryable after git data pushed)
- Add send_event_and_note_purgatory() for tolerant purgatory detection
- Update fixtures to use tolerant method instead of strict assertion
- Update event_acceptance_policy tests to use ValidRepoServed
This enables tests to pass regardless of purgatory implementation status
while still having explicit purgatory tests that verify the behavior.
fix: update doctest to use valid FixtureKind::RepoState variant2026-02-12T11:23:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-12T11:23:51+00:00urn:sha1:869fd91e5c652c48a32d284eedc989a79c7afaea