[Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 41
Liu, David
David.Liu at windriver.com
Fri Jul 21 01:43:19 UTC 2023
Hi Jeremy,
Thank you for providing feedbacks, for the log access, I think it's my network problem.
Yes, I'll try to fix as your solution pointed.
Regards,
David
-----Original Message-----
From: starlingx-discuss-request at lists.starlingx.io <starlingx-discuss-request at lists.starlingx.io>
Sent: Thursday, July 20, 2023 9:20 PM
To: starlingx-discuss at lists.starlingx.io
Subject: Starlingx-discuss Digest, Vol 62, Issue 41
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Send Starlingx-discuss mailing list submissions to
starlingx-discuss at lists.starlingx.io
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
or, via email, send a message with subject or body 'help' to
starlingx-discuss-request at lists.starlingx.io
You can reach the person managing the list at
starlingx-discuss-owner at lists.starlingx.io
When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."
Today's Topics:
1. Re: Starlingx-discuss Digest, Vol 62, Issue 38 (Jeremy Stanley)
2. Re: Community Communication Channels - VOTE NEEDED
(Cervi, Thales Elero)
----------------------------------------------------------------------
Message: 1
Date: Thu, 20 Jul 2023 12:32:29 +0000
From: Jeremy Stanley <fungi at yuggoth.org>
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62,
Issue 38
Message-ID: <20230720123228.fzrsixloayxl5hbf at yuggoth.org>
Content-Type: text/plain; charset="us-ascii"
On 2023-07-20 03:08:05 +0000 (+0000), Liu, David wrote:
> I'm working on submit some code for review, and the zuul gate job
> failed, but I can't download the detailed logs, is there a problem
> with The CI server side?
>
> My zuul job is here:
> https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af4
> 9299c/artifacts
[...]
I'm not sure what logs you think are missing, but the console log there shows that the pyflakes static analysis tool you're running encountered a fatal exception:
AttributeError: 'FlakesChecker' object has no attribute 'JOINEDSTR'
https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/log/job-output.txt#670
I'm able to reproduce this by checking out your change and running `tox -e pep8 -c distributedcloud-client/tox.ini` under python3.7, while running the same with a fresh checkout of the master branch completes successfully, so there's definitely something about
https://review.opendev.org/888424 which is triggering the problem.
A quick web search on the exact error string turns up this mailing list thread from 2019 about incompatibilities between the hacking plugin and (then) newer flake8/pyflakes versions:
https://lists.openstack.org/pipermail/openstack-discuss/2019-November/011027.html
My best guess, without digging deeper, is that something in the code being added in change 888424 is tickling the necessary code paths through pyflakes to hit the incompatibility with hacking. Indeed, editing distributedcloud-client/test-requirements.txt and bluntly replacing the hacking entry with just flake8 gets it to succeed, but of course this is only a reasonable solution if you don't care about the additional rules that module was enforcing.
--
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230720/8137522b/attachment-0001.sig>
------------------------------
Message: 2
Date: Thu, 20 Jul 2023 13:20:11 +0000
From: "Cervi, Thales Elero" <ThalesElero.Cervi at windriver.com>
To: Ildiko Vancsa <ildiko at openinfra.dev>, StarlingX ML
<starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Community Communication Channels -
VOTE NEEDED
Message-ID:
<CY8PR11MB703503D4AAB7E87382F62A11E83EA at CY8PR11MB7035.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
+1 for matrix
________________________________
From: Ildiko Vancsa <ildiko at openinfra.dev>
Sent: Wednesday, July 12, 2023 8:14 PM
To: StarlingX ML <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi,
Thank you all for the feedback so far!
I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it:
- As a reminder, you can find out more about the tool here: https://matrix.org
- There are different options to use as a browser or desktop client. Many of them are also available on smartphones.
+ I?m using Element - https://element.io
+ Some other options include
~ Weechat - https://github.com/poljar/weechat-matrix
~ SchildiChat - https://schildi.chat/
~ FluffyChat - https://fluffychat.im/
- The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org
~ You will need to create an account first
~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account
During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following:
- Have multiple chat rooms available for community communication:
+ starlingx-general room - topics that are relevant to the whole community
+ StarlingX project team channels
~ topics that are relevant to a project team
~ ie: starlingx-build, starlingx-containers, etc
+ Optional channel ideas - specific topic areas that are outside of the existing project teams
~ starlingx-newcomers
~ starlingx-troubleshooting
__ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__
Please let me know if you have any questions, or if you need help with setting up Matrix.
Best Regards,
Ildik?
???
Ildik? V?ncsa
Director of Community
Open Infrastructure Foundation
> On Jul 4, 2023, at 21:42, open infra <openinfradn at gmail.com> wrote:
>
> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord.
> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply).
>
>
>
>
>
> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa <ildiko at openinfra.dev> wrote:
> Hi StarlingX Community,
>
> I?m reaching out to you about a recurring topic that came up during the PTG last week again.
>
> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate.
>
> Challenges:
> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity.
> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about.
>
>
> Proposal to move forward:
> * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org
> - It is an open tool, which ensures continued access to the platform and its features
> - It is more modern than IRC
>
> * Format: The idea came up to create multiple channels for the StarlingX project
> - We can keep the all-community channel
> - We can create channels for each project team, that are more topic specific
> - We also have the option to create a channel for newcomers, which
> could include troubleshooting type of conversations as well
>
>
> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels?
>
> Thanks and Best Regards,
> Ildik?
>
> ???
>
> Ildik? V?ncsa
> Director of Community
> Open Infrastructure Foundation
>
>
>
>
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230720/e9cc9748/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
------------------------------
End of Starlingx-discuss Digest, Vol 62, Issue 41
*************************************************
More information about the Starlingx-discuss
mailing list