Invalid Intent

Hi
I have tried the following code to call the app,
 var sApp = startApp.set({
      "action"      :  "ACTION_SEND",
      "category"    :  "CATEGORY_DEFAULT",
      "package"     :  "PACKAGE NAME",//The packageName of the app I want to open
      "intent"      :  "INTENT ID",//Name of the intent
      "intentstart" :  "startActivityForResult",
      "type"        :  "text/xml"
   }, { /* extras */
        "PID_OPTIONS":"PASS DATA"//Here i want to pass some xml data
   })

   sApp.start(function(result) { /* success */
        console.log("Success"+result);
   }, function(error) { /* fail */
        alert("error :"+error);
   });

I am getting "success callback result as OK", but I am getting toast message in my app as "Invalid intent code 999".
Can anyone help to resolve this issue?
Anyone can explain how to get the intent callback result?????

Hi!
Please, update plugin to 6.1.0 and check this code:
var sApp = startApp.set({
    "action"      :  "ACTION_SEND",
    "category"    :  "CATEGORY_DEFAULT",
    "package"     :  "PACKAGE NAME",//The packageName of the app I want to open
    "intent"      :  "INTENT ID",//Name of the intent
     "intentstart" :  "startActivityForResult",
   "type"        :  "text/xml"
}, { /* extras */
    "PID_OPTIONS":"PASS DATA"//Here i want to pass some xml data
}).start(function(result) { /* success */
    console.log("Success"+result);
}, function(error) { /* fail */
    alert("error :"+error);
}, function(result, requestCode, resultCode) {
    console.log(result, requestCode, resultCode);
});

Hi @lampaa
I have tried the following code to call the app,
              var sApp = startApp.set({
			"category":"CATEGORY_APP_MUSIC",
			"intentstart":"startActivity"
		}).start(function(result) { /* success */
			console.log("Success"+result);
		}, function(error) { /* fail */
			console.log("error :"+error);
		}, function(result, requestCode, resultCode) {
			console.log(result, requestCode, resultCode);
		});

I'm getting error :
error :class android.content.ActivityNotFoundException: No Activity found to handle Intent { cat=[android.intent.category.APP_MUSIC] }
Can anyone help to resolve this issue?
System Information
Ionic 1
Node 4.5.0
NPM 2.15.9
Cordova 6.5.0

Hi!
for start application to play music test this code:
var sApp = startApp.set({
    "action": "android.intent.action.MUSIC_PLAYER",
    "noParse": true
}).


Command "python setup.py egg_info" failed with error code 1

Installing requirements on Ubuntu server I get the following:
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-xgpuxZ/pynacl

Try pip install --upgrade pynacl

Thanks Washo, still same error though
On 7 Feb 2016, at 3:30 PM, Dr Washington Sanchez <notifications<EMAIL_ADDRESS>wrote:
Try pip install --upgrade pynacl

Reply to this email directly or view it on GitHubhttps://github.com/OpenBazaar/OpenBazaar-Server/issues/207#issuecomment-180949040.

@bitcoinbrisbane join us in our Slack group here so we can give you closer support: https://openbazaar-slackin-drwasho.herokuapp.com/


GET /deviation/embeddedcontent

The endpoint doesn't have mature content filter

We're aware of this and we may add the filter in next versions. For now, you can use the "is_mature" flag on deviation objects


Combobox Itemtemplate WinUI 3 Preview 4

I always get an error while adding an Itemtemplate to a combobox in winui preview 4.

This xaml in the mainwindow (.net5 for desktop) end with a error:
Exception thrown at 0x75BDA8B2 (KernelBase.dll) in WinUI3Test.exe: WinRT originate error - 0x8000FFFF : 'Catastrophic failure'.
onecore\com\combase\winrt\error\restrictederror.cpp(1016)\combase.dll!76832FD0: (caller: 767957D6) ReturnHr(3) tid(9ac) 8007007E The specified module could not be found.
Thanks for your help

@Dalli2602 thanks for the issue report, can you please include a repro app? It will help us track down the issue a lot.

Hello @StephenLPeters  thank you for your help. You could donload an project from here:
https://1drv.ms/u/s!AgKnNZZb6YimoNBTqgEpHMJiUzNLiQ?e=waaj79

This issue occurred to me as well, after going in rounds pulling my hair out, I found out that the reason was I set both the ItemTemplate and the DisplayMemberPath property.
Definitily did not expect a misterious 'Catastrophic failure' message.


low-power: add stop support for stm32l5

This PR adds support for the low-power modes STOP1 and STOP2.
In this image enable_debug_during_sleep is true (by default) and the power-consumption is around 700uA. This is already better than normal because of the sleep mode.

In this image enable_debug_during_sleep is set to false and the power-consumption is much lower (170uA). The blinky example has a pretty high interval (300ms). With a lower interval I tested a power-consumption of ~12uA (no wakeup in this measurement). With an interval of 1s I measured around 50uA (active led uses 60uA).

LGTM! Can you fix CI?


Add docs about installing Flamingo via a HelmRelease and a Helm chart

Running into the same problem - did you manage to do it?

Please advise how to install via HelmRelease.

Added to README: https://github.com/flux-subsystem-argo/flamingo?tab=readme-ov-file#install-flamingo-with-helmrelease


Allow to specify a callback that is executed once submit was called and

use it for clearing the IovArrays
Motivation:
IOUringSubmissionQueue may call submit() internally when there is no
space left in the buffer. Once this is done we can reuse for example
IovArrays etc. Because of this its useful to be able to specify a
callback that is executed after submission
Modifications:

Allow to specify a Runnable that is called once submission was
complete
Use this callback to clear the IovArrays

Result:
IovArrays are automatically cleared on each submit call.

Thanks @njhill for the nice idea :)

/cc @1Jo1

The test failure is not related at all....


Uncomment skipped rex pytests

The aim of the pr is to triage the currently skipped rex pytests and link to issues and or fix whatever is possible in the scope of this pr.

@ayushdg seems like this fixes several tests. Do you want to merge with upstream and have it reviewed now or want to work on it more to get all tests in test_rex.py passing?

I plan on triaging a few more tests and link to issues for those tests before marking this ready for review.

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@accde51). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #661   +/-   ##
=========================================================
  Coverage                          ?   66.82%
=========================================================
  Files                             ?       73
  Lines                             ?     3635
  Branches                          ?      747
=========================================================
  Hits                              ?     2429
  Misses                            ?     1061
  Partials                          ?      145

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Granular dam break example

Description of the problem

There was only a single example with DEM that had moving geometries

Description of the solution

Add a granular dam break example. It's not the richest example ever, but it is quite simple and straightforward and I appreciate that of it. There is also a small comparison with experimental results and the agreement is quite good even though I had to scale up the particles significantly. The example is also very fast to run (8 minutes on my computer)

Documentation

Example is fully documented

Future changes

Could be interesting to try with more than one height.  Will do this as an addendum in following days

Comments

I have a few examples like this in the oven, will make PRs with them soon.

@lpsaavedra Ready for a last look :)

Just a few minor comments and then it should be ready to go :)
I still think that we should add the reference at the end of the example in an additional section, like in the other DEM examples (e.g., rectangular hopper), just to keep the same format everywhere.

Sorry I had forgotten about the reference comment. You are absolutely right, I added the reference at the end of the example. I also found a link that gives access to a PDF so I used this one instead :).
Everything should be all good now.


Config test button

Currently the only way to determine if you have setup the webhook correctly is to wait until you get a rare drop. Potentially add a button on the plugin settings to push a message to discord to confirm everything is working as intended?
If this exists already please ignore

We're thinking of not implementing this, opens up an very easy way to spam a server & you can just change your other settings to a lower value and kill something to test the webhook url.

@izaakgray feel free to continue commenting here. Might re-open after discussion

If the issue is spamming channels surely couldn't people just do that by setting their rarity/value to a value that would spam a channel with drops? Could just implement a cooldown on how often you can send messages via a test config button.
The reason i asked is that it seemed inconsistent on what drops would be posted with a 1/1 and 1gp rarity/value setting. I'm assuming its only items with a listed rarity value on the wiki that are posted? Was just a minor headache when getting people in my discord server to adopt this plugin and set it up correctly without a way to check if they did it correctly instantly.


Update Composer dependencies (2023-04-29-00-12)

Visual regression test passed!
View the visual regression test report


Error fetching event without a call

[SubsquidAdapter] getEvents: TypeError: Cannot read properties of null (reading 'argsStr')

Fixed in development branch, will go to main in next update


Add "Enable GPU hardware acceleration" option

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Please provide the following information:
Summary
Add "Enable GPU hardware acceleration" option.
It's enabled by default.
Issue link
#713
Test Cases

config.json (covered by CI)

enableHardwareAcceleration key is saved when clicking the option in the settings page.

Actual process

Set Enable GPU hardware acceleration to disabled.
Restart the app.
Check running mattermost-desktop processes.
Processes which have an argument --type=gpu-process should not exist.

Additional Notes
https://circleci.com/gh/yuya-oc/desktop/696#artifacts

Tested own build and CI-Build on Win 10 Pro x64 with AMD 18.3.1 Drivers and no problems so far, toggled GPU acceleration on and off a few times.
Will test Linux (Fedora 27) tomorrow morning and report back.

Great! Thanks @yuya-oc
Tested on Mac, one of the three Mattermost processes is removed after disabling the acceleration. I'll use the app with acceleration disabled today to see if there are any issues, but ready to merge from my side.
@amyblais please help test on Windows?

Tested on Windows as well and saw no issues either.

I think this one is good to merge then @yuya-oc. Hopefully it helps with the blank page issues

In my Ubuntu 16.04 VM, such process did not originally exist. Possibly because it's VM and hardware acceleration doesn't work well. However it's effective on other OS, so I think it's good to merge.


[tftrt update]

Added support for TRT plugin during conversion

converter & shape inference are now aware of plugin factory.
PluginTensorRT

wrapper for nvinfer1::IPlugin
base class for custom plugins
provides serialization/deserialization of plugin op type & input tensor dimensions

PluginFactoryTensorRT

wrapper for nvinfer1::PluginFactory
singleton with plugin registration, allow user to register plugin op type (string), plugin construction function & plugin deserialization function.
owns constructed & deserialized plugins.

Unit tests for plugin registration

compatible with TRT 3.0.4 plugin API.
future plugin API changes willl be updated.

@aaroey

Updated the description.
Added unit test.
Let me know if we want more details & examples here @aaroey .

I didn't enable the custom_plugin_examples as default.
Will do that for following PRs when I wrapped TensorRT official plugins that comes with TRT package (nvplugins)

Hi @jjsjann123,
There seems to be conflicts, would you help to resolve them? After that I'll import this PR to test.
Thanks. :)

Resolved conflicts and comments.
Feel free to ping me if there's issue with internal build. :)

Seems like the CI build is complaining about SWIG? Seems to have issue with importing tensorrt and my SWIG interface calling tensorflow::tensorrt::RegisterIncOpPlugin(). Build on local machine is working.
Any hint on how to fix this?

Hi @jjsjann123,
Sorry for the delay, I was distracted by some internal trt build problems and is still working on it. Is this PR urgent? If not, may I take a look at it later this week?
Thanks.

Yay~~~
@aaroey Thanks a lot for handling internal build errors and the format issue 💯


added GH action

#5 Updated the repo with GH action.
Please update and review the PR.

@rishvantsingh Thanks for your great work. See the comment I made, once that is addressed I can merge it. Great work 👍🏽

Thankyou so much @AlvinKuruvilla

HI @AlvinKuruvilla . Where have you commented?

Check the PR on GitHub I have made a comment that for this project I am using the black formatted not flake8 so I was wondering if you could change that in the workflow
On Mar 8, 2022, 13:24 -0500, Rishivant Singh @.***>, wrote:

HI @AlvinKuruvilla . Where have you commented?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @AlvinKuruvilla . I have updated the workflow as per your need. Please review and merge it.


Types List support

What changes were proposed in this pull request?
Types List support
How was this patch tested?
unit + manual
Quick checklist
The following checklist helps ensure your PR is complete:

[x] Eclipse Contributor Agreement signed, and signed commits - see IP Requirements page for details
[x] Reviewed the Contributing Guidelines and followed the steps within.
[x] Created tests for any significant new code additions.
[x] Relevant tests for your changes are passing.

documentation was added inside types.h


Claims not returned for users with email as username - userinfo endpoint

Describe the issue:
After the fix provided by the PR, the username will be obtained as follows.
username = accessTokenDO.getAuthzUser().getUserName();

The returned username will be a tenant aware username. (It will return<EMAIL_ADDRESS>for the user, user1@mail.com@dom.com). Then the user claims will be retrieved as follows.
Map<String, String> userClaims = userstore.getUserClaimValues(MultitenantUtils.getTenantAwareUsername
                (username), claimURIList.toArray(new String[claimURIList.size()]), null);

However, since the above username is already a tenant aware username, when we invoke the MultitenantUtils.getTenantAwareUsername for the returned username (user1@mail.com), it will consider mail.com as a tenant domain and will return the username: user1.
Since there is no such user with the username user1, the userClaims will be empty.

Product Version: IS 5.7.0

Fixed with https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/1405


Futures attempt to execute threads directly if those have not started executing

adding new API function hpx::threads::get_outer_self_id

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a9512ad8af289c7830b2ab8fcc437a2bfad221ab506HPX Datetime2022-05-31T12:57:29+00:002022-12-08T14:00:01+00:00Datetime2022-05-31T15:13:01.357969+02:002022-12-08T15:17:48.968956+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.0ClusternamedaintdaintEnvfileHostnamenid01193nid01598ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a9512ad8af289c7830b2ab8fcc437a2bfad221ab506HPX Datetime2022-05-31T12:57:29+00:002022-12-08T14:00:01+00:00Datetime2022-05-31T15:13:18.026239+02:002022-12-08T15:18:06.081889+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.0ClusternamedaintdaintEnvfileHostnamenid01193nid01598ComparisonBENCHMARKFORK_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 Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a12ad8af289c7830b2ab8fcc437a2bfad221ab506HPX Datetime2021-11-10T19:14:21+00:002022-12-08T14:00:01+00:00Datetime2021-11-10T20:28:18.266961+01:002022-12-08T15:18:21.342210+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.0ClusternamedaintdaintEnvfileHostnamenid00120nid01598Explanation 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 Datetime2022-05-31T12:57:29+00:002022-12-08T17:30:39+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95138dae8014198bcbdfa7c6dd66bf6bd155a9e0e3Datetime2022-05-31T15:13:01.357969+02:002022-12-08T18:48:17.538240+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.0ClusternamedaintdaintHostnamenid01193nid00097EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-12-08T17:30:39+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95138dae8014198bcbdfa7c6dd66bf6bd155a9e0e3Datetime2022-05-31T15:13:18.026239+02:002022-12-08T18:48:33.891186+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.0ClusternamedaintdaintHostnamenid01193nid00097EnvfileComparisonBENCHMARKFORK_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-12-08T17:30:39+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a138dae8014198bcbdfa7c6dd66bf6bd155a9e0e3Datetime2021-11-10T20:28:18.266961+01:002022-12-08T18:48:49.290784+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.0ClusternamedaintdaintHostnamenid00120nid00097EnvfileExplanation 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 Commitd5655f89770ba953e8de3ceb349567d5fcb74a9564783acfd40ccbe49a6a49f81b5c8f17178f0812HPX Datetime2022-05-31T12:57:29+00:002022-12-10T23:51:35+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.0Hostnamenid01193nid01030Datetime2022-05-31T15:13:01.357969+02:002022-12-11T01:06:43.939432+01:00ClusternamedaintdaintEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a9564783acfd40ccbe49a6a49f81b5c8f17178f0812HPX Datetime2022-05-31T12:57:29+00:002022-12-10T23:51:35+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.0Hostnamenid01193nid01030Datetime2022-05-31T15:13:18.026239+02:002022-12-11T01:06:59.960993+01:00ClusternamedaintdaintEnvfileComparisonBENCHMARKFORK_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 Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a64783acfd40ccbe49a6a49f81b5c8f17178f0812HPX Datetime2021-11-10T19:14:21+00:002022-12-10T23:51:35+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.0Hostnamenid00120nid01030Datetime2021-11-10T20:28:18.266961+01:002022-12-11T01:07:15.316774+01:00ClusternamedaintdaintEnvfileExplanation 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 Datetime2022-05-31T12:57:29+00:002022-12-11T17:51:39+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95954baafba240b5a1e2b78a3e13862cc1bf523d72ClusternamedaintdaintCompiler/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.0Datetime2022-05-31T15:13:01.357969+02:002022-12-11T19:07:45.281830+01:00EnvfileHostnamenid01193nid00016ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-12-11T17:51:39+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95954baafba240b5a1e2b78a3e13862cc1bf523d72ClusternamedaintdaintCompiler/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.0Datetime2022-05-31T15:13:18.026239+02:002022-12-11T19:08:01.937971+01:00EnvfileHostnamenid01193nid00016ComparisonBENCHMARKFORK_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-12-11T17:51:39+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a954baafba240b5a1e2b78a3e13862cc1bf523d72ClusternamedaintdaintCompiler/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.0Datetime2021-11-10T20:28:18.266961+01:002022-12-11T19:08:17.388211+01:00EnvfileHostnamenid00120nid00016Explanation 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 Datetime2022-05-31T12:57:29+00:002022-12-16T13:22:56+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a959f76f753f634bd157efce1c44debd1a373dd51c4EnvfileCompiler/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.0Datetime2022-05-31T15:13:01.357969+02:002022-12-16T14:45:25.112446+01:00Hostnamenid01193nid00029ClusternamedaintdaintComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002022-12-16T13:22:56+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a959f76f753f634bd157efce1c44debd1a373dd51c4EnvfileCompiler/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.0Datetime2022-05-31T15:13:18.026239+02:002022-12-16T14:45:41.426001+01:00Hostnamenid01193nid00029ClusternamedaintdaintComparisonBENCHMARKFORK_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-12-16T13:22:56+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a9f76f753f634bd157efce1c44debd1a373dd51c4EnvfileCompiler/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.0Datetime2021-11-10T20:28:18.266961+01:002022-12-16T14:45:56.800708+01:00Hostnamenid00120nid00029ClusternamedaintdaintExplanation 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-16T23:14:48+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4d380f081ad47f17328c7eae3731b589881f1af2Datetime2023-01-13T04:10:15.951027-06:002023-01-16T17:19:49.296830-06:00Compiler/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.eduClusternamerostamrostamEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch?InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-16T23:14:48+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4d380f081ad47f17328c7eae3731b589881f1af2Datetime2023-01-13T04:10:31.068958-06:002023-01-16T17:20:04.576825-06:00Compiler/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.eduClusternamerostamrostamEnvfileComparisonBENCHMARKFORK_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-16T23:14:48+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4d380f081ad47f17328c7eae3731b589881f1af2Datetime2023-01-13T04:10:46.398919-06:002023-01-16T17:20:20.331395-06:00Compiler/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.eduClusternamerostamrostamEnvfileExplanation 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 Datetime2022-05-31T12:57:29+00:002023-01-16T23:14:48+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a954d380f081ad47f17328c7eae3731b589881f1af2EnvfileDatetime2022-05-31T15:13:01.357969+02:002023-01-17T00:25:47.084751+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.0ClusternamedaintdaintHostnamenid01193nid01540ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2022-05-31T12:57:29+00:002023-01-16T23:14:48+00:00HPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a954d380f081ad47f17328c7eae3731b589881f1af2EnvfileDatetime2022-05-31T15:13:18.026239+02:002023-01-17T00:26:06.513032+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.0ClusternamedaintdaintHostnamenid01193nid01540ComparisonBENCHMARKFORK_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:002023-01-16T23:14:48+00:00HPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a4d380f081ad47f17328c7eae3731b589881f1af2EnvfileDatetime2021-11-10T20:28:18.266961+01:002023-01-17T00:26:23.184021+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.0ClusternamedaintdaintHostnamenid00120nid01540Explanation 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 Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2023-01-12T23:07:58+00:002023-01-17T13:06:58+00:00EnvfileDatetime2023-01-13T04:10:15.951027-06:002023-01-17T07:14:31.494532-06:00ClusternamerostamrostamHostnamemedusa08.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 Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2023-01-12T23:07:58+00:002023-01-17T13:06:58+00:00EnvfileDatetime2023-01-13T04:10:31.068958-06:002023-01-17T07:14:47.052988-06:00ClusternamerostamrostamHostnamemedusa08.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 Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee4a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2023-01-12T23:07:58+00:002023-01-17T13:06:58+00:00EnvfileDatetime2023-01-13T04:10:46.398919-06:002023-01-17T07:15:02.815157-06:00ClusternamerostamrostamHostnamemedusa08.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 Commitd5655f89770ba953e8de3ceb349567d5fcb74a954a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2022-05-31T12:57:29+00:002023-01-17T13:06:58+00:00Hostnamenid01193nid01193Datetime2022-05-31T15:13:01.357969+02:002023-01-17T14:23:14.438384+01:00EnvfileCompiler/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.0ClusternamedaintdaintComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a954a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2022-05-31T12:57:29+00:002023-01-17T13:06:58+00:00Hostnamenid01193nid01193Datetime2022-05-31T15:13:18.026239+02:002023-01-17T14:23:34.131075+01:00EnvfileCompiler/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.0ClusternamedaintdaintComparisonBENCHMARKFORK_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 Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a4a0e5d72959a042ca72401e8dc50f50340a4bbb8HPX Datetime2021-11-10T19:14:21+00:002023-01-17T13:06:58+00:00Hostnamenid00120nid01193Datetime2021-11-10T20:28:18.266961+01:002023-01-17T14:23:49.289395+01:00EnvfileCompiler/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.0ClusternamedaintdaintExplanation 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-27T22:40:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee8d58e5f650296f8346e87b4648311108cf0acee1Hostnamemedusa08.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.1Datetime2023-01-13T04:10:15.951027-06:002023-01-27T16:50:01.016997-06:00ClusternamerostamrostamComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-27T22:40:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee8d58e5f650296f8346e87b4648311108cf0acee1Hostnamemedusa08.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.1Datetime2023-01-13T04:10:31.068958-06:002023-01-27T16:50:22.114559-06:00ClusternamerostamrostamComparisonBENCHMARKFORK_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-27T22:40:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee8d58e5f650296f8346e87b4648311108cf0acee1Hostnamemedusa08.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.1Datetime2023-01-13T04:10:46.398919-06:002023-01-27T16:50:37.213667-06:00ClusternamerostamrostamExplanation 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-01-27T22:40:19+00:00HPX Commitd4827232e3d49d63f41287db1e8b5767b6dbd95f8d58e5f650296f8346e87b4648311108cf0acee1ClusternamedaintdaintCompiler/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.0EnvfileHostnamenid00267nid00457Datetime2023-01-12T16:07:32.649261+01:002023-01-27T23:55:49.745417+01:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Datetime2023-01-18T08:41:20+00:002023-01-27T22:40:19+00:00HPX Commitda01e78993b6bb8da476492b2770f1cc3f1179958d58e5f650296f8346e87b4648311108cf0acee1ClusternamedaintdaintCompiler/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.0EnvfileHostnamenid00005nid00457Datetime2023-01-18T09:57:57.669847+01:002023-01-27T23:56:09.606769+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 Datetime2023-01-17T08:25:42+00:002023-01-27T22:40:19+00:00HPX Commit52952d870ab05881c0ef01bde746b95bf5e74ef08d58e5f650296f8346e87b4648311108cf0acee1ClusternamedaintdaintCompiler/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.0EnvfileHostnamenid00005nid00457Datetime2023-01-17T09:44:28.090718+01:002023-01-27T23:56:25.057154+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-02-09T21:28:31+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee5c81e06b75998c088d923b82983aecf5310123f2Datetime2023-01-13T04:10:15.951027-06:002023-02-09T15:34:46.837597-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-02-09T21:28:31+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee5c81e06b75998c088d923b82983aecf5310123f2Datetime2023-01-13T04:10:31.068958-06:002023-02-09T15:35:08.022548-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-02-09T21:28:31+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4ee5c81e06b75998c088d923b82983aecf5310123f2Datetime2023-01-13T04:10:46.398919-06:002023-02-09T15:35:24.770436-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 Commitd4827232e3d49d63f41287db1e8b5767b6dbd95fad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-12T14:41:15+00:002023-02-09T21:35:39+00: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.0EnvfileHostnamenid00267nid01323Datetime2023-01-12T16:07:32.649261+01:002023-02-09T22:47:50.655473+01:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f117995ad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-18T08:41:20+00:002023-02-09T21:35:39+00: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.0EnvfileHostnamenid00005nid01323Datetime2023-01-18T09:57:57.669847+01:002023-02-09T22:48:09.874857+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 Commit52952d870ab05881c0ef01bde746b95bf5e74ef0ad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-17T08:25:42+00:002023-02-09T21:35:39+00: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.0EnvfileHostnamenid00005nid01323Datetime2023-01-17T09:44:28.090718+01:002023-02-09T22:48:24.997869+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 Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eead9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-12T23:07:58+00:002023-02-09T21:35:39+00:00Datetime2023-01-13T04:10:15.951027-06:002023-02-09T15:50:06.540326-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch??InfoPropertyBeforeAfterHPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eead9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-12T23:07:58+00:002023-02-09T21:35:39+00:00Datetime2023-01-13T04:10:31.068958-06:002023-02-09T15:50:27.491691-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileComparisonBENCHMARKFORK_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 Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eead9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-12T23:07:58+00:002023-02-09T21:35:39+00:00Datetime2023-01-13T04:10:46.398919-06:002023-02-09T15:50:43.276341-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileExplanation 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 Commitd4827232e3d49d63f41287db1e8b5767b6dbd95fad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-12T14:41:15+00:002023-02-09T21:35:39+00:00EnvfileCompiler/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-09T23:31:23.741205+01:00ClusternamedaintdaintHostnamenid00267nid00434ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch--InfoPropertyBeforeAfterHPX Commitda01e78993b6bb8da476492b2770f1cc3f117995ad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-18T08:41:20+00:002023-02-09T21:35:39+00:00EnvfileCompiler/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-09T23:31:42.831073+01:00ClusternamedaintdaintHostnamenid00005nid00434ComparisonBENCHMARKFORK_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 Commit52952d870ab05881c0ef01bde746b95bf5e74ef0ad9a6bb28b75813a045bd8c205cc3aacffe4731aHPX Datetime2023-01-17T08:25:42+00:002023-02-09T21:35:39+00:00EnvfileCompiler/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-09T23:31:57.889928+01:00ClusternamedaintdaintHostnamenid00005nid00434Explanation 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-03-06T15:59:25+00:002023-05-05T11:23:07+00:00HPX Commit6b6e1e71343e80ad04bf610e41c26a41c1f373338839d700097c4339e2cc889ea88ce801a47f7c56ClusternamerostamrostamDatetime2023-03-10T03:27:49.135034-06:002023-05-05T06:29:52.814171-05: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.1EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Datetime2023-03-06T15:59:25+00:002023-05-05T11:23:07+00:00HPX Commit6b6e1e71343e80ad04bf610e41c26a41c1f373338839d700097c4339e2cc889ea88ce801a47f7c56ClusternamerostamrostamDatetime2023-03-10T03:28:21.991297-06:002023-05-05T06:30:25.300395-05: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.1EnvfileComparisonBENCHMARKFORK_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-03-06T15:59:25+00:002023-05-05T11:23:07+00:00HPX Commit6b6e1e71343e80ad04bf610e41c26a41c1f373338839d700097c4339e2cc889ea88ce801a47f7c56ClusternamerostamrostamDatetime2023-03-10T03:28:29.145749-06:002023-05-05T06:30:32.592345-05: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.1EnvfileExplanation 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 Commit6b6e1e71343e80ad04bf610e41c26a41c1f37333565748ebd0a48e877140001568d1c8e793ae6d67HPX Datetime2023-03-06T15:59:25+00:002023-05-05T19:51:25+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-03-10T03:27:49.135034-06:002023-05-05T15:38:59.539708-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Commit6b6e1e71343e80ad04bf610e41c26a41c1f37333565748ebd0a48e877140001568d1c8e793ae6d67HPX Datetime2023-03-06T15:59:25+00:002023-05-05T19:51:25+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-03-10T03:28:21.991297-06:002023-05-05T15:39:32.565664-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKFORK_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 Commit6b6e1e71343e80ad04bf610e41c26a41c1f37333565748ebd0a48e877140001568d1c8e793ae6d67HPX Datetime2023-03-06T15:59:25+00:002023-05-05T19:51:25+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-03-10T03:28:29.145749-06:002023-05-05T15:39:39.892124-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileExplanation 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…

