Skip to content

Crash with some network-specific ignore lists

Issue

On my local QuasselClient, I have a bunch of ignore list entries that look like this:

{
   "Strictness": "Dynamic",
   "Rule Type": "Sender",
   "Ignore Rule": "username!.+",
   "Regular expression": true,
   "Scope": {
      "Type": "Network",
      "Rule": "*network-name"
   }
}

(screenshot from the interface)

What causes QuasselDroid-ng to fail, where there are no issues that I know of with Quasselclient, Quasselweb or QuasselDroid (legacy) is the * before network-name. (crash report)

This happens even when the rule is not enabled.

(note: the rule was written as such because my networks are actually called [x] network-name to have them well-organized. I am aware it's pretty crude, but it worked.)

Steps to reproduce

  1. Use a quasselclient that supports ignore list rules editing
  2. Add a new dynamic entry with a scope that is Network-wide, not Global
  3. Set the Scope rule as a network name starting with a wildcard
  4. Try to initialize a connection to the core from a quasseldroid-ng client
  • Expected outcome: the client connects and the rule is effective
  • Actual outcome: the client crashes because the regex does not compile

Conclusion

I don't know if that's actually a bug, or if QuasselDroid-ng is actually behaving properly and the other clients are just too lax.

Edited by karlyeurl