[bug]: dispatch() returns exception object instead of HTTP response on error

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

In all four base view files, the dispatch() method catches exceptions, calls self.handle_exception(exc) to build a proper HTTP response, and then returns the raw Python exception object (exc) instead of the response it just built.

except Exception as exc:
    response = self.handle_exception(exc)
    return exc  # ← should be `return response`

The response variable is correctly built but then discarded. Django/DRF receives a bare exception object instead of an HttpResponse, so error responses from all inherited views are broken.

Affected files:

• apps/api/plane/app/views/base.py — BaseViewSet, BaseAPIView
• apps/api/plane/api/views/base.py — BaseAPIView
• apps/api/plane/license/api/views/base.py — BaseAPIView
• apps/api/plane/space/views/base.py — BaseViewSet, BaseAPIView

Steps to reproduce

1. Hit any endpoint that triggers an exception (e.g. request a non-existent resource to get a 404, or send invalid data to get a 400)
2. Observe that instead of a structured JSON error response, the framework receives a bare exception object

Environment

All environments

Browser

N/A (backend)

Variant

All

Version

All

Inspect the dispatch() methods in the four listed base view files, covering BaseViewSet and BaseAPIView variants. Reproduce an exception response using the issue's 404 or 400 examples, then verify that each affected method returns the constructed HTTP response and that structured error responses are restored.