Moved over to https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/427.

Can we please continue this over on Gitlab?

Can we please continue this over on Gitlab?

Phabricator is not used for bug reports but rather for developer task tracking, which is already being discussed at T11859. Please file bug reports at https://bugs.kde.org.

hurikhan77 : thank you very much for post.
Yes, I use dual boot with Windows 10.

In T13298#233444, @jackyalcine wrote:

To be honest, this is something I wanted to contribute. I've had moments as I'd code that my computer would lock up and it was because baloo was indexing pictures (not even the source code). I'm not sure but it's not explicit that Baloo runs only when the computer is idle. I'd want to extend this to communicate:

• How much time / progress is made for a full index

jackyalcine: thank you very much for answer.
I am sorry, I am not programmer, I am not understand of all your questions.
I send you any screenshots. In Stacer app monitor application you can see up applications who use most processor.
Baloo file extractor use sometimes 1 GB RAM

To be honest, this is something I wanted to contribute. I've had moments as I'd code that my computer would lock up and it was because baloo was indexing pictures (not even the source code). I'm not sure but it's not explicit that Baloo runs only when the computer is idle. I'd want to extend this to communicate:

Shipit!

This looks abandoned or stalled. @michaelh do you have any plans on this front?

This looks abandoned with 2 years of no movement. @michaelh do you still feel this is a WIP?

This looks abandoned with 2 years of no movement. @michaelh do you still feel this is a WIP?

This looks abandoned, no movement in over two years. @michaelh did you still want to introduce docId instead of quint64? This diff was supposed to supplant D10851 but seems to have fallen asleep as well. (In retrospect, perhaps I would have suggested first introducing just using docId = quint64; somewhere, to get the more-expressive-type-name part out of the way before real changes)

This looks abandoned, no movement in over two years. @michaelh do you want to explicitly abandon this one, so we have a clean slate for invent? None of the docId type changes seem to have made it to master (see also D10856)

Strange. It worked with gmake locally, but failed on the Flathub buildbot again (https://flathub.org/builds/#/builders/32/builds/19809, only x86_64 failed, not arm or aarch64).

Indeed. It failed with cmake 3.15.2 + ninja 1.9.0 and worked with make (4.2.1).

Your build system seems to be broken. The "missing" methods are statically linked, see src/file/extractor/CMakeFiles/baloo_file_extractor.dir/baloosettings.cpp.o

In D29454#664222, @ngraham wrote:

Nice!

Nice!

Sorry for the delay. Makes sense.

This has been pending for more than two weeks now, without any sort of review ...

Ping!

• use continue

• fix another stupid mistake

• more fixes

• implement review

Good to me

whitespace

Wrap at ~80 characters, please.

In D28972#657193, @bruns wrote:

In D28972#657192, @meven wrote:

@bruns does this sounds good to you ?

The code looks fine. Can you extend the summary so it is immediately visible where this is needed/useful, without having to folllow the bug link?

In D28972#657192, @meven wrote:

@bruns does this sounds good to you ?

@bruns does this sounds good to you ?

In D28932#657011, @ngraham wrote:

I'll get around to reviewing this soon. I'm trying to figure out of I think the loss is acceptable.

I'll get around to reviewing this soon. I'm trying to figure out of I think the loss is acceptable.

Ping!

Ping!

Instead of adding Windows support where the platform *is* different, you introduce additional differences.

In D20739#653647, @rjvbb wrote:

any bug reports for the Windows platform will be rejected immediately then.

Because they aren't already given that baloo only works on Linux and *BSD?

This is the sort of attitude that always makes my eyes roll whenever I see a reference to the idea of support in most KDE software.

any bug reports for the Windows platform will be rejected immediately then.

In D20739#653485, @rjvbb wrote:

Qt 5.10. is required since KF 5.55: https://kde.org/announcements/kde-frameworks-5.55.0.php.

True, but not relevant here because the issue is not with KF5 APIs but with QMap. The frameworks relevant for baloo all build against Qt 5.9 either without or with minimal patching (which in essence reintroduce removed code).

Ultimately this wasn't difficult, so apologies for the noise!