-
Notifications
You must be signed in to change notification settings - Fork 2
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
Multiple Issues when running inside JupyterLab #110
Comments
I think the first point already is an untenable situation. It can't be that we need to essentially busy wait on a global variable to be populated. There needs to be a more canonical way to ensure that google charts is loaded, or some kind of promise we can reliably wait on. edit: Appears like google killed Support for charts two months ago: google/charts#798. Tbh. I don't know how much more work we should be putting towards google charts anymore. |
I'd love to dump Google Charts. FTM, since the project is no longer maintained, the simple solution is for Google to open-source it and let us download the damn thing through NPM, like any other package. |
Incidentally, I set
So my guess is that there is a timing issue that is triggered by the multiple timeouts, and as a result a ton of async code isn't getting called. I'll put in a test for those next. |
OK, I think I have a lead. I put in console.log messages when the morphic properties for a chart are assigned, and when the chart is first drawn. They didn't appear, and a message saying gViz is null DID appear. When I checked gViz in the console, it was there, and then I reloaded the dashboard using |
And, @merryman, you're right. We have to ditch Google Charts asap. I'm going to devote fulltime to the editor. It's the only way. |
I got it fixed, though frankly the fix shouldn't have been necessary. I put in a defensive call in
which shouldn't be necessary, because Since we may have not drawn charts because Google Charts wasn't loaded, a callback was added to the charts loader: |
I'm leaving this issue open because we need to talk about it. Mostly, this is Google stabbing us in the back, @merryman please look at the code and see if there is anything I have missed.
And addChart:
Everything checked in. |
Fixed and closed |
$world.get('dashboard').viewModel.gViz
isundefined
await $world.get('dashboard').viewModel.drawAllCharts()
does draw the charts, but they are all at position (0, 0)renderViaCSS
on top bar tofalse
. Will reset totrue
to check this.The text was updated successfully, but these errors were encountered: