Skip to main content

LoongSuite slop-code-bench Instrumentation

OpenTelemetry instrumentation for the slop-code-bench benchmark orchestrator.

Span Tree

ENTRY  "enter_ai_application_system"
└── CHAIN  "chain {problem_name}"
    ├── ENTRY  "enter_ai_application_system"    [checkpoint worker]
    │   └── TASK  "run_task {checkpoint_name}"
    │       └── AGENT  "invoke_agent {agent_name}"
    │           ├── STEP  "react step"          [MiniSWE only]
    │           │   └── TOOL  "execute_tool bash"
    │           └── ...
    ├── ENTRY  "enter_ai_application_system"    [checkpoint worker]
    │   └── TASK  "run_task {checkpoint_name}"
    │       └── AGENT  "invoke_agent {agent_name}"
    └── ...
LLM  "chat {model_name}"                       [Rubric Judge]

Installation

pip install loongsuite-instrumentation-slop-code

Usage

from opentelemetry.instrumentation.slop_code import SlopCodeInstrumentor

SlopCodeInstrumentor().instrument()

Metadata

Release files for loongsuite-instrumentation-slop-code 0.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for loongsuite-instrumentation-slop-code 0.9.0
File Interpreter ABI Platform Actions
loongsuite_instrumentation_slop_code-0.9.0-py3-none-any.whl Python 3 none any Details for loongsuite_instrumentation_slop_code-0.9.0-py3-none-any.whl

Release files / loongsuite_instrumentation_slop_code-0.9.0-py3-none-any.whl

Download URL loongsuite_instrumentation_slop_code-0.9.0-py3-none-any.whl
Size 19.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aff5908de2e0fb21722f7928e1d668c478e96267275d1285fb47781e17e9f459
BLAKE2b-256 checksum
How to use checksums
1927dbeb9f09a07f95931de47cca3c7d4a3763c5ebece205b3421e077400772a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.10

Security for loongsuite-instrumentation-slop-code 0.9.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page