Overview - Ghost

GhostWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

Ghost

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

GhostWorkspace

Agents
Replay
VCS
Self-Healing

Average execution time

9m 54s

1686 CI pipeline executions

Computation time saved

42d 4h

Cache hit rate

90%

Protect cache integrity with sandboxing

Time to Green

54m 29s

Was 1h 6m, improved by 18%

Succeeded
31278
aaca3736 Fixed the React editor reverting another writer's alt text and caption (#31279) no ref Another writer's alt text or caption edit doesn't move the post's version token. When a read brought that edit in, this writer's editor turned dirty, and their next save silently reverted it. - Another writer's alt text and caption now show in the feature image field and survive this writer's next save. - Typing in either field builds on their value. A caption the writer is typing in updates once they leave it. - The writer's own alt or caption edit still wins.
by Steve Larson
S
Succeeded
31278
4da3452d Fixed a late save answer rolling the editor's cached read back no ref A read of another writer's later version could land in the editor's query cache before this tab's save answer, which then overwrote it, so a reopen showed the older version and its next save raised a false conflict. The answer now leaves a later cached version alone, by the comparison a reload already makes. A caller that throws on the answer is reported instead of failing a save that has landed, and a spec's held reads are released when it finishes.
by Steve Larson
S
Succeeded
31278
762af764 Merge branch 'main' into slars/editor-seed-saved-post
by Steve Larson
S
Failed
31278
b0b7c3be Fixed a late save answer rolling the editor's cached read back no ref A read of another writer's later version could land in the editor's query cache before this tab's save answer, which then overwrote it, so a reopen showed the older version and its next save raised a false conflict. The answer now leaves a later cached version alone, by the comparison a reload already makes. A caller that throws on the answer is reported instead of failing a save that has landed, and a spec's held reads are released when it finishes.
by Steve Larson
S
Failed
31278
63662782 Fixed posts reopened right after a save opening their pre-save copy no ref After a save the editor refetches the post, and a post reopened before that read landed was built from the copy cached before the save. The read then carried a newer token, which the session only adopts at the token it holds, so the next save raised a false "Someone else is editing this post" banner against the writer's own save. Each acknowledged save now writes the server's answer into the editor's query cache, as a reload already does, so a reopen starts from the saved copy. The acceptance helper that waits for a read now waits for the read itself rather than that copy.
by Steve Larson
S