Profile — Demangled Symbols That Break the Folded Format (txt)
Demangled C++ templates, Rust trait impls, Java generics, lambdas and unresolved hex addresses in the folded format — including one symbol containing a semicolon, which the format has no way to escape. That line is genuinely ambiguous, and how a parser handles it is the point.
main;std::vector<std::pair<int, std::string>, std::allocator<...> >::push_back;operator new 1420
main;shop::Pricing<double>::apply(const Cart&, double);shop::detail::round_half_even 2180
main;<shop_core::pricing::Engine as core::ops::Fn>::call;core::iter::Iterator::fold 1960
main;com.example.shop.Pricing.apply(java.util.List<Item>, double);java.util.stream.ReferencePipeline$3.accept 2410
main;lambda$handle$0;checkout.Handle::{lambda(HttpRequest)#1} 880
main;anonymous namespace'::helper(int, int);memcpy 640
main;shop::parse<Config; strict=true>::run;shop::lex 310
main;[unknown];[unknown];0x00007f4a1c0b2e18 1290
Specifications
- Stacks
- 8
- Languages
- C++, Rust, Java
- Symbols With Commas
- 4
- Symbols With Spaces
- 6
- Symbols With Angle Brackets
- 4
- Ambiguous Semicolon Symbols
- 1
- Unresolved Frames
- 3
Testing contract
Expected to recover- Scenario
- Parse the file and count frames per stack.
- Expected result
- Symbols containing commas, spaces and angle brackets stay intact as single frames, and the semicolon-bearing symbol is either split with a documented rule or reported as ambiguous rather than silently producing an extra frame.
What is a .txt file?
TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.
How to use this file
Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.
How to use this file for testing
“Profile — Demangled Symbols That Break the Folded Format (txt)” is a deterministic Novus Examples fixture for Observability, Log parsing, Encoding detection. Structured and plain-text telemetry with known timestamps, levels, request identifiers, and error states for testing log ingestion, correlation, dashboards, and alert pipelines.
Documented properties for this file: TXT · 618 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Telemetry fixtures use fixed trace IDs, span IDs, and timestamps so ingestion is reproducible run to run. Point your collector, parser, or query layer at the file and assert the documented span tree, metric families, or severity mix; service and host names are invented.
Related files
- loglogfmt — Quoting, Escaping and Bare-Key Edge Cases (log)logfmt lines built to break naive splitting on spaces and equals signs: a value containing an equals sign, escaped quotes, a trailing backslash before the closing quote, a bare key with no value, duplicate keys, non-ASCII values and one unterminated quote followed by a clean line.
- logPlain-Text Log — ANSI Colour Codes in the Stream (log)A developer-mode log where the level and service are wrapped in ANSI colour codes, ending with one uncoloured line. Colour codes sit inside the field a parser wants to read, so level extraction fails unless the sequences are stripped first — the classic symptom of a container run without a TTY check.
- logPlain-Text Log — Mixed CRLF and LF Line Endings (log)One log file written by two agents, four lines ending CRLF and three LF, with one line carrying trailing spaces before its break. Splitting on \n alone leaves a stray carriage return at the end of four fields, which is how a level or status ends up with an invisible character attached.
- logPlain-Text Log — NUL, Control Bytes and Invalid UTF-8 (log)Five log lines carrying a NUL byte, bell, backspace, vertical tab and form feed, plus one 0xFF byte that is not valid UTF-8 — the debris that arrives when binary data reaches a log field. Deliberately contains no terminal-escape sequences, only inert control bytes.
- jsonlStructured Log — Ten Timestamp Formats, One Instant (jsonl)The same instant written ten ways — RFC 3339 at three precisions and with a non-UTC offset, epoch seconds as integer and float, epoch milliseconds and nanoseconds, Common Log Format and the log4j comma-decimal form. What a timestamp autodetector must resolve to one moment.
- jsonlStructured Log — Unicode, RTL, Emoji and Control Characters (jsonl)Log messages in Latin, Japanese and Arabic scripts, an emoji flag and a zero-width-joiner family, NFC and NFD forms of the same accented letter, and escaped tab, newline and carriage return. Everything that makes a log line's byte length and its display width disagree.
Generated by generation/observability.py. Free for any use, no attribution required — license.