trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      chore/stripe-fixture-collection-harness
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Fixed collection flags being read for truthiness Stripe's SDK form-encodes its request bodies, so a checkout that switched tax collection off arrives carrying the string "false" rather than the boolean. The fake server read that flag for truthiness, and a string is truthy whichever word it holds, so it refused a checkout that had asked for no tax number at all and named a requirement the request had already met. The existing tests missed it because they post JSON, where the flag is a real boolean, so the refusal only appeared under the encoding Ghost actually uses. The completion helper read the same flags the same way and would have let a test answer a question the page never rendered. ref https://linear.app/ghost/issue/BER-3872
    nx run-many --target=build --projects=tag:public-app
Succeeded
Linux
4 CPU cores
read-write access token used
0b29b1d230304
100%

Cache hits

6 of 6 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

6 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