• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

decentraland / squid-management-server / 24801025979
54%
main: 48%

Build:
Build:
LAST BUILD BRANCH: security/pin-github-actions-sha
DEFAULT BRANCH: main
Ran 22 Apr 2026 08:29PM UTC
Jobs 1
Files 13
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Apr 2026 08:29PM UTC coverage: 51.573% (+6.0%) from 45.54%
24801025979

Pull #75

github

LautaroPetaccio
docs: document purge API and log every drop, would-drop, and skip

Address two gaps reviewers flagged:

1. Public types and methods for the schema purge were thinly or
   inconsistently documented while the extracted queries in
   queries.ts already had JSDoc. Bring them up to the same level:
   - src/ports/squids/types.ts: JSDoc on DatabaseName, PurgedSchema,
     PurgeSkipReason (with a short description of each variant),
     PurgeResult, and ISquidComponent.purgeOldSchemas (contract +
     safety rails + logging summary).
   - src/ports/squids/component.ts: JSDoc on SAFE_SCHEMA_NAME,
     purgeSchemasInDatabase (the classification flow),
     getRunningSquidServiceNames (why it's separate from list()),
     and purgeOldSchemas (entry-point contract).

2. Only the final summary line mentioned schema names; there was no
   per-schema trace and a failed DROP was attributed to the whole
   database rather than to the specific schema. Now every candidate
   produces exactly one log line:
   - info: `Dropped schema` (or `(dry-run) Would drop schema`) with
     { database, schema, ageMs }.
   - debug: `Skipped schema` with { database, schema, reason, ageMs }.
   - error: `Failed to drop schema` with { database, schema, ageMs,
     error } when `withTransaction` throws.

   A per-schema try/catch replaces the coarse outer one: a single
   broken DROP is logged and the run continues with the next
   schema instead of aborting the whole database.

Test-side changes: the mock loggers now include `debug: jest.fn()`
so the new skip log doesn't crash against undefined. No assertion
changes — existing tests cover behaviour, not log call counts.
Pull Request #75: Purge old, unused squid schemas on a daily schedule

72 of 162 branches covered (44.44%)

Branch coverage included in aggregate %.

72 of 93 new or added lines in 3 files covered. (77.42%)

1 existing line in 1 file now uncovered.

223 of 410 relevant lines covered (54.39%)

5.08 hits per line

Uncovered Changes

Lines Coverage ∆ File
18
0.0
0.0% src/components.ts
3
74.49
7.83% src/ports/squids/component.ts

Coverage Regressions

Lines Coverage ∆ File
1
0.0
0.0% src/components.ts
Jobs
ID Job ID Ran Files Coverage
1 24801025979.1 22 Apr 2026 08:29PM UTC 13
51.57
GitHub Action Run
Source Files on build 24801025979
  • Tree
  • List 13
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Pull Request #75
  • PR Base - chore/dependency-overhaul (#24787181135)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc