trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      mike-onc-1925
    • 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
    Changed comment cleanup on post deletion to run in the delete transaction ref https://linear.app/ghost/issue/ONC-1925 No foreign key delete rule works for `comments.in_reply_to_id`: `SET NULL` fails mid-cascade (`errno 1452`) for any post with a reply-to-reply comment, and `CASCADE` hits MySQL's 15-level cascade depth limit (`errno 3008`) on long back-and-forth reply chains, which form a linked list through `in_reply_to_id`. The previous approach of migrating the foreign key to `CASCADE` is therefore reverted - the fix is instead to clear `in_reply_to_id` for the post's comments inside the delete transaction (single and bulk destroy), so the existing `post_id` cascade can delete the comments regardless of thread shape
    nx run ghost:test:e2e
Succeeded
Linux
4 CPU cores
7e89863329682
95%

Cache hits

19 of 20 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

20 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubGhostWorkspace