Antoine Broyelle

Jump straight into a given step

1

This feature sets the initial view to a given step. ex: `bulmaSteps.attach('.steps', {'step_idx': 2});`

Hello Ross! Thanks for sharing your code and releasing all the model weights. It would be nice if you could add the `args.yaml` to the repo whenever you release new...

I made a small modification in provision.sh in order to quickly change the password for MySQL. The password is defined in MYSQL_PW variable.

# What does this PR do? The `ImageVisualizer` doesn't need `wanbd`. This is the responsibility of the logger. We are trying to use a different logger and the `ImageVisualizer` crashes...

`affine` creates artefacts on the edges of the image

4

### 🐛 Describe the bug When employing the affine functional operation (in both v1 and v2), it's evident that black borders are introduced around the image, even when the fill...

Forward metric name to `update_metric`

7

## 🚀 Feature Request ## Motivation `get_metrics` returns a mapping between strings and `Metric`s. However the name isn't available in the `update_metric`. Checking for types might not be sufficient to...

Trainer.fit is missing the `optimizers` parameter

3

Hello, The `.fit()` method of the Trainer is [missing the `optimizers` parameters](https://github.com/mosaicml/composer/blob/4c5ba954e3007ce2af6eb3003efa9d76de38c959/composer/trainer/trainer.py#L1611C17-L1611C17) although it is [part of its documentation](https://github.com/mosaicml/composer/blob/4c5ba954e3007ce2af6eb3003efa9d76de38c959/composer/trainer/trainer.py#L1725). It would be nice to keep the optimizers and the schedulers...

Add server-side dry-run for apply, create, patch, replace, delete and deletecollection

2

This contribution exposes a `dry_run` parameter equivalent to `kubectl --dry-run`

[MSHARED-562] Color recognition based on color related methods' name

1

this modification take into account the background color and not only the foreground one. The distinction is made by starting color name with 'bg' og 'fg'. Example of `.mavenrc` :...

`pytest`: Append to coverage report

1

`pytest` is used twice, once for unit tests and once for integration tests. The second execution no longer overrides the coverage report generated by the first one.