Skip to content

Bug with latest version, opts.dflt is undefined #3359

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

Closed
ShaneHudson opened this issue Dec 20, 2018 · 8 comments
Closed

Bug with latest version, opts.dflt is undefined #3359

ShaneHudson opened this issue Dec 20, 2018 · 8 comments
Assignees
Labels
bug something broken regression this used to work

Comments

@ShaneHudson
Copy link

Unfortunately upgrading to the latest version (v1.43) has not been possible for me. I particularly want it due to the fix of #3306.

I am unsure how to replicate the bug (it may be due to have a large amount of null data) but can show a screenshot of the issue. It happened once I upgraded to 1.43 and going back to 1.42.5 fixed the issue.

screenshot 2018-12-20 10 46 35

@ShaneHudson ShaneHudson changed the title Bug with latest version Bug with latest version, opts.dflt is undefined Dec 20, 2018
@etpinard
Copy link
Contributor

Thanks very much for the report!

I am unsure how to replicate the bug

Could you just share the "data" and "layout" you used to generate your graph?

@ShaneHudson
Copy link
Author

data.txt
layout.txt

Here you are, they are large amounts of data but primarily null. Please advise me if there are better ways of achieving this but previously the data would autofill when we need to see the blank space.

@archmoj
Copy link
Contributor

archmoj commented Dec 20, 2018

OK. @etpinard Let me test this...

@etpinard
Copy link
Contributor

My gut feeling: this appears like a bug coming from the new multicategory logic that propagated to 3D erroneously.

Thanks for your help @archmoj !

@archmoj
Copy link
Contributor

archmoj commented Dec 20, 2018

Here is a simplified demo that could be used (by changing the version to v.1.43.0) to illustrate the regression coming from the new multi-category logic as @etpinard mentioned which happens when one has both heatmap and surface traces.

@archmoj archmoj added bug something broken regression this used to work labels Dec 20, 2018
@archmoj
Copy link
Contributor

archmoj commented Dec 20, 2018

@ShaneHudson Until this regression is addressed you could test the changes with v.1.43.0; however, you would need to move your surface plot data to the top of the file. Please refer to the attachment below!
Also as described on #3306, you may consider changing the times on the ticks from dates to minutes until #3306 fixed.

timeseries-null-breaklines-gl3d_surface-gl2d_heatmap.txt

@archmoj
Copy link
Contributor

archmoj commented Dec 20, 2018

@etpinard here is another observation:
Not only surface plot that has this issue. It is not possible to add another trace e.g. scatter3d after heatmap set the axis type to multicategory. Here is a demo.

@ShaneHudson
Copy link
Author

@ShaneHudson Until this regression is addressed you could test the changes with v.1.43.0; however, you would need to move your surface plot data to the top of the file. Please refer to the attachment below!

Thank you, this fixed the issue.

Also as described on #3306, you may consider changing the times on the ticks from dates to minutes until #3306 fixed.

Hmm yes, that is possible but would rather not as I also have minutes/hours/days too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken regression this used to work
Projects
None yet
Development

No branches or pull requests

3 participants