Skip to content

Conversation

@Mathdee
Copy link

@Mathdee Mathdee commented Jan 21, 2026

Issue:
As described in #37370, running pipelines with large options on Dataflow causes fork/exec /usr/local/bin/python: argument list too long.
This occurs because the bootloader passes the complete JSON config via PIPELINE_OPTIONS environment variable --> exceeds the OS ARG_MAX limit.

The Fix:
This change uses an identical pattern from the Go SDK (Issue #27839, Commit e31e885) to Python.

  1. boot.go(file): Writing the pipeline options to a temp file (pipeline_options.json) and sets the PIPELINE_OPTIONS_FILE environment variable.
  2. sdk_worker_main.py(file): This then checks for PIPELINE_OPTIONS_FILE and loads the configs from the disk if present.

Outcome:


  • 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.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Mathdee, I'm Gemini Code Assist1! 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 introduces a robust solution for handling large pipeline options in the Python SDK, which previously led to an 'argument list too long' error due to operating system limitations on environment variable size. By transitioning from direct environment variable passing to a file-based approach, where options are written to a temporary file and its path is referenced, the system can now accommodate extensive configurations without encountering runtime failures. This enhancement ensures greater stability and consistency across SDKs.

Highlights

  • Addresses Argument List Too Long Error: This pull request resolves the fork/exec /usr/local/bin/python: argument list too long error that occurs when running Dataflow pipelines with excessively large pipeline options, by preventing the complete JSON config from being passed directly via the PIPELINE_OPTIONS environment variable.
  • File-based Pipeline Options: Pipeline options are now written to a temporary file named pipeline_options.json by the Go bootloader. The path to this file is then passed to the Python SDK worker via the PIPELINE_OPTIONS_FILE environment variable.
  • Python SDK Worker Adaptation: The Python SDK worker (sdk_worker_main.py) has been updated to check for the PIPELINE_OPTIONS_FILE environment variable and load the pipeline configuration from the specified file if present, ensuring compatibility with the new mechanism.
  • Feature Parity: This change brings the Python SDK into feature parity with the Java and Go SDKs for handling large pipeline options, using an identical pattern previously implemented in the Go SDK.

🧠 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

@Mathdee
Copy link
Author

Mathdee commented Jan 22, 2026

All linting and integration checks are passing. Ready for review

@github-actions
Copy link
Contributor

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).

@claudevdm
Copy link
Collaborator

@shunping can you take a pass at this since you have more context?

@shunping
Copy link
Collaborator

Ack! Will do

// Assumes the options string is JSON formatted.
//
// Stores the file name in question in PIPELINE_OPTIONS_FILE for access by the SDK.
func MakePipelineOptionsFileAndEnvVar(options string) (string, error) {
Copy link
Collaborator

@shunping shunping Jan 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason to redefine this function? I see we already have that at

func MakePipelineOptionsFileAndEnvVar(options string) error {
, and we already imported the Go package in this boot.go at
"github.com/apache/beam/sdks/v2/go/container/tools"

if optionsFile, err := MakePipelineOptionsFileAndEnvVar(options); err != nil {
logger.Fatalf(ctx, "Failed to create a pipeline options file: %v", err)
} else {
os.Setenv("PIPELINE_OPTIONS_FILE", optionsFile)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In either the original MakePipelineOptionsFileAndEnvVar or your own copy (which seems to be unnecessary), the environment variable is already set. I think we don't need to do that again here.


pipeline_options_dict = _load_pipeline_options(options_json)

#pipeline_options_dict = _load_pipeline_options(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove unnecessary comments.

// (3) Invoke python

os.Setenv("PIPELINE_OPTIONS", options)
//Commented out -->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean up comments

//Commented out -->
//os.Setenv("PIPELINE_OPTIONS", options)

//To prevent crashes if options > ARG_MAX -->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you follow the comment style of this file to polish your comment here?

Something like:

// Write the JSON string of pipeline options into a file to prevent `argument list too long` error.

// --> Write the large JSON content into a file on disk
// --> environment only receives the short filename
if optionsFile, err := MakePipelineOptionsFileAndEnvVar(options); err != nil {
logger.Fatalf(ctx, "Failed to create a pipeline options file: %v", err)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency, could we use the same error message as Java and GO Sdks?

if err := tools.MakePipelineOptionsFileAndEnvVar(options); err != nil {
logger.Fatalf(ctx, "Failed to load pipeline options to worker: %v", err)

if err := tools.MakePipelineOptionsFileAndEnvVar(options); err != nil {
logger.Fatalf(ctx, "Failed to load pipeline options to worker: %v", err)

Copy link
Collaborator

@shunping shunping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for submitting the PR. Please check out my inline comments.

@Mathdee
Copy link
Author

Mathdee commented Jan 30, 2026

@shunping I saw the re-run failed again, so I dug into the logs. It looks like it's hitting the exact same timeout (DEADLINE_EXCEEDED) in test_builtin_combines.
Since that test is totally unrelated to the pipeline options logic (and the other 7,610 tests passed), this seems like a flake in the test environment.
Is there a way to merge despite this, or should we try triggering it one more time?

@shunping
Copy link
Collaborator

Let's give it another try. :)

@Mathdee
Copy link
Author

Mathdee commented Jan 30, 2026

All checks passed! Ready for final review/merge when you are. Thanks again @shunping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request]: Support large pipeline options in Python SDK

3 participants