Properly detect macOS/Linux/Windows incompatibility for the language server

[samuelchen]

Environment data

• VS Code version: 1.27.2
• Extension version (available under the Extensions sidebar): 2018.8.0
• OS and version: MacOS EI Captain 10.11.6
• Python version (& distribution if applicable, e.g. Anaconda): 3.7.0 from Brew
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
• Relevant/affected Python packages and their versions: N/A

Actual behavior

Error log shows in "output"

Expected behavior

N/A

Steps to reproduce:

N/A

Logs

Starting Microsoft Python language server.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 11:50:16 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 11:50:17 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 11:50:18 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Info  - 11:50:18 PM] Connection to server got closed. Server will restart.
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/samuel/.vscode/extensions/ms-python.python-2018.8.0/languageServer/libcoreclr.dylib (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

[Error - 11:50:19 PM] Connection to server got closed. Server will not be restarted.

[brettcannon]

Did you get a banner about the language server not supporting macOS 10.11? (Notice the message "which was built for Mac OS X 10.12" in the output.)

[samuelchen]

@brettcannon Thank you for the reply.
I did not get a banner about the language server not support the macOS version. I just found the message in the log.

[samuelchen]

Besides the banner displaying, is there anyway to make it work in macOS 10.11 ?

[DonJayamanne]

Please could you install the development version form here and let us know what you get?
Instructions for installing the development version can be found here https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build

[ev-dev]

Also had this happen running on El Capitan 10.11, didn't display a incompatibility banner vs code let me download and install language server which then just errored out immediately on reload. Was confusing since VS Code prompted the recommendation to try out the language server first. Would be good to notate the restricted system requirements in the extension info page or elsewhere while the bug persists