-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
stream.write raises error in plotly 3.1.0 #1108
Comments
In 3.1.1 I made a change allowing the
This error can be fixed by converting the trace to a dict before removing the The reason that the data is overwriting rather than appending seems to be related to the fact that the new I suspect the version 2 would also have the overwriting behavior if Is this something you could look into @Kully or @tarzzz ? Seems it may require some insight into what the plot.ly stream service is doing. |
I am also experimenting the very same issue. @Kully workaround resulted in the same behaviour (unwanted) for Scatter instead of Bar. I also tried to include a 'type' entry in the input dictionary that could have solved the issue. |
@gnthibault BTW, what is your streaming use case? The cloud-based streaming is being deprecated, but it is possible to update existing figures using a At the moment with |
Thanks for enquiring. I finally found what I was looking for. I now use a Dash app, in which some browser-side code triggers a callback at regular interval, that I use to do some query in a database. |
Fixed in #1145 |
A simple streaming example that was working in Plotly 2.2 now does not work in 3.1.0+
results in the validation error
Changing
m = stream.write(dict(x=[i+2], y=[5]))
tom = stream.write(Bar(x=[i+2], y=[5]))
bypasses the problem, allowing the script to run and print the statements. But the figure is not appending to its data, but replacing each Bar trace that is added as evidenced by the (i)plot that updates.cc @jonmmease @tarzzz
The text was updated successfully, but these errors were encountered: