Updating Russian translation#70366
Open
puzzle-rpa-team wants to merge 71 commits into
Open
Conversation
Co-authored-by: renat-sagut <renat.sagut@gmail.com>
Co-authored-by: renat-sagut <renat.sagut@gmail.com>
Co-authored-by: renat-sagut <renat.sagut@gmail.com>
# Conflicts: # .github/CODEOWNERS # airflow-core/src/airflow/ui/public/i18n/locales/ru/assets.json # airflow-core/src/airflow/ui/public/i18n/locales/ru/common.json # airflow-core/src/airflow/ui/public/i18n/locales/ru/dashboard.json
Co-authored-by: renat-sagut <renat.sagut@gmail.com>
Co-authored-by: renat-sagut <renat.sagut@gmail.com>
…8929) (apache#68940) * Correct the example and docstring for the coordinators * Guard the config.yml coordinators example against drift (cherry picked from commit 4aafb95)
…pache#68842) (apache#68948) (cherry picked from commit 31f7ba7) Co-authored-by: Hasnain Raza <4294680+HasnainRaz@users.noreply.github.com>
…onAPI` (apache#68980) (apache#68982) PR apache#68840 fixed an issue where exceptions thrown by the FastAPI lifecycle hook were swallowed. In doing so, it exposed a pre-existing problem where the lifecycle hook couldn't run when the JWT secret was not provided. As the `InProcessExecutionAPI` overrides auth, it doesn't need a JWT secret, and we certainly don't want to start crashing processes that previously ran fine as a result of a missing secret that we don't need. This commit stubs out the registered `JWTValidator` in the FastAPI app created for the `InProcessExecutionAPI`. This is done in an isolated services registry to ensure we don't leak this into any real app instantiations. (cherry picked from commit e886dfd) Co-authored-by: Nick Stenning <nick@whiteink.com>
…sistency (apache#68978) (apache#68987) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
…pache#68977) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
Co-authored-by: Andrew Chang <69671930+Andrushika@users.noreply.github.com>
) (cherry picked from commit 4b92536) Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
…`state-store clean` (apache#69316) (apache#69322) The command added in 3.3.0rc1 repeated "state store" in both the group and the subcommand. Rename it to `airflow state-store clean`, mirroring `airflow db clean`. The old name only shipped in 3.3.0rc1, so renaming before GA keeps a single stable name for 3.3.0. Also make the help text and docs accurate about the current behavior: the command intentionally supports the metastore backend only and skips custom (worker-side) backends, and the docstring now explains why (correct cleanup of a worker-side backend needs to delete the DB refs and the backend data in order, which has to run where the backend's dependencies live, not on the server-side CLI). Fix a wrong class name (`MetastoreStateBackend` -> `MetastoreBackend`) in the docs. (cherry picked from commit 71be2b4) Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…) (apache#69318) The page header in the details panel is a HeaderCard, which clips its own overflow. As a flex child of the details column it could shrink when vertical space is tight — most visibly on Dag pages, whose header has the most rows — cropping its content so the tabs appear to overlap the scheduling information. Pinning its flex size keeps the header at its natural height and lets the scrollable tab content take the reduced space instead. (cherry picked from commit b6cb7c6) closes: apache#69247 Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
…pper (apache#69311) (apache#69326) * Fix asset event ingestion crash for Dags using FixedKeyMapper Core FixedKeyMapper's generated __init__ never called PartitionMapper.__init__, so instances had no max_downstream_keys attribute. Since the Execution API reads mapper.max_downstream_keys with no surrounding error handling when queuing partitioned Dag runs, every producer task emitting an asset event consumed by a Dag with a bare FixedKeyMapper failed to record SUCCESS and became a zombie. * fixup! Fix asset event ingestion crash for Dags using FixedKeyMapper (cherry picked from commit 0643e33) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
Co-authored-by: raphaelauv <raphaelauv@users.noreply.github.com>
puzzle-rpa-team
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
potiuk and
vatsrahul1001
as code owners
July 24, 2026 08:28
boring-cyborg
Bot
added
area:dev-tools
area:translations
area:UI
jason810496
reviewed
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Russian translations. This PR, in part, continues where @renat-sagut 's closed PR left off (#67073). For example, it adds plural form "many" they added as well.
Thanks to all reviewers for their time in advance!
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.