Re: Fastly Peering Contact

[Justin Wilson (Lists)]

We have sent them some inquiries in markets we are with no reply.  Just figured 
they weren’t interested.




Justin Wilson
j...@mtin.net
jus...@fd-ix.com
Https://www.fdi-ix.com

> On Dec 5, 2023, at 4:14 PM, Peter Potvin via NANOG  wrote:
> 
> Looking for someone on the Fastly peering team to reach out regarding peering 
> on a couple mutual IXPs - sent an email to the peering contact as listed on 
> PeeringDB and never heard back, and also have a few colleagues who have 
> experienced the same issue.
> 
> Regards,
> Peter Potvin | Executive Director
> --
> Accuris Technologies Ltd.
> 

Re: Let's test the list!

[mike wilson]

Neither inbox nor spam here.
> On 06/12/2023 12:40 GMT ann sanfedele  wrote:
> 
>  
> I replied but did not see my reply come up in my PDML inbox..  only in 
> my sent folder.
> Just made my usual wiseass Jokey reply.. did it get through?
> 
> I saw the email below of course and all the asnwer to it but mine
> I think my Thunderbird update may be responsible
> 
> ann
> 
> 
> On 12/5/2023 2:27 PM, Mark Roberts wrote:
> > Are the Server God's happy?
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: [go-cd] Repo Sync issues

[Chad Wilson]

Yeah, sorry, that artifact was probably unintentionally included in the
metadata. It'll be fixed in the next release when the metadata is corrected.

I'm not familiar with Foreman, but is it possible to filter out this
artifact (NessusAgent) with a content view or similar?

-Chad

On Wed, Dec 6, 2023 at 10:59 PM Miguel Santos  wrote:

> Hey guys,
>
> We would like to mirror your repository http://download.gocd.org, but
> your metadata file is pointing to files that do not have the correct
> permissions?
>
> We are trying to sync with Foreman http://download.gocd.org and the task
> fails because the first file you reference:
>
> http://linux.duke.edu/metadata/common; xmlns:rpm="
> http://linux.duke.edu/metadata/rpm; packages="161">
> 
>   NessusAgent
>   x86_64
>   
>pkgid="YES">e29737f08f303a268bcdb5f73dded015c7df9ba343a04182e4fd58665e764b47
>   Nessus Agent, supported by Tenable
>   The Nessus Client Agent
>   Renaud Deraison rderai...@tenablesecurity.com
> 
>   http://www.nessus.org
>   
>   
>   
>   
> Proprietary
> 
> Administration Tools
> ip-10-254-69-199.eu.build.aws.tenablesecurity.com
> 
> NessusAgent-10.1.0-amzn.src.rpm
> 
> 
>rel="amzn"/>
>ver="10.1.0" rel="amzn"/>
> 
> 
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
> /etc/rc.d/init.d/nessusagent
> /opt/nessus_agent/bin/nasl
> /opt/nessus_agent/sbin/nessus-service
> /opt/nessus_agent/sbin/nessuscli
> /opt/nessus_agent/sbin/nessusd
>   
> 
>
>
> Gives a 403: tenable-agents/NessusAgent-10.1.0-amzn.x86_64.rpm
> 403 Forbidden
>
>- Code: AccessDenied
>- Message: Access Denied
>- RequestId: 6QRJB3V4160FY9SK
>- HostId:
>
> dA5S81S4IDNE1Ek981rVMIRH3+sKqLPRMOcjLCB2igR3PrHV+4ZrIBMRgfQnmWWX2hX7NH74D/w=
>
>
> Can you help us sort this out or confirm if you do not allow the mirroring
> of your repository as policy?
>
> Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/f885e2f1-13eb-4d91-bf20-e45475b59ba0n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH-O8KvTNDgJsv1bghewZNk73t%2BbwCwX6B2Ui9bRufWdAA%40mail.gmail.com.

Re: Let's test the list!

[mike wilson]

Server Gods might be happy - the hard drive on my desktop definitely is not.  
Unless Loki has been out to play.
> On 05/12/2023 19:27 GMT Mark Roberts  wrote:
> 
>  
> Are the Server God's happy?
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Re: Ready for translation: Tech News #49 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 21 languages) to 1,098 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 49

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/49. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages:Bahasa Indonesia
, Deutsch
, Dusun Bundu-liwan
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - The spacing between paragraphs on Vector 2022 has been changed from
   7px to 14px to match the size of the text. This will make it easier to
   distinguish paragraphs from sentences. [1]
   
   - The "Sort this page by default as" feature in VisualEditor is working
   again. You no longer need to switch to source editing to edit
   {{DEFAULTSORT:...}} keywords. [2]
   

*Changes later this week*

   - There is no new MediaWiki version this week. [3]
   [4]
   
   - On 6 December, people who have the enabled the preference for "Show
   discussion activity" will notice the talk page usability improvements
   

   appear on pages that include the __NEWSECTIONLINK__ magic word. If you
   notice any issues, please share them with the team on Phabricator
   .

*Future changes*

   - The Toolforge Grid Engine shutdown process
   
   will start on December 14. Maintainers of tools that still use this old
   system  should plan to
   migrate to Kubernetes, or tell the team your plans on Phabricator in the
   task about your tool, before that date. [5]
   

   - Communities using Structured Discussions
   
   are being contacted regarding the upcoming deprecation of Structured
   Discussions
   
.
   You can read more about this project, and share your comments, on the
   project's page
   

   .

*Events*

   - Registration & Scholarship applications are now open for the Wikimedia
   Hackathon 2024
   
   that will take place from 3–5 May in Tallinn, Estonia. Scholarship
   applications are open until 5 January 2024.

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute

[African Wikimedians] [Rappel][Wiki Loves Africa] Dernier Appel pour les Ambassadeurs 2024

[Wilson Oluoha]

Chers Wikimédiens,


Nous vous remercions d'avoir répondu à l'appel à candidatures pour les
ambassadeurs linguistiques de Wiki Loves Africa. Nous sommes très
enthousiastes quant à la qualité des candidats jusqu'à présent.

Cet e-mail vous rappelle que la *date limite de dépôt des candidatures est
fixée au 4 Décembre*. N'oubliez pas de poser votre candidature si vous êtes
intéressé ou si vous connaissez quelqu'un qui le serait.

*Click to Apply
<https://docs.google.com/forms/d/e/1FAIpQLSfkhgoUb854R-z7cXhdRXd4ByUAuWdEzKEwk537dohrwIXUIg/viewform?usp=pp%20url>*

*Plus précisément, nous vous demandons de partager l'ouverture avec les
membres de la communauté portugaise ou toute personne ayant une
connaissance pratique du portugais et susceptible d'être intéressée.*


DATE LIMITE DE DÉPÔT DES CANDIDATURES : 4 Décembre 2023* – *minuit, partout
sur Terre.

Pour plus d'informations et le lien vers le formulaire de candidature,
cliquez ici : Wiki In Africa/Wiki Loves Africa/Ambassadors
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors>


Le meilleur,


Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Reminder][Wiki Loves Africa] Last Call For 2024 Ambassadors

[Wilson Oluoha]

Dear Wikimedians,


Thank you for your response so far to the call for Wiki Loves Africa
linguistic Ambassadors. We are super excited with the quality of candidates
thus far.

This email is to remind you that the deadline for applications is *today
4th December*. Just a quick reminder to apply if you are interested or know
someone who would be.

*Click to Apply
<https://docs.google.com/forms/d/e/1FAIpQLSfkhgoUb854R-z7cXhdRXd4ByUAuWdEzKEwk537dohrwIXUIg/viewform?usp=pp%20url>*

*Specifically, we wish to request that you share the opening with members
of the portuguese community or anyone who has working knowledge of
portuguese and would be interested.*


DEADLINE FOR APPLICATIONS : *4 December 2023 – midnight, everywhere on
Earth*

See more information and application link here : Wiki In Africa/Wiki Loves
Africa/Ambassadors
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors>


Best,


Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Seattle Area D-Meetup

[Adam Wilson via Digitalmars-d-announce]

Hello Everyone,

If you're going to be in the Seattle area over the holidays, 
Walter, Bruce C, and I will be hanging out at the Red Robin in 
Redmond on December 14th from 7PM until whenever they kick us 
out. Normally we would meet after NWCPP, but they are on a 
holiday break this month so we have the opportunity to rant and 
rage... I mean have collegial dialog with Walter for an extended 
period of time this month.


Address: 2390 148th Ave NE, Redmond, WA 98052

Re: Release D 2.106.0

[Adam Wilson via Digitalmars-d-announce]

On Saturday, 2 December 2023 at 18:09:11 UTC, Iain Buclaw wrote:

Glad to announce D 2.106.0, ♥ to the 33 contributors.

This release comes with...

- In the D language, it is now possible to statically 
initialize AAs.

- In dmd, there's a new `-nothrow` CLI flag.
- In dub, `dub init` now has a select menu for package format 
and license.


As always, you can find the release binaries and full changelog 
on the dlang.org site.


http://dlang.org/download.html
http://dlang.org/changelog/2.106.0.html

-Iain
on behalf of the Dlang Core Team


I'm excited about this release! The ImportC fixes alone are with 
the wait. And it's good to see the ODBC bindings restored. Up 
next: ODBC 4.0 in Phobos.

Re: [Servercert-wg] SC-065: Convert EVGs into RFC 3647 format pre-ballot

[Ben Wilson via Servercert-wg]

All,
See
https://github.com/BenWilson-Mozilla/pkipolicy/commit/1a94642cb95017cf382e4e93811db16a2342a806.
This proposed change was to clarify that the outline in section 6 of RFC
3647 is what is intended to be followed in CPs and CPSes, and not some
other outline found in RFC 3647.  Unfortunately, this change did not make
it into Mozilla Root Store Policy v. 2.9, but it is slated for inclusion in
version 3.0.
Thanks,
Ben

On Sat, Dec 2, 2023 at 3:26 AM Dimitris Zacharopoulos (HARICA) via
Servercert-wg  wrote:

> We still have a disagreement so please allow me one more attempt to
> clarify my position because it seems you didn't check the links included in
> my previous post. I will copy some of that text here for convenience.
>
> On 1/12/2023 11:31 μ.μ., Tim Hollebeek wrote:
>
> No.
>
>
>
> IETF has both Normative and Informative RFCs.  While it is true that
> compliance with a Normative RFC is voluntary, if you do choose to comply,
> the RFC has requirements stated in RFC 2119 standards language that make it
> clear what the compliance rules are.  Informative RFCs like 3647 do not
> have any normative requirements at all.  They merely contain information.
>
>
>
> “all sections of the RFC 3647 framework” is fine, this covers the sections
> enumerated in RFC 3647 section 4, which includes the TOP TWO levels of an
> outline in numbered form, e.g. the requirements for section 3.2 are
> described in RFC 3647 section 4.3.2.  There is no RFC 3647 section 4.3.2.1,
> which proves my point.  RFC 3647 only has a two level outline structure.
>
>
> I think I might have a hint on our disconnect. RFC 3647 has an indicative
> Table of Contents in Chapter 6 (
> https://datatracker.ietf.org/doc/html/rfc3647#section-6) outlining the
> proposed CP/CPS sections and subsections using 3 levels.
>
> Here is the text of the opening paragraph of that section (emphasis added):
>
>This section contains a recommended outline for a set of provisions,
>intended to serve as a checklist or (with some further development) a
>standard template for use by CP or CPS writers.  Such a common
>outline will facilitate:
>
>(a) Comparison of two certificate policies during cross-
>certification or other forms of interoperation (for the purpose
>of equivalency mapping).
>
>(b) Comparison of a CPS with a CP to ensure that the CPS faithfully
>implements the policy.
>
>(c) Comparison of two CPSs.
> *   In order to comply with the RFC, the drafters of a compliant CP or
>CPS are strongly advised to adhere to this outline.*  While use of an
>alternate outline is discouraged, it may be accepted if a proper
>justification is provided for the deviation and a mapping table is
>provided to readily discern where each of the items described in this
>outline is provided.
>
>
> The reason the CA/B Forum BRs were structured according to this outline
> was to assist with comparisons between CP/CPS documents of different CAs,
> making the review of these documents easier.
>
> That's why you see sections like 1.5.4 "CPS approval procedures" in the
> BRs as an empty section with "No Stipulation". There are many such sections
> in the BRs, all coming from section 6 of RFC 3647.
>
> I hope this is clearer now.
>
>
>
> BR Section 2.2 needs to be re-written, as there are no materials required
> by RFC 3647 (because RFC 3647 contains no requirements).  It needs to say
> something like “structured in accordance with RFC 3647 and MUST include all
> sections of the outline described in section 4” or something like that.
> What it says right now doesn’t capture the intent that you correctly
> summarized.
>
>
> During the last couple of years reviewing CP/CPS documents, I saw some
> uniformity at least in Publicly Trusted CAs, and they all seem to follow
> the BRs structure which comes from the outline of section 6 of RFC 3647.
> However, it's not a bad idea to further clarify BR section 2.2 to better
> meet the expectations.
>
>
>
> The MSRP language is better, I think I may have made all of these same
> points when it was being drafted, which is why it says “section and
> subsection” (two levels) and uses “structured according to” and not
> “complies with the requirements of”.
>
>
>
> But anyway, this is all background that supports what I’ve been saying all
> along: BR 3.2 is a RFC 3647 section.  BR 3.2.1 **is not** a RFC 3647
> required section, nor is it even a section that is even mentioned in RFC
> 3647.  If you don’t believe me, please go to RFC 3647, Section 4.3.2.1 and
> read what it says.  OH, WAIT, IT DOESN’T EXIST! 
>
>
> To my point, BR 3.2.1 IS an RFC 3647 required section as it is explicitly
> mentioned in the outline of section 6 of RFC 3647:
>
> 3.2.1  Method to prove possession of private key
>
>
> Details about the contents of that section can be found in the first
> bullet of section 4.3.2 of RFC 3647
> .
>
> Does that make 

[Translators-l] Re: Ready for translation: Tech News #49 (2023)

[Nick Wilson (Quiddity)]

On Thu, Nov 30, 2023 at 3:28 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/49
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F49=page
>

The text of the newsletter is now final.

*Two items have been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Translators-l] Ready for translation: Tech News #49 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/49

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F49=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[African Wikimedians] Wiki Loves Africa 2024 - Precisamos da vossa ajuda!

[Wilson Oluoha]

Dear Friends,

Wiki Loves Africa recently announced a call for linguistic Ambassadors. *Thank
you for the swift response so far. *

This email is to request specifically for *Portuguese speaking Africans* to
also consider applying for the role of Portuguese Language Ambassadors with
Wiki Loves Africa.

*Click to Apply
<https://docs.google.com/forms/d/e/1FAIpQLSfkhgoUb854R-z7cXhdRXd4ByUAuWdEzKEwk537dohrwIXUIg/viewform?usp=pp%20url>*

We request your kind assistance in helping transmit this message to
colleagues and friends in the Portuguese speaking communities.

Many thanks

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: [cabfpub] Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter - VOTING PERIOD

[Clint Wilson via Public]

Apple votes YES on Ballot FORUM-019 v.2

> On Nov 27, 2023, at 7:44 AM, Ben Wilson via Public  
> wrote:
> 
> The voting period for Ballot FORUM-019 v.2 starts today. Votes must be cast 
> on the Forum public list in accordance with the Forum's Bylaws.  Voting will 
> conclude at 16:00 UTC on 4 December 2023.
> 
> Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter
> 
> Purpose of Ballot
> 
> This ballot proposes to amend the Server Certificate Working Group (SCWG) 
> Charter, based on existing version 1.2 of the Charter and on recent updates 
> to the Forum’s Bylaws.
> 
> During discussions at Face-to-Face Meeting 58, it was noted that the 
> membership criteria for Certificate Consumers in the SCWG Charter lacked 
> sufficient detail. Since then, through discussions on the mailing list of the 
> SCWG and elsewhere, better criteria for membership of Certificate Consumers 
> in the SCWG have been developed, and the ballot also adds a 6-month 
> probationary period for all applicants to the SCWG before they become voting 
> members.
> 
> Additionally, section numbering has been added, the outdated "Root 
> Certificate Issuer" voting category has been removed, and provisions 
> regarding voting percentages and quorum have been clarified.
> 
> The following motion has been proposed by Ben Wilson of Mozilla and endorsed 
> by Martijn Katerbarg of Sectigo and Dimitris Zacharopoulos of HARICA.
> 
> 
> 
> - Motion Begins -
> 
> MODIFY the Charter of the Server Certificate Working Group as specified in 
> the following redline:
> 
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...3af42d2d9e38a0dfcdf9450d5ca772365d5b5dbb
> 
> 
> 
> 
> 
> - Motion Ends -
> 
> 
> 
> This ballot does not propose a Final Guideline or Final Maintenance 
> Guideline. 
> 
> The procedure for approval of this ballot is as follows:
> 
> Discussion Period (7+ days)
> 
> Start Time: 2023-11-16  23:00 UTC
> 
> End Time: Not before 2023-11-23  23:00 UTC
> 
>  
> Vote for approval (7 days)
> 
> Start Time: 2023-11-27  16:00 UTC
> 
> End Time:  2023-12-04  16:00 UTC
> 
> ___
> Public mailing list
> Public@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/public



smime.p7s
Description: S/MIME cryptographic signature
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

Re: Rock 'n Roll, Rush and Pentax

[mike wilson]

Rock'n'roll r us!  (Makes devil's horn sign with fingers and hangs tongue down 
chin without really knowing why)
> On 30/11/2023 00:27 GMT Postmaster  wrote:
> 
>  
> Around the 1:24 :-)
> 
> https://www.youtube.com/watch?v=OIAcVSSHJgc
> 
>
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: PESO Another Cobra Pic

[mike wilson]

Much better than the usual steroidal, lumpen mess.  Perfect focus on the badge, 
with (coincidentally?) nice, sharp, tyre treads.  Smooth, uncluttered 
background.  We have come to expect nothing less...

> On 29/11/2023 14:28 GMT paul stenquist  wrote:
> 
>  
> Another pic from last week’s shoot of a genuine ’64 Cobra. This car is 
> numbers matching and unmolested. It was never raced and has only had two 
> owners. It’s among the world’s best examples of a Mark II Cobra. K-1 with D 
> FA 150-450, f5.6, 300mm
> 
> https://www.dropbox.com/scl/fi/myonlwtx6jrspwo7wft7c/cobra8.jpg?rlkey=wruirumzc2t613qw4qo2x17pt=0
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: [nysbirds-l] Little Blue Heron?

[Jennifer Wilson-Pines]

It's possible. It's a hard area to access, mostly viewed from across the
back of the harbor.

Jennifer Wilson Pines

On Wed, Nov 29, 2023 at 10:19 AM Francisco Rodríguez <
franciscojrodrig...@gmail.com> wrote:

> Hi,
>
> I think this list includes Long Island, if not please disregard.
>
> What did I see?
>
> I was driving this morning on 25A by the Roslyn bridge, which is a tall
> bridge over land and the beginning of the marshes of that bay and this bird
> was going up very vertically from the marshes, to get a little higher than
> I was on the side of the bridge. Perspective could be deceiving and I had
> only few seconds to see it but it was small-ish, blue-ish (dark), with
> pretty decent pace flapping going upwards and it totally looked like a
> Little Blue Heron. Only that it is pretty late for them to stay around,
> right?
>
> I have never seen a Great Blue Heron flap fast like that. That doesn't
> mean that they can't. I just haven't seen it. I am sure that there are
> plenty of Great Blue Herons in that area currently. But it "looked" more
> dark blue and smaller.
>
> So, if anybody birds in that area, I would like to hear what it could have
> been...
>
> Thanks,
>
> Regards
> Fran
> --
> *NYSbirds-L List Info:*
> Welcome and Basics <http://www.northeastbirding.com/NYSbirdsWELCOME.htm>
> Rules and Information <http://www.northeastbirding.com/NYSbirdsRULES.htm>
> Subscribe, Configuration and Leave
> <http://www.northeastbirding.com/NYSbirdsSubscribeConfigurationLeave.htm>
> *Archives:*
> The Mail Archive
> <http://www.mail-archive.com/nysbirds-l@cornell.edu/maillist.html>
> Surfbirds <http://www.surfbirds.com/birdingmail/Group/NYSBirds-L>
> ABA <http://birding.aba.org/maillist/NY01>
> *Please submit your observations to **eBird*
> <http://ebird.org/content/ebird/>*!*
> --
>


-- 
Jennifer Wilson-Pines

--

(copy & paste any URL below, then modify any text "_DOT_" to a period ".")

NYSbirds-L List Info:
NortheastBirding_DOT_com/NYSbirdsWELCOME_DOT_htm
NortheastBirding_DOT_com/NYSbirdsRULES_DOT_htm
NortheastBirding_DOT_com/NYSbirdsSubscribeConfigurationLeave_DOT_htm

ARCHIVES:
1) mail-archive_DOT_com/nysbirds-l@cornell_DOT_edu/maillist_DOT_html
2) surfbirds_DOT_com/birdingmail/Group/NYSBirds-L
3) birding_DOT_aba_DOT_org/maillist/NY01

Please submit your observations to eBird:
ebird_DOT_org/content/ebird/

--

[Translators-l] Re: Ready for translation: Tech News #48 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 21 languages) to 1,096 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 48

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/48. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, Ελληνικά
, русский
, עברית
, العربية
, हिन्दी
, বাংলা
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 28 November. It
   will be on non-Wikipedia wikis and some Wikipedias from 29 November. It
   will be on all wikis from 30 November (calendar
   ). There is no
   new MediaWiki version next week. [1]
   [2]
   
   - MediaWiki's JavaScript system will now allow async/await syntax in
   gadgets and user scripts. Gadget authors should remember that users'
   browsers may not support it, so it should be used appropriately. [3]
   
   - The deployment of "Add a link
   
"
   announced last week
   
   was postponed. It will resume this week.

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

[grpc-io] Grpc Java server test for ServerInterceptors

[John Wilson]

Hi Grpc team! 
I have a ServerInterceptor instance for my grpc server, it does something 
like this:

@Override
public  ServerCall.Listener interceptCall(
ServerCall call, Metadata headers, 
ServerCallHandler next) {
Context context = Context.current();
 // more code here 
context = context.withValue(USER_ID, "my-user-id");
return Contexts.interceptCall(context, call, headers, next);
}

and in my service method I get access to the userId using smth like this:

USER_ID.get()


I have some questions:
Is this implementation correct?
Is this thread safe?
Is there any way to test that implementation?
Is there any documentation that I can check to understand how Threads are 
handled by the grpc server?

Thanks in advance! :) 

Edu-

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/3ad6e782-f38d-4e69-9d94-d39674faeca0n%40googlegroups.com.

[grpc-io] Grpc Java server test for ServerInterceptors

[John Wilson]

  Hi Grpc team! 
I have a ServerInterceptor instance for my grpc server, it does something 
like this:

@Override
public  ServerCall.Listener interceptCall(
ServerCall call, Metadata headers, 
ServerCallHandler next) {
Context context = Context.current();
 // more code here 
context = context.withValue(USER_ID, "my-user-id");
return Contexts.interceptCall(context, call, headers, next);
}

and in my service method I get access to the userId using smth like this:

USER_ID.get()


I have some questions:
Is this implementation correct?
Is this thread safe?
Is there any way to test that implementation?
Is there any documentation that I can check to understand how Threads are 
handled by the grpc server?

Thanks in advance! :) 

Edu-

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/dd20dd3f-a743-4a1d-b9d6-a86d01028a32n%40googlegroups.com.

[grpc-io] c-ares and CVE-2022-4904 in gRPC C# v1.46.x

[John Wilson]

Hi gRPC Team!

I see the C# version in maintenance mode (v1.46.x) uses version 1.17.2, 
which is impacted by CVE-2022-4904 (fixed in version 1.19).
Are there plans to upgrade the version included in gRPC? Or is it not 
impacted by the c-ares vulnerability?

- sebas

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/67438bdc-61d6-47a0-be56-85be7aca8b2dn%40googlegroups.com.

[grpc-io] c-ares and CVE-2022-4904 in gRPC C# v1.46.x

[John Wilson]

Hi gRPC Team!

I see the C# version in maintenance mode (v1.46.x) uses version 1.17.2, 
which is impacted by CVE-2022-4904 (fixed in version 1.19).
Are there plans to upgrade the version included in gRPC? Or is it not 
impacted by the c-ares vulnerability?

- sebas

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/1b7745c5-2fed-4052-aacb-b0d661af28e4n%40googlegroups.com.

Re: [cabfpub] Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter - VOTING PERIOD

[Ben Wilson via Public]

Mozilla votes "yes" on Ballot FORUM-019 v.2.

On Mon, Nov 27, 2023 at 8:44 AM Ben Wilson via Public 
wrote:

> The voting period for Ballot FORUM-019 v.2 starts today. Votes must be
> cast on the Forum public list in accordance with the Forum's Bylaws.
> Voting will conclude at 16:00 UTC on 4 December 2023.
>
> *Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter*
>
> *Purpose of Ballot*
>
> This ballot proposes to amend the Server Certificate Working Group (SCWG)
> Charter, based on existing version 1.2 of the Charter and on recent updates
> to the Forum’s Bylaws.
>
> During discussions at Face-to-Face Meeting 58, it was noted that the
> membership criteria for Certificate Consumers in the SCWG Charter lacked
> sufficient detail. Since then, through discussions on the mailing list of
> the SCWG and elsewhere, better criteria for membership of Certificate
> Consumers in the SCWG have been developed, and the ballot also adds a
> 6-month probationary period for all applicants to the SCWG before they
> become voting members.
>
> Additionally, section numbering has been added, the outdated "Root
> Certificate Issuer" voting category has been removed, and provisions
> regarding voting percentages and quorum have been clarified.
>
> The following motion has been proposed by Ben Wilson of Mozilla and
> endorsed by Martijn Katerbarg of Sectigo and Dimitris Zacharopoulos of
> HARICA.
>
>
>
> *- Motion Begins -*
>
> MODIFY the Charter of the Server Certificate Working Group as specified in
> the following redline:
>
>
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...3af42d2d9e38a0dfcdf9450d5ca772365d5b5dbb
>
>
> *- Motion Ends -*
>
>
> This ballot does not propose a Final Guideline or Final Maintenance
> Guideline.
>
> The procedure for approval of this ballot is as follows:
>
> Discussion Period (7+ days)
>
> Start Time: 2023-11-16  23:00 UTC
>
> End Time: Not before 2023-11-23  23:00 UTC
>
>
>
> Vote for approval (7 days)
>
> Start Time: 2023-11-27  16:00 UTC
>
> End Time:  2023-12-04  16:00 UTC
> ___
> Public mailing list
> Public@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/public
>
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

Re: [Infrastructure] WordPress Instructions

[Ben Wilson via Infrastructure]

Thanks.
I have added more instructions for posting meeting minutes, although I
might not have captured all that you envisioned regarding which tags to
use.  It might be good to add sub-sections specific to each Working Group.
Ben

On Mon, Nov 27, 2023 at 9:00 AM Inigo Barreira via Infrastructure <
infrastructure@cabforum.org> wrote:

> +1. I think that list would be a good adding.
>
> -Mensaje original-
> De: Infrastructure  En nombre de
> Dimitris Zacharopoulos (HARICA) via Infrastructure
> Enviado el: lunes, 27 de noviembre de 2023 11:59
> Para: infrastructure@cabforum.org
> Asunto: Re: [Infrastructure] WordPress Instructions
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Ben, thank you for working on those instructions,
>
> Except for the tags you have indicated, should we perhaps have a listing
> of the exact tags that should be used on each occasion? For example, when
> publishing minutes, there may be tasks to distinguish if the minutes are
> for a Teleconference or a Physical (F2F) Meeting.
>
>
> Thanks,
> Dimitris.
>
> On 8/11/2023 11:57 μ.μ., Ben Wilson via Infrastructure wrote:
> > Today I started to edit the WordPress instructions for the website and
> > bring them up to date. (They're quite out-of-date.) I have provided a
> > link to them on the wiki -
> >
> https://wiki.cabforum.org/books/infrastructure/page/wordpress-instructions
> .
> > If you'd like to help me edit them and need "edit" access, then please
> > let me know.
> > Thanks,
> > Ben
> >
> > ___
> > Infrastructure mailing list
> > Infrastructure@cabforum.org
> > https://list/
> > s.cabforum.org%2Fmailman%2Flistinfo%2Finfrastructure=05%7C01%7Cin
> > igo.barreira%40sectigo.com%7Cf7f52e76a8174abb9df708dbef37e87c%7C0e9c48
> > 946caa465d96604b6968b49fb7%7C0%7C0%7C638366795630643042%7CUnknown%7CTW
> > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> > Mn0%3D%7C3000%7C%7C%7C=3c8iDFBeFZI%2FoQfYbm5BEz6LqCQUfF0rnT1oids
> > 6WnE%3D=0
>
> ___
> Infrastructure mailing list
> Infrastructure@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/infrastructure
> ___
> Infrastructure mailing list
> Infrastructure@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/infrastructure
>
___
Infrastructure mailing list
Infrastructure@cabforum.org
https://lists.cabforum.org/mailman/listinfo/infrastructure

[cabfpub] Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter - VOTING PERIOD

[Ben Wilson via Public]

 The voting period for Ballot FORUM-019 v.2 starts today. Votes must be
cast on the Forum public list in accordance with the Forum's Bylaws.
Voting will conclude at 16:00 UTC on 4 December 2023.

*Ballot FORUM-019 v.2 - Amend Server Certificate Working Group Charter*

*Purpose of Ballot*

This ballot proposes to amend the Server Certificate Working Group (SCWG)
Charter, based on existing version 1.2 of the Charter and on recent updates
to the Forum’s Bylaws.

During discussions at Face-to-Face Meeting 58, it was noted that the
membership criteria for Certificate Consumers in the SCWG Charter lacked
sufficient detail. Since then, through discussions on the mailing list of
the SCWG and elsewhere, better criteria for membership of Certificate
Consumers in the SCWG have been developed, and the ballot also adds a
6-month probationary period for all applicants to the SCWG before they
become voting members.

Additionally, section numbering has been added, the outdated "Root
Certificate Issuer" voting category has been removed, and provisions
regarding voting percentages and quorum have been clarified.

The following motion has been proposed by Ben Wilson of Mozilla and
endorsed by Martijn Katerbarg of Sectigo and Dimitris Zacharopoulos of
HARICA.



*- Motion Begins -*

MODIFY the Charter of the Server Certificate Working Group as specified in
the following redline:

https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...3af42d2d9e38a0dfcdf9450d5ca772365d5b5dbb


*- Motion Ends -*


This ballot does not propose a Final Guideline or Final Maintenance
Guideline.

The procedure for approval of this ballot is as follows:

Discussion Period (7+ days)

Start Time: 2023-11-16  23:00 UTC

End Time: Not before 2023-11-23  23:00 UTC



Vote for approval (7 days)

Start Time: 2023-11-27  16:00 UTC

End Time:  2023-12-04  16:00 UTC
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

[nysbirds-l] Shinnecock Inlet (Suffolk Co.) Black Guillemot found dead

[Angus Wilson]

Quick heads up for those thinking about traveling out. According to Adam
Kohler's eBird checklist from this morning, the guillemot has joined the
Choir Invisible.

https://ebird.org/checklist/S155247693

-- 
Angus Wilson

--

(copy & paste any URL below, then modify any text "_DOT_" to a period ".")

NYSbirds-L List Info:
NortheastBirding_DOT_com/NYSbirdsWELCOME_DOT_htm
NortheastBirding_DOT_com/NYSbirdsRULES_DOT_htm
NortheastBirding_DOT_com/NYSbirdsSubscribeConfigurationLeave_DOT_htm

ARCHIVES:
1) mail-archive_DOT_com/nysbirds-l@cornell_DOT_edu/maillist_DOT_html
2) surfbirds_DOT_com/birdingmail/Group/NYSBirds-L
3) birding_DOT_aba_DOT_org/maillist/NY01

Please submit your observations to eBird:
ebird_DOT_org/content/ebird/

--

[Translators-l] Re: Ready for translation: Tech News #48 (2023)

[Nick Wilson (Quiddity)]

On Thu, Nov 23, 2023 at 2:11 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/48
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F48=page
>

The text of the newsletter is now final.

*One item has been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] Call For 2024 Ambassadors

[Wilson Oluoha]

Dear Wikimedians,

We are looking for 4 individuals to become Wiki Loves Africa Linguistic
Ambassadors to heighten awareness of, support during, and participation in
the Wiki Loves Africa contest and related activities. The ambassadors will
assist the international organizing team to manage and coordinate the
project throughout 2024 and will be distributed in linguistic categories
thus:

   - *French*
   - *Portuguese*
   - *English*
   - *Arabic*


DEADLINE FOR APPLICATIONS : *4 December 2023 – midnight, everywhere on
Earth*

See more information and application link here : Wiki In Africa/Wiki Loves
Africa/Ambassadors
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors>


Best,


Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] Appel à candidatures pour les ambassadeurs 2024

[Wilson Oluoha]

Chers Wikimédiens,

Nous recherchons 4 personnes pour devenir ambassadeurs linguistiques de
Wiki Loves Africa afin d'accroître la sensibilisation, le soutien et la
participation au concours Wiki Loves Africa et aux activités connexes. Les
ambassadeurs aideront l'équipe organisatrice internationale à gérer et à
coordonner le projet tout au long de l'année 2024 et seront répartis dans
les catégories linguistiques suivantes:

   - *Français*
   - *portugais (en anglais)*
   - *Anglais*
   - *Arabe*

DATE LIMITE DE DÉPÔT DES CANDIDATURES : *4 décembre 2023 - minuit, partout
sur Terre*

Pour plus d'informations et le lien vers le formulaire de candidature,
cliquez ici:
Wiki In Africa/Wiki Loves Africa/Ambassadors
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors>

Bonne chance,

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[Python-modules-team] Dugan’s: Quick time this afternoon?

[Danny Wilson]

Hello,

Thought to let you know that this month we helped your State business with
3 employees cut $346/yr from their telecom bill by switching them to an
award-winning VoIP provider. Open to see if we can help Dugan’s reduce
cut its phone bill also?

This is a full-service VoIP system that offers SMS, video, auto-attendant &
more.

If this sounds good, simply reply to this email letting me know a good
number to briefly connect (and number of users on your phone system).
Someone will then get in touch to start you on a quick/easy quote.


Excited to hear from you,

Danny Wilson
Partnership and Marketing Assistant
Ponial
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Translators-l] Ready for translation: Tech News #48 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/48

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F48=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [go-cd] Re: GOCD Email server configuration

[Chad Wilson]

Do you have the SMTPS setting enabled? IIRC needs to be enabled for port
465 on Gmail but something might have changed.

And which GoCD version (if you have tried both and they don't work on port
465)

On Thu, 23 Nov 2023, 14:40 Vijayakumaran A., <
vijayakumara...@praniontech.com> wrote:

> HI PFA,
>
> jvm 1| 2023-11-23 06:39:41,213 ERROR [Thread-2818] GoSmtpMailSender:63
> - Sending failed for email [Go Email Notification] to [u...@gmail.com]
> jvm 1| jakarta.mail.MessagingException: Got bad greeting from SMTP
> host: smtp.gmail.com, port: 465, response: [EOF]
> jvm 1|  at
> org.eclipse.angus.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2231)
> jvm 1|  at
> org.eclipse.angus.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:729)
> jvm 1|  at jakarta.mail.Service.connect(Service.java:345)
> jvm 1|  at
> com.thoughtworks.go.config.GoSmtpMailSender.send(GoSmtpMailSender.java:58)
> jvm 1|  at
> com.thoughtworks.go.config.BackgroundMailSender.lambda$send$0(BackgroundMailSender.java:44)
> jvm 1|  at java.base/java.lang.Thread.run(Unknown Source)
>
> On Thursday, November 23, 2023 at 11:30:29 AM UTC+5:30
> ashwant...@gmail.com wrote:
>
>> Can you please share the relevant gocd-server logs that would likely have
>> more information which is useful for debugging.
>>
>> Thanks,
>>
>> On Thu, 23 Nov 2023 at 11:25, Vijayakumaran A. <
>> vijayak...@praniontech.com> wrote:
>>
>>> ps:Before 2 month back im used the same that time its works that was
>>> installed by apt ubuntu package.Now we are using GOCD by docker.
>>>
>>> On Thursday, November 23, 2023 at 11:17:14 AM UTC+5:30 Vijayakumaran A.
>>> wrote:
>>>
 Team,I was setting up an email server configuration with my smtp server
 credentials but its throw error.my credentials are correct. Why am I having
 this error ?

 There was an unknown error performing the operation. Possible reason
 (Not Acceptable)




 --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+un...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/5d47e887-8e96-45c0-8e0f-0ab02706278an%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Ashwanth Kumar / ashwanthkumar.in
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/1ee6c52b-b972-4918-b501-dde6f60bb41en%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH-z4n-9yxa9t9%3DrTArZikzbtBw4Jpqf8OKfMFHQ_UiH5A%40mail.gmail.com.

Re: Another replicated cache oddity

[Raymond Wilson]

gt; in case this is a corner case that doesn't justify a consistency-maximized
> cache setup.
>
> It's entirely possible your cache system is only set up to provide "best
> effort" consistency, while your compute tasks need more. At GridGain, this
> is often felt by our commercial clients when their clusters accrete new
> workloads that were not a part of the original design. I've only been with
> GridGain a short while, but I've heard this question raised more than once,
> and the tradeoffs and consistency design is well documented, so my guess is
> that's popular subject matter for similar reasons to your experience.
>
> Are there any signs of strain in any of the Ignite servers' monitoring
> metrics when these events happen? What kind of accumulated workload is on
> the cluster at those times, and how often does this happen?
>
>
> On Wed, Nov 22, 2023 at 1:50 PM Raymond Wilson 
> wrote:
>
>> Hi Jeremy,
>>
>> My initial query was to see if this had been observed by others.
>>
>> To answer some of your questions:
>>
>> Do we specifically check that an element is added to all nodes
>> participating in a replicated cache: No, we do not (we take it on trust
>> Ignite sorts that out ;) )
>>
>> Do we think it is a race condition? No, for three reasons: (1) The grid
>> was restarted in the interval between initial addition of the element and
>> the time the three nodes were failing to perform the Get(), (2) This
>> particular element failed on the same three nodes over many invocations of
>> the request over a substantial time period and (3) a subsequent grid
>> restart fixed the problem.
>>
>> From our logs we don't see delays, timeouts or Ignite logged errors
>> relating to the Get().
>>
>> In terms of troubleshooting this has been a bit tricky. In this instance
>> only this one element (of many thousands of similar elements with similar
>> cluster compute requests being made across them) failed. And only within
>> the duration between a pair of grid restarts.
>>
>> The replicated cache update is just a simple ICache.PutAsync() with
>> a key struct and a byte[] array as payload. In terms of the distributed
>> compute code it is just performing a simple ICache.GetAsync() with
>> the key struct.
>>
>> So far it seems like the three failing nodes just temporarily 'forgot'
>> they had this element, and remembered it again after the restart.
>>
>> For context, this is the first time we have seen this specific issue on a
>> system that has been running in production for 2+ years now. We have seen
>> numerous instances with replicated caches where Ignite has (permanently)
>> failed to write at least one, but not all, copies of the element where grid
>> restarts do not correct the issue. This does not feel the same though.
>>
>> Raymond.
>>
>>
>>
>>
>>
>> On Thu, Nov 23, 2023 at 6:50 AM Jeremy McMillan <
>> jeremy.mcmil...@gridgain.com> wrote:
>>
>>> I suspect a race condition with async mode caches. This is a naive guess
>>> though, as we don't have enough details. I'll assume this is a plea for
>>> help in troubleshooting methodology and the question is really "what should
>>> we look at next?"
>>>
>>> The real answer comes from tracing the insert of element E and
>>> subsequent cache get() failures. Do we know if E was completely inserted
>>> into each replicated cache backup partition prior to the get()? Do we know
>>> if the reported cache get() failure was actually a fully functioning cache
>>> lookup and retrieval that failed during lookup, or were there timeouts or
>>> exceptions indicating something abnormal was happening?
>>>
>>> What steps did you take to troubleshoot this issue, and what is the
>>> cluster and cache configuration in play? What does the code look like for
>>> the updates to the replicated cache, and what does the code look like for
>>> the distributed compute operation?
>>>
>>> On Tue, Nov 21, 2023 at 5:21 PM Raymond Wilson <
>>> raymond_wil...@trimble.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have been triaging an odd issue we encountered in a system using
>>>> Ignite v2.15 and the C# client.
>>>>
>>>> We have a replicated cache across four nodes, lets call them P0, P1, P2
>>>> & P3. Because the cache is replicated every item added to the cache is
>>>> present in each of P0, P1, P2 and P3.
>>>>
>>>> Some time ago an element (E) w

Re: Another replicated cache oddity

[Raymond Wilson]

Hi Jeremy,

My initial query was to see if this had been observed by others.

To answer some of your questions:

Do we specifically check that an element is added to all nodes
participating in a replicated cache: No, we do not (we take it on trust
Ignite sorts that out ;) )

Do we think it is a race condition? No, for three reasons: (1) The grid was
restarted in the interval between initial addition of the element and the
time the three nodes were failing to perform the Get(), (2) This particular
element failed on the same three nodes over many invocations of the request
over a substantial time period and (3) a subsequent grid restart fixed
the problem.

>From our logs we don't see delays, timeouts or Ignite logged errors
relating to the Get().

In terms of troubleshooting this has been a bit tricky. In this instance
only this one element (of many thousands of similar elements with similar
cluster compute requests being made across them) failed. And only within
the duration between a pair of grid restarts.

The replicated cache update is just a simple ICache.PutAsync() with a
key struct and a byte[] array as payload. In terms of the distributed
compute code it is just performing a simple ICache.GetAsync() with
the key struct.

So far it seems like the three failing nodes just temporarily 'forgot' they
had this element, and remembered it again after the restart.

For context, this is the first time we have seen this specific issue on a
system that has been running in production for 2+ years now. We have seen
numerous instances with replicated caches where Ignite has (permanently)
failed to write at least one, but not all, copies of the element where grid
restarts do not correct the issue. This does not feel the same though.

Raymond.





On Thu, Nov 23, 2023 at 6:50 AM Jeremy McMillan <
jeremy.mcmil...@gridgain.com> wrote:

> I suspect a race condition with async mode caches. This is a naive guess
> though, as we don't have enough details. I'll assume this is a plea for
> help in troubleshooting methodology and the question is really "what should
> we look at next?"
>
> The real answer comes from tracing the insert of element E and subsequent
> cache get() failures. Do we know if E was completely inserted into each
> replicated cache backup partition prior to the get()? Do we know if the
> reported cache get() failure was actually a fully functioning cache lookup
> and retrieval that failed during lookup, or were there timeouts or
> exceptions indicating something abnormal was happening?
>
> What steps did you take to troubleshoot this issue, and what is the
> cluster and cache configuration in play? What does the code look like for
> the updates to the replicated cache, and what does the code look like for
> the distributed compute operation?
>
> On Tue, Nov 21, 2023 at 5:21 PM Raymond Wilson 
> wrote:
>
>> Hi,
>>
>> We have been triaging an odd issue we encountered in a system using
>> Ignite v2.15 and the C# client.
>>
>> We have a replicated cache across four nodes, lets call them P0, P1, P2 &
>> P3. Because the cache is replicated every item added to the cache is
>> present in each of P0, P1, P2 and P3.
>>
>> Some time ago an element (E) was added to this cache (among many others).
>> A number of system restarts have occurred since that time.
>>
>> We started observing an issue where a query running across P0/P1/P2/P3 as
>> a cluster compute operation needed to load element E on each of the nodes
>> to perform that query. Node P0 succeeded, while nodes P1, P2 & P3 all
>> reported that element E did not exist.
>>
>> This situation persisted until the cluster was restarted, after which the
>> same query that had been failing now succeeded as all four 'P' nodes were
>> able to read element E.
>>
>> There were no Ignite errors reported in the context of these
>> failing queries to indicate unhappiness in the Ignite nodes.
>>
>> This seems like very strange behaviour. Are there any suggestions as to
>> what could be causing this failure to read the replicated value on the
>> three failing nodes, especially as the element 'came back' after a cluster
>> restart?
>>
>> Thanks,
>> Raymond.
>>
>>
>>
>>
>> --
>> <http://www.trimble.com/>
>> Raymond Wilson
>> Trimble Distinguished Engineer, Civil Construction Software (CCS)
>> 11 Birmingham Drive | Christchurch, New Zealand
>> raymond_wil...@trimble.com
>>
>>
>> <https://worksos.trimble.com/?utm_source=Trimble_medium=emailsign_campaign=Launch>
>>
>

-- 
<http://www.trimble.com/>
Raymond Wilson
Trimble Distinguished Engineer, Civil Construction Software (CCS)
11 Birmingham Drive | Christchurch, New Zealand
raymond_wil...@trimble.com

<https://worksos.trimble.com/?utm_source=Trimble_medium=emailsign_campaign=Launch>

Re: Improvements to Vulnerability Disclosure wiki page

[Ben Wilson]

All,
For your review and comment, today I reorganized the security incident and
vulnerability disclosure report's expected contents
<https://wiki.mozilla.org/CA/Vulnerability_Disclosure#Reportable_Vulnerability.2FIncident_Disclosure_Contents>
and added a markdown template
<https://wiki.mozilla.org/CA/Vulnerability_Disclosure#Markdown_Template>
that can be used in Bugzilla.
Ben

On Wed, Sep 27, 2023 at 11:47 AM Ben Wilson  wrote:

> All,
> As mentioned in a previous email, I am soliciting feedback regarding the 
> Vulnerability
> Disclosure wiki page
> <https://wiki.mozilla.org/CA/Vulnerability_Disclosure>. If you have any
> specific suggestions that we can use to enhance clarity or to make the page
> more complete, please don't hesitate to share them, either here or directly
> with me. Your feedback is instrumental in our commitment to maintain a safe
> and secure online environment.
> Thanks,
> Ben
>

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabbqDu6N7yPnU9uL0RZQXPiMquHh-1FxTmPbQSeOj8T5w%40mail.gmail.com.

Re: [go-cd] LDAP Group Authentication/Roles/Permissions

[Chad Wilson]

Editing agent attributes via the UI requires wider server administration
permissions. Don't think there is anything finer grained specifically for
agent administration.

Generally speaking, to automate tagging resources and environments to
agents it is done on the agent side configuration itself via "auto
registration":
https://docs.gocd.org/current/advanced_usage/agent_auto_register.html.

You can then subsequently control which jobs are allowed to use which
logical environments and resources (i.e which agents they are able to be
scheduled on) when using pipelines as code on the permissions for a config
repository - but I do not believe that finer grained control is available
if users use the GoCD UI or APIs to edit their pipelines/jobs (i.e they
have direct edit/admin permissions for pipeline groups).

-Chad

On Wed, Nov 22, 2023 at 10:11 PM  wrote:

> Do you know if this plugin allows any configuration for static agent
> modify/admin permissions? Its doing exactly what I was looking for and
> mapping permissions from roles, and also applying the role permissions for
> pipeline groups. I’m trying to see if I can give certain users permissions
> to add resource tags or assign environments to agents without giving them
> full admin access to the server.
>
>
>
> Thanks!
>
>
>
> *From:* chant...@gmail.com 
> *Sent:* Wednesday, November 8, 2023 2:00 PM
> *To:* go-cd@googlegroups.com
> *Subject:* RE: [go-cd] LDAP Group Authentication/Roles/Permissions
>
>
>
> Thanks! I’ll take a look. We are using the bundled version.
>
>
>
> *From:* go-cd@googlegroups.com  *On Behalf Of *Chad
> Wilson
> *Sent:* Wednesday, November 8, 2023 1:09 PM
> *To:* go-cd@googlegroups.com
> *Subject:* Re: [go-cd] LDAP Group Authentication/Roles/Permissions
>
>
>
> There are multiple LDAP plugins, so it depends which one you are referring
> to. Sounds like you might want to look at
> https://github.com/gocd/gocd-ldap-authorization-plugin rather than the
> bundled 'authentication-only' version?
>
>
>
> -Chad
>
>
>
> On Thu, 9 Nov 2023, 05:33 Funkycybermonk,  wrote:
>
> Hello!
>
> I'm trying to manage a pool of users that is going to change over time and
> their permissions across multiple GoCD servers. (regional server split)
>
> I can add a group into permissions using the LDAP plugin, but it doesn't
> seem initially like the user permissions are inherited or managed by that
> group membership. Is it possible to do group based permissions from AD or
> does it have to be per-user?
>
> I'm trying to minimize work since we'll have to manually replicate the
> roles and permissions across several servers.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/4183dab6-4dad-4fd3-9055-01333843d0dbn%40googlegroups.com
> <https://groups.google.com/d/msgid/go-cd/4183dab6-4dad-4fd3-9055-01333843d0dbn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "go-cd" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/go-cd/YXdA8U4UNEY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CAA1RwH8fUnhEOODV7im%2BVU_xkTfkTEDkmpvsz_bhmDGcLrfWJA%40mail.gmail.com
> <https://groups.google.com/d/msgid/go-cd/CAA1RwH8fUnhEOODV7im%2BVU_xkTfkTEDkmpvsz_bhmDGcLrfWJA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/063a01da1d4d%24d23be980%2476b3bc80%24%40gmail.com
> <https://groups.google.com/d/msgid/go-cd/063a01da1d4d%24d23be980%2476b3bc80%24%40gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH8-uVFze56viifrbiYTUStdp6%2BG87EmZQadv4dyy6Q3yA%40mail.gmail.com.

Re: PESO: Hélène

[mike wilson]

No wonder she can't fly.
> On 21/11/2023 07:31 GMT Bob W PDML  wrote:
> 
>  
> Lunched a thousand chips, I think.
> 
> > On 20 Nov 2023, at 21:54, Larry Colen  wrote:
> > 
> > It's a lovely photo.  Is it a reference to "launching a thousand ships"?
> > 
> >> On Nov 20, 2023, at 12:21 AM, Alan C  wrote:
> >> 
> >> Very Clever!
> >> 
> >> Alan C
> >> 
> >>> On 20-Nov-23 01:30 AM, Ralf R Radermacher wrote:
> >>> ...on her favourite bollard in the port of Boulogne. There, she has
> >>> everything in sight, especially the chip shop on the other side, just in
> >>> case somehone might drop something.
> >>> 
> >>> https://www.fotocommunity.com/photo/helene-fotoralfbe/47872402
> >>> 
> >>> Enjoy
> >>> Ralf
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: [go-cd] Ruby on Rails-Server-Version end-of-life

[Chad Wilson]

Hiya Erik

Plans, yes: https://github.com/gocd/gocd/pull/12077 - but it's not EOL
*quite* yet :P. Arguably there are riskier pieces of EOL software within
GoCD than Rails right now (Spring Security, Spring Framework) and if things
get messy I'm more inclined to focus on pieces with better risk/effort
ratios.

The main "messiness" blocker with Rails 7+ right now is that GoCD currently
relies on jruby-rack which is very lightly maintained and Rack's Rails
integration, and seems to be broken in some way with Rails 7. It's not
exactly my personal core expertise, so if anyone has some clue with
Ruby/Rails/Rack these days, help would be appreciated. What is confusing to
me may be simple to you!

Unfortunately, there are not too many "GoCD people" actively working on
things left to speak of :-)

-Chad



On Wed, Nov 22, 2023 at 4:42 PM Erik Wölfel  wrote:

> Dear Gocd-People,
>
> first of all we love gocd and admire your work :-)
>
> Our security system mentions gocd using end-of-life software having the
> ruby on rails-server on version 6.1.7.6 which will be out of security
> support in half a year (1st June 24, https://endoflife.date/rails)
>
> Are there any plans on upgrading to the latest version 7.1?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/96cadc38-e56b-4812-8b37-27ac8fe189f3n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH_VACi8P%3D1yOXE9DxngGQOcY0JYmjmqOrWCsb0yNMRiTg%40mail.gmail.com.

Another replicated cache oddity

[Raymond Wilson]

Hi,

We have been triaging an odd issue we encountered in a system using Ignite
v2.15 and the C# client.

We have a replicated cache across four nodes, lets call them P0, P1, P2 &
P3. Because the cache is replicated every item added to the cache is
present in each of P0, P1, P2 and P3.

Some time ago an element (E) was added to this cache (among many others). A
number of system restarts have occurred since that time.

We started observing an issue where a query running across P0/P1/P2/P3 as a
cluster compute operation needed to load element E on each of the nodes to
perform that query. Node P0 succeeded, while nodes P1, P2 & P3 all reported
that element E did not exist.

This situation persisted until the cluster was restarted, after which the
same query that had been failing now succeeded as all four 'P' nodes were
able to read element E.

There were no Ignite errors reported in the context of these
failing queries to indicate unhappiness in the Ignite nodes.

This seems like very strange behaviour. Are there any suggestions as to
what could be causing this failure to read the replicated value on the
three failing nodes, especially as the element 'came back' after a cluster
restart?

Thanks,
Raymond.




-- 
<http://www.trimble.com/>
Raymond Wilson
Trimble Distinguished Engineer, Civil Construction Software (CCS)
11 Birmingham Drive | Christchurch, New Zealand
raymond_wil...@trimble.com

<https://worksos.trimble.com/?utm_source=Trimble_medium=emailsign_campaign=Launch>

[African Wikimedians] [WIKI LOVES AFRICA] REQUESTING TRANSLATION SUPPORT FOR THEME PAGE

[Wilson Oluoha]

Chers amis,

Comme vous le savez, le thème de Wiki Loves Africa pour 2024 est le
suivant *L'Afrique
Crée.*
Nous avons maintenant fini d'affiner le thème et nous aimerions demander le
soutien des membres de la communauté pour aider à la traduction afin de
permettre la compréhension et l'interprétation correcte par tous les
participants potentiels.

Pour cette étape, nous recherchons une aide à la traduction pour;

   - French
   - Arabic
   - Portuguese


D'autres langues sont également les bienvenues. Pour traduire, veuillez
cliquer sur ce lien:
*Traduire la page du WLA theme 2024
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024/Theme>*

Merci de votre attention.

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [WIKI LOVES AFRICA] REQUESTING TRANSLATION SUPPORT FOR THEME PAGE

[Wilson Oluoha]

Dear Friends,

As you are aware, the Wiki Loves Africa theme for 2024 is *Africa Create*.
We are now done refining the theme and would like to request the support of
members of the community to assist with translations to enable
comprehension and proper interpretation by all prospective participants.

For this stage, we are seeking translation support to;

   - French
   - Arabic
   - Portuguese


Other languages are also welcome. To translate, please click on this link:
*Translate 2024 WLA Theme page
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024/Theme>*

Thank you

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: Audit Reminder Email Summary - Intermediate Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of November 2023 Outdated Audit Statements for 
Intermediate Certs
Date: Tue, 21 Nov 2023 13:00:30 + (GMT)


CA Owner: Government of The Netherlands, PKIoverheid (Logius)
   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Services 
CA - 2023
SHA-256 Fingerprint: 
6E25C0044C7EBB30D01A4CC3D5733D734D06CD296A6823E63527F4182D528351
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Burger CA - 2023
SHA-256 Fingerprint: 
66388EE649CBE920FD949FA9B77E2AA45B5DEC4120B8FFAB371B0C9C5E38C1C1
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Persoon CA 
- 2023
SHA-256 Fingerprint: 
C8C77ECF368D73214D50D88384464339E6F8E59F34B47E39E7965F4E5787CF1D
Standard Audit Period End Date (mm/dd/): 05/31/2022


Mozilla Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1843265




-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/f7e45b22-9908-447e-b543-2d64c0f2c614n%40mozilla.org.

Re: Audit Reminder Email Summary - Root Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of November 2023 Audit Reminder Emails
Date: Tue, 21 Nov 2023 13:00:30 + (GMT)

Mozilla: Audit Reminder
CA Owner: Internet Security Research Group
Root Certificates:
   ISRG Root X2**
   ISRG Root X1**

** Audit Case in the Common CA Database is under review for this root 
certificate.

Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=cd221a0a-aa3c-49a9-bd8a-ad336588075a
Standard Audit Period End Date: 2022-08-31
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=7f5e9f87-ecfd-4120-ae6f-e136e8637a4b
BR Audit Period End Date: 2022-08-31
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Cybertrust Japan / JCSI
Root Certificates:
   SecureSign RootCA11
Standard Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=861a269b-8367-46fd-a227-b72800a41ad7
Standard Audit Period End Date: 2022-10-15
BR Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=4657c08b-4914-40ef-b905-4f21bca93b95
BR Audit Period End Date: 2022-10-15
CA Comments: null



Mozilla: Audit Reminder
CA Owner: DigiCert
Root Certificates:
   Baltimore CyberTrust Root
   DigiCert Assured ID Root CA
   DigiCert Assured ID Root G2
   DigiCert Assured ID Root G3
   DigiCert Global Root CA
   DigiCert Global Root G2
   DigiCert Global Root G3
   DigiCert High Assurance EV Root CA
   DigiCert Trusted Root G4
   VeriSign Class 1 Public Primary Certification Authority - G3
   VeriSign Class 2 Public Primary Certification Authority - G3
   Symantec Class 2 Public Primary Certification Authority - G6
   Symantec Class 1 Public Primary Certification Authority - G6
   DigiCert SMIME ECC P384 Root G5
   DigiCert TLS RSA4096 Root G5
   DigiCert TLS ECC P384 Root G5
   DigiCert SMIME RSA4096 Root G5
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=752b4e1a-b27f-4127-b7bb-a3514e573972
Standard Audit Period End Date: 2022-09-30
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=28bb7d12-a930-4d88-b8c2-c6e34ffde3da
BR Audit Period End Date: 2022-09-30
BR Audit:
BR Audit Period End Date:
EV Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=492df153-25b6-48ec-a3c3-43779fad1944
EV Audit Period End Date: 2022-09-30
EV Audit:
EV Audit Period End Date:
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Google Trust Services LLC
Root Certificates:
   GTS Root R4
   GTS Root R1
   GTS Root R2
   GTS Root R3
   GlobalSign
Standard Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=4525b841-06ec-4ec8-9cae-ad27ee4e19a9
Standard Audit Period End Date: 2022-09-30
BR Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=465a8d9c-52af-4325-9e12-bd627c853f8f
BR Audit Period End Date: 2022-09-30
EV Audit:
EV Audit Period End Date:
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Viking Cloud, Inc.
Root Certificates:
   Trustwave Global ECC P256 Certification Authority
   Trustwave Global Certification Authority
   Trustwave Global ECC P384 Certification Authority
   Secure Global CA
   SecureTrust CA
   XRamp Global Certification Authority
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=8137867c-0799-43ef-bb97-5ef63a190001
Standard Audit Period End Date: 2022-09-30
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=2b3dc01c-221d-40ed-abea-1c3d8145254f
BR Audit Period End Date: 2022-09-30
EV Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=e3b67377-1419-46b9-b9ea-bc3849bf7ef6
EV Audit Period End Date: 2022-09-30
CA Comments: Changed CA Name from Trustwave to SecureTrust on February 1, 
2019.



Mozilla: Audit Reminder
CA Owner: Agence Nationale de Certification Electronique
Root Certificates:
   TunTrust Root CA
Standard Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=edb2405f-e9c5-4cd3-a8b6-e474da09926e
Standard Audit Period End Date: 2022-09-30
BR Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=78c994d9-254e-42f4-8d52-ee104f6c936c
BR Audit Period End Date: 2022-09-30
CA Comments: null



Mozilla: Audit Reminder
CA Owner: D-Trust
Root Certificates:
   D-TRUST Root Class 3 CA 2 2009
   D-TRUST Root Class 3 CA 2 EV 2009
   D-TRUST Root CA 3 2013
   D-TRUST EV Root CA 1 2020
   D-TRUST BR Root CA 1 2020
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121604_D-TRUST_Root_Class_3_CA_2_2009.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121605_D-TRUST_Root_Class_3_CA_2_EV_2009.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/en/AA2022121603_D-TRUST_Root_CA_3_2013.pdf

:once again

[Peter Wilson]

Hello virtualization,

Are you Thinking of starting a new project or expanding your business? We can 
fund it. Terms and Conditions Apply.

Regards,
Peter Wilson

Total posting costs and precision issues?

[Bob Wilson]

Hi folks,
   I have some stock purchases that I have specified using total costs. 
Because of not-round-numbers, I'm having trouble specifying the lot so I 
can sell it cleanly.

Here's an example:

2023/11/01 * Buy Shares
Assets:401K 6.456 FSKAX @@ $734.43
Income:Opening Balances  -$734.43

2023/11/02 * Sell Shares
Assets:401K-6.456 FSKAX {$113.7592936803} 
[2023/11/01] @ $120.00
Income:Capital Gains  -$40.29
Assets:401K   $774.72

The first transaction uses the total posting cost. To record the second 
transaction, I ran, `ledger --lots balance Assets:401K`. I copied that $113 
number verbatim as printed.

So I've sold all the shares, but now when I run `ledger --lots balance 
Assets:401K`, the result is:

 $774.72
6.456 FSKAX {$113.7592936803} [2023/11/01]
-6.456 FSKAX {$113.7592936803} [2023/11/01]  Assets:401K

So it looks like the lot I sold doesn't quite match what ledger thinks I 
owned. I anticipate the issue is that the precision used in printing is 
different than the precision used to store lots internally.

I tried selling using the total posting cost:

2023/11/02 * Sell Shares
Assets:401K-6.456 FSKAX {{$734.43}} 
[2023/11/01] @ $120.00
Income:Capital Gains  -$40.29
Assets:401K   $774.72

That works great as long as I sell whole lots. But as soon as I try to sell 
a partial lot, it doesn't work at all. (The capital gains are not 
calculated correctly.)

The best idea I have right now is to just not use total posting costs, and 
always use the per-share price. But I find total posting costs to be 
convenient for many use cases.

Any suggestions?

Thanks folks!
Bob Wilson

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ledger-cli/94432f4e-fa9d-42af-8b76-3f2924c12b3bn%40googlegroups.com.

[Translators-l] Re: Ready for translation: Tech News #47 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 19 languages) to 1,100 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 47

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/47. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Changes later this week*

   - There is no new MediaWiki version this week. [1]
   [2]
   
   - Starting on Wednesday, a new set of Wikipedias will get "Add a link
   
"
   (Quechua Wikipedia, Romansh Wikipedia, Romani Wikipedia, Rundi Wikipedia,
   Aromanian Wikipedia, Tarandíne Wikipedia, Rusyn Wikipedia, Kinyarwanda
   Wikipedia, Sanskrit Wikipedia, Sakha Wikipedia, Santali Wikipedia,
   Sardinian Wikipedia, Sicilian Wikipedia, Scots Wikipedia, Sindhi Wikipedia,
   Northern Sami Wikipedia, Sango Wikipedia, Serbo-Croatian Wikipedia, Sinhala
   Wikipedia, Slovak Wikipedia, Slovenian Wikipedia, Samoan Wikipedia, Somali
   Wikipedia, Albanian Wikipedia, Serbian Wikipedia, Sranan Tongo Wikipedia,
   Swati Wikipedia, Southern Sotho Wikipedia, Saterland Frisian Wikipedia,
   Sundanese Wikipedia, Silesian Wikipedia, Tamil Wikipedia, Tulu Wikipedia,
   Telugu Wikipedia, Tetum Wikipedia, Tajik Wikipedia, Thai Wikipedia, Turkmen
   Wikipedia, Tagalog Wikipedia, Tswana Wikipedia, Tongan Wikipedia, Tok Pisin
   Wikipedia, Turkish Wikipedia, Tsonga Wikipedia, Tatar Wikipedia, Twi
   Wikipedia, Tahitian Wikipedia, Tuvinian Wikipedia, Udmurt Wikipedia, Uyghur
   Wikipedia, Uzbek Wikipedia, Venda Wikipedia, Venetian Wikipedia, Veps
   Wikipedia, West Flemish Wikipedia, Volapük Wikipedia). This is part
of the progressive
   deployment of this tool to more Wikipedias
   . The communities can configure
   how this feature works locally
   
.
   [3] [4]
   [5]
   
   - The Vector 2022 skin will have some minor visual changes to drop-down
   menus, column widths, and more. These changes were added to four Wikipedias
   last week. If no issues are found, these changes will proceed to all wikis
   this week. These changes will make it possible to add new menus for
   readability and dark mode. Learn more
   
.
   [6] 

*Future changes*

   - There is an update on re-enabling the Graph Extension
   
.
   To speed up the process, Vega 2 will not be supported and only some
   protocols  will be available
   at launch. You can help by sharing what you think about the plan.

*Tech news 

Re: ipv6 address management - documentation

[Justin Wilson (Lists)]

Netbox or PHPipam. Phpipam allows you to break down subnets easier IMHo.


Justin Wilson
j...@j2sw.com

—
https://j2sw.com (AS399332)
https://blog.j2sw.com - Podcast and Blog

> On Nov 16, 2023, at 1:09 PM, Jason Biel  wrote:
> 
> My recommendation:
> 
> https://github.com/netbox-community
> 
> 
> On Thu, Nov 16, 2023 at 12:04 PM Aaron Gould  <mailto:aar...@gvtc.com>> wrote:
>> For years I've used an MS Excel spreadsheet to manage my IPv4 
>> addresses.  IPv6 is going to be maddening to manage in a spreadsheet.  
>> What does everyone use for their IPv6 address prefix management and 
>> documentation?  Are there open source tools/apps for this?
>> 
>> -- 
>> -Aaron
>> 
> 
> 
> --
> Jason

Re: PUG themes for 2014

[mike wilson]

Best of..
Blur
Fungi
> On 18/11/2023 09:36 GMT bria...@lyons-ryan.org wrote:
> 
>  
> Here's a list of suggested themes.  Please pick your LEAST favoured 
> ones.
> 
> Up Close
> Circular
> On reflection
> Still Life
> Best of 2023
> Roots
> Abstract
> Long Exposure
> Bridges
> Blur
> On four legs
> Ice
> Marine Life
> Fungi
> Framed
> My Favourite Place
> Urban Life
> Repetition
> Sailing
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Re: Ready for translation: Tech News #47 (2023)

[Nick Wilson (Quiddity)]

On Thu, Nov 16, 2023 at 3:45 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/47
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F47=page
>

The text of the newsletter is now final.

*One item has been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [go-cd] Material branch check exclusion?

[Chad Wilson]

I think it wouldn't be so much that the *material polling* on an upstream
would affect a downstream pipeline, but more that if a build runs upstream
(regardless of trigger type), when it triggers the downstream pipeline it
possibly triggers a material check on the other materials that pipeline has
as inputs, to determine which revision the other materials should use. Kind
of like when you manually trigger a pipeline (with the "play" button) GoCD
will trigger with the latest revisions of the materials on that pipeline,
regardless of whether you have polling enabled or disabled - meaning it
triggers a modification check.

However if the same *logical* Git material (generally determined by
identical URL and branch) is used in different pipelines whether connected
to each other or not, then the polling setting of one can definitely affect
others, I believe. Generally speaking GoCD complains at you when there are
conflicting values for the same logical material and asks you to make them
all the same, but I have seen cases where it gets confused or ends up
allowing inconsistent values here, and behaviour becomes indeterminate.
This is one of the testing challenges with fixing/allowing the change in
https://github.com/gocd/gocd/pull/11636 which would make it easier to
support such autoUpdate=false repos from pipelines-as-code. If the concern
is the triggering (rather than spurious errors from deleting branches as in
your case) the workaround some folks use for this is to put **/* material
deny lists on pipelines, so even if the material is polled and updated it
shouldn't cause a trigger since the denylists/allowlists are processed in
the context of an individual pipeline, rather than the (de-duplicated)
material itself.

But yes, the "default" is autoUpdate=true/polling.

-Chad

On Sat, Nov 18, 2023 at 1:27 AM 'Chris Gillatt' via go-cd <
go-cd@googlegroups.com> wrote:

> Thanks Chad
>
> I've done some more investigation and you're right - there's some upstream
> pipelines set to "Regularly fetch updates to this repository" rather than
> our company strategy of "Fetch updates only on webhook or manual trigger".
> I wasn't aware that upstream material configurations could affect
> downstream ones.  We rely on templates for the majority of our pipeline
> creations, and use an in-house tool (relying on GoCD APIs) that explicitly
> specify 'autoUpdate="false"'.  It's been a while since I've created a
> pipeline from the GoCD wizard or from scratch, so not sure if this has
> always been the case, but through the GoCD GUI Create Pipeline workflow,
> the material configuration is selected *before* a template is chosen,
> meaning templates cannot control advanced material configuration, such as
> autoUpdate="false".  Unless the user selects this from the material
> Advanced menu at the time, the default is essentially 'autoUpdate="true"'.
> I think that a bunch of these has crept in since I last cleared them up.
>
> For posterity for anyone else reading this, some contextual info is useful
> to know:
>
> 1. When "Regularly fetch updates to this repository" is selected, it is
> not explicitly expressed in the XML.  Its absence on the line beginning
>  simply delete the key value pair, and "Regularly fetch updates to this
> repository" is selected.
> 2. When "Fetch updates to this repository only on webhook or manual
> trigger" is selected, on the line beginning  3. This property must be the same over all pipelines which use the same
> material.  You cannot have one pipeline which pulls and one which receives
> a push for the same material.
> On Friday, November 17, 2023 at 2:54:32 AM UTC Chad Wilson wrote:
>
>> In theory if you have disabled polling on all usages of the material (via
>> its URL/branch combination), and there are no triggers from webhooks, APIs
>> or elsewhere then it shouldn't be trying to do modification checks that
>> generate such an error.
>>
>> [image: image.png]
>> Having said that, I wouldn't *entirely* be surprised if there is some
>> other kind of trigger for an update/modification check, e.g as a side
>> effect of an upstream pipeline completing (if there is one) or a server
>> restart, even if that is not intended.
>>
>> If you have disabled that polling everywhere and are still seeing the
>> error appear, it'd be interesting to know if you can figure out when it is
>> triggered.
>>
>> -Chad
>>
>>
>> On Fri, Nov 17, 2023 at 5:51 AM 'Chris Gillatt' via go-cd <
>> go...@googlegroups.com> wrote:
>>
>>> Hi all
>>>
>>> Is there a way to exclude a pipeline or pipeline group from the material
>>> checks?
>>>
>>> [image: S

Re: [go-cd] GOCD Version Upgrade Issue - Windows Agents Failing to Execute 'git pull'

[Chad Wilson]

Hi, the screenshot didn't come through correctly, so it would be good if
you can include that.

>From looking at the XML, If I recall correctly, it might be that you were
using the "legacy"/historical syntax for handling exec commands, but need
to dig a bit more. With this syntax it is somewhat indeterminate how spaces
should be handled. However, I don't think it was intentionally broken by
the changes I mentioned in 22.2.0 - although it looks like it might be the
case for you. I'd have to validate separately whether you were just using
incorrect configuration that happened to work. It should look like this on
the UI if you want to do it this way without using a separate script.

[image: image.png]
You might want to try editing the command via the UI, and then editing it
back in case the syntax needs converting, which will look like:

  
pull

  

-Chad

On Sat, Nov 11, 2023 at 2:38 AM Sri Sai Sruthi JAGANNADDAM <
sjagannad...@mdsol.com> wrote:

> Here is the screenshot
>
> git pull & mkdir reports 2nul & IF DEFINED APP_IR_GENERATOR
> (%APP_IR_GENERATOR%)" are failing as they are not able to recognize git &
> mkdir, its not a agent issue because the same agent when attached to the
> gocd server running on 21.2 version it works fine but not working on 23.3
> version, as you mentioned custom commands does not allow spaces in the new
> gocd version, what is best way to handle this, thanks for your inputs
> backend code:
>
> 
>   
> 
>   
>pipeline="" stage="Build" job="defaultJob">
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
>
> [image: image.png]
> On Friday, November 10, 2023 at 12:15:03 AM UTC-6 Chad Wilson wrote:
>
>> It's possibly a side effect of fixing issues with spaces in windows
>> commands in GoCD 22.2.0:  https://www.gocd.org/releases.html#22-2-0
>>
>> It may be that some of your command tasks were *technically* incorrectly
>> configured on earlier versions but worked as a side effect of these bugs in
>> GoCD, and GoCD is now stricter. Or it may be that there is a regression in
>> some circumstances.
>>
>> Can you please
>> - share a screenshot of the UI pipeline task configuration for the 'git
>> pull' example above?
>> - find that specific task's XML definition inside admin > config XML and
>> share the XML fragment for the task or job (you can redact any sensitive
>> text, I am mainly interested in the 'shape' of the XML)
>>
>> If my suspicion is correct, a workaround will certainly be possible to
>> correct the task config, but as there are a couple of historical ways tasks
>> could be configured, I'd like to understand what your config looked like
>> before you workaround the problem so I can see if this is avoidable.
>>
>> -Chad
>>
>>
>> On Fri, 10 Nov 2023, 15:55 Sri Sai Sruthi JAGANNADDAM, <
>> sjagan...@mdsol.com> wrote:
>>
>>>  Could any one please help with this - I am writing to report a
>>> challenge we’ve encountered following our recent upgrade from GOCD version
>>> 21.2 to version 23.3. During our testing phase, we observed that certain
>>> pipelines, which execute on Windows agents, are failing with the following
>>> error when run through "Custom Command"
>>>
>>>  [go] Task: git pull
>>> Took: 0.179s
>>> Exited: 1
>>> '"git pull"' is not recognized as an internal or external command,
>>> operable program or batch file.
>>>
>>>
>>> This issue seems to be isolated to the Windows agents as the pipelines
>>> running on Linux agents are performing without any issues.
>>> The same pipelines were functioning correctly on the previous version of
>>> the GOCD server,
>>> which suggests a potential configuration or environment variable path
>>> discrepancy in the new version.
>>>
>>>
>>> --
>>> The information in this email and any attachments are intended solely
>>> for the recipient(s) to whom it is addressed, and may be confidential
>>> and/or privileged. Any unauthorized distribution or copying of this
>>> transmittal or its attachments is prohibited. If you are not a named
>>> recipient or have received this email in error: (i) you should not read,
>>> disclose, or copy it, (ii) please noti

[Translators-l] Ready for translation: Tech News #47 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/47

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F47=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[ovs-dev] [PATCH] python: idl: Handle monitor_canceled

[Terry Wilson]

Currently python-ovs claims to be "db change aware" but does not
parse the "monitor_canceled" notification. Transactions can continue
being made, but the monitor updates will not be sent. Adding a
force_reconnect() upon receiving a "monitor_canceled" notification
resolves this issue.

Signed-off-by: Terry Wilson 
---
 python/ovs/db/idl.py | 4 
 1 file changed, 4 insertions(+)

diff --git a/python/ovs/db/idl.py b/python/ovs/db/idl.py
index 16ece0334..cfd81a1ec 100644
--- a/python/ovs/db/idl.py
+++ b/python/ovs/db/idl.py
@@ -481,6 +481,10 @@ class Idl(object):
 break
 else:
 self.__parse_update(msg.params[1], OVSDB_UPDATE)
+elif (msg.type == ovs.jsonrpc.Message.T_NOTIFY
+and msg.method == "monitor_canceled"):
+self.force_reconnect()
+break
 elif (msg.type == ovs.jsonrpc.Message.T_REPLY
   and self._monitor_request_id is not None
   and self._monitor_request_id == msg.id):
-- 
2.34.3

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [OVN RFC 0/7] OVN IC bugfixes & proposals/questions

[Terry Wilson]

On Tue, Jan 24, 2023 at 8:00 AM Ilya Maximets  wrote:
>
> On 1/24/23 14:12, Vladislav Odintsov wrote:
> > Hi Ilya,
> >
> > could you please take a look on this?
> > Maybe you can advice any direction how to investigate this issue?
> >
> > Thanks in advance.
> >
> > Regards,
> > Vladislav Odintsov
> >
> >> On 24 Nov 2022, at 21:10, Anton Vazhnetsov  wrote:
> >>
> >> Hi, Terry!
> >>
> >> In continuation to our yesterday’s conversation [0], we were able to 
> >> reproduce the issue with KeyError. We found that the problem is not 
> >> connected with ovsdb-server load but it appears when the ovsdb-server 
> >> schema is converted online (it even doesn’t matter whether the real ovs 
> >> schema is changed) while the active connection persists.
> >> Please use next commands to reproduce it:
> >>
> >> # in terminal 1
> >>
> >> ovsdb-tool create ./ovs.db /usr/share/ovn/ovn-nb.ovsschema
> >> ovsdb-server --remote punix://$(pwd)/ovs.sock  
> >> $(pwd)/ovs.db -vconsole:dbg
> >>
> >>
> >> # in terminal 2. run python shell
> >> python3
> >> # setup connection
> >> import ovsdbapp.schema.ovn_northbound.impl_idl as nb_idl
> >> from ovsdbapp.backend.ovs_idl import connection
> >>
> >> remote = "unix:///"
> >>
> >> def get_idl():
> >>"""Connection getter."""
> >>
> >>idl = connection.OvsdbIdl.from_server(remote, "OVN_Northbound",
> >>  leader_only=False)
> >>return nb_idl.OvnNbApiIdlImpl(connection.Connection(idl, 100))
> >>
> >> idl = get_idl()
> >>
> >>
> >> # in terminal 1
> >> ovsdb-client convert unix:$(pwd)/ovs.sock /usr/share/ovn/ovn-nb.ovsschema
> >>
> >> # in terminal 2 python shell:
> >> idl.ls_add("test").execute()
> >>
> >>
> >> We get following traceback:
> >>
> >> Traceback (most recent call last):
> >>  File 
> >> "/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/connection.py", 
> >> line 131, in run
> >>txn.results.put(txn.do_commit())
> >>  File 
> >> "/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/transaction.py",
> >>  line 143, in do_commit
> >>self.post_commit(txn)
> >>  File 
> >> "/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/transaction.py",
> >>  line 73, in post_commit
> >>command.post_commit(txn)
> >>  File 
> >> "/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/command.py", 
> >> line 94, in post_commit
> >>row = self.api.tables[self.table_name].rows[real_uuid]
> >>  File "/usr/lib64/python3.6/collections/__init__.py", line 991, in 
> >> __getitem__
> >>raise KeyError(key)
> >> KeyError: UUID('0256afa4-6dd0-4c2c-b6a2-686a360ab331')
> >>
> >> In ovsdb-server debug logs we see that update2 or update3 messages are not 
> >> sent from server in response to client’s transaction, just reply with 
> >> result UUID:
> >> 2022-11-24T17:42:36Z|00306|poll_loop|DBG|wakeup due to [POLLIN] on fd 18 
> >> (///root/ovsdb-problem/ovs.sock<->) at lib/stream-fd.c:157
> >> 2022-11-24T17:42:36Z|00307|jsonrpc|DBG|unix#5: received request, 
> >> method="transact", 
> >> params=["OVN_Northbound",{"uuid-name":"row03ef28d6_93f1_43bc_b07a_eae58d4bd1c5","table":"Logical_Switch","op":"insert","row":{"name”:"test"}}],
> >>  id=5
> >> 2022-11-24T17:42:36Z|00308|jsonrpc|DBG|unix#5: send reply, 
> >> result=[{"uuid":["uuid","4eb7c407-beec-46ca-b816-19f942e57721"]}], id=5
> >>
> >> We checked same with ovn-nbctl running in daemon mode and found that the 
> >> problem is not reproduced (ovsdb-server after database conversion sends 
> >> out update3 message to ovn-nbctl daemon process in response to 
> >> transaction, for example ovs-appctl -t  run ls-add 
> >> test-ls):
>
> If the update3 is not sent, it means that the client doesn't monitor
> this table.  You need to look at monitor requests sent and replied
> to figure out the difference.
>
> Since the database conversion is involved, server will close all
> monitors on schema update and notify all clients that are db_change_aware.
> Clients should re-send monitor requests at this point.  If clients
> are not db_change_aware, server will just disconnect them, so they
> can re-connect and see the new schema and send new monitor requests.
>
> On a quick glance I don't see python idl handling 'monitor_canceled'
> notification.  That is most likely a root cause.  Python IDL claims
> to be db_change_aware, but it doesn't seem to be.
>

Reviving a very old thread, but yes this is definitely the issue. I
just tested and see that we get the monitor_canceled and do not do
anything with it. Parsing it and calling self.force_reconnect() seems
to fix the issue. I can send a patch shortly.

Terry


> Best regards, Ilya Maximets.
>
> >> 2022-11-24T17:54:51Z|00623|jsonrpc|DBG|unix#7: received request, 
> >> method="transact", 
> >> params=["OVN_Northbound",{"uuid-name":"rowcdb152ce_a9af_4761_b965_708ad300fcb7","table":"Logical_Switch","op":"insert","row":{"name":"test-ls"}},{"comment":"ovn-nbctl:
> >>  run ls-add test-ls","op":"comment"}], id=5
> >> 

Re: Stabilized Eclipse Video

[mike wilson]

Interesting that you didn't get any level of "diamond ring" effect.  I'm not 
sure what that indicates.

> On 16/11/2023 01:36 GMT John Sessoms  wrote:
> 
>  
> https://flic.kr/p/2pg1zWk
> 
> Wasn't as difficult as I thought it was going to be. One of my schemes 
> actually worked which smoothed production immensely.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[List admins] Re: Spam prevention

[Nick Wilson (Quiddity)]

On Thu, Nov 16, 2023 at 1:11 AM Ciell Wikipedia 
wrote:

> In the old system we could use regex strings to avoid the most obvious
> spam: am I reading it correctly we should now enter these strings under the
> 'banned addresses' tab? Do we have a quick-guide on how to compose these
> strings? (I think my lists lost these settings in the upgrade, and my regex
> knowledge is insufficient to write them myself.)
>

I believe that is correct, and the details in this section should be
uptodate:
https://meta.wikimedia.org/wiki/Mailing_lists/Administration#Auto-discarding_spam
(I.e. They were added after the Mailman3 migration, and edited by multiple
people, so hopefully any errors have already been corrected!)
However, they could perhaps be improved with more examples?
(If anyone has questions about specific examples, perhaps ask on the
talkpage there?)

Op do 16 nov 2023 om 03:23 schreef Platonides :
>
>> PS: I see some outdated pieces on
>> https://meta.wikimedia.org/wiki/Mailing_lists/Administration
>> 
>> that are no longer applicable on mailman 3
>>
>
Please boldly edit the page to remove/update anything inaccurate, or raise
concerns on the talkpage!
+1 to your other comments.

I hope that helps,
Quiddity
___
Listadmins mailing list -- listadmins@lists.wikimedia.org
To unsubscribe send an email to listadmins-le...@lists.wikimedia.org

To request technical changes for a specific list, please instead create a task 
in Phabricator. See https://meta.wikimedia.org/wiki/Mailing_lists

:once again

[Peter Wilson]

Hello lvs-devel,

Are you Thinking of starting a new project or expanding your business? We can 
fund it. Terms and Conditions Apply.

Regards,
Peter Wilson

Re: DLF September 2023 Planning Update

[Adam Wilson via Digitalmars-d-announce]

On Wednesday, 15 November 2023 at 05:27:40 UTC, Mike Parker wrote:
If someone misses all of that and tries to use tuples without 
specifying edition N, the compiler should be able to tell them 
what the problem is, how to solve it (annotate your module 
declaration with `@edition(N)`), and provide the URL to the 
relevant documentation.


This is exactly backwards from how most languages today. By 
default you are working with the current edition and you have to 
down-select to earlier editions.


But if we're really enamored of using the crippled version of the 
language by default then it is absolutely imperative that edition 
selection be a command-line option.


Here is how it should work IMO. The build system needs to able to 
specify editions at the package level, but when no package level 
edition is specified, then you assume current. If you need to 
down-select to an older edition then the dependency specifier in 
the project file that I control must set the correct edition. 
This neatly works around the lack of edition specifier in 
abandonware without enforcing crippled-by-default behavior that 
is going to confuse the entire world.

Re: Computers! Aargh!

[mike wilson]

> On 15/11/2023 02:28 GMT Rick Womer  wrote:
> 
>  
> I’ve accumulated a lot of photos recently, from travel and walks through 
> groves of autumn color.
> 
> Today I sat down to post some. But…
> 
> When I launched Lightroom the window that should have displayed the photos 
> was blank. Both my primary and secondary external hard drives had errors that 
> Disk Utility couldn’t fix. I have no idea why.
> 
> Not sure how to approach this yet, but I will likely spend several more hours 
> sorting things out.
> 
> Sometimes I really miss film, a light box, and a loupe.

I feel your pain.  I lost about four years' work due to a hardware failure 
(exacerbated by my own stupidity) and have hardly picked up a camera since.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: First Beta 2.106.0

[Adam Wilson via Digitalmars-d-announce]

On Tuesday, 14 November 2023 at 17:44:11 UTC, Steven 
Schveighoffer wrote:

This might be one of the greatest releases of D ever.

-Steve


I second this.

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

[Chad Wilson]

While getting a new plugin initially configured, I would use the UI to
begin with, yes.

Your `ls` command starts with 'gocd-' so is filtering out plugins that
don't start with the same (such as the docker elastic agent plugin). If the
version and list of plugins is correct on the admin > plugins list, you can
rely on that.

Your other thread mentions an intention to use ECS containers as agents.
Note that there is a different ECS-specific plugin to use if you want to
use ECS and have GoCD manage instances for agents to run on. The docker
elastic agent plugin will run agent instances as containers on an existing
individual local or remote host but is not intended for ECS usage which
require specific API usage to create task definitions etc. Just to be clear.

-Chad

On Wed, 15 Nov 2023, 10:14 Satya Elipe,  wrote:

> Thank you Chad, so what's the best approach to add the profiles, server
> console/UI ?
>
> Also, I'm trying to understand this:
> I see v3.2.3 on the console () and the container shows the old version
> that's 2.2.0 (ec2 plugin and not docker)
> Attached are the screenshots for both, am I missing something ?
>
> This is how I run the container and volume mounts are from the original
> backed-up server to the container.
> ```
> docker run -d -p 8153:8153 -p 8154:8154 \
>   -v /etc/go:/etc/go \
>   -v /var/lib/go-server:/var/lib/go-server \
>   -e GOCD_PLUGIN_INSTALL_docker-elastic-agents=
> https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/download/v3.2.3-399/docker-elastic-agents-3.2.3-399.jar
> \
>   --name gocd-server \
>   gocd/gocd-server:v22.3.0```
>
> Sorry about cruise-config.xml, looks like I have sent the old config.
>
> Best
> Satya
>
>
> On Tue, Nov 14, 2023 at 8:18 PM Chad Wilson 
> wrote:
>
>> The pluginId in that cluster profile fragment refers to a completely
>> different ec2 elastic agent plugin so not sure what you're trying to show
>> us there 
>>
>> Personally, I don't think it's a good idea to be directly configuring
>> cruise-config.xml especially for plugin-oriented config, since it
>> necessarily cannot be schema validated. Elastic agent config is typically
>> complex with validation rules implemented in the plugin. If automation is
>> the goal, using the APIs for automation is likely a better experience than
>> cruise-config.xml hacking.
>>
>> If you really want to control cruise config directly, start with a
>> working UI-driven configuration and work backwards to the required
>> cruise-config XML fragment.
>>
>> Otherwise you'll need to look at the logs and there's no guarantee as to
>> how friendly the error messages will be, as you are shortcutting all of the
>> UI-based validation assistance with that approach.
>>
>> -Chad
>>
>> On Wed, 15 Nov 2023, 04:16 Satya Elipe,  wrote:
>>
>>> Thank you Chad, as suggested I have used v3.2.3 in the container and it
>>> appears in the console.
>>>
>>> Im now into configuring cluster and agents profiles and trying to build
>>> them in cruise-config.xml (attached the code snippet), but doesn't seem to
>>> be working as those profiles doesn't appear on the Admin->Elastic Agents
>>> Configurations tab, but its asking for a fresh configuration, wonder what
>>> am I missing? Also, is it still a valid way of configuration ?
>>>
>>> Regards
>>> Satya
>>>
>>>
>>> On Mon, Nov 13, 2023 at 11:08 PM Chad Wilson 
>>> wrote:
>>>
>>>> There's no such release. You should use a non-experimental release from
>>>> https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases
>>>> and find the link to the main jar file within that release.
>>>>
>>>> There should be no reason you cannot use the most recent release
>>>> <https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/tag/v3.2.3-399>:
>>>>
>>>> https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/download/v3.2.3-399/docker-elastic-agents-3.2.3-399.jar
>>>>
>>>> -Chad
>>>>
>>>> On Tue, Nov 14, 2023 at 10:50 AM Satya Elipe 
>>>> wrote:
>>>>
>>>>> Hi All
>>>>>
>>>>> Im containerizing my standalone GoCD server v22.3.0 with elastic
>>>>> agents, and looking for the elastic agents plugin jar file location for 
>>>>> the
>>>>> version that works with server version v22.3.0 and use it in the container
>>>>> something like:
>>>>>
>>>>> docker run -d -p 8153:8153 -p 

Re: [go-cd] Agent docker image

[Chad Wilson]

The default go-server docker image is Alpine based, so the equivalent image
would be https://hub.docker.com/r/gocd/gocd-agent-alpine-3.18

Having said this, most folks find they end up building their own agent
image using a GoCD official image as base image, so they can add on
required tooling of their own which they want to be available to jobs.

If you are moving from running builds directly on your EC2 instances you
might want to consider picking a base image closer to your normal Linux
ecosystem or package manager, especially if you do native compiles or
things like that which require a C/C++ compiler toolchain inside agents.
Your choices right now are Alpine, Debian, Ubuntu, CentOS Stream (other
than building your own) https://www.gocd.org/download/#docker

-Chad

On Wed, 15 Nov 2023, 06:27 Satya Elipe,  wrote:

> Thank you Sriram.
> My comments inline please.
>
> Are you planning to run the go server as an ECS instance and The go agent
> as a ECS instance?
> Satya] Yes, server will be part of ECS (ECS instance) and it will launch
> the agents dynamically when theres a job to perform and once the job is
> done the agent is terminated
>
> You should start by understanding the following:
> -  how the containerised server and agent work
> Satya] If Im not wrong, this goes with docker elastic plugin, configuring
> cluster and agent profiles, setting up agentAutoRegisterKey in
> cruise-config.yml and the below configuration in the cruise-config.yml.
>
> Agent: this would go into agent container
> ```
>   ec2_user_data
>   echo
> "agent.auto.register.environments=production,sandbox" 
> /var/lib/go-agent/config/autoregister.properties
> ```
>
> So, we should have this file updated with the required details including
> the agentAutoRegisterKey (as given here
> 
> ), so agent would know what server it is working with, correct me if I am
> wrong please.
>
> - auto registration of the agent
> Satya] as mentioned above.
>
> - scaling ECS instances ( for the agent)
> - addressing a server instance via an ALB
> - the security group settings needed to enable the agent ECS cluster to
> connect to the server on port 8153.
> - using RDS for the server data ( including migrating from the H2DB to RDS)
> - storing files on EFS and making available to the go server instance (
> artifacts, configuration, logs)
> - sending logs to cloud watch
>
> Satya] Yes, mostly set up is the same, but just that whether H2DB or RDS .
>
> Thank you
> Satya
>
> On Fri, Nov 10, 2023 at 4:31 PM Sriram Narayanan 
> wrote:
>
>>
>>
>> On Sat, 11 Nov 2023 at 12:00 AM, Satya Elipe 
>> wrote:
>>
>>> Hi All
>>>
>>> Any recommendation for go-agent docker image like we have for go-server
>>> (gocd/go-server:v22.3.0) ?
>>>
>>> We are dockerizing a stand-alone g-server runs as an ec2 at the moment
>>> but would like to move it to ECS.
>>>
>>> any inputs will be appreciated.
>>>
>>
>> Are you planning to run the go server as an ECS instance and The go agent
>> as a ECS instance?
>>
>> You should start by understanding the following:
>> -  how the containerised server and agent work
>> - auto registration of the agent
>> - scaling ECS instances ( for the agent)
>> - addressing a server instance via an ALB
>> - the security group settings needed to enable the agent ECS cluster to
>> connect to the server on port 8153.
>> - using RDS for the server data ( including migrating from the H2DB to
>> RDS)
>> - storing files on EFS and making available to the go server instance (
>> artifacts, configuration, logs)
>> - sending logs to cloud watch
>>
>> You could also consider using the Elastic Agent support to use EKS based
>> agents instead of ECS. See:
>> https://github.com/gocd/kubernetes-elastic-agents
>>
>> — Sriram
>>
>>
>>
>>> Many thanks
>>> Satya
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/CADKEDRrGqba1Oi3Wcu7%2BTJEuKMENkWOc-JbMcKb2XG1Px6BJGQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/CANiY96Y8ZwK5fcVeSsySGLXxdLdPNG356_f-BGVWkaa%3DAA%2BX3w%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because 

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

[Chad Wilson]

The pluginId in that cluster profile fragment refers to a completely
different ec2 elastic agent plugin so not sure what you're trying to show
us there 

Personally, I don't think it's a good idea to be directly configuring
cruise-config.xml especially for plugin-oriented config, since it
necessarily cannot be schema validated. Elastic agent config is typically
complex with validation rules implemented in the plugin. If automation is
the goal, using the APIs for automation is likely a better experience than
cruise-config.xml hacking.

If you really want to control cruise config directly, start with a working
UI-driven configuration and work backwards to the required cruise-config
XML fragment.

Otherwise you'll need to look at the logs and there's no guarantee as to
how friendly the error messages will be, as you are shortcutting all of the
UI-based validation assistance with that approach.

-Chad

On Wed, 15 Nov 2023, 04:16 Satya Elipe,  wrote:

> Thank you Chad, as suggested I have used v3.2.3 in the container and it
> appears in the console.
>
> Im now into configuring cluster and agents profiles and trying to build
> them in cruise-config.xml (attached the code snippet), but doesn't seem to
> be working as those profiles doesn't appear on the Admin->Elastic Agents
> Configurations tab, but its asking for a fresh configuration, wonder what
> am I missing? Also, is it still a valid way of configuration ?
>
> Regards
> Satya
>
>
> On Mon, Nov 13, 2023 at 11:08 PM Chad Wilson 
> wrote:
>
>> There's no such release. You should use a non-experimental release from
>> https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases
>> and find the link to the main jar file within that release.
>>
>> There should be no reason you cannot use the most recent release
>> <https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/tag/v3.2.3-399>:
>>
>> https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/download/v3.2.3-399/docker-elastic-agents-3.2.3-399.jar
>>
>> -Chad
>>
>> On Tue, Nov 14, 2023 at 10:50 AM Satya Elipe 
>> wrote:
>>
>>> Hi All
>>>
>>> Im containerizing my standalone GoCD server v22.3.0 with elastic agents,
>>> and looking for the elastic agents plugin jar file location for the version
>>> that works with server version v22.3.0 and use it in the container
>>> something like:
>>>
>>> docker run -d -p 8153:8153 -p 8154:8154 \
>>>   -v /etc/go:/etc/go \
>>>   -v /var/lib/go-server:/var/lib/go-server \
>>>   -e GOCD_PLUGIN_INSTALL_docker-elastic-agents=
>>> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
>>> \
>>>   --name gocd-server \
>>>   gocd/gocd-server:v22.3.0
>>>
>>> The above command fails with the below error:
>>> ```$ mkdir -p /godata/plugins/external
>>> $ curl --silent --location --fail --retry 3
>>> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
>>> --output /godata/plugins/external/docker-elastic-agents.jar
>>> /usr/local/sbin/install-gocd-plugins: cannot curl --silent --location
>>> --fail --retry 3
>>> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
>>> --output /godata/plugins/external/docker-elastic-agents.jar```
>>>
>>>
>>> I see the documentation available for the same, my bad that I couldn't
>>> locate the jar file:
>>> https://github.com/gocd-contrib/docker-elastic-agents-plugin
>>>
>>> https://github.com/gocd-contrib/docker-elastic-agents-plugin/blob/master/INSTALL.md
>>>
>>> Any inputs will be of great help.
>>>
>>> Many thanks
>>> Satya
>>>
>>> [P.S: Right now the server runs as a standalone ec2 on AWS, plan is to
>>> run it as part of ECS.]
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/CADKEDRpTctJDBtWXSJWoEW81ryUwL7cAzeePbuZd4wi7LDmQFg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/go-cd/CADKEDRpTctJDBtWXSJWoEW81ryUwL7cAzeePbuZd4wi7LDmQFg%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>>

Re: DLF September 2023 Planning Update

[Nicholas Wilson via Digitalmars-d-announce]

On Tuesday, 14 November 2023 at 08:18:20 UTC, Mike Parker wrote:

## Editions
We had agreed in [the September monthly 
meeting](https://forum.dlang.org/post/hetwfhikjqwzlvywm...@forum.dlang.org) the week before that we need to define what editions will look like before we start deciding which features should go in any given edition.


Good

My goal with this session was to establish the first point on 
the timeline: a deadline for the editions proposal. I also 
thought it would be a good opportunity for all of us to clarify 
what editions are (there were some different ideas about that) 
and discuss aspects of the concept we need to consider.


Here are some points that came out of the discussion.

* Editions are essentially feature sets. Each edition can 
add/remove/deprecate features.
* Editions are entirely opt-in and only affect the source you 
explicitly apply them to, i.e., they are not transitive to 
dependencies.


(see note below about packages)

* Editions will most likely be implemented via an attribute on 
the module declaration. We haven't discussed any details about 
that, but for now, just imagine something like `@edition(2024) 
module foo;`.


There are an awful lot of `version`s set by things that should be 
part of editions, but exactly how this is supposed to be 
implemented can be hashed out later.


They should also be ideally settable via a (say) an attribute, on 
the module declaration of a package and have that apply to the 
whole package. That way we limit a whole lot of redundant 
configuration.


* Features cannot be opted into individually. When you apply an 
edition to a module, you get the whole thing.


Well that's DoA then. Why bother to implement feature sets if you 
can't select them?
This is a particular problem from incompatible sets of features, 
which D has a not insignificant amount of ( betterC, basically 
all of the -preview flags), including things that affect 
safety/codegen like `-boundscheck`, `-check`, `-checkaction`, 
`-cov`.


Selectable features would solve the problem of "a dependancy uses 
an option I don't want to enable"


Implementing default combinations of features (editions) on top 
of selectable features would be reasonable.


* The default edition, meaning the code you have now, should 
compile forever.


I hope you mean "we will keep around old editions as (potentially 
command line) selectable options and we can update the default to 
be the current"


* We should have a tool that automates as much as possible the 
migration of modules to new editions
* DMD-as-a-library is a critical component for that tool and 
other tools in the ecosystem. We need to put a priority on 
working out all the implementation issues Razvan has raised.
* Given that much of the D community uses code-d, we need to 
bring Jan Jurzitza into any discussions about DMD-as-a-library.


Yes, yes, yes.

[Translators-l] Re: Ready for translation: Tech News #46 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 20 languages) to 1,097 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 46

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/46. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, বাংলা
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - Four new wikis have been created:
  - a Wikipedia in Moroccan Amazigh
   (w:zgh:
  ) [1]
  
  - a Wikipedia in Dagaare  (
  w:dga: ) [2]
  
  - a Wikipedia in Toba Batak  (
  w:bbc: ) [3]
  
  - a Wikiquote in Banjar  (q:bjn:
  ) [4]
  

*Problems*

   - Last week, users who previously visited Meta-Wiki or Wikimedia Commons
   and then became logged out on those wikis could not log in again. The
   problem is now resolved. [5] 
   - Last week, some pop-up dialogs and menus were shown with the wrong
   font size. The problem is now resolved. [6]
   

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 14 November. It
   will be on non-Wikipedia wikis and some Wikipedias from 15 November. It
   will be on all wikis from 16 November (calendar
   ).

*Future changes*

   - Reference Previews are coming to many wikis as a default feature. They
   are popups for references, similar to the PagePreviews feature
   . You
   can opt out
   

   of seeing them. If you are using the gadgets
   
   Reference Tooltips or Navigation Popups, you won’t see Reference Previews.
   Deployment  is planned for
   November 22, 2023.
   - Canary (also known as heartbeat) events will be produced into Wikimedia
   event streams  from December
   11. Streams users are advised to filter out these events, by discarding all
   events where meta.domain == "canary". Updates to Pywikibot
    or
   wikimedia-streams 
   will discard these events by default. [7]
   

*Tech news 
prepared by Tech News writers

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

[Chad Wilson]

There's no such release. You should use a non-experimental release from
https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases and
find the link to the main jar file within that release.

There should be no reason you cannot use the most recent release
:
https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases/download/v3.2.3-399/docker-elastic-agents-3.2.3-399.jar

-Chad

On Tue, Nov 14, 2023 at 10:50 AM Satya Elipe  wrote:

> Hi All
>
> Im containerizing my standalone GoCD server v22.3.0 with elastic agents,
> and looking for the elastic agents plugin jar file location for the version
> that works with server version v22.3.0 and use it in the container
> something like:
>
> docker run -d -p 8153:8153 -p 8154:8154 \
>   -v /etc/go:/etc/go \
>   -v /var/lib/go-server:/var/lib/go-server \
>   -e GOCD_PLUGIN_INSTALL_docker-elastic-agents=
> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
> \
>   --name gocd-server \
>   gocd/gocd-server:v22.3.0
>
> The above command fails with the below error:
> ```$ mkdir -p /godata/plugins/external
> $ curl --silent --location --fail --retry 3
> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
> --output /godata/plugins/external/docker-elastic-agents.jar
> /usr/local/sbin/install-gocd-plugins: cannot curl --silent --location
> --fail --retry 3
> https://github.com/gocd-contrib/docker-elastic-agents/releases/download/v2.2.0-218/docker-elastic-agents-2.2.0-218.jar
> --output /godata/plugins/external/docker-elastic-agents.jar```
>
>
> I see the documentation available for the same, my bad that I couldn't
> locate the jar file:
> https://github.com/gocd-contrib/docker-elastic-agents-plugin
>
> https://github.com/gocd-contrib/docker-elastic-agents-plugin/blob/master/INSTALL.md
>
> Any inputs will be of great help.
>
> Many thanks
> Satya
>
> [P.S: Right now the server runs as a standalone ec2 on AWS, plan is to run
> it as part of ECS.]
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CADKEDRpTctJDBtWXSJWoEW81ryUwL7cAzeePbuZd4wi7LDmQFg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH_-2KLLOTYUOuHHVuSNBLO1Ax24n6zyRHTpm6KftaUKkQ%40mail.gmail.com.

Re: test 1 - godfreydigio...@me.com

[mike wilson]

Only about 4-5 members get dumped in SPAM, including myself.  Have tired all 
ways of whitelisting and suchlike but no luck.  It's clearly something outside 
my control.  I suspect it might be because the addresses have been spoofed at 
some time.  I know mine has because I used to get quite a few offers for blue 
pills from myself.

> On 11/11/2023 17:33 GMT Godfrey DiGiorgi  wrote:
> 
>  
> Thanks mike. Shows that this is the email address that gets through, even if 
> Mail puts it into the spam folder … like it does for 80% of all the active 
> PDML posts. Wish I knew the cause of that… it's a PITA. 
> 
> G
> 
> > On Nov 11, 2023, at 8:56 AM, mike wilson  wrote:
> > 
> > No, you're in my SPAM folder, as usual...
> > 
> >> On 11/11/2023 16:49 GMT Godfrey DiGiorgi  wrote:
> >> 
> >> 
> >> replies and messages I've sent don't seem to be getting to the list. I'm 
> >> testing both my email addresses to see if either of these get there. 
> >> 
> >> G
> --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: test 1 - godfreydigio...@me.com

[mike wilson]

No, you're in my SPAM folder, as usual...

> On 11/11/2023 16:49 GMT Godfrey DiGiorgi  wrote:
> 
>  
> replies and messages I've sent don't seem to be getting to the list. I'm 
> testing both my email addresses to see if either of these get there. 
> 
> G
> --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Re: Ready for translation: Tech News #46 (2023)

[Nick Wilson (Quiddity)]

On Thu, Nov 9, 2023 at 3:53 PM Nick Wilson (Quiddity) 
wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/46
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F46=page
>

The text of the newsletter is now final.

*Two items have been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [go-cd] GOCD Version Upgrade Issue - Windows Agents Failing to Execute 'git pull'

[Chad Wilson]

It's possibly a side effect of fixing issues with spaces in windows
commands in GoCD 22.2.0:  https://www.gocd.org/releases.html#22-2-0

It may be that some of your command tasks were *technically* incorrectly
configured on earlier versions but worked as a side effect of these bugs in
GoCD, and GoCD is now stricter. Or it may be that there is a regression in
some circumstances.

Can you please
- share a screenshot of the UI pipeline task configuration for the 'git
pull' example above?
- find that specific task's XML definition inside admin > config XML and
share the XML fragment for the task or job (you can redact any sensitive
text, I am mainly interested in the 'shape' of the XML)

If my suspicion is correct, a workaround will certainly be possible to
correct the task config, but as there are a couple of historical ways tasks
could be configured, I'd like to understand what your config looked like
before you workaround the problem so I can see if this is avoidable.

-Chad


On Fri, 10 Nov 2023, 15:55 Sri Sai Sruthi JAGANNADDAM, <
sjagannad...@mdsol.com> wrote:

>  Could any one please help with this - I am writing to report a challenge
> we’ve encountered following our recent upgrade from GOCD version 21.2 to
> version 23.3. During our testing phase, we observed that certain pipelines,
> which execute on Windows agents, are failing with the following error when
> run through "Custom Command"
>
>  [go] Task: git pull
> Took: 0.179s
> Exited: 1
> '"git pull"' is not recognized as an internal or external command,
> operable program or batch file.
>
>
> This issue seems to be isolated to the Windows agents as the pipelines
> running on Linux agents are performing without any issues.
> The same pipelines were functioning correctly on the previous version of
> the GOCD server,
> which suggests a potential configuration or environment variable path
> discrepancy in the new version.
>
>
> --
> The information in this email and any attachments are intended solely for
> the recipient(s) to whom it is addressed, and may be confidential and/or
> privileged. Any unauthorized distribution or copying of this transmittal or
> its attachments is prohibited. If you are not a named recipient or have
> received this email in error: (i) you should not read, disclose, or copy
> it, (ii) please notify the sender of your receipt by reply email and delete
> this email and all attachments.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/08c6247d-e0c3-4d05-b449-e31c3b899e1dn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH_ky2xbJDscSAz%2BMvypJ_Zva_P-0_P%2BwtHPXc48CrgNVg%40mail.gmail.com.

[Translators-l] Ready for translation: Tech News #46 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/46

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F46=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: finding source of outdated dependencies

[Garret Wilson]

Ah! So, reading between the lines, you're recommending that I issue this 
command:


    mvn help:effective-pom -Dverbose=true

I didn't know there was a `verbose` option for the effective POM that 
had anything to do with dependency management. Thanks. That gives me 
effective dependency management, along with the POM it comes from—even 
with line numbers. Nice!


And (drumroll …) it looks like 
`biz.aQute.bnd:biz.aQute.bnd.annotation:6.4.1` is coming from 
`org.apache.logging:logging-parent:10.1.1`.


And `org.mockito:mockito-inline:4.8.1` was getting in because one of my 
own dependencies  hasn't been updated to use my newer root POM, which 
manages the versions of testing libraries. hehe It's good to find 
out—and now to know /how/ to find out.


Thanks, Tamás.

Garret

On 11/9/2023 5:25 PM, Tamás Cservenák wrote:

Well, depMgt is "flattened" (so if depMgt import of POM imports another POM
and ...), and if you use verbose with effective, you will see the source of
flattened things, at least

T

On Thu, Nov 9, 2023 at 9:18 PM Garret Wilson
wrote:


On 11/9/2023 5:10 PM, Tamás Cservenák wrote:

Howdy,

Did you try to take a peek at effective POM?

Hi. The effective POM doesn't show me anything helpful—and I don't know
that I expected it to. The effective POM simple resolves the inheritance
tree, right? I don't know if that would have any relationship to
transitive dependency management.


But also,https://issues.apache.org/jira/browse/MPH-183

So that seems to be a suggestion someone made to make the effective POM
show something about dependency management, but was never
finished/integrated?

Garret


On Thu, Nov 9, 2023 at 9:04 PM Garret Wilson
wrote:


In my Maven project (an aggregate project with child projects) I issue
the following command for the Versions Maven Plugin:

   mvn versions:display-dependency-updates

There are a couple of outdated dependencies I'm not sure where are
coming from:

[INFO] The following dependencies in Dependency Management have newer
versions:
[INFO]   biz.aQute.bnd:biz.aQute.bnd.annotation  6.4.1
-> 7.0.0
[INFO]   org.mockito:mockito-inline  4.8.1
-> 5.2.0

Unfortunately, try as I might, I can't find which library references
these. I've tried the following with the Maven Dependency Plugin, both
in the root project and in child projects:

   mvn dependency:tree

None of the output mentions `biz.aQute.bnd:biz.aQute.bnd.annotation` or
`org.mockito:mockito-inline`.

The two suspects are:

* `com.amazonaws:aws-lambda-java-log4j2:1.6.0` or
`org.apache.logging.log4j:log4j-bom:2.21.1` (for
`biz.aQute.bnd:biz.aQute.bnd.annotation`)
* `com.fasterxml.jackson:jackson-bom:2.15.3` (for
`org.mockito:mockito-inline`)

But those are just suspicions based upon the additional dependency
management I have in the subprojects where those outdated dependencies
show up.

Is there any command I can use to find out which dependency is bringing
in the outdated dependencies listed by the Versions Maven Plugin?

Thanks,

Garret


-
To unsubscribe,e-mail:users-unsubscr...@maven.apache.org
For additional commands,e-mail:users-h...@maven.apache.org

Re: finding source of outdated dependencies

[Garret Wilson]

On 11/9/2023 5:10 PM, Tamás Cservenák wrote:

Howdy,

Did you try to take a peek at effective POM?


Hi. The effective POM doesn't show me anything helpful—and I don't know 
that I expected it to. The effective POM simple resolves the inheritance 
tree, right? I don't know if that would have any relationship to 
transitive dependency management.



But also,https://issues.apache.org/jira/browse/MPH-183


So that seems to be a suggestion someone made to make the effective POM 
show something about dependency management, but was never 
finished/integrated?


Garret


On Thu, Nov 9, 2023 at 9:04 PM Garret Wilson
wrote:


In my Maven project (an aggregate project with child projects) I issue
the following command for the Versions Maven Plugin:

  mvn versions:display-dependency-updates

There are a couple of outdated dependencies I'm not sure where are
coming from:

[INFO] The following dependencies in Dependency Management have newer
versions:
[INFO]   biz.aQute.bnd:biz.aQute.bnd.annotation  6.4.1
-> 7.0.0
[INFO]   org.mockito:mockito-inline  4.8.1
-> 5.2.0

Unfortunately, try as I might, I can't find which library references
these. I've tried the following with the Maven Dependency Plugin, both
in the root project and in child projects:

  mvn dependency:tree

None of the output mentions `biz.aQute.bnd:biz.aQute.bnd.annotation` or
`org.mockito:mockito-inline`.

The two suspects are:

* `com.amazonaws:aws-lambda-java-log4j2:1.6.0` or
`org.apache.logging.log4j:log4j-bom:2.21.1` (for
`biz.aQute.bnd:biz.aQute.bnd.annotation`)
* `com.fasterxml.jackson:jackson-bom:2.15.3` (for
`org.mockito:mockito-inline`)

But those are just suspicions based upon the additional dependency
management I have in the subprojects where those outdated dependencies
show up.

Is there any command I can use to find out which dependency is bringing
in the outdated dependencies listed by the Versions Maven Plugin?

Thanks,

Garret


-
To unsubscribe, e-mail:users-unsubscr...@maven.apache.org
For additional commands, e-mail:users-h...@maven.apache.org

finding source of outdated dependencies

[Garret Wilson]

In my Maven project (an aggregate project with child projects) I issue 
the following command for the Versions Maven Plugin:


    mvn versions:display-dependency-updates

There are a couple of outdated dependencies I'm not sure where are 
coming from:


[INFO] The following dependencies in Dependency Management have newer 
versions:
[INFO]   biz.aQute.bnd:biz.aQute.bnd.annotation  6.4.1 
-> 7.0.0
[INFO]   org.mockito:mockito-inline  4.8.1 
-> 5.2.0


Unfortunately, try as I might, I can't find which library references 
these. I've tried the following with the Maven Dependency Plugin, both 
in the root project and in child projects:


    mvn dependency:tree

None of the output mentions `biz.aQute.bnd:biz.aQute.bnd.annotation` or 
`org.mockito:mockito-inline`.


The two suspects are:

* `com.amazonaws:aws-lambda-java-log4j2:1.6.0` or 
`org.apache.logging.log4j:log4j-bom:2.21.1` (for 
`biz.aQute.bnd:biz.aQute.bnd.annotation`)
* `com.fasterxml.jackson:jackson-bom:2.15.3` (for 
`org.mockito:mockito-inline`)


But those are just suspicions based upon the additional dependency 
management I have in the subprojects where those outdated dependencies 
show up.


Is there any command I can use to find out which dependency is bringing 
in the outdated dependencies listed by the Versions Maven Plugin?


Thanks,

Garret


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [SOGo] Question

["Simon Wilson"]

See https://bugs.sogo.nu/view.php?id=5793

There has been no visibility on progress to resolve since it was acknowledged 
in June.

Simon




On Monday, November 06, 2023 19:04 AEST, Mladen Knežević 
(mladen.kneze...@mtel.ba)  wrote:
  
 
Poslovno-POVJERLJIVO 
Hello there,


 
Is there any knowledge about the possible cause of the page below?

The correct page is rendered after the reload. 


 



 

 
Best Regards,

Mladen

 

S poštovanjem,
 
Mladen Knežević,
Glavni inženjer za eksploataciju i održavanje servisnog dijela ISP-a
 

Služba ISP
Funkcija eksploatacije i održavanja
Direkcija za tehniku
Mtel, a.d. Banja Luka
 
Vuka Karadžića 2 
78000 Banja Luka
Republika Srpska, BIH
 
Telefon: + 387 51 214 712
Fax:   + 387 51 222 730
E-mail: mladen.kneze...@mtel.ba
WEB:    www.mtel.ba
 
 
-- 
Simon Wilson
M: 0400 121 116

[Infrastructure] WordPress Instructions

[Ben Wilson via Infrastructure]

Today I started to edit the WordPress instructions for the website and
bring them up to date. (They're quite out-of-date.) I have provided a link
to them on the wiki -
https://wiki.cabforum.org/books/infrastructure/page/wordpress-instructions.
If you'd like to help me edit them and need "edit" access, then please let
me know.
Thanks,
Ben
___
Infrastructure mailing list
Infrastructure@cabforum.org
https://lists.cabforum.org/mailman/listinfo/infrastructure

Re: [go-cd] LDAP Group Authentication/Roles/Permissions

[Chad Wilson]

There are multiple LDAP plugins, so it depends which one you are referring
to. Sounds like you might want to look at
https://github.com/gocd/gocd-ldap-authorization-plugin rather than the
bundled 'authentication-only' version?

-Chad


On Thu, 9 Nov 2023, 05:33 Funkycybermonk,  wrote:

> Hello!
>
> I'm trying to manage a pool of users that is going to change over time and
> their permissions across multiple GoCD servers. (regional server split)
>
> I can add a group into permissions using the LDAP plugin, but it doesn't
> seem initially like the user permissions are inherited or managed by that
> group membership. Is it possible to do group based permissions from AD or
> does it have to be per-user?
>
> I'm trying to minimize work since we'll have to manually replicate the
> roles and permissions across several servers.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/4183dab6-4dad-4fd3-9055-01333843d0dbn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH8fUnhEOODV7im%2BVU_xkTfkTEDkmpvsz_bhmDGcLrfWJA%40mail.gmail.com.

Re: [go-cd] Where can I find the end-of-support documentation for GoCD releases?

[Chad Wilson]

Other than Ram's (accurate) comments about non-use of semantic versioning,
please see https://github.com/gocd/gocd/blob/master/SECURITY.md

Upgrading from 22.3.0 through to 23.3.0 or 23.4.0 is likely to be very low
risk/impact given the slow rate of change in GoCD over the last year.

-Chad

On Wed, 8 Nov 2023, 00:50 Satya Elipe,  wrote:

> Hi All
>
> We are currently on GoCD version 22.3.0 and wonder when is the right time
> to upgrade, so the documentation for end-of-support dates would be a help
> here, many thanks.
>
> Regards
> Satya
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CADKEDRr_8jWerqD8enn%2BcJP7AEVCAs%2BMQijXQ7%2BmZARqeV94YQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH_dqivHCgNH2LzXMwGLx0q_t3QhvU7Aei7hg-UmtNR7gQ%40mail.gmail.com.

[Commons-l] Re: Commons app - v4.2 release

[Wilson Oluoha]

Dear Sivaraam,

Thank you for the information.

I look forward to sharing feedback from my interaction with the new app.

Long overdue, I must say.

Best,

Wilson

On Mon, Nov 6, 2023 at 7:25 PM Kaartic Sivaraam 
wrote:

> Hi all,
>
> Hope you have been well! We have just released v4.2 of the Commons
> Android app to production. The update is now available on Play store [1]
> and F-droid [2]. You could also build the app directly from our GitHub
> repository [3].
>
> An important thing we wanted to communicate. We've changed the Mapbox
> API key used by the app in this release (v4.2.1) due to some unforeseen
> circumstances. We also had to revoke the old API key that is being used
> by the older version of the app (< v4.2.1).
>
> You might face issues with accessing maps in those versions of the app
> such as the Nearby screen appearing blank etc. We request your to kindly
> upgrade to v4.2.1 in order to continue using the features for which
> rendering a map is necessary. Other features should work fine. We regret
> the inconvenience that this may cause. Feel free to open an issue in our
> issue tracker [4] for any assistance. We'll be glad to help.
>
> This release also includes the done by Ritika Pahwa during GSoC 2023.
> This includes changes done to improve the reliability of the failed,
> stuck uploads and changes to prevent location metadata loss for uploads
> done via in the app.
>
> In case you've been facing issues with the uploads, do give the latest
> version a try. It should be better than before. Feel free to reach out
> to us with any feedback you may have. It would be very helpful.
>
> Other significant changes:
>
> - Dark mode colour improvements
>
> - Uploading via the in-app camera has been fixed and should work
>normally.
>
> - Provide the ability to edit an image to losslessly rotate it while
>uploading.
>
> - Category search now shows exact matches without any discrepancies
>
> - We've switched to using MapLibre instead of Mapbox and thereby
>disabled telemetry sent to Mapbox. We're also actively exploring
>alternatives to Mapbox so that we could completely move away from it.
>Check out the related issue [5] for information regarding the same.
>
> - Fix some redundant crash issues
>
> Checkout our changelog [6] for a more detailed set of changes since the
> last announcement.
>
> [[ References ]]
>
> [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons
> [2]: https://f-droid.org/en/packages/fr.free.nrw.commons
> [3]:
> https://github.com/commons-app/apps-android-commons/releases/tag/v4.2.1
> [4]: https://github.com/commons-app/apps-android-commons/issues
> [5]: https://github.com/commons-app/apps-android-commons/issues/5352
> [6]:
> https://github.com/commons-app/apps-android-commons/blob/main/CHANGELOG.md
>
>
> Best regards,
> Sivaraam (User:Kaartic)
> ___
> Commons-l mailing list -- commons-l@lists.wikimedia.org
> To unsubscribe send an email to commons-l-le...@lists.wikimedia.org
>
___
Commons-l mailing list -- commons-l@lists.wikimedia.org
To unsubscribe send an email to commons-l-le...@lists.wikimedia.org

Re: [grpc-io] gRPC client fallback from load-balancer to round robin DNS endpoint on LB outage

['Terry Wilson' via grpc.io]

Krishna,

I'll mention that we also have a short guide on custom LBs 
 that can help you with 
the fundamentals.

On Monday, November 6, 2023 at 3:53:01 PM UTC-8 Larry Safran wrote:

> Yes, you will need a custom NameResolver.  
> You could have your NameResolver do one of the following
> 1)  Extend DnsNameResolver (as is done by the internal GrpcNameResolver) 
> and override the doResolve method
> 2)  Directly extend NameResolver and have a field with a DnsNameResolver 
> created through the DnsNameResolverProvider (which should be gotten from 
> the registry).  
>
> There is already a load balancer that is switching between 2 child load 
> balancers.  It is experimental and can be specified as 
> "priority_experimental".  What it does is to use a specific attribute that 
> must be set by the NameResolver.  Even if you go with your own load 
> balancer, that would be the best way to differentiate which addresses 
> should be used for which child.  If you want to use it as an example, it is 
> https://github.com/grpc/grpc-java/blob/master/xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java
>
>
>
> On Mon, Nov 6, 2023 at 1:53 PM Krishna Sai Veera Reddy <
> krishnasaiv...@gmail.com> wrote:
>
>> Hey Larry,
>>
>> Thank you for your response! Are there any examples out in the wild on 
>> how to do this? Also the part that is confusing me is the name resolution. 
>> Do we have to add a custom name resolution policy as well so that we get 
>> both the LB and round robin IP addresses in `acceptResolvedAddresses 
>> `
>>  
>> method in the LB policy?
>>
>> On Friday, November 3, 2023 at 12:50:20 PM UTC-7 Larry Safran wrote:
>>
>>> This is a perfect scenario for a custom LB policy.  Since LB policies 
>>> form a tree, you could easily have your policy delegate to either a 
>>> PickFirst or RoundRobin policy depending on whether or not the LB is up.  
>>> Just have your policy define a ForwardingLoadbalanceHelper whose 
>>> updateBalancingState passes the picker from the oppropriate downstream 
>>> policy.
>>>
>>> On Fri, Nov 3, 2023 at 12:29 PM Krishna Sai Veera Reddy <
>>> krishnasaiv...@gmail.com> wrote:
>>>
 Hello All,

 I am working on a gRPC client that connects to a gRPC service fronted 
 by an LB but would like the client to automatically fallback to using 
 round-robin DNS to directly connect to the backend servers when the LB 
 goes 
 down. How do I go about this? Would I need to implement my own custom LB 
 policy? Any help is appreciated and thanks in advance!

 -- 
 You received this message because you are subscribed to the Google 
 Groups "grpc.io" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to grpc-io+u...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/grpc-io/df8f4a85-5020-4c68-bb94-cbea67d7c75an%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to grpc-io+u...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/grpc-io/2e7b95aa-cd66-40f5-bf41-0484fa12892cn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/51db24a6-3faa-4f9e-a979-54a0d5368921n%40googlegroups.com.

[Translators-l] Re: Ready for translation: Tech News #45 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 19 languages) to 1,098 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 45

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/45. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, العربية
, ไทย
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - In the Vector 2022 skin, the default font-size of a number of
   navigational elements (tagline, tools menu, navigational links, and more)
   has been increased slightly to match the font size used in page content.
   [1] 

*Problems*

   - Last week, there was a problem displaying some recent edits on a few
   wikis
   ,
   for 1-6 hours. The edits were saved but not immediately shown. This was due
   to a database problem. [2] 

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 7 November. It
   will be on non-Wikipedia wikis and some Wikipedias from 8 November. It will
   be on all wikis from 9 November (calendar
   ).
   - The Growth team will reassign newcomers from former mentors to the
   currently active mentors
   
.
   They have also changed the notification language to be more user-friendly.
   [3] [4]
   

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

Re: Public Discussion of D-Trust CA Inclusion Request

[Ben Wilson]

All,

Regarding the D-Trust Certification Practice Statement—instead of
referencing the D-Trust Root PKI CPS, it should have referenced the CPS of
the D-Trust CSM PKI, v.4.0, valid from 28-September-2023 (
https://www.d-trust.net/internet/files/D-TRUST_CSM_PKI_CPS.pdf) (from 19
July 2023, the CSM PKI CPS applies to certificates with policy levels
QEVCP-w, QNCP-w, EVCP, OVCP and LCP).

Also, it didn’t mention the following Bugzilla bugs opened in the past 24
months:

1756122 <https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>

D-TRUST: Wrong key usage (Key Agreement)
<https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>

RESOLVED

[dv-misissuance]

1793440 <https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>

D-TRUST: CRL not DER-encoded
<https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>

RESOLVED

[crl-failure]

1861069 <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>

D-Trust: Issuance of 15 DV certificates containing ‘serialNumber’ field
within subject <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>

OPEN

[dv-misissuance]

1862082 <https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>

D-Trust: Delay beyond 5 days in revoking misissued certificate
<https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>

OPEN

[leaf-revocation-delay]



Ben

On Fri, Nov 3, 2023 at 9:39 AM Ben Wilson  wrote:

> All,
>
> This email commences a six-week public discussion of D-Trust’s request to
> include the following CA certificates as publicly trusted root certificates
> in one or more CCADB Root Store Member’s program. This discussion period is
> scheduled to close on December 15, 2023.
>
> The purpose of this public discussion process is to promote openness and
> transparency. However, each Root Store makes its inclusion decisions
> independently, on its own timelines, and based on its own inclusion
> criteria. Successful completion of this public discussion process does not
> guarantee any favorable action by any root store.
>
> Anyone with concerns or questions is urged to raise them on this CCADB
> Public list by replying directly in this discussion thread. Likewise, a
> representative of the applicant must promptly respond directly in the
> discussion thread to all questions that are posted.
>
> CCADB Case Numbers:   # 1000
> <https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1000>
> and # 1001
> <https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1001>
>
> Organization Background Information (listed in CCADB):
>
>-
>
>CA Owner Name: D-Trust GmbH
>-
>
>Website:  https://www.d-trust.net/en
>-
>
>Address:  Kommandantenstr. 15, Berlin, 10969, Germany
>-
>
>Problem Reporting Mechanisms:
>-
>
>   https://www.d-trust.net/en/support/reporting-certificate-problem
>   -
>
>Organization Type: D-Trust GmbH is a subsidiary of the Bundesdruckerei
>Group GmbH (bdr) and is fully owned by the German State.
>-
>
>Repository URL:  https://www.bundesdruckerei.de/en/Repository
>
> Certificates Requested for Inclusion:
>
>1.
>
>D-Trust SBR Root CA 1 2022:
>-
>
>   384-bit ECC
>   -
>
>   Certificate download links: (CA Repository
>   <http://www.d-trust.net/cgi-bin/D-Trust_SBR_Root_CA_1_2022.crt>,
>   crt.sh
>   
> <https://crt.sh/?sha256=D92C171F5CF890BA428019292927FE22F3207FD2B54449CB6F675AF4922146E2>
>   )
>   -
>
>   Use cases served/EKUs:
>   -
>
>  Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
>  -
>
>  Client Authentication 1.3.6.1.5.5.7.3.2
>  -
>
>  Document Signing AATL 1.2.840.113583.1.1.5
>  -
>
>  Document Signing MS 1.3.6.1.4.1.311.10.3.12
>
>
>
>1.
>
>D-Trust SBR Root CA 2 2022:
>-
>
>   4096-bit RSA
>   -
>
>   Certificate download links: (CA Repository
>   <http://www.d-trust.net/cgi-bin/D-Trust_SBR_Root_CA_2_2022.crt>,
>   crt.sh
>   
> <https://crt.sh/?sha256=DBA84DD7EF622D485463A90137EA4D574DF8550928F6AFA03B4D8B1141E636CC>
>   )
>   -
>
>   Use cases served/EKUs:
>   -
>
>  Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
>  -
>
>  Client Authentication 1.3.6.1.5.5.7.3.2
>  -
>
>  Document Signing AATL 1.2.840.113583.1.1.5
>  -
>
>  Document Signing MS 1.3.6.1.4.1.311.10.3.12
>
> Relevant Policy and Practices Documentation:
>
>-
>
>Certificate Policy - CP of D-Trust GmbH
><https://www.d-trust.net/internet/files/D-TRUST_CP.pdf>, v.5.1, v

[Translators-l] Re: Ready for translation: Tech News #45 (2023)

[Nick Wilson (Quiddity)]

On Thu, Nov 2, 2023 at 4:44 PM Nick Wilson (Quiddity) 
wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/45
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F45=page
>

The text of the newsletter is now final.

*Two items have been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Public Discussion of D-Trust CA Inclusion Request

[Ben Wilson]

All,

This email commences a six-week public discussion of D-Trust’s request to
include the following CA certificates as publicly trusted root certificates
in one or more CCADB Root Store Member’s program. This discussion period is
scheduled to close on December 15, 2023.

The purpose of this public discussion process is to promote openness and
transparency. However, each Root Store makes its inclusion decisions
independently, on its own timelines, and based on its own inclusion
criteria. Successful completion of this public discussion process does not
guarantee any favorable action by any root store.

Anyone with concerns or questions is urged to raise them on this CCADB
Public list by replying directly in this discussion thread. Likewise, a
representative of the applicant must promptly respond directly in the
discussion thread to all questions that are posted.

CCADB Case Numbers:   # 1000

and # 1001


Organization Background Information (listed in CCADB):

   -

   CA Owner Name: D-Trust GmbH
   -

   Website:  https://www.d-trust.net/en
   -

   Address:  Kommandantenstr. 15, Berlin, 10969, Germany
   -

   Problem Reporting Mechanisms:
   -

  https://www.d-trust.net/en/support/reporting-certificate-problem
  -

   Organization Type: D-Trust GmbH is a subsidiary of the Bundesdruckerei
   Group GmbH (bdr) and is fully owned by the German State.
   -

   Repository URL:  https://www.bundesdruckerei.de/en/Repository

Certificates Requested for Inclusion:

   1.

   D-Trust SBR Root CA 1 2022:
   -

  384-bit ECC
  -

  Certificate download links: (CA Repository
  ,
  crt.sh
  

  )
  -

  Use cases served/EKUs:
  -

 Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
 -

 Client Authentication 1.3.6.1.5.5.7.3.2
 -

 Document Signing AATL 1.2.840.113583.1.1.5
 -

 Document Signing MS 1.3.6.1.4.1.311.10.3.12



   1.

   D-Trust SBR Root CA 2 2022:
   -

  4096-bit RSA
  -

  Certificate download links: (CA Repository
  ,
  crt.sh
  

  )
  -

  Use cases served/EKUs:
  -

 Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
 -

 Client Authentication 1.3.6.1.5.5.7.3.2
 -

 Document Signing AATL 1.2.840.113583.1.1.5
 -

 Document Signing MS 1.3.6.1.4.1.311.10.3.12

Relevant Policy and Practices Documentation:

   -

   Certificate Policy - CP of D-Trust GmbH
   , v.5.1, valid
   from 28-Sept-2023
   -

   Trust Services Practice Statement - TSPS of D-Trust
   , v.1.8, valid
   from 28-Sept-2023
   -

   Certification Practice Statement - CPS of the D-Trust Root PKI
   ,
   v.3.10, valid from 31-May-2023

Most Recent Self-Assessment / CPS Review:

   -

   D-Trust - CCADB Self Assessment (v1.2) 2023
    (XLS)
   (2-November-2023)

Audit Statements:

   -

   Auditor: TÜV Informationstechnik GmbH
   -

   Audit Criteria:
   -

  ETSI EN 319 411-1, V1.3.1 (2021-05)
  -

  ETSI EN 319 401, V2.3.1 (2021-05)
  -

  Baseline Requirements, version 1.8.4
  -

  ETSI EN 319 403 V2.2.2 (2015-08)
  -

  ETSI TS 119 403-2 V1.2.4 (2020-11)
  -

   Date of Audit Issuance: December 16, 2022
   -

   For Period of Time: 2022-07-06 to 2022-10-07
   -

   Audit Statement(s):
   -


  
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121606_D-Trust_SBR_Root_CA_1_2022.pdf
  -


  
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121607_D-Trust_SBR_Root_CA_2_2022.pdf


Thank you,

Ben, on behalf of the CCADB Steering Committee

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaZes1TUd8UefomNVXxXMn%3DamoGjQ95226zJZUuHPPZ%2BgQ%40mail.gmail.com.

Bug#1055262: inetutils-telnetd: inetutils daemon packages should have systemd as a dependency

[Neil Wilson]

Package: inetutils-telnetd
Version: 2:2.4-3
Severity: wishlist
Tags: patch
X-Debbugs-Cc: n...@aldur.co.uk

Dear Maintainer,

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-3-cloud-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages inetutils-telnetd depends on:
ii  inetutils-inetd [inet-superserver] 2:2.4-3
ii  inetutils-syslogd [system-log-daemon]  2:2.4-3
ii  libc6  2.37-12
ii  libcom-err21.47.0-2+b1
ii  libk5crypto3   1.20.1-5
ii  libkrb5-3  1.20.1-5
ii  libtinfo6  6.4+20231016-1
ii  netbase6.4

inetutils-telnetd recommends no packages.

inetutils-telnetd suggests no packages.

-- no debconf information

telnetd (and the other inetutils packages) depend upon the inet-superserver and 
system-log-daemon, which is too
tight a dependency on a system with systemd installed. The dependency should be 
loosened to include a systemd alternative.

The daemons can be run directly from systemd with two systemd unit files, which 
should be included in each package.

The telnet example is below. The other daemons use the same pattern. 

telnetd.socket

[Unit]
Description=Telnet per-connection server
Before=sockets.target

[Socket]
ListenStream=23
Accept=yes

[Install]
WantedBy=sockets.target


telnetd@.service

[Unit]
Description=Telnet server
Documentation=man:telnetd(8)

[Service]
StandardInput=socket
User=root
ExecStart=-/usr/sbin/telnetd

[Translators-l] Ready for translation: Tech News #45 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/45

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F45=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Announcing the formation Wiki Club Jamia

[Wilson Oluoha]

Congratulations Aafi.

It's nice how you are keeping the global community updated.

Cheers!

Wilson

On Thu, Nov 2, 2023 at 12:53 PM Wikimedia Community Ireland <
wikimediairel...@gmail.com> wrote:

> Congratulations and welcome to the Wikimedia Family!
>
> Shannon Eichelberger
> Chair-Wikimedia Community Ireland
>
> On Wed, 1 Nov 2023 at 13:11, pavan santhosh 
> wrote:
>
>> Dear Aafi,
>>
>> I wanted to extend my congratulations on the establishment of "Wiki Club
>> Jamia" at Jamia Millia Islamia University. This initiative promises to
>> further the efforts in engaging students in the Wikimedia Movement.
>>
>> I wish Wiki Club Jamia all the best in its endeavours.
>>
>> Best regards,
>> Pavan.
>>
>>
>> On Wed, Nov 1, 2023 at 6:04 PM The Aafi  wrote:
>>
>>> Hello everyone,
>>>
>>> I am thrilled to announce the formation of "Wiki Club Jamia", an
>>> extra-curricular club at Jamia Millia Islamia University, in New Delhi,
>>> India. The club aims to engage the varsity's students in global knowledge
>>> through the Wikimedia movement.
>>>
>>> This club has been formed as a part of the Deoband Community Wikimedia
>>> <https://meta.wikimedia.org/wiki/Deoband_Community_Wikimedia>'s
>>> Leadership Development and Skills Infrastructure Program and a total of
>>> seventeen students and research scholars are credited as its founders.
>>>
>>> The Chenab Times has covered this. Please take a look at the news piece
>>> <https://thechenabtimes.com/2023/10/31/students-establish-wiki-club-at-jamia-millia-islamia-university/>
>>>  and
>>> find the Meta-Wiki page here
>>> <https://meta.wikimedia.org/wiki/Wiki_Club_Jamia>.
>>>
>>> Best regards
>>> Aafi
>>> ___
>>> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
>>> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>>> https://meta.wikimedia.org/wiki/Wikimedia-l
>>> Public archives at
>>> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/PXKULM6LZ4F2YVT3IARXGI55YHVKU5J7/
>>> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>>
>>
>>
>> --
>> Pavan Santhosh.
>> ___
>> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
>> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> Public archives at
>> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MLKE7FA7E2G6AFPBR6XAXX6MKPM53YZ6/
>> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
>
>
> --
> --
> Wikimedia Community Ireland
> Chair - Shannon Eichelberger
>
> Online: Wikimedia Community Ireland <http://wikimedia.ie>
> On Twitter: @WikimediaIE <https://twitter.com/WikimediaIE>
> On Facebook: Wikimedia Ireland <https://www.facebook.com/WikimediaIreland>
> On Instagram: wikimediaie <https://www.instagram.com/wikimediaie/>
> On Meetup: Wikimedia Community Ireland Meetup
> <https://www.meetup.com/Wikimedia-Community-Ireland-Meetup/>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/5RRN422TGEVT3MJLGRQKBKYOGA57XYCW/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/IUX5K2LOY3LWRXBIGYZAKM5BWTOSDUWK/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[go-cd] Release Announcement - 23.4.0

[Chad Wilson]

Hello everyone,

A new release of GoCD  (23.4.0) is
out.

This release is mainly a maintenance release. As always, please remember to
take a backup before upgrading.

Special thanks to Victor Sollerhed (MPV) and k-c-p for helping us debug a
(likely) rather old bug reported in various guises over time, which can
lead to server configuration values being toggled unexpectedly on a GoCD
restart. Hopefully we've nailed it this time!

To know more about the features and bug fixes in this release, see the release
notes  or head to the downloads page
 to try it. Feedback and ideas are always
welcome - we appreciate the discussion on issues you are having, and how we
can improve things.

Cheers,
Chad & Aravind

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH9Ho%3D%3D_7XO8PM_2hh4o9ZrAmePpdr3SjyaxHnZq5assUg%40mail.gmail.com.

Re: [Smcwg-public] VOTE FOR APPROVAL Ballot SMC04: Addition of ETSI TS 119 411-6 to audit standards

[Ben Wilson via Smcwg-public]

Mozilla votes "Yes" on Ballot SMC 004 (Addition of ETSI TS 119 411-6).

On Wed, Nov 1, 2023 at 11:07 AM Stephen Davidson via Smcwg-public <
smcwg-public@cabforum.org> wrote:

> Hello:
>
>
>
> The voting period for Ballot SMC04 has started. Votes must be cast on the
> SMCWG public list and in accordance with the Charter and By-Laws.
>
> Voting on SMC04 concludes on 08 November 2023 at 17:00 UTC.
>
>
>
> Regards, Stephen
>
>
>
>
>
> *Ballot SMC04: Addition of ETSI TS 119 411-6 to audit standards*
>
>
>
> *Purpose of Ballot:*
>
>
>
> The ballot proposes changes to the S/MIME Baseline Requirements, and in
> others to make corrections.  The affected sections include:
>
>
>
>- Clarify the Revisions table in section 1.2.1 to more clearly
>differentiate the effective date (publication of the version) from
>additional compliance dates; and
>- Add ETSI TS 119 411-6 as an audit criteria in Sections 1.6.3, 8.4,
>and 8.6.
>
>
>
> The following motion has been proposed by Stephen Davidson of DigiCert and
> endorsed by Dimitris Zacharopoulos of HARICA and Paul van Brouwershaven of
> Entrust.
>
>
>
> *— MOTION BEGINS —*
>
>
>
> This ballot modifies the “Baseline Requirements for the Issuance and
> Management of Publicly-Trusted S/MIME Certificates” (“S/MIME Baseline
> Requirements”) resulting in Version 1.0.2.
>
>
>
> The proposed modifications to the S/MIME Baseline Requirements may be
> found at
>
>
> https://github.com/cabforum/smime/compare/241e92cde85c25d7e0d4a5c70118ecadacd4d72b...c6916c7156a711b59f8e6790ff0ee0fedb7bd270
> 
> .
>
>
>
> The SMCWG Chair or Vice-Chair is permitted to update the Relevant Dates
> and Version Number of the S/MIME Baseline Requirements to reflect final
> dates.
>
>
>
> *— MOTION ENDS —*
>
>
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
>
>
>
> Discussion (7 days)
>
> Start Time: October 25, 2023 17:00 UTC
>
> End Time: November 1, 2023 17:00 UTC
>
>
>
> Vote for approval (7 days)
>
> Start Time: November 1, 2023 17:00 UTC
>
> End Time: November 8, 2023 17:00 UTC
>
>
>
>
> ___
> Smcwg-public mailing list
> Smcwg-public@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/smcwg-public
>
___
Smcwg-public mailing list
Smcwg-public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/smcwg-public

[Translators-l] Re: Ready for translation: Tech News #44 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 19 languages) to 1,096 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 44

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/44. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, বাংলা
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - The Structured Content team, as part of its project of improving
   UploadWizard on Commons
   
,
   made some UX improvements to the upload step of choosing own vs not own
   work (T347590 ), as well as
   to the licensing step for own work (T347756
   ).
   - The Design Systems team has released version 1.0.0 of Codex
   , the new design system for
   Wikimedia. See the full announcement about the release of Codex 1.0.0
   

   .

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 31 October. It
   will be on non-Wikipedia wikis and some Wikipedias from 1 November. It will
   be on all wikis from 2 November (calendar
   ).
   - Listings on category pages are sorted on each wiki for that language
   using a library
   .
   For a brief period on 2 November, changes to categories will not be sorted
   correctly for many languages. This is because the developers are upgrading
   to a new version of the library. They will then use a script to fix the
   existing categories. This will take a few hours or a few days depending on
   how big the wiki is. You can read more
   
.
   [1] [2]
   
   - Starting November 1, the impact module (Special:Impact) will be
   upgraded by the Growth team. The new impact module shows newcomers more
   data regarding their impact on the wiki. It was tested by a few wikis
   during the last few months. [3]
   

*Future changes*

   - There is a proposed plan
   

   for re-enabling the Graph Extension. You can help by reviewing this
   proposal and sharing what you think about it
   

   .
   - The WMF is working on making it possible for administrators to edit
   MediaWiki configuration directly
   
.
   This is similar to previous work on Special:EditGrowthConfig. A
   technical RfC 

Re: [cabfpub] Ballot FORUM-019 - Amend Server Certificate Working Group Charter - Discussion Period

[Ben Wilson via Public]

Thanks, Tobias.
I'll take a look at your suggestions and see if I can work in a few
revisions, and then we can restart the discussion period.
Ben

On Thu, Oct 26, 2023 at 12:30 PM Tobias S. Josefowitz 
wrote:

> Hi Ben,
>
> On Mon, 23 Oct 2023, Ben Wilson wrote:
>
> > *Ballot FORUM-019:  Amend Server Certificate Working Group Charter*
> >
> > *Purpose of the Ballot*
> >
> > This ballot proposes changes to the Server Certificate Working Group
> (SCWG)
> > Charter, based on existing version 1.2 of the Charter and on recent
> updates
> > to the Forum's Bylaws.
> >
> > During discussions at Face-to-Face Meeting 58, it was noted that the
> > membership criteria for Certificate Consumers in the SCWG Charter lacked
> > sufficient detail. Since then, through discussions on the mailing list of
> > the SCWG, better criteria for membership of Certificate Consumers in the
> > SCWG have been developed, and the ballot also adds a 6-month probationary
> > period for all applicants to the SCWG before they become voting members.
> >
> > *Motion Begins*
> >
> > MODIFY the Charter of the Server Certificate Working Group as specified
> in
> > the following redline:
> >
> >
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce?f029c48cfd8a53ca563904835d6bd5d4b41fa4c8
> >
> > *Motion Ends*
>
> My biggest concern with this Ballot is the language in 4. (d), which
> introduces the limitation of "upon the request of any Member that
> challenges the Applicant's adherence to all of the requirements of section
> 3(a) or 3(b)" for requesting the membership to be decided by a vote.
>
> I recognize that we have members that interpret the current mechanism of
> deciding membership by vote "upon the request of any Member" to only
> result in a vote about the applicant meeting the formal membership
> criteria. Understandably, from that perspective, adding pretty much any
> sensible requirement to the list of formal membership criteria for
> Certificate Consumer members is obviously beneficial and without any
> downsides.
>
> As someone who does not share that perspective but maintains that the
> current "upon the request of any Member" mechanism results in a vote in
> which members can apply a level of discretion which allows at least e.g.
> refusing membership to applicants who's membership (if granted) might
> substantially erode trust into the WebPKI ecosystem or endanger the SCWG's
> ability to maintain and produce documents that are incorporated into root
> program policies in a mostly verbatim fashion, the new language is
> extremely concerning.
>
> When taking into account that the new set of requirements for Certificate
> Consumers can indeed still be trivially met by even a single individual
> with a few hours of time on their hands (unless, maybe, "software product
> intended for use by the general public for browsing the Web securely"
> somehow will turn into a requirement that will not be considered to be
> trivially fulfilled), the new language in my opinion becomes
> disqualifying. I hope that this change to the mechanism can be reverted
> until we have a set of formal membership criteria for Certificate
> Consumers that makes such discretion obsolete.
>
> In addition, I have some minor concerns regarding the new formal
> membership criteria for Certificate Consumers in 3.(b). In particular, for
> the sake of the argument, I assume a browser that generally uses the OS
> root store as a base mechanism (potentially with the ability to exclude
> specific certificates that might be included in the OS root store). It is
> my understanding that for example Google Chrome has worked like this until
> somewhat recently, which to me kind of implies that it ought to be
> considered an acceptable practice for SCWG Certificate Consumer Member
> qualifying software products in good standing. From our discussion during
> the F2F #60 (I am not sure if this was in the SCWG or Forum plenary) I
> understand that you intend
>
>"its membership-qualifying software product uses a list of CA
>certificates to validate the chain of trust from a TLS certificate to a
>CA certificate in such list"
>
> to cover that case. However, such a software as described would indeed use
> different lists on different platforms. We could consider the specific
> version for one platform to be the "membership qualifying software", but
> that does not seem elegant, and might come into conflict with "for the
> general public" in a strict interpretation.
>
> In such a case, it would also be problematic to
>
>"pu

[African Wikimedians] [WLA][REMINDER] Notification of Deadline for Rapid Grants Applications

[Wilson Oluoha]

Dear Wikimedians,

This email is to notify you that the deadline for applying for a rapid
grant for the purpose of organizing Wiki Loves Africa 2024 is *1st November
2023*.

You are encouraged to complete your applications (for those who need a
rapid grant) and submit on or before the above mentioned deadline. We would
also be grateful if you list out details of your community on the participants
page here
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities#Participating_communities_in_2024>
.

The Theme for the 2024 contest is *Africa Create* and will commence in
March 2024.

Kindly email *wil...@wikiinafrica.org * if you
have any questions or need any information and/or assistance.

Best regards




-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [WLA][RAPPEL] Notification de la date limite de pour demander une rapide subvention pour le concours 2024

[Wilson Oluoha]

 Chers Wikimédiens,

Cet e-mail a pour vous informer que la date limite de dépôt des demandes de
subvention rapide pour l'organisation de Wiki Loves Africa 2024 est fixée
au *1er novembre 2023*.

Nous vous encourageons à compléter vos demandes (pour ceux qui ont besoin
d'une subvention rapide) et à les soumettre au plus tard à la date limite
mentionnée ci-dessus. Nous vous serions également reconnaissants d'indiquer
les détails de votre communauté sur la page des participants ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities#Participating_communities_in_2024>
.

Le thème du concours 2024 est *Africa Create* et débutera en mars 2024.

N'hésitez pas à envoyer un courriel à *wil...@wikiinafrica.org
* si vous avez des questions ou si vous avez
besoin d'informations et/ou d'assistance.

Cordialment




-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

[Chad Wilson]

Thanks for sharing. Sounds like it could be a network policy thing or
something like that? Did you double check the cluster profile config to see
if anything is amiss there?

I can't see why you'd get a different error message with 23.1.0 (and the
same plugin version) unless there was something different about the cluster
profile config (API server url etc), so that might be an avenue for
investigation?

-Chad

On Sat, 28 Oct 2023, 05:16 Kim Pham,  wrote:

> Hi,
>
> I just wanted to give an update.  We're still unsure what's preventing
> agents from spinning up on our old cluster.  The pods aren't getting
> created at all and there's no logs in Kubernetes side indicating activity.
> I've tried with a regular Debian agent and the logs are the same.  I did
> roll back to GoCD 23.1.0 to see what the log output was and it's showing a
> SocketTimeoutException error.  We're still investigating but it's possible
> some configuration changed that we're not aware of with that cluster.
>
> I was able to spin up a new cluster and it works fine there.  That cluster
> is running:
>
>- GoCD Server: 23.3.0
>- GoCD DinD Agent: 23.3.0
>- Elastic Agent Node Pools: 1.25.10-gk3.2700
>
> I'll update if there's anything relevant to share.  Thanks for all the
> help!
>
> On Thu, Oct 26, 2023 at 10:55 AM Kim Pham  wrote:
>
>> Hi Chad,
>>
>> I was just reading up on the changes for Kubernetes.  Looks 1.24 moves to
>> containerd runtime images and we are still using DIND for our elastic
>> agents.  That seems like it could be the culprit.  I'll do some testing and
>> change our elastic agent images.  Thanks for pointing that out.
>>
>> On Thu, Oct 26, 2023 at 10:46 AM Chad Wilson 
>> wrote:
>>
>>> Unfortunately the error message is a bit mysterious and useless. Which
>>> agent image you are using? Anything special in the elastic agent pod spec
>>> that might no longer work as expected on Kubernetes 1.24? (e.g use of
>>> docker dind images)
>>>
>>> Does the pod get created (and fail) if you look at the events on the
>>> kubernetes side, or does it never get that far?
>>>
>>> -Chad
>>>
>>> On Thu, Oct 26, 2023 at 11:37 PM Chad Wilson 
>>> wrote:
>>>
>>>> Just curious - were the errors/stack traces on failure essentially
>>>> identical before and after you upgraded your gocd and elastic agent plugin
>>>> versions?
>>>>
>>>> On Thu, Oct 26, 2023 at 11:33 PM Kim Pham  wrote:
>>>>
>>>>> Hi Ashwanth,
>>>>>
>>>>> I checked the clusterrole of the service account it's using and it
>>>>> basically has full access atm.
>>>>>
>>>>> PolicyRule:
>>>>>   Resources   Non-Resource URLs  Resource Names  Verbs
>>>>>   -   -  --  -
>>>>>   events  [] []  [*]
>>>>>   namespaces  [] []  [*]
>>>>>   nodes   [] []  [*]
>>>>>   pods/log[] []  [*]
>>>>>   pods[] []  [*]
>>>>>
>>>>> On Thu, Oct 26, 2023 at 10:21 AM 'Ashwanth Kumar' via go-cd <
>>>>> go-cd@googlegroups.com> wrote:
>>>>>
>>>>>> A wild guess, anything changed on the service account side or a
>>>>>> custom role being added as part of the upgrade that is probably not
>>>>>> allowing the gocd plugin to create the pod?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>> On Thu, 26 Oct 2023 at 20:27, Kim Pham  wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> We recently began to encounter issues where pods were unable to be
>>>>>>> created.  Nothing has changed in terms of GoCD server, agent, and
>>>>>>> Kubernetes elastic agent plugin versions.  However, we did notice that 
>>>>>>> the
>>>>>>> cluster went through an automatic upgrade and updated gke version to
>>>>>>> 1.24.14.  GoCD is able to see the node pools through the 'Status Report'
>>>>>>> button.
>>>>>>>
>>>>>>> When attempting to create an agent on those node pools, I do see a
>>>>>>> 500 in the plugin logs and gocd-server logs.  Attached are logs.
>>>>