Skip to content

Conversation

@satvu
Copy link
Member

@satvu satvu commented May 8, 2023

Issue describing the changes in this PR

resolves #9104

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Depends on #94 in the protobuf repo.

@satvu satvu force-pushed the satvu/retry-options branch from 9efa002 to dc9592e Compare May 17, 2023 18:09
@satvu satvu marked this pull request as ready for review May 17, 2023 18:09
@satvu satvu requested a review from a team as a code owner May 17, 2023 18:09
// populate retry options if json string representation is provided
if (!string.IsNullOrEmpty(rawFunction.RetryOptions))
{
function.Retry = JObject.Parse(rawFunction.RetryOptions).ToObject<RetryOptions>();
Copy link
Member

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)?

Copy link
Member Author

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));
Copy link
Member Author

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

@satvu satvu merged commit 428215c into dev May 24, 2023
@satvu satvu deleted the satvu/retry-options branch May 24, 2023 18:29
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.

Add support for Retry context for Worker Indexing

4 participants