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

potential api example

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

Given a stream s1 that contains a NULL value:

CREATE STREAM s1 (x INTEGER) ...
INSERT INTO s1 (x) VALUES (null);

If that NULL expression is used in an arithmetic operation, the result of the operation will be NULL:

SELECT x + 1 FROM s1 EMIT CHANGES;

However, if a NULL literal is used in the same way, an NPE will be thrown:

ksql> SELECT NULL + 1 FROM

Aim/Problem: Improve the docstrings in all the python files in the codebase. This will also fulfill the prerequisite for the lint check Check to enforce use of Args, Returns and Raises in the docstring. to be introduced for #8423.

Suggested fix: Do a grep or a search (CTRL+F) for def keyword in the file to get all the possible places that we would need to fix. Verify that the

Currently, we ignore all code inside a quoted expression:

julia> Base.show(io::IO, ::MIME"text/plain", b::Bool) = println(io, b ? "👍" : "😢")

julia> import Pluto: ReactiveNode

julia> ReactiveNode("""
       begin
           x = 1
           y = quote
               z = 3
           end
       end
       """).definitions
Set{Symbol} with 2 elements:
  :y
  :x

julia> :

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: