Skip to content
CI

Feature: Disable rich logging #1022

Sign in to view logs

Feature: Disable rich logging

Feature: Disable rich logging #1022

Triggered via pull request July 5, 2025 06:26
@kozlov721kozlov721
opened #339
feature/disable-rich
Status Success
Total duration 10m 30s
Artifacts 1

ci.yaml

on: pull_request
pre-commit
31s
pre-commit
auto-assigner
3s
auto-assigner
labeler
5s
labeler
update-base-report
0s
update-base-report
Matrix: check-requirements
type-check
1m 30s
type-check
semgrep
27s
semgrep
docs
15s
docs
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Semgrep Issue: examples/utils/torch_utils.py#L90
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: examples/utils/torch_utils.py#L89
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: examples/utils/torch_utils.py#L82
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX
Semgrep Issue: examples/utils/torch_utils.py#L81
Functions reliant on pickle can result in arbitrary code execution. Consider loading from `state_dict`, using fickling, or switching to a safer serialization method like ONNX

Artifacts

Produced during runtime
Name Size Digest
coverage Expired
14.8 KB
sha256:1cd09181b04aaffd6767554f63c675c3f6c9ccb7a1e35f838e72d7051dc3e6af