Repository navigation
test(codeapi): qualify independent REST clients and bounded workloads - #46
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Direct CodeAPI qualification currently depends on ad hoc probes. This adds a maintained REST client that runs independently of LibreChat, checks runtime output and exact file bytes, preserves owned references for cleanup, and stops admission on stale observations, unexpected responses or exhausted budgets.
The client offers contract qualification, finite sequential/burst dispatch phases, and an opt-in resource/stability mode. The resource mode verifies deterministic CPU results and bounded memory integrity, then runs sixteen paced checks over ten minutes. It rejects missed slots or a window that cannot fit, requires a fresh terminal observation, and preserves the existing request, runtime, concurrency and cleanup limits. It does not retry work. The capability guide explains optional bridge, workspace, PTC, hosted-app and extraction prerequisites.
Validation: fourteen offline cases pass in the pinned Node container, including deadline refusal, corrupt output, failure during the final idle interval and owned cleanup. Generated Python and Node workload programs also pass bounded real-runtime checks. The existing source-only CI runs without cluster credentials. Independent final source review and its focused correction pass are complete; Hosted source CI passed for the final branch. The progress checkpoint changes documentation only. The optional scoped scanner could not retrieve its rules; that scan remains unavailable. Operational measurements stay in private receipts.
This remains a draft and changes no service configuration. A periodic bounded workload does not establish sustained capacity, maximum memory, ingress, new-issuer onboarding, fairness, leak freedom or fault-recovery guarantees. Merge and production rollout retain separate authority.
Execution plan · Capability guide