activeagents-telemetry 0.3.1 → 0.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +36 -0
- data/lib/activeagents/telemetry/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d5c22b8b7c041a5278a6c6c2f948a1820ea54a099d2f4bac96445099da53ae1e
|
|
4
|
+
data.tar.gz: 9d1bd15b970d51f40a37a6f252f7254d9527ac6af075d07290dfcebc92d78a85
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: add8d0851e06f9930eb6e10ea6e26e23bbb5f2fc1b90f76a185746b3c0a786868273249d33efd078ab756baf796b932bac797cec340f6ddbdb7adb7ef3d8fd07
|
|
7
|
+
data.tar.gz: fb490fc4977187a2160851693b8a13fcf5e6330b601911cc96a9354f080f80ed84deaf5b0662558478ecf4335f2b36d603c27a4310d237880348e60ce4650f0d
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,41 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.3.2] - 2026-09-22
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- `RubyLLM.with_agent` scopes compose. Inside an enclosing scope, a nested
|
|
8
|
+
call merges its `attributes` onto the enclosing ones (a nested key wins on
|
|
9
|
+
collision) and inherits `on_trace` and `synchronous` unless it passes its
|
|
10
|
+
own. `synchronous:` now defaults to `nil`, meaning "inherit, else false",
|
|
11
|
+
so an explicit `synchronous: false` still overrides an inherited `true`.
|
|
12
|
+
Without `pin`, a nested scope replaces `name` and `action` as before.
|
|
13
|
+
- `RubyLLM.with_agent` takes `pin: true`. A pinned scope owns the turn's
|
|
14
|
+
identity: while it is active a nested `with_agent` may only add
|
|
15
|
+
attributes, and the pinned scope's `name`, `action`, `on_trace` and
|
|
16
|
+
`synchronous` stay in force whatever the nested call passes. The previous
|
|
17
|
+
scope is still restored exactly on exit, including when the block raises.
|
|
18
|
+
- `RubyLLM.correlation_tracer(synchronous: true, pin: true)` returns the
|
|
19
|
+
`tracer:` lambda `ActiveAgent::Evals::Correlation` (activeagent >= 1.6.3)
|
|
20
|
+
expects, `->(name, action:, attributes:, on_trace:, &block)`, opening a
|
|
21
|
+
pinned, synchronous `with_agent` scope with those arguments. activeagent
|
|
22
|
+
is not a dependency; only the lambda's signature is shared.
|
|
23
|
+
|
|
24
|
+
### Fixed
|
|
25
|
+
|
|
26
|
+
- A `with_agent` scope opened inside another one replaced it outright, so
|
|
27
|
+
when an evaluation replay wrapped the code under test in a scope carrying
|
|
28
|
+
`eval.*` attributes, an `on_trace` callback and `synchronous: true`, and
|
|
29
|
+
that code opened its own scope around the actual `chat.ask`, the trace
|
|
30
|
+
lost the evaluation attributes, the callback never received the trace id
|
|
31
|
+
and delivery went back to the background thread. Nested scopes now
|
|
32
|
+
compose as described above, and an evaluation pins its scope so the inner
|
|
33
|
+
one cannot detach the trace from it.
|
|
34
|
+
|
|
35
|
+
The core gem is republished at 0.3.2 with no changes, so the two gems stay on
|
|
36
|
+
one version.
|
|
37
|
+
|
|
38
|
+
|
|
3
39
|
## [0.3.1] - 2026-09-20
|
|
4
40
|
|
|
5
41
|
### Fixed
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: activeagents-telemetry
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.3.
|
|
4
|
+
version: 0.3.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- ActiveAgents
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-
|
|
11
|
+
date: 2026-10-07 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
13
|
description: |
|
|
14
14
|
The wire format, configuration, and delivery layer behind ActiveAgents
|