When a peer message is held, you now see whether org or repo settings caused it.
What's wrong with this entry?
When an inbound cross-session peer message is held, the explanation now tells you whether an org managed setting or the repository's own settings forced it, rather than just reporting an explicit setting.
- Two new hold-reason cases:
managed-settingandrepo-setting, in addition to the plainexplicit-settingcase. - The repo case explains that a repo may only tighten, so your own "accept" cannot override it, and points at --setting-sources to exclude it.
- The resolver was reworked to return both the effective value and which tier decided it; repo-level local and project settings are attributed as repoSettings.
This repository's settings set "crossSessionInbound" to "hold" (a repo may only tighten, so your own "accept" cannot override it); remove the repo setting or exclude it with --setting-sources., This repository's settings set "crossSessionInbound" to "hold" (your own "accept" cannot override a repo tightening).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross