Is there a particular reason that yaml_to_string() sorry about that, I was copying from the example in #539 and wasn't really paying attention to the name. I'll follow up in the ansible-lint issue, thanks
Is there a particular reason that yaml_to_string() sorry about that, I was copying from the example in #539 and wasn't really paying attention to the output. I'll follow up in the ansible-lint issue, thanks
Extra \ inserted in transformation with 0.18.11
Thank you for your time looking at this. I'm still a bit confused as to what is going on, as we do try in the plugin to set the name/source field correctly when using insert_input. In the above, I'm not sure the lines = f.read() quite works because I don't think that puts it into a nice array of lines for parsing; so I think it might hide the issue. I have been back to our build environment and found some more details -- including bisecting this down to a change between sphinx 5.2.3 and 5.3; see...
Thanks -- I guess the problem here is that this directive uses insert_input to insert input which then just happens to have a .. include:: directive inside it. It seems like the suggestion is to directly modify the document.include_log which is probably close to the change I've suggested in our actual code at https://review.opendev.org/c/zuul/zuul-sphinx/+/862215/2/zuul_sphinx/zuul.py It feels like a bit of a breaking change to insert_input if the include log needs to be manually managed around that...
Invalid circular inclusion warning when including multiple documents from a directive
This was using the extensions from the release jar files So all signs point to the...
I've attached what I can use to replicate it Included is the jstack logs from both...