KDE CI: Frameworks » kdoctools » kf5-qt5 WindowsMSVCQt5.11 - Build # 12 - Fixed!

BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20WindowsMSVCQt5.11/12/ Project: kf5-qt5 WindowsMSVCQt5.11 Date of build: Wed, 31 Oct 2018 03:50:31 + Build duration: 7 min 2 sec and counting JUnit Tests

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.9 - Build # 47 - Fixed!

BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.9/47/ Project: kf5-qt5 SUSEQt5.9 Date of build: Wed, 31 Oct 2018 03:50:31 + Build duration: 1 min 13 sec and counting JUnit Tests Name: (root)

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.10 - Build # 61 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.10/61/ Project: kf5-qt5 SUSEQt5.10 Date of build: Wed, 31 Oct 2018 03:50:31 + Build duration: 1 min 6 sec and counting JUnit Tests Name: (root)

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.9 - Build # 46 - Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.9/46/ Project: kf5-qt5 SUSEQt5.9 Date of build: Wed, 31 Oct 2018 03:39:36 + Build duration: 4 min 2 sec and counting JUnit Tests Name: (root)

KDE CI: Frameworks » kdoctools » kf5-qt5 WindowsMSVCQt5.11 - Build # 11 - Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20WindowsMSVCQt5.11/11/ Project: kf5-qt5 WindowsMSVCQt5.11 Date of build: Wed, 31 Oct 2018 03:39:36 + Build duration: 2 min 9 sec and counting JUnit Tests

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.10 - Build # 60 - Still Unstable!

BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.10/60/ Project: kf5-qt5 SUSEQt5.10 Date of build: Wed, 31 Oct 2018 03:39:36 + Build duration: 1 min 13 sec and counting JUnit Tests Name: (root)

KDE CI: Frameworks » baloo » kf5-qt5 SUSEQt5.9 - Build # 132 - Failure!

BUILD FAILURE Build URL https://build.kde.org/job/Frameworks/job/baloo/job/kf5-qt5%20SUSEQt5.9/132/ Project: kf5-qt5 SUSEQt5.9 Date of build: Wed, 31 Oct 2018 00:39:34 + Build duration: 5 min 52 sec and counting CONSOLE OUTPUT [...truncated

D15826: [Balooshow] Avoid out-of-bounds access when accessing corrupt db data

This revision was automatically updated to reflect the committed changes. Closed by commit R293:563dd3418b60: [Balooshow] Avoid out-of-bounds access when accessing corrupt db data (authored by bruns). REPOSITORY R293 Baloo CHANGES SINCE LAST UPDATE

D16344: Do not try to fallback to "less secure" protocols

This revision was automatically updated to reflect the committed changes. Closed by commit R241:e11d4d18f66a: Do not try to fallback to less secure protocols (authored by aacid). CHANGED PRIOR TO COMMIT https://phabricator.kde.org/D16344?vs=43997=44509#toc REPOSITORY R241 KIO CHANGES SINCE

D16529: make libssh module default to the "new" libssh config by default

broulik accepted this revision. This revision is now accepted and ready to land. REPOSITORY R320 KIO Extras BRANCH master REVISION DETAIL https://phabricator.kde.org/D16529 To: sitter, broulik, asn Cc: kde-frameworks-devel, kfm-devel, alexde, sourabhboss, feverfew, michaelh, spoorun,

Re: New contributor seeking guidance

Thanks for wishing to get involved in KDE development! We have the "junior-jobs" keyword in Bugzilla, which is a good place to start:

D16529: make libssh module default to the "new" libssh config by default

sitter created this revision. sitter added reviewers: broulik, asn. Herald added projects: Dolphin, Frameworks. Herald added subscribers: kfm-devel, kde-frameworks-devel. sitter requested review of this revision. REVISION SUMMARY - rename module from LibSSH to libssh so casing is consistent

Re: Getting Started With KDE

Hi Alex, Thanks for wishing to get involved in KDE development! It's good to hear you read through the Get Involved/Development page, that's a good start. As mentioned, we do have the Junior Jobs tag as a good start as well:

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

bruns marked an inline comment as done. bruns added inline comments. INLINE COMMENTS > poboiko wrote in app.cpp:74 > I haven't work with `QDataStream` before, but shouldn't `m_inputStream >> > nIds` do the same? (and same below) > And probably you should avoid magical constants (4, 8, etc) -

D16471: [RFC] Listen for added DBus interfaces instead of registered services

jgrulich added a comment. > This is RFC because: > > I'm not sure whether it's guaranteed that InterfacesAdded is emitted on service registration as well or both connections are necessary I'm not sure about this either. I'll build it locally and try to use it for a while. > I

D16520: proper kwalletd dbus service file for the legacy name

bruns added a comment. In D16520#350934 , @damjang wrote: > > but before doing this change the migration agent has to be changed. > > Can you expand on this what needs to be changed? I'd be happy to do it if it's in my capability

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

bruns added a comment. In D16523#350888 , @poboiko wrote: > That's nice! I'll test it a little. This step keeps binary compatibility with the current streaming format. The big cleanup happens in the next commit (D16524

D15464: [server] Touch drag support

davidedmundson accepted this revision. This revision is now accepted and ready to land. REPOSITORY R127 KWayland BRANCH touchDrag REVISION DETAIL https://phabricator.kde.org/D15464 To: romangg, #kwin, #frameworks, davidedmundson Cc: davidedmundson, kde-frameworks-devel, michaelh,

D16520: proper kwalletd dbus service file for the legacy name

damjang added a comment. > but before doing this change the migration agent has to be changed. Can you expand on this what needs to be changed? I'd be happy to do it if it's in my capability REPOSITORY R311 KWallet REVISION DETAIL https://phabricator.kde.org/D16520 To: damjang,

D15826: [Balooshow] Avoid out-of-bounds access when accessing corrupt db data

poboiko accepted this revision. poboiko added a comment. This revision is now accepted and ready to land. Yep, fine by me REPOSITORY R293 Baloo BRANCH oob2 REVISION DETAIL https://phabricator.kde.org/D15826 To: bruns, #baloo, #frameworks, poboiko Cc: anthonyfieroni,

D16416: z/OS CLIST file syntax highlighting

cullmann added a comment. Thanks for the needed info, will merge this. REPOSITORY R216 Syntax Highlighting REVISION DETAIL https://phabricator.kde.org/D16416 To: phily, #framework_syntax_highlighting, dhaumann, cullmann Cc: cullmann, dhaumann, kwrite-devel, kde-frameworks-devel,

Re:Getting Started With KDE

Hello Gregor, I am not at all trying to put off a newcomer, but I firmly believe that using search engines can help one get involved in KDE development with ease. If you find conflicting answers about getting involved in KDE, could you please report them? It's something we need to fix. Best

Re:Getting Started With KDE

> Amazing what search engines can do these days! This is ironic speech, isn't it? Such thing does not help to provide a warm welcome but rathers scares people off. Search engines can yield conflicting results and the question of the new guy is perfectly valid. Maybe an apology could be

Re:Getting Started With KDE

Hello! When working on open source projects, you shouldn't expect to always be guided by someone. A quick Google search for "KDE get involved" gives me this awesome article: https://community.kde.org/Get_Involved Then, assuming I need a simple task to start with, I google "KDE junior jobs",

Getting Started With KDE

To whom it may concern, Hello, I am a student new to KDE community. I want to get involved with KDE development to hone my programming skills and make contribution to KDE. But I don't know what work I can do and where do I start. Could anyone give me some guidance? It would be better if we can

New contributor seeking guidance

Hi all, I'm Remya, a CS sophomore and I would like to start contributing to KDE projects. I'm a KDE user have been working on projects in C++/Qt for the past few months. I would like to work towards beginner bugs. So, can anyone please suggest me some beginner bugs to start with? With Regards,

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

poboiko added a comment. That's nice! I'll test it a little. INLINE COMMENTS > app.cpp:74 > + > +memcpy(, buf, 4); > +for (quint32 i = 0; i < nIds; i++) { I haven't work with `QDataStream` before, but shouldn't `m_inputStream >> nIds` do the same? (and same below) And probably you

D15960: Don't check if file is directory based on mime-type

poboiko edited the summary of this revision. REPOSITORY R293 Baloo REVISION DETAIL https://phabricator.kde.org/D15960 To: poboiko, #baloo, #frameworks, bruns Cc: bruns, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, spoorun, ngraham, abrahams

Re: Getting Started With KDE

Hello Pranam, Thanks for the response. I wish I could be a part of the Google Code-In but unfortunately I am too old for this activities. Actually I am a first-year graduate student in Computer Science. But I started learning Computer Science since the master. So I have only less than one year

D16524: [Extractor] Use QDataStream serialization in place of cooked one

lbeltrame accepted this revision. This revision is now accepted and ready to land. REPOSITORY R293 Baloo BRANCH extractor REVISION DETAIL https://phabricator.kde.org/D16524 To: bruns, #baloo, #frameworks, ngraham, poboiko, lbeltrame Cc: kde-frameworks-devel, ashaposhnikov, michaelh,

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

lbeltrame added a comment. In general (for my limited Baloo knowledge) this makes sense. You might want to add a few CCBUGs if you are aware of specific bugs this alleviates (@ngraham or someone from the bugsquad may help). REPOSITORY R293 Baloo REVISION DETAIL