Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #88841
| From | Spiros Bousbouras <spibou@gmail.com> |
|---|---|
| Newsgroups | comp.lang.c++, news.admin.net-abuse.usenet |
| Subject | Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) |
| Date | 2023-01-25 22:58 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <CalGwGYMri+TaoE2w@bongo-ra.co> (permalink) |
| References | (16 earlier) <z8dmrhuM9xNk7FY=M@bongo-ra.co> <730105qr-2qrs-oo6q-30r7-p3o6r8p793p4@zvaqfcevat.pbz> <tqoluk$5cht$2@dont-email.me> <B1jyOFXZ9kwyO2oB1@bongo-ra.co> <tqpcje$8v5p$3@dont-email.me> |
Cross-posted to 2 groups.
On Tue, 24 Jan 2023 20:46:54 +0100
David Brown <david.brown@hesbynett.no> wrote:
> On 24/01/2023 18:47, Spiros Bousbouras wrote:
> > All 3 of you use Thunderbird. Not precisely the same version but close. I assume
> > you have tried to reproduce the steps which originally led you to see the defective
> > post and you can no longer reproduce them.
> >
>
> You are correct that we all use Thunderbird, and it is definitely
> something I considered. More relevantly, however, we all use
> news.eternal-september.org. And I have just tested using a clean
> installation of pan as an alternative newsreader, and seen exactly the
> same effect.
>
> I don't know why you think I can no longer reproduce the effect of the
> broken post - I have made no such suggestion, precisely because I /can/
> replicate it. I still see it on two different computers with
> Thunderbird, and now also with Pan.
I thought so because it is one of the first things you should have mentioned
in the very first post you talked about a server glitch. You are a technical
person , you *know* that for bugs , glitches , etc. one ideally should
mention precise steps which would allow one to reproduce the problem. So I
can't imagine what you were thinking in failing to do so. It couldn't have
been for lack of time because you posted some very long responses which were
light on technical content but made no mention whatsoever of the very
important fact that you could consistently reproduce the problem. In fact ,
in at least 4 posts you said "a server fault" or something analogous without
mentioning that there was one specific server on which you saw the issue. I
was actually wondering what the hell was happening and you weren't giving
specifics.
> For convenience, I have taken a screenshot of the effect. I have not
> used this site "paste.pics" before, and I apologise if there are
> unwanted adverts or other effects. If you are sceptical of clicking the
> link, then I can happily email the screenshot. But it seems a quick and
> easy way to make a link to the screenshot.
>
> <https://paste.pics/b4149f38abb4e210da0a71886714d014>
This isn't very helpful and in particular it doesn't help to distinguish
whether it's a server issue or a Thunderbird issue. Just because Thunderbird
threads posts in a certain way or puts some post under a certain group ,
does not imply that the server has the same view of things. Perhaps Thunderbird
received correct responses from the server and messed things up. Below I will
give 2 precise ways to reproduce the problem which clearly show that it's an
eternal-september issue. Before doing so I will note that when you want to
talk about the date of a message it is best to quote the following 2 lines from
the header
Date: Thu, 19 Jan 2023 01:42:00 -0800 (PST)
Injection-Date: Thu, 19 Jan 2023 09:42:01 +0000
instead of saying for example (from <tqoluk$5cht$2@dont-email.me>)
"timestamp 19.01.2023, 10:31" .If Thunderbird does not allow you to see the
header exactly as it received it from the server then it's no good for
diagnosing issues.
For both of the following methods one must have an eternal-september account
since this is the server which displays the issue.
Method 1
You need to have the lynx text based browser installed. You do
lynx news://news.eternal-september.org/comp.lang.c++/137660-137665
.This asks lynx to contact news.eternal-september.org and fetch article
numbers 137660-137665 from the group comp.lang.c++ .Note that article
numbers are server and group specific , a different server might not have
articles with such numbers or they might refer to different posts. But the
important point here is that whatever posts the server returns , they must
have been posted to comp.lang.c++ , possibly among other groups. The first
post you will see is
Newsgroups: rec.arts.books
Date: Thu, 19 Jan 2023 01:42:00 -0800 (PST)
Message-ID: <36403165-3cf1-4b73-8ad1-da339b960339n@googlegroups.com>
Subject: Change and Choice
From: Ilya Shambat <ibshambat@gmail.com>
.Note that it was not (cross)posted on comp.lang.c++ so it should have
never been returned. The last post you will see in the above list is
=====
From: Bonita Montero <Bonita.Montero@gmail.com>
Newsgroups: rec.arts.books,comp.lang.c++
Subject: Re: Compute Unique Numbers in a Set
Date: Thu, 19 Jan 2023 15:42:54 +0100
Message-ID: <tqbkrr$1ja1c$1@dont-email.me>
References: <36403165-3cf1-4b73-8ad1-da339b960339n@googlegroups.com>
[...]
Are you the twin-brother of Amine Moulay Ramdane ?
Am 19.01.2023 um 10:31 schrieb Muttley@dastardlyhq.com:
[...]
=====
.This correctly appears in the response by the server since it was crossposted
on comp.lang.c++ .
Method 2
You have to run a Python script which I will give below. It runs on Python
2.5 .Yes it's an old version but it's the only one I have handy and I haven't
bothered to learn Python 3.whatever .But the script should run on the newest
Python with little or no modifications. You run the script with
python path-to-script username password
where username and password are the ones you have for eternal-september .
The script will append its output to file /tmp/server-glitch-2 .
==== Script starts on the next line
import os
import string
import sys
import nntplib
import datetime
class TerminateError(Exception) :
def __init__(self , message) :
self.mes = message
def __str__(self) : return self.mes
def terminate(*args) :
global util_name
mes = util_name + " :"
for a in args :
mes = mes + " " + str(a)
raise TerminateError(mes)
util_name = "server-glitch"
server = "news.eternal-september.org"
separ = '\n@@@ \n\n'
port = 119
if len(sys.argv) != 3 :
terminate("2 arguments required : username and password")
username = sys.argv[1]
password = sys.argv[2]
fnobj = open("/tmp/server-glitch-2" , "a")
now = datetime.datetime.now()
fnobj.write("Starting at " + now.strftime("%Y-%m-%d %H:%M:%S %z") + '\n\n')
try :
connection = nntplib.NNTP(server , port , username , password)
response = connection.group("comp.lang.c++")
fnobj.write("Response choosing comp.lang.c++ was\n\n" + str(response) + "\n\n")
response , overviews = connection.xover("137660" , "137665")
fnobj.write("Response asking for range of articles was\n\n" +
str(response) + "\n\n")
for art in overviews :
fnobj.write("Article number " + str(art[0]) + " :\n")
fnobj.write(str(art[1]) + "\n\n")
for art in overviews :
response , number , id , content = connection.article(str(art[0]))
if id == '<36403165-3cf1-4b73-8ad1-da339b960339n@googlegroups.com>' or \
id == '<tqbkrr$1ja1c$1@dont-email.me>' :
fnobj.write("Printing article number " + str(art[0]) + " :\n\n")
for l in content :
fnobj.write(l + '\n')
fnobj.write(separ)
else :
fnobj.write("Skipping article with id\n " + id + separ)
connection.quit()
except nntplib.NNTPError,exception :
terminate("NNTP error\n" , "Exception was\n" , exception)
now = datetime.datetime.now()
fnobj.write("Terminating at " + now.strftime("%Y-%m-%d %H:%M:%S %z") +
'\n\n =======\n\n')
fnobj.close
====
The important points are the following :
server = "news.eternal-september.org"
connection = nntplib.NNTP(server , port , username , password)
response = connection.group("comp.lang.c++")
It connects to eternal-september and goes to comp.lang.c++ .
response , overviews = connection.xover("137660" , "137665")
Asks for list of articles from 137660 to 137665 , same numbers as with
lynx above.
Then it goes through the articles one by one and puts in
/tmp/server-glitch-2 the articles with IDs
<36403165-3cf1-4b73-8ad1-da339b960339n@googlegroups.com> and
<tqbkrr$1ja1c$1@dont-email.me> .It puts the articles exactly as it receives
them from the header. Again you will see that the Shambat article has
Newsgroups: rec.arts.books
so it should not have appeared under comp.lang.c++ regardless of what
range of articles we asked for.
--
Technology is dominated by two types of people: those who understand
what they do not manage, and those who manage what they do not
understand.
Putt's law
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Compute Unique Numbers in a Set Bonita Montero <Bonita.Montero@gmail.com> - 2023-01-19 15:42 +0100
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-19 16:18 +0100
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:32 +0000
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-19 19:22 +0100
Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:00 +0000
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-20 15:48 +0000
Re: Compute Unique Numbers in a Set Richard Harnden <richard.nospam@gmail.com> - 2023-01-25 13:00 +0000
Re: Compute Unique Numbers in a Set James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:52 -0500
Re: Compute Unique Numbers in a Set Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-25 14:13 -0800
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-26 00:03 +0100
Re: Compute Unique Numbers in a Set ikook <iKook@GMAIL.COM> - 2023-01-25 23:17 +0000
Re: Compute Unique Numbers in a Set scott@slp53.sl.home (Scott Lurndal) - 2023-01-25 23:37 +0000
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-26 09:19 +0100
Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-26 00:09 +0000
Re: Compute Unique Numbers in a Set James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 23:55 -0500
Re: Compute Unique Numbers in a Set Öö Tiib <ootiib@hot.ee> - 2023-01-19 08:40 -0800
Re: Compute Unique Numbers in a Set red floyd <no.spam.here@its.invalid> - 2023-01-19 08:42 -0800
Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:10 +0000
Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-19 20:17 +0000
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-20 15:49 +0000
Re: Compute Unique Numbers in a Set Spiros Bousbouras <spibou@gmail.com> - 2023-01-20 17:21 +0000
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-21 15:50 +0000
Re: Compute Unique Numbers in a Set "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2023-01-20 11:35 -0800
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-21 13:06 +0100
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-21 15:56 +0000
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-22 13:33 +0100
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-23 09:34 +0000
Re: Compute Unique Numbers in a Set David Brown <david.brown@hesbynett.no> - 2023-01-23 14:29 +0100
Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 14:21 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-23 13:03 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 20:06 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-23 14:46 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-23 22:00 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 14:20 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 15:36 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-01-24 08:06 -0800
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 18:30 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 18:50 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:36 +0100
Re: Server glitch vs other possibilities "Adam H. Kerman" <ahk@chinet.com> - 2023-01-24 19:50 +0000
Re: Server glitch vs other possibilities Marc SCHAEFER <schaefer@alphanet.ch> - 2023-01-24 19:56 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:31 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-01-24 20:07 -0800
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-25 05:02 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-24 17:47 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-24 13:30 -0500
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:42 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-24 20:46 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) scott@slp53.sl.home (Scott Lurndal) - 2023-01-24 19:56 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Manu Raju <MR@invalid.invalid> - 2023-01-24 22:00 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-25 00:00 +0100
Re: Server glitch vs other possibilities snipeco.2@gmail.com (Sn!pe) - 2023-01-25 00:17 +0000
Re: Server glitch vs other possibilities David Brown <david.brown@hesbynett.no> - 2023-01-25 09:43 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-25 10:39 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 14:51 -0500
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 00:00 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-25 23:49 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 09:23 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 02:27 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 23:55 -0500
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 18:22 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 09:44 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Öö Tiib <ootiib@hot.ee> - 2023-01-26 01:40 -0800
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 13:14 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) iKook <iKook@gmail.com> - 2023-01-26 18:13 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-27 22:12 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-28 13:20 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 20:20 -0800
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:00 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) gazelle@shell.xmission.com (Kenny McCormack) - 2023-01-29 12:01 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Daniel <danielaparker@gmail.com> - 2023-01-29 16:23 -0800
[OT] Writing IMHO Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-01-30 01:14 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Spiros Bousbouras <spibou@gmail.com> - 2023-01-25 22:58 +0000
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-26 13:10 +0100
Thunderbird Broken Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 19:54 -0800
Re: Thunderbird Broken Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:04 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:30 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Ritz <dritz@mindspring.com> - 2023-01-24 20:25 -0600
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-01-25 00:10 -0500
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-25 10:56 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) Pluted Pup <plutedpup@outlook.com> - 2023-01-28 19:28 -0800
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) David Brown <david.brown@hesbynett.no> - 2023-01-29 12:36 +0100
Pluted Pup is trolling you, you blithering idiot (was: Server glitch vs other possibilities) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-29 17:23 +0000
Re: Pluted Pup is trolling you, you blithering idiot (was: Server glitch vs other possibilities) David Brown <david.brown@hesbynett.no> - 2023-01-30 08:22 +0100
Re: Server glitch vs other possibilities (Was : Compute Unique Numbers in a Set) "Adam H. Kerman" <ahk@chinet.com> - 2023-01-23 22:18 +0000
Re: Compute Unique Numbers in a Set Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2023-01-19 17:08 +0000
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 17:15 +0000
Re: Compute Unique Numbers in a Set gazelle@shell.xmission.com (Kenny McCormack) - 2023-01-19 16:54 +0000
Re: Compute Unique Numbers in a Set Pluted Pup <plutedpup@outlook.com> - 2023-01-21 13:03 -0800
Re: Compute Unique Numbers in a Set Pluted Pup <plutedpup@outlook.com> - 2023-01-21 14:01 -0800
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:30 +0000
Re: Compute Unique Numbers in a Set Muttley@dastardlyhq.com - 2023-01-19 16:48 +0000
csiph-web