You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 7, 2025. It is now read-only.
When we set a value for maxTrustedBiddingSignalsURLLength we do observe a split in the KV calls in smaller batches (for the ones with many tbs keys). And this is expected.
We would then expect that generateBid() is called for each of these batches independently of the others as they return.
Is this assumption correct?
This seems to be described here: https://github.com/WICG/turtledove/blob/main/PA_implementation_overview.md#trusted-signals-fetches--reprioritization ( we are setting enableBiddingSignalsPrioritization to false)
However we conducted a test and it does seems to wait for all the calls to the KV server to finish before starting generateBid()
Could you please advise on the expected behaviour?
When we set a value for
maxTrustedBiddingSignalsURLLengthwe do observe a split in the KV calls in smaller batches (for the ones with many tbs keys). And this is expected.We would then expect that
generateBid()is called for each of these batches independently of the others as they return.Is this assumption correct?
This seems to be described here: https://github.com/WICG/turtledove/blob/main/PA_implementation_overview.md#trusted-signals-fetches--reprioritization ( we are setting
enableBiddingSignalsPrioritizationto false)However we conducted a test and it does seems to wait for all the calls to the KV server to finish before starting
generateBid()Could you please advise on the expected behaviour?