54c8fda65f
* Fix tenant context propagation for alteration jobs Capture the current tenant when dispatching a background alteration job and restore it while executing the queued callback. Add regression coverage verifying that the dispatch-time tenant is used and the worker's previous tenant context is restored. Fixes #7961 * test(alterations): cover tenant restore on failure and concurrent tenant isolation Add coverage for the spec lines that were previously untested: the worker's tenant context is restored after execution even when the job runner throws, and concurrent jobs dispatched under different tenants do not exchange tenant context. Extract the shared service provider / job queue / recording runner arrange logic into constructor-initialized fields so the three tests stay DRY. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * test(alterations): cover default-tenant dispatch and share dispatcher test setup Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| component | ||
| integration | ||
| performance | ||
| TlsSmoke | ||
| unit | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||