Page MenuHomePhabricator

Skip Conduit call log writes in read-only mode, allowing "conduit.ping" to run
ClosedPublic

Authored by epriestley on Jul 18 2017, 3:51 PM.
Tags
None
Referenced Files
F18994802: D18233.id43865.diff
Wed, Nov 19, 3:01 PM
F18964762: D18233.diff
Nov 14 2025, 12:31 PM
F18837287: D18233.diff
Oct 27 2025, 4:47 AM
F18812790: D18233.diff
Oct 20 2025, 12:23 PM
F18810039: D18233.id.diff
Oct 19 2025, 7:01 PM
F18781348: D18233.id.diff
Oct 12 2025, 10:20 PM
F18779191: D18233.diff
Oct 11 2025, 12:46 PM
F18625409: D18233.id43865.diff
Sep 15 2025, 10:45 PM
Subscribers
None

Details

Summary

Ref T10769. See PHI8. We have an unconditional logging write which we can skip in read-only mode.

Test Plan
  • Put Phabricator in read-only mode with cluster.read-only.
  • Called conduit.ping via web UI.
    • Before: write-on-read-only exception.
    • After: good result.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable