Fix 'occured' -> 'occurred' typos across Python, Go, and Java SDKs

[SAY-5]

Trivial spelling fix in three source files.

• sdks/python/apache_beam/runners/worker/data_sampler.py — 2 occurrences on dataclass field comments (transform_id, instruction_id).
• sdks/go/pkg/beam/runners/prism/internal/engine/teststream.go — internal code comment.
• sdks/java/testing/nexmark/src/main/java/org/apache/beam/sdk/nexmark/sources/generator/Generator.java — Javadoc on the eventTimestamp field.

No functional changes.

[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 minor typographical errors found in comments within the codebase. These changes are purely cosmetic and do not impact the functionality or performance of the SDKs.

Highlights

• Spelling Corrections: Corrected the misspelling of 'occured' to 'occurred' in code comments and documentation across Python, Go, and Java SDKs.

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

[SAY-5]

The failing job is beam_PreCommit_Python_Examples (3.10) on an assertion inside apache_beam/examples/cookbook/ordered_window_elements/batch_test.py::test_long_slide. The other four Python versions (3.11/3.12/3.13/3.14) pass on the same commit, and this PR only touches three code comments (data_sampler.py, teststream.go, Generator.java) — none of which are exercised by that test. Looks like a pre-existing flake on 3.10. Happy to retry or rebase if helpful.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers