You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "/odoo/src/odoo/http.py", line 2061, in __call__
response = request._serve_db()
File "/odoo/src/odoo/http.py", line 1649, in _serve_db
return service_model.retrying(self._serve_ir_http, self.env)
File "/odoo/src/odoo/service/model.py", line 133, in retrying
result = func()
File "/odoo/src/odoo/http.py", line 1676, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "/odoo/external-src/rest-framework/extendable_fastapi/fastapi_dispatcher.py", line 19, in dispatch
return super().dispatch(endpoint, args)
File "/odoo/external-src/rest-framework/fastapi/fastapi_dispatcher.py", line 34, in dispatch
if self.inner_exception:
AttributeError: 'FastApiDispatcher' object has no attribute 'inner_exception'
This is with an up-to-date fastapi addon on 16.0
The text was updated successfully, but these errors were encountered:
It looks to me that if the app at line 33 does not yield anything for the response you won't have the inner_exceptionattribute set. That attribute is initialized in the wrong place IMO. It should go to __init__.
I'll open a PR.
simahawk
changed the title
fastapi: object has no attribute inner_exception
[16.0] fastapi: object has no attribute inner_exception
Jan 9, 2025
simahawk
added a commit
to camptocamp/rest-framework
that referenced
this issue
Jan 9, 2025
It looks to me that if the app does not yield anything for the response
you might encour into an attribute error as the attribut won't be defined yet.
In general, the init method sounds like a better place for shared attributes.
FixesOCA#487
We are seeing this stack trace in the logs:
This is with an up-to-date fastapi addon on 16.0
The text was updated successfully, but these errors were encountered: