What is the problem?

Although @ray.remote contains an argument for placement group, it doesn't work. We should either remove it or allow it. (placement_group_capture_child_task)

Reproduction (REQUIRED)

Please provide a script that can be run to reproduce the issue. The script should have **no

Summary

Today in the R package, there are a lot of internal function calls which use only positional arguments. Change them to use keyword arguments for extra safety.

I've added this issue to provide a small, focused contribution opportunity for Hacktoberfest 2020 participants. If you are an experienced open source contributor, please leave this

• I have tried using the latest released version of Numba
• I have included below a minimal working reproducer

In trying to replace numpy's setxor1d (which is unfortunately not supported by Numba), I came across an error that does occur for (integer) ndarrays but not for lists.
In my case the setxor1d can be replaced by [i for i in a if i not in b], but for the sake of testing, here i

Motivation

From following resources, the search space of examples/xgboost_simple.py seems not to be practical.

• https://www.analyticsvidhya.com/blog/2016/03/complete-guide-parameter-tuning-xgboost-with-codes-python/
• https://www.youtube.com/watch?v=VC8Jc9_lNoY
• https://www.amazon.co.jp/dp/B07YTDBC3Z/

Description

Improve the search space of examples/xgboost_simple.py.

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

Describe the bug

As discussed in the ROOT forum:
WIthout the memstat feature, root.exe still offers the -memstat option but produced failures like

input_line_11:2:6: error: unknown type name 'TMemStat'
 new TMemStat("",100000,5000000);

Expected behavior

If memstat is not part of the build, the memstat option

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() ?