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
F15517643: D18233.diff
Sat, Apr 19, 7:23 AM
F15514870: D18233.id43865.diff
Fri, Apr 18, 6:04 AM
F15498436: D18233.id43865.diff
Sun, Apr 13, 12:57 PM
F15486845: D18233.id.diff
Thu, Apr 10, 9:50 AM
F15467379: D18233.id43865.diff
Thu, Apr 3, 2:16 PM
F15467113: D18233.id43856.diff
Thu, Apr 3, 12:52 PM
F15455965: D18233.diff
Sun, Mar 30, 6:02 AM
F15452367: D18233.id43856.diff
Sat, Mar 29, 4:15 AM
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