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

11m 8s

1129 CI pipeline executions

Computation time saved

21d 17h

Cache hit rate

87%

Protect cache integrity with sandboxing

Time to Green

38m 53s

Was 49m 37s, improved by 22%

Failed
30779
94cc2c1c Changed the limit service to be built from settings that have been read Host settings arrive from Ghost(Pro) as strings in a single column, and nothing read them before handing them to the limit service. A maximum that is not a number survives that journey intact and then compares false against every count, so the limit reads as configured, is charged for, and is never enforced; the only way anyone finds out is a customer exceeding a limit they were sold. Reading them now happens in one place, which decides everything that makes a limit usable: whether its values can be read, whether a counted limit has anything to count, whether a list has anything on it, and whether a limit that resets has a period to reset against. The service takes what was read rather than raw configuration, so it can assume the limits it is handed already work, and the type it accepts can only be produced by reading a host's settings. How to count what a limit measures is passed apart from the configuration, because it is behaviour rather than configuration and a browser counts differently to a server. None of this can stop a site starting. A limit nobody can use cannot be applied either way, and refusing to boot over one would take a site off the air for a mistake made elsewhere, so each limit is read on its own and the ones that cannot be used are set aside and logged at error level. That also ends one limit taking every other limit down with it, which used to leave a site unlimited in ways nobody chose. ref BER-3952
by Rob Lester
R
Failed
30779
ffa92e46 Fixed a misconfigured limit being accepted and silently never applied Host settings arrive from Ghost(Pro) as strings in a single column, and nothing read them before handing them to the limit service. A maximum that is not a number survives that journey intact and then compares false against every count, so the limit reads as configured, is charged for, and is never enforced. The only way anyone finds out is a customer exceeding a limit they were sold, by which point there is nothing in a log to explain it. Both places that read host settings now parse them, coercing the string-encoded values a host legitimately sends and refusing outright anything that cannot be read, so a mistake fails at the moment it is made rather than becoming a support case months later. The parser lives beside the type it produces and is handed its error type the way the rest of the package is, which keeps Ghost's errors on the server and Admin's in the browser. ref BER-3952
by Rob Lester
R
Failed
30779
fc3b0081 Fixed a misconfigured limit being accepted and silently never applied Host settings arrive from Ghost(Pro) as strings in a single column, and nothing read them before handing them to the limit service. A maximum that is not a number survives that journey intact and then compares false against every count, so the limit reads as configured, is charged for, and is never enforced. The only way anyone finds out is a customer exceeding a limit they were sold, by which point there is nothing in a log to explain it. Both places that read host settings now parse them, coercing the string-encoded values a host legitimately sends and refusing outright anything that cannot be read, so a mistake fails at the moment it is made rather than becoming a support case months later. The parser lives beside the type it produces and is handed its error type the way the rest of the package is, which keeps Ghost's errors on the server and Admin's in the browser. ref BER-3952
by Rob Lester
R
Succeeded
chore/limit-service-faults
57f00374 Merge e0f1aa81c5b00bcb47185fb08197f6ac31bce433 into 5f0bb77cf75d4dd165aa20b6ee66f70cc778f083
by Rob Lester
Failed
chore/limit-service-faults
57f00374 Merge e0f1aa81c5b00bcb47185fb08197f6ac31bce433 into 5f0bb77cf75d4dd165aa20b6ee66f70cc778f083
by Rob Lester
Failed
30779
e0f1aa81 Fixed a misconfigured limit being accepted and silently never applied Host settings arrive from Ghost(Pro) as strings in a single column, and nothing read them before handing them to the limit service. A maximum that is not a number survives that journey intact and then compares false against every count, so the limit reads as configured, is charged for, and is never enforced. The only way anyone finds out is a customer exceeding a limit they were sold, by which point there is nothing in a log to explain it. Both places that read host settings now parse them, coercing the string-encoded values a host legitimately sends and refusing outright anything that cannot be read, so a mistake fails at the moment it is made rather than becoming a support case months later. The parser lives beside the type it produces and is handed its error type the way the rest of the package is, which keeps Ghost's errors on the server and Admin's in the browser. ref BER-3952
by Rob Lester
R
Failed
30779
fc9f28e4 Fixed a misconfigured limit being accepted and silently never applied Host settings arrive from Ghost(Pro) as strings in a single column, and nothing read them before handing them to the limit service. A maximum that is not a number survives that journey intact and then compares false against every count, so the limit reads as configured, is charged for, and is never enforced. The only way anyone finds out is a customer exceeding a limit they were sold, by which point there is nothing in a log to explain it. Both places that read host settings now parse them, coercing the string-encoded values a host legitimately sends and refusing outright anything that cannot be read, so a mistake fails at the moment it is made rather than becoming a support case months later. The parser lives beside the type it produces and is handed its error type the way the rest of the package is, which keeps Ghost's errors on the server and Admin's in the browser. ref BER-3952
by Rob Lester
R
Failed
30779
55c41e82 Moved the pins the package now holds out of Ghost's limits suite That suite was written to pin what a host limit does to a site before any of this moved, at a point when the package had no tests worth trusting and no way to reach Ghost's configuration. Some of what it recorded was never about a site at all: whether an unbuildable limit takes the others down with it, whether a periodic limit registers when its start date cannot be read, whether a name nobody declared is ignored. Those are answered by building a service, and now that the package is here and typed, that is where they are answered. The ones about Ghost's own wiring move beside it, to the suite that already covers loading a host's configuration. What is left asserts only what a caller receives through the API, which is what the suite says it does and the only thing in this repository that proves limits work rather than that Ghost calls a stub.
by Rob Lester
R
Failed
30779
a949aca3 Moved the pins the package now holds out of Ghost's limits suite That suite was written to pin what a host limit does to a site before any of this moved, at a point when the package had no tests worth trusting and no way to reach Ghost's configuration. Some of what it recorded was never about a site at all: whether an unbuildable limit takes the others down with it, whether a periodic limit registers when its start date cannot be read, whether a name nobody declared is ignored. Those are answered by building a service, and now that the package is here and typed, that is where they are answered. The ones about Ghost's own wiring move beside it, to the suite that already covers loading a host's configuration. What is left asserts only what a caller receives through the API, which is what the suite says it does and the only thing in this repository that proves limits work rather than that Ghost calls a stub.
by Rob Lester
R
Succeeded
30779
be20cbe1 Added where limit-service came from to its README The package was moved into Ghost with its history rather than copied, but git log --follow cannot reach the commits from before the move because it does not traverse the merge that brought them in, so following a file stops at the move into src. The README now says where to pick the history back up and which commit to ask from.
by Rob Lester
R
Failed
30779
73fea722 Added where limit-service came from to its README The package was moved into Ghost with its history rather than copied, but git log --follow cannot reach the commits from before the move because it does not traverse the merge that brought them in, so following a file stops at the move into src. The README now says where to pick the history back up and which commit to ask from.
by Rob Lester
R
Failed
30779
58ae13b7 Added where limit-service came from to its README The package was moved into Ghost with its history rather than copied, but git log --follow cannot reach the commits from before the move because it does not traverse the merge that brought them in, so following a file stops at the move into src. The README now says where to pick the history back up and which commit to ask from.
by Rob Lester
R
Succeeded
30779
c95254da Added where limit-service came from to its README The package was moved into Ghost with its history rather than copied, but git log --follow cannot reach the commits from before the move because it does not traverse the merge that brought them in, so following a file stops at the move into src. The README now says where to pick the history back up and which commit to ask from.
by Rob Lester
R
Failed
30779
ed70aecc Added where limit-service came from to its README The package was moved into Ghost with its history rather than copied, but git log --follow cannot reach the commits from before the move because it does not traverse the merge that brought them in, so following a file stops at the move into src. The README now says where to pick the history back up and which commit to ask from.
by Rob Lester
R