Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

breg tests: stale re-freeze command, unused migration helpers, and a stale source view copy

Open Beginner friendly
  • Is something wrong?
#2,034 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
postgresql, rust
Domain
databases, testing

Research direction

Read the re-freeze command in crates/registry-breg/tests/frozen_rhai_package.rs, the warnings from the postgres_migration target, and the recreated source view in crates/registry-breg/tests/postgres_statistics_http.rs. Add the runtime feature to the documented command, remove or use the listed unused helpers, and match the view options to those generated by the engine. Confirm with the stated cargo check command and verify the fixture command writes the fixture.

Written by the indexing model from the issue text.

Description

area:breg rust

Three small leftovers in the registry-breg test tree, noticed while working on #1564. None changes behaviour.

  1. The re-freeze command for the frozen Rhai package fixture runs no test. The header of crates/registry-breg/tests/frozen_rhai_package.rs documents cargo test --locked -p registry-breg --test frozen_rhai_package -- --ignored write_frozen_fixture. The file is gated on #![cfg(feature = "runtime")] and runtime is not a default feature, so the command exits green with 0 tests and writes nothing. It needs --features runtime.

  2. postgres_migration builds with 10 unused-code warnings under --features postgres-test,tooling, on main as of 2026-10-13:

    • unused imports successor_plan_is_empty_for_predecessor and successor_plan_is_empty
    • unused functions load_rewritten_person_package, copy_package_tree, person_registration_acceptance_root, person_registration_project, person_registration_assets, compile_person_registration, prepare_and_load_person_registration
    • source_bytes and drop_null_members from tests/support/source_bytes.rs, unused in this binary only

    They look like helpers of tests that were removed. No gate reports them because the clippy job does not build the postgres-test targets.

  3. Once #2030 merges, one test keeps a stale copy of the source view options. crates/registry-breg/tests/postgres_statistics_http.rs recreates a source view WITH (security_invoker=true, security_barrier=true) to inject a delay. The engine no longer emits security_barrier there. The test still passes; the copy should match the engine.

Done when

  • The documented re-freeze command writes the fixture.
  • cargo check --locked -p registry-breg --features postgres-test,tooling --test postgres_migration is free of warnings.
  • The statistics test recreates the view with the options the engine generates.
Dominant language
Rust
Stars
2
Forks
0
Avg merge
10h 36m
Merged PRs (30d)
257

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from registrystack/registry-stack

All issues in registrystack/registry-stack

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.