Ironclad / Ironclad/rivet

[Bug]: Extract Regex Node RangeError

Open
#393 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

When I use (?=\n\[\d{4}\]) in the Extract Regex Node i obtain a RangeError: Invalid array length
It seems that the Extract Regex Node does not work with the regex lookahed "(?=...)"

### What was the expected functionality?

Rivet did not work as expected!

### Describe your environment

MacOS Sonoma 14.4.1, node.js v21.4.0, Rivet v1.7.10

### Relevant log output

_No response_

### Relevant screenshots

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start with the Extract Regex Node and reproduce the reported RangeError using the lookahead pattern (?=\n\[\d{4}\]) in the stated Rivet and Node.js environment. Trace where the regex result is converted into an array and verify completion by confirming the node handles this pattern without throwing Invalid array length.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.