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

test vrf listener processes old requests on start up #11554

Merged
merged 8 commits into from
Feb 13, 2024

Conversation

jinhoonbang
Copy link
Contributor

  • test vrf listener processes old requests on start up

Copy link
Contributor

I see that you haven't updated any README files. Would it make sense to do so?

Copy link
Contributor

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

ibrajer
ibrajer previously approved these changes Jan 11, 2024
Copy link
Contributor

@ibrajer ibrajer left a comment

Choose a reason for hiding this comment

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

LGTM, the test is relatively simple but covers the exact use case.

Perhaps adding another one in the future like this:

  • send multiple requests before the node shuts down
  • shut down the node
  • send another batch of requests while the node is down
  • restart the node
  • send another batch of new requests
  • validate that all three batches were successfully processed and all requests are fulfilled

Not sure if this test (or a variation of it) would be beneficial or not, but the idea here is to hunt down any potential issues with queueing requests and the node processing that queue.

@jinhoonbang
Copy link
Contributor Author

LGTM, the test is relatively simple but covers the exact use case.

Perhaps adding another one in the future like this:

  • send multiple requests before the node shuts down
  • shut down the node
  • send another batch of requests while the node is down
  • restart the node
  • send another batch of new requests
  • validate that all three batches were successfully processed and all requests are fulfilled

Not sure if this test (or a variation of it) would be beneficial or not, but the idea here is to hunt down any potential issues with queueing requests and the node processing that queue.

Thanks for reviewing this! Agreed on the suggested test use case. We discussed a similar test during one of the stand ups and decided to add it in QA integration test. it's not easy to add such tests in the integration tests here because the Application instance cannot be re-started once stopped.

@jinhoonbang jinhoonbang added this pull request to the merge queue Jan 11, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 11, 2024
@jinhoonbang jinhoonbang added this pull request to the merge queue Jan 16, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 16, 2024
@jinhoonbang jinhoonbang added this pull request to the merge queue Jan 19, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 19, 2024
@jinhoonbang jinhoonbang added this pull request to the merge queue Jan 19, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 19, 2024
@cl-sonarqube-production
Copy link

@jinhoonbang jinhoonbang requested a review from ibrajer February 13, 2024 16:17
@jinhoonbang jinhoonbang added this pull request to the merge queue Feb 13, 2024
Merged via the queue into develop with commit 453153d Feb 13, 2024
93 checks passed
@jinhoonbang jinhoonbang deleted the VRF-720-test-various-scenarios-that-need-replays branch February 13, 2024 16:52
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.

2 participants