-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
[prophet] prophet installation fails with ModuleNotFoundError: No module named 'lunarcalendar' #20901
Comments
I have the same issue, but I was unable to fix it with |
This is what i have exactly in my Dockerfile. RUN pip install --upgrade pip |
I have some problem, I can't use prophet. I'm using 2.0 superset |
@villebro @zhaoyongjie @etr2460 As more people are reporting this issue, request you to provide your opinion for a permanent solution. |
Hello, I used the command @mdeshmu suggested to use, but it's still not working. Whenever I toggle forecast, it says "No results were returned for this query". Any idea ? (Not using Superset 2.0 btw) |
With this Dockerfile:
I was able to build Superset with prophet, but it still doesn't work. I'm having the same problem as above, no more errors, but forecast always returns 0 rows. |
@wiktor2200 @EliottTardieu Can you confirm you don't have multiple App containers running and prophet is installed on the container you are browsing for. You may check using |
I'm using Dockerfile from above and when I exec into container/pod, prophet is there, but returning 0 rows in every query when
|
I'm having the exact same issue as @wiktor2200 (0 rows when |
Hello! Today I've tried again with my Dockerfile and now prophet works in both |
Same here, but even Friday. For some reason when I tried again (using the exact same dockerfile), it worked. |
Preinstalling |
Just tried @john-bodley's branch, after getting stuck on this issue when trying to use prophet with superset in docker. Initially it did not work for me on the master branch or @john-bodley's. However, after pulling @john-bodley's branch: #24129 and then running docker exec -it superset_app /bin/bash
# in container
pip uninstall fbprophet pystan
pip --no-cache-dir install pystan==2.19.1.1
pip install --upgrade pip
pip install lunarcalendar tqdm "pystan<3.0" && pip install "prophet>=1.0.1, <1.1" Forecasting seems to be working consistently. |
@john-bodley Can we close this issue given #24129? |
How to reproduce the bug
Following methods to install prophet on docker image of Superset 1.5.1 fails with ModuleNotFoundError: No module named 'lunarcalendar'
docker pull apache/superset:1.5.1
docker run -it <imageid> bash
pip install apache-superset[prophet]
pip install --no-cache-dir apache-superset[prophet]
pip install prophet==1.0.1
pip install --no-cache-dir prophet==1.0.1
Note that the missing dependency can be anything, depending of what it is already installed or not, I personally saw errors about missing lunarcalendar, pystan, tqdm. Same has been explained here
For me, this worked finally:
pip install lunarcalendar tqdm "pystan<3.0" && pip install "prophet>=1.0.1, <1.1"
but i think even this might break in future if version of any of the other common dependencies with superset are changed or dependency is removed altogether.Note: prophet dependency issues were solved recently in 1.1 release.
I can install latest 1.1 prophet package with
pip install prophet
without errors but holidays package gets upgraded and thensuperset db upgrade
breaks and gives below error.pkg_resources.ContextualVersionConflict: (holidays 0.14.2 (/usr/local/lib/python3.8/site-packages), Requirement.parse('holidays==0.10.3'), {'apache-superset'})
pkg_resources.DistributionNotFound: The 'holidays==0.10.3' distribution was not found and is required by apache-superset
Can holidays package dependency be bumped to 0.14.2 in Superset ?
Expected results
It should be easy to install prophet
Actual results
its really messy
Screenshots
Here are the logs:
prophet-latest-directly.txt
prophet-via-setup-py.txt
prophet-1.0.1-directly.txt
Environment
Checklist
Additional context
The text was updated successfully, but these errors were encountered: