yaml_transform_test - add some debug logs and increase row count

[derrickaw]

1. Seeing some flakey test for test_csv_to_json, so adding some debug logs when encountered again.
2. Tried increasing input data to 10,000,000 rows to detect any splitting into multiple shards but nothing seen.
3. Tried running 100 times, but didn't catch it.
4. Tried PrismRunner instead of DirectRunner, but nothing caught.
5. Added some debug logs to tell if maybe an empty file is created by chance.
6. There could be a race condition where the system hasn't cleaned up the temporary file yet used during the pipeline and we globbed the output + "*" pattern, we caught that condition. So changing to "-*" to eliminate that possibility.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses intermittent test failures in the yaml_transform_test suite. By refining the output file matching logic and providing more descriptive error reporting, the changes aim to stabilize the test environment and make debugging future failures more efficient.

Highlights

• Test Stability: Increased the input data size in the test_csv_to_json test case to improve test coverage and reliability.
• File Globbing Fix: Updated the output file globbing pattern from '' to '-' to prevent potential race conditions with temporary file cleanup.
• Enhanced Debugging: Added detailed error messaging including file sizes when the expected shard count is not met.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the test_csv_to_json test case in yaml_transform_test.py by increasing the test data volume to 1024 records and enhancing the shard count assertion with a more descriptive error message that includes file sizes. A review comment suggests replacing the backslash line continuation in the assertion message with implicit string concatenation to adhere to PEP 8 standards and prevent unintended whitespace in the output.

[github-actions]

Assigning reviewers:

R: @claudevdm for label python.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.51%. Comparing base (c5d0ab1) to head (fc6c920).
⚠️ Report is 13 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master   #38367   +/-   ##
=========================================
  Coverage     60.50%   60.51%           
  Complexity    20442    20442           
=========================================
  Files          3307     3307           
  Lines        315339   315393   +54     
  Branches      16942    16942           
=========================================
+ Hits         190799   190851   +52     
- Misses       116084   116086    +2     
  Partials       8456     8456           

Flag	Coverage Δ
python	79.87% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.