b60439152b
- harness/es.py: append-only event store + проекции (образец — кооп-портал) - harness/levels.py: уровни 1с/1м/1ч/1д, контекст ∝ масштабу - harness/scheduler.py: уровневые потоки, идемпотентные тики, absorbed-стабы - harness/isolated_runner.py + _llm_worker.py: LLM-тик в сабпроцессе (глобальный asyncio-рантайм Strands не переживает 2+ create_harness) - cli.py: init/task/tasks/status/events + requeue (написан самим минутным агентом) - 9router: отдельный ключ sk-simbiot, модель auto (glm-5.3 первым)
32 lines
1.2 KiB
Python
32 lines
1.2 KiB
Python
# Copyright The OpenTelemetry Authors
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
from typing import Final
|
|
|
|
EXCEPTION_ESCAPED: Final = "exception.escaped"
|
|
"""
|
|
Deprecated: It's no longer recommended to record exceptions that are handled and do not escape the scope of a span.
|
|
"""
|
|
|
|
EXCEPTION_MESSAGE: Final = "exception.message"
|
|
"""
|
|
The exception message.
|
|
Note: > [!WARNING]
|
|
>
|
|
> This attribute may contain sensitive information.
|
|
"""
|
|
|
|
EXCEPTION_STACKTRACE: Final = "exception.stacktrace"
|
|
"""
|
|
A stacktrace as a string in the natural representation for the language runtime. The representation is to be determined and documented by each language SIG.
|
|
"""
|
|
|
|
EXCEPTION_TYPE: Final = "exception.type"
|
|
"""
|
|
The type of the exception (its fully-qualified class name, if applicable). The dynamic type of the exception should be preferred over the static type in languages that support it.
|
|
Note: If the recorded exception type is a wrapper that is not meaningful for
|
|
failure classification, instrumentation MAY use the type of the inner
|
|
exception instead. For example, in Go, errors created with `fmt.Errorf`
|
|
using `%w` MAY be unwrapped when the wrapper type does not help
|
|
classify the failure.
|
|
"""
|