fix(ci_visibility): set up Test Optimization logging before pytest log capture #13030

vitor-de-araujo · 2025-04-02T15:58:07Z

We have a recurring problem where emitting logs at the end of a pytest test session results in errors like:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/logging/__init__.py", line 1103, in emit
    stream.write(msg + self.terminator)
ValueError: I/O operation on closed file.

This happens because our plugin calls take_over_logger_stream_handler(), which calls logging.StreamHandler(), which defaults to using sys.stderr as its output stream, but by the time we call it, pytest's pytest_load_initial_conftests hook from capture.py has already executed and replaced sys.stderr with a FileIO buffer that is closed by the end of the test session, so we grab a reference to this internal FileIO buffer instead of the actual sys.stderr. This PR makes our own pytest_load_initial_conftests hook run earlier than pytest's capture.py one.

Additionally, this fixes take_over_logger_stream_handler() to copy the handler list before calling removeHandler(), as this mutates the list we are iterating through.

One user-visible side effect of this is that now we always print these logs at the beginning of the test session, regardless of whether pytest -s is used:

[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:294 Service: vitor-test (env: some-env)
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:295 Requests mode: agentless
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:296 Git metadata upload enabled: True
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:297 API-provided settings: coverage collection: False
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:298 API-provided settings: Intelligent Test Runner: False, test skipping: False
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:303 API-provided settings: Early Flake Detection enabled: True
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:307 API-provided settings: Auto Test Retries enabled: True
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:308 Detected configurations: {'os.architecture': 'x86_64', 'os.platform': 'Linux', 'os.version': '6.5.0-1027-oem', 'runtime.name': 'CPython', 'runtime.version': '3.10.14'}
[Datadog CI Visibility] WARNING  ddtrace.internal.ci_visibility.recorder:recorder.py:313 CODEOWNERS file is not available
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:628 Unique tests fetched for Early Flake Detection: 34
[Datadog CI Visibility] INFO     ddtrace.internal.ci_visibility.recorder:recorder.py:576 Final settings: coverage collection: False, test skipping: False, Early Flake Detection: True, Auto Test Retries: True, Flaky Test Management: True

Whether this is a bug or a feature is up to discussion. Previously we only printed this if pytest was called with -s, more by accident than by design.

The way I managed to reproduce it was by raising an exception right after tracer shutdown in CIVisibility._stop_service():

    def _stop_service(self) -> None:
        ...
        try:
            self.tracer.shutdown()
            raise Exception("ꙮ")  # <--- added here
        except Exception:
            log.warning("Failed to shutdown tracer", exc_info=True)

Checklist

PR author has checked that all the criteria below are met
The PR description includes an overview of the change
The PR description articulates the motivation for the change
The change includes tests OR the PR description describes a testing strategy
The PR description notes risks associated with the change, if any
Newly-added code is easy to change
The change follows the library release note guidelines
The change includes or references documentation updates if necessary
Backport labels are set (if applicable)

Reviewer Checklist

Reviewer has checked that all the criteria below are met
Title is accurate
All changes are related to the pull request's stated goal
Avoids breaking API changes
Testing strategy adequately addresses listed risks
Newly-added code is easy to change
Release note makes sense to a user of the library
If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
Backport labels are set in a manner that is consistent with the release branch maintenance policy

…g capture

github-actions · 2025-04-02T15:58:48Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries

…raujo/SDTEST-323/io-operation-closed-file

github-actions · 2025-04-02T16:17:09Z

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 230 ± 4 ms.

The average import time from base is: 232 ± 4 ms.

The import time difference between this PR and base is: -2.1 ± 0.2 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 2.008 ms (0.87%)

ddtrace.bootstrap.sitecustomize 1.344 ms (0.58%)

ddtrace.bootstrap.preload 1.344 ms (0.58%)

ddtrace.internal.products 1.344 ms (0.58%)

ddtrace.internal.remoteconfig.client 0.645 ms (0.28%)

ddtrace 0.664 ms (0.29%)

rkomorn · 2025-04-02T16:49:22Z

Finally! Yet another of my crimes is will be avenged. 😍

rkomorn · 2025-04-02T16:51:44Z

Whether this is a bug or a feature is up to discussion. Previously we only printed this if pytest was called with -s, more by accident than by design.

This is a feature. This output was missing since the migration to the the v2 plugin.

pr-commenter · 2025-04-02T16:56:09Z

Benchmarks

Benchmark execution time: 2025-04-04 09:44:51

Comparing candidate commit c53aa66 in PR branch vitor-de-araujo/SDTEST-323/io-operation-closed-file with baseline commit 25684ea in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 490 metrics, 2 unstable metrics.

…raujo/SDTEST-323/io-operation-closed-file

github-actions · 2025-04-03T09:06:23Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

tests/contrib/pytest/test_pytest.py

github-actions · 2025-04-03T09:08:35Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

github-actions · 2025-04-03T09:08:48Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries

This reverts commit 713155e.

github-actions · 2025-04-03T10:30:20Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

github-actions · 2025-04-03T12:25:27Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

github-actions · 2025-04-03T13:39:20Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

github-actions · 2025-04-03T13:49:17Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries
tests/contrib/pytest/test_pytest.py                                     @DataDog/ci-app-libraries

github-actions · 2025-04-03T14:13:59Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries

…ed-file

github-actions · 2025-04-03T14:14:54Z

CODEOWNERS have been resolved as:

releasenotes/notes/ci_visibility-fix-io-operation-closed-file-1e1089eabd5296ce.yaml  @DataDog/apm-python
ddtrace/contrib/internal/pytest/_plugin_v2.py                           @DataDog/ci-app-libraries
ddtrace/internal/ci_visibility/utils.py                                 @DataDog/ci-app-libraries

…ed-file

…g capture (#13030) We have a recurring problem where emitting logs at the end of a pytest test session results in errors like: ``` Traceback (most recent call last): File "/usr/local/lib/python3.10/logging/__init__.py", line 1103, in emit stream.write(msg + self.terminator) ValueError: I/O operation on closed file. ``` This happens because our plugin calls `take_over_logger_stream_handler()`, which calls `logging.StreamHandler()`, which defaults to using `sys.stderr` as its output stream, but by the time we call it, pytest's [`pytest_load_initial_conftests` hook from `capture.py`](https://github.com/pytest-dev/pytest/blob/8.3.x/src/_pytest/capture.py#L155) has already executed and replaced `sys.stderr` with a `FileIO` buffer that is closed by the end of the test session, so we grab a reference to this internal `FileIO` buffer instead of the actual `sys.stderr`. This PR makes our own `pytest_load_initial_conftests` hook run earlier than pytest's `capture.py` one. Additionally, this fixes `take_over_logger_stream_handler()` to copy the handler list before calling `removeHandler()`, as this mutates the list we are iterating through. One user-visible side effect of this is that now we always print these logs at the beginning of the test session, regardless of whether `pytest -s` is used: ``` [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:294 Service: vitor-test (env: some-env) [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:295 Requests mode: agentless [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:296 Git metadata upload enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:297 API-provided settings: coverage collection: False [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:298 API-provided settings: Intelligent Test Runner: False, test skipping: False [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:303 API-provided settings: Early Flake Detection enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:307 API-provided settings: Auto Test Retries enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:308 Detected configurations: {'os.architecture': 'x86_64', 'os.platform': 'Linux', 'os.version': '6.5.0-1027-oem', 'runtime.name': 'CPython', 'runtime.version': '3.10.14'} [Datadog CI Visibility] WARNING ddtrace.internal.ci_visibility.recorder:recorder.py:313 CODEOWNERS file is not available [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:628 Unique tests fetched for Early Flake Detection: 34 [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:576 Final settings: coverage collection: False, test skipping: False, Early Flake Detection: True, Auto Test Retries: True, Flaky Test Management: True ``` Whether this is a bug or a feature is up to discussion. Previously we only printed this if `pytest` was called with `-s`, more by accident than by design. The way I managed to reproduce it was by raising an exception right after tracer shutdown in `CIVisibility._stop_service()`: ``` def _stop_service(self) -> None: ... try: self.tracer.shutdown() raise Exception("ꙮ") # <--- added here except Exception: log.warning("Failed to shutdown tracer", exc_info=True) ``` ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) (cherry picked from commit 2db08ec)

…g capture (#13030) We have a recurring problem where emitting logs at the end of a pytest test session results in errors like: ``` Traceback (most recent call last): File "/usr/local/lib/python3.10/logging/__init__.py", line 1103, in emit stream.write(msg + self.terminator) ValueError: I/O operation on closed file. ``` This happens because our plugin calls `take_over_logger_stream_handler()`, which calls `logging.StreamHandler()`, which defaults to using `sys.stderr` as its output stream, but by the time we call it, pytest's [`pytest_load_initial_conftests` hook from `capture.py`](https://github.com/pytest-dev/pytest/blob/8.3.x/src/_pytest/capture.py#L155) has already executed and replaced `sys.stderr` with a `FileIO` buffer that is closed by the end of the test session, so we grab a reference to this internal `FileIO` buffer instead of the actual `sys.stderr`. This PR makes our own `pytest_load_initial_conftests` hook run earlier than pytest's `capture.py` one. Additionally, this fixes `take_over_logger_stream_handler()` to copy the handler list before calling `removeHandler()`, as this mutates the list we are iterating through. One user-visible side effect of this is that now we always print these logs at the beginning of the test session, regardless of whether `pytest -s` is used: ``` [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:294 Service: vitor-test (env: some-env) [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:295 Requests mode: agentless [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:296 Git metadata upload enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:297 API-provided settings: coverage collection: False [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:298 API-provided settings: Intelligent Test Runner: False, test skipping: False [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:303 API-provided settings: Early Flake Detection enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:307 API-provided settings: Auto Test Retries enabled: True [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:308 Detected configurations: {'os.architecture': 'x86_64', 'os.platform': 'Linux', 'os.version': '6.5.0-1027-oem', 'runtime.name': 'CPython', 'runtime.version': '3.10.14'} [Datadog CI Visibility] WARNING ddtrace.internal.ci_visibility.recorder:recorder.py:313 CODEOWNERS file is not available [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:628 Unique tests fetched for Early Flake Detection: 34 [Datadog CI Visibility] INFO ddtrace.internal.ci_visibility.recorder:recorder.py:576 Final settings: coverage collection: False, test skipping: False, Early Flake Detection: True, Auto Test Retries: True, Flaky Test Management: True ``` Whether this is a bug or a feature is up to discussion. Previously we only printed this if `pytest` was called with `-s`, more by accident than by design. The way I managed to reproduce it was by raising an exception right after tracer shutdown in `CIVisibility._stop_service()`: ``` def _stop_service(self) -> None: ... try: self.tracer.shutdown() raise Exception("ꙮ") # <--- added here except Exception: log.warning("Failed to shutdown tracer", exc_info=True) ``` ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

fix(ci_visibility): set up Test Optimization logging before pytest lo…

e97cbb1

…g capture

vitor-de-araujo added 2 commits April 2, 2025 16:01

Merge branch 'main' of github.com:DataDog/dd-trace-py into vitor-de-a…

5451c99

…raujo/SDTEST-323/io-operation-closed-file

release note

8f3b921

vitor-de-araujo marked this pull request as ready for review April 3, 2025 09:04

vitor-de-araujo requested review from a team as code owners April 3, 2025 09:04

vitor-de-araujo requested review from ManuelPalenzuelaDD, gnufede and lievan April 3, 2025 09:04

vitor-de-araujo added 3 commits April 3, 2025 09:05

release note oopsie

7a1526e

noooo

713155e

Merge branch 'main' of github.com:DataDog/dd-trace-py into vitor-de-a…

0395a17

…raujo/SDTEST-323/io-operation-closed-file

datadog-datadog-prod-us1 bot reviewed Apr 3, 2025

View reviewed changes

tests/contrib/pytest/test_pytest.py Outdated Show resolved Hide resolved

unused import

b82d642

vitor-de-araujo added [DEPRECATED] backport 3.1 [DEPRECATED] backport 3.2 backport 3.3 labels Apr 3, 2025

vitor-de-araujo added 2 commits April 3, 2025 09:35

Revert "noooo"

7043db1

This reverts commit 713155e.

tests?

8acdd84

vitor-de-araujo added 2 commits April 3, 2025 11:33

extra docstring

0278d64

is this the problem?

2aebfa5

vitor-de-araujo added 2 commits April 3, 2025 12:44

no it isn't

c5890c5

attempt to test, take ∞ 🎬

a332b13

a

ba320c8

things as they were

438ecc9

Merge branch 'main' into vitor-de-araujo/SDTEST-323/io-operation-clos…

5282545

…ed-file

emmettbutler approved these changes Apr 3, 2025

View reviewed changes

vitor-de-araujo added 2 commits April 3, 2025 17:00

Merge branch 'main' into vitor-de-araujo/SDTEST-323/io-operation-clos…

e4428b5

…ed-file

Merge branch 'main' into vitor-de-araujo/SDTEST-323/io-operation-clos…

c53aa66

…ed-file

gnufede approved these changes Apr 4, 2025

View reviewed changes

vitor-de-araujo merged commit 2db08ec into main Apr 4, 2025
311 of 312 checks passed

vitor-de-araujo deleted the vitor-de-araujo/SDTEST-323/io-operation-closed-file branch April 4, 2025 10:09

github-actions bot mentioned this pull request Apr 4, 2025

fix(ci_visibility): set up Test Optimization logging before pytest log capture [backport 3.1] #13063

Closed

2 tasks

github-actions bot mentioned this pull request Apr 4, 2025

fix(ci_visibility): set up Test Optimization logging before pytest log capture [backport 3.2] #13064

Closed

2 tasks

github-actions bot mentioned this pull request Apr 4, 2025

fix(ci_visibility): set up Test Optimization logging before pytest log capture [backport 3.3] #13065

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(ci_visibility): set up Test Optimization logging before pytest log capture #13030

fix(ci_visibility): set up Test Optimization logging before pytest log capture #13030

Uh oh!

vitor-de-araujo commented Apr 2, 2025 •

edited by gnufede

Loading

Uh oh!

github-actions bot commented Apr 2, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Apr 2, 2025 •

edited

Loading

Uh oh!

rkomorn commented Apr 2, 2025

Uh oh!

rkomorn commented Apr 2, 2025

Uh oh!

pr-commenter bot commented Apr 2, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

Uh oh!

Uh oh!

fix(ci_visibility): set up Test Optimization logging before pytest log capture #13030

fix(ci_visibility): set up Test Optimization logging before pytest log capture #13030

Uh oh!

Conversation

vitor-de-araujo commented Apr 2, 2025 • edited by gnufede Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Checklist

Reviewer Checklist

Uh oh!

github-actions bot commented Apr 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Apr 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bootstrap import analysis

Summary

Import time breakdown

Uh oh!

rkomorn commented Apr 2, 2025

Uh oh!

rkomorn commented Apr 2, 2025

Uh oh!

pr-commenter bot commented Apr 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

github-actions bot commented Apr 3, 2025

Uh oh!

Uh oh!

Uh oh!

vitor-de-araujo commented Apr 2, 2025 •

edited by gnufede

Loading

github-actions bot commented Apr 2, 2025 •

edited

Loading

github-actions bot commented Apr 2, 2025 •

edited

Loading

pr-commenter bot commented Apr 2, 2025 •

edited

Loading