Issue #3644 describes the reasons why this warning was created. However, I get this warning even with as little as 17 actors:

According to ulimit -n I can safely run many more procs.

Potential solutions:

• Allow to specify number of acceptable actors before warning

One unit test in the R package is currently broken. Steps to reproduce on Mac

export CXX=/usr/local/bin/g++-8 CC=/usr/local/bin/gcc-8
Rscript build_r.R
cd R-package/tests
Rscript testthat.R

This results in the following error at the ends of the logs

[LightGBM] [Info] Saving data to binary file /var/folders/xq/wktq4zdx4jd3qdpk34d28m940000gn/T//RtmpiY1DzV/lgb.Dataset_1555

Probably we can catch the error message and give you a better message along the lines of: "Numba is currently unable to compile your code."

Originally posted by @esc in numba/numba#6142 (comment)

We can catch the NotDefinedError can report a better message that says the compiler failed to analyze the bytecode.

Motivation

Examples in the API reference should be pedagogical. The plot for the contour plot is not with somewhat poorly visible categorical parameter values.

Description

The contour plot example could use a better suited objective function

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

Feature request

The asynchronous functionality of parallel-ssh is very much appreciated for management tasks. Thank you for this!

For the feature request:

It seems that the open_session() can keep worker allocated for much longer than expected in failure cases. Would it be reasonable to stretch the timeout option of wait_socket() to open_session() ?