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
F17657539: D21475.diff
Sat, Jul 12, 12:21 PM
Unknown Object (File)
Jun 3 2025, 8:57 PM
Unknown Object (File)
May 1 2025, 10:16 PM
Unknown Object (File)
Apr 26 2025, 9:32 AM
Unknown Object (File)
Apr 25 2025, 10:39 PM
Unknown Object (File)
Apr 23 2025, 11:28 PM
Unknown Object (File)
Apr 11 2025, 9:23 AM
Unknown Object (File)
Apr 4 2025, 9:32 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.