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
Describe the bug
After upgrading from permitio/opal-client:0.7.15 to permitio/opal-client:0.7.16, triggering a data update via the API results in an error.
To Reproduce
Trigger a data update via API: curl -XPOST http://localhost:7766/data-updater/trigger
The first attempt works fine with response {"status": "ok"}.
However, the second attempt fails with the response {"detail":"Failed to update data"} and the following logs:
opal_client_1 | 2025-02-14T06:13:24.792695+0000 | 17 | opal_client.data.api | INFO | triggered policy data update from api
opal_client_1 | 2025-02-14T06:13:24.793278+0000 | 17 | opal_client.data.api |ERROR | Error during data update: object NoneType can't be used in 'await' expression
opal_client_1 | 2025-02-14T06:13:24.793762+0000 | 17 | uvicorn.protocols.http.httptools_impl | INFO | 192.168.0.1:42128 - "POST /data-updater/trigger HTTP/1.1" 500
Describe the bug
After upgrading from permitio/opal-client:0.7.15 to permitio/opal-client:0.7.16, triggering a data update via the API results in an error.
To Reproduce
curl -XPOST http://localhost:7766/data-updater/trigger
The settings used were:
https://github.com/permitio/opal/blob/master/docker/docker-compose-example.yml
The following error occurs in the opal_client.data.api module:
The issue seems to be triggered by the _handle_policy_data_update function in the opal_client/data/api.py file:
The error seems related to the tracing logic, as shown in the following code in opal-common/monitoring/tracing_utils.py:
Expected behavior
The data update should trigger successfully and return the expected response without errors.
Screenshots
If applicable, add screenshots to help explain your problem.
OPAL version
The text was updated successfully, but these errors were encountered: