Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observability i18n fixes #72984

Merged
merged 2 commits into from
Jul 27, 2020
Merged

Observability i18n fixes #72984

merged 2 commits into from
Jul 27, 2020

Conversation

smith
Copy link
Contributor

@smith smith commented Jul 22, 2020

  • Format xpack.apm.percentOfParent correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
  • Format xpack.infra.logs.customizeLogs.textSizeRadioGroup correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.

Fixes #72794

* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
@smith smith added bug Fixes for quality problems that affect the customer experience release_note:fix v7.9.0 labels Jul 22, 2020
@smith smith requested review from Bamieh and a team July 22, 2020 22:35
@sorenlouv
Copy link
Member

sorenlouv commented Jul 23, 2020

How can this continue to happen? I thought this PR would prevent it?

@smith
Copy link
Contributor Author

smith commented Jul 26, 2020

@elasticmachine merge upstream

@smith
Copy link
Contributor Author

smith commented Jul 26, 2020

How can this continue to happen? I thought this PR would prevent this?

@Bamieh any idea how this could have happened? I'm pretty sure these problems already existed when the check was added, so maybe we weren't checking for problems that were already there.

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Member

@Bamieh Bamieh left a comment

Choose a reason for hiding this comment

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

These shouldnt have passed the i18n_check given the new check i've added does parse every message and fails if the formatting is incorrect. I'll check how this happened and fix any issues to prevent it from happening again. Thanks lgtm 👍

@smith smith merged commit 76150a4 into elastic:master Jul 27, 2020
@smith smith deleted the nls/jp-fixes branch July 27, 2020 13:20
kibanamachine pushed a commit that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
@kibanamachine
Copy link
Contributor

💚 Backport successful

The PR was backported to the following branches:

smith added a commit to smith/kibana that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
smith added a commit to smith/kibana that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
smith added a commit that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
smith added a commit that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
smith pushed a commit that referenced this pull request Jul 27, 2020
* Format `xpack.apm.percentOfParent` correctly so the transactions page in APM doesn't crash. In English it reads like, "(X% of transaction)". I'm not sure what the intention of the changed translation is, but I've changed it to be the equivalent of "(X% transaction)". A correction to the Japanese form here would be appreciated, but this fixes the crash and gets the message across.
* Format `xpack.infra.logs.customizeLogs.textSizeRadioGroup` correctly. This was not causing the whole logs page to crash, but was causing an error in the JS console.
Bamieh added a commit that referenced this pull request Jul 29, 2020
Bamieh added a commit that referenced this pull request Jul 29, 2020
Bamieh added a commit that referenced this pull request Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience release_note:fix v7.9.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

APM trace screen is blank
5 participants