Skip to content

Dev - #2118

Merged
pikonha merged 45 commits into
mainfrom
dev
Aug 13, 2026
Merged

Dev#2118
pikonha merged 45 commits into
mainfrom
dev

Conversation

@pikonha

@pikonha pikonha commented Aug 12, 2026

Copy link
Copy Markdown
Member

Note

Cursor Bugbot is generating a summary for commit 669294b. Configure here.

pikonha and others added 30 commits August 11, 2026 09:38
Show a "Calldata reviewed" badge on proposals that have a calldata review
folder in blockful/dao-proposals, on the proposals list and the proposal
detail page (whitelabel included).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Also correct the ErpcCacheHitRateLow description, which still said 15
minutes after the 'for' duration moved to 1h.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Monitoring changes belong in their own PR; this branch is calldata review only.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ENS-Incentives runs a production application that must reach the self-hosted
Reth node, so mirror the dev consumer stack in production: a per-project
nodeful Tailscale proxy plus an eRPC built from erpc.consumer.prod.yaml.

The rate limiter uses the in-memory driver, so each eRPC deployment counts
independently and the node sees the sum across deployments. Cut anticapture's
own slice (nodeful 800 -> 700, chainstack 200 -> 180) by exactly what the
consumer config grants, keeping total node load unchanged at 800/s.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Matching severity="warning" widened the interval to every warning alert, so
ErpcNodefulNoTraffic, IndexerSyncStale and PostgreSQLHighConnections would
re-notify every 12h instead of hourly. Match the alertname instead, and correct
the ErpcCacheHitRateLow description to the 1h duration the rule now requires.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…-reviewed

# Conflicts:
#	infra/monitoring/alertmanager.yml
Drop the free-form title-slug fallback: it could attach an older proposal's
review to any later proposal whose title reused the phrase. Matching is now
proposal id (numbered folders) or the EP tag in the title (ENS folders).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- iconVariant="success" so ShieldCheck isn't rendered in the inverted color
- hover opacity on the linked badge, so it reads as clickable next to the
  static pills
- let the proposal detail badge row wrap instead of overflowing

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Fixes eight specs that drifted from the current UI, tags a @smoke subset,
adds an hourly Checkly check against production with Slack alerting,
re-enables the dashboard-e2e CI job, and adds a checkly deploy sync workflow.
Links straight to the proposal's calldataCheck.t.sol, which is the actual
proof, instead of the folder.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…uery

The hook only ran once a ProposalItem/TitleSection mounted, so the shield
icons popped in after the list. Kick it off from the sections instead; the
query key is shared, so the rows read it from cache.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Supplies USER_API_URL to the dashboard-e2e job (the /api/user proxy threw
without it and its 500s tripped the 5xx watcher), raises the PGlite hook
timeout in the offchain-indexer db tests for cold CI runners, and pins
playwright to 1.58.2, the version bundled by Checkly's 2026.04 runtime,
so monitor runs stop failing on missing browser binaries.
…meout

Turbo's strict env mode was stripping USER_API_URL before it reached the
Playwright webServer, and the e2e passthrough lists still referenced the
old NEXT_PUBLIC_WC_PROJECT_ID name. Also raises the api vitest hookTimeout
for PGlite suites on cold CI runners, matching user-api.
…headroom

Tags stakeholders, activity feed, and revenue renders as @smoke (7 tests,
one per top-nav surface), raises the webServer boot timeout for cold CI
runners, and resets the checkly monitor history via a fresh logicalId.
… preview

The preview stack runs its own authful, so the dev-issued e2e token gets
401s from the preview gateful and every data-backed spec fails.
Reads BLOCKFUL_API_TOKEN from the dashboard's Vercel project at run time
so the CI copy cannot rot, falling back to the E2E_BLOCKFUL_API_TOKEN
secret when the Vercel read fails.
… one

Collects every BLOCKFUL_API_TOKEN from the Vercel project plus the E2E
secret, uses the first candidate that returns 200 from dev gateful, and
fails fast with a clear message when none authenticates.
…dress-column

fix(dashboard): keep the address column readable on whitelabel stakeholders
Tokens are only valid for their own gateway, so probing every token
against shared dev could never succeed. The e2e job now reads each Vercel
environment's ANTICAPTURE_API_URL, BLOCKFUL_API_TOKEN, and USER_API_URL
as a unit, probes the pair against its own gateway, and adopts the first
one that authenticates, preferring custom (dev) environments.
Drops the Vercel env reading entirely (the API returns ciphertext for
encrypted values, so it can never supply a usable token) and keeps one
up-front check that fails in seconds with the fix when the
E2E_BLOCKFUL_API_TOKEN secret stops authenticating.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@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: e69a484873

ℹ️ 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 .github/workflows/tests.yaml
Comment thread .github/workflows/tests.yaml
A gateful reporting no commit is the previous release still answering
(deployed via `railway up`), so returning ready immediately let codegen read
the stale spec while the CI deploy was in flight. Keep waiting instead, and
downgrade the timeout to a warning when the deploy never lands.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@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: 7e46cb2e70

ℹ️ 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 .github/workflows/release.yaml
Comment thread .github/workflows/tests.yaml
…view

Fork PRs get no repository secrets, so the token probe failed every
external contribution before a test ran. Gate the job on the same trust
output the rest of the workflow uses.

test:e2e also rebuilds the dashboard, regenerating @anticapture/client
from whichever spec ANTICAPTURE_API_URL points at — shared dev, which
omits endpoints the PR adds. Set RAILWAY_ENVIRONMENT_NAME so codegen
resolves the PR's preview gateful while the tests keep hitting dev.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@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: 99f4f9001d

ℹ️ 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 .github/workflows/tests.yaml
… gates

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@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: 6601ba20e0

ℹ️ 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 scripts/wait-for-gateful.mjs
@railway-app
railway-app Bot temporarily deployed to anticapture-infra / dev August 13, 2026 16:25 Inactive
@railway-app
railway-app Bot temporarily deployed to anticapture-infra / anticapture-pr-2118 August 13, 2026 16:25 Destroyed
@pikonha
pikonha merged commit fb6db49 into main Aug 13, 2026
17 of 19 checks passed
@railway-app
railway-app Bot temporarily deployed to anticapture-infra / anticapture-pr-2118 August 13, 2026 16:26 Destroyed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants