Ryan Leonard

@wabiloo, I notice that `p.parse_known_args()` is being called where `p` is the 2nd subparser, not the top-level parser. I think the intention might be to actually call `ap.parse_known_args()`, which seems...

Great note, I also ran into this. I dug into [BasePipelineTest.groovy and found there is an `addEnvVar` method defined](https://github.com/jenkinsci/JenkinsPipelineUnit/blob/master/src/main/groovy/com/lesfurets/jenkins/unit/BasePipelineTest.groovy#L540)! Perfect! I've updated the example to use `addEnvVar`: > ℹ Also,...

On my Jenkins Agents (CICD servers), this has not been an issue. It really seems the issue is related to my "mashing ctrl+c to cancel a build and instead rapidly...

> Bumping this. This would be incredibly helpful. I want to transition my team to using Mermaid but it's hard to justify if labels aren't legible without hacky fixes. This...

Today, I'm noticing this issue issue consistently, even though I did **not** use "ctrl+c" consistently. Between yesterday and early this morning, I was able to use ansible-runner for some 20-40...

Fair point! Thanks for taking a look, @Shrews! 🙏 I was surprised when the issue came back up a couple of weeks ago without using "ctrl+c". I do definitely wonder...

The problem is also reproducible on `9.1.0` when fetching "hardware" data. It was also solved for me by installing `xmltodict` Python module.

A fix for this https://github.com/NativeScript/playground-tutorials/pull/56

Thanks for taking a look at this @Ruchip16! From a triage perspective, issue #534 is a major concern for my team -- if you are in a space of triaging...

I found a workaround! * Use the `juniper.device.config` Ansible module (instead of the `junipernetworks.junos.junos_config` Ansible Module.) That `juniper.device.config` Ansible Module does require using the "ignore_warnings" option to workaround this issue....