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
Unknown Object (File)
Thu, Apr 25, 12:42 AM
Unknown Object (File)
Sun, Mar 31, 11:34 AM
Unknown Object (File)
Mar 19 2024, 11:01 PM
Unknown Object (File)
Mar 4 2024, 5:41 PM
Unknown Object (File)
Feb 4 2024, 12:08 AM
Unknown Object (File)
Jan 27 2024, 2:56 AM
Unknown Object (File)
Dec 3 2023, 2:27 AM
Unknown Object (File)
Nov 30 2023, 4:23 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