1. 12 Nov, 2020 1 commit
  2. 16 Sep, 2020 1 commit
    • Harald Sitter's avatar
      disabe ksycoca rebuilding on runner threads · 5a648c56
      Harald Sitter authored
      this frees the internal per-thread inotify instance used to watch
      database changes meaning runner applications no longer claim N inotify
      instances (N=size of threadweaver pool).
      the database is still reloaded by ksyscoca internally if it finds the
      backing file has changed.
      
      CCBUG: 423818
      5a648c56
  3. 14 Sep, 2020 1 commit
    • Harald Sitter's avatar
      adjust relevance of kcms in service runner · a3f22cde
      Harald Sitter authored
      kcms are handy but not nearly as handy as an actual application. this is
      particular notable with the test case where the user could type 'virt'
      but that wouldn't have pushed virtualization software to the top but kcms
      since kcms are kde things so they always get a .09 bump to
      relevance.
      
      the revised scoring excludes kcms from the bump and further reduces the
      relvance by the tiniest fraction. this results in all applications that
      match at least as well as the KCM to outscore the KCM
      a3f22cde
  4. 15 Jun, 2020 1 commit
  5. 19 Mar, 2020 1 commit
  6. 04 Sep, 2019 1 commit
  7. 27 Aug, 2018 1 commit
  8. 29 Jan, 2018 1 commit
  9. 31 May, 2017 1 commit
  10. 07 Feb, 2017 1 commit
    • Harald Sitter's avatar
      make services disqualification much stricter · 7b1dc9a4
      Harald Sitter authored
      Summary:
      after the recent set of changes to disqualification we ended up with a bit
      too lax disqualification. if we saw the exec OR the storageid we'd
      hence forth disqualify a service with either of them being equal.
      
      in case of system settings this causes a match problem. systemsettings
      has two desktop files one !KDE and one OnlyKDE they are however exactly
      the same except for a different name and storageid. as a result if the !KDE
      one is encountered first it will be disqualified on account of
      noDisplay=true and marked as seen. when the OnlyKDE systemsettings is then
      iterated it will already have the Exec entry in the seen list and be
      disqualified on account of that.
      
      to prevent this type of confusion make it a requirement to match both
      storageid AND exec before disqualifying.
      
      it may actually be suitable to drop the exec altogether. say I copy firefox
      into the user local applications dir and set it NoDisplay=true but change
      the exec. this would still lead to the system-wide firefox being found as
      it is not getting disqualified. long story short: maybe we should
      disqualify services solely on the storageid?
      
      Test Plan:
      - new autotest case
      - fails without changes
      - passes with changes
      
      Reviewers: broulik
      
      Reviewed By: broulik
      
      Subscribers: plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D4415
      7b1dc9a4
  11. 23 Dec, 2016 1 commit
    • Harald Sitter's avatar
      add simple test rig for service runner · e21d625a
      Harald Sitter authored
      Summary:
      - make sure that chrome apps have lower relevance than chrome itself
      - makes sure that konsole has higher relevance than yakuake (latter
        only references onsole in the comment entry)
      
      Test Plan:
      - it passes and at a glance doesn't seem to break my production sycoca
      
      Would be cool if @dfaure could take a look at the ksycoca setup to make sure the test doesn't negatively impact the production cache.
      
      Reviewers: broulik, dfaure
      
      Reviewed By: dfaure
      
      Subscribers: dfaure, plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D3707
      e21d625a