I often run into issues by accidentally starting a new cluster when one is already running. Then, this later causes problems when I try to connect and there are two running clusters. I'm then forced to ray stop both clusters and ray start my new one again.

My workflow would be improved if I just got an error when trying to start the second cluster and knew to immediately tear down the exist

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

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

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