- Boost - lists.boost.org

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Gavin Lambert 04 May '23

04 May '23

On 4/05/2023 18:34, Julien Blanc wrote: > You're luckier than me. The current thread is semi-broken, but the > "replacing the ML with a forum" one is completely broken for me. Sorry, that was sloppy reporting on my part. There was a large tree of posts that were all together so I foolishly assumed that this was the whole thread. There were *also* a bunch of disconnected replies earlier on, but since these were completely disconnected they didn't "follow" the parent higher in the list since I'm sorting by date. This meant they were out of sight at the time I was thinking about this and writing my message. > I'm starting to wonder if we all receive the same emails (in the sense > that they may not contain the same set of headers). For me, the initial > message of Vinnie in the "replacing the ML with a forum" thread contains > the following: > > Message-ID: > <010f0187bde5599a-e76c27f2-225d-4d7e-b2c8-887e3a07ecb8-000000(a)us-east-2.amazonses.com> > > But Mashshall's answer, on the other side, contains the following headers : > > References: > <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> > In-Reply-To: > <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> > > The "In-Reply-To" should match the Id of the initial message, for > threading to work correctly. This is too obvious to be a client bug. Can > someone check the Message-ID he has for the initial message of Vinnie in > the "replacing the ML with a forum" thread? If it's different from mine, > then that's probably the source of the issues. For me (via gmane), Vinnie's original message has: Message-ID: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000(a)us-east-2.amazonses.com> And Marshall's reply (did not thread properly) has: Message-ID: <010f0187bde8bc2e-bebb94d1-2dfb-4165-ad8d-6af8e9b41381-000000(a)us-east-2.amazonses.com> References: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> In-Reply-To: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> Robert's reply (did thread properly) has: Message-ID: <010f0187bf4b951d-1f6d7af8-3f2e-458b-9ffd-ca91ecfe04f9-000000(a)us-east-2.amazonses.com> References: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000(a)us-east-2.amazonses.com> In-Reply-To: <010f0187bde523cc-f60c3688-3843-44d4-b848-f37b2fd6a598-000000(a)us-east-2.amazonses.com> These do indeed seem to be different from yours, which is unfortunate. It would be good if someone else not using gmane could check both results as well (although that shouldn't be a factor, as I have other groups that don't appear to be getting flattening). The threads that are semi-flat appear to be because it did match one of the References but not all of them. For example, in this thread, your reply was: Message-ID: <010f0187e5785f8e-23fd3577-ced2-4f4a-a235-6b7a24d0022c-000000(a)us-east-2.amazonses.com> References: <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000000(a)us-east-2.amazonses.com> <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000000(a)us-east-2.amazonses.com> <010f0187e09fef87-f959fd75-f882-47dc-b20c-f103c943383d-000000(a)us-east-2.amazonses.com> <010f0187e141f8b1-75bb05d0-8b61-4190-af34-2efb57ce70df-000000(a)us-east-2.amazonses.com> <CANEqPjFF80D2dp5pAZfo1aF7YHt73_cs5wFgENNZ40_piTZnvA(a)mail.gmail.com> <010f0187e2536549-44ef0b67-13ba-420a-8c95-50e5212ccbf5-000000(a)us-east-2.amazonses.com> <010f0187e400f951-96bb316d-68ca-4d38-a08a-6f9cfb56ec78-000000(a)us-east-2.amazonses.com> In-Reply-To: <010f0187e400f951-96bb316d-68ca-4d38-a08a-6f9cfb56ec78-000000(a)us-east-2.amazonses.com> Replying to my message: Message-ID: <010f0187e400b04d-bdb05955-7e9a-4aae-b4f5-cde46033a981-000000(a)us-east-2.amazonses.com> References: <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000000(a)us-east-2.amazonses.com> <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000000(a)us-east-2.amazonses.com> <010f0187e09fef87-f959fd75-f882-47dc-b20c-f103c943383d-000000(a)us-east-2.amazonses.com> <010f0187e141f8b1-75bb05d0-8b61-4190-af34-2efb57ce70df-000000(a)us-east-2.amazonses.com> <CANEqPjFF80D2dp5pAZfo1aF7YHt73_cs5wFgENNZ40_piTZnvA(a)mail.gmail.com> <010f0187e2536549-44ef0b67-13ba-420a-8c95-50e5212ccbf5-000000(a)us-east-2.amazonses.com> In-Reply-To: <010f0187e2536549-44ef0b67-13ba-420a-8c95-50e5212ccbf5-000000(a)us-east-2.amazonses.com> Which was a reply to Andrey's: Message-ID: <010f0187e2536549-44ef0b67-13ba-420a-8c95-50e5212ccbf5-000000(a)us-east-2.amazonses.com> References: <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000000(a)us-east-2.amazonses.com> <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000000(a)us-east-2.amazonses.com> <010f0187e09fef87-f959fd75-f882-47dc-b20c-f103c943383d-000000(a)us-east-2.amazonses.com> <010f0187e141f8b1-75bb05d0-8b61-4190-af34-2efb57ce70df-000000(a)us-east-2.amazonses.com> <CANEqPjFF80D2dp5pAZfo1aF7YHt73_cs5wFgENNZ40_piTZnvA(a)mail.gmail.com> In-Reply-To: <CANEqPjFF80D2dp5pAZfo1aF7YHt73_cs5wFgENNZ40_piTZnvA(a)mail.gmail.com> And yet I'm seeing both my message and your reply to it as siblings under Andrey's, because you appear to have a different id for my message than I do.

1 0

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Julien Blanc 04 May '23

04 May '23

Le 2023-05-04 01:44, Gavin Lambert via Boost a écrit : > This is what I'm seeing -- note that the current thread appears > semi-flat (even though most of these sibling messages were actually a > reply chain), but the "replacing the ML with a forum" thread appears > mostly normal. > https://imgur.com/a/GfTS6ig You're luckier than me. The current thread is semi-broken, but the "replacing the ML with a forum" one is completely broken for me. I'm starting to wonder if we all receive the same emails (in the sense that they may not contain the same set of headers). For me, the initial message of Vinnie in the "replacing the ML with a forum" thread contains the following: Message-ID: <010f0187bde5599a-e76c27f2-225d-4d7e-b2c8-887e3a07ecb8-000000(a)us-east-2.amazonses.com> But Mashshall's answer, on the other side, contains the following headers : References: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> In-Reply-To: <010f0187bde530fb-ff3c1911-df7d-4399-b5d2-82f8062bf18c-000000(a)us-east-2.amazonses.com> The "In-Reply-To" should match the Id of the initial message, for threading to work correctly. This is too obvious to be a client bug. Can someone check the Message-ID he has for the initial message of Vinnie in the "replacing the ML with a forum" thread? If it's different from mine, then that's probably the source of the issues. Regards, Julien

1 0

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Gavin Lambert 03 May '23

03 May '23

On 4/05/2023 03:55, Andrey Semashev wrote: > The fact that the initial message is not part of the thread now is a > relatively recent issue. This is the mailman archive from a year ago: > > https://lists.boost.org/Archives/boost/2022/04/index.php > > Threading is fine there. In fact, threading was working correctly as > recently as in February 2023: > > https://lists.boost.org/Archives/boost/2023/02/index.php > > and has been broken in March: > > https://lists.boost.org/Archives/boost/2023/03/index.php > > If the system works (and worked) the way you describe, mailman was able > to associate the initial message with the thread before and now it > isn't. I suspect, this may have something to do with the headers that > are added by SES to the messages it sends to the subscribers. Threading only sometimes works in the gmane view as well. Usually it's not the mailing list itself at fault, but due to the mail client used by the person posting -- or sometimes that they're replying to a digest rather than the original mail, so the context headers are lost (even if they edit it to look like it was a reply to a single post). I have noticed an apparent increase recently in the number of posts that appear "flat" or semi-flat (still showing as a reply, but to a grandparent post rather than the real parent post) -- but other recent threads still do appear normally nested, so I don't think it's a systemic issue. This is what I'm seeing -- note that the current thread appears semi-flat (even though most of these sibling messages were actually a reply chain), but the "replacing the ML with a forum" thread appears mostly normal. https://imgur.com/a/GfTS6ig

1 0

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Sam Darwin 03 May '23

03 May '23

