Skip to content

[Doc][Umbrella] Walk through documentation and validate documented functionality for 0.4 #1283

Closed
4 of 4 issues completed

Description

@wenjin272

Description

As planned in the community sync, we will run a documentation walkthrough on October 21–25, 2026, ahead of the Flink Agents 0.4 release targeted for the end of October.

This umbrella issue tracks the walkthrough and any problems found along the way. It builds on the documentation improvements tracked in #1225.

What to validate

  • Documentation correctness: Check that explanations, API names, configuration options, prerequisites, commands, code snippets, and links are accurate and up to date for 0.4.
  • Consistency across documents: Check that concepts, terminology, examples, defaults, and support boundaries agree across tutorials, feature guides, and reference pages, including Java, Python, and YAML where applicable.
  • Documented functionality: Follow the documented steps and run the examples to verify that users can actually use the features as described. Check setup, execution, and expected results, and identify missing steps or implementation bugs.

Participants

@wenjin272, @yunfengzhou-hub, @joeyutong, and @eemario will participate. Other contributors are very welcome to join!

Reporting and fixing problems

  • Feel free to submit a hotfix PR directly for straightforward fixes and link it to this umbrella issue.
  • Alternatively, create a sub-issue under this umbrella to track a problem that needs discussion or follow-up. Include the affected documentation, reproduction steps where applicable, and expected versus actual behavior.
  • If a problem is already tracked, link the existing issue or PR to avoid duplicating work.

Bug fixes and documentation improvements can still be included in 0.4 during the freeze; new features will be considered for the next release.

Activity

  1. added
    tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.
    priority/majorDefault priority of the PR or issue.
    on Oct 20, 2026
  2. sangkyoonnam commented on Oct 21, 2026

    @sangkyoonnam
    Contributor

    Filed #1309 from the walkthrough: when a CEL Action trigger condition (#821) leaves an input without a matching Action, the next input already queued for the same key can stay unprocessed on continuation execution (JDK 21+) or with serial execution. The fix and a regression test are in #1310.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    fixVersion/0.4.0priority/majorDefault priority of the PR or issue.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions