Page MenuHomePhabricator

Fix an invalid index access for synthetic lint inline comments from Harbormaster
ClosedPublic

Authored by epriestley on Apr 27 2020, 9:18 PM.
Tags
None
Referenced Files
F19489861: D21178.diff
Thu, Jan 8, 6:07 AM
F19083305: D21178.id50433.diff
Dec 2 2025, 12:33 PM
F19061436: D21178.diff
Nov 29 2025, 12:20 PM
F19017432: D21178.id.diff
Nov 23 2025, 7:51 AM
F19014582: D21178.diff
Nov 22 2025, 8:34 PM
F18985461: D21178.id50432.diff
Nov 17 2025, 1:03 PM
F18828415: D21178.id.diff
Oct 24 2025, 4:09 PM
F18819754: D21178.id.diff
Oct 22 2025, 9:17 AM
Subscribers
None

Details

Summary

Ref T13524. If a Harbormaster lint message has no line number (which is permitted), we try to access an invalid index here. This is an exception after D21044.

Treat comments with no line number as unchanged. These comments do not have "ghost" behavior and do not port across diffs.

Test Plan
  • Used "harbormaster.sendmessage" to submit lint with no line number on a changeset.
  • Viewed changeset.
    • Before patch: "Undefined index: <null>" error.
    • After patch: Clean changeset with lint message.

Screen Shot 2020-04-27 at 2.17.38 PM.png (236×856 px, 18 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable