1. 22 Jan, 2021 3 commits
  2. 21 Jan, 2021 3 commits
  3. 19 Jan, 2021 5 commits
    • Harald Sitter's avatar
      include the drkonqi version in reports · 621ea6dd
      Harald Sitter authored
      when looking at odd ball reports that ended up on bugzilla I'm never
      quite sure what version let the report get through. in the interest of
      actually debugging defects with drkonqi we'll therefore want the drkonqi
      version itself. this way it's easier to pin point a version that might
      have (e.g.) problems detecting a trace as useless
      
      also has the rather advantageous side effect that drkonqi is part of
      plasma so its version will generally be the same as the rest of plasma
      giving a sense of what versions are in play when plasma is involved
      621ea6dd
    • Harald Sitter's avatar
      report all reproducible selections · 46948b3a
      Harald Sitter authored
      (also switch over it so the compiler warns when things aren't mapped)
      
      there isn't a practical reason to exclude the unsure reproducibility
      scenario. knowing that one doesn't know if it is reproducible is
      information, not very useful one but information none the less
      46948b3a
    • Harald Sitter's avatar
      capitalize consistently · d4aebce6
      Harald Sitter authored
      d4aebce6
    • Laurent Montel's avatar
    • Laurent Montel's avatar
      Don't include QtTest · 41530ec2
      Laurent Montel authored
      41530ec2
  4. 12 Dec, 2020 1 commit
    • Christoph Roick's avatar
      Modify DBus service name to allow using QDBusServiceWatcher · 243461e9
      Christoph Roick authored
      Fix the DBus connection which allows passing a debuggee to one of the
      KDevelop debuggers for future versions (>=5.7) of KDevelop. Instead of the
      deprecated serviceOwnerChanged signal, a QDBusServiceWatcher is used,
      which requires a different naming scheme. See KDevelop commit 69ef7ea8.
      
      This change has no impact on the connection with current versions of KDevelop.
      243461e9
  5. 11 Nov, 2020 2 commits
  6. 05 Nov, 2020 1 commit
  7. 03 Nov, 2020 1 commit
    • Harald Sitter's avatar
      fix buttongroup state toggles · b21006b7
      Harald Sitter authored
      this was recently changed on the BugAwarenessPage and broke state
      tracking as idPressed is emitted when pressing down, before the group
      state actually switches. the yes/no group on that page was effectively
      inverted as updateCheckBoxes was called before the property update and
      thus when the user clicked Yes the internal state in the slot was still
      No and vice versa.
      
      the duplicates dialog similarly was wrong but it's much harder to
      stumble over since the relevant UI elements are only visible when trying
      to mark a bug duplicate to a closed bug or a "common" bug
      
      use the idClicked signal instead, it's what the code originally used (as
      the now deprecated buttonClicked)
      
      BUG: 428346
      b21006b7
  8. 31 Oct, 2020 1 commit
  9. 29 Oct, 2020 1 commit
  10. 23 Oct, 2020 1 commit
  11. 22 Oct, 2020 6 commits
  12. 03 Oct, 2020 1 commit
  13. 24 Sep, 2020 1 commit
  14. 21 Sep, 2020 2 commits
  15. 20 Sep, 2020 1 commit
  16. 17 Sep, 2020 3 commits
  17. 16 Sep, 2020 1 commit
  18. 31 Aug, 2020 1 commit
  19. 17 Aug, 2020 2 commits
    • Ahmad Samir's avatar
      Fix the port to QRegularExpression · 7d2cfbe4
      Ahmad Samir authored
      I made some mistakes when porting from QRegExp to QRegularExpression:
      - With QRegularExpression::DotMatchesEverythingOption enabled, better use
        QRegularExpression::anchoredPattern and not rely on "^" and "$" to anchor
        the pattern (anchoredPattern uses "\A" and "\z" which is more accurate/precise)
      - Disable QRegularExpression::DotMatchesEverythingOption before subsequent
        setPattern calls, it's only needed for the first matching
      - When calling setPattern, obviously the previous QRegularExpression::anchoredPattern
        isn't going to be in effect, call it again if you want the pattern to be
        anchored
      
      Thanks to sitter for the unit tests that exposed the issue, and for
      spotting the issue with needing to anchor the pattern.
      
      All unit tests pass.
      7d2cfbe4
    • Harald Sitter's avatar
      add gdb line test for thread start and current thread markers · 7512f620
      Harald Sitter authored
      these tests do not presently pass because they regressed in the
      qregularexpression port 8d8062fe
      
      as for exmaple observed in https://bugs.kde.org/show_bug.cgi?id=423222
      which lacks the marker lines
      
      at a glance exactMatch->hasMatch wasn't a good port and so the line
      falls into the CRAP regex' `0x[0-9a-f]+.*|` which would match line
      containing a hex number
      7512f620
  20. 10 Aug, 2020 1 commit
  21. 08 Jul, 2020 1 commit
  22. 18 Jun, 2020 1 commit