Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-2470

Add a timeout the NuxeoDrive.GetChangeSummary call

    Details

      Description

      Add a timeout the NuxeoDrive.GetChangeSummary call to prevent such huge times as reported in the attached CSV file. The interesting column in "Event Label" which is the number of seconds the call take to complete.

      Values are sorted in descendant order (longer -> shorter calls). Some are really huge and should be discared. I am not sure how to get such values though. Maybe the computer that goes sleeping?

      In any cases, as we are polling for changes on a regular basis (defined by the delay option, defaults to 30 seconds), it makes sense to limit with a timeout the time that call could take.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 30 minutes
                30m

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.