Artificial Intelligence

All the docs still say:

Trainer(gpus=...)

But we now support a different syntax:

Trainer(devices=4, accelerator='gpu')

Although we have backward support, all the docs (including readme) needs to reflect the new way of doing it

cc @Borda @rohitgr7 @akihironitta @ananthsub @carmocca @Borda

Thank you for submitting a feature request. Before proceeding, please review MLflow's Issue Policy for feature requests and the MLflow Contributing Guide.

**Please fill in this feature request template to ensure a timely and thorough response.

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

We've see many people complain about Milvus 2.0 spent too many disk spaces.

One thing we can do is do compress the binlogs and check if we can get some compression ratio, If so compression should also help the load speed due to saved IOs

D

We support toml as params file. There are a few issues with our current toml parsing:

1. We use toml library, which is not toml 1.0 standard compatible. Also, the library is not being actively maintained.
2. toml dumping does not preserve existing formatting.
3. iterative/dvc#6402

We can try migrating to tomli (which

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

Currently, you can do something like this: Task(Flow/RunID/StepName) and this will not result in an error but then the resulting Task object behaves in a bizarre manner where things like t.data will work but t.data.my_artifact will not for example.

We should validate the format of the pathspec passed in to each object and verify that the following are the only possible cases:

• Metaflo