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

#667 Error setting resourceFile: "Maximum call stack size exceeded" #773

Merged
merged 6 commits into from
Oct 6, 2021

Conversation

cima
Copy link
Contributor

@cima cima commented Jul 5, 2021

  • Preventing the infinite recursion by not translating warning about missing translation.

Please see and reopen issue #667 . What I provide here is fix of catastrphic failure in infinite recursion. It doesn't fix translation in compilation systems like webpack.

…xceeded"

 + Preventing the infinite recustion by not translating warning about missing translation.
node/internal.ts Outdated Show resolved Hide resolved
node/internal.ts Outdated Show resolved Hide resolved
@anatolybolshakov
Copy link
Contributor

@cima thanks for the fix here!
Could you please take a look at suggestions above and bump patch number of package version also?

@anatolybolshakov anatolybolshakov self-assigned this Sep 16, 2021
- Getting rid of unnecessary escaping backslash
@ghost
Copy link

ghost commented Sep 16, 2021

CLA assistant check
All CLA requirements met.

@cima
Copy link
Contributor Author

cima commented Sep 16, 2021

@anatolybolshakov I have taken a look at it and I wasn't happy with my own code. I've just add a brief unit test to be able to put breakpoint and debug and discovered two things:

  1. Backslash is not necessary at all as it is in backtics that translates to double quotes so the direct apostrophe is not interfering with compiler when parsing a string quotation.
  2. The parameter in formated string was totally wrong. It supposed to be key not path.

I have compile it, run tests and the fix is pushed in the branch.

Package lock remains almost untouched as no version has been changed.
The missing file lib.json is simulated via resporting nonexistent file via mockery.
Copy link
Contributor

@anatolybolshakov anatolybolshakov left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for contribution!

@anatolybolshakov anatolybolshakov requested a review from a team October 1, 2021 13:28
@anatolybolshakov anatolybolshakov removed their assignment Oct 5, 2021
@AnnaOpareva
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@AnnaOpareva AnnaOpareva merged commit ac8458c into microsoft:master Oct 6, 2021
fullstackinfo pushed a commit to fullstackinfo/azure-pipelines-task-lib that referenced this pull request Aug 17, 2024
…xceeded" (microsoft#773)

* microsoft#667 Error setting resourceFile: "Maximum call stack size exceeded"

 + Preventing the infinite recustion by not translating warning about missing translation.

* Wrong variable in warning output.

- Getting rid of unnecessary escaping backslash

* Bumping package version

* Missing Localization test using mockery

The missing file lib.json is simulated via resporting nonexistent file via mockery.

Co-authored-by: Martin Šimek <martin.simek@digiteqautomotive.com>
Co-authored-by: Anatoly Bolshakov <anatoly.bolshakov@akvelon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants