From 7dc962281f0ed98d3fbdae2152927a0cde707076 Mon Sep 17 00:00:00 2001
From: Raymond Hill <rhill@raymondhill.net>
Date: Sun, 7 Jun 2020 08:50:20 -0400
Subject: [PATCH] Set max token length on parser for consistent compilation

Reported internally. The issue could cause the logger
to be unable to successfully reverse-lookup a filter
list for a filter which had tokens longer than 6
characters followed by wildcard.

Regression from:
- https://github.com/gorhill/uBlock/commit/01b1ed9a982965378d732ab0cb4bcd68727fe910
---
 src/js/reverselookup.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/js/reverselookup.js b/src/js/reverselookup.js
index 2b6e59f36..8be351967 100644
--- a/src/js/reverselookup.js
+++ b/src/js/reverselookup.js
@@ -136,6 +136,7 @@ const fromNetFilter = async function(rawFilter) {
     const µb = µBlock;
     const writer = new µb.CompiledLineIO.Writer();
     const parser = new vAPI.StaticFilteringParser();
+    parser.setMaxTokenLength(µb.urlTokenizer.MAX_TOKEN_LENGTH);
     parser.analyze(rawFilter);
 
     if ( µb.staticNetFilteringEngine.compile(parser, writer) === false ) {