fix(deps): update dependency @lezer/lr to v1.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@lezer/lr	1.2.0 -> 1.4.0

---

Release Notes

lezer-parser/lr (@​lezer/lr)

v1.4.0

Compare Source

New features

The new InputStream.acceptTokenTo method allows a tokenizer to create a token that ends at some absolute position.

v1.3.14

Compare Source

Bug fixes

Further reduce maximum parse depth—the old limit could still cause the tree building function to overflow the stack on V8 when all rules on the stack produce actual visible tree nodes.

v1.3.13

Compare Source

Bug fixes

The parser will now emit an error node when it reaches the end of the top rule but not the end of the input, and restarts parsing the top rule.

Fix an issue that could, when error-recovery happened after a skipped token, cause the parser to emit nodes whose start position was after their end position.

v1.3.12

Compare Source

Bug fixes

Reduce tree depth limit to avoid V8 overflowing its stack.

v1.3.11

Compare Source

Bug fixes

When parsing input ranges with gaps, don't treat the token after a gap as covering the entire gap.

v1.3.10

Compare Source

Bug fixes

Make this package usable in TypeScript setups using node16/nodenext resolution.

v1.3.9

Compare Source

Bug fixes

Fix another issue in the way local token groups and input gaps interact.

v1.3.8

Compare Source

Bug fixes

Fix an issue that caused incorrect trees to be emitted when a forced reduction happened inside a skipped term.

v1.3.7

Compare Source

Bug fixes

Fix a bug where the parser could skip characters while tokenizing in a local token group.

v1.3.6

Compare Source

Bug fixes

Fix an issue where context-tracking parsers, in specific circumstances, could create incorrectly nested trees.

v1.3.5

Compare Source

Bug fixes

Fix an issue where some grammars could make the parser unable to force reductions on invalid input, leading to trees that were missing some wrapping nodes around the broken input.

v1.3.4

Compare Source

Bug fixes

Fix tokenizing of @else tokens that span separate input ranges.

v1.3.3

Compare Source

Bug fixes

Fix a crash when parsing a non-atomic skippable at the top of a nested parse.

Fix a bug that caused the tree-depth limit on left-associative rules to be applied to rules generated for repeat operators.

v1.3.2

Compare Source

Bug fixes

Place a limit on the amount of (non-recovering) parse stacks active at the same time to avoid exponential slowdown on inputs that nest ambiguous constructs.

Reduce the maximum left-associative nesting depth, since the old value could still cause Chrome (but not Firefox) to overflow its call stack.

v1.3.1

Compare Source

Bug fixes

Further reduce maximum parse depth—the old limit could still cause the tree building function to overflow the stack on V8 when all rules on the stack produce actual visible tree nodes.

v1.3.0

Compare Source

Bug fixes

Avoid the problem of huge numbers of repeated left-associative operator applications creating a stack too deep to recurse on by detecting such parses and force-reducing out of them.

New features

Add support for grammars that use @local tokens declarations.

v1.2.5

Compare Source

Bug fixes

Fix a bug that made Stack.canShift incorrectly return true in some circumstances.

v1.2.4

Compare Source

Bug fixes

Fix a tokenizer bug that broke tokenizing of the character \uffff.

v1.2.3

Compare Source

Bug fixes

Fix a regression in the way tokenizers read input when parsing multiple separate ranges.

v1.2.2

Compare Source

Bug fixes

Fix an issue that could cause the tokenizer to crash when tokens ended directly on a gap in the input ranges.

v1.2.1

Compare Source

Bug fixes

Include LRParser.deserialize in the TypeScript declarations.

Fix a bug that broke ParserConfig.specializers (requires @​lezer/generator 1.1.1).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[yegor256]

@rultor please, try to merge, since 6 checks have passed

[rultor]

@rultor please, try to merge, since 6 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor please, try to merge, since 6 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 12s)

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 3178041
+ echo '1.75.1 50eb0c708'
1.75.1 50eb0c708
+ date
Wed 19 Jul 2023 07:39:32 PM CEST
+ uptime
 19:39:32 up 238 days, 17 min,  0 users,  load average: 3.77, 3.71, 1.99
+ cat
com.rultor.spi.Profile: There is no 'merge' section in .rultor.yml for branch main in repo objectionary/try-phi
	at com.rultor.agents.req.StartsRequest.docker(StartsRequest.java:350)
	at com.rultor.agents.req.StartsRequest.vars(StartsRequest.java:255)
	at com.rultor.agents.req.StartsRequest.script(StartsRequest.java:148)
	at com.rultor.agents.req.StartsRequest.process(StartsRequest.java:109)
	at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:75)
	at com.rultor.spi.Agent.execute(Agent.java:84)
	at com.rultor.agents.VerboseAgent.execute(VerboseAgent.java:62)
	at com.rultor.Routine.process(Routine.java:202)
	at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
	at com.rultor.Routine.run(Routine.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
	at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
	at com.rultor.Routine.unsafe(Routine.java:175)
	at com.rultor.Routine.run(Routine.java:142)
	at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
	at com.jcabi.aspects.aj.MethodScheduler.lambda./run.sh(MethodScheduler.java:194)
	at java.base/java.util.concurrent.Executors.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
	at com.jcabi.log.VerboseThreads.run(VerboseThreads.java:222)
	at java.base/java.lang.Thread.run(Thread.java:833)

+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly