Describe your feature request

It is already possible to give actors a name: https://docs.ray.io/en/master/actors.html#named-actors and to retrieve the actor handle via ray.get_actor("some_name").
It would however be very handy to have some kind of ray.list_named_actors() API method to get a list/dict of all currently available named actors.
It can be useful for:

• Better debugging

Description of the problem

As of the changes in #3160 , builds of the CRAN version of the R package with gcc now raise "unknown pragma" warnings.

CRAN does not allow the use of -Wunknown-pragmas to suppress such warnings, so we remove them with sed when building the R package.

The "bug" here is that LightGBM's CI did not catch this. That should also be fixed.

How to fix thi

Reporting a bug

• [x]

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

In the following reproducer, t.Scan() prints values for column out_x.out_x but the output is truncated to out_x.out, which can be quite confusing for larger trees with nested branches:

root [0] TTree t;
root [1] int x = 42;
root [2] t.Branch("out_x", &x)
(TBranch *) 0x5559ed5dc4f0
ro

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