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
_get_default_route is failing to find the /proc/net/route file - it doesn't exist on OSX, but the log.error is never seen, None is returned, and used in get_socket, which is an invalid input.
Current unit test confirms that the option is set post-initialize, but not whether the resulting client works. I did not see a relevant integration test for this.
I don't know if the right answer is to add a condition from sys.platform and use the equivalent of something like one of these for OSX:
We often develop on OSX, and use a common settings file to initialize the library.
With the setting of use_default_route on OSX, we trigger this easily-reproducible failure:
_get_default_route is failing to find the
/proc/net/route
file - it doesn't exist on OSX, but thelog.error
is never seen,None
is returned, and used inget_socket
, which is an invalid input.Current unit test confirms that the option is set post-initialize, but not whether the resulting client works. I did not see a relevant integration test for this.
I don't know if the right answer is to add a condition from
sys.platform
and use the equivalent of something like one of these for OSX:netstat -rn | grep 'default' | awk '{print $2}'
route -n get default | grep 'gateway' | awk '{print $2}'
The text was updated successfully, but these errors were encountered: