Repository navigation
Conversation
This branch has not been deployed
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.
Endpoint.runandrun_syncwrap an already formed request again when itsinputis an empty object. For example,{"input": {}, "webhook": "...", "policy": {...}}becomes nested under a secondinput, so the handler receives the envelope and the request loses its top-level controls.Check for the presence of the
inputkey when deciding whether to wrap raw handler data. This preserves empty input envelopes as well as existing nonempty envelopes; bare input dictionaries still wrap once. The two methods' docstrings now describe this existing dual input contract. The async endpoint API is unchanged.The send-requests documentation describes
inputand top-levelwebhook/policy. Current CLI tests already accept an empty object as handler input.Validation on macOS arm64 / Python 3.10.22:
The stock remote E2E exclusion was preserved. Full local tests used fake credentials and a test-process guard rejecting unexpected non-loopback connections. No live Runpod service, GPU, worker deployment or cluster was used. Python 3.11–3.14 and the Linux CI platform were not run locally.
AI assistance was used for implementation, regression testing and independent automated local review.
Maintenance integrates current main
fd16b99through a normal merge commit, without rewriting history. Main already includes #667's fix for the old volume-cache test fixture; that fix is not duplicated here. The PR's net change remains the same two files (88 additions, four deletions). The new-head hosted CI run is awaiting maintainer approval and has not executed tests; local success is not a hosted CI pass.