Document fix for literal_compare == False

[jemand771]

While this should be obvious to experienced ansible users, I didn't know you could just use the not keyword like that. Documenting this doesn't take up much extra space but can potentially save time wihle fixing linter warnings.

[jemand771]

I haven't built this since it's a very small change and nothing should really break.

Feel free to close this if you feel like it adds too much noise

edit: oh well, looks like something did break. I'll look at this later

[4ch1m]

I haven't built this since it's a very small change and nothing should really break.

Feel free to close this if you feel like it adds too much noise

edit: oh well, looks like something did break. I'll look at this later

I don't think the errors are caused by your PR.
One of my PRs also fails due to the same problems.

I believe it has something to do with these changes: #3117

I've spent quite some time to understand what's going on; trying to fix it.
No luck so far. 😢

Maybe @ssbarnea can help us out.

[4ch1m]

I've spent quite some time to understand what's going on; trying to fix it. No luck so far. cry

Maybe @ssbarnea can help us out.

I found the root cause of the issue.

The store.json is under version control and part of the unit-tests.

The file holds several ETags of GitHub-server-files/-resources.

IMHO this is not suitable for unit-tests, since ETags are - per definition - non-deterministic (check: ETag).

Meaning: It's up to the server(-implementation) how ETags are being generated; and how/if they change over time.

@ssbarnea : Maybe we should find a workaround for this?

[jemand771]

ah, thanks for looking into that! I couldn't really figure out what was frong at first glance.
I just saw something about failed schemas and thought that maybe help texts are only allowed to one paragraph long or something like that, but apparently that's not it