{"action":"created","issue":{"url":"https://api.github.com/repos/garstka/idact/issues/8","repository_url":"https://api.github.com/repos/garstka/idact","labels_url":"https://api.github.com/repos/garstka/idact/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/garstka/idact/issues/8/comments","events_url":"https://api.github.com/repos/garstka/idact/issues/8/events","html_url":"https://github.com/garstka/idact/issues/8","id":393564569,"node_id":"MDU6SXNzdWUzOTM1NjQ1Njk=","number":8,"title":"Connecting to cluster fails on fresh windows installation","user":{"login":"grzanka","id":7374733,"node_id":"MDQ6VXNlcjczNzQ3MzM=","avatar_url":"https://avatars0.githubusercontent.com/u/7374733?v=4","gravatar_id":"","url":"https://api.github.com/users/grzanka","html_url":"https://github.com/grzanka","followers_url":"https://api.github.com/users/grzanka/followers","following_url":"https://api.github.com/users/grzanka/following{/other_user}","gists_url":"https://api.github.com/users/grzanka/gists{/gist_id}","starred_url":"https://api.github.com/users/grzanka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grzanka/subscriptions","organizations_url":"https://api.github.com/users/grzanka/orgs","repos_url":"https://api.github.com/users/grzanka/repos","events_url":"https://api.github.com/users/grzanka/events{/privacy}","received_events_url":"https://api.github.com/users/grzanka/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-12-21T19:20:09Z","updated_at":"2019-01-02T21:15:21Z","closed_at":null,"author_association":"COLLABORATOR","body":"I've tried to run idact on Windows 10 with freshly installed python 3.7 (using 64bit Anaconda).\r\n\r\nInstallation (`python -m pip install idact`) went well:\r\n![zrzut ekranu 4](https://user-images.githubusercontent.com/7374733/50359445-1261af80-055d-11e9-8978-2d49310fb09e.png)\r\n\r\nThen I've started new Jupyter Lab instance to add a cluster. Just for fun I've checked  what happens if user would blindly copy-paste code snippet from instruction and execute it.\r\n![zrzut ekranu 6](https://user-images.githubusercontent.com/7374733/50359522-4f2da680-055d-11e9-902a-267b41d5af3d.png)\r\n\r\nSome unfriendly stack trace appears which ends with:\r\n![zrzut ekranu 7](https://user-images.githubusercontent.com/7374733/50359542-61a7e000-055d-11e9-897f-64611ced5b1f.png)\r\n\r\nAs the system was fresh and SSH keys were installed I've tried this one, from main page of installation manual:\r\n![zrzut ekranu 8](https://user-images.githubusercontent.com/7374733/50359556-797f6400-055d-11e9-9ee1-1f6baaac43ef.png)\r\n\r\nit ended up in same error message:\r\n![zrzut ekranu 12](https://user-images.githubusercontent.com/7374733/50359582-8b610700-055d-11e9-88b6-e70ff2cf43b5.png)\r\n\r\nGoing deeper into the documentation I've discovered `key = KeyType.RSA` option which was not obvious at the beggining. I hoped this would generate a key for me as I didn't owned any.\r\n![zrzut ekranu 13](https://user-images.githubusercontent.com/7374733/50359625-b21f3d80-055d-11e9-9d98-adc2de198db7.png)\r\n\r\nBut same things happened as before\r\n![zrzut ekranu 14](https://user-images.githubusercontent.com/7374733/50359636-b9464b80-055d-11e9-875e-adcdf0697ce6.png)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/garstka/idact/issues/comments/450987269","html_url":"https://github.com/garstka/idact/issues/8#issuecomment-450987269","issue_url":"https://api.github.com/repos/garstka/idact/issues/8","id":450987269,"node_id":"MDEyOklzc3VlQ29tbWVudDQ1MDk4NzI2OQ==","user":{"login":"garstka","id":19312474,"node_id":"MDQ6VXNlcjE5MzEyNDc0","avatar_url":"https://avatars0.githubusercontent.com/u/19312474?v=4","gravatar_id":"","url":"https://api.github.com/users/garstka","html_url":"https://github.com/garstka","followers_url":"https://api.github.com/users/garstka/followers","following_url":"https://api.github.com/users/garstka/following{/other_user}","gists_url":"https://api.github.com/users/garstka/gists{/gist_id}","starred_url":"https://api.github.com/users/garstka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garstka/subscriptions","organizations_url":"https://api.github.com/users/garstka/orgs","repos_url":"https://api.github.com/users/garstka/repos","events_url":"https://api.github.com/users/garstka/events{/privacy}","received_events_url":"https://api.github.com/users/garstka/received_events","type":"User","site_admin":false},"created_at":"2019-01-02T21:15:21Z","updated_at":"2019-01-02T21:15:21Z","author_association":"OWNER","body":"I removed the prefix entry and renamed the environment to condabad:\r\n\r\nError on `conda create env -f condabad.txt`:\r\n\r\n```\r\nSolving environment: failed\r\n\r\nUnsatisfiableError: The following specifications were found to be in conflict:\r\n  - astropy==3.0.4=py37hfa6e2cd_0\r\n  - mkl==2019.0=118\r\n```\r\n\r\nAfter removing the mkl entry:\r\n```\r\nSolving environment: failed\r\n\r\nUnsatisfiableError: The following specifications were found to be in conflict:\r\n  - anaconda==5.3.1=py37_0 -> pycurl==7.43.0.2=py37h74b6da3_0 -> openssl[version='>=1.0.2o,<1.0.3a']\r\n  - openssl==1.1.1a=he774522_0\r\n```\r\n\r\nAfter removing the anaconda entry, I was able to create the environment and reproduce the stack trace:\r\n\r\n```\r\n     12 from cryptography import utils\r\n     13 from cryptography.exceptions import InternalError\r\n---> 14 from cryptography.hazmat.bindings._openssl import ffi, lib\r\n     15 from cryptography.hazmat.bindings.openssl._conditional import CONDITIONAL_NAMES\r\n     16\r\n\r\nImportError: DLL load failed: The specified procedure could not be found.\r\n```\r\n\r\nI executed `conda update --all` and retried:\r\n\r\n```\r\n    576         # Handle DNS error / name lookup failure\r\n    577         except socket.gaierror as e:\r\n--> 578             raise NetworkError('Name lookup failed for %s' % host, e)\r\n    579         # Handle timeouts and retries, including generic errors\r\n    580         # NOTE: In 2.6, socket.error subclasses IOError\r\n\r\nNetworkError: Name lookup failed for login-node.cluster.example.com\r\n```\r\n\r\nWhich is expected error. So the solution is to update the base environment at least once.\r\n\r\n\r\n"}}
{"actor":{"display_login":"garstka"}}