Issues

test: CI fails on node-v24.x-nsolid-v6.x for every PR, from the branch itself

nodesource/nsolid#604 · opened

on Oct 14, 2026

V8: CPU profiles startTime/endTime are 32-bit, so a profile across a wrap ends before it starts

nodesource/nsolid#592 · opened

on Oct 13, 2026

gRPC: the Command stream reconnects without backoff

nodesource/nsolid#591 · opened

on Oct 13, 2026

Core: the startup package scan blocks the main thread and re-reads each package.json

nodesource/nsolid#590 · opened

on Oct 13, 2026

gRPC: GRPC_MAX_SIZE comment says 4GB; the value is 4 MiB

nodesource/nsolid#589 · opened

on Oct 13, 2026

OTLP vendors: metrics carry no service/host/agent identity

nodesource/nsolid#588 · opened

on Oct 13, 2026

OTLP vendors: first export sends cumulative counters as one delta

nodesource/nsolid#587 · opened

on Oct 13, 2026

gRPC/StatsD JS wrappers reference native functions the bindings do not export

nodesource/nsolid#586 · opened

on Oct 13, 2026

ZMQ: a command missing version resets the negotiated protocol version to 3

nodesource/nsolid#585 · opened

on Oct 13, 2026

StatsD: send binding prepends len empty strings

nodesource/nsolid#584 · opened

on Oct 13, 2026

OTLP vendor metrics: no HTTP result check and no timeout

nodesource/nsolid#583 · opened

on Oct 13, 2026

OTLP Dynatrace: thread gauges have no thread_id, so threads collide

nodesource/nsolid#582 · opened

on Oct 13, 2026

StatsD: bucket and tags go stale on app/env/hostname/tags change

nodesource/nsolid#581 · opened

on Oct 13, 2026

StatsD: UDP retry reads one past the end of the address list

nodesource/nsolid#580 · opened

on Oct 13, 2026

ZMQ: a command missing requestId aborts the process

nodesource/nsolid#579 · opened

on Oct 13, 2026

ZMQ: exit message is invalid JSON when a profile ran at exit

nodesource/nsolid#578 · opened

on Oct 13, 2026

Windows: processes die with 0xC0000409 or hang at exit, intermittently (6.2.4)

nodesource/nsolid#577 · opened

on Oct 13, 2026

A setting that gates the `source_code` command, off by default

nodesource/nsolid#576 · opened

on Oct 13, 2026

· N|Solid 7.0

Log lines from `nsolid.logger` are exported without the active span's trace and span ids

nodesource/nsolid#575 · opened

on Oct 13, 2026

Explicit span startTime/endTime from the OTel API get the process start time added, so Date.now() lands in 2082

nodesource/nsolid#570 · opened

on Oct 9, 2026

Span events, exceptions and links are dropped by the gRPC and OTLP agents

nodesource/nsolid#569 · opened

on Oct 9, 2026

· N|Solid 7.0

agents: report the container memory limit, CPU throttling, open file descriptors, startup flags, and libc and OS release

nodesource/nsolid#565 · opened

on Oct 8, 2026

otel: export application metrics through the agent (a meter provider from nsolid.otel.register())

nodesource/nsolid#564 · opened

on Oct 8, 2026

· N|Solid 7.0

Span timestamps drift behind wall-clock time after host suspend (start computed as process start + monotonic offset)

nodesource/nsolid#555 · opened

on Sep 30, 2026

1

Inconsistent contCpuProfileInterval default (60 s native vs 30 s JS) and stale nsolid.1 / --help env var docs

nodesource/nsolid#548 · opened

on Sep 28, 2026

Navigation Menu

Repository navigation

Issues

test: CI fails on node-v24.x-nsolid-v6.x for every PR, from the branch itself

V8: CPU profiles startTime/endTime are 32-bit, so a profile across a wrap ends before it starts

gRPC: the Command stream reconnects without backoff

Core: the startup package scan blocks the main thread and re-reads each package.json

gRPC: GRPC_MAX_SIZE comment says 4GB; the value is 4 MiB

OTLP vendors: metrics carry no service/host/agent identity

OTLP vendors: first export sends cumulative counters as one delta

gRPC/StatsD JS wrappers reference native functions the bindings do not export

ZMQ: a command missing version resets the negotiated protocol version to 3

StatsD: send binding prepends len empty strings

OTLP vendor metrics: no HTTP result check and no timeout

OTLP Dynatrace: thread gauges have no thread_id, so threads collide

StatsD: bucket and tags go stale on app/env/hostname/tags change

StatsD: UDP retry reads one past the end of the address list

ZMQ: a command missing requestId aborts the process

ZMQ: exit message is invalid JSON when a profile ran at exit

Windows: processes die with 0xC0000409 or hang at exit, intermittently (6.2.4)

A setting that gates the `source_code` command, off by default

Log lines from `nsolid.logger` are exported without the active span's trace and span ids

Explicit span startTime/endTime from the OTel API get the process start time added, so Date.now() lands in 2082

Span events, exceptions and links are dropped by the gRPC and OTLP agents

agents: report the container memory limit, CPU throttling, open file descriptors, startup flags, and libc and OS release

otel: export application metrics through the agent (a meter provider from nsolid.otel.register())

Span timestamps drift behind wall-clock time after host suspend (start computed as process start + monotonic offset)

Inconsistent contCpuProfileInterval default (60 s native vs 30 s JS) and stale nsolid.1 / --help env var docs