Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

Project abandoned? #70

Closed
litghost opened this issue Oct 21, 2021 · 10 comments
Closed

Project abandoned? #70

litghost opened this issue Oct 21, 2021 · 10 comments

Comments

@litghost
Copy link

litghost commented Oct 21, 2021

Is this project abandoned by plotly? I have identified a couple issues and have fixes (e.g. #60), but there hasn't been any commits since January 22, 2021. There also doesn't appear to have been any responses to issues. I don't mind maintaining a fork with fixes, but would prefer to move good changes upstream if possible.

@fxheng
Copy link

fxheng commented Nov 8, 2021

I'm also interrested in getting this thing run for jupyterlab 3. Is plotly still there?

@nicolaskruchten
Copy link

Plotly is still here and this project isn't abandoned, it just mostly works without many modifications needed. I'm sorry we haven't been able to review your PR #60 yet @litghost :)

@litghost
Copy link
Author

litghost commented Nov 8, 2021

Plotly is still here and this project isn't abandoned, it just mostly works without many modifications needed. I'm sorry we haven't been able to review your PR #60 yet @litghost :)

Since JupyterLab integrated async, I believe there are some issues with "infer_jupyter_config" (e.g. #62) that exist now.

I also have a fix for #63 and #64.

@datainvestor
Copy link

#62 Is very serious issue, I wanted to introduce Dash in my company but so far I am failing to set even a working demo for them...

@litghost
Copy link
Author

litghost commented Dec 13, 2021

#62 Is very serious issue, I wanted to introduce Dash in my company but so far I am failing to set even a working demo for them...

If you have time, I have proposed changes for #62 (and #63 and #64) mixed in with #60 and some other changes in https://github.com/litghost/jupyter-dash/tree/iterate_jupyter_dash3 . Feel free to take a look.

@fxheng
Copy link

fxheng commented Dec 13, 2021

Currently I'm using dash with only jupyter-server-proxy
2 main issues burden me:

  • First there is a issue while launching any flask server from the ipython and ipykernel stack. I think there is a double call somewhere always ending to block the choosen port.
  • Second is can't run JupyterDash.infer_jupyter_proxy_config() in Jupyterhub #62 preventing to get your session information.
    Currently my workaround was a propers lab configuration to run the flask app from the terminal and use jupyter-server-proxy(You cannot use the console because of the port issue). This way you can take advantage of flask debugging session and and auto reload. Drawback is that your terminal is not link to the explorer and you need navigate and launch the python from shell command.

@t89
Copy link

t89 commented Jan 30, 2022

Judging from the amount of issues and the current update schedule it might as well be dead.

@johnc1231
Copy link

Is there a current update schedule?

@cmosguy
Copy link

cmosguy commented Mar 2, 2022

Sounds to me that they make the open source capabilities broken so you are forced to buy their expensive enterprise solutions 👎🏽

@chriddyp
Copy link
Member

Thanks everyone for sharing these issues and sorry for the radio silence on this issue.

We've merged 6 PRs in the last 30 days and 8 PRs since the start of the year. These versions are available in on 0.4.2 and 0.2.1, see the CHANGELOG: https://github.com/plotly/jupyter-dash/blob/master/CHANGELOG.md

Closing this issue for now since we made recent activity and fixed those bugs. Please create new issues as you encounter problems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants