feat: add archive diagnostics - #113
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 17691890bc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| lockPath := filepath.Join(dir, ".discrawl-sync.lock") | ||
| require.NoError(t, os.WriteFile(lockPath, []byte("locked"), 0o600)) | ||
| writeSyncLockMetadata(t, lockPath, "wiretap", os.Getpid()) | ||
| require.NoError(t, os.Chmod(lockPath, 0)) |
There was a problem hiding this comment.
Make the lock-probe failure test work as root
When the suite runs as root or with CAP_DAC_OVERRIDE (common in Docker-based CI), chmod 0 does not make os.Open fail, so syncLockState can acquire/release the lock and the command reports stale_metadata instead of unknown. That makes this new Unix test fail in those environments; use a root-independent failure setup or skip this case when running as root.
Useful? React with 👍 / 👎.
Summary
discrawl diagnosticshuman and JSON output for database/WAL paths, sizes, SQLite journal/schema/integrity state, and archive freshnessVerification
GOWORK=off go test -count=1 ./...go vet ./...GOOS=windows GOARCH=amd64 go test -c ./internal/clinode scripts/build-docs-site.mjsCloses #102.