trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      chore/limit-service-declared-names
    • Runs and Agents
    • TimelineBeta
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Made the set of limit names a declared one The manifest was already the allowlist the loader applies, but only at runtime: a caller could ask about any name at all, and asking about one nobody had declared quietly answered that the site was not limited. That is the same shape as a typo, and nothing told them apart. The names are now taken from the manifest itself, so asking about a limit that has not been declared does not compile. The loader narrows the host's spelling onto that set, which is the one place a name arrives as text and the only place it needs checking at runtime. Ghost's own route guard and Admin's limiter take the same set, and Admin names the limit a private feature depends on rather than describing it as a string.
    nx run ghost:test:legacy
Succeeded
Linux
4 CPU cores
read-write access token used
8c7b9fb130778
92%

Cache hits

24 of 26 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

25 groups of tasks optimized.

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubGhostWorkspace