Reading artifact comments is now behind a server switch that is off, so nothing is fetched.
Comment reading requires tengu_onyx_sluice, which falls back off and returns a "not available right now" message.
tengu_onyx_sluice On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.242: on
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Reading comments on an Artifact is gated on tengu_onyx_sluice, which falls back to off in this build. With it off nothing is fetched at all and you get "comments are not available on this artifact right now", counted as cp_read_disabled. With it on, transport errors and HTTP 5xx or 499 are retried once after a random backoff and the unavailable message includes the HTTP status.
- Retries are reported as
server_read_retried. - The old path that fetched comment JSON directly from the content host is gone, along with its
__frame_tandjson_egress_blockedhandling.
cp_read_disabled
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.