aglinxinyuan opened a new pull request, #7034:
URL: https://github.com/apache/texera/pull/7034

   ### What changes were proposed in this PR?
   
   Deletes 
`amber/src/main/python/core/util/customized_queue/double_blocking_queue.py`, 
which has contained no code since 2022. All 16 remaining lines are the ASF 
license header.
   
   | When | What |
   | --- | --- |
   | 2021-07-23 | `DoubleBlockingQueue` added by #1262 |
   | 2022-11-29 | #1725 switched `InternalQueue` to `LinkedBlockingMultiQueue` 
and emptied the class — but left the file behind |
   | 2025-05-03 | #3415 stamped an ASF license header onto the now-empty file |
   
   Nothing imports it. The package barrel `customized_queue/__init__.py` 
exports only `LinkedBlockingMultiQueue` and `IQueue`, so no `__init__` change 
is needed.
   
   −16 lines, no behaviour change.
   
   ### Any related issues, documentation, discussions?
   
   Closes #7033
   
   ### How was this PR tested?
   
   Existing tests only — there is nothing to add or remove, since the file has 
no code and no spec.
   
   From `amber/`:
   
   - `python -m pytest src/test/python/core/util/customized_queue/` — 54 passed.
   - `python -m ruff check src/main/python/core/util/customized_queue/` — all 
checks passed.
   - `python -m ruff format --check 
src/main/python/core/util/customized_queue/` — 4 files already formatted.
   
   Verification that the file is empty and unreferenced, re-runnable by a 
reviewer:
   
   ```
   grep -vc '^\s*#\|^\s*$' 
amber/src/main/python/core/util/customized_queue/double_blocking_queue.py
   grep -rn "double_blocking_queue\|DoubleBlockingQueue" . --include=*.py 
--include=*.scala --include=*.txt --include=*.toml
   ```
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to