Uploaded image for project: 'Nuxeo Python Client'
  1. Nuxeo Python Client
  2. NXPY-213

Handle incomplete serialized HTTP error

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 5.1.0
    • Component/s: Core

      Description

      Issue

      Sentry Issue: NUXEO-DRIVE-4WH

      HTTPError: 500 Server Error: Erreur Interne de Servlet for url: $HOST/nuxeo/api/v1/upload/batchId-6605fcae-7797-466b-9030-02a3d3e1edc8/0/execute/NuxeoDrive.CreateFile
        File "nuxeo\client.py", line 305, in request
        File "requests\models.py", line 943, in raise_for_status
      
      HTTPError: HTTPError(-1), error: None, server trace: None
      (9 additional frame(s) were not displayed)
      ...
        File "nxdrive\client\uploader\__init__.py", line 392, in link_blob_to_doc
        File "nxdrive\client\remote_client.py", line 263, in execute
        File "nxdrive\client\remote_client.py", line 259, in execute
        File "nuxeo\operations.py", line 199, in execute
        File "nuxeo\client.py", line 308, in request
      
      Unknown error
      

      Analysis

      It happens when the serialized error does not contain a status.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 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 - 1 hour, 30 minutes
                  1h 30m

                    PagerDuty

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