Repository navigation
Fetch the cloud service's keys and properties once, not for every request - #48
Closed
jwrosewell wants to merge 2 commits into
Closed
jwrosewell wants to merge 2 commits into
jwrosewell wants to merge 2 commits into
Conversation
This was referenced Nov 11, 2026
Contributor
Author
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.
Stacked on #46.
Problem
The cloud request engine fetched the cloud service's evidence keys and accessible properties again for every request, instead of once.
keysAndPropertiesFetchedtestedthis.evidenceKeyFilter.length > 0(cloudRequestEngine.js line 119). An evidence key filter has nolength, so the test was always false.ready()fetches whenever that test is false (lines 159 to 168), and every cloud engine callsready()when it processes (cloudEngine.js line 117).evidencekeysand one toaccessiblePropertiesbefore the request it was meant to make.Change
cloudRequestEngine.js:getEvidenceKeysrecordsevidenceKeysFetchedwhen the keys arrive, andkeysAndPropertiesFetchedtests that with the properties, so the keys and properties are fetched once.How to verify
A new test,
the keys and properties are not fetched again for a later requestintests/cloudRequestEngine.test.js, counts the stand-in client's requests across two processed requests in a Pipeline with a cloud engine. Both runs used a temporary workflow on Ubuntu with Node 20, runningtests/cloudRequestEngine.test.jsandtests/cloudEngine.test.js.nightly-pull-request.yml, run as a dry run from a temporary branch, built 2d6cba6, this branch's head, merged withrc(run 42507610109). All eight build and test jobs passed on the second attempt. The first attempt failed only inmacOS_Node_22, where the cloud TAC lookup and native model lookup example tests ran past jest's 10 second limit waiting for the cloud service. Both passed in the other seven jobs, and in the rerun.Release note
What remains
rcbefore Accept only the evidence each element reads, and none by default #46's branch is deleted, or GitHub closes it.