-
Notifications
You must be signed in to change notification settings - Fork 473
Add retry policy support for worker-indexing scenarios #9265
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
Conversation
9efa002 to
dc9592e
Compare
src/WebJobs.Script.Grpc/MessageExtensions/GrpcMessageConversionExtensions.cs
Outdated
Show resolved
Hide resolved
src/WebJobs.Script.Grpc/MessageExtensions/GrpcMessageConversionExtensions.cs
Outdated
Show resolved
Hide resolved
| // populate retry options if json string representation is provided | ||
| if (!string.IsNullOrEmpty(rawFunction.RetryOptions)) | ||
| { | ||
| function.Retry = JObject.Parse(rawFunction.RetryOptions).ToObject<RetryOptions>(); |
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.
Oh, we still have the Json string for the retry option data ? I See this is existing code. Are we planning to make this prop obsolete and recommend language owners to use the strongly typed version (The new property we recently added to proto file)?
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.
The strongly typed version added here is only for worker-indexing scenarios - I'm not sure if host indexing (or other providers like extension loader or custom providers from partner services) are still using the legacy bits.
| if (!retryOptions.MinimumInterval.HasValue) | ||
| { | ||
| throw new ArgumentNullException(nameof(retryOptions.DelayInterval)); | ||
| throw new ArgumentNullException(nameof(retryOptions.MinimumInterval)); |
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.
@kshyju thanks to your suggestion of testing the error message :) found a bug
Issue describing the changes in this PR
resolves #9104
Pull request checklist
release_notes.mdAdditional information
Depends on #94 in the protobuf repo.