Files
PaperClipAI/server/src/__tests__/instrumentation.test.ts
T
Nicky LeachandClaude Opus 5.5 11ac90e31f fix(build): typecheck server/src/__tests__ and fix every type error (#18739)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work
> - The server has about 1,100 test and helper files in
`server/src/__tests__`
> - `server/tsconfig.json` excludes that directory, Vitest does not
check types, and no script runs the tsconfig in that directory
> - So a test can call a function with the wrong arguments and still
pass, and no tool reports it
> - This gap hid 2,168 real type errors, and some of them hid tests that
did not test what they claim
> - This pull request fixes all of these errors and adds the directory
to the server layers from paperclipai/paperclip#18737
> - The benefit is that a type error in a server test now fails the
typecheck, with no baseline and no backlog

## Linked Issues or Issue Description

Refs paperclipai/paperclip#18737, which is merged and added the server
layers. Refs paperclipai/paperclip#18738, which is merged and checks the
test projects outside `pnpm -r`, so it is not a duplicate. Refs
paperclipai/paperclip#18137, which records that this directory has no
check.

**What happened?**

No tool checked the types of 1,074 of the 1,101 files in
`server/src/__tests__`. I searched `package.json`, the workflows, and
all tsconfig files. 27 files are in the program of another tsconfig, and
these 27 have 0 errors. 11 of the 27 are in
`helpers/maintenance/tsconfig.json`. No script ran that project when I
measured this. paperclipai/paperclip#18738 now runs it.

**Expected behavior**

The server typecheck checks these files, and a type error fails the
check.

**Steps to reproduce**

1. On the base commit, run `tsc -p server/src/__tests__/tsconfig.json
--noEmit`. It reports 6,536 errors and needs 12.3 GiB.
2. Add a type error to any file in `server/src/__tests__`.
3. Run `pnpm --filter @paperclipai/server typecheck`. It passes.

**Paperclip version or commit**

I measured the error breakdown below on commit `8dfd632452`, with
TypeScript 7.0.2. The branch now includes master up to
paperclipai/paperclip#18865.

**Deployment mode**

Not applicable. This issue applies to development and CI. No production
source file in the server changes.

### Error breakdown

Each row adds one change to the row above.

| Step | Total errors | Change | Cause |
| --- | --- | --- | --- |
| Config as committed | 6,536 | | |
| Add `src/types/*.d.ts` | 4,447 | -2,089 | Config. The Express request
types were missing. |
| Set `rootDir` to the repository root | 2,436 | -2,011 | Config. |
| Set `allowImportingTsExtensions` | 2,181 | -255 | Config. Vitest
accepts `.ts` imports. |
| Add `ES2024.Promise` to `lib` | 2,138 | -43 | Config. Node 24 has
`Promise.withResolvers`. |
| Set `allowJs` for `.mjs` imports | 2,148 | +10 | Config. It removes 8
`TS7016` errors and shows new real errors. |
| Set `declaration` to false | 2,142 | -6 | Config. Tests emit nothing.
|
| Count only files in `server/src` | 2,058 | -84 | Other packages: 53
Daytona, 29 Runner test, 2 UI. |

So 4,478 of the 6,536 errors (69%) came from config or scope, and 2,058
are real type errors in 314 files. The 29 Runner test errors are also
real, which gives 2,087 errors. Tests that master added after this
measurement had 81 more errors, so this pull request fixes 2,168 errors.

This table classifies the first 2,058 errors.

| Kind of real error | Errors |
| --- | --- |
| Wrong argument or assignment type | 1,023 |
| Stale or partial fixture objects | 525 |
| Property that the type does not have | 317 |
| Missing narrowing of null or unknown | 101 |
| Implicit any | 60 |
| Missing name or module | 16 |
| Other | 16 |

### What the type errors hid

Most errors were stale fixtures and loose mocks. These errors hid real
test problems, and this pull request fixes them:

- **A test that never ran.** `instrumentation.test.ts` required
`sdk-trace-base`, which is not installed. So 3 span tests were skipped.
They now run and pass.
- **Assertions that could not fail.**
- `issue-thread-interactions-service` used a company ID as an issue ID.
- `status-card-evaluation-work` compared `[]` with `[]` in a rollback
check.
- `slack-conversation-lifecycle` read `item.issueId`, which does not
exist.
  - `email-channels` used a permission key that does not exist.
- `heartbeat-project-env` imported `LOW_TRUST_REVIEW_PRESET`, which is
not exported. The value was undefined.
- **Postgres processes that did not stop.** 11 test files called `stop`
on the test database helper. That method does not exist, and the helper
method is `cleanup`.
- **Arguments that the service ignored.**
- `methodKey` is now `connectionMethodKey` in the Daytona, Unikraft,
1Password, and Railway tests.
- 108 calls passed `"owner-user"` to a parameter that expects an options
object.
- 9 chat wizard fixtures passed `managementContext` as `source`, so they
ran `existing_app` and not `manifest`.
  - 2 tests passed a `{ userId }` actor that the function ignores.
- Inserts into `environments` passed a `companyId` column that the table
does not have.
- **Problems in tests that master added during this work.**
- `sandbox-creation-operations` read `database.connectionString` when an
external test database was set. In that mode `database` is undefined, so
the fixture would stop with a TypeError. It now uses the external URL.
- `idle-completed-history` set a Dot operation to `dispatched`. That is
a Muse status, and the Dot type does not have it. The fixture now uses
`admitted`, which is a real in-flight Dot status.

### Possible product problems, not changed

These may be real problems in production code or types. I did not change
them, because this pull request does not change production behavior:

- `decisions-service` `service.create` does not validate the lenient
`cancel_issue_tree` input.
- `createConnection` ignores `input.connectionPurpose`.
- The `createConnection` route schema default stores `{}` for
`transportConfig`.
- `prepareManagedAiRuntime` accepted the invalid value `mode:
"connection"`.
- `createBinding` accepts invalid `projectionClass` strings outside
class 3.
- `ensureManagedProjectWorkspace` forwards an untyped `repoRef` by
spread.
- `routineVariableSchema.label` is optional, but `RoutineVariable.label`
is required.
- `ToolRunContext.projectId` may be too strict.
- `withdrawInteraction` reads `issue.status`, which its type omits.
- `issueService.list` and `reconcileNativeFinalizations` omit fields
that they return at runtime.
- `createGitHubExternalObjectProvider` handles `tokenProvider: null`,
but its type forbids this value.

## What Changed

- Fixed the 2,168 type errors. The diff changes 322 test and helper
files.
- Corrected `server/src/__tests__/tsconfig.json`. Editors and the
typecheck now read the same options and report the same errors.
- Added three `test-tree` layers to
`server/scripts/typecheck-layers.mjs`. They read the server layers as
declarations, and any error fails them. A hash of the path selects the
shard, so a new file does not move other files.
- Added `server/scripts/typecheck-stubs/daytona-sdk.d.ts`. Server tests
reach Daytona plugin source, and the root install does not have
`@daytonaio/sdk`.
- Changed two imports in `ui/src/lib/issue-execution-policy.ts` to use
`.js` extensions, because server tests import this file.
- Made `declarationsConfig` and `--declarations-only` skip the
`test-tree` layers, because these layers emit nothing. Other projects
read only the source layers. Added a test for this.
- Updated `doc/DEVELOPING.md`.

## Verification

Run these commands:

```sh
pnpm --filter @paperclipai/server typecheck
pnpm exec vitest run server/scripts/typecheck-layers.test.mjs
```

Results on macOS (arm64), Node 24, 16 cores. Each check ran after the
merge of paperclipai/paperclip#18738 unless the row says otherwise:

| Check | Commit | Result |
| --- | --- | --- |
| Server typecheck, `PAPERCLIP_TYPECHECK_LOW_MEMORY=1`, all 7 layers |
`6e45a08573` | Exit 0, 0 errors, 62 seconds, peak 3.52 GiB |
| `node scripts/typecheck-test-projects.mjs --low-memory` | `a3306bd13e`
| Exit 0, 0 errors, 42 seconds, peak 3.25 GiB |
| The same script with `--reuse-declarations` | `1b878aabc0` | Exit 0, 0
errors |
| `typecheck-layers.test.mjs` and `live-recovery-work.test.ts` |
`01db5634e4` | 90 passed. These include real compiler runs for a pass, a
type error, and an invalid tsconfig. |
| `tsconfig.declarations.json` after a full server typecheck |
`0fb1e4fb0a` | It references only `below`, `cycle`, and `above`. No
generated config names a `tsconfig.layers.json` file. |
| Owned runtime test in `idle-completed-history` | `e8f2f448ac` |
Passed, with the fix that master later replaced |
| `idle-incoming-wake`, `plugin-idle-manager`, and the changed
`chat-channels` test | `6e45a08573` | 30 passed |
| Runner `native-execution.test.ts` | `eab4dcc1f4` | 114 passed |
| The 19 server test files that changed since `eab4dcc1f4`, and
`typecheck-layers.test.mjs` | `259737b700` | 4,275 of 4,277 passed. The
2 failures are in `chat-channels` and are in the list of 7 below. |

The peak is the largest single process, from `/usr/bin/time -l`. Peaks
for the server typecheck were between 3.42 GiB and 3.56 GiB across 8
runs. Peaks for the test projects were 3.25 GiB and 3.37 GiB across 2
runs. I did not measure a cgroup.

**Runtime check of the fixes.** Types do not prove that a test still
works. So I ran all 309 changed server test files, 11,929 tests, before
the rebase onto paperclipai/paperclip#18737:

| Result | Tests | Detail |
| --- | --- | --- |
| Passed | 11,913 | Includes the 2 tests and the 54 `dot-runner` tests
that passed in a later run, as described below. |
| Failed | 7 | The same 7 tests also fail on the commit before the
fixes. |
| Skipped | 9 | These tests have their own skip conditions: `sentry` 5,
and 1 each in `bundled-plugin-registration`, `customer-success-cloud`,
`onepassword-connection`, and `workspace-runtime-https-live-exercise`. |

The 7 tests that fail with and without this change, on my machine:

- 3 tests in `chat-channels` and `email-channels` stop with `ENOENT` on
a `SKILL.md` file. The path is in the parent checkout, above the git
worktree that I used, so I expect that the worktree is the cause. I did
not prove this.
- `workspace-instance-cleanup` compares `/private/var/...` with
`/var/...`. This is a macOS symlink difference.
- 2 tests in `git-reproducible-managed-checkouts` get
`unknown_base_git_files` and expect `unpushed_managed_checkout`. I did
not find the cause.
- 1 more test in `chat-channels`, `materializes direct external-chat
finals once`, gets `undefined`. I did not find the cause.

CI is the check for these 7 tests. `ci / verify` passed on `eab4dcc1f4`.

Failures during this work:

- My fix to `agent-runtime-connector-access` changed an invalid
permission key in the setup, but not in the assertion. The runtime check
found this. I corrected the assertion, and the file passes.
- `heartbeat-plugin-environment` failed one wait in the full run. It
passed three times alone, so I think that load caused the failure. It
can fail again under load.
- `dot-runner` skipped all 54 tests in the full run because `cargo` was
not on my `PATH`. It then passed 54 of 54 with the toolchain on the
`PATH`.
- My first `lib` value removed the default DOM types, and the error
count went up by 375. I added the DOM libraries.
- My Daytona stub with bare `any` left 48 errors, because generic
helpers then inferred `unknown`. I added shapes that return promises.
- One fix to `agent-secrets-routes` used `class_3_static_lease`, and the
test failed. That class allows only specific paths. I reverted to
`unclassified`.
- `ci / General tests (server (8/12))` failed on `259737b700` because of
the flaky port in `idle-completed-history`. paperclipai/paperclip#18853
fixed this test on master, so this pull request keeps that fix.

**Audit of the diff.** I counted these patterns in added and removed
lines, to find fixes that only hide an error:

| Pattern | Added | Removed |
| --- | --- | --- |
| `@ts-ignore` | 0 | 0 |
| `@ts-expect-error` | 0 | 1 |
| `.skip` | 0 | 0 |
| `as any` | 9 | 9 |
| `: any` | 11 | 2 |
| `as never` | 8 | 2 |
| `as unknown as` | 35 | 4 |
| `Promise<unknown>` | 16 | 5 |
| `expect(` | 128 | 113 |

No hunk removes more `expect(` calls than it adds. Three removals of
test content were intentional, and I checked each one:

- `muse-control` removed `signalToken`. Line 1012 already asserts that
it is absent.
- `merged-pr-confirmation-sweep` removed legacy aliases. Other tests
cover them.
- `heartbeat-workspace-branch-containment` removed a `finalize` branch
that no test row can reach.

Some partial fixtures stay unchecked through `as unknown as` and
`Promise<unknown>`, mostly in `issue-agent-mutation-ownership-routes`
and `issue-comment-reopen-routes`.

**Accuracy of the check.** One program over the tree and the three
shards reported the same errors at the same positions. Memory, as the
peak of the largest process on one thread, was 3.93 GiB for one program
and 2.43 GiB for the largest shard. I measured these two values before
the fixes.

Not run or not proven:

- I did not run the full `pnpm test:run`, or a root `pnpm build`. I
expect CI to run the full suites.
- I did not run the 4 GiB container check, or the full
`scripts/typecheck-low-memory.mjs`. The peaks above come from macOS, so
they are not a Linux cgroup measurement.
- I did not run the UI typecheck after the merges.
- `workspace-runtime-https-live-exercise` is skipped, so its `cleanup`
fix did not run.

## Risks

- **A large diff in test files.** 328 files change. A pull request that
edits the same tests can get merge conflicts. New tests on master can
also add type errors before this merges. Any such error fails this check
and needs a fix here.
- **A higher cost for changes to source types.** A change to a type can
add errors in test files that the author did not touch. The author must
then fix them. This is the purpose of the check, but it is new work.
- **Changed test behavior.** Some tests now run paths that they did not
run before, such as the 9 chat wizard fixtures and the 3 span tests.
They pass here, but they can be more sensitive to timing or to the
environment.
- **The Daytona stub can go stale.** The stub is written by hand. If the
plugin uses a new SDK member, the typecheck reports an error until
someone updates the stub.
- **The release path.** `release-verify.yml` and `scripts/release.sh`
run `pnpm -r typecheck`, so they now run this check.
- **The tsconfig change.** The test transform reads
`server/src/__tests__/tsconfig.json`. The options that I changed are for
type checks, and the runs above passed.
- **A gap that remains.** Tsconfigs in `packages/paperclip-runner` and
in most sandbox provider plugins exclude `*.test.ts`. This check does
not read most of those test files, so they can still drift. That work is
separate from this pull request.

> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.

## Model Used

Anthropic Claude Opus 5.5 (`claude-opus-5-5`) through Claude Code, with
reasoning, tool use, code execution, and subagents. The runtime does not
show the context window size.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [ ] I have run tests locally and they pass (7 tests fail locally, with
and without this change. See Verification.)
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 15:27:38 -08:00

451 lines
19 KiB
TypeScript

import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
import { createRequire } from "node:module";
/**
* Tests for the opt-in OpenTelemetry bootstrap. The @opentelemetry/* packages
* are optional peer dependencies and are NOT installed in CI, which is itself
* part of the contract under test: with the endpoint set but packages absent,
* the module must warn and settle instead of crashing the server.
*
* The module reads OTEL_* env vars at import time, so each test resets the
* module registry and imports a fresh copy.
*/
const ENDPOINT_ENV = "OTEL_EXPORTER_OTLP_ENDPOINT";
const PROTOCOL_ENV = "OTEL_EXPORTER_OTLP_PROTOCOL";
const originalEndpoint = process.env[ENDPOINT_ENV];
const originalProtocol = process.env[PROTOCOL_ENV];
async function importFreshInstrumentation() {
vi.resetModules();
return await import("../instrumentation.js");
}
beforeEach(() => {
delete process.env[ENDPOINT_ENV];
delete process.env[PROTOCOL_ENV];
});
afterEach(() => {
if (originalEndpoint === undefined) delete process.env[ENDPOINT_ENV];
else process.env[ENDPOINT_ENV] = originalEndpoint;
if (originalProtocol === undefined) delete process.env[PROTOCOL_ENV];
else process.env[PROTOCOL_ENV] = originalProtocol;
vi.restoreAllMocks();
});
describe("resolveProtocol", () => {
it.each([
[undefined, "grpc", "@opentelemetry/exporter-trace-otlp-grpc"],
["", "grpc", "@opentelemetry/exporter-trace-otlp-grpc"],
["grpc", "grpc", "@opentelemetry/exporter-trace-otlp-grpc"],
["http/protobuf", "http/protobuf", "@opentelemetry/exporter-trace-otlp-proto"],
["http/json", "http/json", "@opentelemetry/exporter-trace-otlp-http"],
["HTTP/JSON", "http/json", "@opentelemetry/exporter-trace-otlp-http"],
// Surrounding space is trimmed before the switch, not only letter case.
[" HTTP/PROTOBUF ", "http/protobuf", "@opentelemetry/exporter-trace-otlp-proto"],
])("maps OTEL_EXPORTER_OTLP_PROTOCOL=%s to %s", async (raw, protocol, packageName) => {
if (raw === undefined) delete process.env[PROTOCOL_ENV];
else process.env[PROTOCOL_ENV] = raw;
const { resolveProtocol } = await importFreshInstrumentation();
expect(resolveProtocol()).toEqual({ protocol, packageName });
});
it("warns and falls back to grpc on an unrecognized protocol", async () => {
process.env[PROTOCOL_ENV] = "carrier-pigeon";
// Spy before the import so the assertion holds even if a future change
// makes the warning fire at module load time instead of on the call.
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
const { resolveProtocol } = await importFreshInstrumentation();
// The fallback must also select the grpc exporter package, not just a
// grpc-labeled protocol.
expect(resolveProtocol()).toEqual({
protocol: "grpc",
packageName: "@opentelemetry/exporter-trace-otlp-grpc",
});
expect(warn).toHaveBeenCalledWith(expect.stringContaining("carrier-pigeon"));
// One unknown input logs exactly one warning, not one per lookup.
expect(warn).toHaveBeenCalledOnce();
});
});
describe("instrumentationReady", () => {
it("resolves immediately when OTEL_EXPORTER_OTLP_ENDPOINT is unset", async () => {
const { instrumentationReady } = await importFreshInstrumentation();
await expect(instrumentationReady).resolves.toBeUndefined();
});
it("settles with a diagnostic instead of throwing when the endpoint is set but packages are missing", async () => {
process.env[ENDPOINT_ENV] = "http://collector:4318";
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
const { instrumentationReady } = await importFreshInstrumentation();
// Bootstrap must absorb the failed dynamic imports — the server keeps
// booting without tracing rather than crashing on an opt-in feature.
await expect(instrumentationReady).resolves.toBeUndefined();
expect(warn).toHaveBeenCalledWith(
expect.stringContaining("@opentelemetry/* packages are not installed"),
expect.anything(),
);
});
});
describe("checkExactPeerVersions", () => {
it("passes when the installed version matches the declared version exactly", async () => {
const { checkExactPeerVersions } = await importFreshInstrumentation();
const require = createRequire(import.meta.url);
const vitestVersion = (require("vitest/package.json") as { version: string }).version;
const result = checkExactPeerVersions(["vitest"], { vitest: vitestVersion });
expect(result).toEqual({ ok: true });
});
it("reports a package as missing when it cannot be resolved", async () => {
const { checkExactPeerVersions } = await importFreshInstrumentation();
const result = checkExactPeerVersions(["@paperclipai/does-not-exist-anywhere"], {
"@paperclipai/does-not-exist-anywhere": "1.0.0",
});
expect(result.ok).toBe(false);
if (!result.ok) {
expect(result.diagnostic).toContain("@opentelemetry/* packages are not installed");
expect(result.diagnostic).toContain("@paperclipai/does-not-exist-anywhere");
}
});
it("reports a package as mismatched when the installed version differs from the declared version", async () => {
const { checkExactPeerVersions } = await importFreshInstrumentation();
const require = createRequire(import.meta.url);
const vitestVersion = (require("vitest/package.json") as { version: string }).version;
const result = checkExactPeerVersions(["vitest"], {
vitest: "0.0.0-not-the-installed-version",
});
expect(result.ok).toBe(false);
if (!result.ok) {
expect(result.diagnostic).toContain("a package is installed at an unsupported version");
expect(result.diagnostic).toContain(`vitest@${vitestVersion}`);
expect(result.diagnostic).toContain("expected 0.0.0-not-the-installed-version");
}
});
});
describe("bootstrapOtel exact-version gate", () => {
it("does not mention the two exporters OTEL_EXPORTER_OTLP_PROTOCOL did not select", async () => {
process.env[ENDPOINT_ENV] = "http://collector:4318";
process.env[PROTOCOL_ENV] = "http/json";
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
const { instrumentationReady } = await importFreshInstrumentation();
await instrumentationReady;
// The OTel packages are absent in this test environment, so the gate
// reports every checked package as missing. It must have checked the
// selected exporter (http/json → exporter-trace-otlp-http) and skipped
// the two the protocol did not select.
const diagnosticCall = warn.mock.calls.find((call) =>
String(call[0]).includes("@opentelemetry/* packages are not installed"),
);
expect(diagnosticCall).toBeDefined();
const message = String(diagnosticCall![0]);
expect(message).toContain("@opentelemetry/exporter-trace-otlp-http");
expect(message).not.toContain("@opentelemetry/exporter-trace-otlp-grpc");
expect(message).not.toContain("@opentelemetry/exporter-trace-otlp-proto");
});
it("emits exactly one diagnostic when the endpoint is set and packages are absent", async () => {
process.env[ENDPOINT_ENV] = "http://collector:4318";
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
const { instrumentationReady } = await importFreshInstrumentation();
await instrumentationReady;
const diagnosticCalls = warn.mock.calls.filter((call) =>
String(call[0]).includes("@opentelemetry/* packages are not installed"),
);
expect(diagnosticCalls).toHaveLength(1);
});
});
describe("bootstrapOtel post-gate load failure", () => {
it("logs a load-failure diagnostic, not the missing-package message, when a package passes the gate but its dynamic import fails", async () => {
process.env[ENDPOINT_ENV] = "http://collector:4318";
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
// Fake the resolution steps the exact-version gate uses, so every checked
// package reports as installed at its declared version. The dynamic
// `import(...)` calls in bootstrapOtel are untouched, so they still fail
// for real — the packages are not actually installed in this test run.
// That forces the one path the catch block now must describe: a package
// that passed the gate but failed to load.
const FAKE_ROOT = "/fake-otel-pkg";
const require = createRequire(import.meta.url);
const peerDependencies = (
require("../../package.json") as { peerDependencies?: Record<string, string> }
).peerDependencies ?? {};
vi.resetModules();
vi.doMock("node:fs", async (importOriginal) => {
const actual = await importOriginal<typeof import("node:fs")>();
return {
...actual,
existsSync: (path: unknown) =>
String(path).startsWith(FAKE_ROOT) ? true : actual.existsSync(path as never),
readFileSync: (path: unknown, options?: unknown) => {
const asString = String(path);
if (asString.startsWith(FAKE_ROOT) && asString.endsWith("package.json")) {
const name = decodeURIComponent(
asString.slice(FAKE_ROOT.length + 1, -"/package.json".length),
);
return JSON.stringify({ name, version: peerDependencies[name] });
}
return actual.readFileSync(path as never, options as never);
},
};
});
vi.doMock("node:module", async (importOriginal) => {
const actual = await importOriginal<typeof import("node:module")>();
return {
...actual,
createRequire: (...args: Parameters<typeof actual.createRequire>) => {
const real = actual.createRequire(...args);
const fake = ((id: string) => real(id)) as typeof real;
fake.resolve = ((id: string, options?: unknown) =>
id in peerDependencies
? `${FAKE_ROOT}/${encodeURIComponent(id)}/index.js`
: real.resolve(id, options as never)) as typeof real.resolve;
return fake;
},
};
});
try {
const { instrumentationReady } = await import("../instrumentation.js");
await instrumentationReady;
} finally {
vi.doUnmock("node:fs");
vi.doUnmock("node:module");
}
for (const call of warn.mock.calls) {
expect(String(call[0])).not.toContain("packages are not installed");
expect(String(call[0])).not.toContain("Install @opentelemetry/sdk-node");
}
expect(warn).toHaveBeenCalledWith(
expect.stringContaining("passed the version check"),
expect.anything(),
);
});
});
describe("getStartupTracer", () => {
it("returns a usable tracer-shaped object when OTEL_EXPORTER_OTLP_ENDPOINT is unset", async () => {
const { getStartupTracer } = await importFreshInstrumentation();
const tracer = getStartupTracer();
// The accessor never returns null. The result exposes the span surface the
// startup seam calls, so the caller needs no null check.
expect(tracer).not.toBeNull();
expect(typeof tracer.startSpan).toBe("function");
// A no-op tracer must carry attribute, status, and end calls without
// throwing: the startup seam sets attributes and status before it ends.
expect(() => {
const span = tracer.startSpan("workspace.resolve");
span.setAttribute("k", "v");
span.setStatus({ code: 0 });
span.end();
}).not.toThrow();
});
it("loads no OTel SDK package when the endpoint is unset", async () => {
const warn = vi.spyOn(console, "warn").mockImplementation(() => {});
const { getStartupTracer, instrumentationReady } = await importFreshInstrumentation();
// The endpoint is unset, so the bootstrap never runs and no SDK package
// import is attempted; readiness resolves at once.
await expect(instrumentationReady).resolves.toBeUndefined();
// The accessor still returns a usable tracer even though no @opentelemetry
// SDK package is installed. That proves it never imported the SDK: a hard
// dependency on the SDK would throw here instead.
const tracer = getStartupTracer();
expect(typeof tracer.startSpan).toBe("function");
expect(() => tracer.startSpan("stage.sync").end()).not.toThrow();
// The bootstrap "packages are not installed" diagnostic must not fire on
// this path. That message comes only from the endpoint-set bootstrap.
for (const call of warn.mock.calls) {
expect(String(call[0])).not.toContain("@opentelemetry/* packages are not installed");
}
});
});
describe("getStartupTraceContext", () => {
it("returns a tracer and a parent-context helper that never throw when the endpoint is unset", async () => {
const { getStartupTraceContext } = await importFreshInstrumentation();
const traceContext = getStartupTraceContext();
// The tracer handle carries the same span surface as getStartupTracer.
expect(() => {
const span = traceContext.tracer.startSpan("runtime.exec");
span.setAttribute("k", "v");
span.setStatus({ code: 0 });
span.end();
}).not.toThrow();
// The helper never throws. It returns a parent token when the api
// resolves, or `undefined` from the no-op fallback when it does not.
expect(() => traceContext.contextWithSpan({})).not.toThrow();
});
});
describe("shutdownInstrumentation", () => {
it("is a no-op when tracing is off and idempotent across calls", async () => {
const { shutdownInstrumentation } = await importFreshInstrumentation();
const first = shutdownInstrumentation();
const second = shutdownInstrumentation();
// Memoized: concurrent callers share one shutdown promise.
expect(first).toBe(second);
await expect(first).resolves.toBeUndefined();
});
it("resolves after a failed bootstrap instead of hanging", async () => {
process.env[ENDPOINT_ENV] = "http://collector:4318";
vi.spyOn(console, "warn").mockImplementation(() => {});
const { shutdownInstrumentation } = await importFreshInstrumentation();
await expect(shutdownInstrumentation()).resolves.toBeUndefined();
});
});
// The `@opentelemetry/*` packages are optional. When they are absent,
// `recordProviderPluginSpan` is a no-op by contract, so a native-duration test
// cannot run. Resolve the SDK first and skip the test when it is not installed.
const otelSdk = (() => {
try {
const require = createRequire(import.meta.url);
return {
api: require("@opentelemetry/api") as typeof import("@opentelemetry/api"),
sdk: require("@opentelemetry/sdk-trace") as typeof import("@opentelemetry/sdk-trace"),
};
} catch {
return null;
}
})();
const hrTimeToMs = (time: [number, number]): number => time[0] * 1000 + time[1] / 1e6;
describe.skipIf(!otelSdk)("recordProviderPluginSpan native duration", () => {
it("opens the span at the true start time and ends it at the true end time", async () => {
const { api, sdk } = otelSdk!;
const exporter = new sdk.InMemorySpanExporter();
const provider = new sdk.TracerProvider({
spanProcessors: [new sdk.SimpleSpanProcessor({ exporter })],
});
api.trace.setGlobalTracerProvider(provider);
try {
const { recordProviderPluginSpan } = await import("../instrumentation.js");
const startTimeMs = Date.now() - 4500;
const endTimeMs = startTimeMs + 4500;
recordProviderPluginSpan({
name: "sandbox.daytona.ensureDirectory",
parent: {
traceId: "0af7651916cd43dd8448eb211c80319c",
spanId: "b7ad6b7169203331",
traceFlags: 1,
},
attributes: { provider: "daytona" },
startTimeMs,
endTimeMs,
});
const finished = exporter.getFinishedSpans();
expect(finished).toHaveLength(1);
const span = finished[0]!;
expect(span.name).toBe("sandbox.daytona.ensureDirectory");
expect(Math.round(hrTimeToMs(span.startTime as [number, number]))).toBe(startTimeMs);
expect(Math.round(hrTimeToMs(span.endTime as [number, number]))).toBe(endTimeMs);
// The native width equals the true wall-clock difference, not near zero.
expect(Math.round(hrTimeToMs(span.duration as [number, number]))).toBe(4500);
} finally {
api.trace.disable();
}
});
it("exports an earlier lifecycle as a separate trace linked to its observer",async()=>{
const {api,sdk}=otelSdk!;
const exporter=new sdk.InMemorySpanExporter();
const provider=new sdk.TracerProvider({spanProcessors:[new sdk.SimpleSpanProcessor({ exporter })]});
api.trace.setGlobalTracerProvider(provider);
try {
const {recordProviderPluginSpan}=await import("../instrumentation.js");
const parent={traceId:"0af7651916cd43dd8448eb211c80319c",spanId:"b7ad6b7169203331",traceFlags:1};
const end=Date.now()-100;
recordProviderPluginSpan({name:"plugin.remote.lifecycle",parent,linked:true,attributes:{},startTimeMs:end-500,endTimeMs:end});
const span=exporter.getFinishedSpans()[0]!;
expect(span.parentSpanContext).toBeUndefined();
expect(span.spanContext().traceId).not.toBe(parent.traceId);
expect(span.links[0].context).toMatchObject(parent);
expect(Math.round(hrTimeToMs(span.duration as [number,number]))).toBe(500);
} finally {api.trace.disable();}
});
it("opens and ends the span now when the timestamp pair is absent", async () => {
const { api, sdk } = otelSdk!;
const exporter = new sdk.InMemorySpanExporter();
const provider = new sdk.TracerProvider({
spanProcessors: [new sdk.SimpleSpanProcessor({ exporter })],
});
api.trace.setGlobalTracerProvider(provider);
try {
const { recordProviderPluginSpan } = await import("../instrumentation.js");
recordProviderPluginSpan({
name: "sandbox.daytona.pack",
parent: {
traceId: "0af7651916cd43dd8448eb211c80319c",
spanId: "b7ad6b7169203331",
traceFlags: 1,
},
attributes: { provider: "daytona" },
});
const finished = exporter.getFinishedSpans();
expect(finished).toHaveLength(1);
// The synchronous open-and-end path yields a near-zero native width.
expect(hrTimeToMs(finished[0]!.duration as [number, number])).toBeLessThan(1000);
} finally {
api.trace.disable();
}
});
});
it("gives a linked lifecycle an explicit root context and a host-owned observer link",async()=>{
const root={},active={};const end=vi.fn();
const startSpan=vi.fn(()=>({end,setStatus:vi.fn(),spanContext:()=>({traceId:"a".repeat(32),spanId:"b".repeat(16),traceFlags:1})}));
const setSpanContext=vi.fn(()=>active);
vi.doMock("node:module",()=>({createRequire:()=>()=>({ROOT_CONTEXT:root,context:{active:()=>active},trace:{getTracer:()=>({startSpan}),setSpanContext}})}));
try {
const {recordProviderPluginSpan}=await importFreshInstrumentation();
const parent={traceId:"0af7651916cd43dd8448eb211c80319c",spanId:"b7ad6b7169203331",traceFlags:1};
recordProviderPluginSpan({name:"plugin.remote.lifecycle",parent,linked:true,attributes:{},startTimeMs:100,endTimeMs:500});
expect(startSpan).toHaveBeenCalledWith("plugin.remote.lifecycle",{attributes:{},startTime:100,links:[{context:{...parent,isRemote:true}}]},root);
expect(setSpanContext).not.toHaveBeenCalled();expect(end).toHaveBeenCalledWith(500);
startSpan.mockClear();
recordProviderPluginSpan({name:"plugin.remote.lifecycle",parent:{...parent,traceFlags:0},linked:true,attributes:{},startTimeMs:100,endTimeMs:500});
expect(startSpan).not.toHaveBeenCalled();
} finally {vi.doUnmock("node:module");vi.resetModules();}
});