Paul Sanchez

Same issue here. I'm currently having to upload a different application version for each environment that I run an application on because of this. I'd imagine one way that might...

Just ran into this as well. I'm running VirtualBox version 6.1.38 on MacOS 12.6. I did some sleuthing of the code with a bunch of print statements and found that...

> @basicdays want to create a PR for that (with a [changelog fragment](https://docs.ansible.com/ansible/devel/community/collection_development_process.html#creating-a-changelog-fragment))? While this isn't a great long-term fix (as you noted), at least it makes it restores basic...

@notetiene Yeah not sure which version. My guess is this change in information format might have started with version 6.1 perhaps.

Found a couple more: - `-ms-grid-column-align` - `-ms-grid-row-align`

Using the follow definition file as a temporary workaround. ``` export type MSGridRowAlignProperty = 'start' | 'end' | 'center' | 'stretch'; export type MSGridColumnAlignProperty = 'start' | 'end' | 'center'...

Just ran into this, I also think this should be added to the documentation before closing.

This would be insanely awesome. Would this also cover the situation of not having to set `cache-from` and `cache-to`? My understanding is that image layer caching by default is kept...

Running into this as well. With the `setTimeout` workaround that @ulion used, it seems to _almost_ work. Except `nodemon` seems to just start the next process before the previous process...

Fwiw I do actually have the following code. Unfortunately it still causes the same issues on the latest version (3.0.1). Still stuck on version 2.0.1: ```js // set nodemon restart...