Repository navigation
Conversation
Add Prometheus jobs for subscription-server, dispatcher, consumers and logic-system (blockful/notification-system), a Notification System row in the Grafana dashboard (scrape status, request rate, 5xx, p99 latency) and document the NOTIF_*_ENDPOINT variables. ServiceDown already matches every non-DAO job, so the new jobs are covered without a rule change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…lugin Add createHttpServerMetrics / createHttpServerRequestDuration, the standard http_server_request_duration_seconds histogram with the labels the alerts and dashboard expect, and registerFastifyMetrics under @anticapture/observability/fastify, which serves /metrics and records every request. Only fastify types are imported, so the entry adds no runtime dependency (fastify is an optional peer). Fix createObservabilityProvider registering the instrumentations before the global meter provider was set: instruments were created on the API no-op meter, so the HTTP auto-instrumentation never exported http_server_duration. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ystem feat(monitoring): scrape the notification system services
Shutter's veto runs through Snapshot X: the Security Council (5-of-8 Safe 0x3ea7...c0C0) owns the Snapshot X space (0x594E...B769) and vetoes a proposal by calling Space.cancel(proposalId) before execution. Point the DAO Overview Security Council card at that multisig. Unlike ENS's renewable term or Compound's guardian expiry, this veto is an owner privilege with no fixed term. Add a `noExpiration` flag to the securityCouncil config; when set, the card shows "No expiration" instead of a countdown and drops the progress/danger bar (ENS and Compound keep their expiration blocks and behavior).
Drop the separate `noExpiration` flag added in the previous commit and treat `securityCouncil.expiration.timestamp === 0` as "no fixed term" instead. This keeps a single source of truth (the timestamp itself) and matches the convention useCountdown already uses (it treats timestamp <= 0 specially). The card still shows "No expiration" and hides the progress/danger bar for Shutter; ENS and Compound keep their real non-zero timestamps and behavior.
…gate button The Delegate column was 96px wide in a table-fixed layout, so the button with the gasless "Free" badge overflowed the table, got clipped by the container and produced a horizontal scroll. The column is now 160px, the whitelabel-only numeric columns give up a few points to the address, and the row actions (Copy + Details) only join the row while it is hovered instead of reserving ~130px of invisible space next to the name. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
fix(dashboard): respect each SPP program's report deadline
…card feat(dashboard): add Shutter Security Council card
fix(dashboard): stop the whitelabel delegates table clipping the Delegate button
chore: version packages
brunod-e
requested review from
LeonardoVieira1630,
PedroBinotto,
alextnetto,
isadorable-png and
pikonha
as code owners
September 30, 2026 18:42
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Collaborator
🎨 UI Review
Overview → Security Council card (Shutter, "No expiration")
Holders & Delegates → Delegates table (whitelabel)
Service Providers
Mobile
Generated by Claude Code |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7c71ed304a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
🚅 Deployed to the anticapture-pr-2170 environment in anticapture-infra
|
railway-app
Bot
temporarily deployed
to
anticapture-infra / anticapture-pr-2170
September 30, 2026 18:47
Destroyed
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.