In numba/stencils/stencil.py, there are various places (like line 552, "if isinstance(kernel_size[i][0], int):") where we check for "int" in relation to neighborhoods. I ran across a case where I was creating a neighborhood tuple by extracting values from a Numpy array. This causes a problem because those Numpy values will not match in these isinstance int checks. I worked around it by conver

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:

While the test_suite presented in #589 does work, it is still pretty simple and can be improved and enhanced.

• Add tests for gnutils and coreutils.
• Add necessary utilities so more complex programs can be compiled from sources.
• Integrate CMake, so one could write something like make validate and the subset of test that is deemed necessary (for example everything with min t

Scenario:
I have a project, with build tools of cmake, when I try to run it with cling. It prompts some headers are not included.

So I was wondering if there is a way to make use of the cmake script to load the build environment into cling and run directly?

Appreciate the great work!

Currently, the architecture of the CLI is based on (sub)commands and options. Commands are expected to be provided as the first argument, and do effectively decide which feature is to be used. OTOH, options provide parameters to the commands. However, there is no syntactical difference, as both commands and options start with -- or -i. As a result, we rely on properly formating --help and on

enable cyclic-import check in pylint and fix the imports if there are problems

https://blog.llvm.org/posts/2021-01-05-stack-clash-protection/

Appears to be as simple as adding {"probe-stack"="inline-asm"} to all function attributes.

In:
https://github.com/TheDan64/inkwell/blob/f768691fccb04fe262a6ccf22c215657dc08de98/src/context.rs#L950
the lifetimes are left implicit, which unnecessarily shortens the lifetime of the return value. Making the lifetimes explicit:

impl<'ctx> Context<'ctx> {
    pub fn const_string<'a>(&'a self, string: &'a [u8], null_terminated: bool) -> VectorValue<'a> {
        ...
    }
}