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

fix(core): fix flaky durable providers #11666

Closed

Conversation

KamalAman
Copy link

@KamalAman KamalAman commented May 25, 2023

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #11664

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Comment on lines +91 to +92
// How to test this?
// const constructorStub = sinon.stub(DurableService, 'constructor').throws(new Error('test error'));
Copy link
Author

@KamalAman KamalAman May 25, 2023

Choose a reason for hiding this comment

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

@micalevisk any suggestions on how to use sinon to stub the constructor to throw an error for very first request?

I cannot find any references to that and I don't know if there is a clean way to do that. Any suggestions?

Copy link
Member

@micalevisk micalevisk May 25, 2023

Choose a reason for hiding this comment

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

I don't know either :/ I will try to find something later

Copy link
Member

@micalevisk micalevisk left a comment

Choose a reason for hiding this comment

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

can you please remove the yarn.lock

@KamalAman
Copy link
Author

i'll try to get back to this over the weekend and close it off

@dberardo-com
Copy link

@KamalAman @kamilmysliwiec what was the reason why this PR was never accepted ? i reopened an issue on the matter: #13953

@KamalAman
Copy link
Author

@dberardo-com yeah this is an annoying bug. I never figured out how to test it. Anyone who wants to pick it up, please feel free to take this over.

@kamilmysliwiec
Copy link
Member

#14133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants