Skip to content

chore: allow logging unredacted messages MCP-103 #1405

chore: allow logging unredacted messages MCP-103

chore: allow logging unredacted messages MCP-103 #1405

Triggered via pull request August 4, 2025 13:05
Status Failure
Total duration 7m 26s
Artifacts 3

code_health.yaml

on: pull_request
Matrix: Run MongoDB tests
Run Atlas tests
2m 23s
Run Atlas tests
Report Coverage
36s
Report Coverage
Fit to window
Zoom out
Zoom in

Annotations

13 errors, 19 warnings, and 3 notices
Run MongoDB tests (macos-latest)
Process completed with exit code 1.
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should timeout if machine ID resolution takes too long: tests/unit/telemetry.test.ts#L280
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002007 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002007, }, - "telemetry", - "Device ID retrieval timed out", + "message": "Device ID retrieval timed out", + "noRedaction": true, + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:280:39
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should handle machine ID resolution failure: tests/unit/telemetry.test.ts#L253
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002006 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002006, }, - "telemetry", - "Error: Failed to get device ID", + "message": "Error: Failed to get device ID", + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:253:39
Run MongoDB tests (ubuntu-latest)
Process completed with exit code 1.
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should timeout if machine ID resolution takes too long: tests/unit/telemetry.test.ts#L280
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002007 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002007, }, - "telemetry", - "Device ID retrieval timed out", + "message": "Device ID retrieval timed out", + "noRedaction": true, + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:280:39
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should handle machine ID resolution failure: tests/unit/telemetry.test.ts#L253
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002006 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002006, }, - "telemetry", - "Error: Failed to get device ID", + "message": "Error: Failed to get device ID", + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:253:39
Run Atlas tests
Process completed with exit code 1.
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should timeout if machine ID resolution takes too long: tests/unit/telemetry.test.ts#L280
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002007 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002007, }, - "telemetry", - "Device ID retrieval timed out", + "message": "Device ID retrieval timed out", + "noRedaction": true, + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:280:39
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should handle machine ID resolution failure: tests/unit/telemetry.test.ts#L253
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002006 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002006, }, - "telemetry", - "Error: Failed to get device ID", + "message": "Error: Failed to get device ID", + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:253:39
Run MongoDB tests (windows-latest)
Process completed with exit code 1.
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should timeout if machine ID resolution takes too long: tests/unit/telemetry.test.ts#L280
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002007 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002007, }, - "telemetry", - "Device ID retrieval timed out", + "message": "Device ID retrieval timed out", + "noRedaction": true, + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:280:39
tests/unit/telemetry.test.ts > Telemetry > sending events > when telemetry is enabled > machine ID resolution > should handle machine ID resolution failure: tests/unit/telemetry.test.ts#L253
AssertionError: expected "debug" to be called with arguments: [ { __value: 1002006 }, …(2) ] Received: 1st debug call: [ { + "context": "telemetry", + "id": { "__value": 1002006, }, - "telemetry", - "Error: Failed to get device ID", + "message": "Error: Failed to get device ID", + }, ] Number of calls: 1 ❯ tests/unit/telemetry.test.ts:253:39
Report Coverage
Unable to download artifact(s): Artifact not found for name: test-results Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Run MongoDB tests (macos-latest)
No ALTQ support in kernel ALTQ related functions disabled pf enabled
Run MongoDB tests (macos-latest)
pfctl: Use of -f option, could result in flushing of rules present in the main ruleset added by the system at startup. See /etc/pf.conf for further details. No ALTQ support in kernel ALTQ related functions disabled
Run MongoDB tests (macos-latest)
YES (0)
Run MongoDB tests (macos-latest)
[notice] A new release of pip is available: 25.1.1 -> 25.2 [notice] To update, run: /Users/mitmproxyuser/venv/bin/python3.13 -m pip install --upgrade pip
Run MongoDB tests (macos-latest)
2025-08-04 13:05:15.967 sysadminctl[1090:6487] Creating home directory at /Users/mitmproxyuser
Run MongoDB tests (macos-latest)
2025-08-04 13:05:15.924 sysadminctl[1090:6487] Assigning UID: 502 GID: 20
Run MongoDB tests (macos-latest)
2025-08-04 13:05:15.730 sysadminctl[1090:6487] Creating user record…
Run MongoDB tests (macos-latest)
IOServiceMatchingfailed for: AppleM2ScalerCSCDriver
Run MongoDB tests (macos-latest)
2025-08-04 13:05:15.325 sysadminctl[1090:6487] ---------------------------- 2025-08-04 13:05:15.325 sysadminctl[1090:6487] No clear text password or interactive option was specified (adduser, change/reset password will not allow user to use FDE) ! 2025-08-04 13:05:15.325 sysadminctl[1090:6487] ----------------------------
Run MongoDB tests (ubuntu-latest)
No files were found with the provided path: coverage/lcov.info. No artifacts will be uploaded.
Run MongoDB tests (ubuntu-latest)
1 added, 0 removed; done.
Run MongoDB tests (ubuntu-latest)
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
Run MongoDB tests (ubuntu-latest)
Updating certificates in /etc/ssl/certs...
Run MongoDB tests (ubuntu-latest)
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Run Atlas tests
No files were found with the provided path: coverage/lcov.info. No artifacts will be uploaded.
Run Atlas tests
1 added, 0 removed; done.
Run Atlas tests
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
Run Atlas tests
Updating certificates in /etc/ssl/certs...
Run Atlas tests
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Run MongoDB tests (macos-latest)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
Run MongoDB tests (macos-latest)
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
Run MongoDB tests (windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
run-atlas-tests-permissions-c3161698577b190a24206ef7b2d3e323
140 Bytes
sha256:7a3ec814d4e9c41f69e5c8eb5f565c20db40070930a686ffb2752b441f60df98
run-tests-permissions-eb0b5977b38bc0093281edeafec63400
140 Bytes
sha256:ec0dd0edc55f46bc70614ebd2ac29fbef2c39460d49c471e4cc42e6ff4b755e5
run-tests-permissions-f212f8bffbf80ff0c6cac47a852d3b3e
140 Bytes
sha256:0fb1d4c349ea8f57ee5b665de3602e9af08e0443339541954fe7a8a36d8e55be