Skip to content

Lasagna 0.2.0

Choose a tag to compare

@dolev31 dolev31 released this 01 Nov 11:20
cf6d313

The first release with outside contributors. Thank you to
@ect2000, for the 2wikimultihopqa benchmark
with its distractor paragraphs and the agentic-pipeline checks in
lasagna component validate, and to @juliasadler,
for the fix to two services racing to create a collection, measured against
the stack's own Qdrant.

Deprecated

  • The old names renamed in 0.1.0 (lasagna benchmark compare, lasagna benchmark leaderboard, results interaction --bootstrap, and the names
    dropped from lasagna.__all__) and the unversioned /api/config/knowledge
    routes stay for one more release, with their warnings, and are removed in
    0.3.0. 0.1.0 said 0.2.0; their warnings now name 0.3.0.

Changed

  • The PyPI page links the documentation site and the paper.

Added

  • A pinned 2wikimultihopqa benchmark adapter with a validation corpus that
    retains gold paragraphs and distractors, with version-specific IDs that deduplicate
    formatting-only whitespace differences while keeping the first original text.
  • A "PR quality" check on every pull request (scripts/check_pr_body.py). It
    fails until the description fills in the template, a person names themselves
    as having read the whole diff, every suppression in the added lines gives a
    reason, every TODO links an issue, and a change to src/lasagna/ comes with a
    test and a line here. The no-changelog and no-new-test labels waive the
    last two. CONTRIBUTING.md has the full bar under "Quality bar".
  • A pull request template, and CODEOWNERS.
  • Issue forms for a benchmark request and a research proposal. The component
    form now asks for the stage, the paper and the number it reports, and a
    comparison with a built-in control. Blank issues are off; questions go to
    Discussions.
  • A Wanted page: the
    components, benchmarks, studies and deployment work the project would like to
    have, each with what "done" means.
  • A pull request checklist in docs/contributing-components.md.
  • An IMAGE_EXTRAS build argument for the Docker image (set in .env): extras
    installed beyond the production set, empty by default. IMAGE_EXTRAS=eval
    runs lasagna benchmark and sweeps inside the Compose stack.
  • Every pull request is tested in the production environment, the Compose
    stack built from its branch (CONTRIBUTING.md, "Tested in the production
    environment"). The "PR quality" check fails while "How it was tested" shows
    no docker compose command, and the template has a box for it.

Fixed

  • On a Milvus server, the benchmark's corpus census and pre-flight see the
    rows written just before them. A server reads with the collection's Bounded
    consistency, so a count right after ingestion came up short (0 of 24
    documents), and every cold lasagna benchmark run in the Compose stack was
    refused as "changed while this run used it". Backends gain read_fresh(),
    a block whose filter reads see every earlier write (a no-op by default; on a
    Milvus server it reads Strong, about 200 ms a query, so only these checks
    use it and search keeps its speed). iter_all on a server first runs one
    Strong query, since pymilvus's query iterator ignores the consistency level,
    so a scan right after an insert could come up short. PooledVectorBackend,
    which the Compose stack runs in front of a Milvus server, passes both on: it
    enters read_fresh on every pooled instance, and iter_all uses an
    instance's own cursor instead of paging by offset, which read stale and
    stopped at Milvus's 16,384-row limit. The pool also passes on is_lite, so
    a pool over Milvus Lite (connection_pool_size above 1) is no longer taken
    for a server.
  • Two services starting together no longer fail when the other creates the
    collection first: create_collection raises CollectionExistsError (a
    ValueError subclass) on an existing name, and collection initialization
    continues as the "already exists" branch does instead of failing to start.
    The same lost-race handling now covers the third check-then-create path,
    CollectionManager.ensure_backend_collection, which the API process and a
    Celery worker can reach at the same time.
  • Validate BaseAgenticPipeline components with an async contract check and
    report incorrect results or input mutation instead of rejecting the stage.

Earlier changes: https://github.com/dolev31/lasagna/blob/v0.2.0/CHANGELOG.md