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

Lazify cloud request engine properties #25

Conversation

Riabkov
Copy link
Contributor

@Riabkov Riabkov commented Oct 9, 2023

No description provided.

@justadreamer
Copy link
Contributor

We also need to verify a couple more scenarios with unit/integration tests. Please use mocking/injection techniques to write these tests. We need to simulate the failing cloud call (a call to cloud.51degrees.com)

  1. If the call to the cloud fails - we should not get an exception on pipeline construction, for the properties are now lazy, but should get it when we call Process() function
  2. if we construct the pipeline with the SuppressProcessExceptions=true, we should not get the exceptions when cloud.51degrees.com is unavailable, but they should be logged and added into the flowData.errors

Copy link
Contributor

@justadreamer justadreamer left a comment

Choose a reason for hiding this comment

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

a couple changes in code (to prevent race conditions) + a couple unhappy path scenario tests need to be added

Copy link
Contributor

@justadreamer justadreamer left a comment

Choose a reason for hiding this comment

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

a couple more amendments to the tests would be nice

@Riabkov Riabkov requested a review from justadreamer October 11, 2023 13:36
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.

3 participants