I just noticed the Random stdlib has an UnsafeView type for filling arrays. With the new layout optimizations, this should no longer be necessary. We should try using the normal SubArray type for this. If it's still too slow/complex, then at least the type can be made safe by holding the underlying array directly instead of a Ptr.

Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.

This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

Currently spack does not support the following packages, all of these packages are installed outside of Spack at Cori, we would like to get support for these packages if possible.

• cpmd https://www.lcrc.anl.gov/for-users/software/available-software/cpmd/
• ComputeCPP https://github.com/codeplaysoftware/computecpp-sdk need to confirm link
• ds9 https://sites.google.com/cfa.harvard.

I often use -v just to see that something is going on, but a progress bar (enabled by default) would serve the same purpose and be more concise.

We can just factor out the code from futhark bench for this.

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature
/help wanted

Description:

Currently, we publish helm chart at https://github.com/volcano-sh/charts and keep helm charts up-to-date at
https://github.com/volcano-sh/volcano/tree/master/installer , and they already mismatched. It's better to make charts as submod of volcano to keep them sync.

The documentation for the function shmem_wait seems inconsistent with the function signatures as it describes parameters target, pe, and value that are actually not part of the interface. The parameter ivar is described but at least in the C interface the variable is named var (without the prefix i).

See https://github.com/open-mpi/ompi/blob/master/oshmem/shmem/man/man3/shmem_wai

Describe the bug
When explaining the Symmetry Wall in https://su2code.github.io/docs_v7/Markers-and-BC/, there is a copy paste from the explanation for Euler (slip) Wall:

"For all Finite Volume (FVM) solvers, i.e. not the FEM_* solvers, its implementation is identical to MARKER_SYM solvers and both options can be used interchangeably."

which makes no sense.

Add the appropriate libncurses package name for each supported distro. This is commonly named libncurses5.

The envml tool that ends up in Modules/bin/ seems quite useful but does not show up in the documentation (apart from the Release Notes: https://modules.readthedocs.io/en/latest/NEWS.html?highlight=envml).