Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27152

Show REST exceptions in the Symfony profiler

    Details

      Description

      When an REST exception occurs, it is not shown in the Symfony profiler. It is easily reproduced by requesting a content that doesn't exist, like /api/ezp/v2/content/objects/77777. The profiler for the failing request will have 0 exceptions reported, while one did occur.

      REST exceptions should be listed like any other exception.

        Issue Links

          Activity

          Nuno Oliveira (Inactive) created issue -
          Nuno Oliveira (Inactive) made changes -
          Field Original Value New Value
          Component/s Platform > Profiler > Full stack [ 13349 ]
          Nuno Oliveira (Inactive) made changes -
          Link This issue relates to CS-6080 [ CS-6080 ]
          Nuno Oliveira (Inactive) made changes -
          Link This issue relates to EZP-24853 [ EZP-24853 ]
          Nuno Oliveira (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Nuno Oliveira (Inactive) made changes -
          Description When debugging new components (e.g. a new FieldType), it is not possible to see the full stack trace of the actual error, only the latest trace. The problem is that the exception is caught in the ez rest code and retrown. When the code is retrown the earlier stack trace is no longer available. When debugging new components (e.g. a new FieldType), it is not possible to see the full stack trace of the actual error, only the latest trace. The problem is that the exception is caught in the ez rest code and retrown. When the code is retrown the earlier stack trace is no longer available.

          Please improve that behavior, so that the whole stack trace is available for inspection.
          André Rømcke made changes -
          Status Confirmed [ 10037 ] InputQ [ 10001 ]
          Damien Pobel (Inactive) made changes -
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Status InputQ [ 10001 ] Backlog [ 10000 ]
          Bertrand Dunogier made changes -
          Description When debugging new components (e.g. a new FieldType), it is not possible to see the full stack trace of the actual error, only the latest trace. The problem is that the exception is caught in the ez rest code and retrown. When the code is retrown the earlier stack trace is no longer available.

          Please improve that behavior, so that the whole stack trace is available for inspection.
          When an REST exception occurs, it is not shown in the Symfony profiler. It is easily reproduced by requesting a content that doesn't exist, like {{/api/ezp/v2/content/objects/77777}}. The profiler for the failing request will have 0 exceptions reported, while one did occur.

          REST exceptions should be listed like any other exception.
          Bertrand Dunogier made changes -
          Summary Enhance REST output when debugging new components Show REST exceptions in the Symfony profiler
          Bertrand Dunogier made changes -
          Status Backlog [ 10000 ] Development [ 3 ]
          Bertrand Dunogier made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Bertrand Dunogier made changes -
          Status Development Review [ 10006 ] Backlog [ 10000 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 103303 ] EZEE Development Workflow [ 108148 ]

            People

            • Assignee:
              Bertrand Dunogier
              Reporter:
              Nuno Oliveira (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: