-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[core-amqp] Refactor time units to milliseconds #4401
Conversation
Build is failing because Event Hubs needs to be updated. |
Seconding what @ShivangiReja said. |
Please see the PR description - "this PR is for core-amqp package only, once this PR is final and other Event Hub PRs in flight are through, can send another / update same PR to consume these changes from Event Hubs" This one's for |
But we can't merge this if it fails master right? We should never allow master to get into a state where it fails to build. |
Yes, GitHub will not allow PRs to be merged unless the conflicts and syntax/build errors are fixed. So it is automatically not allowed and we don't have to worry about these going into master. |
Ah, well then for what it's worth I think these changes look fine, I would wait to approve until the build is passing though. |
cc: @ramya-rao-a @chradek Merged in changes from #4400 and updated EventHubs to absorb the seconds -> milliseconds refactor in Also, it looks like there might be a bug with usage of |
typeof retryOptions.retryInterval === "number" | ||
? retryOptions.retryInterval / 1000 | ||
? retryOptions.retryInterval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesnt need any checks anymore. We should be able to say delayInMs: retryOptions.retryInterval
and expect core-amqp
to do all the checks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for other places that have this pattern
For more context refer to #4277
cc: @ramya-rao-a