Repository navigation
feat: add shared records and isolated load execution - #118
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 1833 |
| Duplication | 33 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



LoadDensity now supports local native HTTP runs through Python, action files, CLI and desktop engine selection. Package/command imports defer Locust, each HTTP user keeps isolated parameters and sessions, and the desktop runs engines in fresh interpreters with explicit Start/Stop and retained results. Locust masters can opt into provenance-preserving canonical record aggregation alongside native worker health and capacity recovery.
Validation: coordinated full suite 1605 passed, 14 optional skips, with four existing warnings; changed Python Ruff E/F/W/C90/I and whitespace checks pass. Seven rebuilt installed-wheel CLI/report/SLA/dashboard/MCP/native/XML smoke tests pass against published ActionCore 0.0.2. XML entity expansion failed its regression first and is now rejected using the existing required defusedxml dependency. The final annotation-only follow-up passes 32 native import/parameter tests and independent review. Codacy and SonarCloud both pass on head 7d7b090; their APIs report completed analysis with zero new Codacy issues and zero unresolved Sonar issues. Reviewed false positives have exact-rule, site-specific annotations with trust-boundary explanations and recorded issue IDs; no tools, patterns, or files were globally disabled. Prior runtime verification includes the installed-wheel desktop completion/cancellation/active-close probe with Locust prepatched. Sphinx dummy parsing succeeds with configuration/autosummary warnings. Final-head Actions run 37100889307 passed the complete matrix; PR checks show 62 passed and one intentionally skipped.
Canonical APIs remain opt-in pending the coordinated ActionCore release (ActionCore PR 1, APITestka PR 146). Native I/O after selecting Locust requires a fresh interpreter, provided by bench and the desktop supervisor. Full native exporter/non-HTTP/master-worker parity, embedded scheduler switching, dashboard run-state views and the unified functional/load/synthetic script remain in progress.md. Record delivery uses bounded in-memory queues; it does not provide finite-work leases, HTTP replay, durable recovery or session migration.