Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 154 of 221; 24 results per page.
Five recording rules following the level:metric:operation naming convention, where one rule consumes two others recorded earlier in the same group: evaluation order inside a group is sequential, which is exactly what makes that legal and what a rule validator must understand.
Three scrape jobs with the parts that actually matter: relabel_configs rewriting a target label with a capture group, metric_relabel_configs dropping the two unbounded labels from the cardinality fixture, honor_timestamps for the textfile collector and a federation job with a match[] selector.
The file a cron job drops into the node_exporter textfile directory so a batch task can be monitored without a scrape endpoint: last-success timestamp, artefact size, duration and per-job exit codes, one of which is non-zero. The canonical shape for batch-job alerting.
A reusable prompt library in JSON Lines: 20 templated prompts for summarization, translation, extraction, code, and more, each with a task label, tags, and {curly-brace} placeholders. A fixture for prompt-management tools and JSONL parsers.
Tiny SAMPLE prompt fixture (fewshot-translate) for harness and eval wiring.
Tiny SAMPLE prompt fixture (system-concise) for harness and eval wiring.
Tiny SAMPLE prompt fixture (system-json-only) for harness and eval wiring.
Tiny SAMPLE prompt fixture (user-classify) for harness and eval wiring.
Tiny SAMPLE prompt fixture (user-extract-entities) for harness and eval wiring.
Tiny SAMPLE prompt fixture (user-summarize) for harness and eval wiring.
Three synthetic protein sequences that begin with methionine and include the X, B and Z ambiguity codes, which are legal IUPAC residues rather than errors. A validator restricted to the twenty standard amino acids rejects all three files.
A single protobuf User message in binary wire format (varint + length-delimited fields): the serialized counterpart to the user.proto schema. For testing protobuf decoders without the generated code.
A proto3 Protocol Buffers schema with messages, an enum, and a repeated field, for testing protobuf compilers (protoc), codegen, and schema tooling.
The compatible proto3 Customer message for field-number and wire-compatibility testing. Backward compatible: existing field numbers/types are retained and optional email uses new field number 3.
The baseline proto3 Customer message for field-number and wire-compatibility testing. Reference wire contract: field 1 is string id and field 2 is string name.
The breaking proto3 Customer message for field-number and wire-compatibility testing. Breaking relative to baseline: field number 2 is reused with a different name and wire type.
The five checks a verifier must perform against the attestation fixtures in this category, and the exact result each one should produce, including the two that are meant to fail. Every package, version, hash and licence is fictional: the tree describes nothing real.
Pseudolocalization SAMPLE (bracket-wrapped) for i18n layout overflow testing.
A Dart pubspec.lock in YAML, labelling each fictional package as direct main or transitive and recording a sha256 in its description block along with the SDK constraint. Every package, version, hash and licence is fictional: the tree describes nothing real.
A purchase order with repeating line items whose field names use array notation, so a parser has to reconstruct three rows from flat form data. The total is computed in the browser and submitted as a read-only control.
A purchase order with buyer and vendor blocks, a line-item table, totals, and Net-30 terms: an editable Word document paired with a PDF twin.
The purchase order as a branded print-ready PDF with a line-item table and totals: the format twin of the DOCX version for converter and print testing.
A 192×192 PNG app icon referenced by the web app manifest (purpose 'any'), for testing PWA icon pipelines and manifest icon resolution.
A 512×512 PNG app icon referenced by the web app manifest (purpose 'any'), for testing PWA icon pipelines and manifest icon resolution.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
