What is the problem?

After running tune.run, the experiment results are missing from progress.csv but are in result.json.
A possible solution is written by mannyv: https://discuss.ray.io/t/saving-checkpoints-with-good-custom-metric-using-tune-run/2109/12

Ray version and other system information (Python version, TensorFlow version, OS):

Ray version 1.2.0.
Tensorflow 1.15.4.
Python

Migrate all Python code from old-fashioned format() functions, formatting % operators and simple concatenations (+) to modern f-strings (brief guide). They are known to be the fastest approach and also increase code readability.

![image](https://user-images.githubusercontent.com/25141164/112898582-a

In numba/stencils/stencil.py, there are various places (like line 552, "if isinstance(kernel_size[i][0], int):") where we check for "int" in relation to neighborhoods. I ran across a case where I was creating a neighborhood tuple by extracting values from a Numpy array. This causes a problem because those Numpy values will not match in these isinstance int checks. I worked around it by conver

Motivation

Test cases in tests/pruners_tests/*.py can be simpler using should_prune and the ask-and-tell interface. e.g. optuna/optuna#2644

Description

• test_hyperband.py
• test_median.py
• test_nop.py
• test_percentile.py
• test_successive_halving.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

Explain what you would like to see improved

After root-project/root#7399 we can now add RNTuple field descriptions to the output of RNTupleDescriptor::PrintInfo, as in TTree::Print().

Optional: share how it could be improved

Right now I think the most appropriate info category is `kStorageDetails

• I have searched issues for similar feature requests

What is this feature about (1 sentence)

Adding an option in the dashboard to filter runs by start date.

Why is it needed? What is the value? For whom do we build it?

In case of multiple runs (over night, at deploys etc.) the dashboard can end up having multiple runs for 1 day, that are not separated from yesterday's.

Hig