-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ValueError: 'fe80::1%lo0' does not appear to be an IPv4 or IPv6 address" error when running notebook #3754
Comments
Can you check the output of: import socket
socket.getaddrinfo('localhost', 8888, 0, socket.SOCK_STREAM) Is that address in there? If so, can you figure out where it's coming from? E.g. is it in If we can't figure this out quickly, or if it looks like this might be a more common problem for mac users, we can disable the check by default for the 5.6 release and debug it more afterwards. |
Here is the output that I get when running 5.5.0 (because I can't actually start the notebook server on master): [(<AddressFamily.AF_INET6: 30>,
<SocketKind.SOCK_STREAM: 1>,
6,
'',
('::1', 8888, 0, 0)),
(<AddressFamily.AF_INET6: 30>,
<SocketKind.SOCK_STREAM: 1>,
6,
'',
('fe80::1%lo0', 8888, 0, 1)),
(<AddressFamily.AF_INET: 2>,
<SocketKind.SOCK_STREAM: 1>,
6,
'',
('127.0.0.1', 8888))] The top of my
That's macOS defaults... |
OK, if this is going to affect lots of Mac users, let's disable the check, do a release, and try to figure it out for 5.7. Can you investigate more what this |
(PR #3766 disables the host check for now) |
Disable the host check for 5.6 because of gh-3754
Thanks, but it was a workaround, not a fix. I still want to investigate this and find a proper fix so we can have the check enabled by default. |
Understood, but I thought #3767 was intended to track a longer term fix |
I've just done some reading and the |
It works for me 👍 |
Thanks. Let's land that again and see how it goes in master, then. |
Follow up from #3751 (comment):
I'm getting a strange error when trying to run the notebook against master:
According to @takluyver, likely related to #3714:
The text was updated successfully, but these errors were encountered: