hera | A desktop app for Jupyter Notebook | Code Editor library

There is a way of importing the data from a data table into the SQL Table. You need to use SqlBulkCopy

var sqlBulkCopy = new SqlBulkCopy(conn);

You can even map which data table column goes to which SQL Table column as well.

Here is an example.

Error creating bean with name 'resourceHandlerMapping' defined in class path resource [org/springframework/boot/autoconfigure/web/servlet/WebMvcAutoConfiguration$EnableWebMvcConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.web.servlet.HandlerMapping]: Factory method 'resourceHandlerMapping' threw exception; nested exception is java.lang.NoSuchMethodError: 'org.springframework.web.servlet.config.annotation.ResourceHandlerRegistration org.springframework.web.servlet.config.annotation.ResourceHandlerRegistration.setUseLastModified(boolean)'

Based on the above line, you didn't annotate the class with @Component, IOC can't register that been

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.

The problem is that you are attempting to dodge text on a continuous axis (your flipped x axis is a datetime axis), whereas you probably want this to be a discrete axis. So you can do something like this:

The Live Server extention opens the localhost tab on your default browser, but you can copy the URL into any other browser and it will work, as long as the server is running.

If you want the tab to always open in Firefox Developer Edition, you can change the settings of Live Server.

• In VScode, go to File > Preferences > Settings (or Code > Preferences > Settings on Mac)

• In the search bar, type liveServer.settings.AdvanceCustomBrowserCmdLine

• Click on Edit in settings.json

• change the value of "liveServer.settings.AdvanceCustomBrowserCmdLine" to the location of Firefox Developer Edition (for example, C:\Program Files\Firefox Developer Edition\firefox.exe)

Note: Live Server also has a CustomBrowser setting, which is simpler to edit, but it has limited options and Firefox Developer Edition is not one of them. AdvanceCustomBrowserCmdLine overrides CustomBrowser.

You can read the Live Server docs here.

After some investigation, I found that the problem was coming from W3TC trying to access to the Memcached server.

The W3TC plugin was trying to access to our production Memcached server (inaccessible from outside) and result to a silent timeout.

The package only depends on python3.6: https://packages.ubuntu.com/bionic/python3-pyqt5. It will be installed because it is a prerequisite.

It's been clarified to me by pydatatable team, and i would have to contact google colab team for this issue. and for now i'm not going to use this in Colab notebooks.