Conversation
Bumps [@types/supertest](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/supertest) from 6.0.3 to 7.2.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/supertest) --- updated-dependencies: - dependency-name: "@types/supertest" dependency-version: 7.2.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
deleted the
dependabot/npm_and_yarn/backend/types/supertest-7.2.0
branch
Gracker
added a commit
that referenced
this pull request
May 2, 2026
, #70, #109, #112) MemoryRootCauseContract folds eight memory-class Spark ideas into one graph contract. Five facets, all optional and provenance-tagged so missing data surfaces explicitly: - ProcessMemorySnapshot[] for RSS / Swap / mm_event / oomScoreAdj (Spark #11) - LmkKillEvent[] tying kills to oom_score_adj and reason (Spark #12) - DmaBufAllocation[] for DMA / dmabuf / ion / GPU pressure (Spark #13) - MemoryExternalArtifact[] for LeakCanary / KOOM / hprof / baseline imports (Spark #51, #70, #109, #112) - baselineDiff with topContributors[] for the leak baseline diff graph (Spark #34) Plan: docs/superpowers/spark/plans/14-memory-lmk-dmabuf.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Gracker
added a commit
that referenced
this pull request
May 2, 2026
#70, #109, #112) buildMemoryRootCause folds five orthogonal facets (process snapshots, LMK events, DMA/DMABUF allocations, external artifacts, baseline diff) into one MemoryRootCauseContract. baseline.perCategoryBytes is reduced to topContributors[] sorted by absolute delta so the largest-impact category surfaces first regardless of sign (Spark #34 leak baseline diff graph). Coverage status is computed per facet: LeakCanary external artifacts flip Spark #51/#70/#109 to implemented; KOOM artifacts flip Spark #112; baselineDiff flips Spark #34. Missing facets remain scaffolded so the contract honestly records partial coverage. When every facet is omitted, the contract is marked unsupportedReason rather than emitting an empty graph that consumers might mistake for "no memory pressure observed". Tests: 4 cases covering facet pass-through, topContributors ordering, LeakCanary status promotion, and unsupported. Plan: docs/superpowers/spark/plans/14-memory-lmk-dmabuf.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Gracker
added a commit
that referenced
this pull request
May 2, 2026
Land Plan 50 (Spark #34, #67, #105, #150, #176, #177, #178) — durable App/Device/Build/CUJ baseline store with diff and CI regression gate. Reuse boundary: `TraceSummaryBaselineRef` (Plan 02) and `TraceSummaryMetric.metricId` namespace already exist. Plan 50 does not re-define those — `BaselineRecord extends TraceSummaryBaselineRef` so consumers see one shape, and metric ids stay in the same namespace. Plan 50's contribution is durable persistence + cross-baseline diff + CI gate semantics on top of Plan 02. Types added to `backend/src/types/sparkContracts.ts`: - `BaselineMetric` — per-metric aggregate (median/p95/p99/max + sampleCount). Carries `unsupportedReason` so devices that cannot collect a metric (e.g. GPU render stages on certain SoCs) don't silently zero-fill. - `BaselineRecord` — extends SparkProvenance + TraceSummaryBaselineRef. Adds `key` (PerfBaselineKey), `status` (CurationStatus), and `redactionState` ('raw'|'partial'|'redacted'). Service layer enforces sampleCount >= 3 for status='published'; the schema does not so older snapshots remain readable. - `BaselineDiffDelta` — per-metric delta with optional numeric fields + `severity: ... | 'unsupported'`. `unsupportedReason` is required when severity is 'unsupported' (missing on baseline, sample below 3, divide-by-zero, etc.). - `BaselineDiffArtifact` — diff between two baselines or trace-vs-baseline. - `RegressionGateResult` — CI gate output. `diff` is **optional** when status is 'skipped'; the gate must instead record `skipReason` so triagers can audit why the gate did not run. - `BaselineStoreContract` — service surface with `baselines[]` and optional `matrix[]` for SoC/OEM cross-baseline comparison. Seven new test cases in `__tests__/sparkContracts.test.ts` cover the reuse boundary (BaselineRecord populates inherited fields), the unsupported-data paths (metric and delta both), and the skipped-gate contract. Test count: 50 (was 43). Test tier: contract / type-only. `npx tsc --noEmit` clean, sparkContracts.test.ts passes 50/50. Trace regression intentionally not run per the tiered policy in commit d8529e1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @types/supertest from 6.0.3 to 7.2.0.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)