- User Since
- Nov 24 2016, 9:05 AM (200 w, 3 d)
Mar 15 2020
Sep 29 2019
Sep 24 2019
Should I land it on master or it seems good enough for the stable branch?
Sep 22 2019
Jun 27 2019
Jun 23 2019
Just to clarify the email used is going to be public anyway in the commit history.
Emails on identity.kde.org are only public for developers or to sysadmins. Can you post it here?
Jun 18 2019
Thanks for the patch.
Hi, thanks for the patch.
Jun 13 2019
Hi, thanks for the patch. Hopefully this is the last calibration issue, unfortunately I can't really test/track them down because I currently don't have access to a screen tablet.
I should make a bugfix release with it in the next few days.
May 23 2019
May 20 2019
May 2 2019
Apr 28 2019
Mar 13 2019
Mar 10 2019
- do not ignore results of PostingDB::iter in case of an error/end of db
Feb 21 2019
- fix MTimeDB::get loop
- review warning fixes
Feb 9 2019
- fix ::del error logging criteria, don't return without closing cursor in
- update logging per review
is it now how it's supposed to look in the end? not really sure where .category syntax is defined
- update categories per review
- use new syntax for baloo.categories
- move new logging category to D18873: add baloo engine debugging category
- clean up rest of the asserts
Feb 3 2019
I've chosen those bugs based on backtraces I could get myself but without core dumps I can't vouch for that, even with core dumps it'd be hard to tell. Alternatively I can CCBUG and after this gets into a release, ask in those bugs people if they still experience the crash and close them if they won't get back in a month or so.
- For now, logging is the only way to know if there's something bad going on. In that case I would suggest to at least increase severity of those messages - it would increase chances users will notice it. For example, use qCCritical (but this would also require additional check for okayish/non-critical return codes, such as MDB_NOTFOUND)
These errors have good potential to flood users log files. I get around 30 megabytes of those on each boot. I'd rather see them disabled by default.
It might make sense to add a catch-all error message somewhere on higher level, that would get printed out once, but I haven't looked yet where such message could be placed.
- Looks like this patch is composed of two parts - introducing new logging category and and improving error handling. It would be also nice to split those into two separate patches.
- There are a lot of redundant Q_ASSERT_X left, which could be removed. I suggest just grep'ing over the code to catch'em all. I've started marking them here, but then I gave up - too many of them.
- There are also several unchecked return codes as well, such as inside *DB::size() calls. Those can also be found by grep'ing over Q_ASSERT_X.
I'll look into these this week.
Feb 2 2019
- unbreak documentdatadb::contains, oops :(
Dec 16 2018
Dec 9 2018
Sep 20 2018
Sep 19 2018
Sep 12 2018
Sep 11 2018
neither QWidget::adjustSize() nor QWidget::adjustedSize() seem to use devicePixelRatio (https://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/kernel/qwidget.cpp#n8665), but I can't test that to vouch that it works on HiDPI as intended
I can land it as is but I don't really want to break kcmshell further for HiDPI users
Sep 10 2018
Sep 5 2018
Landed it on 5.1, messed up with arc so it didn't close the diff
Sep 4 2018
Backtraces are a bit inconsistent, usually it ends with malloc aborting with invalid porinter or other memory error
- fix typo
Sep 3 2018
Aug 28 2018
Aug 13 2018
Aug 12 2018
I don't know, it's frameworks after all but I guess I can land it today since it's a popular bug. Should I just land it on master since there seem to be no other branches?
Aug 8 2018
- add link to qt bug
I think it's this bug/suggestion: https://bugreports.qt.io/browse/QTBUG-10459
Context for the size hint limitation this patch is supposed to circumvent: https://code.woboq.org/qt5/qtbase/src/widgets/widgets/qscrollarea.cpp.html#403