interactive

We would like to avoid confusion like we have in webpack-contrib/webpack-bundle-analyzer#185

We could document statsFilename and reportFilename options allowing the use of an absolute file path like /path/to/folder so that people would know it's supported.

Let us know in this issue if you would like to contribute to this!

Most items coming from questions on the community forum

• a proper multicategory bar example based on https://community.plotly.com/t/multicategory-axis-type-example/26392
• example of shape or annotation covering several subplots thanks to xref='paper'. Also the shapes and annotations tutorial should link to each other.
• orthographic projection example in 3d axes tutorial (or

We should make a GitHub action so that when we update our README it automatically goes to the website. At the moment, our README is out of sync with the website. The repo's README should be the source for the website.

potential api example

bit fix undo-commit
bit fix untrack-file
bit fix rename-commit
bit fix catch-up-to-branch

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently, ksqlDB causes a full topic scan whenever performing a pull query over a stream. This is inefficient when looking up specific sets of data, but necessary due to how pull queries are implemented over streams.

**Describe the

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

1. Work computer works fine loading .gml
2. Home PC gets angry
3. Java is updated

Context

Describe the bug
When viewing subtopics on larger screens, the topic name is displayed on the navbar.

On smaller screens, the topic name is omitted due to space constraints. Therefore, the topic name should instead be displayed above the subtopic name, as per these mocks: http

We currently use some internal Pkg API to make https://github.com/fonsp/Pluto.jl/wiki/%F0%9F%8E%81-Package-management work, we we should try to avoid as much as possible. Take a look at src/packages/PkgCompat.jl to learn more, the compatibility issues are pretty well documented.

Hey everyone!

mapd-core-cpu is already available on conda-forge (https://anaconda.org/conda-forge/omniscidb-cpu)

now we should add some instructions on the documentation.

at this moment it is available for linux and osx.

some additional information about the configuration:

1. for now, always install omniscidb-cpu inside a conda environment (also it is a good practice), eg:

I'm trying to replace the background diagram-maker canvas svg, with custom small circular nodes. So, probably this lead to more than 5000 number of circular nodes.

This is causing Performance Issues. Any suggestions, how to optimize this usecase?