🚀 Feature

When evaluation trainer.validate(verbose=True) (or test) finishes, we print a dictionary with the results obtained

--------------------------------------------------------------------------------
DATALOADER:0 TEST RESULTS
{'test_loss': -3.4134674072265625}
--------------------------------------------------------------------------------

https://github.co

MLflow Roadmap Item

This is an MLflow Roadmap item that has been prioritized by the MLflow maintainers. We're seeking help with the implementation of roadmap items tagged with the help wanted label.

For requirements clarifications and implementation questions, or to request a PR review, please tag @BenWilson2 in your communications related to this issue.

Proposal Summary

Includ

Is there an existing issue for this?

• I have searched the existing issues

What would you like to be added?

I would like to add DataType_UInt64.

Why is this needed?

Databases like mysql support unsigned integer numbers through keywords such as UNSIGNED.
In order to enrich the data type, we have no reason not to support it.

Anything else?

No response

Bug Report

Got error message on an empty directory, shouldn't it show nothing? like ls command.

Description

![image](htt

Currently, when entering epic mode the README is frozen in the last level of the tower. When you're trying to fine-tune the score for a level other than the last one, it would be helpful if we had the README for that level available. The proposal is that when entering epic mode, the README is updated with all levels, one following the other.

Example:

# Starbolt - beginner

Specs

• Leon version: latest
• OS (or browser) version: Fedora 30
• Node.js version: 10.16.3
• Complete "npm run check" output:

➡ Here is the diagnosis about your current setup
✔ Run
✔ Run modules
✔ Reply you by texting
❗ Amazon Polly text-to-speech
❗ Google Cloud text-to-speech
❗ Watson text-to-speech
❗ Offline text-to-speech
❗ Google Cloud speech-to-text
❗ Watson spee

With a config like this

{
    "METAFLOW_DATASTORE_SYSROOT_S3": "s3://mf-test/metaflow/",
}

(note a slash after METAFLOW_DATASTORE_SYSROOT_S3)

metaflow.S3(run=self).put* produces double-slashes like here:

s3://mf-test/metaflow//data/DataLoader/1630978962283843/month=01/data.parquet

The trailing slash in the config shouldn't make a difference