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

[Direct Edit] Handle HTTPError 404 (Not Found) errors

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: NoFixVersionApplicable
    • Fix Version/s: 5.2.0
    • Component/s: Direct Edit

      Description

      Sentry Issue: NUXEO-DRIVE-2T8

      HTTPError: 404 Client Error: Not Found for url: https://<SUBHOST>.us-west-2.amazonaws.com/...
        File "nuxeo/client.py", line 305, in request
        File "requests/models.py", line 943, in raise_for_status
      
      HTTPError: HTTPError(404), error: b'<?xml version="1.0" encoding="UTF-8"?>\n<Error><Code>NoSuchVersion</Code><Message>The specified version does not exist.</Message><Key>...</Key><VersionId>...</VersionId><RequestId>...</RequestId><HostId>...</HostId></Error>', server trace: None
        File "nxdrive/direct_edit.py", line 599, in edit
        File "nxdrive/direct_edit.py", line 585, in edit
        File "nxdrive/direct_edit.py", line 525, in _prepare_edit
        File "nxdrive/direct_edit.py", line 351, in _download
        File "nxdrive/client/remote_client.py", line 339, in download
        File "nuxeo/client.py", line 308, in request
      

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h

                    PagerDuty

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