Amazon SES is a basic SMTP gateway service. It has fewer features and options than mailgun. Incoming and outgoing mail are handled differently. When emails are sent out from the mailman server, they are proxied through SES. Only verified identities may send mail. Notice the sender says "boost(a)lists.boost.org", since lists.boost.org is a verified domain that is working, otherwise it would be blocked. Incoming emails go directly to mailman, not through any intermediary. SES is not involved with incoming emails to the mail server. This is the same situation as before. - Are emails being sent out? Almost certainly all the emails are being sent as shown by the mail logs on the mail server, and on SES it says "0.01% bounce rate", which is very good. - Is threading working? checking lists.boost.org, messages are organized into threads. However, it may be that threading is only partially correct. If that is what you are reporting. There are only a few settings exposed in the gateway to be able to adjust. One of them which hasn't been added yet is "Custom MAIL FROM domain", that could be modified from the default of amazonses.com to "a subdomain of lists.boost.org". As an experiment, I will set that today, and observe if it helps. Mailgun has been in production for many years. It costs $500 per month to send smtp messages. It's a reasonable idea to try out another service that's only 5% of the cost. But at the same time, it's not impossible to switch back to mailgun, if threading is partially disrupted, and we can't find a solution. On Wed, May 3, 2023 at 4:56 AM Andrey Semashev via Boost <boost(a)lists.boost.org> wrote: > > On 5/3/23 10:59, Julien Blanc via Boost wrote: > > Le 2023-05-02 15:25, David Sankel via Boost a écrit : > >> I wanted to call out Sam Darwin's work on this: > >> > >>> Transitioned boost mailing list gateway from mailgun to Amazon SES > >> > >> This transition has resulted in a $575 per month cost reduction in Boost > >> Foundation hosting expenses. Sam did an excellent job here. > > > > Did that happen around end of february / start of march? I've noticed > > that threaded view was broken around that date (and still is). At first, > > i blamed my client (evolution) but i see the same issue with another > > (roundcube). > > > > A quick look at mail headers seems to show wrong values in the > > References: header (but that is far beyond my expertise). > > I can see the threaded view is indeed broken in the mailman archive, for > example see here: > > https://lists.boost.org/Archives/boost/2023/04/index.php > > You can see the initial post is not grouped with the following thread. > > I should also mention that I was not totally correct when I said I don't > use threaded view when I read Boost ML. On my mobile email app that I > forgot about, I do use threaded view, and I did notice that some > messages were not grouped with the rest of the discussion. It didn't > occur to me until now whether those messages were the initial ones in > the discussion, but it may have been so. > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by David Sankel 03 May '23

03 May '23

I wanted to call out Sam Darwin's work on this: > Transitioned boost mailing list gateway from mailgun to Amazon SES This transition has resulted in a $575 per month cost reduction in Boost Foundation hosting expenses. Sam did an excellent job here. Thanks Sam and C++ Alliance for this valuable work! David Boost Foundation

2 1

Re: [boost] Boost CI Infrastructure
by Boris Kolpackov 03 May '23

03 May '23

Vinnie Falco via Boost <boost(a)lists.boost.org> writes: > I guess what I'm trying to say here is that we care deeply about long > turnaround times on CI ("they suck) have been working on the problem. This email may give an impression that the CI suckage is an inherent problem that one just has to live with so I want to provide a different perspective. As part of the build2 project we have implemented our own CI infrastructure from the grounds up: from managing our own hardware, to VM-based CI job handling, to custom web interface for result viewing. This was based on concluding that all the existing off- the-shelf solutions are primarily focused on "web development" and will result in the subpar experience for large C/C++ projects (Boost, Qt, etc). Some key differences of our approach compared to the commonly used setups (e.g., GitHub Actions): 1. "Push CI" explicitly triggered during development as opposed to "pull CI" triggered on commit/PR/etc. This allows specifying the target configurations to build in, alternative project configurations, etc.[1] 2. Standard "CI script"[2] that is used by all the C/C++ projects instead of each projects doing their own thing. This "CI script" is written in C++ and has evolved to cover a fairly elaborate set of scenarios, including: 1. Testing of preparation of source distributions (to make sure there are no missing files, etc). 2. Testing of libraries as installed (to make sure no public headers were omitted during installation, etc). 3. Ability to test projects with build-time dependencies (e.g., source code generators, build system modules, etc) in cross- compiled environments. 3. Interactive CI support. The push CI can request an interactive session where the above "CI script" is stopped at one of the pre-defined breakpoints allowing the user to login into the machine via VNC or SSH and investigate the problem. 4. Large number of build configurations covering all the major platforms/compilers/versions[3] with a well-defined obsolescence policy. To give a sense of how this works in practice, here is my typical workflow: 1. Hack on some feature in a branch, build and test locally. 2. When need to test on other platforms, push the branch to remote and submit the CI request. Normally it's just: $ bdep ci The result is a URL with the interface like this: https://ci.stage.build2.org/@04e5ffb7-cf96-42f9-bc91-94d3ffe48de1 One nice touch is that it detects compiler warnings, as can be seen in this result: https://ci.stage.build2.org/@23da340d-cb4d-4105-8474-bb870e1a1380 (Drop the UUID from the above URL to see some other CI jobs.) 3. Say everything works fine except on Windows with an old MSVC version. If the fix is clear, I push it and re-CI but just on this specific configuration (this is both faster for me and saves resources for others): $ bdep ci --build-config windows_10-msvc_14.3 If the fix is not clear and I need to play with it or run the debugger, I can request an interactive CI session: $ bdep ci --interactive windows_10-msvc_14.3/error That `/error` part is a breakpoint, meaning that the CI job will execute the standard "CI script" until the first error (compile error, test failure, etc) and pause. 4. Once all is good I clean up my feature branch (squash commits, etc), rebase on master, CI one more time for good measure, and merge to master. When I push my changes to master, there can be a hook that submits a "verification" CI job. [1] https://build2.org/bdep/doc/bdep-ci.xhtml [2] https://build2.org/bbot/doc/build2-build-bot-manual.xhtml#arch-worker [3] https://ci.cppget.org/?build-configs

