Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    toxicafunk
    @toxicafunk
    looks like a version issue from here
    jeremyrsmith
    @jeremyrsmith
    @sachdevasahil7 this particular issue is from the IntelliJ run configuration. You have to open the run configuration and make sure Include dependencies with "provided" scope is checked.
    apologies, I hope to have actual docs about this kind of stuff in the not-too-distant future
    Moritz Baumotte
    @moritzbaumotte

    Just quoting this from your page - "Polynote is currently only tested on Linux and MacOS, using the Chrome browser as a client. We hope to be testing other platforms and browsers soon. Feel free to try it on your platform, and be sure to let us know about any issues you encounter by filing a bug report." When should Windows guys expect support for our platform? Don't get us sidelined. This looks more promising than what we should miss, you know?

    In case you haven't got it running yet, I created a script to run polynote on windows (using docker). It run's the currently latest polynote version 0.3.11 but I'll soon update it to automatically pull the newest version (notebooks are persisted in a mounted folder). Feel free to check it out.

    https://github.com/moritzbaumotte/polynote-windows-inofficial

    jonathanindig
    @jonathanindig
    Hi @moritzbaumotte thanks for your interest in Polynote! I’m curious, what prevents users from using the official polynote docker images (https://hub.docker.com/r/polynote/polynote) on Windows?
    jonathanindig
    @jonathanindig
    By the way, it does seem like a decent number of people have been successful running Polynote on Windows with Windows System for Linux: polynote/polynote#671
    It looks like our documentation was out of date on the website, because it was supposed to say that. I’ll fix the doc update job and hopefully reduce confusion here.
    Moritz Baumotte
    @moritzbaumotte
    Hi @jonathanindig thanks for providing it! I though about the Windows subsystem for Linux as well but unfortunately it is blocked in my company via the Active Directory.
    As for the official docker image, you can run it properly on Windows, Polynote starts correctly inside the container but you can't access it from the Windows host (you'll get some connection refused or connection timeout error). To access it from Windows Polynote would need to socket bind to 0.0.0.0 inside the container rather than 127.0.0.1 (which it is per default I belief). That's what this tiny config.yml is for in my repository.
    Moritz Baumotte
    @moritzbaumotte
    I'm not a networking guy though, I can't really explain why 127.0.0.1 doesn't work but I experienced the same issue before with python web servers.
    jonathanindig
    @jonathanindig
    That’s expected with Docker. Here’s our official docker documentation: https://github.com/polynote/polynote/tree/master/docker#official-docker-images
    For security reasons the official Docker distribution needs you to provide your own configuration. This is by design; please see https://github.com/polynote/polynote/issues/666#issuecomment-555212474 for more about our rationale.
    Moritz Baumotte
    @moritzbaumotte
    Okay, then I can't explain it. I basically took an older approach on Dockerizing Polynote for Windows and completed it fixing any bug I could find until it worked.
    Btw, I've updated my repo that it automatically uses the newest Polynote version - not a pretty solution but good enough to make it run. ;)
    João Costa
    @JD557
    Not sure if this is possible or easy, but has anyone got polynote to run inside of docker with cuda working?
    I think the base image would have to be based on something like nvidia/cuda:9.0-base :(
    jonathanindig
    @jonathanindig
    Unless there’s something about those cuda images I’m not familiar with, there shouldn’t be anything inherently difficult about getting Polynote onto those images, at least from Docker’s POV
    Here’s the Dockerfile Polynote uses. You should be able to change the base image to whatever you like, all you'd need to do is make sure to install java
    (now, getting the python running inside of Polynote to properly interface with cuda… no idea if that would work. )
    João Costa
    @JD557
    I was looking into that, I might try to build a docker image later
    the nvidia GPU is not on my main dev machine, so this is quite cumbersome to try... maybe I'll check that during the weekend :sweat_smile:
    jonathanindig
    @jonathanindig
    good luck :) if it works, feel free to contribute a Dockerfile
    raproth
    @raproth
    Currently python stopped working in polynote, I get Uncaught exception: <class 'SyntaxError'>: future feature annotations is not defined (jep.JepException) any idea whats wrong? Running Python 3.6.10 on Linux. Do I need Python > = 3.7?
    Clay Lambert
    @claylambert33_twitter
    @raproth it has been my experienxe that 3.7 works better overall. I don’t know if that will resolve your jep exception per se.
    jonathanindig
    @jonathanindig
    @raproth This is due to a recent change in the new release: polynote/polynote#951 Didn’t realize it wouldn’t work in 3.6 but we’re mainly targeting 3.7. Any particular reason you’re using 3.6?
    jeremyrsmith
    @jeremyrsmith
    heh, python is so hard to support with one interpreter, because there's no union of "all of python" even within 3.x. Minor versions have removed stuff and added other stuff, you can't capture that in a union
    I imagine we'll run into the same thing when we start worrying about Scala 3... :grimacing:
    Should there be a Python < 3.7 interpreter and a Python >= 3.7 interpreter? I don't know really... I'd prefer not, but this is the kind of thing that may become necessary :frowning:
    João Costa
    @JD557
    FWIW, according to https://endoflife.date/python, python 3.6 support ends in 1 year and 3 months
    I would say that it might not be worth it to add that support just for one year, but OTOH, all surveys that I can find say that 3.6 is the most used version :grimacing:
    raproth
    @raproth
    @jonathanindig no particular reason, currently python 3.6.10 is installed on our server and I do not have the permissions to change that myself. But don't worry, at least I know what to do
    Lanking
    @lanking520

    Hi all, I am new to PolyNote, currently trying to install it on my mac (Mac OS Catalina) and failed with Python 3.7 virtualenv:

        ld: library not found for -lpython3.7m
        clang: error: linker command failed with exit code 1 (use -v to see invocation)
        error: command 'xcrun' failed with exit status 1

    It seemed to be an issue with jep, did anyone saw this before?

    jonathanindig
    @jonathanindig
    @lanking520 from a quick Google search, it looks like you need to install Xcode tools: https://ma.ttias.be/mac-os-xcrun-error-invalid-active-developer-path-missing-xcrun/
    Lanking
    @lanking520
    I already installed that, 'xcrun' failed
    ld: warning: directory not found for option '-L/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib'
    João Costa
    @JD557
    @lanking520 have you tried using the docker image instead? I find that easier than having to fix the local python version
    jonathanindig
    @jonathanindig
    +1 for the Docker version being easier. If you still want to set things up locally, unfortunately you will need to debug your python environment. Are you using the stock python that ships with OS X? Unfortunately Python installation environments tend to be horrible: https://xkcd.com/1987/
    Lanking
    @lanking520
    Nope, I use the virtualenv Python instead, just don't want it messed up local environment. I am trying to use polynote along with my demo on Spark and provide instruction for users to start using it. Using Docker although would work but I am looking for some out-of-box solution for users so they don't have to dive into configuration... Also my application will also use GPU, I am not sure if the docker env will have CUDA driver
    btw:
    (env) 3c22fb785594:polynote qingla$ xcode-select --install
    xcode-select: error: command line tools are already installed, use "Software Update" to install updates
    (env) 3c22fb785594:polynote qingla$ clang --version
    Apple clang version 11.0.3 (clang-1103.0.32.62)
    Target: x86_64-apple-darwin19.6.0
    Thread model: posix
    InstalledDir: /Library/Developer/CommandLineTools/usr/bin
    jonathanindig
    @jonathanindig
    What is the output of python --version and python-config --ldflags
    Also, what command are you running to get that error? pip install jep ?
    Lanking
    @lanking520
    Here you go
    (env) 3c22fb785594:polynote qingla$ python --version
    Python 3.7.3
    (env) 3c22fb785594:polynote qingla$ python-config --ldflags
    -L/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -lpython2.7 -ldl -framework CoreFoundation
    Yes, pip install jep failed
    jonathanindig
    @jonathanindig
    and pip --version ?
    Lanking
    @lanking520
    (env) 3c22fb785594:polynote qingla$ pip --version
    pip 19.0.3 from /Users/qingla/Documents/GitHub/polynote/env/lib/python3.7/site-packages/pip (python 3.7)
    Lanking
    @lanking520
    It seemed there is a mismatch on my python-config which is using python2.7... And it mayu cause the issues while jep trying to find python3.7m package
    jonathanindig
    @jonathanindig
    That’s possible, but the ld warning you posted above seemed to be looking for a python 3 path. I wonder where it got /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib
    Lanking
    @lanking520
    ls /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib
    ls: /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib: No such file or directory
    jonathanindig
    @jonathanindig
    Hmm, I don’t really know much about the Python build environment unfortunately. Maybe try python3-config --ldflags?
    My guess is there are two different python installations around that are confusing things