The latest commit addresses the following race contition on the runs_child_ variable:
Here is future_data::set_value(). The modification (resetting) of runs_child_ happens under a lock. This is alright:
https://github.com/STEllAR-GROUP/hpx/blob/0ad30ef89b666f557de3a91902e745a08a3abe6f/libs/core/futures/include/hpx/futures/detail/future_data.hpp#L559-L561
However, there was a race condition which happened when a scheduled thread was executed very rapidly. Here's the code that schedules a thread:
https://github.com/STEllAR-GROUP/hpx/blob/3236b2fd7c82e56917c0e37d1ecaa92a3097f6fd/libs/core/futures/include/hpx/futures/packaged_continuation.hpp#L233-L237
this->runs_child_ = spawner(...) is supposed to keep a reference of the scheduled thread.
When the scheduled thread was executed very quickly, this->runs_child_ = spawner(...) could run at the same time (or after) future_data::set_value().
Thus, there was a race condition between runs_child_.reset() and runs_child_ = spawner(...) .
Here's the fix I applied:
https://github.com/STEllAR-GROUP/hpx/blob/0ad30ef89b666f557de3a91902e745a08a3abe6f/libs/core/futures/include/hpx/futures/packaged_continuation.hpp#L239-L243
Firstly, I added a lock to prevent concurrent modification of runs_child_.
I also added a check for future_data::is_ready(), ensuring we don't keep an unneeded reference to the scheduled thread (in case it has been already executed).
Let's hope this makes things better

I also noticed that the code below does not check whether there is a thread_execution_hint::run_as_child hint.
https://github.com/STEllAR-GROUP/hpx/blob/3236b2fd7c82e56917c0e37d1ecaa92a3097f6fd/libs/core/futures/include/hpx/futures/packaged_continuation.hpp#L233-L237
I'm not sure if that was intentional, but my instinct is that we would also want to enable/disable it here depending on the hint.

I also noticed that the code below does not check whether there is a thread_execution_hint::run_as_child hint.
https://github.com/STEllAR-GROUP/hpx/blob/3236b2fd7c82e56917c0e37d1ecaa92a3097f6fd/libs/core/futures/include/hpx/futures/packaged_continuation.hpp#L233-L237
I'm not sure if that was intentional, but my instinct is that we would also want to enable/disable it here depending on the hint.

I'd need to look closer, but I believe this is only called after the check has happened before in other places.

I'd need to look closer, but I believe this is only called after the check has happened before in other places.

I did my learning/testing on the cross_pool_injection example. The .then would lead to those lines executing, even with no hint placed anywhere.

Firstly, I added a lock to prevent concurrent modification of runs_child_.
I also added a check for future_data::is_ready(), ensuring we don't keep an unneeded reference to the scheduled thread (in case it has been already executed).

@Pansysk75 please check my commit. I think I was able to remove this lock.

I'd need to look closer, but I believe this is only called after the check has happened before in other places.

I did my learning/testing on the cross_pool_injection example. The .then would lead to those lines executing, even with no hint placed anywhere.
Also now that I think about it, the lock could be avoided if the thread was first "registered" (ie created in a suspended state so that we get a thread_id) and then executed/resumed separately. I think I saw that someplace in this PR

In that case we will need to add the check here as well.

I'm not quite sure what we should do here. If we left this as is we would loose the direct execution optimization in the worst case...

@Pansysk75 I enabled the new feature on gcc10, clang11, and clang12 and now we see hangs: tests.unit.modules.resource_partitioner.suspend_thread and tests.unit.modules.resource_partitioner.suspend_thread_external hang :/

@Pansysk75 I enabled the new feature on gcc10, clang11, and clang12 and now we see hangs: tests.unit.modules.resource_partitioner.suspend_thread and tests.unit.modules.resource_partitioner.suspend_thread_external hang :/

I'll have a look

@Pansysk75 FWIW, my last commit has improved things, but not entirely fixed the hangs.

@Pansysk75 the next error (segfault) happens in suspend_pool_external, however I'm not able to reproduce it locally. Could you try that, please?

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??-InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-07-23T16:57:02+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2c782734c1c6622f9ec62ec8365051c6912e2db86Datetime2023-05-10T14:50:18.616050-05:002023-07-23T12:05:18.603724-05: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-05-10T12:07:53+00:002023-07-23T16:57:02+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2c782734c1c6622f9ec62ec8365051c6912e2db86Datetime2023-05-10T14:52:35.047119-05:002023-07-23T12:07:34.168265-05: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-05-10T12:07:53+00:002023-07-23T16:57:02+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2c782734c1c6622f9ec62ec8365051c6912e2db86Datetime2023-05-10T14:52:52.237641-05:002023-07-23T12:07:51.495519-05: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…

@Pansysk75 the next error (segfault) happens in suspend_pool_external, however I'm not able to reproduce it locally. Could you try that, please?

Copying the exact setup on Rostam did it for me.
That means doing
source src/.jenkins/lsu/env-gcc-10.sh
building with
-DHPX_WITH_PARALLEL_TESTS_BIND_NONE=ON -DCMAKE_BUILD_TYPE=Debug -DHPX_WITH_CHECK_MODULE_DEPENDENCIES=ON -DHPX_WITH_PARCELPORT_COUNTERS=ON -DLCI_DEBUG=ON -DHPX_WITH_CXX_STANDARD=17 -DHPX_WITH_MALLOC=system -DHPX_WITH_FETCH_ASIO=ON -DHPX_WITH_ASIO_TAG=asio-1-12-0 -DHPX_WITH_COMPILER_WARNINGS=ON -DHPX_WITH_COMPILER_WARNINGS_AS_ERRORS=ON -DHPX_WITH_PARCELPORT_MPI=ON -DHPX_WITH_PARCELPORT_LCI=ON -DHPX_WITH_FETCH_LCI=ON -DHPX_COROUTINES_WITH_THREAD_SCHEDULE_HINT_RUNS_AS_CHILD=ON
and executing
bin/suspend_thread_external_test --hpx:ini=hpx.stacks.use_guard_pages=0 --hpx:bind=none
Now, the segfault stack trace points at the catch part of the following try-catch block:
https://github.com/STEllAR-GROUP/hpx/blob/09eabc71da8f2a150b2e26efe3d52d4163e49072/libs/core/thread_pools/include/hpx/thread_pools/scheduled_thread_pool_impl.hpp#L314-L362
It seems like std::thread() (inside ofadd_processing_unit_internal() call,  L338) occasionally throws a "Resource temporarily unavailable".
I guess we are not handling that properly, as stop_locked(l) (L358) leads to Scheduler::get_thread_count() being called, and it trying to read uninitialized data.
That's all for now, hope it helps!

@Pansysk75 thanks a lot for this analysis. Nw the next question is why does it throw that exception to begin with? There has to be a reason.

@Pansysk75 thanks a lot for this analysis. Now the next question is why does it throw that exception to begin with? There has to be a reason.

I wrote a script that monitors the amount of memory mappings (using the pmap utility).
Looks like std::thread fails when we have more mappings than specified by /proc/sys/vm/max_map_count (currently 65530 on Rostam).
Increasing  /proc/sys/vm/max_map_count or decreasing the amount of allocations would allow the tests to complete successfully. The failing tests spawn an absurd amount of futures, so it seems sensible to just limit the amount of futures spawned.

@hkaiser Here's what I see happening:
Work started without the hint, gets scheduled through register_work, which does not directly create a thread object, but only adds the thread descripition to Scheduler.new_data_. That keeps the amount of allocations low, because the allocated stack memory can be reused.
Work started with the runs_as_child hint gets handled through register_thread, which leads to Scheduler::create_thread always creating the thread object (and allocating the memory for it). So if a bulk of tasks (ie through hpx::async) are created, we immediately do as many stack allocations as there are threads created, and there is no chance for memory recycling to happen
So, the exessive memory usage is not a bug, rather it's a design issue. I remember you telling me about how you wanted to delay the thread allocation, now I get why that could be a good idea :)

@hkaiser Here's what I see happening:
Work started without the runs_as_child hint, gets scheduled through register_work, which does not directly create a thread object, but only adds the thread descripition to Scheduler.new_data_. The actual thread will be allocated/created when the Scheduler starts running out of threads in the queues. That keeps the amount of allocations low, because, since the threads are created on an as-needed basis, the allocated thread-stack memory can be reused.
Work started with the runs_as_child hint gets handled through register_thread, which leads to Scheduler::create_thread always creating the thread object (and allocating the memory for it). So if a bulk of tasks are created (ie through a ton of calls of hpx::async), we immediately do as many stack allocations as there are threads created, and there is no chance for memory recycling to happen
So, the exessive memory usage is not a bug, rather it's a design issue. I remember you telling me about how you wanted to delay the thread allocation, now I get why that could be a good idea :)

Yes, that's it! Very nice analysis! The creation of a thread with the hint uses register_thread instead of register_work as we need the thread id. A possible solution would be (as you said) to recycle the stacks separately from the thread objects, possibly we can even avoid recycling the thread objects themselves, just the stacks. Another solution could be to delay storing the thread_id until the thread is actually created.

Although disabling run_as_child decreases allocations by a lot, here is still a memory-leak-like issue arising with hpx:ini=hpx.stacks.use_guard_pages=0. I'm investigating it rn.

That would explain why the suspend_runtime et.al. now fail even for builders that don't enable the run_as_child hint by default.

That would explain why the suspend_runtime et.al. now fail even for builders that don't enable the run_as_child hint by default.

Here, does mmap-ing memory of (size + EXEC_PAGESIZE)  make sense even if we are not using guard pages?
https://github.com/STEllAR-GROUP/hpx/blob/dd17010adf02cdab681d96f10f96626d476459c0/libs/core/coroutines/include/hpx/coroutines/detail/posix_utility.hpp#L84-L96
Deallocation seems to not take EXEC_PAGESIZE into account if we don't use guard pages:
https://github.com/STEllAR-GROUP/hpx/blob/dd17010adf02cdab681d96f10f96626d476459c0/libs/core/coroutines/include/hpx/coroutines/detail/posix_utility.hpp#L156-L172

Excellent catch! Could you patch that, please?

Excellent catch! Could you patch that, please?

Thank you, I'll do that :)

I'm also preparing a change right now that starts deleting stack segments of recycled threads once more then a certain number of threads have been recycled. That should keep the amount of memory allocated down a bit as well.

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??(=)InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-07-28T19:24:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2f3f8ff1cfd76c39b99d67cf3dfc76c9cddbb9064Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:50:18.616050-05:002023-07-28T14:30:05.676471-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch---InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-07-28T19:24:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2f3f8ff1cfd76c39b99d67cf3dfc76c9cddbb9064Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:52:35.047119-05:002023-07-28T14:58:06.050998-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamComparisonBENCHMARKFORK_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-05-10T12:07:53+00:002023-07-28T19:24:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b2f3f8ff1cfd76c39b99d67cf3dfc76c9cddbb9064Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:52:52.237641-05:002023-07-28T14:58:23.094324-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileClusternamerostamrostamExplanation 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 Commitdcb541576898d370113946ba15fb58c20c8325b28e94a223de1d11702519c1f69224d9fd60b77430HPX Datetime2023-05-10T12:07:53+00:002023-07-28T23:20:37+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-05-10T14:50:18.616050-05:002023-07-28T18:30:19.100757-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch---InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b28e94a223de1d11702519c1f69224d9fd60b77430HPX Datetime2023-05-10T12:07:53+00:002023-07-28T23:20:37+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-05-10T14:52:35.047119-05:002023-07-28T18:58:30.325592-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKFORK_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 Commitdcb541576898d370113946ba15fb58c20c8325b28e94a223de1d11702519c1f69224d9fd60b77430HPX Datetime2023-05-10T12:07:53+00:002023-07-28T23:20:37+00:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1Datetime2023-05-10T14:52:52.237641-05:002023-07-28T18:58:47.228080-05:00ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileExplanation 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…

@Pansysk75 your fix did the trick! I will roll back my change that limits the numer of recycled stacks as it made the performance tests fail. Let's see if after that change things will be still green.

@Pansysk75 your fix did the trick! I will roll back my change that limits the numer of recycled stacks as it made the performance tests fail. Let's see if after that change things will be still green.

Yes, things are much better.
The memory mappings now barely go above a few hundred, as the OS is able to merge the mapped areas more efficiently. Even with guard_pages=on, they are in the hundreds now (an order of magnitude less than before).
That seems very significant, so keep an eye out for any macroscopic effects it may have.
The only memory "concern" is the slightly higher memory usage when using direct execution (because of the immediate thread spawining), but it's not that significant. So the thread stack allocation / recycling change is not as crucial.

@Pansysk75 I think this is finally good to be merged. What do you think?

@hkaiser There is a single timed-out test on daint (I had a look yesterday but didn't get anywhere), but other than that, nothing further to add.

I believe this is unrelated. Could be another case of the synchronization object going out of scope too early.

bors merge


Strange letter "U" in ZIP filename

OpenJDK8U-jdk_x64_windows_hotspot_8u181b13
No idea what the "U" after "OpenJDK8" should mean.
And after it is extracted the folder is now named jdk8u181-b13, but should be jdk-8u181+b13 I guess or at least jdk-8u181-b13. This every release name changes really suxxx.

The openjdk repository we seed our source code from is called jdk8u (See http://hg.openjdk.java.net/jdk8u for the original source we pull from) therefore the U is correct.
Why do you want an extra - after jdk?
Ref "This every release name changes really suxxx." what are you seeing as inconsistent? Oracle put the build identifier (e.g. 192) into their directories in the tarball too. The + character isn't good to use on Windows which is why we replace it with a -.

Why do you want an extra - after jdk?
This is how oracle names it.

I'm also not the fan of "+" in file names.
My point main point is about consistency and readability and not change the name in every minor release. This is what happened in last ~3 minor releases. Every time I need to change scripts to build the MSI setup. This waste a lot of time for nothing.


Routing question: placeholders vs slash

Expected Behavior

Request to /api/ would go to / downstream
Request to /api/test would go to /test downstream

Actual Behavior / Motivation for New Feature

Reqeust to /api/ is not resolved (see error below)
Request to /api/test goes to downstream `/test

Steps to Reproduce the Problem

Have something listening on localhost:8000
Configure ocelot to listen on localhost:5000
Use config below

Config:
{
    "ReRoutes": [
        {
            "DownstreamPathTemplate": "/{everything}",
            "DownstreamScheme": "http",
            "DownstreamHostAndPorts": [
                {
                    "Host": "localhost",
                    "Port": 8000
                }
            ],
            "UpstreamPathTemplate": "/api/{everything}",
            "UpstreamHttpMethod": [
                "GET",
                "POST"
            ]
        }
    ],
    "GlobalConfiguration": {
        "BaseUrl": "http://localhost:5000"
    }
}

Specifications

Version: 12.0.1
Platform: mac
Subsystem: ?

Comments
It is interesting to note, that if I configure ReRoute as /{everything} -> /{everything}, then it works, so it seems to me that {everything} wildcard match is not consistent in theese two cases.

@skyflyer
Request to /api/ would go to / downstream
This doesn't work because /{everything} expects something after the slash, you need a reroute that is just /
Request to /api/test goes to downstream `/test
Not sure if this is a typo? I assume it's working?

So here is what is puzzling me (it is unexpected).
Scenario 1

Config 1
{
    "ReRoutes": [
        {
            "DownstreamPathTemplate": "/{everything}",
            "DownstreamScheme": "http",
            "DownstreamHostAndPorts": [
                {
                    "Host": "localhost",
                    "Port": 8000
                }
            ],
            "UpstreamPathTemplate": "/{everything}",
            "UpstreamHttpMethod": [
                "GET",
                "POST"
            ],
            "RateLimitOptions": {
                "EnableRateLimiting": true,
                "ClientWhiteList": [],
                "Period": "1s",
                "Limit": 1,
                "PeriodTimespan": 5
            }
        }
    ],
    "GlobalConfiguration": {
        "BaseUrl": "http://localhost:5000",
        "RateLimitOptions": {
            "DisableRateLimitHeaders": false,
            "QuotaExceededMessage": "Over limit",
            "HttpStatusCode": 429
          }
    }
}

Config1, where I configure that everything coming to ocelot, goes to localhost:8000 works. So here, the pattern is /{everything} and it matches even / and also /ocelot.json and all works as one would expect.

request to http://localhost:5000/ returns content from http://localhost:8000/
request to http://localhost:5000/ocelot.json returns content from http://localhost:8000/ocelot.json

Scenario 2

Config2
{
    "ReRoutes": [
        {
            "DownstreamPathTemplate": "/{everything}",
            "DownstreamScheme": "http",
            "DownstreamHostAndPorts": [
                {
                    "Host": "localhost",
                    "Port": 8000
                }
            ],
            "UpstreamPathTemplate": "/api/{everything}",
            "UpstreamHttpMethod": [
                "GET",
                "POST"
            ],
            "RateLimitOptions": {
                "EnableRateLimiting": true,
                "ClientWhiteList": [],
                "Period": "1s",
                "Limit": 1,
                "PeriodTimespan": 5
            }
        }
    ],
    "GlobalConfiguration": {
        "BaseUrl": "http://localhost:5000",
        "RateLimitOptions": {
            "DisableRateLimitHeaders": false,
            "QuotaExceededMessage": "Over limit",
            "HttpStatusCode": 429
          }
    }
}

Based on the Config1, I would expect similar behaviour, only it is not, and I believe it should be (at least based on my experience with Apache and Nginx proxy setttings.

request to http://localhost:5000/api return 404 (?)
request to http://localhost:5000/api/ returns 404 (?)
request to http://localhost:5000/api/ocelot.json returns content from http://localhost:8000/ocelot.json (expected)

Are you saying that if I want to achieve that, I would need to configure two ReRoutes? One for /api/ and one for /api/{everything}?

@skyflyer yeh i think I might be wrong. This probably should work the way you expect but I don't know why it doesnt :/ I will mark this as a bug and see if we can get a fix!

The issue has been accepted due to open PR #1333 by @AndyConlisk :

#1333

Duplicate of #748

Fixed by #1911


pub shouldn't throw strings

As of r21498, thrown strings no longer have stack traces attached to them in async code. Pub throws some strings, which should be migrated to some non-primitive object.

This issue has been moved to dart-lang/pub#511.


Add / delete nodes

The following operations should be supported for dynamic scenarios:

[x] make_tree(weight): creates a new node with weight.
[ ] delete_tree(node_idx): deletes the subtree rooted at node node_idx.

delete_tree(node_idx) is unnecessary as it is trivial to replace a new node with the deleted one.


Link to Node.js Developer Center is broken

404: https://docs.microsoft.com/en-us/develop/nodejs/

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 51fa6592-d9d4-37e7-1d7b-90e0d39716ef
Version Independent ID: 681707f2-0fa0-4d7a-e754-04261aad4309
Content: Build and deploy a Node.js Express app to Azure Cloud Services
Content Source: articles/cloud-services/cloud-services-nodejs-develop-deploy-express-app.md
Service: cloud-services
GitHub Login: @Thraka
Microsoft Alias: adegeo

Thanks for the feedback! We are currently investigating and will update you shortly.


Add DSW template links for all cheat sheets

add DWS link to all cheat sheets
https://elixir-no.ds-wizard.org/projects/create/from-template?selected=
https://elixir-no.ds-wizard.org/projects?sort=updatedAt,desc&isTemplate=true

[ ] biobanks.md
[ ] biodiversity.md
[ ] crystallography.md
[ ] high-throughput_screening.md
[ ] light_microscopy.md
[ ] marine_metagenomics.md
[ ] nmr.md
[ ] preclinical_imaging.md
[ ] proteomics.md
[ ] sequencing.md - see PR

@korbinib The DSW link is on the page already (under RDM services > Data Stewardship Wizard).
Is this ok, or would you like me to make any changes?

We discussed this will go in section/topic boxes on Cheat Sheet main page, but also mentioned under 'More information' for each topic/field page.


[FEAT]: "Import" button

Is your feature request related to a problem? Please describe.
The user can import any image of her/his choice and work on that. There are cases where user needs to complete an assignment of artwork on pre-existing template. Thus, allowing an "import" function would be a scalable solution.
Describe the solution you'd like
An "import" button , similar to "export" to pick an image (any (standards) png, jpg) from the system or drive.
Describe alternatives you've considered
A side panel near canvas to shift between "upload image" and canvas (drawing board)
Additional context
I want to take this up

I want to take up this issue.

@StephenStolk You are already assigned #70
Kindly resolve that first.

It's completed. Pr is raised

@singodiyashubham87
I have made the changes in PR #70 . Please look into it.
If it's alright then please assign me this issue.

@singodiyashubham87
I want to take this up.

@StephenStolk Assigned!
Best of Luck! :)

@StephenStolk Any update?

Working on it. I faced some issues. Trying to solve it.

Unassigning due to inactivity.


share screen for specific window or application

This is a feature I've been trying to find for some time.  and it may just not be possible with the way Webex sets up the share screen dialog.  is it possible to share a specific application/window/file/etc with a single keystroke?  I'd love to be able to make one button on my deck that starts sharing and chooses the correct source, instead of just bringing the screen sharing dialog.

This issue seems to be related to Webex App, not the hardware devices, so it may not fit in this category, as the module is only connecting to the hardware devices with xAPI, effectively running RoomOS.
I will agree the naming has been a bit confusing, being "Webex Devices", so Cisco has now renamed them to "Cisco Devices", as they do support multiple meeting platforms.


No publisher to /dual_arm/panda_1/franka_gripper/joint_states using franka_combined_control.launch

Hello, I am trying to config double franka panda arm in ROS using franka_combined_control.launch
I bringup the franka panda robots usingroslaunch franka_control franka_combined_control.launch robot_ips:="{panda_1/robot_ip: <IP_ADDRESS>, panda_2/robot_ip: <IP_ADDRESS>}". After bringup, I can get the topic using rostopic list and can also echo the topic using rostopic echo /dual_arm/joint_states.
However, the joint position information about gripper in the topic  /dual_arm/joint_states is always 0. See as below.

Also, i found there is no publisher to /dual_arm/panda_1/franka_gripper/joint_states:

My franka_combined_control.launch file is as follows:

In addition, when i use roslaunch franka_control franka_control.launch robot_ip:=<IP_ADDRESS> to bringup single arm, all the things work well.
How can i solve this problem.
Any suggestion would mean a lot!

I think the problem is that you did not set arm_id in the gripper_node. Compare to the teleop_gripper.launch.
You can also check the teleop_joint_pd_examle_controller.launch. Maybe this example already is what you are trying to achieve. And even if not it should help you to find the problem in your launch file. Keep in mind that this launch file is using the franka_combined_control.launch, so you need to revert the changes that you made there to run the example.

@aodongdong hi, i wanna start with the dual arm on the simulation and real panda. Did you try it on the gazebo? I'm looking for your sharing. Thanks a lot!

Same as @mitsui29, I want to create simulation on gazebo for two panda robots and the dual impedance cartesian controller. I'm facing lots of issues though... Have you tried?


Consume ImGui with FetchContent

Dear ImGui source code is currently in sdk/external/imgui. It should have its own repo and pulled in with FetchContent. It would be best to fork the repo (still need docking branch?) if possible. This could also be a good time to update to latest.

Fork created, and a top level CMakeLists.txt was added. This needs to be updated to trim down some install files and perhaps some other cleanup.
If we switch from Win32 to GLFW before this gets done, CMake will also need to be updated to build with the correct backend.

Closing - no need to maintain a separate repo for this


Add UI test and error message for Vec<T> where T hasn't been declared within the bridge module.

Right now you get a useless error message when you have a Vec<T> where the T hasn't been declared within the bridge module.
An example of triggering this issue (note that we didn't declare type UndefinedType):
#[swift_bridge::bridge]
mod ffi {
    extern "Rust" {
        fn some_function() -> Vec<UndefinedType>;
    }
}

Here's a explanation of how to implement a compile time error https://chinedufn.github.io/swift-bridge/contributing/adding-compile-time-errors/index.html


[Feature] JSON Schema for Config file

Description

The config should have a JSON Schema to have autocompletion and validation inside the config.
See: https://json-schema.org/

Fixed by https://github.com/theoludwig/html-w3c-validator/commit/8934ac1b7ace68cda3522ea7dba1814285b94550.


Port The Strategy to Huff

Common @FrankieIsLost, we all know the closed source one uses huff, let's add a huff strategy here 🤠

👀

@FrankieIsLost
re huff-rust bindings: it depends. huff does include syntax for generating a json abi compatible with solc. however, it is common for huff contracts to include non-standard abi encoding schemes. bc of this, devs usually roll their own encoding.
re porting the sudo x opensea strat to huff : implementing it in accordance with the solc abi spec means we could just pass the deployed address into the cli with no compatibility issues
the questions/issues around this are:

adding this to the repo either requires we hard code the huffc output or implicitly add huffc as a dependency to the arb contract directory. is there a preference between the two? note that the latter also requires ffi to be enabled for testing to pass.
huff opens up a notable attack surface that solc abstracts away. currently the contract has a single test but migrating to huff demands a lot more contract tests given the risk.

if this is something that seems fit to add to the repo, i'd be happy to make a pr with the huffc contract.

re huff-rust bindings: it depends. huff does include syntax for generating a json abi compatible with solc. however, it is common for huff contracts to include non-standard abi encoding schemes. bc of this, devs usually roll their own encoding.

ah makes sense!

adding this to the repo either requires we hard code the huffc output or implicitly add huffc as a dependency to the arb contract directory. is there a preference between the two? note that the latter also requires ffi to be enabled for testing to pass.

Adding huffc as a dependency to the arb repo isn't a problem. What do you mean by hard code the huffc output? Taking the huffc output using something like forge etch to set it to a specific address? Seems a bit clunky but would prefer it to enabling FFI in the repo. Maybe there's a middle ground where we can run a setup script in CI to deploy the bytecode before running the tests instead of the broad FFI perms.

huff opens up a notable attack surface that solc abstracts away. currently the contract has a single test but migrating to huff demands a lot more contract tests given the risk.

Agree, and I'd be happy to help write some more tests here if helpful.
Overall, would love to see a huff implementation, and happy to support wherever helpful to see it happen :)


feat: add keepMissing option

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Reliving message window shows "Next" button to update instead of "Update"

Open any memory and click on relive memory.
Relive memory is shown in the chat.
But it shows Next button in relive memory instead of Update.

@Vudum Can you confirm something for me? The functionality here should work as follows:
By default upon initial display, button should read NEXT
If typing occurs in the chat input area (maybe 2+chars?) the button text should change to UPDATE
So let me know your thoughts - I definitely think I should add a placeholder text that says something like:
Type here to add or update details to this memory

Yes, this now works exactly as you said, Update appears if I type >2 characters otherwise Next is shown to the member.


HIVE-28340: Test concurrent JDBC connections with Kerberized cluster, impersonation, and HTTP transport

What changes were proposed in this pull request?

New test case simulating JDBC clients concurrently accessing a Kerberized cluster, with impersonation and HTTP transport.
Set transport mode based on configuration when creating MiniHS2 from MiniHiveKdc#getMiniHS2WithKerbWithRemoteHMSWithKerb.

Why are the changes needed?
Increase test coverage and guard against regressions. More info under HIVE-28340.
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
mvn test -Dtest=TestJdbcWithMiniKdcDoAsHttp -pl itests/hive-minikdc -Pitests

Tests are green can you have another look @dengzhhu653 ? Thanks!


Error Response

await HttpService.post('/signin', data);
how to  catch error response data?
I have tried error.response but the result is undefined

hey @itgelo,
did you try:
try {
  await HttpService.post('/signin', data);
} catch (e) {
  console.log(e);
}

?

I have tried.
try {   await HttpService.post('/signin', data); } catch (e) {   console.log(e.response); // response is undefined }
what I need, how to get an error response from API?

@itgelo it depends a little bit on your API, for this reason, I would log out the error object and see how it is structured. instead of console.log(e.response); you do console.log(e); and then see where you can get the necessary information.
I am not 100% sure if this is a vuesion or an axios issue. But please try this approach first before I start spending time on troubleshooting.

hi @devCrossNet, thanks for the response.
ok i will investigate this further.


GraphiQL question/feature request: show graphql endpoint being queried

My team is currently using GraphQL Playground that's shipped with Apollo Server, but due to the fact that Playground is no longer maintained and GraphiQL is now preferred, we are looking to switch. I'm currently running GraphiQL locally as outlined here.
One thing I appreciated about the GraphQL Playground is the ability to see which GraphQL endpoint was being hit/queried as seen in the screenshot below. Is this possible in GraphiQL or GraphiQL v2 that is being worked on?

If this wasn't the appropriate place to ask let me know and I can direct my question appropriately. Thank you!

This might be good to consider as a 3.0.0 feature. The current API doesn't allow users to specify a UI directly, instead the fetcher takes this in as an internal detail, however the idea of making (multiple) URI endpoints a configuration feature in 3.0.0 is something that could make sense!
This would work if, for example a simple uri prop or a graphql-config like config object could conditionally be provided instead of the required fetcher.  This would require props overloads but it would enable us to have per-endpoint headers, fetcher configuration, etc manageable in the UI

Hey @joshft91 👋 just wanna ask a clarifying question: Is your feature request just about showing the one URL that's used to send queries to? Or is it about adding support for querying multiple endpoints in a single instance of GraphiQL?

Hey @acao and @thomasheyenbrock 👋  - thanks for the responses!
Good clarifying question - I was in the middle of a response to do just that. While I like the idea of querying multiple endpoints, my request/question was simpler (famous last words): display/show (read only) - the URL that's configured in the fetcher essentially. It seems that this could be useful to me as a UI user of GraphiQL to know where my queries are being sent.
I believe this could even tie in with #2485 which seems like it's basically asking for a refresh button to trigger the introspection query. Something like what GraphQL Playground does now, just without the ability to specify a different endpoint.

Hope that makes sense!

Thanks for clarifying 🙌 We'll implement schema reloading with the new design that will ship with v2. The button for that will likely be placed in a menu or dialog. There will also be a keyboard shortcut for that (probably Cmd/Ctrl + R). I don't see an obvious spot where we could show the endpoint in the new design, but this should be solvable.
@acao Sounds like we won't need a new major for that, so labeling this just as "enhancement".

@thomasheyenbrock another pattern we can borrow from GraphQLPlayground is multiple service-layer components, which it seems you're already moving to to some degree.
GraphiQL could remain the component you use when you want to provide fetcher directly, and then GraphiQLEditor or some such could be more heavy-weight and act as an abstraction around GraphiQL and createFetcher() and eventually createRouter() (simple query params parser, maybe more some day?) and other details i imagined might be useful at this level.
For later major versions, 4 or 5 even at this point, it could eventually be something like this, like playground but with plugins
const token = import.meta.env.TOKEN

const projects = [
{
  name: "local",  schema: "localhost:3000/graphql"
},
{
  name: "stage",
  schema: "https://myschema.com/graphql",
  headers: { Authorization: `bearer ${token}` }
  }
]
<GraphiQLEditor
   projects={projects}
   settings={/* JSON string like playground or perhaps object */}
   plugins={/*array of components and/or modules definitions or objects*/}
/>

which opens us to other playground-esque service layers for server middlewares and beyond

playground has so many great service layer design patterns that I want to clone for the more modern era haha! but one at a time, one at a time

@acao great ideas! But should we keep this issue scoped for now on showing the endpoint somewhere in the design and open up another one that focusses on multi-project support? (Maybe there already is one?)

Is your feature request just about showing the one URL that's used to send queries to? Or is it about adding support for querying multiple endpoints in a single instance of GraphiQL?

Actually if I may I'd like to put in a vote for supporting querying multiple endpoints in a single GraphiQL instance. That would be super useful!

That is part of this feature request!
Lets track it here, since it documents the architectural changes needed to achieve this


Adds analytics notice and settings component

Ticket: https://emurgo.atlassian.net/browse/YOMO-657
Figma: https://www.figma.com/file/KeBVo6rWNYFLXwTphz9lHi/Mobile-App---iOS?type=design&node-id=5913-137622&mode=design&t=TvpltnNuHm1qUfF6-0

Settings
Notice

relates to #2568 - for settings

@stackchain Do we add at least the English translation manually into the locales json, or leave it for the translation tool?
The manage-translations script creates a lot of changes not related to these new lines.

@stackchain Do we add at least the English translation manually into the locales json, or leave it for the translation tool?
The manage-translations script creates a lot of changes not related to these new lines.

We add for the base en-US.json and CrowdIn ping the translators and open the PRs automatically, so yes, we add for en-US, make sure to don't update any other language cuz this will unsynch crowdin.