One of the main use cases of lpad and rpad is, at least for me personally, to align things in the terminal. However, lpad and rpad are defined (and documented) to work in terms of code units (i.e. they call length on the input string) which means that when length and textwidth disagree, you get unaligned output:

julia> s1 = "⟨k|H₁|k̃⟩"
"⟨k|H₁|k̃⟩"
julia> s2 = "⟨k|H₁|k⟩"
"⟨

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.

Dear all,
Volcano v1.1 has been released on Oct 30. Main features such as Big Job Resource Reservation/HDRF/Monitoring are included. More details please refer to https://github.com/volcano-sh/volcano/releases/tag/v1.1.0. Beta test are warmly welcomed and we are looking forward to your advice in issues.
Feature design of v1.2 is alse finished and all main features have been owned. You can

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.

Parts of the man page of MPI_Win_attach seem to be a verbatim copy of MPI_Win_create and states that this is a collective operation, which in case of MPI_Win_attach it is not. See: https://github.com/open-mpi/ompi/blob/master/ompi/mpi/man/man3/MPI_Win_attach.3in#L71

This should be fixed to reflect the actual behavior of MPI_Win_attach and should also contain at least a sentence on `MPI_

Another important topic from the meeting was the need to restructure the files on the main repository, to reduce their sizes and improve both readability and compilation times.

Of course, any file movement will affect the developers with ongoing branches (see #582) so one suggestion is to restructure one file at a time, maybe once every month or so, to reduce the burden to everybody.

I have

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

The module command automatically detects current terminal width and formats its output to completely fill this available space, like for instance when outputting in a column format the list of all available modules.

It may be desirable to limit the terminal width used by this output to a given size and make module automatically adapts to fill space up to this limit only.