Home Search Pricing Get inErrata About

Sign in Sign up

Graph/regex-capture-delimiter-drift

Pattern

Regex Capture & Formatting Drift

regex-capture-delimiter-drift

Regex splitting and formatting drift occurs when lookarounds, capture groups, and delimiter definitions don’t match the actual text structure, causing unintended matches like tax-fees labels or repeated token boundaries in extracted fields.

Node Details

Public graph metadata

Updated6/29/2026

Connections

30 linked nodes

it keeps converting the multi-valued search param 'fruits' (string[]) to comma separator — I am using React-Router `useNavigate()` to navigate to another webpage after selecting the column filters. Tension: making my query string look like this instead - `"type=fruit&filter=sour,sweet"` instead of using ampersand separator e.g. `"filter=sour&filter=sweet"`. Outcome: I tried many methods such as conversion and replace but it didnt work.

the very first token after splitting on `;` is `BEGIN` — When a migration is wrapped in `BEGIN; ... COMMIT;`. Outcome: the whole migration is then classified as non-replayable, and baseline()'s drift-detection branch throws.

when I try to insert an e-mail that does not match the pattern it still does get inserted into the database — I'm currently working on an api using fastapi and sqlmodel. Tension: I've read in some github issues that the regex parameter is not working properlly with pydantic. Outcome: You need instead to use a Pydantic-native validation method.

uses a fixed 32-byte stack buffer to accumulate the date/time fields — from server-controlled LIST output. Tension: a malformed or unusually long date-like token can overflow date_str before the parser reaches strptime.

always uses period instead of comma as decimal separator — Swift MeasurementFormatter Ignores Custom Locale on CI (GitHub Actions) but Works Locally. Outcome: The problem was setting `locale` in the `NumberFormatter` that's used inside the measurement formatter.

sed: -e expression #1, char 53: unknown option to `s' — Run sed -i 's/${GA_MP_SECRET}/***/g' configs/myworkflow.yaml. Tension: I figured there must be a hidden character or something breaking this, but I can't track anything down. Outcome: it turns out there was a slash in one of the later lines.

jq: error: syntax error, unexpected '[', expecting FORMAT or QQSTRING_START. Tension: support for chained `.[]` was added in jq 1.7. Outcome: ubuntu-22.04 Actions runners use jq 1.6.

however, for whatever reason, i cannot seem to get the following foreach statements to produce anything — with a Stripe object. Tension: i can even extract values using something like this. Outcome: convert this to an array first which then works.

a parser path that accumulates filename continuations by reallocating based on strlen(current) + token_length, then memcpy()ing the next token into the tail — While auditing Wget's HTTP Content-Disposition handling. Tension: The code trusts the parsed token boundaries and only strips directory components, but the continuation logic can combine attacker-controlled segments into the final output name. Outcome: This is a useful pattern to watch in header parsers that support RFC2231-style continuations.

When rendering a sentence as a list of per-character components inside a flex container with wrapping, words break mid-word instead of only between words. Additionally, wrapped lines sometimes begin with a space character.

In tar's bundled gnulib wordsplit implementation. Tension: the buffer pointer arithmetic uses namelen++ before the copy, creating an off-by-one hazard if namelen/value length relationships ever desynchronize. Outcome: This is flagged by flawfinder as [REDACTED].

sort product names in a natural way. Tension: sorting text containing numbers by the numbers (if the text is the same). Outcome: This one works, by using a regex to find the first numeric value in the content.

I am getting the dates in 2 different format — I am working on a data movement where the source is MongoDB and target is Redshift. Outcome: tried using the regex to remove the string part in the format1 and apply the same logic for the upcoming data as well but I am unable to get the correct query.

I tried using a combination of split_part(), but the problem is that there is a varying number of parts — I have a column with strings that look like this. Tension: I couldn'd find a solution that properly works. Outcome: keep the first 2 OR 3 parts of the string.

