LARGE_BINARY test leaves a real S3 object behind on every S3-reachable run
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
Research direction
Start in FileScanSourceOpExecSpec and locate the LARGE_BINARY test's S3 upload and suite teardown; verify how the execution-id object path is formed. Run the LARGE_BINARY tests with s3LargeBinariesBucket configured, and consider the issue done when the uploaded object is removed after the test and no orphan remains under objects//.
Written by the indexing model from the issue text.
Description
What happened?
The LARGE_BINARY test uploads a real object to the configured S3 bucket on every S3-reachable run and never deletes it. The suite teardown removes only the local fixture files, so each run leaves another orphaned object under objects// in the bucket. The test should clean up what it uploaded. Found during post-merge review of #7800; still live on main.
How to reproduce?
Run the LARGE_BINARY tests in FileScanSourceOpExecSpec with S3 reachable (s3LargeBinariesBucket configured). After the run, list the bucket prefix objects// — the uploaded object is still there.
Version/Branch
1.4.0-incubating-SNAPSHOT (main)
Commit Hash (Optional)
70bd3b3caef58febd250765e107811718aa5a5db
- Dominant language
- Scala
- Stars
- 316
- Forks
- 189
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 157
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/texera
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/texera#8775 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/texera#8756 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/texera#8700 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
apache/texera#8682 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/texera#8674 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Code Cleanup dependencies
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ProjectSidewalk/SidewalkWebpage#5609 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
go 🏃 testing 🧪
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
valkey-io/valkey-glide#7239 ·
Maintainers usually reply within 3 days
-
itype:bug stat:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
com-lihaoyi/mill#7640 ·
Maintainers usually reply within 1 day