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
Unknown Object (File)
Apr 5 2026, 5:47 AM
Unknown Object (File)
Apr 2 2026, 1:05 PM
Unknown Object (File)
Mar 17 2026, 9:51 PM
Unknown Object (File)
Mar 14 2026, 6:08 PM
Unknown Object (File)
Mar 13 2026, 4:44 PM
Unknown Object (File)
Jan 5 2026, 8:36 AM
Unknown Object (File)
Jan 4 2026, 10:40 PM
Unknown Object (File)
Dec 2 2025, 12:35 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 24930
Build 34394: Run Core Tests
Build 34393: 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.