Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
  3. SENTRY-1765

CounterWait.update should be less strict

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Sentry
    • None

    Description

      CounterWait.update is called 3 times when HMSFollower. When it is called after each notification event processing, the input ID is older than what's in CounterWait, and exception is thrown.

      Should we remove the place that causes the issue? Or/And we allow older value as input, and not throw exception?

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue SENTRY-1669 HMSFollower should read current processed notification ID from database every time it runs

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          links to

          Web Link Code Review

          Activity

            People

              akolb Alex Kolbasov
              linaataustin Na Li
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: