Marc Mueller

Opened #1327 with a simple fix. Let's hope someone can get to it quickly so this is fixed.

Hi guys, I'd like to continue with this one. Since the time I left it, the testing structure in Home Assistant was changed which allows for a better performance comparison...

Just merged https://github.com/pylint-dev/astroid/pull/2380 which should at least improve the situation a bit. Instead of ``, the module name will be included in the warning message. Tbh I'm not sure if...

> > As an example, most of them I see for [Home Assistant](https://github.com/home-assistant/core), I wouldn't have noticed if not for pylint. > > @cdce8p Do you have a example you...

I was torn myself as it would be trivial to just ignore all SyntaxWarnings when building the AST. However, in case of HA the errors are mainly emitted for parts...

> I think I'm still missing some context -- are you saying there are parts of HA that not only aren't covered by pytest, but aren't covered by pylint? Why...

Writing this: That would be an argument to ignore the `SyntaxWarnings` entirely tbh.

Thanks for the update @kotewar! > However to also ensure that lot of configuration is not in place, as said by other users in #94 we are trying to avoid...

[`v3.2.4`](https://github.com/actions/cache/releases/tag/v3.2.4) was just released which adds a new option to `actions/cache` and `actions/cache/restore`: `fail-on-cache-miss`. https://github.com/actions/cache/blob/main/restore/README.md#exit-workflow-on-cache-miss

I've implemented a possible solution with #1041. A `dry-run: true` option would work well from my initial testing. If someone else wants to test it ```yaml - uses: cdce8p/cache@restore-dry-run with:...