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

Hotfix: Stop using vscode-nls for some key localizations #10773

Merged
merged 3 commits into from
Jul 12, 2022

Conversation

sadasant
Copy link
Contributor

@sadasant sadasant commented Jul 12, 2022

This PR undoes localization on some localization keys that are breaking the related features of the vscode-jupyter extension.

Last week we released version 6.100 of the vscode-jupyter. Unbeknown to us, the extension shipped with some of its features broken. Customers began reporting that some of the commands, like the one for restarting kernels and the one for interrupting kernels, were missing from the UI.

In the developer tools of VSCode (version 1.69.0 and above), when 6.100 is loaded, we see a large influx of error messages:

Screen Shot 2022-07-11 at 8 17 20 PM

While debugging, we realized that:

  • Version 5.100 does not have the issue, even though it shipped with the localization code (though it didn't ship with the new localizations themselves, only with the code that uses them).
  • Version 6.100 does not include localization changes to the related localization IDs.
  • The problem doesn't reproduce building a .VSIX of the extension locally.
  • Changing the problematic entries in the package.json to use existing keys pointing to other localized phrases bypasses the problem.
  • Changing the problematic entries in the package.json to use plain strings also bypasses the problem.

This PR aims to replace all of the problematic localizations for plain text English strings in order to deliver a hotfix for 6.100.

The changes included in this PR do make all of the errors shown in the screenshot go away.

(Once released)
Fixes microsoft/vscode#154955

@sadasant sadasant requested a review from a team as a code owner July 12, 2022 00:26
@sadasant sadasant self-assigned this Jul 12, 2022
news/2 Fixes/10752.md Outdated Show resolved Hide resolved
Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>
Copy link
Contributor

@DonJayamanne DonJayamanne left a comment

Choose a reason for hiding this comment

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

Probably consider re-wording the news entry, not necessary, just a suggestion

@sadasant
Copy link
Contributor Author

I have also made an issue to follow up on the re-introduction of these localizations: #10774

@sadasant sadasant merged commit 9caa26d into microsoft:main Jul 12, 2022
@sadasant sadasant deleted the localization-issue-july branch July 12, 2022 00:40
sadasant added a commit to sadasant/vscode-jupyter that referenced this pull request Jul 12, 2022
…0773)

* Hotfix: Stop using vscode-nls for some key localizations

* news

* Update news/2 Fixes/10752.md

Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>

Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>
sadasant added a commit that referenced this pull request Jul 12, 2022
…0775)

* Hotfix: Stop using vscode-nls for some key localizations (#10773)

* Hotfix: Stop using vscode-nls for some key localizations

* news

* Update news/2 Fixes/10752.md

Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>

Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>

* Other changes needed for the hotfix release

* 2022.6.101 to 2022.6.110

Co-authored-by: Don Jayamanne <don.jayamanne@outlook.com>
sadasant added a commit that referenced this pull request Jul 14, 2022
sadasant added a commit that referenced this pull request Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants