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
F15415969: D18233.id43865.diff
Thu, Mar 20, 8:35 AM
F15409537: D18233.id43856.diff
Wed, Mar 19, 4:40 AM
F15409016: D18233.id43865.diff
Wed, Mar 19, 2:46 AM
F15395549: D18233.id43856.diff
Sun, Mar 16, 7:54 AM
F15386442: D18233.id43865.diff
Sat, Mar 15, 12:35 AM
F15336440: D18233.id43865.diff
Sat, Mar 8, 6:51 PM
Unknown Object (File)
Mon, Mar 3, 4:22 PM
Unknown Object (File)
Sun, Mar 2, 10:51 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