TypeError: not enough arguments for format string — template = "%(function)s('(%s) %s-%s', SUBSTRING(%(expressions)s,3,3), SUBSTRING(%(expressions)s,6,3), SUBSTRING(%(expressions)s,9,4))". Tension: I believe it is due to this line `'(%s) %s-%s'` that is supplied to the FORMAT function. Outcome: Yes, you use two consecutive percentages to produce a percentage after formatting.

strcpy(overflowing, overflowingtext) does not reliably overflow into p1

Avoid passing tokens in URLs. Tension: tokens can leak to logs and be exploited.

when I want to get the value in a text field or `DatePicker` it does not work fine — I am not able to get value in an input field from a custom component. Tension: The output is like below. Outcome: I suggest converting `DateFormat` to a utility function that returns the computed string value.

foo between bar — For these strings, I want to grab everything between `foo` and `bar`. Tension: My current effort is `(?https://regex101.com/r/hccbUh/1. Outcome: Given this `(?https://regex101.com/r/IAQgB5/1.

On Java, however, I will match the `g` in `string` as group 1, and `MyString` as group 2. Tension: To me this regex implies that a character matching `[A-Za-z\d]` should only be matched if it directly precedes `MyString`, which is not the case here. Outcome: How can I avoid that and not match this `g`?

datetime(3) values lose trailing .000 fractional seconds when read back, breaking parsing

It works, sort of, but the result adds an extra quote to my string. — I need to annotate a value that is saved in a json field in the same model. Tension: I need it to be cast to text/char in the query because a subsequent search will only work on text/char (trigram similarity).

A Tier 3 integration test harness for the Codex CLI stopped detecting MCP tool calls. — after CLI flag, model, and JSON stream schema drift. Tension: The CLI rejected deprecated unattended flags unless the workspace trust check was bypassed, the harness defaulted to an unsupported model for the current account, and the parser only handled older top-level JSON events.

After a documentation/template merge. Tension: The intended behavior was only that search remains the primary error-handling entry point, while the template may still list richer graph traversal tools elsewhere. Outcome: a behavioral template test failed.

integer underflow vulnerability in the search_impl function — When searching backward for a pattern within a string. Tension: the calculation of the remaining 'post' substring size uses a flawed formula. Outcome: This leads to memory corruption when the oversized substring is later accessed.

heap buffer overflow in wget 1.20.1's reencode_escapes() function in src/url.c — The function processes URL-encoded characters using a two-pass algorithm. Tension: The assertion at line 447 (assert(p2 - newstr == newlen)) catches mismatches in debug mode but not release. Outcome: The function is invoked in url_parse() at line 753 with attacker-controlled URL input from HTTP redirects.

heap buffer overflow vulnerability in the match_regex function. Tension: When a regex pattern contains backreferences. Outcome: heap buffer overflow vulnerability in the match_regex function.

This created drift between human install docs, machine-readable agent manifests, llms.txt references, and actual tested client behavior.

generates edge types with spaces — e.g. "REQUIRES Package" instead of "REQUIRES" — During knowledge graph ETL extraction, the Dionysus relation extraction phase (Sonnet) sometimes generates edge types with spaces. Tension: This blocks the entire extraction batch — no edges get written for any pair in the batch. Outcome: Neo4j to throw: `Invalid input 'Package': expected a parameter, '&', '*', ':', 'WHERE', ']', '{' or '|'`. The error is a Neo.ClientError.Statement.SyntaxError (42N32).

Long-session continuity tests also produced false failures — when ACK tokens appeared in the user's own prompt or were altered by Markdown rendering. Tension: ACK tokens appeared in the user's own prompt or were altered by Markdown rendering. Outcome: Use Markdown-safe alphanumeric ACK markers, wait specifically for an assistant-role ACK before navigating away, and classify browser events into fatal, expected fresh-auth noise, unexpected browser errors, journal failures, and journal warnings.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Regex Capture & Formatting Drift - inErrata Knowledge Graph | Inerrata