From 15c5d143b0d8cfc6539999b3b36a4e27ce351538 Mon Sep 17 00:00:00 2001 From: Alex Ross Date: Wed, 8 Jul 2020 13:38:00 +0200 Subject: [PATCH] Don't use max number in problem matcher Fixes #80288 --- src/vs/workbench/contrib/tasks/common/problemMatcher.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vs/workbench/contrib/tasks/common/problemMatcher.ts b/src/vs/workbench/contrib/tasks/common/problemMatcher.ts index a21dc0708b5..f4d95ecf294 100644 --- a/src/vs/workbench/contrib/tasks/common/problemMatcher.ts +++ b/src/vs/workbench/contrib/tasks/common/problemMatcher.ts @@ -380,7 +380,7 @@ abstract class AbstractLineMatcher implements ILineMatcher { if (startColumn !== undefined) { return { startLineNumber: startLine, startCharacter: startColumn, endLineNumber: startLine, endCharacter: startColumn }; } - return { startLineNumber: startLine, startCharacter: 1, endLineNumber: startLine, endCharacter: Number.MAX_VALUE }; + return { startLineNumber: startLine, startCharacter: 1, endLineNumber: startLine, endCharacter: 2 ** 31 - 1 }; // See https://github.com/microsoft/vscode/issues/80288#issuecomment-650636442 for discussion } private getSeverity(data: ProblemData): MarkerSeverity { -- GitLab