Felix Fontein
Felix Fontein
Ah, so that's different from "normal" `rebuild_merge`. :) I would be fine if it is somehow possible to restart CI, it doesn't matter that much whether it is via `rebuild_merge`...
incorrect caching: classified PR as new_module even though the module it modifies was merged earlier
Another case: ansible/ansible#56103, ansible/ansible#56186
incorrect caching: classified PR as new_module even though the module it modifies was merged earlier
In this new case, the new PR adds another module and modifies the previously merged module, and gets the "this PR contains more than one new module" error.
What MIME type should be used? I guess not `text/html` :-) I guess `text/plain` would be a simple solution, since every server should have support for that.
This is really problematic since these internal names should not be exposed to users, and must really not be used. One problem with redirects is that it is totally unclear...
This is probably more a bug in https://github.com/ansible/ansible-language-server since all the code that does something is in there. @ssbarnea does it makes sense to create a new issue there, or...
@ganeshrn @priyamsahoo any update on this? From my point of view this is a pretty critical bug that should be fixed as soon as possible.
Some updated would be great indeed. This is a very serious bug that has been around for at least two months now.
I created an ansible-lint rule which flags the invalid actions generated: https://github.com/ansible/ansible-lint/pull/2572
@priyamsahoo by not treating this as a bug you are risking that your uses will suffer a lot when they have to undo all these suggestions.