Re: [Boost-users] Issues with boost executor_work_guard

On Mon, Apr 7, 2025 at 7:07 AM João Fernando Silva via Boost-users < boost-users@lists.boost.org> wrote: > ...despite the work_guard still being valid, we see that the threads exit > because boost::asio::detail::scheduler::outstanding_work reaches 0. > If you could create a small, self-contained

Re: [Boost-users] boost::json question

On Tue, Feb 11, 2025 at 12:05 PM Keeling, William via Boost-users < boost-users@lists.boost.org> wrote: > Any ideas what I am doing wrong? > What version of Boost are you using? Thanks ___ Boost-users mailing list Boost-users@lists.boost.org https://li

[Boost-users] [boost] Boost.LEAF in Embedded Systems (CppCon)

At CppCon 2024 the C++ Alliance sponsored a program to interview conference goers about Boost-related topics. This is the first video in the series: Boost.LEAF in Embedded Systems: Insights from Ex-Google Engineer Khalil Estelle at CppCon https://www.youtube.com/shorts/BksBxnTLltY Enjoy! Thanks

Re: [Boost-users] Boost.Asio UDP sockets guarantee for ordering

On Tue, Sep 17, 2024 at 6:59 AM Kalesis, Ioannis via Boost-users wrote: > The point that I need help understanding is whether there is a guarantee on > the order of the packets being enqueued to kernels network stack. There are no portable guarantees. > Is there any possible way for “packet2” t

Re: [Boost-users] [release] Boost.1.86.0

On Fri, Aug 16, 2024 at 1:08 AM Dominique Devienne via Boost-users < boost-users@lists.boost.org> wrote: > If wanting to improve Boost communication, then please have > a good description of what's in the GitHub release, and/or a link > to a blog post Bun-like with full details. My $0.02. --DD >

Re: [Boost-users] [release] Boost.1.86.0

On Wed, Aug 14, 2024 at 10:17 AM Marshall Clow via Boost-users wrote: > Release 1.86.0 of the Boost C++ Libraries is now available. With some attention, Boost's image could be exciting and relevant to younger engineers. To enhance the libraries' social media presence, our digital artist creates a

Re: [Boost-users] coroutine condition_variable

On Wed, Dec 6, 2023 at 6:19 AM Keith Bennett via Boost-users < boost-users@lists.boost.org> wrote: > "If only there was something like that" sounds snarky to me and doesn't > answer the question at all. > You are right about that but honestly it is irresistible for me to go for the obvious punchl

Re: [Boost-users] coroutine condition_variable

On Tue, Dec 5, 2023 at 5:43 PM Keith Bennett via Boost-users < boost-users@lists.boost.org> wrote: > One of the things that keeps cropping up in the ability to notify another > function that something has finished. > So... "call a function to indicate something has finished?" If only there was so

Re: [Boost-users] JSON and no-alloc

On Mon, Aug 14, 2023 at 11:46 AM Marc Oscar Singer via Boost-users < boost-users@lists.boost.org> wrote: > I'm targeting the boost JSON library for an embedded target. There > appears to be one place where there could be either a beneficial new > feature, or the feature exists and I'm not seeing

[Boost-users] Full-Text Search is LIVE!

Greetings. I am proud to announce that Mohammad’s excellent work on implementing a full-text search which looks into all the Boost libraries and their documentation is now complete, and has been published to the live website. You can access the search by pressing the Search button in the top right

Re: [Boost-users] [asio] monitoring io_context load

On Mon, Jul 3, 2023 at 6:00 AM Dmitry wrote: > > What you are asking for is more or less possible, but what do you plan on > > doing with this information? > ... > Thanks for asking! After thinking more about the metric, it does not seem > helpful anymore. I would be careful using the informat

Re: [Boost-users] [asio] monitoring io_context load

On Fri, Jun 30, 2023 at 7:31 AM Dmitry wrote: > I would like to measure io_context load before it became overloaded to > estimate capacity. What you are asking for is more or less possible, but what do you plan on doing with this information? ___ Boost

Re: [Boost-users] [asio] monitoring io_context load

On Fri, Jun 30, 2023 at 6:58 AM Dmitry via Boost-users wrote: > I would like to have a metric that measures time spent for > work (executing completion handlers) vs time spent waiting > for work in thread pool executing io_context::run(). Maybe there are some ideas here? https://github.com/XRPLF

Re: [Boost-users] New Website !

On Thu, May 11, 2023 at 8:08 AM Damien via Boost-users wrote: > This looks really good. Congratulations to the team. Thank you very much for the kind words! Regards ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailma

[Boost-users] New Website !

Hey, it’s Vinnie here again! I have some very exciting news to share with you. The renovated website for Boost that we’ve been working on for far too long is now going into its Public Beta phase! Feel free to poke around and kick the tires but keep in mind this is a piece of software and it is stil

Re: [Boost-users] [iostreams] When plan to move to C++20

On Thu, Feb 9, 2023 at 7:35 AM Seyyed Soroosh Hosseinalipour via Boost-users wrote: > I think iostreams library have very more clean if using modern C++ features, > such as Concept Functionally speaking, what would change for users? Would their programs behave differently? Would the API change?

Re: [Boost-users] [release] Boost 1.81.0

On Wed, Dec 14, 2022 at 10:37 AM Marshall Clow via Boost-users wrote: > Release 1.81.0 of the Boost C++ Libraries is now available. Please Like, Follow, and Amplify our social media presence!

Re: [Boost-users] Boost support for Arm64/Windows

On Fri, Aug 12, 2022 at 3:16 PM Jonathon Penix via Boost-users wrote: > I am interested in using Boost as a dependency on the Arm64/Windows platform Boost.URL (soon to be reviewed, starting August 13th if you would like to participate) is tested on ARM64. Boost.JSON (which IS part of Boost) shou

Re: [Boost-users] C++11 or C++14?

On Sun, Jul 24, 2022 at 10:09 AM Vinnie Falco wrote: > I'm considering bumping up the C++ language requirement for Boost.URL > from C++11 to C++14. So, here is some fantastic news. My motivation for raising the language requirement in Boost.URL was for better support for constexpr, as I wanted to

[Boost-users] C++11 or C++14?

I'm considering bumping up the C++ language requirement for Boost.URL from C++11 to C++14. I have concerns about doing this, because it affects all my downstream libraries (HTTP.Proto, HTTP.IO, Websocket.Proto, Websocket.IO, and any examples or complete clients/servers that I write). My main fear

Re: [Boost-users] Boost.URL review planned for 13-22 August 2022

On Fri, Jun 24, 2022 at 2:15 AM Mateusz Loskot via Boost-users wrote: > we have planned the review shortly after the upcoming release of the Boost > 1.80. The review starts in August but there is no rule that says folks can't look at the library sooner :) The library is in very good shape and li

Re: [Boost-users] [boost] Boost Twitter is Blowing Up!!!

On Tue, Jun 21, 2022 at 10:59 AM Bo Persson via Boost wrote: > Isn't the rule that when the seniors see a platform as mature enough to > actually register and use it, the juniors have already desiced that it > is un-cool and have moved somewhere else? Twitter solves the problem of "how do I disco

[Boost-users] [JSON] Vote for Boost.JSON in this poll!

There's an online poll asking about which JSON library you use. If you use Boost.JSON consider voting for it: Also, consider voting for it if you _don't_ use Boost.JSON, but you want to. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinnie

Re: [Boost-users] Boost Twitter is Blowing Up!!!

On Tue, Jun 21, 2022 at 7:40 AM John McCabe via Boost-users wrote: > Younger generations are using TikTok, Instagram and Discord as far as I > can see. My late teen/early 20s kids rarely touch Twitter unless someone > on TikTok has posted a link! I'm talking about the younger generations of C++ e

Re: [Boost-users] Boost Twitter is Blowing Up!!!

On Mon, Jun 20, 2022 at 7:48 PM 😉 Good Guy 😉 via Boost-users wrote: > The problem with Twitter is that it requires an account to read the posts. Yeah, so... my assumption when I made this post is that most folks have a Twitter account. I see that is not the case, even for long-time Boost authors.

[Boost-users] Boost Twitter is Blowing Up!!!

Greetings fellow users, library authors, maintainers, review wizards, release wizards, and Boost Foundation Board members! As part of our ongoing effort to continue the revitalization of Boost, a handful of us have taken the reins to post about Boost on social media. We have postings on Reddit and

Re: [Boost-users] Any objections to making C++14 the current baseline for Boost support and testing?

On Fri, May 6, 2022 at 1:20 AM John Maddock via Boost-users wrote: > Does anyone have any concrete objections to Boost moving to a C++14 baseline? Yes. If any of Boost.Beast's dependencies requires C++14, then Beast will require C++14. I am not quite ready to force half of Beast's existing userba

Re: [Boost-users] boost.org domain expired?

On Tue, May 3, 2022 at 10:42 AM Warren Weckesser via Boost-users wrote: > FYI: Attempting to visit https://www.boost.org results in a Network > Solutions page, with links for "Renew Now" and "Backorder Domain". When I said we needed a new website this is NOT what I had in mind Thanks __

Re: [Boost-users] [release] Boost 1.79.0

On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users wrote: > Release 1.79.0 of the Boost C++ Libraries is now available. The thing that I absolutely LOVE about a new release of Boost, is that someone always reports a crashing bug just after the release is published:

Re: [Boost-users] [release] Boost 1.79.0

On Wed, Apr 13, 2022 at 8:13 AM Marshall Clow via Boost-users wrote: > Release 1.79.0 of the Boost C++ Libraries is now available. Thanks! ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users

Re: [Boost-users] Boost.ASIO SSL Version?

On Wed, Mar 9, 2022 at 3:18 PM Osman Zakir wrote: > handshake: An existing connection was forcibly closed by the remote host Well, that is the error ECONNRESET. You need to study why that error happens and apply it to the context of your particular use-case. Regards _

Re: [Boost-users] Boost.ASIO SSL Version?

On Wed, Mar 9, 2022 at 11:59 AM Osman Zakir via Boost-users wrote: > What version of OpenSSL does Boost.ASIO use? You should be using "OpenSSL 1.1.1m" Thanks ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listi

Re: [Boost-users] Test post - please ignore

On Wed, Mar 2, 2022 at 6:52 AM Marshall Clow via Boost-users wrote: > > I’ve got a report that posts to the lists are failing… Testing. I can see this post Thanks ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/

Re: [Boost-users] Boost::coroutine2 and compiling for ASAN problems

On Wed, Feb 16, 2022, 10:03 AM tjisana (泰志) via Boost-users < boost-users@lists.boost.org> wrote: > That was such a low-grade, I need a swift-kick-in-the-pants flub - > apologies! > LOL.. happens to best of us, no worries Regards > ___ Boost-users mai

Re: [Boost-users] Crash in async_handshake function

On Tue, Feb 8, 2022 at 7:37 AM Ales Mulej wrote: > only one. I reduced this number to one until this problem is not solved. If you temporarily replace > boost::beast::websocket::stream> with > boost::asio::ssl_stream and adjust the surrounding code for the change, what happens? Thanks __

Re: [Boost-users] Crash in async_handshake function

On Tue, Feb 8, 2022 at 6:57 AM Ales Mulej via Boost-users wrote: > I'm writing TLS client/server and my server is continuously crashing in the > async_handshake function. How many threads are calling io_context::run() ? Thanks ___ Boost-users mailing

