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
An axum application that uses openstack_sdk may face networking issues under MacOS when a single request handler sends multiple requests to the same server.
So far I have seen this during development when keystone is running under uwsgi on localhost and the app runs also on the localhost and send multiple requests. Tuning timeouts, enabling keepalive doesn't seem to make any influence. The only thing so far that helped was setting .pool_max_idle_per_host(0) on the client. However it feels that some general networking configuration is responsible for that.
On Linux this issue is not reproducible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
An axum application that uses openstack_sdk may face networking issues under MacOS when a single request handler sends multiple requests to the same server.
So far I have seen this during development when keystone is running under uwsgi on localhost and the app runs also on the localhost and send multiple requests. Tuning timeouts, enabling keepalive doesn't seem to make any influence. The only thing so far that helped was setting
.pool_max_idle_per_host(0)on the client. However it feels that some general networking configuration is responsible for that.On Linux this issue is not reproducible.
When occured openstack_sdk returns
openstack_sdk::api::error::ApiError::Client(client error: communication with openstack: error sending request for url, https://github.com/gtema/openstack/blob/main/openstack_sdk/src/api/error.rs#L51) errorReference:
Beta Was this translation helpful? Give feedback.
All reactions