You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@burr.apache.org by "elijahbenizzy (via GitHub)" <gi...@apache.org> on 2026/04/21 01:26:56 UTC
[I] Release CI follow-ups: tighter coverage [burr]
elijahbenizzy opened a new issue, #747:
URL: https://github.com/apache/burr/issues/747
Follow-ups identified during code review of #745. Not blocking, but worth doing.
## Files / scripts
- [ ] **Rename `examples/deep-researcher/utils.py`** — currently shares its basename with 4 other ASF-owned `utils.py` files. The new `.rat-excludes` uses basename matching, so all 5 are skipped. A future regression in any of the 4 ASF files would silently pass RAT.
- [ ] **Thread `--skip-signing` through `cmd_verify`** in `scripts/apache_release.py`. Today running the `verify` subcommand against a `--skip-signing` build crashes on missing `.asc` files.
- [ ] **Run RAT on the wheel too**, not just the tarballs. Wheel is also redistributed.
- [ ] **Pin the RAT JAR by SHA256** in `.github/workflows/release-validation.yml`. Currently the workflow downloads from Maven Central without integrity verification.
## Smoke test (`scripts/ci_smoke_server.py`)
- [ ] Replace `time.sleep(2)` after running the tracked app with a poll-then-assert loop on `/api/v0/projects` (currently flake-prone).
- [ ] Forward `SIGTERM` to the uvicorn child via process group (currently only kills the burr CLI wrapper; child can be orphaned on dev boxes).
- [ ] Add `--cleanup` flag and default to cleaning the workspace locally (CI keeps it via `GITHUB_ACTIONS` env, currently always retained).
## CI coverage gaps
- [ ] Add a matrix cell that does **bare `pip install <wheel>`** (no `[learn]` extras) and at least imports `burr` and `burr.tracking.server.run`. Catches optional-extra dep leakage into base.
- [ ] Add a step that **builds the wheel from the sdist tarball** (what voters do) and asserts the result matches the CI-built wheel. Catches sdist-vs-wheel drift.
- [ ] Hit `GET /` in the smoke test to confirm the UI build is actually served (not just present in the wheel).
## Hygiene
- [ ] Add a pre-commit hook that grep-checks new files for ASF headers (RAT in CI is the safety net but slow).
- [ ] Add a weekly cron job running this workflow against `main` to catch dep-drift between RCs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4553717443
@elijahbenizzy, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the [assignment policy](../blob/main/CONTRIBUTING.rst#issue-assignment-policy)).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "andreahlert (via GitHub)" <gi...@apache.org>.
andreahlert commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4304770486
This issue is a follow-up of #745 and part of the release process automation epic #715.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "elijahbenizzy (via GitHub)" <gi...@apache.org>.
elijahbenizzy closed issue #747: Release CI follow-ups: tighter coverage
URL: https://github.com/apache/burr/issues/747
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4439747648
@elijahbenizzy, this issue has been inactive for 19 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the [assignment policy](../blob/main/CONTRIBUTING.rst#issue-assignment-policy)).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4913534314
@elijahbenizzy, @t1mato, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the [assignment policy](../blob/main/CONTRIBUTING.rst#issue-assignment-policy)).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "t1mato (via GitHub)" <gi...@apache.org>.
t1mato commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4784448579
Hello, would love to work on this issue if it hasn't been finished already.
@elijahbenizzy @andreahlert
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Release CI follow-ups: tighter coverage [burr]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #747:
URL: https://github.com/apache/burr/issues/747#issuecomment-4669458873
@elijahbenizzy, this issue has been inactive for 14 days.
Are you still working on it? Drop a comment to let us know.
If there is no update within 7 days, the assignment will be removed
so someone else can pick it up
(per the [assignment policy](../blob/main/CONTRIBUTING.rst#issue-assignment-policy)).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@burr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org