Skip to content

Add event journal#25

Merged
defnone merged 3 commits into
mainfrom
events-journal
Jun 23, 2026
Merged

Add event journal#25
defnone merged 3 commits into
mainfrom
events-journal

Conversation

@defnone

@defnone defnone commented Jun 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • add an event journal database table, migrations, repository, service, and typed API routes
  • record torrent update, download, file copy, and failure events from workers
  • add a settings journal page with read/read-all actions and infinite loading
  • add route, service, repo, and worker regression tests

Rationale

The app now keeps user-visible operational history for torrent changes and worker outcomes, so failures and important torrent updates can be reviewed from the UI instead of only logs.

Validation

  • bun run lint
  • bun run test
  • bun run build
  • cd server && bunx tsc --noEmit --strict -p tsconfig.app.json
  • cd client && bunx tsc --noEmit --strict -p tsconfig.app.json

Notes

  • Existing lint warnings remain in older React hook and fast-refresh files.
  • Vitest reports an existing nested vi.mock warning in server/test/transmission-adapter.test.ts; it should be cleaned up before a future Vitest release turns it into an error.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces an Event Journal feature to track and display system events related to torrent management. On the backend, it adds a new event_journal database table, migrations, a repository, and a service to record events such as torrent title/magnet changes, sync failures, download statuses, and file copy operations. It also exposes API endpoints to fetch paginated events and mark them as read. On the frontend, a new 'Events Journal' settings page has been added, featuring infinite scrolling, a custom text diff viewer for title/magnet changes, and options to mark events as read. The workers have been updated to log these events, and comprehensive tests have been added. No review comments were provided, and the implementation looks solid, so I have no additional feedback.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@defnone defnone marked this pull request as ready for review June 23, 2026 12:38
@defnone defnone changed the title [codex] Add event journal Add event journal Jun 23, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 217c6ed134

ℹ️ 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".

Comment thread server/src/db/migrations/meta/_journal.json
@defnone defnone merged commit b556d3a into main Jun 23, 2026
7 checks passed
@defnone defnone deleted the events-journal branch June 23, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant