Page MenuHomePhabricator

Use "getInlines()", not "_inlines", to access inlines on client Changeset objects
ClosedPublic

Authored by epriestley on Oct 2 2020, 4:11 PM.
Tags
None
Referenced Files
F17943980: D21475.id51117.diff
Thu, Jul 31, 9:09 AM
F17943977: D21475.id51116.diff
Thu, Jul 31, 9:09 AM
F17943976: D21475.id51115.diff
Thu, Jul 31, 9:09 AM
F17943670: D21475.id.diff
Thu, Jul 31, 8:36 AM
F17914379: D21475.id51117.diff
Tue, Jul 29, 7:17 PM
F17833489: D21475.diff
Sat, Jul 26, 1:37 PM
F17708857: D21475.id51117.diff
Thu, Jul 17, 3:13 AM
F17705257: D21475.id51116.diff
Wed, Jul 16, 7:27 AM
Subscribers
None

Details

Summary

See PHI1898. An install is reporting an execution/initialization order issue where this code is reachable before _inlines is initialized.

I can't immediately reproduce it, but using "getInlines()" is preferable anyway and seems likely to fix the problem.

Test Plan

Viewed revisions with inlines, added/removed/edited/replied to inlines, didn't find anything broken.

Diff Detail

Repository
rP Phabricator
Branch
inline1
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 24931
Build 34396: Run Core Tests
Build 34395: arc lint + arc unit

Event Timeline

  • Fix a possible call reentrancy issue, where "getInlines()" and "getInlineForRow()" could call one another.
This revision was not accepted when it landed; it landed in state Needs Review.Oct 2 2020, 4:19 PM
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.