Re: More thoughts on threads...

Yo Hal! On Wed, 16 Dec 2020 20:21:55 -0800 Hal Murray via devel wrote: > But maybe I'm fooling myself. Are people comfortable with threads > and locks? (I've been working with them since 1976.) In theory: vey much yes. In practice: the devil is in the details. RGDS GARY -

Re: Blizard of mail from GitLab-Abuse-Automation

Yo Richard! On Wed, 16 Dec 2020 22:37:19 -0600 Richard Laager via devel wrote: > I got a response from GitLab's (presumably first-level support) on > the ticket I filed earlier: No response to my complaints? > "I see you're being affected by our @GitLab-Abuse-Automation bot. > This could be re

Re: Blizard of mail from GitLab-Abuse-Automation

I got a response from GitLab's (presumably first-level support) on the ticket I filed earlier: "I see you're being affected by our @GitLab-Abuse-Automation bot. This could be related to Content Violation. I'm raising this internally and we will get back to you soon." The first part, at least

More thoughts on threads...

I'm still scheming on this topic. Here is what I'd like to end up with: N server threads, each with their own socket listening on UDP 123 a client thread for each server we are using (with own socket) a thread for each refclock the main thread for whatever is left Getting there is a lot

Re: Blizard of mail from GitLab-Abuse-Automation

The project audit settings in the GitLab UI show: Author Object Action Target IP Address Date GitLab-Abuse-Automation NTPsec/ntpsec Changed visibility from Public to Private NTPsec/ntpsec 35.223.150.201 2

Re: Blizard of mail from GitLab-Abuse-Automation

Sanjeev Gupta via devel : > Ah, so not my fault. > > I tried updating my fork about 11 hours ago, and was to authenticate to > pull from the NTPsec git repo. I tried with another repo, it worked, so I > assumed one of us was modifying the security settings of the repo. Somwething either very spec

Fw: GitLab | Projects forced to "Private" (#294196)

Yo All! I opened GitLab issue #29419Y6. See blow. Only 34,000+ open isues in the queue ahead of me... Anyone have a contact at GitLab?? RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703

Re: Blizard of mail from GitLab-Abuse-Automation

Yo Sanjeev! On Thu, 17 Dec 2020 09:52:48 +0800 Sanjeev Gupta via devel wrote: > Ah, so not my fault. > > I tried updating my fork about 11 hours ago, and was to authenticate > to pull from the NTPsec git repo. I tried with another repo, it > worked, so I assumed one of us was modifying the secu

Re: Blizard of mail from GitLab-Abuse-Automation

On Wed, Dec 16, 2020, at 5:53 PM Sanjeev Gupta wrote: > Ah, so not my fault. > > I tried updating my fork about 11 hours ago, and was to authenticate to > pull from the NTPsec git repo. I tried with another repo, it worked, so I > assumed one of us was modifying the security settings of the repo.

Re: Blizard of mail from GitLab-Abuse-Automation

Ah, so not my fault. I tried updating my fork about 11 hours ago, and was to authenticate to pull from the NTPsec git repo. I tried with another repo, it worked, so I assumed one of us was modifying the security settings of the repo. On Thu, 17 Dec 2020, 7:38 am James Browning via devel, wrote:

Re: Blizard of mail from GitLab-Abuse-Automation

Thanks. I added that to the GitLab ticket. Maybe that will help them get to the bottom of it. No response from them yet. On 12/16/20 5:38 PM, James Browning via devel wrote: After looking at it a little more it appears that something temporarily disconnected several forked projects and during t

Re: Blizard of mail from GitLab-Abuse-Automation

On Wed, Dec 16, 2020 at 12:40 PM Richard Laager via devel wrote: > GitLab Abuse folks: > > A user (bot?) named @GitLab-Abuse-Automation closed a bunch of > legitimate NTPsec merge requests: > > > :::snip list of merge requests::: > > > Worse, I (@rlaager) seem to be unable to reopen the MRs, so

Re: Blizard of mail from GitLab-Abuse-Automation

GitLab Abuse folks: A user (bot?) named @GitLab-Abuse-Automation closed a bunch of legitimate NTPsec merge requests: https://gitlab.com/NTPsec/www/-/merge_requests/33 https://gitlab.com/NTPsec/www/-/merge_requests/42 https://gitlab.com/NTPsec/www/-/merge_requests/63 https://gitlab.com/NTPsec/n

Re: Blizard of mail from GitLab-Abuse-Automation

On Wed, Dec 16, 2020, 10:06 AM Hal Murray via devel wrote: > > Can somebody tell me/us what happened? Why? ... > My guess is that GitLab deployed a new bot and it (probably) somewhat overzealously closed almost all of the merge requests. > ___ devel

Blizard of mail from GitLab-Abuse-Automation

Can somebody tell me/us what happened? Why? ... -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel