Local JUnit and console output are not scrubbed (document it, or add an opt-in)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
Research direction
Read the report and CI documentation that describe Probe Cloud uploads, then trace where probe test writes local JUnit, JSON, and console output. Update the docs to identify which outputs are scrubbed and advise keeping secrets out of test names and error messages; add a CHANGELOG entry. The issue leaves whether to add --scrub-output undecided, so settle that scope in the PR description.
Written by the indexing model from the issue text.
Description
Summary
Only the Probe Cloud upload payload is scrubbed (relative paths, secret patterns, no artifacts). The JUnit file and the console output that probe test writes locally are the user's own output and are not scrubbed, so a secret that appears in a test name or error message can land in a CI log or a JUnit artifact.
Acceptance criteria
- The report and CI docs say plainly which outputs are scrubbed (the upload payload) and which are not (local JUnit, JSON, console), and advise keeping secrets out of test names and error messages.
- Decide in the PR description whether an opt-in
--scrub-outputis worth adding; if yes, it reuses the upload scrubber and is additive. - CHANGELOG entry.
- Dominant language
- Go
- Stars
- 6
- Forks
- 3
- Avg merge
- 6h 28m
- Merged PRs (30d)
- 362
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
area/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
AlphaWaveSystems/flutter-probe#424 ·
Maintainers usually reply within 1 day
-
area/docs documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AlphaWaveSystems/flutter-probe#409 ·
Maintainers usually reply within 1 day
-
Dial timeout error should say how long it waited and name the timeout settingPossibly taken @jay23606 claimed this 2 days ago. Openarea/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AlphaWaveSystems/flutter-probe#408 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
AlphaWaveSystems/flutter-probe#888 ·
Maintainers usually reply within 1 day
All issues in AlphaWaveSystems/flutter-probe
Similar issues
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jordansmall/spindrift#7254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pg-sharding/spqr#3275 ·
Maintainers usually reply within 1 day
-
create_or_update_file rejects explicitly empty file contentPossibly taken @Elon-Jiang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/github-mcp-server#3883 ·
Maintainers usually reply within 4 days
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databricks/terraform-provider-databricks#6210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Maintainers usually reply within 2 days