Skip to content

[release-0.7] feat: retract executor attributes when cached data is evicted - #634

Merged
k82cn merged 1 commit into
xflops:release-0.7from
k82cn:backport/pr-633-release-0.7
Oct 27, 2026
Merged

k82cn merged 1 commit into
xflops:release-0.7from
k82cn:backport/pr-633-release-0.7

Conversation

@k82cn

@k82cn k82cn commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Cherry-picks #633 onto release-0.7.

This backport contains only commit 62d0803b (the release-branch cherry-pick of 6c34e794), made with git cherry-pick -x. It applied without conflicts, and its patch-id matches the source commit.

What it is: ExecutorAttributes carries publish (field 1, renamed from attr) and retract (field 2), so a service can withdraw keys when cached data is evicted or cleared; the session manager validates the update and applies it atomically; the Rust and Python SDKs get unpublish (fixes #632).

Compatibility, as in #633: backward compatibility is not kept. The manager and the SDKs must be upgraded together, because an older manager ignores retract and keeps the keys. This is a wire change that is new in v0.7.0-rc2 relative to v0.7.0-rc1.

Validation, on the release-0.7 base:

  • cargo test: flame-session-manager (296 passed), flame-rs lib (61), flame-executor-manager (163) and common (293 and 2) pass.
  • cargo clippy --workspace --all-targets -- -D warnings and cargo fmt --check pass.
  • Python SDK: 417 tests pass and ruff check is clean.
  • Not run: flame-rs benchmark_test, which needs a live session manager (it fails here with a connection error, as the description of feat: retract executor attributes when cached data is evicted #633 says), and the end-to-end jobs, which CI runs.

It is not yet in docs/releases/v0.7.0-rc2.md (#624), which has to list it and the compatibility note if this is included in rc2.

@k82cn
k82cn merged commit 410cc94 into xflops:release-0.7 Oct 27, 2026
15 of 16 checks passed
@k82cn
k82cn deleted the backport/pr-633-release-0.7 branch October 27, 2026 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant