Add experimental sycl integration/executor

This pull request adds a basic, experimental HPX-SYCL integration
In a nutshell: This allows us to get HPX futures from asynchronous SYCL calls.
The main features added are:

Allow compilation with dpcpp (Intel OneAPI) and hipSYCL. For dpcpp we use the compiler arguments -fsycl (for sycl related files) and -fno-sycl for normal HPX files. Due to problems with the compilation using hipSYCL's syclcc, we rely on its cmake integration here instead.
Added event polling to create HPX futures from SYCL events. Effectively, this allows to write code like:

        // Submit kernel into sycl queue [pure SYCL]
        cl::sycl::event my_kernel_event = my_sycl_queue.submit([&](cl::sycl::handler& h) {
            cl::sycl::accessor a(a_buf, h, cl::sycl::read_only);
            cl::sycl::accessor b(b_buf, h, cl::sycl::read_only);
            cl::sycl::accessor results(results_buf, h, cl::sycl::write_only, cl::sycl::no_init);
            h.parallel_for(num_items, [=](auto i) { /* insert numeric code here */ });
        });
        // Get future from event [HPX-SYCL]
        hpx::future<void> my_kernel_future =
            hpx::sycl::experimental::detail::get_future(my_kernel_event);

Bolted on top of this basic get_future functionality, the PR also adds an experimental SYCL executor. The executor encapsulates a SYCL queue and allows calling queue member functions using async_execute and post by specifying the desired member function, as well as passing all required arguments like this:

        // Create executor
        hpx::sycl::experimental::sycl_executor exec(cl::sycl::default_selector{});
        // Launch kernel
        hpx::future<void> fut = exec.async_execute(
            &cl::sycl::queue::submit, [&](cl::sycl::handler& h) {
                cl::sycl::accessor a(a_buf, h, cl::sycl::read_only);
                cl::sycl::accessor b(b_buf, h, cl::sycl::read_only);
                cl::sycl::accessor results(results_buf, h, cl::sycl::write_only, cl::sycl::no_init);
                h.parallel_for(num_items, [=](auto i) { /* insert numeric code here */ });
            });

Added three simple vector_add tests/examples: One just using the basic get_future integration, one using the executor and a last one subdividing the problem into chunks and using multiple executors, launching kernels from multiple threads.

Some implementation details:
I used the CUDA HPX integration as a template, so overall it is rather similar to the event polling implemented there (see PR  #4385). However, I had to adapt things for a) differences in the SYCL specification (lack of normal callbacks, lack of the ability to just create and record sycl events without any kernel/memcpy calls) and b) for differences between two used SYCL implementations (oneapi, hipsycl). Notable SYCL-implementation-specific workarounds for said differences:

For hipSYCL, we need to flush hipSYCL's internal DAG after launching a kernel and creating a future, as it is not guaranteed that hipSYCL is actually going to start the kernel before we request its results (resulting in a deadlock).
Also for hipSYCL: We need to keep the hipSYCL runtime alive whilst the event polling is activated - if we don't we might recreate and destroy the entire hipSYCL runtime each time we call poll() as long as no other SYCL object is alive. This can result in significant overhead during phases where we don't have a kernel/executor active (which was already noticeable in the concurrent executor test and the beginning and ending of the test). This can be prevented by simply keeping an extra queue alive as long as the polling is active, which is done internally (so the user won't have to worry about it).
For oneAPI: Here the sycl queue member functions have a different interface (including a code_location parameter), requiring adaptations in the sycl executor async_execute and post implementation to find the correct member function given the passed function pointer.
Compilation differences: For oneAPI we could simply compile with dpcpp (given the correct flags for sycl/none-sycl files), for hipSYCL the compilation with its syclcc caused too many compilation issues, so I ended up using its cmake integration instead.

How to build/test:
I tested this PR on my local laptop which contains an integrated Intel GPU (Iris Xe) and a discrete NVIDIA Geforce GTX 1650). I used the Intel GPU with oneAPI, the NVIDIA GPU with hipSYCL. Hence there are two build configurations:

With OneAPI (using dpcpp version 2<IP_ADDRESS>21020 as installed from the ubuntu 20.04 PPA) I used:

cmake -DCMAKE_CXX_COMPILER=dpcpp -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DHPX_WITH_EXAMPLES=ON -DHPX_WITH_TESTS=ON -DHPX_WITH_TESTS_UNIT=ON -DHPX_WITH_NETWORKING=OFF -DHPX_WITH_FETCH_ASIO=ON -DHPX_WITH_CXX17=ON -DHPX_WITH_CUDA=OFF -DHPX_WITH_SYCL=ON -DHPX_WITH_MALLOC=system -DCMAKE_INSTALL_PREFIX=/where/ever/you/want/to/have/this /hpx-with-PR-checked-out

With hipSYCL (I used hipSYCL commit ee450740dade99b9174cbc0845cf881ec64bdd10 from early October 2022), first configure hipSYCL like this (assuming you use clang 12 like I did and have an NVIDIA GPU):

 cmake -DCMAKE_INSTALL_PREFIX=/hipsycl/install/path -DCMAKE_CXX_COMPILER=clang++-12 -DCMAKE_C_COMPILER=clang-12  -DWITH_CUDA_BACKEND=ON ../hipSYCL/

then make and install hipsycl.
Using this, configure HPX like this:
cmake -DCMAKE_CXX_COMPILER=clang++-12 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DHPX_WITH_EXAMPLES=ON -DHPX_WITH_TESTS=ON -DHPX_WITH_NETWORKING=OFF -DHPX_WITH_FETCH_ASIO=ON -DHPX_WITH_CXX17=ON -DHPX_WITH_CUDA=ON -DHPX_WITH_MALLOC=system -DCMAKE_INSTALL_PREFIX=/where/ever/you/want/to/have/this-DhipSYCL_DIR=/hipsycl/install/path/lib/cmake/hipSYCL -DHIPSYCL_TARGETS="cuda.integrated-multipass:sm_75" -DCMAKE_CXX_FLAGS="-Wno-unknown-cuda-version " -DHPX_WITH_SYCL=ON -DHPX_WITH_HIPSYCL=ON /hpx-with-PR-checked-out

(change HIPSYCL_TARGETS depending on what GPU you have available -- consult the hipSYCL documentation for this).
Once all of this is done, you can simply build the HPX SYCL test with
make tests.unit.modules.async_sycl

You can run them with
ctest -R sycl
or, to run the tests/examples individually from the build directory:
./bin/sycl_vector_add_get_future_test
./bin/sycl_vector_add_executor_test
./bin/sycl_vector_add_concurrent_executors_test -t 4

Possible next steps:

While I am considering the SYCL executor itself to be rather experimental (basically a proof-of-concept), the basic get_future functionality seems to work well. In theory, this can already be used in HPX-Kokkos for getting futures from Kokkos kernels that run on the SYCL execution space. This could in turn allow applications like Octo-Tiger to use the Kokkos SYCL execution space.
More examples/polish and testing on machines other than my laptop.

@G-071 Thanks for doing this!
Does this also enable writing:
hpx::sycl::experimental::sycl_executor exec(cl::sycl::default_selector{});
hpx::async(exec, ...);

(in theory it should)?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-11-25T13:46:05+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a9510e5509fe1ebd7846b640221892c52cd911e5b89ClusternamedaintdaintDatetime2022-05-31T15:13:01.357969+02:002022-11-25T15:02:12.798878+01:00EnvfileHostnamenid01193nid00830Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-11-25T13:46:05+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a9510e5509fe1ebd7846b640221892c52cd911e5b89ClusternamedaintdaintDatetime2022-05-31T15:13:18.026239+02:002022-11-25T15:02:29.603183+01:00EnvfileHostnamenid01193nid00830Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2021-11-10T19:14:21+00:002022-11-25T13:46:05+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a10e5509fe1ebd7846b640221892c52cd911e5b89ClusternamedaintdaintDatetime2021-11-10T20:28:18.266961+01:002022-11-25T15:02:45.032518+01:00EnvfileHostnamenid00120nid00830Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@hkaiser Thanks for the feedback!
It's good that you mentioned whether it works with hpx::async -- turns out it did not! So I took care of that first:
The tag_invoke for it was still missing. After adding that it worked but only when specifying the exact type of the sycl queue function which was rather ugly:
auto my_sycl_kernel_to_submit = [&](cl::sycl::handler& h) {
                cl::sycl::accessor a(a_buf, h, cl::sycl::read_only);
                cl::sycl::accessor b(b_buf, h, cl::sycl::read_only);
                cl::sycl::accessor results(results_buf, h, cl::sycl::write_only, cl::sycl::no_init);
                h.parallel_for(num_items, [=](auto i) { /* insert numeric code here */ });
            };
auto fut = hpx::async<decltype(exec), my_queue_function_t<decltype(my_sycl_kernel_to_submit)>>(exec,
            &cl::sycl::queue::submit, my_sycl_kernel_to_submit);

Essentially, the issue here was that the compiler could not figure out the type of the sycl queue member function pointer &cl::sycl::queue::submit on its own as it depends on other templates (most of the queue functions do) so it needed some help!
To work around this, I added an overload to hpx::async (and one for hpx::apply) for the sycl executors. These specify the member function itself not as a template, but simply as a pointer depending on the type of the following arguments -- this seems to be enough for clang to figure out the rest! Link to said overloads.
With all that done, we can now write this as expected:
auto fut = hpx::async(exec,
            &cl::sycl::queue::submit, [&](cl::sycl::handler& h) {
                cl::sycl::accessor a(a_buf, h, cl::sycl::read_only);
                cl::sycl::accessor b(b_buf, h, cl::sycl::read_only);
                cl::sycl::accessor results(results_buf, h, cl::sycl::write_only, cl::sycl::no_init);
                h.parallel_for(num_items, [=](auto i) { /* insert numeric code here */ });
            });

I added two additional tests for this to the single executor vector_add file and changed the concurrent vector_add test  to use hpx::async and hpx::apply altogether.
Overall, I am now happy with this and will move on to the rest of the comments (though I am still open to other solutions besides having the async/apply overloads).

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-11-25T14:24:31+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95c0afeb1792970c218be6f511efe16df75cd50e1fHostnamenid01193nid00826Datetime2022-05-31T15:13:01.357969+02:002022-11-25T15:38:09.011382+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-11-25T14:24:31+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95c0afeb1792970c218be6f511efe16df75cd50e1fHostnamenid01193nid00826Datetime2022-05-31T15:13:18.026239+02:002022-11-25T15:38:25.989479+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPX Datetime2021-11-10T19:14:21+00:002022-11-25T14:24:31+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01ac0afeb1792970c218be6f511efe16df75cd50e1fHostnamenid00120nid00826Datetime2021-11-10T20:28:18.266961+01:002022-11-25T15:38:41.200017+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@hkaiser I think I addressed all of your feedback (I took the liberty of marking the minor points as resolved already)!

auto fut = hpx::async(exec,
            &cl::sycl::queue::submit, [&](cl::sycl::handler& h) {
                cl::sycl::accessor a(a_buf, h, cl::sycl::read_only);
                cl::sycl::accessor b(b_buf, h, cl::sycl::read_only);
                cl::sycl::accessor results(results_buf, h, cl::sycl::write_only, cl::sycl::no_init);
                h.parallel_for(num_items, [=](auto i) { /* insert numeric code here */ });
            });

Now I'm wondering whether this could be simplified further:
auto fut = hpx::async(exec, as_result(results_buf), std::ref(a_buf), std::ref(b_buf));

Using SYCL USM, I should be able to add an example like (or at least close to this). I think that will be worth having as an example. I will add that to the PR this week when I find some time for! I still need to clean up the circleci-inspect warnings anyways.

SYCL USM

I wasn't thinking in terms of universal memory. I think that it is possible to rewrap things such to achieve what I suggested without adding more capabilities...

@G-071 would you mind resolving the conflicts, please?

@hkaiser Done! I just merged master into the branch!
I've also added some additional changes to this PR:

It now works with the Intel LLVM instead of just the ubuntu-PPA-version of dpcpp (handy for having one single toolchain able to target Intel, NVIDIA and AMD GPUs).
I added support and a test for USM memory.
Additionally, I added support for the SYCL queue shortcut methods, allowing us to call kernels like this (for example):

auto fut = hpx::async(exec, &cl::sycl::queue::parallel_for, cl::sycl::range<1>{number_workitems}, kernel);

I was also able to get both HPX-Kokkos and Octo-Tiger itself working with SYCL (using the HPX-SYCL integration added  in this PR together with the Kokkos-SYCL execution space). See referenced hpx-kokkos/octotiger PRs for more details.
For the lack of a FP64-capable Intel GPU (my own iGPU only seems to supports FP64 via emulation which I haven't tried yet), I've tested Octo-Tiger on both a NVIDIA A100 and an AMD MI100 GPU using the SYCL execution space and it seems to work well. From my first impression on these GPUs, there is a slight performance price to pay, though it did not seem too bad. Though, my next step would be some more thorough performance tests with Octo-Tiger and SYCL to get more data.

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f59054ee9399726e8d432fad6c86f40b3e92f51e9HPX Datetime2023-01-12T14:41:15+00:002023-01-31T18:28:47+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-12T16:07:32.649261+01:002023-01-31T19:41:42.219005+01:00EnvfileClusternamedaintdaintHostnamenid00267nid00604ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f11799559054ee9399726e8d432fad6c86f40b3e92f51e9HPX Datetime2023-01-18T08:41:20+00:002023-01-31T18:28:47+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-18T09:57:57.669847+01:002023-01-31T19:42:02.863460+01:00EnvfileClusternamedaintdaintHostnamenid00005nid00604ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef059054ee9399726e8d432fad6c86f40b3e92f51e9HPX Datetime2023-01-17T08:25:42+00:002023-01-31T18:28:47+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-17T09:44:28.090718+01:002023-01-31T19:42:18.189821+01:00EnvfileClusternamedaintdaintHostnamenid00005nid00604Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-31T18:28:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee59054ee9399726e8d432fad6c86f40b3e92f51e9EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:15.951027-06:002023-01-31T13:13:18.474683-06:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-31T18:28:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee59054ee9399726e8d432fad6c86f40b3e92f51e9EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:31.068958-06:002023-01-31T13:13:39.386578-06:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+---++Stream Benchmark - Scale(=)(=)-Stream Benchmark - Triad+---++Stream Benchmark - Copy+---(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-31T18:28:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee59054ee9399726e8d432fad6c86f40b3e92f51e9EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:46.398919-06:002023-01-31T13:13:55.633908-06:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeedf37a8c46f1f79c0f81438a205948318797af05HPX Datetime2023-01-12T23:07:58+00:002023-02-01T23:12:09+00:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:15.951027-06:002023-02-01T17:22:45.702670-06:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeedf37a8c46f1f79c0f81438a205948318797af05HPX Datetime2023-01-12T23:07:58+00:002023-02-01T23:12:09+00:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:31.068958-06:002023-02-01T17:23:05.574382-06:00ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------+Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad------+Stream Benchmark - Copy---InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeedf37a8c46f1f79c0f81438a205948318797af05HPX Datetime2023-01-12T23:07:58+00:002023-02-01T23:12:09+00:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:46.398919-06:002023-02-01T17:23:22.468377-06:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T14:41:15+00:002023-02-01T23:12:09+00:00HPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95fedf37a8c46f1f79c0f81438a205948318797af05ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-12T16:07:32.649261+01:002023-02-02T00:41:45.904979+01:00EnvfileHostnamenid00267nid01283ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2023-01-18T08:41:20+00:002023-02-01T23:12:09+00:00HPX Commitda01e78993b6bb8da476492b2770f1cc3f117995edf37a8c46f1f79c0f81438a205948318797af05ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-18T09:57:57.669847+01:002023-02-02T00:42:06.155647+01:00EnvfileHostnamenid00005nid01283ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+-(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad+-(=)Stream Benchmark - Copy=(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-17T08:25:42+00:002023-02-01T23:12:09+00:00HPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef0edf37a8c46f1f79c0f81438a205948318797af05ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-17T09:44:28.090718+01:002023-02-02T00:42:21.430844+01:00EnvfileHostnamenid00005nid01283Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee141f539cbbde9abb8288cf5edcd3fe3eef5e9fadHPX Datetime2023-01-12T23:07:58+00:002023-02-02T00:29:16+00:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:15.951027-06:002023-02-01T18:40:11.704896-06:00EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee141f539cbbde9abb8288cf5edcd3fe3eef5e9fadHPX Datetime2023-01-12T23:07:58+00:002023-02-02T00:29:16+00:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:31.068958-06:002023-02-01T18:40:31.720129-06:00EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add++--+++Stream Benchmark - Scale(=)--(=)Stream Benchmark - Triad++--+++Stream Benchmark - Copy+(=)(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee141f539cbbde9abb8288cf5edcd3fe3eef5e9fadHPX Datetime2023-01-12T23:07:58+00:002023-02-02T00:29:16+00:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-01-13T04:10:46.398919-06:002023-02-01T18:40:46.645057-06:00EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T14:41:15+00:002023-02-02T00:29:16+00:00HPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f141f539cbbde9abb8288cf5edcd3fe3eef5e9fadDatetime2023-01-12T16:07:32.649261+01:002023-02-02T01:40:21.503924+01:00EnvfileClusternamedaintdaintHostnamenid00267nid00269Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch---InfoPropertyBeforeAfterHPX Datetime2023-01-18T08:41:20+00:002023-02-02T00:29:16+00:00HPX Commitda01e78993b6bb8da476492b2770f1cc3f117995141f539cbbde9abb8288cf5edcd3fe3eef5e9fadDatetime2023-01-18T09:57:57.669847+01:002023-02-02T01:40:41.376200+01:00EnvfileClusternamedaintdaintHostnamenid00005nid00269Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)=(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-17T08:25:42+00:002023-02-02T00:29:16+00:00HPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef0141f539cbbde9abb8288cf5edcd3fe3eef5e9fadDatetime2023-01-17T09:44:28.090718+01:002023-02-02T01:40:56.735072+01:00EnvfileClusternamedaintdaintHostnamenid00005nid00269Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@G-071 What's the status of this?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-12T23:07:58+00:002023-03-07T23:42:49+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileDatetime2023-01-13T04:10:15.951027-06:002023-03-07T17:49:33.252955-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-12T23:07:58+00:002023-03-07T23:42:49+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileDatetime2023-01-13T04:10:31.068958-06:002023-03-07T17:49:53.630818-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+---+Stream Benchmark - Scale(=)(=)-Stream Benchmark - Triad+---(=)Stream Benchmark - Copy+(=)(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-12T23:07:58+00:002023-03-07T23:42:49+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileDatetime2023-01-13T04:10:46.398919-06:002023-03-07T17:50:09.499896-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-12T14:41:15+00:002023-03-07T23:42:49+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00267nid00025ClusternamedaintdaintEnvfileDatetime2023-01-12T16:07:32.649261+01:002023-03-08T00:59:46.048843+01:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch---InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f117995184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-18T08:41:20+00:002023-03-07T23:42:49+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00005nid00025ClusternamedaintdaintEnvfileDatetime2023-01-18T09:57:57.669847+01:002023-03-08T01:00:06.747841+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad+(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef0184686fec9885e7880a3d2755b46a0f7dce05da5HPX Datetime2023-01-17T08:25:42+00:002023-03-07T23:42:49+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00005nid00025ClusternamedaintdaintEnvfileDatetime2023-01-17T09:44:28.090718+01:002023-03-08T01:00:23.061485+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)--(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T21:50:50+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eedd210c052c9e61b385767942a0cdab3d2e62d887ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:15.951027-06:002023-03-08T15:59:35.828130-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T21:50:50+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eedd210c052c9e61b385767942a0cdab3d2e62d887ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:31.068958-06:002023-03-08T15:59:57.481565-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add-----+++Stream Benchmark - Scale-(=)(=)Stream Benchmark - Triad-----+++Stream Benchmark - Copy+(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T21:50:50+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eedd210c052c9e61b385767942a0cdab3d2e62d887ClusternamerostamrostamEnvfileDatetime2023-01-13T04:10:46.398919-06:002023-03-08T16:00:13.291588-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:00:05+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:15.951027-06:002023-03-08T16:04:33.084825-06:00ClusternamerostamrostamEnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:00:05+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:31.068958-06:002023-03-08T16:04:54.331261-06:00ClusternamerostamrostamEnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------+++Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad-----+++Stream Benchmark - Copy=(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:00:05+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:46.398919-06:002023-03-08T16:05:10.037080-06:00ClusternamerostamrostamEnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T14:41:15+00:002023-03-08T22:00:05+00:00HPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaHostnamenid00267nid00807ClusternamedaintdaintEnvfileDatetime2023-01-12T16:07:32.649261+01:002023-03-08T23:18:39.728192+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2023-01-18T08:41:20+00:002023-03-08T22:00:05+00:00HPX Commitda01e78993b6bb8da476492b2770f1cc3f117995420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaHostnamenid00005nid00807ClusternamedaintdaintEnvfileDatetime2023-01-18T09:57:57.669847+01:002023-03-08T23:18:58.252499+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-17T08:25:42+00:002023-03-08T22:00:05+00:00HPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef0420fc5cb28fae11daa8e4d3b87fe4a95a48cbdbaHostnamenid00005nid00807ClusternamedaintdaintEnvfileDatetime2023-01-17T09:44:28.090718+01:002023-03-08T23:19:13.594701+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:18:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee41e91f7b8265e71eb88a9eaa55783f01ccc1d7f8Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamDatetime2023-01-13T04:10:15.951027-06:002023-03-08T16:24:57.351792-06:00EnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:18:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee41e91f7b8265e71eb88a9eaa55783f01ccc1d7f8Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamDatetime2023-01-13T04:10:31.068958-06:002023-03-08T16:25:18.722393-06:00EnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add-------Stream Benchmark - Scale(=)(=)---Stream Benchmark - Triad-------Stream Benchmark - Copy+(=)---InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-08T22:18:47+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee41e91f7b8265e71eb88a9eaa55783f01ccc1d7f8Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamDatetime2023-01-13T04:10:46.398919-06:002023-03-08T16:25:36.029087-06:00EnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)=(=)InfoPropertyBeforeAfterHPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f41e91f7b8265e71eb88a9eaa55783f01ccc1d7f8HPX Datetime2023-01-12T14:41:15+00:002023-03-08T22:18:47+00:00Hostnamenid00267nid00604EnvfileDatetime2023-01-12T16:07:32.649261+01:002023-03-08T23:32:26.593666+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f11799541e91f7b8265e71eb88a9eaa55783f01ccc1d7f8HPX Datetime2023-01-18T08:41:20+00:002023-03-08T22:18:47+00:00Hostnamenid00005nid00604EnvfileDatetime2023-01-18T09:57:57.669847+01:002023-03-08T23:32:45.739289+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef041e91f7b8265e71eb88a9eaa55783f01ccc1d7f8HPX Datetime2023-01-17T08:25:42+00:002023-03-08T22:18:47+00:00Hostnamenid00005nid00604EnvfileDatetime2023-01-17T09:44:28.090718+01:002023-03-08T23:33:01.085588+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-09T09:00:39+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eef3729de26072aebb84f8ee4e5fe7472e209abd62Datetime2023-01-13T04:10:15.951027-06:002023-03-09T03:09:33.286335-06:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-09T09:00:39+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eef3729de26072aebb84f8ee4e5fe7472e209abd62Datetime2023-01-13T04:10:31.068958-06:002023-03-09T03:09:53.552525-06:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add-----++Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad-----++Stream Benchmark - Copy(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-09T09:00:39+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eef3729de26072aebb84f8ee4e5fe7472e209abd62Datetime2023-01-13T04:10:46.398919-06:002023-03-09T03:10:09.656698-06:00ClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-12T23:07:58+00:002023-03-10T15:04:44+00:00Datetime2023-01-13T04:10:15.951027-06:002023-03-10T09:09:42.460571-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-12T23:07:58+00:002023-03-10T15:04:44+00:00Datetime2023-01-13T04:10:31.068958-06:002023-03-10T09:10:03.649105-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add-----Stream Benchmark - Scale(=)--(=)Stream Benchmark - Triad-----Stream Benchmark - Copy+(=)(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-12T23:07:58+00:002023-03-10T15:04:44+00:00Datetime2023-01-13T04:10:46.398919-06:002023-03-10T09:10:19.842315-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)=(=)InfoPropertyBeforeAfterHPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f1d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-12T14:41:15+00:002023-03-10T15:04:44+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2023-01-12T16:07:32.649261+01:002023-03-10T16:18:50.958729+01:00Hostnamenid00267nid01193ClusternamedaintdaintComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f1179951d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-18T08:41:20+00:002023-03-10T15:04:44+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2023-01-18T09:57:57.669847+01:002023-03-10T16:19:10.700474+01:00Hostnamenid00005nid01193ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef01d0f310b6fbc58cb85644c1ac3f0375baeb9cf05HPX Datetime2023-01-17T08:25:42+00:002023-03-10T15:04:44+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2023-01-17T09:44:28.090718+01:002023-03-10T16:19:26.384395+01:00Hostnamenid00005nid01193ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

I have added some additional modifications to this PR. It now offers two versions of the HPX-SYCL integration: The event-polling that I originally added and a second version using SYCL host tasks to set the future data. In the end, the event polling version performs a lot better, but I wanted to have the comparison data for both, so now we have also have both implemented!
I also re-tested everything with dpcpp/icpx and hipSYCL (now called Open SYCL). With dpcpp/icpx everything works, both the SYCL-related tests within HPX , as well as the Octo-Tiger tests.
With hipSYCL the event-polling integration works as well and passes the HPX tests. However, hipSYCL lacks support for the SYCL host tasks and the required oneapi SYCL extensions that we would need for the Kokkos SYCL execution space (and thus for Octo-Tiger), so I couldn't test that. Though support for SYCL host tasks is completely optional for this HPX-SYCL integration itself anyway, as long as one sticks with the event polling version (which I would also recommend for performance reasons). Hence, hipSYCL can still be used together with HPX as long as one does not need any of the oneapi SYCL extensions.
Other than that, I think I addressed the issues mentioned in January @hkaiser. Can you have another look at it? Please let me know if I missed anything. From my end, this looks good to be merged, though!
In the future, I would like to add asynchronous exception handling for the SYCL executor and some tests for that. However, I would put this in a future PR and rather get this one in for the 1.9.0 release.

@G-071 one last thing - could you fix the inspect and cmake-format issues, please?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-12T18:59:33+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eebb62a6802666e26cf6d8955ac2b499fdc60153b1Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:15.951027-06:002023-03-12T14:04:47.389900-05:00EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-12T18:59:33+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eebb62a6802666e26cf6d8955ac2b499fdc60153b1Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:31.068958-06:002023-03-12T14:05:08.318008-05:00EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add----(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad---(=)Stream Benchmark - Copy+(=)-InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-03-12T18:59:33+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eebb62a6802666e26cf6d8955ac2b499fdc60153b1Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-01-13T04:10:46.398919-06:002023-03-12T14:05:24.836567-05:00EnvfileClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95fbb62a6802666e26cf6d8955ac2b499fdc60153b1HPX Datetime2023-01-12T14:41:15+00:002023-03-12T18:59:33+00:00EnvfileClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-12T16:07:32.649261+01:002023-03-12T20:14:14.383476+01:00Hostnamenid00267nid00023ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f117995bb62a6802666e26cf6d8955ac2b499fdc60153b1HPX Datetime2023-01-18T08:41:20+00:002023-03-12T18:59:33+00:00EnvfileClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-18T09:57:57.669847+01:002023-03-12T20:14:32.970093+01:00Hostnamenid00005nid00023ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add+(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad+(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef0bb62a6802666e26cf6d8955ac2b499fdc60153b1HPX Datetime2023-01-17T08:25:42+00:002023-03-12T18:59:33+00:00EnvfileClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2023-01-17T09:44:28.090718+01:002023-03-12T20:14:48.145821+01:00Hostnamenid00005nid00023Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)-(=)InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1827dbfa713d5b23512b227df5b0476c0d7cfa56HPX Datetime2023-01-12T23:07:58+00:002023-03-12T19:17:15+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamDatetime2023-01-13T04:10:15.951027-06:002023-03-12T14:24:55.077657-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1827dbfa713d5b23512b227df5b0476c0d7cfa56HPX Datetime2023-01-12T23:07:58+00:002023-03-12T19:17:15+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamDatetime2023-01-13T04:10:31.068958-06:002023-03-12T14:25:15.812161-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add---------Stream Benchmark - Scale(=)(=)--Stream Benchmark - Triad-------Stream Benchmark - Copy+(=)---InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee1827dbfa713d5b23512b227df5b0476c0d7cfa56HPX Datetime2023-01-12T23:07:58+00:002023-03-12T19:17:15+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamDatetime2023-01-13T04:10:46.398919-06:002023-03-12T14:25:33.101748-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T14:41:15+00:002023-03-12T19:17:15+00:00HPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f1827dbfa713d5b23512b227df5b0476c0d7cfa56EnvfileDatetime2023-01-12T16:07:32.649261+01:002023-03-12T20:33:02.220340+01:00Hostnamenid00267nid00752ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2023-01-18T08:41:20+00:002023-03-12T19:17:15+00:00HPX Commitda01e78993b6bb8da476492b2770f1cc3f1179951827dbfa713d5b23512b227df5b0476c0d7cfa56EnvfileDatetime2023-01-18T09:57:57.669847+01:002023-03-12T20:33:20.323288+01:00Hostnamenid00005nid00752ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)--Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)--Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-17T08:25:42+00:002023-03-12T19:17:15+00:00HPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef01827dbfa713d5b23512b227df5b0476c0d7cfa56EnvfileDatetime2023-01-17T09:44:28.090718+01:002023-03-12T20:33:35.785476+01:00Hostnamenid00005nid00752ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@G-071 one last thing - could you fix the inspect and cmake-format issues, please?

The last two commits resolved those issues! The remaining test failures ("tests.unit.segmented_algorithms") look like they are unrelated to this PR (I think).

@hkaiser Is there anything else that should be fixed before merging this?

bors merge


Make package.name optional

Problem
The primary motivation for this is to close the gap between Cargo.toml and the cargo script experiment (#12207).
For Cargo.toml, package.name is required
For "cargo script", package.name is defaulted to a slug of the file stem.
Proposed Solution
Like with #9829, making this field optional would reduce the specialized documentation around "cargo script". The default for Cargo.toml would be a slug of the parent directory.
Notes
I think there are some other concrete cases that could potentially benefit from this, like rust-lang/rfcs#3452 though I overall see this rarely being relied upon.

I'm not sure we'd be able to reduce documentation much here, as the logic to take the filename would not be suiting for Cargo.toml, so we'd have to document that differing logic. We would be able to reduce the overhead of writing existing Cargo.toml files though, which would be a benefit. I'd propose taking the name of the directory the Cargo.toml file is inside.

Oops, forgot to specify the parent directory.
While that technically is still a difference, the general concept is the same which makes it easier to teach.


api: move unwrap to helpers

Coverage remained the same at 82.11% when pulling 4b5d95eba0b268b90400188660ad5f64601dcf87 on move-unwrap into cf6614b3f3d2d5b0df3c60fa4f2b8e7fe89487fe on master.


Crashes when opening browser after restarting computer on XP 64x

Describe the bug
After restarting/turning on the computer and booting into XP, trying to run the browser shows a window, then closes immediately after. Opening the browser afterward works fine, it only crashes once on a fresh boot.
To Reproduce
Steps to reproduce the behavior:

Double click Supermium on the desktop after a restart of the computer, and after loading, it crashes.

Expected behavior
The browser should start the first time, rather than having to re-open it for it to load correctly.
Desktop (please complete the following information):

OS: [e.g. Windows XP SP2 x64]
Bitness of browser: x64

Additional context
This only seems to happen on XP, Vista and higher don't have this issue. I've had this issue across several versions of Supermium, it doesn't seem to be caused by any one version.

WinXP SP2 x64 @ VMWare - had no such issue, however i not check Supermium 126.0.6478.256 R5 x64, only R4

I believe it's related to issue #1030.


[logstash] update doc and values.yaml for http.host issues

add warning that http.host: <IP_ADDRESS> is required with default probes
add syntax to disable or override default probes

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[x] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

backported to 7.7 branch in ab26d11


Remove jenkins, admin-console and perf operator logic

Jenkins, admin-console, and perf operator are deprecated.
We need to remove all dependencies and related logic from the cd-pipeline operator.

Dependency removed.


Errors when opening text.exe

Warning, this software is designed for an old version of the game, so if you're trying to run it on a new version, it won't work. If you are indeed running it on an old version, please describe the problem in detail. Additionally, you can use MonoInjector.


[Questions] about the pods checking in the kube-system

We check this kube-system namespace in the WaitForPodsRunningReady, but no pods, daemonset in the kube-system namespace, why checking it? Or am I missing something? Thanks!
Test running logs as follows:
I1218 06:00:30.692485   15947 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
Dec 18 06:00:30.736: INFO: Waiting up to 30m0s for all (but 100) nodes to be schedulable
Dec 18 06:00:30.814: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Dec 18 06:00:30.891: INFO: 0 / 0 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Dec 18 06:00:30.891: INFO: expected 0 pod replicas in namespace 'kube-system', 0 are Running and Ready.
Dec 18 06:00:30.891: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start
Dec 18 06:00:30.916: INFO: e2e test version: v0.0.0-master+$Format:%h$
Dec 18 06:00:30.935: INFO: kube-apiserver version: v1.19.0+7070803
Dec 18 06:00:30.959: INFO: Cluster IP family: ipv4

@deads2k  Do you happen to know it? Thanks!

@deads2k  Do you happen to know it? Thanks!


[COM-1158] deploy browser files

@francoislg should the "browser" property of package.json be changed also?


glibc warnings compiling for 5.9-RELEASE_ubuntu_jammy_aarch64

I've created a simple helloworld tool, and compiling it generates warning messages that seem to be spurious.  Here's the project structure:
./Package.swift
./Sources/helloworld/main.swift
./Tests/LinuxMain.swift
./Tests/helloworldTests/helloworldTests.swift
./Tests/helloworldTests/XCTestManifests.swift

Package consists of:
// swift-tools-version:5.9
import PackageDescription

let package = Package(
    name: "helloworld",
    dependencies: [],
    targets: [
        .executableTarget(
            name: "helloworld",
            dependencies: []
        ),
        .testTarget(
            name: "helloworldTests",
            dependencies: ["helloworld"]
        ),
    ]
)

main.c consists of:
print("Successful launch!")

This produces the following output:
swift build --experimental-swift-sdk 5.9-RELEASE_ubuntu_jammy_aarch64
Building for debugging...
warning: Could not read SDKSettings.json for SDK at: /Users/rvs/Library/org.swift.swiftpm/swift-sdks/5.9-RELEASE_ubuntu_jammy_aarch64.artifactbundle/5.9-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk
<unknown>:0: warning: glibc not found for 'aarch64-unknown-linux-gnu'; C stdlib may be unavailable
<unknown>:0: warning: glibc not found for 'aarch64-unknown-linux-gnu'; C stdlib may be unavailable
warning: Could not read SDKSettings.json for SDK at: /Users/rvs/Library/org.swift.swiftpm/swift-sdks/5.9-RELEASE_ubuntu_jammy_aarch64.artifactbundle/5.9-RELEASE_ubuntu_jammy_aarch64/aarch64-unknown-linux-gnu/ubuntu-jammy.sdk
[5/5] Linking helloworld
Build complete! (9.02s)

The glibc warnings seem to be spurious.

Did you mean main.c or was that a typo?

sorry main.swift.  will fix

Tracked internally as rdar://115492638

I've been having similar issues with my manually configured cross-compilation build where
swift build --sdk <path/to/sysroot>

no longer works as expected in 5.9. Swift neither seems to find libc nor any other libraries in the sysroot. For a full log, see e.g. this failed build (I prepare a sysroot in the first Docker stage, then copy it over into /usr/local/<targetarch>-ubuntu-jammy and point --sdk to this sysroot, along with some flags for the C/C++ compilers).
Would of course be nice to migrate over to the new SDK bundles once the Ubuntu host -> Ubuntu target scenario is properly supported, but I assume this is still a regression.

This has gotten much worse in 5.9.1, now I get a ton of the following warnings:
clang-13: warning: -Z-reserved-lib-stdc++: 'linker' input unused [-Wunused-command-line-argument]
warning: Could not read SDKSettings.json for SDK at: /Users/____/Library/org.swift.swiftpm/swift-sdks/5.9.1-RELEASE_ubuntu_jammy_x86_64.artifactbundle/5.9.1-RELEASE_ubuntu_jammy_x86_64/x86_64-unknown-linux-gnu/ubuntu-jammy.sdk
<unknown>:0: warning: glibc not found for 'x86_64-unknown-linux-gnu'; C stdlib may be unavailable

The good news is that then I get:
[798/798] Linking echoserver
Build complete! (19.56s)


Migrate automation from autosynth to owlbot

This is the last googleapis python repo which is still using autosynth. I'm planning to migrate this repo to use owl-bot.
Assuming that we can use the existing googleapis-gen repository for both GAPIC and DIREGAPIC, The following steps are required:
[] - In a test environment, update this script in bazel-bot to also pull proto files from googleapis-discovery and confirm that the generated client for compute is updated for all 7 languages.
[] - Open a PR for bazel-bot to update the script with the above changes.
[] - Open a PR in this repo to delete synth.py in this repo and add owlbot.py

Closing as obsolete


Letcode workspace - Input automation

Automation testing for the following url: https://letcode.in/edit
Tasks for this page:

[x] Input Full Name
[x] Append text and press tab
[x] Check text inside element
[x] Clear text inside element
[x] Check if text field is disabled
[x] Check if text is readonly
[x] Documentation

Done 03/05/2023


Refactor Home template

FEATURE DESCRIPTION
Feature Inspiration
There are more model components than compound now.
Feature Description
Change the home template to compound_list and come up with a home view that links all the existing list views.
Alternatives Considered
A home view that previews a few records from every other model table.
Comment
There is no requirement set for a home page on the project roadmap yet.

ISSUE OWNER SECTION
Assumptions
none
Requirements

separate page for compound list that is the same as the current home page
Create a very basic home page that links to all the list views for each model component

Limitations
none
Affected/Changed Components

DataRepo/templates/home.html
DataRepo/templates/compound_list.html
DataRepo/views.py

DESIGN
GUI Change description
Home page changes from a compound list to a table of each database table's list view.
Code Change Description (Pseudocode optional)
Basically copy the home.html page to compound_list.html and edit the home.html page to link to every list view (currently only the compound list view).
Tests
none

As agreed in the meeting, I am proceeding on this in lieu of rockets.


feat: support gRPC multi-service on a server

What type of PR is this?
feat

Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.
[x] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

any progress? @Marina-Sakai

close by https://github.com/cloudwego/kitex-examples/pull/91


Rackspace integration

In the scope of this PR rackspace compute site integration will be implemented. To make it possible following actions need to be supported:

[x] Get flavors (FlavorManager)
[x] Get flavor data (FlavorManager)
[x] Get vms (VmMonitoringWorker)
[x] Get vm data (VmUpdater)
[x] Create tags for vm (VmTagsCreator)
[x] Get templates	 (VmTemplateMonitoringWorker)
[x] Destroy vm (VirtualMachine)
[x] Managing vm (VirtualMachine)
[x] Save template	(VirtualMachineTemplate)
[x] Destroy template (VirtualMachineTemplate)
[x] Create vm (VmCreator)
[x] Import key pair (UserKey)
[x] Delete key pair (UserKey)
[x] Get template data (VmtUpdater)

Rackspace integration ready, @dice-cyfronet/atmo-dev-team please take a look

:+1:

Why there is many bullets in first comment, but only 15 lines are changed and rest are added as configuration. Everything other is included in dependencies? Anyway :+1:

14 (not 15 :smile:) bullets are a checklist what need to be supported by concrete cloud provider. Rackspace is quite similar to openstack, that is why there so many changes.

I counted lines which are changed by your commits, but not added as new. OK, again: :+1:


installation issue

Hi Karen,
I'm attempting to install and try your "memory bot", which looks very interesting. When I get to step #3 Install dependencies using the requirements.txt file, e.g.,
"pip -r requirements.txt"
The following error is returned:
"Usage:
pip  [options]
no such option: -r"
I'm not a coder and don't know if this is an issue with your command or something else. Do you have a suggestion? Thanks.
Gene

Oh, belatedly, I can fix the instructions. Thank you for pointing it out!


Unable to access services on the local network

Hey, thanks for reporting. Usually, it will work. I will look into it. Thanks

it's related to https://github.com/ollama/ollama/issues/2335,
using OLLAMA_ORIGINS=http://<IP_ADDRESS> OLLAMA_HOST=<IP_ADDRESS> ollama serve, it works now

I know about that issue, which is why I rewrote the request with a custom origin. Which browser are you using, Chrome?

yeah，i'm using chrome


support return command

return from function and sourced script
in simple case (just return from function with static return keyword), just emit return and force translate args to int.
otherwise, emit __shtx_return

add basic support in commit bceda


Koa server

Adding a basic koa server. Note we are using V2.
Templating we're using nunjucks.
I would like to move the static application out to a static dir for clarity and build purposes.

Merging in as I haven't really touched anyone's code and it would be good to try and get a build going...


Redirect Manager: Default CaConfig Configuration not showing up

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.5___
[ ] ACS AEM Commons Version: 5.0.7-SNAPSHOT_
[ ] Reproducible on Latest? yes

Expected Behavior
The default CaConfig configuration is created by a repo-init script and should show up .
Actual Behavior

It's a regression caused by #2589
The repo-init script used to set sling:resourceType and it was commented out:
https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/7c358e8ae6451e871823111d1439973f5190a166/ui.apps/src/main/content/jcr_root/apps/acs-commons/config/org.apache.sling.jcr.repoinit.RepositoryInitializer-aem-cs.config#L12
The fix is coming

@YegorKozlov Is this really fixed? I don't see any merged commit related to this in the master branch.

@kwin  It was a false alarm. On my local I only deployed the ui.apps  package while the CaConfig configuration is created by ui.content.


DocumentDB app.config redirects need to be updated

If anyone tries to use DocumentClient as a parameter type, it'll break. We're referencing 1.13.0 of DocDB, yet the redirect is going to 1.11.0:
https://github.com/Azure/azure-functions-cli/blob/master/src/Azure.Functions.Cli/packages.config#L51
https://github.com/Azure/azure-functions-cli/blob/master/src/Azure.Functions.Cli/App.config#L94

CC @ahmelsayed


sending failed entries and err does not work as expected in gRPC Bulk Publish

In what area(s)?

/area runtime
What version of Dapr?
edge
Expected Behavior
When there are partial failures on a gRPC BulkPublishEventAlpha1() call, the response field must be populated with the failed entries as discussed in dapr/components-contrib#2260.
Actual Behavior
When err field is returned, the response if by default set to nil on the client side. And only the error status is used.
Steps to Reproduce the Problem
For testing this, hard coded in bulk publish API that entry_id: "1" will always fail e.g.: Hardcoded in line https://github.com/dapr/dapr/blob/master/pkg/runtime/pubsub/default_bulkpub.go#L82
// TODO REMOVE HARDCODE
	if entry.EntryId == "1" {
		return &contribPubsub.BulkPublishResponseEntry{
			EntryId: entry.EntryId,
			Error:   ErrBulkPublishFailure,
		}
	}

Then using post man posted a gRPC request such as :
{
    "entries": [
        {
            "content_type": "application/text",
            "event": "e30=",
            "entry_id": "1"
        },
        {
            "content_type": "application/text",
            "event": "e31=",
            "entry_id": "2"
        }
    ],
    "metadata": {},
    "pubsub_name": "pubsub",
    "topic": "testingtopic"
}

The response got back if err is there is

The issue
Reading the issue linked here https://github.com/grpc/grpc/issues/12824, it seems that this is the expected behavior. That is the
Server-implementations of gRPC MUST drop the Message if it is returned with a non-OK response.
Client side SHOULD drop any response messages received with a non-OK response.

The reason stated here is that if there is an error returned on a gRPC call, there is no guarantee that the response object is complete so it must be discarded and only the error status not-OK be considered.
How this is handled when there are partial failures in GetBulkState is that, even if there is error for individual items, then only the itemized error is populated in the response and the overall err for the gRPC call is still nil. See https://github.com/dapr/dapr/blob/master/pkg/grpc/api.go#L802-L817.
          if bgr.bulkGet {
// There is overall error, so send empty response with the err
		if err != nil {
			return bulkResp, err
		}
		for i := 0; i < len(bgr.responses); i++ {
			item := &runtimev1pb.BulkStateItem{
				Key:      stateLoader.GetOriginalStateKey(bgr.responses[i].Key),
				Data:     bgr.responses[i].Data,
				Etag:     stringValueOrEmpty(bgr.responses[i].ETag),
				Metadata: bgr.responses[i].Metadata,
				Error:    bgr.responses[i].Error,
			}
			bulkResp.Items = append(bulkResp.Items, item)
		}
// If there is partial error as seen above, still only send nil overall error and a valid response with the details populated correctly
		return bulkResp, nil
	}

Similar processing is done when state store does not implement bulkGet API also.
Should this be the one that is followed for BulkPublishEventAlpha1 request as well?
That is if there are partial failures, the err is still nil but the BulkPublishResponse is populated with the failed entries alone.
Only on the cases of overall error being such as the following will an empty response with overall error be returned.

nerr := status.Errorf(codes.Internal, messages.ErrPubsubPublishMessage, topic, pubsubName, err.Error())
if errors.As(err, &runtimePubsub.NotAllowedError{}) {
	nerr = status.Errorf(codes.PermissionDenied, err.Error())
}

if errors.As(err, &runtimePubsub.NotFoundError{}) {
	nerr = status.Errorf(codes.NotFound, err.Error())
}
// if pubsub not allowed or not found return empty response with the corresponding error status
return &BulkPublishResponse{}, nerr

@yaron2 @artursouza @ItalyPaleAle
cc @dapr/maintainers-dapr thoughts?
Release Note

RELEASE NOTE:

Don't return an err then when the publish response comes back with failed entries - instead, return err for non publish related calls (connection failures, network, bad request etc.).

Don't return an err then when the publish response comes back with failed entries - instead, return err for non publish related calls (connection failures, network, bad request etc.).

Ok that is what I mentioned in in description. And I will change it to that behavior ...


Add empty meta file

This will allow ansible-galaxy to consider it a role, which makes it available to ansible-galaxy install -r requirements.yml using
#requirements.yml
- src: https://github.com/dlundgren/ansible-freebsd-modules```

and pulling it in to role dependencies via

#roles/bla/meta/main.yml
dependencies:

role: ansible-freebsd-modules

https://galaxy.ansible.com/intro#meta gives some information about what additional info about authorship etc you can put into meta/main.yml

Thanks! I'll read up on the meta and get it updated.


Implement ability to choose output file

currently output file is set only to out.txt, I would like it to automatically set to the file currently assigned when the application is run, and also the ability to set it during runtime, i.e. a keybind or some sort of command. Will think about it.

The output filename now gets set to whatever is chosen when the program is run. I will implement the ability to change it at runtime once I implement a command mode.


Send both gratuitous ARP request and reply on VIP change.

@vholer Is "opennebula" sudoers file also updated? i.e. Cmnd_Alias ONE_NET = /sbin/brctl, /sbin/ebtables, /sbin/iptables, /sbin/ip6tables, /sbin/ip, /sbin/ipset, /usr/bin/arping

Yes.


HTML-Boiler Plate

Need to design the basic HTML design with the form needed.

Nav bar with login information, possible links to mental health resources
Footer with Groups git hub profile links
Form with Journal Title and entry fields.
Radio or some sort of drop down menu to select moods.

Completed initial draft for landing page


Do not show notification for non-confirmed bookings

closes #375 LiveURL: https://smartfaq-375-notification-update.surge.sh

Looks good!


Integration tests

Add e2e testing for Apple

We can use existing integration testing infrastructure: portal seeds and docker-compose that is used to test traffic flows. This will also allow to run those locally.


Showing error

246 packages are looking for funding
run npm fund for details
8 vulnerabilities (2 moderate, 6 high)
It is showing following error and I am unable to tackle it
Kindly help

Why is there no response at all to this ?  Is it a duplicate ?   Is it that developers could not reproduce it ?  It happens to me under  node v21.7.2 (npm v10.5.0). My OS is Ubuntu mantic. I simply run npx create-react-app my-app  and this error shows up, even though the message at the end is Success! Created my-app ... Happy hacking!. Also, if you run npm install just after, you get the same error message. It's kind of weird.

Good. I fix issues let me know if u need me

Why is there no response at all to this ? Is it a duplicate ? Is it that developers could not reproduce it ? It happens to me under node v21.7.2 (npm v10.5.0). My OS is Ubuntu mantic. I simply run npx create-react-app my-app and this error shows up, even though the message at the end is Success! Created my-app ... Happy hacking!. Also, if you run npm install just after, you get the same error message. It's kind of weird. OK, I checked the other issues and it is a duplicate of #13423 .

dont run on ubuntu


Add a side channel attack tutorial

Based on https://github.com/google/scaaml/tree/main/scaaml_intro add a tutorial for side channel attacks.

Part of #35

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.435%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
2313

Relevant Lines:
2676

💛  - Coveralls


Add distributed tracing for analyzing performance

Optionally configurable distributed tracing would be great to help debug slower requests.

@mmurto Would the traceId entry added in #875 fulfill your requirements? Given that the MDC propagation works everywhere, all log lines caused by an API request should now contain the traceID.

@mmurto Would the traceId entry added in #875 fulfill your requirements? Given that the MDC propagation works everywhere, all log lines caused by an API request should now contain the traceID.

Trace ID is a the first step there, thanks! Tracing also requires instrumenting functions (either automatically or manually) to create spans that use the same trace ID for the same call, and setting up the tracing provider that sends the traces to a tracing backend, like Grafana Tempo.

Is this something that the server has to actively support or something that users could configure in their infrastructure without code changes?

Code changes to the server are needed.


Recursive connected HyperRelations are not properly deleted

For example, a construction in renesca-magic:
@Node trait Connectable
@HyperRelation class Connects(startNode: Connectable, endNode: Connectable) extends Connectable

As a workaround, iteratively delete left-over HyperRelations:
match (c:CONNECTS) WHERE NOT (()-[:CONNECTABLETOCONNECTS]->(c) AND (c)-[:CONNECTSTOCONNECTABLE]->()) optional match
 (c)-[r]-() delete c,r return count(c)

Is this renesca-magic or renesca?

To me this is renesca. Eventhough, there is no notion of hyperrelations, we have the notion of paths, which is a connected set of nodes and relations that is matched in one query. So, also the deletion of a path is handled in renesca.
Still not sure, how to solve it.


What if the docker-compose file has a different name

Hi Philipp,
I followed your tutorial about getting the certificates up and running, and it's great. But I spent quite some time figuring out why it did not work for me initially. Turned out that it was because I have two different docker-compose files, "docker-compose.yml" for development and "docker-compose.prod.yml" for production. This made the init-letsencrypt.sh fail, as nginx and certbot does not exist in my development environment. So I had to change all the "docker-compose" commands to "docker-compose -f docker-compose.prod.yml" in init-letsencrypt.sh.
So I would propose that it is briefly mentioned alongside the following section to save others the headache I got, what's your thoughts?

Edit the script to add in your domain(s) and your email address. If you’ve changed the directories of the shared Docker volumes, make sure you also adjust the data_path variable as well.

Hey @knasti, thank you for the suggestion! I have included this feature in the 2.x branch. You can now call ./init-letsencrypt.sh -f you-docker-compose.yml :tada:


Duplicate data

Ran these command in ipython:
from opengraph import OpenGraph
og=OpenGraph("http://www.livemint.com/Industry/VlSovF4AGkwhupYQ2Ps3YN/Bschool-placements-Modest-rise-in-average-salary-offered.html")
og
og=OpenGraph("http://facebook.com")
og
output1:
{'locale:alternate': 'ja_JP', 'site_name': 'http://www.livemint.com/', 'description': 'Initial analysis of the ongoing placement season at IIMs and other top B-schools indicate that most salaries offered show a single digit growth over last year', 'title': 'B-school placements see modest salary growth, fewer offers from start-ups', 'url': 'http://www.livemint.com/Industry/VlSovF4AGkwhupYQ2Ps3YN/Bschool-placements-Modest-rise-in-average-salary-offered.html', 'image'<EMAIL_ADDRESS>'locale': 'hi_IN', 'type': 'article'}
output2:
{'locale:alternate': 'ja_JP', 'site_name': 'Facebook', 'description': 'Initial analysis of the ongoing placement season at IIMs and other top B-schools indicate that most salaries offered show a single digit growth over last year', 'title': 'B-school placements see modest salary growth, fewer offers from start-ups', 'url': 'https://www.facebook.com/', 'image': 'https://www.facebook.com/images/fb_icon_325x325.png', 'locale': 'hi_IN', 'type': 'article'}
description and title are same.

+1
OpenGraph isn't clearing the cached data each time.

As a workaround, you can manually reset the data object before you call it after the first time.
OpenGraph.__data__ = {}

Thanks for the help.


docs: Clarify that FlowControlSettings have a context-sensitive meaning.

(A follow-up PR in google-cloud-dotnet will clarify the meaning for Pub/Sub.)
This aims to help with the docs side of https://github.com/googleapis/google-cloud-dotnet/issues/10358

(Will wait for Amanda's review too. I'm starting on the google-cloud-dotnet part.)


Simplify and document aggressively.

Removes Client and Server and replaces them through flat functions
that are easier to understand.
Make reactor creation explicit to understand data flow in Tokio better
while reading the example.
Document the s*** out of the code to make this a literal code walk
that gets some of the core concepts of Tokio across in an easier to
understand way.

This is an opinionated change: I think this repo should be a tutorial that is easy to follow and read. I therefore removed unneeded helper structs (Server & Client) and implicit reactor creation - the reactor is a core concept of tokio, it should be up and front in a tutorial. What do you think?

Thanks for this. The work is much appreciated. I'm going to merge it as is.
What do you think about updating tokio-line to use Framed (https://github.com/tokio-rs/tokio-minihttp/blob/master/src/lib.rs#L32-L37). It would allow getting rid of all the buffer management work, but it would also hide some concepts.

Also... it looks like this broke on the latest Tokio master. I will work on fixing...

Merged: 1da66682162fa78fde24f52c888825aad067a9bd

Thanks for merging!

What do you think about updating tokio-line to use Framed (https://github.com/tokio-rs/tokio-minihttp/blob/master/src/lib.rs#L32-L37). It would allow getting rid of all the buffer management work, but it would also hide some concepts.

I was considering that - but I think from an educational point of view seeing a full protocol implementation is useful to grasp the concept - since it is so bare metal. I actually thought about how to handle this before and suggest a solution in a separate PR.


Bootstrap

Hello,
i use n3-charts with Twitter Bootstrap, but the chart doesn't resize, when the window is resizing.

        <linechart data="data" options="options"></linechart>

Hi @kevinkasper
here is an example using bootstrap http://embed.plnkr.co/nxFt1XnkJVa0dtoNA8J8/preview
This should work fine if you set the height attribute manually.
Let me know if this helps!
Best,
Christoph

Hi @chaosmail
thanks for quick reply. It works fine.
Best,
Kevin

Nice, please let me know if there are any other problems!
Best,
Christoph


Implement HTTP and ES DataLoaders

add HTTP data-loader
add ES data-loader
[experimental] resolve Ref and Fn::GetAtt dynamically (uses cfn-resolver-lib)

@marcoreni do you want to have a look at this?
thanks


Introducing tests

We definitely want to have tests on this as we're inching towards a non-beta release.
So I started :shipit:

thx for bringing this up. it's indeed super important to have test.
one requirement for introducing tests is to have one specific person being responsible for quality assurance in general, including tests and the related ongoing maintenance effort of keeping it updated. let's find that person first.


Publish TypeScript types along with package?

The repository has a index.d.ts file, but this is not published along with the library code to NPM> Is this possible to change? Typings are, at the moment, available from DefinitelyTyped, but they are outdated, and it looks like the maintainers of said registry are pretty overwhelmed at the moment.
Maybe it would be a good thing to help them out and ship typedefs with the package itself?

I'd definitely support this @tptee @ryan-roemer! Can take some time to do this if folks want to get me up to speed on our npm publishing process.

@parkerziegler -- Awesome. @tptee and/or I can definitely walk you through the publish process.
For this repo, I'm guessing:
$ npm version <major|minor|patch|ACTUAL_VERSION_NUMBER>
$ npm publish
$ git push && git push --tags

Also be sure to check with me before doing any of this that we have all the right permissions set up for you 😄

Thanks @ryan-roemer!  I'll ping you later today when I free up and we can coordinate 🚀

@jonasws The TypeScript defs should now ship with the package as of v15.1.0. Let me know if you hit any issues with accessing the types. Closing this issue for now.


OSPP: Implementation of a Class Incremental Learning Algorithm Evaluation System based on Ianvs

lgtm

/lgtm

/approve


feat: ability for fedimint-cli to call client modules

On top of #2028 , but I just realized it might conflict with client module refactoring, so putting it aside for a moment.

Codecov Report
Patch coverage has no change and project coverage change: -0.08 :warning:

Comparison is base (61402df) 62.55% compared to head (aaaaa2d) 62.47%.

:exclamation: Current head aaaaa2d differs from pull request most recent head f38b932. Consider uploading reports for the commit f38b932 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2030      +/-   ##
==========================================
- Coverage   62.55%   62.47%   -0.08%
==========================================
  Files         143      143
  Lines       28431    28448      +17
==========================================
- Hits        17784    17773      -11
- Misses      10647    10675      +28

Impacted Files
Coverage Δ

client/cli/src/lib.rs
0.18% <0.00%> (-0.01%)
:arrow_down:

fedimint-client/src/module/mod.rs
0.00% <0.00%> (ø)

... and 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.