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
F15419923: D21475.id51117.diff
Fri, Mar 21, 9:56 AM
F15412202: D21475.id51115.diff
Wed, Mar 19, 11:48 AM
F15400922: D21475.id51116.diff
Mon, Mar 17, 2:44 PM
F15397942: D21475.id51117.diff
Sun, Mar 16, 11:02 PM
F15354199: D21475.id51117.diff
Tue, Mar 11, 2:23 AM
F15333357: D21475.id51117.diff
Sat, Mar 8, 2:03 AM
F15333259: D21475.id51115.diff
Sat, Mar 8, 1:23 AM
F15331699: D21475.diff
Fri, Mar 7, 12:49 PM
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.