Page MenuHomePhabricator

Render query strings into concrete scalar "string" values immediately, not lazily
ClosedPublic

Authored by epriestley on Mar 5 2019, 9:42 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Sep 12, 10:52 AM
Unknown Object (File)
Mon, Sep 12, 10:44 AM
Unknown Object (File)
Sun, Sep 11, 6:06 AM
Unknown Object (File)
Mon, Sep 5, 12:52 PM
Unknown Object (File)
Fri, Sep 2, 5:34 PM
Unknown Object (File)
Aug 18 2022, 7:08 AM
Unknown Object (File)
Aug 12 2022, 1:21 PM
Unknown Object (File)
Aug 9 2022, 1:11 AM
Subscribers
None

Details

Summary

See D20067. (Previously, see T13242.) Currently, qsprintf() returns an object which is turned into a string immediately (to test for errors) and then again later, lazily, for actual use.

In theory, the two renderings may produce different results, if you pass one or more objects to qsprintf(...) and then modify the objects after the qsprintf(...) call but before the query is executed. This would likely be very, very surprising.

To avoid this, immediately render the string and store the flat string value, not the arguments.

This is technically also a performance change (it reduces calls to xsprintf_query() by about 50%, since we don't rebuild the string twice) but now justfiable purely as a correctness/simplicity change.

(I'm going to try to make a followup performance change where we just render the masked string and use it for both values if the masked and unmasked strings are identical, but I'll justify that with profiling.)

Test Plan

Browsed around, everything worked. Checked that sensitive values are properly masked in DarkConsole. (Also, added some debugging echo and observed ~50% fewer calls to xsprintf_query().)

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable