Re: New santizer warning in KF 5.98 headers

2023-01-10 Thread Michael Reeves
Thanks. I would say your right there this would definitely have caught
someone's attention if didn't work in practice with what kde needs.
Santizers are by design quite pedantic as serves there purpose well.

On Tue, Jan 10, 2023 at 5:34 PM Albert Astals Cid  wrote:

> El dimarts, 10 de gener de 2023, a les 22:49:43 (CET), Michael Reeves va
> escriure:
> > /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime error:
> > load of value 4294967295, which is not a valid value for type
> > 'Qt::ConnectionType'
> >
> > SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
> > /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64 in
> >
> > The issue stems for assigning an int to a enum which is internally
> > considered unsigned and possibly smaller than the four byte int. If this
> is
> > doing what we expect than I need a way to shut off the warning.
>
> That code has been there since May last year, so not exactly "new".
>
> Given it doesn't seem to be crashing it would seem it's one of those
> "undefined
> but it works in all the compilers we care about".
>
> Of course patches to make the sanitizer are really welcome :)
>
> Cheers,
>   Albert
>
>
>
>


Re: New santizer warning in KF 5.98 headers

2023-01-10 Thread Albert Astals Cid
El dimarts, 10 de gener de 2023, a les 22:49:43 (CET), Michael Reeves va 
escriure:
> /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime error:
> load of value 4294967295, which is not a valid value for type
> 'Qt::ConnectionType'
> 
> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
> /usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64 in
> 
> The issue stems for assigning an int to a enum which is internally
> considered unsigned and possibly smaller than the four byte int. If this is
> doing what we expect than I need a way to shut off the warning.

That code has been there since May last year, so not exactly "new".

Given it doesn't seem to be crashing it would seem it's one of those "undefined 
but it works in all the compilers we care about".

Of course patches to make the sanitizer are really welcome :)

Cheers,
  Albert





New santizer warning in KF 5.98 headers

2023-01-10 Thread Michael Reeves
/usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64: runtime error:
load of value 4294967295, which is not a valid value for type
'Qt::ConnectionType'

SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
/usr/include/KF5/KConfigWidgets/kstandardaction.h:261:64 in

The issue stems for assigning an int to a enum which is internally
considered unsigned and possibly smaller than the four byte int. If this is
doing what we expect than I need a way to shut off the warning.


Fwd: [GSoC Mentors] GSoC 2023 open for org applications January 23 - February 7

2023-01-10 Thread Johnny Jazeix
 Hi,

Are there people willing to help co-admin this year? For now, we are 3
admins so one more would be nice to share the workload.

I've updated the skeleton wiki page to create the 2023 season:
https://community.kde.org/GSoC/2023/Ideas.

Please start discussing among your teams what ideas will be great to have
this year and who is willing to mentor, as the organisation application
date needs to apply between the January 23 - Feb 7, 2023 and we need a wiki
page filled with ideas by then.

More info can be found at
https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html

Cheers,

Johnny

-- Forwarded message -
De : 'sttaylor' via Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>
Date: lun. 14 nov. 2022 à 23:51
Subject: [GSoC Mentors] GSoC 2023 open for org applications January 23 -
February 7
To: Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>


We’re pleased to announce

the Google Summer of Code 2023 program and timeline
. GSoC Org
Applications are open from January 23 - Feb 7, 2023.

In 2022 we implemented our biggest changes to the program in its 18 year
history and had an overwhelmingly positive response to the changes
(extended timelines, medium and large size projects and opening eligibility
beyond students) so we are keeping the changes as we go into 2023 with a
couple of minor tweaks.

   1.

   Per the conversation on the mentor list this summer, we are expanding
   the eligibility to include students and beginners to open source
   development. There was some confusion about students who might have some
   experience in open source so we have fixed that with this new eligibility
   rule.
   2.

   The other change is that we are back to allowing a person to be accepted
   as a GSoC Contributor up to 2 times (regardless of when their first GSoC
   acceptance was). This assumes they could still be considered a beginner -
   ie. they didn’t participate as a GSoC student in 2015 and have been
   actively involved in open source development since then and want to come
   back 8 years later to be a GSoC Contributor.
   3.

   We have shifted the timeline to start a couple of weeks earlier, so that
   the program wraps up for the standard 12 week projects by early September
   which is generally what the schedule looked like for many of the past 18
   years.

*Spreading the word about GSoC*

The GSoC 2023 flyer

and the new, more colorful and exciting GSoC 2023 slides

are available for you to use in any presentations you wish to do about
GSoC. We need your help to spread the word amongst your circles.

We encourage you to explore our resources
, timeline
, the
Contributor/Student
Guide and Mentor Guide
 as well.


*Have a group you think GSoC Program Admins should reach out to?*

Diversity in open source communities is vital to the health of our
communities. Please spread the word about GSoC to communities in your
country or in your network particularly those that reach underrepresented
groups in open source. If you have a suggestion for a group you think the
GSoC team should add to our list of contacts that we send out emails to
about the program early in the new year, or if you have a group that you
think would be a good opportunity for GSoC Administrators to give a talk
about GSoC please email us at gsoc-supp...@google.com with their details
(email and contact person if you have one available).


*See you at FOSDEM!*

As Chris mentioned in the GSoC 22 Mentor Summit a couple of weeks ago, our
team is very excited to attend FOSDEM in Brussels in 2023. We will send
more details in January but we are in the early stages of planning a GSoC
Meetup for Saturday night during FOSDEM as we have done in previous years.
Looking forward to seeing many of you in Brussels in February!


*GSoC Videos*

We have been busy working with our mentors and GSoC contributors to create
new GSoC videos as they are a popular medium for new folks to learn about
GSoC.

A HUGE thank you to our mentors that helped with the new ‘Introduction to
Google Summer of Code’ video  (Adrian,
Benjamin, Ann, Rāzvan,  Meenakshi, Srishti and Gabriel). And thanks to our
mentors and org admins that created 25 GSoC Org videos

helping interested participants understand more about the many 

Re: GItlab update

2023-01-10 Thread Eugen Mohr

Hi Ben

Since the update “Project information” -> “activity” doesn’t show
“Issues” anymore. The tab “Issues events” doesn’t show issues neither.

Example: https://invent.kde.org/multimedia/kdenlive/activity vs.
https://invent.kde.org/multimedia/kdenlive/-/issues.

Eugen

Am 08.01.2023 um 11:03 schrieb Ben Cooksley:

Hi all,

This evening I updated our Gitlab instance at invent.kde.org
 to the latest version - 15.7.1.
The release notes for this can be found at
https://about.gitlab.com/releases/2022/12/22/gitlab-15-7-released/

Of particular note for folks are the following:
- Gitlab CLI Tool: https://docs.gitlab.com/ee/integration/glab/
- Using a SSH key to sign your commits:
https://docs.gitlab.com/ee/user/project/repository/ssh_signed_commits/
- New Web IDE: https://docs.gitlab.com/ee/user/project/web_ide_beta/
(based on VS Code)

Please note that the new VS Code based Web IDE is currently in beta,
if you experience issues with it you can disable it in your
preferences: https://invent.kde.org/-/profile/preferences

Should there be any issues, please let us know.

Thanks,
Ben