Re: [Boost-users] Boost SSL handshake(http_server_sync_ssl) : still reachable memory keeps increasing

On Thu, Feb 3, 2022 at 9:41 AM Sandeep Bhardwaj via Boost-users wrote: > http_server_sync_ssl.cpp Oh, right. Synchronous APIs have no way to time out. So if the remote host does not close gracefully (i.e. just slams the connection shut) then you will be left with a connection object which either

Re: [Boost-users] Boost SSL handshake(http_server_sync_ssl) : still reachable memory keeps increasing

On Thu, Feb 3, 2022 at 6:52 AM Sandeep Bhardwaj via Boost-users wrote: > I am using boost 1.76.0 version. What version of OpenSSL ? Thanks ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-use

Re: [Boost-users] [Boost.Asio] Segmentation fault when ::getaddrinfo() returns EAI_SYSTEM without system error code set (errno = 0) - is this a bug?

On Mon, Aug 9, 2021 at 6:42 AM Nils Frielinghaus via Boost-users wrote: > I experienced a segmentation fault inside Boost in the following scenario: Can you please post a small, self-contained program that reproduces the segfault? Thanks ___ Boost-user

Re: [Boost-users] Boost.Asio as "thread-pool": How to apply back-pressure?

On Tue, Feb 9, 2021 at 7:20 AM Dominique Devienne wrote: > ... At the end of the day, backpressure means that you limit the rate at which you launch the dependee tasks (the A and B tasks). You can do this two ways. Have the dependent task responsible for launching its dependencies every time it c

Re: [Boost-users] Boost.Asio as "thread-pool": How to apply back-pressure?

On Tue, Feb 9, 2021, 10:20 AM Damien via Boost-users < boost-users@lists.boost.org> wrote: > On 2/9/2021 10:59 AM, Niall Douglas via Boost-users wrote: > > On 09/02/2021 15:13, Dominique Devienne via Boost-users wrote: > > > I find Niall's advice to be often wrong, unhelpful, and noisy. Just one

Re: [Boost-users] Boost.Asio as "thread-pool": How to apply back-pressure?

On Tue, Feb 9, 2021 at 5:20 AM Dominique Devienne via Boost-users wrote: > Could someone please recommend a way to have a more balanced flow of tasks in > the graph? > Or alternative designs even, if what I do above is not ideal. Is Boost.Asio > even suitable in this case? Yes. Only queue A and

Re: [Boost-users] shutdown( ) blocks forever

On Wed, Dec 30, 2020 at 6:27 AM Fariya F via Boost-users wrote: > I see that the call to ssl socket member function shutdown() blocks sometimes > forever You are mixing synchronous and asynchronous operations on the same socket, which is generally disallowed. Use async_shutdown instead, and also

Re: [Boost-users] Fwd: [Beast] Slow HTTP connect on Windows. Normal?

> I'm fairly sure it's user-error, but it's not easy to figure out for a Beast > novice like myself. --DD Your response is 200 OK, but you aren't setting Content-Length: 0. Under HTTP rules this means that the end of the body is indicated by an end of file. The documentation for need_eof explains

Re: [Boost-users] Boost.Beast base64 decode

On Thu, Dec 10, 2020 at 8:56 AM Dominique Devienne via Boost-users wrote: > Well, what's to discuss after the above really? I'll just use something else. You can copy the code into your own source file and edit to suit your needs precisely, it is very small. Thanks __

Re: [Boost-users] [Beast] Slow HTTP connect on Windows. Normal?

On Wed, Nov 25, 2020 at 2:55 AM Dominique Devienne via Boost-users wrote: > Given the high connect time on Windows, I thought I'd try to keep the > connection open on the client, and issue several send-request/read-response > pairs, using the Beast-based (sync) HTTP client, but only the first on

Re: [Boost-users] Boost 1.74: Coroutines2 on MSVC 2019 / C++20

On Thu, Oct 29, 2020 at 6:25 AM Daniel Petrovic via Boost-users wrote: > By using coroutines 2 on MSVC 2019 (v16.7.7) with C++20 there is a > compilation issue regarding result_of which is replaced by invoke_result in > C++20. Please open an issue describing the problem here:

Re: [Boost-users] [Beast] streaming a large compressed file

On Sat, Aug 22, 2020 at 8:02 AM Sean Farrow via Boost-users wrote: > Is there any examples of interfacing boost.beast with boost.iostreams in this > sort of streaming context? Not iostreams, but this example in the documentation shows how to read the body one buffer at a time:

Re: [Boost-users] [release] Boost 1.74.0

On Fri, Aug 14, 2020 at 7:30 AM Marshall Clow via Boost-users wrote: > Thanks to everyone who participated in this release. Thank you to the release team for doing this work. Perhaps we should think about doing some kind of simple award ceremony after each release? We could recognize one individ

Re: [Boost-users] [boost] [release] Boost 1.74.0 Release Candidate 2

On Tue, Aug 11, 2020 at 11:01 AM Marshall Clow via Boost wrote: > The second release candidates for the 1.74.0 release are now available at: > > I don't see the fix for this deprecated header warning caused by Boost.Coroutine: #include

Re: [Boost-users] [release] Boost 1.74.0 Release Candidate 1

On Fri, Aug 7, 2020 at 8:14 AM Marshall Clow via Boost-users wrote: > The first release candidates for the 1.74.0 release are now available at: There's a fix for the warning in Boost.Coroutine, merged to master - is it possible to include this in the release? See:

Re: [Boost-users] [boost] [json] [text] Multiple, custom string tyypes

On Mon, Jun 15, 2020 at 4:18 AM Andrzej Krzemienski wrote: > It should be possible to parametrize Boost.JSON with the string type. Another problem with doing this, is that it breaks the invariant of Boost.JSON's DOM value type: * All child elements in a DOM will inherit the allocator of the root

Re: [Boost-users] [boost] [json] [text] Multiple, custom string tyypes

On Mon, Jun 15, 2020 at 4:18 AM Andrzej Krzemienski wrote: > can they use their string in Boost.JSON? No. The design of the library explicitly avoids allowing customizability. > It should be possible to parametrize Boost.JSON with the string type. This has been explored in other libraries, and

Re: [Boost-users] [boost] [review] [text] Text formal review

On Fri, Jun 12, 2020 at 10:36 AM Rainer Deyke via Boost wrote: > String layer: overall, a solution looking for a problem. I created boost::json::string to use instead of std::string for a couple of reasons: 1. It uses a type-erased, reference counted memory resource instead of Allocator template

Re: [Boost-users] lambdish stdlib (was: LEAF review)

On Thu, May 28, 2020 at 11:54 PM Stian Zeljko Vrba via Boost-users wrote: > My informal, "stream of thought" review, > written during linearly reading the documentation. Wonderful review, written in a down to earth style which succinctly captures some of my own thoughts, thank you. > Then I star

Re: [Boost-users] asio, beast and concepts

On Mon, Mar 23, 2020 at 9:10 AM David P. Riedel via Boost-users wrote: > My set up: Perhaps you might provide a self-contained example program which exhibits the problem here: Thanks ___ Boost-users mailing list Boost-us

Re: [Boost-users] Uploading a file to a Boost Beast Server

On Mon, Mar 23, 2020 at 8:05 AM Bill Moo via Boost-users wrote: > Is there a working example anywhere of how I can capture > and save a file uploaded to the server by a user please. I don't think there's an example, but it is as easy as: http::request req; http::read( sock, buf, req );

Re: [Boost-users] Is iterator_facade still relevant in C++11, C++17?

On Sat, Mar 14, 2020 at 2:00 PM Mateusz Loskot via Boost-users wrote: > ...would you use it? Never again. Howard told me so, and I agreed. Thanks ___ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boos