Conversation
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/db561b01-f70a-4723-bd46-068e4b56ae8f Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/db561b01-f70a-4723-bd46-068e4b56ae8f Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/db561b01-f70a-4723-bd46-068e4b56ae8f Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
|
@copilot The tests fail in python 3.24 with |
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/55438f91-bd29-47a8-8cd2-157c5e0ee709 Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Fixed in 8b172a5. The Python 3.14 Ray failure was coming from Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
Benchmark comparison for |
|
Benchmark comparison for |
|
Benchmark comparison for |
|
@copilot find out why the following integration test is failing and fix |
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/39e4383c-94e6-453d-9964-8974046c769d Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/39e4383c-94e6-453d-9964-8974046c769d Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/39e4383c-94e6-453d-9964-8974046c769d Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Agent-Logs-Url: https://github.com/plugboard-dev/plugboard/sessions/39e4383c-94e6-453d-9964-8974046c769d Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Fixed in 0b6cd56. The failure was caused by the test calling Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
Benchmark comparison for |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Adds Python 3.14 to the supported/runtime-tested versions for Plugboard and aligns dependency floors with the releases needed for working 3.14 compatibility across the project and Ray-backed tests. CI and release workflows are updated so packaging and validation run against the expanded version set, and the Ray resource integration test is updated to avoid depending on the dashboard HTTP API in CI.
Changes
Project metadata
requires-python >=3.12,<4.0range and updates dependency floors needed for 3.14:msgspec[yaml] >= 0.20pydantic >= 2.13.1ray[tune] >= 2.55.0CI / release pipelines
Lockfile refresh
uv.lockfor the new dependency constraints and trims packages that were only pulled in byray[default].Python 3.14 Ray compatibility
ray 2.55.0resolving against an olderpydantic.v1compatibility layer.plugboardandplugboard-schemasso Ray state/dashboard imports andray.init()work correctly on Python 3.14.Test harness compatibility
asyncio.events.BaseDefaultEventLoopPolicyannotation intests/conftest.pywith a Python-3.14-safe event loop policy fixture.tests/integration/test_component_resources.pyto verify Ray actor creation and resource reservation using Ray core APIs instead ofray.util.state.list_actors(), avoiding flaky failures when the dashboard API on port8265is unavailable in CI.Warning
Ray 2.55.0 Python 3.14 support depends on resolving to a new enough
pydantic.v1compatibility layer. This PR raises the Pydantic floor accordingly to avoid Ray startup and state API failures on Python 3.14.