1 0

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Andrey Semashev 03 May '23

03 May '23

On 5/3/23 10:59, Julien Blanc via Boost wrote: > Le 2023-05-02 15:25, David Sankel via Boost a écrit : >> I wanted to call out Sam Darwin's work on this: >> >>> Transitioned boost mailing list gateway from mailgun to Amazon SES >> >> This transition has resulted in a $575 per month cost reduction in Boost >> Foundation hosting expenses. Sam did an excellent job here. > > Did that happen around end of february / start of march? I've noticed > that threaded view was broken around that date (and still is). At first, > i blamed my client (evolution) but i see the same issue with another > (roundcube). > > A quick look at mail headers seems to show wrong values in the > References: header (but that is far beyond my expertise). I can see the threaded view is indeed broken in the mailman archive, for example see here: https://lists.boost.org/Archives/boost/2023/04/index.php You can see the initial post is not grouped with the following thread. I should also mention that I was not totally correct when I said I don't use threaded view when I read Boost ML. On my mobile email app that I forgot about, I do use threaded view, and I did notice that some messages were not grouped with the rest of the discussion. It didn't occur to me until now whether those messages were the initial ones in the discussion, but it may have been so.

1 0

Re: [boost] Mailing Lists For The Win!
by Hans Dembinski 03 May '23

03 May '23

> On 2. May 2023, at 17:52, Vinnie Falco via Boost <boost(a)lists.boost.org> wrote: > > This will take additional time so it probably won't make it into the > initial cut of the website, but we will at least be showing read-only > archives for now. And the mailing list will remain as-is, forever. This sounds like a pretty neat solution. I like the mailing list to participate in the communication, but I don't like to browse the ML archive to dig up old conversations. I think that's going to be easier with the forum. Hans

1 0

Re: [boost] Q1 2023 Update: C++ Alliance's Efforts (PDF Attached)
by Julien Blanc 03 May '23

03 May '23

Le 2023-05-02 15:25, David Sankel via Boost a écrit : > I wanted to call out Sam Darwin's work on this: > >> Transitioned boost mailing list gateway from mailgun to Amazon SES > > This transition has resulted in a $575 per month cost reduction in > Boost > Foundation hosting expenses. Sam did an excellent job here. Did that happen around end of february / start of march? I've noticed that threaded view was broken around that date (and still is). At first, i blamed my client (evolution) but i see the same issue with another (roundcube). A quick look at mail headers seems to show wrong values in the References: header (but that is far beyond my expertise). > Thanks Sam and C++ Alliance for this valuable work! Yes, thanks for all this invisible work. Julien

1 0

Re: [boost] Replacing the ML with a forum
by Dominique Devienne 02 May '23

02 May '23

On Mon, May 1, 2023 at 8:15 AM Vinnie Falco via Boost <boost(a)lists.boost.org> wrote: > On Sun, Apr 30, 2023 at 8:56 PM Rainer Deyke via Boost > <boost(a)lists.boost.org> wrote: > > The SDL mailing list moved from true mailing list on gmane to Discourse > > web forum with email notification (but no gmane) a while back > > Good thing that's not happening to Boost > I've already mentioned it, but I feel compelled to re-iterate, given the lets-built-it direction, although I know it's most likely in vein. SQLite made the transition from ML to a custom-built Forum, and it went/was OK. I and several others were against it. In the end, the community survived and thrived. I've used Discord in the past. I've used Basecamp. I've used News (Google Reader, RIP). And of course I've used MLs too, these ones included. [The Fossil Forums][1] are low-key, fast, i.e. good enough. And very low resources on the backend. The Forums integrate with [Pikchr][2] for text-based diagramming. Email notification is implemented, but replies by emails are not. You don't need to use Fossil SCM to use them. Many people use Fossil just for the Forums. Unlike SQLite, Fossil is open to contributions too, although the community is opinionated. I have no stake in Fossil. I'm just a happy user. FWIW. --DD [1]: https://www.fossil-scm.org/home/doc/trunk/www/forum.wiki [2]: https://fossil-scm.org/home/doc/trunk/www/pikchr.md

2 1