Jay Shepherd

Apologize for the misunderstanding, do you have an example of the raw messages that are received on the buffer? The regex currently does a match for messages that include DEVICE;ID...

Yeah looking to just get what the socket sees. So that `s.recvfrom(1024)` in discover being assigned to `message` is what will ultimately be passed to the new function to be...

Here is a working refactored function example. Not sure if this is more readable than regex, let me know your thoughts: ``` def decode_discovery(message: Tuple[bytes, Tuple[str, str]]) -> Tuple: """...

I ran into this as well even without yamllint config file. Just using default `ansible-lint --fix` followed by `ansible-lint` resulted in error on one of our lines that was multi-line...

> I found out that 'Legacy IOS' uses `RO` and `RW`, but IOS XE uses `ro` and `rw` instead. I tested it with my legacy IOS devices and it's working...

For reference our pip is locked to ``` ansible-core==2.16.3 ansible==9.2.0 ``` and collection is set to ``` collections: - name: cisco.ios version: 6.1.2 type: galaxy ```

Another example - in order to query logs for hip we're construction setups like this: ``` (sourcetype="pan:hipmatch" OR log_type="HIPMATCH") AND (hip_type=profile OR HipMatchType=profile) ```

Might need to add some configuration to Codacy. "assert" statements are the proper way of referencing test statements in Pytests framework.

Thanks for the test strings. Yeah the Regex was moved into a function to allow me to test the before and after more easily as a unit with predictable results....

So what I was looking to add to testing was essentially line 859 where `m` equals something from the receive buffer. I was hoping to get examples of `m` maybe...