Skip to content

fix(e2e): rename E2E domains to NoStatus-compatible labels#171

Merged
EnderOfWorlds007 merged 3 commits into
mainfrom
fix/e2e-nostatus-domains
May 18, 2026
Merged

fix(e2e): rename E2E domains to NoStatus-compatible labels#171
EnderOfWorlds007 merged 3 commits into
mainfrom
fix/e2e-nostatus-domains

Conversation

@EnderOfWorlds007
Copy link
Copy Markdown
Collaborator

@EnderOfWorlds007 EnderOfWorlds007 commented May 18, 2026

Summary

  • All 9 `E2E_DOMAINS` had 6-char bases (e.g. `e2epre`, `e2estr`), which `classifyLabel()` classifies as PopLite (base 6–8 chars + 2 trailing digits)
  • On paseo-next-v2, `setUserPopStatus` is owner-gated — a NoStatus signer (the E2E deployer account) cannot self-attest, so every domain registration was failing at the DotNS phase
  • Renamed all 9 labels to use ≥ 9-char bases + exactly 2 trailing digits, classifying as NoStatus (no PoP required)
  • Also updated a stale comment in `availability.ts` that said PoP-gated names are "still registrable on testnet" — they are not on paseo-next-v2 when the signer is NoStatus
  • Also fixes the `pr-mod` CI cell: since b228817 (`feat: migrate to paseo-next-v2`), `dot mod` uses `getReadOnlyRegistryContract` and never calls `resolveSigner` — the test was still asserting on `"No signer available"` output that no longer exists

Test plan

  • CI `pr-mod` cell passes
  • CI `test-publish` cells (`pr-deploy-frontend`, `pr-deploy-foundry`) pass with new domain names
  • Nightly deploy cells (`nightly-deploy-hardhat`, `nightly-deploy-multi`) pass
  • `nightly-rejections` cell passes (uses `E2E_DOMAINS.preflight`, now `e2eprefly00`)
  • After merge: run `tools/register-e2e-fixtures.ts` to pre-register the new names on-chain

Fixes #169, #170.

All 9 E2E_DOMAINS had 6-char bases, classifying as PopLite under
classifyLabel(). On paseo-next-v2 setUserPopStatus is owner-gated,
so a NoStatus deployer cannot self-attest — every deploy cell was
failing at the DotNS registration phase.

Rename all labels to use ≥9-char bases + exactly 2 trailing digits,
which classifies as NoStatus (no PoP required) on any environment.

Also update a stale comment in availability.ts that described
PoP-gated names as "still registrable on testnet" — they are not
on paseo-next-v2 when the signer is NoStatus.

Fixes #169, #170.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 18, 2026

Dev build ready — try this branch:

curl -fsSL https://raw.githubusercontent.com/paritytech/playground-cli/main/install.sh | VERSION=dev/fix/e2e-nostatus-domains bash

Since b228817 (feat: migrate to paseo-next-v2), dot mod uses
getReadOnlyRegistryContract and never calls resolveSigner. The
--suri flag is a deprecated no-op. The test "exits non-zero with
signer suggestion when no signer available" was asserting on
"No signer available" output that no longer exists.

Update the test to reflect the actual signer-less behavior:
dot mod proceeds directly to the registry lookup, and an unknown
domain produces "not found in registry" (not a signer error).
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 18, 2026

E2E Test Pass · ✅ PASS

Tag: e2e-ci-pr · Branch: fix/e2e-nostatus-domains · Commit: 55983a1 · Run logs

Cell Result Time
pr-deploy-frontend ✅ PASS 3m22s
pr-install ✅ PASS 0m48s
pr-init-session ✅ PASS 1m52s
pr-preflight ✅ PASS 1m46s
pr-mod ✅ PASS 1m18s
pr-deploy-foundry ✅ PASS 1m29s
pr-deploy-cdm ✅ PASS 2m31s
${{ matrix.cell }} ⏭️ SKIP 0m00s
${{ matrix.cell }} ⏭️ SKIP 0m00s

Sentry traces: view spans for this run

getChainConfig() error message says 'Use --env paseo-next-v2' not
'Use --env testnet'. The old assertion was written against an earlier
wording and was masked by the DotNS PopLite failures in the same cell.
@EnderOfWorlds007 EnderOfWorlds007 merged commit 4ca2f28 into main May 18, 2026
20 checks passed
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.

Nightly E2E failure: 2026-05-18

1 participant