Refactor adding symbols to be more clear and simplify

Minor refactor of runtime optimizer internals. This encapsulates some code that's repeated a few times into a single add_symbol() call. Also, that call makes sure to temporarily mark a newly added symbol as used potentially at any time so any choices based on lifetime analysis will be extra conservative until the next time that lifetimes for all symbols are re-analyzed (which happens with each optimization pass over the code).

LGTM


Prepare Galactic EOL

https://docs.ros.org/en/galactic/Releases.html

https://github.com/Tiryoh/ros2_setup_scripts_ubuntu/pull/39 merged


chore(disk-filter): add logger for debugging disk claim process

What this PR does / why we need it:
add more logger for disk claim process
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report

Merging #1162 (e723bb6) into main (0f00a8c) will increase coverage by 0.15%.
Report is 2 commits behind head on main.
The diff coverage is 72.72%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main    #1162      +/-   ##
==========================================
+ Coverage   38.83%   38.98%   +0.15%
==========================================
  Files          25       25
  Lines        1970     1980      +10
==========================================
+ Hits          765      772       +7
- Misses       1103     1106       +3
  Partials      102      102

Files
Coverage Δ

...k-manager/handler/localdiskclaim/localdiskclaim.go
69.23% <100.00%> (ø)

pkg/local-disk-manager/filter/filter_disk.go
51.66% <70.00%> (+1.66%)
:arrow_up:

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


fix(builder): typo in dev.progressBar options

PR Details
Description

Fix typo in dev.progressBar options, quite should be quiet
Fix incorrect target label when inspect configs.
Move the getBrowserslistWithDefault method to builder-shared.
Remove the getDataUrlLimit method because it is useless yet.

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

是谁没有装 Code Spell Checker ？

是谁没有装 Code Spell Checker ？

quiet 也是合法单词。。


chore: improve readme and docs

Oversee, I will, please follow: https://github.com/elixir-tesla/tesla/issues/729


VWidgetGuard behavior in flutter web

Does VWidgetGaurd work in flutter web? Clicking android back button (or) browser back button seems to pop without calling the VWidgetGaurd's beforeLeave.
What I want to achieve is when on base route (1st route) and user clicks android back, show a dialog to close the app instead of directly poping the web page on browser.
How can this be achieved?
Thanks.

I don't understand, are you developping for web or mobile? There is no "android back button" apart from within android apps. Am I missing something ?

I meant the browser back button when using flutter web in mobile browser.
The android system back button can be used to go to previous route in android when using browser.

@satvikreddy Is this related to your problem?
https://vrouter.dev/guide/Advanced/Navigation Control/Web Caveat

When a user tries to access an external url by clicking on a button where you use context.vRouter.toExternal, everything works as expected.
When a user tries to access an external url either by typing it, or using the forward/backward button to navigate to an external url, you can’t prevent the user from navigating. This means that trying to use vRedirector.stopRedirection, vRedirector.to, ... in beforeLeave will be ignored.
Reloading the page cannot be stopped as well.
Everything else should work as expected.

Yes, this is. Thanks.


[WIP] Use encrypted database for application password

Description:
Use encrypted database for application password.
To lock:

user supplies password
generate random cypher key
encrypt database with cypher key
encrypt cypher key with supplied password
store the resulting encrypted cypher key in secure storage (keychain etc)
store a hash of the user password in the database (encrypted)

To unlock:

user supplies password
fetch encrypted cypher key from the database
decrypt with the user supplied password
decrypt the database using the resulting encryption key
compare hash of user supplied password with (now decrypted) password hash retrieved from the database

Notes

If you delete the encrypted cypher key from secure storage you will not be able to access the app. Technically, you could hack the codebase to bypass the check for this, but encrypted data will not be decrypted and the application would be unusable as a result.

TODO

[x] basic implementation
[ ] migration path for 0.6 users with password enabled
[ ] extend to encrypt additional data (currently only encrypts database password hash)

Motivation and Context:

Cross platform support for password feature (workaround useless windows credentials vault)
Ability to encrypt selected database entries
Do not store hashed user passwords unencrypted
Re-encrypt encrypted database entries after changing password

How Has This Been Tested?
Manually
Types of changes:
Enhancement
Checklist:

[ ] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[ ] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.1%) to 22.58% when pulling 4fbe8a161867ab37c0f6963f273890cafd0145f5 on mrfelton:feat/app-password into e543d1f4ce6531c12ed21d3e3d84fc01e5eb0578 on LN-Zap:next.


[CO] Change of ROOT_DIR

Hello Pierre,
what do you think about a change of the "root_dir" of pyleecan to ..\XYZ\pyleecan instead of ..\XYZ ?
Therefore all imports have to be corrected, but on the otherhand its enable the user to rename the pyleecan folder without breaking the program.
Best regards, Sebastian

Hello Sebastian,
Indeed that would be handy to be be able to rename the main pyleecan folder (on our side its already creating some confusion!). Maybe we can extend this thought about how pyleecan can be imported in another software. For instance, how should we organized the import if one day we go to pip ?
Best regards,
Pierre

Hello Sebastian, hello Pierre,
First of all, it could be great that users can install Pyleecan with pip. To do so, I think that we would need to reorganize the repository by moving the code into a pyleecan folder and to let general file such that README, LICENSE, and requirements at the root. We would also need to write some setup files as explained in this tutorial. To be able to run the GUI, we would need to add a __main__.py file to parse a command :
python -m pyleecan run_GUI

What do you thing about it ?
To be able to rename pyleecan folder, I think that we could try to switch from absolute to relative imports, I can try to do it soon.
Best regards,
Cédric


Convert empty strings to nil

Hello,
Can we add a property to the parser that converts empty strings to nil? Currently if I want to set a value as nil instead of "" I have to do:
(row["Key"] as String!).isEmpty ? nil : row["Key"]

which is fine for a few values, but it gets a little clunky if you have more than a few.

@dbettermann Thank you for the proposal. An application, not the parser, should be responsible for the convert. The parser always returns all values in a CSV file as String type.

That makes sense. In this case it would be nice if the Dictionary subscript returned Value instead of Value?.


[DatePicker] Issue with selecting dates below 3 years ago

Problem description
Can't select dates below 3 years ago using DatePicker
Steps to reproduce

Open http://www.material-ui.com/#/components/date-picker
Try to select date 4 years ago or earlier using year control
Can't select any year below 2013

Versions

Material-UI: 0.15.0
React: ^15.0.0 (as used in docs site)
Browser: Chrome 50.0.2661.102 (64-bit), Mac OS

Dupe of #4317


Set tsconfigRootDir: __dirname to prevent errors

tsconfigRootDir: __dirname will prevent eslint errors in VisualStudio code when you are in a subfolder and not the root of the app.

I think I didn't have this issue. Anyway I found your solution in the typescript repo: https://github.com/typescript-eslint/typescript-eslint/issues/251#issuecomment-463943250
So, go head!


brand: presentation theme: speaker info not centered over horizontal lines

I'm trying to use the Go presentation theme in a new presentation.
In the first slide (https://golang.org/s/presentation-theme#slide=id.g33148270ac_0_143), there is a text box for presenter information that overlays two horizontal lines.
That text box is not centered over the lines, which looks especially awkward if the text lines are close to the length of the horizontal lines:

CC @cassandraoid @spf13

I know it's not ideal - we can't do much to it right now, I tend to change
the size of the text to help with alignment.
On Wed, Aug 8, 2018 at 1:17 PM Bryan C. Mills<EMAIL_ADDRESS>wrote:

I'm trying to use the Go presentation theme in a new presentation.
In the first slide (
https://golang.org/s/presentation-theme#slide=id.g33148270ac_0_143),
there is a text box for presenter information that overlays two horizontal
lines.
That text box is not centered over the lines, which looks especially
awkward if the text lines are close to the length of the horizontal lines:
[image: screenshot 2018-08-08 at 16 13 22]
https://user-images.githubusercontent.com/5200974/43861858-18ba33c6-9b26-11e8-9172-c3596ebbbf17.png
CC @cassandraoid https://github.com/cassandraoid @spf13
https://github.com/spf13
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/26879, or mute the thread
https://github.com/notifications/unsubscribe-auth/APNWccYLcKjy5UvsHYIKM7O0uzPntX6Vks5uO0dLgaJpZM4V0lzD
.


Set interval for pushing a job flush

Some (old/crappy) mining clients will simply ignore new work notifications from the server unless it signals to flush old jobs. This is an annoyance for merge mined coins, where you probably don't want to flush for some (lower value) Aux chains.
A potential optimization would be to have a configurable time period where if stratum hasn't pushed a  job that flushes to the client in that time it'll proceed to push one.
This has the advantages of not spamming out flushing pushes, but updating a fair bit of stale Aux jobs.
The main disadvantage would be a increase in main chain stales. To mitigate that we could keep the (old but valid) job around and still credit the stale submissions...But then people would need to make sure and configure to send stales...Messy, and not even possible on some miners.
It'd need to be tested/balanced to make sure the increased stales didn't outweigh the increased profits from Aux work...
Overall, quite a bit of work for a slim gain, so its definitely not a priority - just figured I'd put it up for thoughts/feedback. It could be a more valuable feature if merge mined coins continue to grow in popularity

Even cleverer would be to detect if they're still submitting the last flush vs the last push, and then occasionally send a flush for only those clients. Best of both worlds, but honestly our push timing logic is crazy confusing right now as is, so reasoning about this improvement will get tricky fast.

Cool idea. Might actually be worthwhile to make a utility/test for the flushing logic

Yeah, tests in general are a big thing that is needed... Certainly would be a good place to start since I know there's a related bug right now.


chore: add warning when downloading a sBOM

Signed-off-by: hectorj2f<EMAIL_ADDRESS>
Summary

This PR adds a warning to users when downloading sBOMs.In order to ensure tamper-proof sBOMs and validate its authenticity, sigstore recommends to download the attestations that include the sBOMs or validate their signatures if signed.
Related to this RFC #https://github.com/sigstore/cosign/issues/1742
Ticket Link

Fixes
Release Note

Codecov Report

Merging #1763 (38ef2b6) into main (70a3d8c) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1763      +/-   ##
==========================================
- Coverage   30.59%   30.55%   -0.04%
==========================================
  Files         143      143
  Lines        8658     8659       +1
==========================================
- Hits         2649     2646       -3
- Misses       5710     5713       +3
- Partials      299      300       +1

Impacted Files
Coverage Δ

cmd/cosign/cli/download.go
0.00% <0.00%> (ø)

pkg/cosign/tuf/client.go
62.69% <0.00%> (-0.95%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70a3d8c...38ef2b6. Read the comment docs.


docs(textfield,textarea): migrating docs to storybook

Description
Migrating docs for Textfield and Textarea.

Textarea Storybook coverage has been added
Helptext component is now a part of the Textfield Template

Validation steps
Textarea/Textfield docs:

[x] Textarea docs and test are added in textfield stories folder
[x] Disabled, Side Label, Character Count, Help Text, Validation and Error stories are available
[x] Help text text control is available / inValid state example is included
[x] Textarea testing preview mode is available

Regression testing
Validate:

The documentation pages for at least two other components are still loading, including:

[ ] The pages render correctly, are accessible, and are responsive.

If components have been modified, VRTs have been run on this branch:

[ ] VRTs have been run and looked at.
[ ] Any VRT changes have been accepted (by reviewer and/or PR author), or there are no changes.

Screenshots

To-do list

[ ] I have read the contribution guidelines.
[ ] I have updated relevant storybook stories and templates.
[ ] I have tested these changes in Windows High Contrast mode.
[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[ ] ✨ This pull request is ready to merge. ✨

@aramos-adobe Can you rebase your branch and take a look at the VRT changes to see that these are the expected updates: https://www.chromatic.com/build?appId=64762974a45b8bc5ca1705a2&number=3505

@aramos-adobe Can you rebase your branch and take a look at the VRT changes to see that these are the expected updates: https://www.chromatic.com/build?appId=64762974a45b8bc5ca1705a2&number=3505

Done ✅


Allow filtering AND/OR between the three conn-types

Raised by Viv

Issue implemented in the dashboard.


Rename /vocab to /apidoc

As advised by @lanthaler on the Hydra mailing list.
Also fix a typo.

:+1:


Remove old and redundant type package

I think this should fix https://github.com/elifesciences/enhanced-preprints-server/security/dependabot/50


[ESP32C3] cannot finish commissioning

Problem

expected behavior

actual behavior
I set up and follow sequence about all-clusters-app
Run chip-tool but chip-tool was stopped by timeout.
How do I complete commissioning?
If I need to modify menuconfig, please let me know setting on menuconfig.

steps to reproduce

system configuration

example : all-clusters-app.
ESP32 : ESP32-C3 (ESP32-C3-DevkitM-1)
I did not set RPC console.
connectedhomeip : master

$ git log -1
commit 776c06d5bbda9ea59f8eb28a8d328251fe619d61 (HEAD -> master, origin/master, origin/HEAD)
Author: Shubham Patil<EMAIL_ADDRESS>Date:   Sat Jul 9 18:23:18 2022 +0530
[ESP32] Support flash encryption and nvs encryption (#20414)

- Added an option to encrypt the factory partition.
- Securely initialize the NVS partition if NVS encryption is enabled
- Added user guide for flash encryption in lighting-app/esp32

ESP-IDF : v4.4.1

$ git log -1
commit 1329b19fe494500aeb79d19b27cfd99b40c37aec (HEAD, tag: v4.4.1)
Author: Michael (XIAO Xufeng<EMAIL_ADDRESS>Date:   Sat Apr 16 09:43:14 2022 +0800
versions: Update version to 4.4.1

screenshots, images, logs, etc.

chip-tool log
I set $SSID and $PASSWORD are WiFi AP at my home.

$ ./out/debug/chip-tool pairing ble-wifi 12344321 $SSID $PASSWORD 20202021 3840
[1657520561.895036][21740:21740] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1657520561.895478][21740:21740] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1657520561.895627][21740:21740] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1657520561.895737][21740:21740] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1657520561.896225][21740:21740] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-se6Q34)
[1657520561.896933][21740:21740] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1657520561.897038][21740:21740] CHIP:DL: NVS set: chip-counters/reboot-count = 7 (0x7)
[1657520561.897595][21740:21740] CHIP:DL: Failed to get Ethernet interface
[1657520561.897961][21740:21740] CHIP:DL: Failed to reset Ethernet statistic counts
[1657520561.898143][21740:21740] CHIP:DL: Got WiFi interface: wlp1s0
[1657520561.899441][21740:21740] CHIP:DL: Found the primary WiFi interface:wlp1s0
[1657520561.899574][21740:21740] CHIP:IN: UDP::Init bind&listen port=0
[1657520561.899693][21740:21740] CHIP:IN: UDP::Init bound to port=52158
[1657520561.899739][21740:21740] CHIP:IN: UDP::Init bind&listen port=0
[1657520561.899823][21740:21740] CHIP:IN: UDP::Init bound to port=56227
[1657520561.899868][21740:21740] CHIP:IN: BLEBase::Init - setting/overriding transport
[1657520561.899909][21740:21740] CHIP:IN: TransportMgr initialized
[1657520561.899966][21740:21740] CHIP:FP: Initializing FabricTable from persistent storage
[1657520561.900239][21740:21740] CHIP:TS: Last Known Good Time: 2022-07-11T15:15:36
[1657520561.901082][21740:21740] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xC514CBA34B4E423E, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1657520561.901678][21740:21740] CHIP:FP: Fabric index 0x2 was retrieved from storage. Compressed FabricId 0xE9F8A4A0812BB2F3, FabricId 0x0000000000000002, NodeId 0x000000000001B669, VendorId 0xFFF1
[1657520561.902353][21740:21740] CHIP:FP: Fabric index 0x3 was retrieved from storage. Compressed FabricId 0x8EB7D3E2000C9D1D, FabricId 0x0000000000000003, NodeId 0x000000000001B669, VendorId 0xFFF1
[1657520561.905426][21740:21740] CHIP:ZCL: Using ZAP configuration...
[1657520561.906207][21740:21740] CHIP:CTL: System State Initialized...
[1657520561.906304][21740:21740] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1657520561.906352][21740:21740] CHIP:CTL: Setting attestation nonce to random value
[1657520561.906410][21740:21740] CHIP:CTL: Setting CSR nonce to random value
[1657520561.906487][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.906556][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.906597][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.906658][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.906695][21740:21740] CHIP:IN: TransportMgr initialized
[1657520561.906787][21740:21740] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1657520561.906830][21740:21740] CHIP:CTL: Setting attestation nonce to random value
[1657520561.906877][21740:21740] CHIP:CTL: Setting CSR nonce to random value
[1657520561.910132][21740:21740] CHIP:CTL: Generating NOC
[1657520561.911567][21740:21740] CHIP:FP: Validating NOC chain
[1657520561.913924][21740:21740] CHIP:FP: NOC chain validation successful
[1657520561.914161][21740:21740] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1657520561.914211][21740:21740] CHIP:TS: Last Known Good Time: 2022-07-11T15:15:36
[1657520561.914249][21740:21740] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1657520561.914282][21740:21740] CHIP:TS: Retaining current Last Known Good Time
[1657520561.917263][21740:21740] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1657520561.920055][21740:21740] CHIP:TS: Committing Last Known Good Time to storage: 2022-07-11T15:15:36
[1657520561.922726][21740:21740] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1657520561.922806][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.922899][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.922940][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.923005][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.923044][21740:21740] CHIP:IN: TransportMgr initialized
[1657520561.923169][21740:21740] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1657520561.923219][21740:21740] CHIP:CTL: Setting attestation nonce to random value
[1657520561.923281][21740:21740] CHIP:CTL: Setting CSR nonce to random value
[1657520561.924325][21740:21740] CHIP:CTL: Generating NOC
[1657520561.925615][21740:21740] CHIP:FP: Validating NOC chain
[1657520561.927975][21740:21740] CHIP:FP: NOC chain validation successful
[1657520561.928221][21740:21740] CHIP:FP: Updated fabric at index: 0x2, Node ID: 0x000000000001B669
[1657520561.928270][21740:21740] CHIP:TS: Last Known Good Time: 2022-07-11T15:15:36
[1657520561.928308][21740:21740] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1657520561.928340][21740:21740] CHIP:TS: Retaining current Last Known Good Time
[1657520561.931214][21740:21740] CHIP:FP: Metadata for Fabric 0x2 persisted to storage.
[1657520561.933879][21740:21740] CHIP:TS: Committing Last Known Good Time to storage: 2022-07-11T15:15:36
[1657520561.936400][21740:21740] CHIP:CTL: Joined the fabric at index 2. Compressed fabric ID is: 0x0000000000000000
[1657520561.936477][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.936571][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.936614][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.936688][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.936707][21740:21740] CHIP:IN: TransportMgr initialized
[1657520561.936834][21740:21740] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1657520561.936888][21740:21740] CHIP:CTL: Setting attestation nonce to random value
[1657520561.936949][21740:21740] CHIP:CTL: Setting CSR nonce to random value
[1657520561.938088][21740:21740] CHIP:CTL: Generating NOC
[1657520561.939379][21740:21740] CHIP:FP: Validating NOC chain
[1657520561.941697][21740:21740] CHIP:FP: NOC chain validation successful
[1657520561.941966][21740:21740] CHIP:FP: Updated fabric at index: 0x3, Node ID: 0x000000000001B669
[1657520561.942018][21740:21740] CHIP:TS: Last Known Good Time: 2022-07-11T15:15:36
[1657520561.942056][21740:21740] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1657520561.942089][21740:21740] CHIP:TS: Retaining current Last Known Good Time
[1657520561.945048][21740:21740] CHIP:FP: Metadata for Fabric 0x3 persisted to storage.
[1657520561.947797][21740:21740] CHIP:TS: Committing Last Known Good Time to storage: 2022-07-11T15:15:36
[1657520561.950418][21740:21740] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0x0000000000000000
[1657520561.950500][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.950595][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.950636][21740:21740] CHIP:IN: UDP::Init bind&listen port=5550
[1657520561.950703][21740:21740] CHIP:IN: UDP::Init bound to port=5550
[1657520561.950746][21740:21740] CHIP:IN: TransportMgr initialized
[1657520561.988974][21740:21745] CHIP:DL: CHIP task running
[1657520561.989384][21740:21745] CHIP:IN: SecureSession[0x7f8844001a30]: Allocated Type:1 LSID:6378
[1657520561.989425][21740:21745] CHIP:SC: Assigned local session key ID 6378
[1657520561.989469][21740:21745] CHIP:SC: Including MRP parameters in PBKDF param request
[1657520561.989526][21740:21745] CHIP:IN: Prepared unauthenticated message 0x7f885a0b53f0 to 0x0000000000000000 (0)  of type 0x20 and protocolId (0, 0) on exchange 37515i with MessageCounter:204868355.
[1657520561.989567][21740:21745] CHIP:IN: Sending unauthenticated msg 0x7f885a0b53f0 with MessageCounter:204868355 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>7432E3 msec
[1657520561.989596][21740:21745] CHIP:IN: Message appended to BLE send queue
[1657520561.989613][21740:21745] CHIP:SC: Sent PBKDF param request
[1657520561.989632][21740:21745] CHIP:CTL: Setting wifi credentials from parameters
[1657520561.989647][21740:21745] CHIP:CTL: Setting attestation nonce to random value
[1657520561.989670][21740:21745] CHIP:CTL: Setting CSR nonce to random value
[1657520561.989698][21740:21745] CHIP:CTL: Commission called for node ID 0x0000000000BC5C01
[1657520561.989990][21740:21746] CHIP:DL: TRACE: Bluez mainloop starting Thread
[1657520561.990155][21740:21743] CHIP:DL: TRACE: Bus acquired for name C-54ec
[1657520562.000269][21740:21745] CHIP:DL: PlatformBlueZInit init success
[1657520562.029835][21740:21743] CHIP:BLE: BLE removing known devices.
[1657520562.038510][21740:21743] CHIP:BLE: BLE initiating scan.
[1657520562.910776][21740:21745] CHIP:DL: Long dispatch time: 921 ms, for event type 2
[1657520562.915973][21740:21743] CHIP:BLE: New device scanned: FC:A3:BB:37:11:FC
[1657520562.916253][21740:21743] CHIP:BLE: Device discriminator match. Attempting to connect.
[1657520562.926758][21740:21743] CHIP:BLE: Scan complete notification without an active scan.
[1657520563.055751][21740:21743] CHIP:DL: ConnectDevice complete
[1657520572.921398][21740:21745] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1657520572.921464][21740:21745] CHIP:IN: Clearing BLE pending packets.
[1657520572.921495][21740:21745] CHIP:IN: BleConnection Error: ../../third_party/connectedhomeip/src/platform/Linux/BLEManagerImpl.cpp:63: CHIP Error 0x00000032: Timeout
[1657520592.006425][21740:21745] CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33
[1657520592.006505][21740:21745] CHIP:IN: SecureSession[0x7f8844001a30]: Released - Type:1 LSID:6378
[1657520592.006536][21740:21745] CHIP:TOO: Secure Pairing Failed
[1657520592.006614][21740:21745] CHIP:DIS: Closing all BLE connections
[1657520592.006659][21740:21745] CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:244: CHIP Error 0x00000032: Timeout
[1657520592.006975][21740:21740] CHIP:CTL: Shutting down the commissioner
[1657520592.007074][21740:21740] CHIP:CTL: Shutting down the controller
[1657520592.007102][21740:21740] CHIP:CTL: Shutting down the commissioner
[1657520592.007156][21740:21740] CHIP:CTL: Shutting down the controller
[1657520592.007175][21740:21740] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1657520592.007189][21740:21740] CHIP:FP: Forgetting fabric 0x1
[1657520592.007215][21740:21740] CHIP:TS: Pending Last Known Good Time: 2022-07-11T15:15:36
[1657520592.007451][21740:21740] CHIP:TS: Previous Last Known Good Time: 2022-07-11T15:15:36
[1657520592.007470][21740:21740] CHIP:TS: Reverted Last Known Good Time to previous value
[1657520592.007507][21740:21740] CHIP:CTL: Shutting down the commissioner
[1657520592.007560][21740:21740] CHIP:CTL: Shutting down the controller
[1657520592.007577][21740:21740] CHIP:IN: Expiring all sessions for fabric 0x2!!
[1657520592.007589][21740:21740] CHIP:FP: Forgetting fabric 0x2
[1657520592.007605][21740:21740] CHIP:TS: Pending Last Known Good Time: 2022-07-11T15:15:36
[1657520592.007774][21740:21740] CHIP:TS: Previous Last Known Good Time: 2022-07-11T15:15:36
[1657520592.007791][21740:21740] CHIP:TS: Reverted Last Known Good Time to previous value
[1657520592.007820][21740:21740] CHIP:CTL: Shutting down the commissioner
[1657520592.007871][21740:21740] CHIP:CTL: Shutting down the controller
[1657520592.007888][21740:21740] CHIP:IN: Expiring all sessions for fabric 0x3!!
[1657520592.007899][21740:21740] CHIP:FP: Forgetting fabric 0x3
[1657520592.007916][21740:21740] CHIP:TS: Pending Last Known Good Time: 2022-07-11T15:15:36
[1657520592.008080][21740:21740] CHIP:TS: Previous Last Known Good Time: 2022-07-11T15:15:36
[1657520592.008097][21740:21740] CHIP:TS: Reverted Last Known Good Time to previous value
[1657520592.008121][21740:21740] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1657520592.008232][21740:21740] CHIP:DMG: IM WH moving to [Uninitialized]
[1657520592.008251][21740:21740] CHIP:DMG: IM WH moving to [Uninitialized]
[1657520592.008261][21740:21740] CHIP:DMG: IM WH moving to [Uninitialized]
[1657520592.008271][21740:21740] CHIP:DMG: IM WH moving to [Uninitialized]
[1657520592.008283][21740:21740] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1657520592.008337][21740:21740] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1657520592.008824][21740:21740] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-wZDd72)
[1657520592.009861][21740:21740] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1657520592.009995][21740:21740] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1657520592.010051][21740:21740] CHIP:DL: Inet Layer shutdown
[1657520592.010106][21740:21740] CHIP:DL: BLE shutdown
[1657520592.011127][21740:21740] CHIP:DL: System Layer shutdown
[1657520592.011321][21740:21740] CHIP:TOO: Run command failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:244: CHIP Error 0x00000032: Timeout

ESP32-C3 log

ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x16b4
load:0x403ce000,len:0x930
load:0x403d0000,len:0x2d28
entry 0x403ce000
I (30) boot: ESP-IDF v4.4.1 2nd stage bootloader
I (30) boot: compile time 14:24:09
I (30) boot: chip revision: 3
I (32) boot.esp32c3: SPI Speed      : 80MHz
I (37) boot.esp32c3: SPI Mode       : DIO
I (41) boot.esp32c3: SPI Flash Size : 4MB
I (46) boot: Enabling RNG early entropy source...
I (52) boot: Partition Table:
I (55) boot: ## Label            Usage          Type ST Offset   Length
I (62) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (70) boot:  1 otadata          OTA data         01 00 0000f000 00002000
I (77) boot:  2 phy_init         RF data          01 01 00011000 00001000
I (85) boot:  3 ota_0            OTA app          00 10 00020000 00177000
I (92) boot:  4 ota_1            OTA app          00 11 001a0000 00177000
I (100) boot:  5 ot_storage       Unknown data     01 3a 00317000 00002000
I (107) boot: End of partition table
I (112) esp_image: segment 0: paddr=00020020 vaddr=3c100020 size=355c8h (218568) map
I (154) esp_image: segment 1: paddr=000555f0 vaddr=3fc8f600 size=03908h ( 14600) load
I (157) esp_image: segment 2: paddr=00058f00 vaddr=40380000 size=07118h ( 28952) load
I (165) esp_image: segment 3: paddr=00060020 vaddr=42000020 size=f9034h (1019956) map
I (328) esp_image: segment 4: paddr=0015905c vaddr=40387118 size=084a0h ( 33952) load
I (334) esp_image: segment 5: paddr=00161504 vaddr=50000010 size=00010h (    16) load
I (340) boot: Loaded app from partition at offset 0x20000
I (340) boot: Disabling RNG early entropy source...
I (357) cpu_start: Pro cpu up.
I (365) cpu_start: Pro cpu start user code
I (365) cpu_start: cpu freq: 160000000
I (365) cpu_start: Application information:
I (368) cpu_start: Project name:     chip-all-clusters-app
I (374) cpu_start: App version:      TE9-1110-g776c06d5b-dirty
I (381) cpu_start: Compile time:     Jul 11 2022 14:23:44
I (387) cpu_start: ELF file SHA256:<PHONE_NUMBER>284e5b...
I (393) cpu_start: ESP-IDF:          v4.4.1
I (398) heap_init: Initializing. RAM available for dynamic allocation:
I (405) heap_init: At 3FCA40D0 len 0001BF30 (111 KiB): DRAM
I (411) heap_init: At 3FCC0000 len 0001F060 (124 KiB): STACK/DRAM
I (418) heap_init: At 50000020 len 00001FE0 (7 KiB): RTCRAM
I (425) spi_flash: detected chip: generic
I (429) spi_flash: flash io: dio
I (434) sleep: Configure to isolate all GPIO pins in sleep state
I (440) sleep: Enable automatic switching of GPIO sleep configuration
I (447) coexist: coexist rom version 9387209
I (452) cpu_start: Starting scheduler.
I (462) all-clusters-app: ==================================================
I (462) all-clusters-app: chip-esp32-all-cluster-demo starting
I (472) all-clusters-app: ==================================================
I (482) pp: pp rom version: 9387209
I (482) net80211: net80211 rom version: 9387209
I (502) wifi:wifi driver task: 3fcad210, prio:23, stack:6656, core=0
I (502) system_api: Base MAC address is not set
I (502) system_api: read default base MAC address from EFUSE
I (512) wifi:wifi firmware version: 63017e0
I (512) wifi:wifi certification version: v7.0
I (512) wifi:config NVS flash: enabled
I (522) wifi:config nano formating: disabled
I (522) wifi:Init data frame dynamic rx buffer num: 32
I (522) wifi:Init management frame dynamic rx buffer num: 32
I (532) wifi:Init management short buffer num: 32
I (532) wifi:Init dynamic tx buffer num: 32
I (542) wifi:Init static tx FG buffer num: 2
I (542) wifi:Init static rx buffer size: 1600
I (552) wifi:Init static rx buffer num: 10
I (552) wifi:Init dynamic rx buffer num: 32
I (552) wifi_init: rx ba win: 6
I (562) wifi_init: tcpip mbox: 32
I (562) wifi_init: udp mbox: 6
I (572) wifi_init: tcp mbox: 6
I (572) wifi_init: tcp tx win: 5744
I (572) wifi_init: tcp rx win: 5744
I (582) wifi_init: tcp mss: 1440
I (582) wifi_init: WiFi IRAM OP enabled
I (592) wifi_init: WiFi RX IRAM OP enabled
I (602) chip[DL]: NVS set: chip-counters/reboot-count = 7 (0x7)
I (602) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
I (612) all-clusters-app: ------------------------Starting App Task---------------------------
W (612) BTDM_INIT: esp_bt_controller_mem_release not implemented, return OK
I (622) BTDM_INIT: BT controller compile version [d913766]
I (632) phy_init: phy_version 909,156dee4,Apr  7 2022,20:27:09
I (622) app-task: This is ESP32 chip with 1 CPU cores, WiFi/BLE,
I (642) app-task: silicon revision 3,
I (662) app-task: 4MB external flash
I (662) chip[SVR]: SetupQRCode: [MT:Y.K9042C00KA0648G00]
I (662) chip[SVR]: Copy/paste the below URL in a browser to see the QR Code:
I (662) chip[SVR]: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K9042C00KA0648G00
I (682) chip[SVR]: Manual pairing code: [34970112332]
I (682) app-task: App Task started
I (772) BTDM_INIT: Bluetooth MAC: 84:f7:03:60:fb:e6
I (782) NimBLE: GAP procedure initiated: stop advertising.
I (782) CHIP[DL]: BLE host-controller synced
I (1282) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable, device name MATTER-3840)
I (1282) NimBLE: GAP procedure initiated: advertise;
I (1282) NimBLE: disc_mode=2
I (1282) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1292) NimBLE:
I (1302) chip[DL]: CHIPoBLE advertising started
E (1302) chip[DL]: Long dispatch time: 689 ms, for event type 2
I (1312) chip[DL]: Starting ESP WiFi layer
I (1322) wifi:mode : sta (84:f7:03:60:fb:e4)
I (1322) wifi:enable tsf
W (1322) wifi:Haven't to connect to a suitable AP now!
I (1332) chip[DL]: Done driving station state, nothing else to do...
I (1332) phy: chan:1,max_power:80
I (1342) phy: chan:2,max_power:80
I (1342) phy: chan:3,max_power:80
I (1342) phy: chan:4,max_power:80
I (1352) phy: chan:5,max_power:80
I (1352) phy: chan:6,max_power:80
I (1362) phy: chan:7,max_power:80
I (1362) phy: chan:8,max_power:80
I (1362) phy: chan:9,max_power:80
I (1372) phy: chan:10,max_power:80
I (1372) phy: chan:11,max_power:80
I (1382) phy: chan:12,max_power:80
I (1382) phy: chan:13,max_power:80
I (1382) phy: chan:14,max_power:80
W (1392) wifi:Haven't to connect to a suitable AP now!
I (1392) chip[DL]: Done driving station state, nothing else to do...
I (1402) phy: chan:1,max_power:80
I (1402) phy: chan:2,max_power:80
I (1412) phy: chan:3,max_power:80
I (1412) phy: chan:4,max_power:80
I (1422) phy: chan:5,max_power:80
I (1422) phy: chan:6,max_power:80
I (1422) phy: chan:7,max_power:80
I (1432) phy: chan:8,max_power:80
I (1432) phy: chan:9,max_power:80
I (1442) phy: chan:10,max_power:80
I (1442) phy: chan:11,max_power:80
I (1442) phy: chan:12,max_power:80
I (1452) phy: chan:13,max_power:80
I (1452) phy: chan:14,max_power:80
I (1462) chip[SVR]: Server initializing...
I (1462) chip[TS]: Last Known Good Time: 2022-07-11T14:45:24
I (1472) chip[DMG]: AccessControl: initializing
I (1472) chip[DMG]: Examples::AccessControlDelegate::Init
I (1482) chip[DMG]: AccessControl: setting
I (1482) chip[DMG]: DefaultAclStorage: initializing
I (1492) chip[DMG]: DefaultAclStorage: 0 entries loaded
I (1512) chip[ZCL]: Using ZAP configuration...
I (1522) chip[DMG]: AccessControlCluster: initializing
I (1522) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0030', EndPoint ID: '0x00', Attribute ID: '0x0000'
I (1532) app-devicecallbacks: Unhandled cluster ID: 48
I (1542) app-devicecallbacks: Current free heap: 125136
I (1542) chip[ZCL]: Initiating Admin Commissioning cluster.
I (1552) chip[ZCL]: Door Lock server initialized
I (1552) chip[ZCL]: Initialize PCC Plugin Server Cluster.
I (1562) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0003', EndPoint ID: '0x00', Attribute ID: '0x0001'
I (1572) app-devicecallbacks: Current free heap: 125100
I (1582) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x00', Attribute ID: '0x0000'
I (1592) app-devicecallbacks: Unhandled cluster ID: 4
I (1592) app-devicecallbacks: Current free heap: 125100
I (1602) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x00', Attribute ID: '0xfffc'
I (1612) app-devicecallbacks: Unhandled cluster ID: 4
I (1622) app-devicecallbacks: Current free heap: 125100
I (1632) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x002b', EndPoint ID: '0x00', Attribute ID: '0x0000'
I (1642) app-devicecallbacks: Unhandled cluster ID: 43
I (1642) app-devicecallbacks: Current free heap: 125100
I (1652) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0003', EndPoint ID: '0x01', Attribute ID: '0x0001'
I (1662) app-devicecallbacks: Current free heap: 125100
I (1672) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x01', Attribute ID: '0x0000'
I (1682) app-devicecallbacks: Unhandled cluster ID: 4
I (1682) app-devicecallbacks: Current free heap: 125100
I (1692) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x01', Attribute ID: '0xfffc'
I (1702) app-devicecallbacks: Unhandled cluster ID: 4
I (1712) app-devicecallbacks: Current free heap: 125100
I (1712) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0005', EndPoint ID: '0x01', Attribute ID: '0x0000'
I (1732) app-devicecallbacks: Unhandled cluster ID: 5
I (1732) app-devicecallbacks: Current free heap: 125100
I (1742) chip[ZCL]: On/Off set value: 1 0
I (1742) chip[ZCL]: On/off already set to new value
I (1752) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0008', EndPoint ID: '0x01', Attribute ID: '0x0000'
I (1762) app-devicecallbacks: Current free heap: 125100
I (1772) chip[ZCL]: Window Covering Cluster init
I (1772) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0102', EndPoint ID: '0x01', Attribute ID: '0x0007'
I (1782) app-devicecallbacks: Unhandled cluster ID: 258
I (1792) app-devicecallbacks: Current free heap: 125100
I (1802) chip[ZCL]: WC POST ATTRIBUTE=7
I (1802) chip[ZCL]: ConfigStatus 0x1B Operational=1 OnlineReserved=1
I (1812) chip[ZCL]: Lift(PA=1 Encoder=0 Reversed=0) Tilt(PA=1 Encoder=0)
I (1812) chip[ZCL]: Initialize PCC Server Cluster [EP:1]
I (1822) chip[ZCL]: Constant Pressure Supported
I (1832) chip[ZCL]: PCC Server: Constant Proportional Pressure Supported
I (1832) chip[ZCL]: PCC Server: Constant Flow Supported
I (1842) chip[ZCL]: PCC Server: Constant Temperature Supported
I (1852) chip[ZCL]: PCC Server: Constant Speed Supported
I (1852) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0300', EndPoint ID: '0x01', Attribute ID: '0x0007'
I (1862) app-devicecallbacks: Unhandled AttributeId ID: '0x0007
I (1872) app-devicecallbacks: Current free heap: 125100
I (1882) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0300', EndPoint ID: '0x01', Attribute ID: '0x0008'
I (1892) app-devicecallbacks: Unhandled AttributeId ID: '0x0008
I (1892) app-devicecallbacks: Current free heap: 125100
I (1902) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0300', EndPoint ID: '0x01', Attribute ID: '0x4001'
I (1912) app-devicecallbacks: Unhandled AttributeId ID: '0x4001
I (1922) app-devicecallbacks: Current free heap: 125100
I (1932) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0406', EndPoint ID: '0x01', Attribute ID: '0x0001'
I (1942) app-devicecallbacks: Unhandled cluster ID: 1030
I (1942) app-devicecallbacks: Current free heap: 125100
I (1952) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0406', EndPoint ID: '0x01', Attribute ID: '0x0002'
I (1962) app-devicecallbacks: Unhandled cluster ID: 1030
I (1972) app-devicecallbacks: Current free heap: 125100
I (1972) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x02', Attribute ID: '0x0000'
I (1992) app-devicecallbacks: Unhandled cluster ID: 4
I (1992) app-devicecallbacks: Current free heap: 125100
I (2002) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0004', EndPoint ID: '0x02', Attribute ID: '0xfffc'
I (2012) app-devicecallbacks: Unhandled cluster ID: 4
I (2012) app-devicecallbacks: Current free heap: 125100
I (2022) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0406', EndPoint ID: '0x02', Attribute ID: '0x0001'
I (2032) app-devicecallbacks: Unhandled cluster ID: 1030
I (2042) app-devicecallbacks: Current free heap: 125100
I (2042) app-devicecallbacks: PostAttributeChangeCallback - Cluster ID: '0x0406', EndPoint ID: '0x02', Attribute ID: '0x0002'
I (2062) app-devicecallbacks: Unhandled cluster ID: 1030
I (2062) app-devicecallbacks: Current free heap: 125100
I (2072) chip[DIS]: Updating services using commissioning mode 1
I (2082) chip[DIS]: CHIP minimal mDNS started advertising.
I (2082) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15
I (2092) chip[DIS]: CHIP minimal mDNS configured as 'Commissionable node device'.
I (2102) chip[DIS]: mDNS service published: _matterc._udp
I (2112) chip[IN]: CASE Server enabling CASE session setups
I (2112) chip[SVR]: Joining Multicast groups
I (2122) chip[SVR]: Server Listening...
E (2122) chip[DL]: Long dispatch time: 665 ms, for event type 2
I (2132) app-devicecallbacks: Current free heap: 124376
I (2132) chip[DL]: WIFI_EVENT_STA_START
I (2142) phy: chan:1,max_power:80
I (2142) phy: chan:2,max_power:80
I (2152) phy: chan:3,max_power:80
I (2152) phy: chan:4,max_power:80
I (2152) phy: chan:5,max_power:80
I (2162) phy: chan:6,max_power:80
I (2162) phy: chan:7,max_power:80
I (2172) phy: chan:8,max_power:80
I (2172) phy: chan:9,max_power:80
I (2172) phy: chan:10,max_power:80
I (2182) phy: chan:11,max_power:80
I (2182) phy: chan:12,max_power:80
I (2192) phy: chan:13,max_power:80
I (2192) phy: chan:14,max_power:80
W (2202) wifi:Haven't to connect to a suitable AP now!
I (2202) chip[DL]: Done driving station state, nothing else to do...
I (2212) app-devicecallbacks: Current free heap: 124376
I (2212) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable, device name MATTER-3840)
I (2222) chip[DL]: Device already advertising, stop active advertisement and restart
I (2232) NimBLE: GAP procedure initiated: stop advertising.
I (2242) NimBLE: GAP procedure initiated: advertise;
I (2242) NimBLE: disc_mode=2
I (2252) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (2262) NimBLE:
I (2262) chip[SVR]: Cannot load binding table: a0
I (8232) chip[DL]: BLE GAP connection established (con 1)
I (8232) chip[DL]: CHIPoBLE advertising stopped
I (8232) app-devicecallbacks: Current free heap: 124384
I (40442) chip[DL]: BLE GAP connection terminated (con 1 reason 0x213)
I (40452) app-devicecallbacks: CHIPoBLE disconnected
I (40452) app-devicecallbacks: Current free heap: 124384
I (40452) chip[DL]: Configuring CHIPoBLE advertising (interval 500 ms, connectable, device name MATTER-3840)
I (40462) NimBLE: GAP procedure initiated: advertise;
I (40472) NimBLE: disc_mode=2
I (40472) NimBLE:  adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=800 adv_itvl_max=800
I (40482) NimBLE:
I (40492) chip[DL]: CHIPoBLE advertising started
I (40492) app-devicecallbacks: Current free heap: 124376

I'm also facing the same problem....

I solved this issue.
https://github.com/project-chip/connectedhomeip/issues/20470#issuecomment-1181443365
https://github.com/project-chip/connectedhomeip/issues/20470#issuecomment-1181443365


Fixed #29550 -- Made it easier to override pickle.dumps usages protocol.

https://code.djangoproject.com/ticket/29550

Thanks for the merge @timgraham!


[docs] Module mode vs. script mode

Gleaning the docs, it looks like TSC parses files in either Module Mode or Script Mode. From the docs and from playing around with TS-

If a file has at least one import, export, or export =, TSC typechecks the file in Module Mode
Otherwise, TSC typechecks the file in Script Mode

The differences seem to be that in Script Mode:

You can directly consume globals exported by UMD modules (export namespace as)
You can declare globals, that are then available in other files in the project without an explicit import. There seem to be a few ways to do that:

let a = 1, let a: 1, or declare let a: 1 in a .ts file
declare let a: 1 in a .d.ts file

In Module Mode:

You can't use globals exported from UMD modules, and instead have to explicitly import the UMD module's exports
You can declare globals, that are then available in the current file only (not in other files):

let a = 1, let a: 1, or declare let a: 1 in a .ts file
declare let a: 1 in a .d.ts file

Are there any other differences, and are there any TSC flags that affect this behavior? I can't find anything else covering this in the spec or the docs.

Also, why is Script mode vs. Module mode based on a heuristic, instead of an explicit tsconfig flag?

https://www.typescriptlang.org/docs/handbook/2/modules.html


Can't drag again after dropping a box over a different sized box

Reproduction of the bug is possible using the ltGridOnly demo in lg mode.
http://clippings.github.io/layout-grid/demos/only.html
If I drag the #2 box over the #1 box, I can't do any other drag operations afterwards.
It seems that when dropping a bigger box on a smaller one, it creates empty regions and then can't respond anymore.
If I drag box over one of the same size, then I can drag again.
Is this normal? I have to refresh the page to correct the issue.
Thanks

Hi, @soulfire03! Which browser are you using? I can't seem to reproduce.

Hi hkdobrev, I'm using Chrome 70.0.3538.77

Humm... the issue seems related to my VM on RDP.
I tried running with same version of chrome on my physical desktop and it's working fine. But when I try through remote desktop, then it's not working anymore.

@soulfire03 Try it out without any extensions, incognito etc. Check for any issues in the console, as well.

Same thing on incognito without extensions.
But since this only happen through RDP, this is less of an issue for me. Would be great to fix, but not urgent.
Thanks


[Enhancement] Add ICEBERG.ComplexMetricsConfig in query profile for Iceberg tables

Why I'm doing:
To optimize the MetricsModes of the Iceberg tables, it's necessary to display the columns of the FULL or TRUNCATE type MetricsMode in the ICEBERG query profile.
What I'm doing:
e.g.
     - DeployDataSize: 3615
    ICEBERG:
      ComplexMetricsConfig:
        hive_prod:
          testdb:
            census:
               - size: 3
               - columns: {census_year=truncate(16), year=truncate(16), name=truncate(16)}
      ScanMetrics:
        hive_prod:

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

could you add some test to cover this?

could you add some test to cover this?

done

Fix conflicts caused by pull rebase.

@stephen-shelby PTAL.
Fix conflicts by pull rebase.


Improve config for custom networks and add SEI Network

Add to config

Available wallets
Network params

Name
Icon

Popular pairs, popular base and quote tokens and default token pair (for the trade and simulate pages)
Add gasToken and tokenListOverride
Add tokenList parser and define SEI parser

Reference native and gas tokens instead of ETH in the app
Replace chainId in wallet config, check if network doesn't exist in wallet and if not, pass network object
Use network and gas token names throughout the app
Tenderly chain defaults to Ethereum
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE is the token address used for SEI (gas token)
Added SEI Trading View symbols to mapping
Define available wallets in config
Improve readme to specify what each parameters in the config does
App can run without API live
My strategies page checks if user has no strategies in case there is no activity information (API failing, API fetched but no activity, or tenderly fork)
Multicall address wasn't being passed to Carbon SDK initialization

Config structure in: https://github.com/bancorprotocol/carbon-app/blob/improve-config/src/config/types.ts

[ ] text change in notifications "Etherscan" -> "Seitrace"
[ ] Settings Menu -> Currency Selection -> change "ETH" to "SEI"

[ ] better handle cases where there is no token price
flow 1:
create strategy -> input sell/buy price ->
current: there is a calculation with warning indicating ">99.99% above market"

updated: apply the same message as we show on the trade page.

flow 2:
trade -> orderbook -> mid market price
current:

updated: if there is no USD price to use for calculation, omit this usd value

flow 3:
trade -> trade route popup
current: we show value of tokens and average price with usd value to it

updated: if there is no USD price to use for calculation, omit this usd value

[ ] notifications: replace "etherscan" with "seitrace"

[ ] display currency selection: replace ETH with SEI

allow users to select SEI as a display currency

update the price calculation to use SEI

[ ] optional: activity notifications - on click close the notification menu
flow:

click the bell icon
pick an activity notification
click the "view activity"
current: the menu stays open
update: close the menu following the click which will result in a user viewing the relevant activity page
optional because i am not sure if this is a regression from current behavior

[ ] optional: deposit into existing recurring strategy
current: we show a warning indication next to the incorrect input field
flow:

deposit into existing recurring strategy
indicate deposit amount into the "sell high" field
actual: a warning shows up below the "buy low" input field with a warning "Notice: you offer to buy DSWAP above current market price"
expected: there is no market price. therefore, we cannot trigger any real warning.

[ ] optional: withdraw funds from existing recurring strategy
expected: not to show any warning on load. not to show any warning if there is no market price available to use for calculations

Moved one of the flagged issues (activity notifications close on click) to a new issues as it is live in the main app right now:
https://github.com/bancorprotocol/carbon-app/issues/1206


Parse_wikidump: programmatic access

Refactored parse_wikidump to allow programmatic access to its functionality, e.g., initialize db, and initiate downloads via code.

I see how this is a useful feature, but I think it should be implemented differently, viz. by moving functionality from __main__.py (which is mean to be only a script entry point) to the module. E.g., move the functionality you might want to import from your code to parse_wikidump/__init__.py and then import it in __main__.py.

Good points. Let me work on it a bit more and will hear from me soon.

But apart from the sadness, i'm all for this change (i did something similar in my joblib branch.)


Read Cnab Files

The same way that has a layout to convert JSON into CNAB files, we can do backwards.
So using a CNAB file and generate a json with the data, based on the retorno files, for example:

https://github.com/andersondanilo/cnab_yaml/tree/master/cnab400/237/retorno

feito!


PolicyException for a pod with multiple violations

Kyverno Version
1.12
Kubernetes Version
1.28
Kubernetes Platform
Bare metal
Description
Hello everyone!
I am running Kyverno v1.12.1, and trying to create PolicyException object for a given deployment by following PolicyExceptions documentation page.
I am using Kyverno policy to apply Pod Security Standard profile. I am attempting to create a PolicyException for a deployment that has many (five) violations, but I am not getting far. After creating the PolicyException object, the PolicyReport continues to show failures for Pod.
Details in the reproduce section.
Steps to reproduce
Here are the object I've created:

ClusterPolicy for PSS
---
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: pod-security-standards
spec:
  background: true
  validationFailureAction: Audit
  rules:
  - name: restricted
    match:
      any:
      - resources:
          kinds:
          - Pod
    validate:
      podSecurity:
        level: restricted
        version: latest

This is straight out of the documentation, with the only change being validationFailureAction: Audit.
Here is a an example of a Pod that has policy violations:

Pod
---
apiVersion: v1
kind: Pod
metadata:
  name: promtail-djwbc
  namespace: promtail
spec:
  containers:
  - args:
    - -config.file=/etc/promtail/promtail.yaml
    - -config.expand-env=true
    env:
    - name: HOSTNAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: spec.nodeName
    - name: LOKI_GATEWAY_USERNAME
      valueFrom:
        secretKeyRef:
          key: gateway_user
          name: loki-gateway-auth
    - name: LOKI_GATEWAY_PASSWORD
      valueFrom:
        secretKeyRef:
          key: gateway_password
          name: loki-gateway-auth
    image: grafana/promtail:2.9.3
    imagePullPolicy: IfNotPresent
    name: promtail
    ports:
    - containerPort: 3101
      name: http-metrics
      protocol: TCP
    readinessProbe:
      failureThreshold: 5
      httpGet:
        path: /ready
        port: http-metrics
        scheme: HTTP
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources:
      limits:
        cpu: 250m
        memory: 450Mi
      requests:
        cpu: 100m
        memory: 250Mi
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      readOnlyRootFilesystem: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/promtail
      name: config
    - mountPath: /run/promtail
      name: run
    - mountPath: /var/lib/docker/containers
      name: containers
      readOnly: true
    - mountPath: /var/log/pods
      name: pods
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-2v4bw
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext:
    runAsGroup: 0
    runAsUser: 0
    seccompProfile:
      type: RuntimeDefault
  serviceAccount: promtail
  serviceAccountName: promtail
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
    operator: Exists
  - effect: NoSchedule
    key: node-role.kubernetes.io/control-plane
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/disk-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/memory-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/pid-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/unschedulable
    operator: Exists
  volumes:
  - name: config
    secret:
      defaultMode: 420
      secretName: promtail
  - hostPath:
      path: /run/promtail
      type: ""
    name: run
  - hostPath:
      path: /var/lib/docker/containers
      type: ""
    name: containers
  - hostPath:
      path: /var/log/pods
      type: ""
    name: pods
  - name: kube-api-access-2v4bw
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace

This pod violates about five policies. Here is a playground link. I realized that Playground is running Kyverno 1.11, and I was unable to test out the PolicyException object due to older version of API spec.
I created the following PolicyExceptions object for the violations:

Policy Exception
---
apiVersion: kyverno.io/v2
kind: PolicyException
metadata:
  name: promtail-exceptions
  namespace: kyverno
spec:
  exceptions:
  - policyName: pod-security-standards
    ruleNames:
    - restricted
  match:
    any:
    - resources:
        namespaces:
        - promtail
  podSecurity:
  - controlName: "Volume Types"
    restrictedField: spec.volumes[*]
    values:
      - "spec.volumes[*].hostPath"
  - controlName: "HostPath Volumes"
    restrictedField: spec.volumes[*].hostPath
    values:
      - "/run/promtail"
      - "/var/log/pods"
      - "/var/lib/docker/containers"
  - controlName: "Running as Non-root"
    restrictedField: spec.securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root"
    restrictedField: spec.containers[*].securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root user"
    restrictedField: spec.securityContext.runAsUser
    values:
      - "0"

Even after creating the PolicyException object, the next time the Pod is restarted, it is reporting violations:

Policy Exception
apiVersion: wgpolicyk8s.io/v1alpha2
kind: PolicyReport
metadata:
  name: 58a7af12-5ad9-4e72-ba26-6065b3f82503
  namespace: promtail
results:
- message: 'Validation rule ''restricted'' failed. It violates PodSecurity "restricted:latest":
    (Forbidden reason: runAsUser=0, field error list: [spec.securityContext.runAsUser
    is forbidden, forbidden values found: 0])(Forbidden reason: hostPath volumes,
    field error list: [spec.volumes[1].hostPath is forbidden, forbidden values found:
    /run/promtail, spec.volumes[2].hostPath is forbidden, forbidden values found:
    /var/lib/docker/containers, spec.volumes[3].hostPath is forbidden, forbidden values
    found: /var/log/pods])(Forbidden reason: restricted volume types, field error
    list: [spec.volumes[1].hostPath: Forbidden, spec.volumes[2].hostPath: Forbidden,
    spec.volumes[3].hostPath: Forbidden])'
  policy: pod-security-standards
  properties:
    controls: hostPathVolumes,restrictedVolumes,runAsNonRoot,runAsUser
    standard: restricted
    version: latest
  result: fail
  rule: restricted
  scored: true
  source: kyverno
  timestamp:
    nanos: 0
    seconds:<PHONE_NUMBER>
scope:
  apiVersion: v1
  kind: Pod
  name: promtail-djwbc
  namespace: promtail
summary:
  error: 0
  fail: 1
  pass: 0
  skip: 0
  warn: 0

Expected behavior
I expect that after creating the necessary PolicyExceptions, the PolicyReport would not show a failure.
Screenshots
No response
Kyverno logs
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

I've also attempted to use the following variations of the PolicyException objects:

Policy Exception variation 2
---
apiVersion: kyverno.io/v2
kind: PolicyException
metadata:
  name: promtail-exceptions
  namespace: kyverno
spec:
  exceptions:
  - policyName: pod-security-standards
    ruleNames:
    - restricted
  match:
    any:
    - resources:
        kinds:
        - Pod
        namespaces:
        - promtail
  podSecurity:
  - controlName: "Volume Types"
    restrictedField: spec.volumes[*]
    values:
      - "spec.volumes[*].hostPath"
  - controlName: "HostPath Volumes"
    restrictedField: spec.volumes[*].hostPath
    values:
      - "/run/promtail"
      - "/var/log/pods"
      - "/var/lib/docker/containers"
  - controlName: "Running as Non-root"
    restrictedField: spec.securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root"
    restrictedField: spec.containers[*].securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root user"
    restrictedField: spec.securityContext.runAsUser
    values:
      - "0"

Policy Exception variation 3
---
apiVersion: kyverno.io/v2
kind: PolicyException
metadata:
  name: promtail-exceptions
  namespace: promtail
spec:
  exceptions:
  - policyName: pod-security-standards
    ruleNames:
    - restricted
  match:
    any:
    - resources:
        kinds:
        - Pod
  podSecurity:
  - controlName: "Volume Types"
    restrictedField: spec.volumes[*]
    values:
      - "spec.volumes[*].hostPath"
  - controlName: "HostPath Volumes"
    restrictedField: spec.volumes[*].hostPath
    values:
      - "/run/promtail"
      - "/var/log/pods"
      - "/var/lib/docker/containers"
  - controlName: "Running as Non-root"
    restrictedField: spec.securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root"
    restrictedField: spec.containers[*].securityContext.runAsNonRoot
    values:
      - "true"
  - controlName: "Running as Non-root user"
    restrictedField: spec.securityContext.runAsUser
    values:
      - "0"

You only need to specify the control names:
  podSecurity:
  - controlName: "Volume Types"
  - controlName: "HostPath Volumes"
  - controlName: "Running as Non-root"
  - controlName: "Running as Non-root"
  - controlName: "Running as Non-root user"

Here is the Policy Report result of your Pod (I used the default Namespace) after creating the PolicyException:
apiVersion: wgpolicyk8s.io/v1alpha2
kind: PolicyReport
metadata:
  creationTimestamp: "2024-05-17T19:19:21Z"
  generation: 3
  labels:
    app.kubernetes.io/managed-by: kyverno
  name: 5a3afc40-f471-4bb2-b1b1-187ce31ce056
  namespace: default
  ownerReferences:
  - apiVersion: v1
    kind: Pod
    name: promtail-djwbc
    uid: 5a3afc40-f471-4bb2-b1b1-187ce31ce056
  resourceVersion: "921422"
  uid: 6b2c1d8a-233b-4933-945f-d0a255b85bdd
results:
- message: rule skipped due to policy exception kyverno/promtail-exceptions
  policy: pod-security-standards
  properties:
    exception: promtail-exceptions
  result: skip
  rule: restricted
  scored: true
  source: kyverno
  timestamp:
    nanos: 0
    seconds:<PHONE_NUMBER>
scope:
  apiVersion: v1
  kind: Pod
  name: promtail-djwbc
  namespace: default
  uid: 5a3afc40-f471-4bb2-b1b1-187ce31ce056
summary:
  error: 0
  fail: 0
  pass: 0
  skip: 1
  warn: 0

@chipzoller  - Thank you for your response. I guess I am a bit confused. When I was following the linkerd, the example encourages using more filtering (which i agree with). Here is the example for linkerd:
      validate:
        podSecurity:
          level: baseline
          version: latest
          exclude:
            - controlName: Capabilities
              images:
                - "*/istio/proxyv2*"
                - "*/linkerd/proxy-init*"
              restrictedField: spec.initContainers[*].securityContext.capabilities.add
              values:
                - NET_ADMIN
                - NET_RAW

I understand that rules does not require further filterin. But I am now curious as to.. why?

In the HostPath Volumes control in the baseline profile, there is no provision for specifying acceptable values (i.e., a "whitelist"). The control is absolute. Therefore, no amount of values you specify will be evaluated so you have to exclude the entire control. As for other controls, there's no sense in customizing those values because they're boolean.


refactor: remove cniTypesCurr.Result dependency in InterfaceInfo

Reason for Change:

removing cniTypesCurr.Result dependency in InterfaceInfo
adding scope link for swiftv2 gateway route
Issue Fixed:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

/azp run CNI Load Test

can we run cni load test pipeline as well for this PR ?

load tests passed https://msazure.visualstudio.com/One/_build/results?buildId=82852995&view=results


SAK-49223 Messages Breadcrumb innacurate

https://sakaiproject.atlassian.net/browse/SAK-49223

Nice, that breadcrumbs were super buggy. Do you think we should clean up related code in PrivateMessagesTool.java? Though if this gets merged back to < 23.x, it might be nice to have a separate commit for that.


Thread Performance Checker: Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class.

Full debug logs:
Thread Performance Checker: Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions
PID: 70339, TID: 4422014
Backtrace
=================================================================
3   AppNameHere                           0x0000000105bff3dc $s8NIOPosix13NIOThreadPoolC6_start16threadNamePrefixySS_tF + 1524
4   AppNameHere                           0x0000000105c0004c $s8NIOPosix13NIOThreadPoolC5startyyF + 60
5   AppNameHere                           0x00000001055a481c $s6SotoS30B0V18ThreadPoolProviderO6create8NIOPosix09NIOThreadD0CyF + 124
6   AppNameHere                           0x00000001055aab24 $s6SotoS30B0V26openFileForMultipartUpload8filename6logger2on18threadPoolProvider14uploadCallback7NIOCore15EventLoopFutureCyAC08CompletefG6OutputVGSS_7Logging6LoggerVAJ0qR0_pAC06ThreadlM0OAoJ13NIOFileHandleC_AJ0D6RegionV8NIOPosix011NonBlockingD2IOVtctF + 156
7   AppNameHere                           0x00000001055aa888 $s6SotoS30B0V15multipartUpload_8partSize8filename11abortOnFail6logger2on18threadPoolProvider8progress7NIOCore15EventLoopFutureCyAC017CompleteMultipartD6OutputVGAC06CreatevD7RequestV_SiSSSb7Logging6LoggerVAL0rS0_pSgAC06ThreadnO0OySdKctF + 1244
8   AppNameHere                           0x00000001050ffa5c $s9AppNameHere19AWSFileUploadWorkerC7execute4data10completionyAC7RequestV_ySSSg_AC8ResponseVSgtcSgtF + 4424
9   AppNameHere                           0x0000000104f64514 $s9AppNameHere16FileUploadWorkerC7execute4data10completionyAC7RequestC_ySSSg_AC8ResponseVSgtcSgtF05startcD0L_yyF + 536
10  AppNameHere                           0x0000000104f642a4 $s9AppNameHere16FileUploadWorkerC7execute4data10completionyAC7RequestC_ySSSg_AC8ResponseVSgtcSgtF + 984
11  AppNameHere                           0x0000000105218108 $s9AppNameHere13LFFileManagerC18uploadPendingFiles33_A43F4D69DB085DD12FA6694232CB9D21LLyyF6handleL_0E7RequestyAA16FileUploadWorkerC0Q0C_tF + 348
12  AppNameHere                           0x0000000105217f80 $s9AppNameHere13LFFileManagerC18uploadPendingFiles33_A43F4D69DB085DD12FA6694232CB9D21LLyyF + 344
13  AppNameHere                           0x0000000105219174 $s9AppNameHere13LFFileManagerC18uploadPendingFiles33_A43F4D69DB085DD12FA6694232CB9D21LLyyF6handleL_0E7RequestyAA16FileUploadWorkerC0Q0C_tFySSSg_AI8ResponseVSgtcfU_ + 4160
14  AppNameHere                           0x0000000104f65158 $s9AppNameHere16FileUploadWorkerC7execute4data10completionyAC7RequestC_ySSSg_AC8ResponseVSgtcSgtF05startcD0L_yyFyAI_AA07AWSFiledE0CAJVSgtcfU_yAI_AA08FSUploadE0CAJVSgtcfU_ + 1032
15  AppNameHere                           0x0000000104f504b8 $s9AppNameHere14FSUploadWorkerC7execute4data10completionyAC7RequestV_ySSSg_AC8ResponseVSgtcSgtFyAI_AA10RESTWorkerCAJVSgtcfU_ + 1268
16  AppNameHere                           0x000000010525a1c8 $s9AppNameHere10RESTWorkerC7execute4data10completionyAC7RequestV_ySSSg_AC8ResponseVSgtcSgtFy9Alamofire04DataH0Vy10Foundation0J0VAN7AFErrorOGcfU0_ + 3168
17  AppNameHere                           0x00000001063c6a2c $s9Alamofire11DataRequestC9_response33_39EEDF845955893097265C4B130CD574LL5queue0D10Serializer17completionHandlerACXDSo012OS_dispatch_I0C_xyAA0B8ResponseVy16SerializedObjectQzAA7AFErrorOGctAA0boJ8ProtocolRzlFyycfU_yyYbcfU1_yycfU_yyYbcfU_ + 124
18  AppNameHere                           0x00000001063045ac $sIegh_IeyBh_TR + 48
19  libdispatch.dylib                   0x0000000108aa0f14 _dispatch_call_block_and_release + 32
20  libdispatch.dylib                   0x0000000108aa2b4c _dispatch_client_callout + 20
21  libdispatch.dylib                   0x0000000108ab5dcc _dispatch_main_queue_drain + 1100
22  libdispatch.dylib                   0x0000000108ab5970 _dispatch_main_queue_callback_4CF + 44
23  CoreFoundation                      0x000000018a95d220 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
24  CoreFoundation                      0x000000018a91aaac __CFRunLoopRun + 1996
25  CoreFoundation                      0x000000018a919c2c CFRunLoopRunSpecific + 608
26  HIToolbox                           0x0000000194e72448 RunCurrentEventLoopInMode + 292
27  HIToolbox                           0x0000000194e72284 ReceiveNextEventCommon + 648
28  HIToolbox                           0x0000000194e71fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76
29  AppKit                              0x000000018e0f4f90 _DPSNextEvent + 660
30  AppKit                              0x000000018e8c8b94 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
31  AppKit                              0x000000018e0e843c -[NSApplication run] + 476
32  AppKit                              0x000000018e0bf708 NSApplicationMain + 880
33  AppNameHere                           0x000000010530eea8 $sSo21NSApplicationDelegateP6AppKitE4mainyyFZ + 40
34  AppNameHere                           0x000000010530ee70 $s9AppNameHere11AppDelegateC5$mainyyFZ + 44
35  AppNameHere                           0x000000010530f070 main + 28
36  dyld                                0x000000018a4c5058 start + 2224

I'm using S3 to upload multipart content and sometimes happens to receive those logs and progress/completion closures are not called, resulting that the file is stuck on "uploading" state.
Setup (please complete the following information):

OS: macOS Sonoma 14.0
Version of soto: 6.7
Authentication mechanism [hard-coded credentials, IAM Instance Profile on EC2, etc]

let cpf = CredentialProviderFactory.static(accessKeyId: adtConfiguration.pk,
                                           secretAccessKey: adtConfiguration.sk)
let awsClient = AWSClient(credentialProvider: cpf, httpClientProvider: .createNew)
let region = SotoS3.Region(awsRegionName: adtConfiguration.region)
var s3 = S3(client: awsClient, region: region, timeout: .minutes(2))
if adtConfiguration.useAccelerateEndpoint {
    s3 = s3.with(options: .s3UseTransferAcceleratedEndpoint)
}
self.s3 = s3
let request = S3.CreateMultipartUploadRequest(bucket: adtConfiguration.bucket,
                                              contentType: fileURL.mimeType,
                                              key: data.file.serverFileName(withUserUID: true))

s3.multipartUpload(request,
                   partSize: InformationKeeper.shared.otherFileChunkSize,
                   filename: fileURL.path) { progress in
    if self.isCancelled == false {
        handle(progress: progress)
    }
}
                   .whenComplete { (uploadResult) in
                       handle(uploadResult: uploadResult)
                   }

What QoS is calling code running at?

On the main...

Ok one possibility is a thread pool is being created every time you call that function and this is causing issues. Instead you could create a global NIOThreadPool and pass it to s3. multipartUpload as threadPoolProvider: .shared(myThreadPool).
Recently swift-nio supplied a singleton version of the NIOThreadPool. I can change the default to use this singleton instead of creating a new one every time the function is called

PR for using singleton instead #695

@adam-fowler  new version release ?

The PR needs approved first

@adam-fowler  can you solve today?

While waiting for a new release you should be able to use threadPoolProvider: .shared(NIOThreadPool.singleton) in your multipartUpload call to resolve your issue.

Hmm, I tried but is not solving the issue:
Thread Performance Checker: Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions
PID: 39945, TID: 5500604
Backtrace
=================================================================
3   AppNameHere                           0x0000000104d6f540 $s8NIOPosix13NIOThreadPoolC6_start16threadNamePrefixySS_tF + 1524
4   AppNameHere                           0x0000000104d6eed4 $s8NIOPosix13NIOThreadPoolC021_makePerpetualStartedC015numberOfThreads16threadNamePrefixACSi_SStFZ + 104
5   AppNameHere                           0x0000000104da30cc $s8NIOPosix23globalPosixBlockingPool33_54795181D6A4669A6950FD635B385752LLAA09NIOThreadE0CvpfiAEyXEfU_ + 132
6   AppNameHere                           0x0000000104da3038 $s8NIOPosix23globalPosixBlockingPool33_54795181D6A4669A6950FD635B385752LL_WZ + 12
7   libdispatch.dylib                   0x0000000107c02b4c _dispatch_client_callout + 20
8   libdispatch.dylib                   0x0000000107c04a64 _dispatch_once_callout + 160
9   AppNameHere                           0x0000000104da2e68 $s8NIOPosix23globalPosixBlockingPool33_54795181D6A4669A6950FD635B385752LLAA09NIOThreadE0Cvau + 80
10  AppNameHere                           0x0000000104da2dfc $s7NIOCore13NIOSingletonsO8NIOPosixE23posixBlockingThreadPoolAD09NIOThreadG0CvgZ + 16
11  AppNameHere                           0x0000000104da2ed0 $s8NIOPosix13NIOThreadPoolC9singletonACvgZ + 24
12  AppNameHere                           0x000000010426f354 $s9AppNameHere19AWSFileUploadWorkerC7execute4data10completionyAC7RequestV_ySSSg_AC8ResponseVSgtcSgtF + 4140
13  AppNameHere                           0x00000001040d678c $s9AppNameHere16FileUploadWorkerC7execute4data10completionyAC7RequestC_ySSSg_AC8ResponseVSgtcSgtF05startcD0L_yyF + 536
14  AppNameHere                           0x00000001040d651c $s9AppNameHere16FileUploadWorkerC7execute4data10completionyAC7RequestC_ySSSg_AC8ResponseVSgtcSgtF + 984
15  AppNameHere                           0x0000000104388a98 $s9AppNameHere13LFFileManagerC18uploadPendingFiles33_A43F4D69DB085DD12FA6694232CB9D21LLyyF6handleL_0E7RequestyAA16FileUploadWorkerC0Q0C_tF + 348
16  AppNameHere                           0x0000000104388910 $s9AppNameHere13LFFileManagerC18uploadPendingFiles33_A43F4D69DB085DD12FA6694232CB9D21LLyyF + 344
17  AppNameHere                           0x00000001043805f4 $s9AppNameHere13LFFileManagerC11uploadFiles4urlsySay10Foundation3URLVG_tF + 1152
18  AppNameHere                           0x0000000104312d00 $s9AppNameHere21FileManagerHeaderViewV4bodyQrvg7SwiftUI05TupleF0VyAE0F0PAEE7paddingyQrAE4EdgeO3SetV_12CoreGraphics7CGFloatVSgtFQOyAiEE5frame5width6height9alignmentQrAR_ArE9AlignmentVtFQOyAE6HStackVyAGyAE06ScrollF0VyAZyAGyAC09componentF033_FF7633ACFDEA3379B9E4F13A23535CF6LL4text10isSelected12onTapGestureQrAA10BaseStringO_SbyyctFQOy_Qo__AE7ForEachVySayAA6FolderVGSSA8_GtGGGSg_AE6SpacerVAGyAA11ImageButtonVSg_A23_A22_tGSgAiEEAstuVQrAR_ArXtFQOyA20__Qo_A22_A22_A26_AE6VStackVyAiEE12cornerRadius_11antialiasedQrAQ_SbtFQOyAZyAGyAiEE11buttonStyleyQrqd__AE20PrimitiveButtonStyleRd__lFQOyAE6ButtonVyAiEE10background_AVQrqd___AXtAeHRd__lFQOyAiEEAstuVQrAR_ArXtFQOyAiEE15foregroundColoryQrAE5ColorVSgFQOyAE5ImageV_Qo__Qo__A38_Qo_G_AE16PlainButtonStyleVQo__A48_tGG_Qo_GtGG_Qo__Qo__AiEEAJyQrAN_ARtFQOyAiEEAstuVQrAR_ArXtFQOyAZyAGyAiEEA31_yQrqd__AEA32_Rd__lFQOyA34_yA41_G_A47_Qo_Sg_AE19_ConditionalContentVyAE4TextVA63_GA20_AZyAGyAA15SearchTextFieldV_AiEE9fixedSizeQryFQOyAiEE9menuStyleyQrqd__AE9MenuStyleRd__lFQOyAE4MenuVyAiEEA29__A30_QrAQ_SbtFQOyAiEEA35__AVQrqd___AXtAeHRd__lFQOyAiEEAstuVQrAR_ArXtFQOyA28_yA61_yA41_A41_GG_Qo__A38_Qo__Qo_AGyA28_yAGyA63__A34_yAGyA72__A63_tGGA78_A78_A78_A78_AA09SeparatorF0VtGG_A82_A28_yAGyA63__A78_A78_tGGtGG_AE25BorderlessButtonMenuStyleVQo__Qo_AA15SecondaryButtonVA92_tGGtGG_Qo__Qo_tGyXEfU_A95_yXEfU0_A93_yXEfU0_yycfU3_ySayAA012ErrorOverlayF0V6ActionVGSg_Say10Foundation3URLVGSgtcfU_ + 1688
19  AppNameHere                           0x000000010420e928 $s9AppNameHere17FilesPickerWorkerC7execute4data10completionyAA0cD13ConfigurationV_ySayAA16ErrorOverlayViewV6ActionVGSg_Say10Foundation3URLVGSgtcSgtF + 2376
20  AppNameHere                           0x000000010431263c $s9AppNameHere21FileManagerHeaderViewV4bodyQrvg7SwiftUI05TupleF0VyAE0F0PAEE7paddingyQrAE4EdgeO3SetV_12CoreGraphics7CGFloatVSgtFQOyAiEE5frame5width6height9alignmentQrAR_ArE9AlignmentVtFQOyAE6HStackVyAGyAE06ScrollF0VyAZyAGyAC09componentF033_FF7633ACFDEA3379B9E4F13A23535CF6LL4text10isSelected12onTapGestureQrAA10BaseStringO_SbyyctFQOy_Qo__AE7ForEachVySayAA6FolderVGSSA8_GtGGGSg_AE6SpacerVAGyAA11ImageButtonVSg_A23_A22_tGSgAiEEAstuVQrAR_ArXtFQOyA20__Qo_A22_A22_A26_AE6VStackVyAiEE12cornerRadius_11antialiasedQrAQ_SbtFQOyAZyAGyAiEE11buttonStyleyQrqd__AE20PrimitiveButtonStyleRd__lFQOyAE6ButtonVyAiEE10background_AVQrqd___AXtAeHRd__lFQOyAiEEAstuVQrAR_ArXtFQOyAiEE15foregroundColoryQrAE5ColorVSgFQOyAE5ImageV_Qo__Qo__A38_Qo_G_AE16PlainButtonStyleVQo__A48_tGG_Qo_GtGG_Qo__Qo__AiEEAJyQrAN_ARtFQOyAiEEAstuVQrAR_ArXtFQOyAZyAGyAiEEA31_yQrqd__AEA32_Rd__lFQOyA34_yA41_G_A47_Qo_Sg_AE19_ConditionalContentVyAE4TextVA63_GA20_AZyAGyAA15SearchTextFieldV_AiEE9fixedSizeQryFQOyAiEE9menuStyleyQrqd__AE9MenuStyleRd__lFQOyAE4MenuVyAiEEA29__A30_QrAQ_SbtFQOyAiEEA35__AVQrqd___AXtAeHRd__lFQOyAiEEAstuVQrAR_ArXtFQOyA28_yA61_yA41_A41_GG_Qo__A38_Qo__Qo_AGyA28_yAGyA63__A34_yAGyA72__A63_tGGA78_A78_A78_A78_AA09SeparatorF0VtGG_A82_A28_yAGyA63__A78_A78_tGGtGG_AE25BorderlessButtonMenuStyleVQo__Qo_AA15SecondaryButtonVA92_tGGtGG_Qo__Qo_tGyXEfU_A95_yXEfU0_A93_yXEfU0_yycfU3_ + 372
21  SwiftUI                             0x00000001b6842188 OUTLINED_FUNCTION_2 + 900
22  SwiftUI                             0x00000001b5ed8838 __swift_memcpy3_1 + 10188
23  SwiftUI                             0x00000001b5edc760 __swift_memcpy3_1 + 26356
24  SwiftUI                             0x00000001b5edc6ac __swift_memcpy3_1 + 26176
25  SwiftUI                             0x00000001b64c52e8 OUTLINED_FUNCTION_0 + 5048
26  SwiftUI                             0x00000001b530d558 OUTLINED_FUNCTION_37 + 1502636
27  SwiftUI                             0x00000001b5fe5bd0 OUTLINED_FUNCTION_8 + 760
28  SwiftUI                             0x00000001b606c0d0 OUTLINED_FUNCTION_2 + 40
29  SwiftUI                             0x00000001b5fe5bd0 OUTLINED_FUNCTION_8 + 760
30  SwiftUI                             0x00000001b682fd84 OUTLINED_FUNCTION_4 + 4424
31  SwiftUI                             0x00000001b682f53c OUTLINED_FUNCTION_4 + 2304
32  SwiftUI                             0x00000001b69dd1e4 OUTLINED_FUNCTION_3 + 1732
33  SwiftUI                             0x00000001b5deadd0 OUTLINED_FUNCTION_16 + 32804
34  SwiftUI                             0x00000001b5deb428 OUTLINED_FUNCTION_16 + 34428
35  SwiftUI                             0x00000001b5df47c0 OUTLINED_FUNCTION_16 + 72212
36  SwiftUI                             0x00000001b5df45dc OUTLINED_FUNCTION_16 + 71728
37  AppKit                              0x000000018ec0de24 _routeMouseUpEvent + 132
38  AppKit                              0x000000018e220b80 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 384
39  AppKit                              0x000000018e22082c -[NSWindow(NSEventRouting) sendEvent:] + 284
40  AppKit                              0x000000018e8c7c08 -[NSApplication(NSEventRouting) sendEvent:] + 1556
41  AppKit                              0x000000018e51b1bc -[NSApplication _handleEvent:] + 60
42  AppKit                              0x000000018e0e8460 -[NSApplication run] + 512
43  AppKit                              0x000000018e0bf708 NSApplicationMain + 880
44  AppNameHere                           0x000000010447ea34 $sSo21NSApplicationDelegateP6AppKitE4mainyyFZ + 40
45  AppNameHere                           0x000000010447e9fc $s9AppNameHere11AppDelegateC5$mainyyFZ + 44
46  AppNameHere                           0x000000010447ebfc main + 28
47  dyld                                0x000000018a4c5058 start + 2224

Ok, It looks like a similar issue https://github.com/apple/swift-nio/issues/2223 I've seen on the swift-nio repository. The suggested way to resolve this was initialise the singleton on a background thread. This is going to require a little more work to get rid of the warning.
Does the upload still fail after seeing the warning above?

Yes... I mean is not failing (calling the completion function with an error), it's just stuck...

As a test can you stick the following lines somewhere in the initialisation for your application
DispatchQueue.global(qos: .background).async {
    _ = NIOThreadPool.singleton
}

@adam-fowler tested... in the debugger there is no warning displayed, but the upload process is stuck..

Ok looks like we have two issues here. The warning about thread priorities and then the hang.
For the hang can we clean the code up a little. And also add some logging to get a better idea what is going on

The AWSClient should be global. You shouldn't create one for each upload operation.
With the current setup you must be calling AWSClient.syncShutdown somewhere otherwise you would get an error when the client is deleted. Where is this being called? If it is immediately after the multipartUpload call then that'll be the probable cause of your issues. multipartUpload starts an asynchronous process. That process is not complete when it returns. So calling syncShutdown immediately after will kill the process before it completes.
Lets pass a Logger to the multipartUpload operation to see if we get any output.

var logger = Logger(label: "s3hang")
logger.logLevel = .trace
// Your s3 multipart upload call
s3.multipartUpload(request, ..., logger: logger)

We can also get Soto to output details about every request sent to AWS

s3 = s3.with(middlewares: AWSLoggingMiddleware()

@adam-fowler  I sent you an email with the logs file. Also, regarding the first point "The AWSClient should be global. You shouldn't create one for each upload operation." I might have an issue. The app supports multiple accounts and it can happen to have a different configuration for each account. Even if I optimise for use a single instance for an user, if there 10 accounts connected on the same app, I want to use different instances because each user has his own configuration.

Are you uploading all of these at the same time? You might want to queue them. You could be opening too many connections.

Just looking through the logs you sent.

From the log I only see 18 files being loaded. It appears the other 2 don't get loaded at all. Are you sure you are calling the multipart upload 20 times?
Of those 18 uploads only one is larger than 5MB and might benefit from multipartUpload over putObject.

Yes, all the files goes to multipart upload. In previous versions we had made some "hard core tests" like uploading more than 100+ files... selecting like 5 big videos and images, after the batch is ready, start again with other images and so on. Something happen in the last Soto SDK updates... We released the app in 2021 and we didn't had any use in the previous releases.

I only see 18 Open file ... log entries. This is output as soon as the multipart upload function has opened a file ie the first operation it performs. Can you please verify the number of times you are calling the function by adding a log entry prior to calling multipartUpload.

Check email, I sent you some screenshots as well and a new logs file, this time crashes sooner...

Are you able to use a branch of Soto. If so could you use the threadpool-singleton branch. And send me the logs from that.

Also if you aren't able to use one AWSClient could you at least use just the one HTTPClient instead of creating a new one with each AWSClient.
import AsyncHTTPClient

let globalHTTPClient = HTTPClient(eventLoopGroupProvider: .singleton)

let awsClient = AWSClient(..., httpClientProvider: .shared(globalHTTPClient))

Tried both, using singleton for HTTPClient cause a crash, I sent you an email with more details & logs

Sorry I wasn't clear enough globalHTTPClient has to be a global variable. The idea is there is one HTTP client used by all of the AWSClients.

I did as you said, tried 3 tests with 20 images each time, works like a charm.

I think the issue you were seeing was related to the fact each HTTPClient you create, creates a new EventLoopGroup and a new connection pool. Your application was creating an HTTPClient for every request which could cause a thread explosion.

Oh wow, hmmm, should I wait for the SDK update before doing a new release? Maybe a mechanism, by default, to prevent things like this to happen?

6.8 has been released with the singleton stuff


Added New similarity algorithm using Gensim Library

Gensim is billed as a Natural Language Processing package that does ‘Topic Modeling for Humans’. But it is practically much more than that. It is a leading and a state-of-the-art package for processing texts, working with word vector models (such as Word2Vec, FastText etc) and for building topic models.
-Updated READ.me
-Updated requirements.txt

Uploaded new file "gensim_similarity"

Good idea! But could you please organize your code to a class, something like GensimSimilarity?

Good idea! But could you please organize your code to a class, something like GensimSimilarity?
I updated the file you can check now :)

Here are the exceptions:

workdir folder should locate same directory with program file.
On Sun, Oct 6, 2019 at 9:42 AM luozhouyang<EMAIL_ADDRESS>wrote:

Here are the exceptions:
[image: exception]
https://user-images.githubusercontent.com/34032031/66270096-1fe4ed80-e882-11e9-95a5-bc2939077491.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luozhouyang/python-string-similarity/pull/8?email_source=notifications&email_token=AKB62UFP6R55ZZGJQHUWNULQNHTNBA5CNFSM4I5B4KW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOKMUA#issuecomment-538748496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKB62UGNTJ5YJWN6ZKZH7ADQNHTNBANCNFSM4I5B4KWQ
.

It seems that integration with gensim is not that easy.
Both gensim and nltk are heavy libraries, and are often used in deep learning based NLP tasks.
I tend to keep this library simple and small. Let it complement these frameworks, not integrate with them.


Allow compile for Windows

Description
If you are interested in a wheel for Windows, have a look at the pull request code. It is quickly hacked (e.g. there is one type cast error which for Windows I just removed) and not well tested but it does create the windows wheel which works with the pettingzoo magent examples. More testing then a quick run whether the agents move and the pygame Gui is displayed was not done. But maybe it serves as a starting point for you.
To build the wheel I did:
1. Do once
python -m venv magent_venv
magent_venv\scripts\activate
pip install cmake-build-extension wheel
2. BUILD Wheel
python setup.py bdist_wheel
gives
=> dist\magent-0.2.0-cp38-cp38-win_amd64.whl

Hi @git5001, apologies for taking awhile to respond to this, but are you free to discuss this? From our end, we have no idea how Windows works and your PR doesn't really work for us on a valid Windows install.
cc: @jkterry1

No problem, there is no hurry on my side. I just did a quick conversion of your build file to work for Windows (10) since I had no access to a Linux machine then and it is convenient when I can use it on both.  I thought maybe you benefit from my results as well and posted it here.
The build process does create binary windows wheel for me which runs with my example (tiger_deer). But I ave I also no expert in Windows wheel building so if it does not work for you I don't think I can help too much.
To compile it I needed the Microsoft Visual Studio (VS2019) build tools installed. I used MSVC 19 (CMake reports:  "The C compiler identification is MSVC 19.23.28106.4"). The VS build tools installed with me with these components:

MSVC 142 - VS 2019
Windows 10 SDK (10.x)
c++ CMake for Windows
Testtools/Buildtools
c++ address sanitizer
With these settings CMake manages to find the build tools and sets up all automatically.

python setup.py bdist_wheel

does then create
dist/magent-0.2.0-cp38-cp38-win_amd64.whl

PS: If I remember correctly, there is one type cast in your code which the windows C compiler did not like. I just removed it. One would have to look at this cast whether it was needed.

I uploaded two wheels (one tested (python 3.8) one not) to
https://github.com/git5001/MAgent-Wheels
Maybe try whether they work for you.

PS: The wheels and build are for cpython only (not pypy).

@git5001 thanks a ton. Is it possible for the wheel building to be added to our CI the way all the other wheels are built (and windows testing added to CI with github actions), especially given that none of us actually use Windows?

Yes it seems possible. I made a test workflow and it does build a windows wheel. It is partly hardcoded and not very clean and just for one python version (3.8) but once it runs you can probably extend it to your workflow file. The build example is
https://github.com/git5001/Magentwindows-/blob/master/.github/workflows/msbuild.yml
name: MSBuild

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

env:
  # Path to the solution file relative to the root of the project.
  SOLUTION_FILE_PATH: .

  # Configuration type to build.
  # You can convert this to a build matrix if you need coverage of multiple configuration types.
  # https://docs.github.com/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
  BUILD_CONFIGURATION: Release

permissions:
  contents: read

jobs:
 build-wheels:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        include:
        - os: windows-latest
          python: 38

    steps:
    - uses: actions/checkout@v3

    - name: Add MSBuild to PATH
      uses<EMAIL_ADDRESS>      env:
        # Not used...
        CIBW_BUILD: cp${{ matrix.python }}-${{ matrix.platform }}
        CIBW_ARCHS: all
        CIBW_BUILD_VERBOSITY: 1

    - name: Build
      working-directory: ${{env.GITHUB_WORKSPACE}}
      run:  |
        pip install wheel cmake-build-extension
        pip wheel .  --no-deps -w wheelhouse/

    - uses: actions/upload-artifact@v3
      with:
        path: ./wheelhouse/*.whl

creates magent-0.2.0-cp39-cp39-win_amd64.whl

@git5001 Do you mind adding this to CI, then we can merge this PR? Thanks!

As a separate .workflow file parallel to yours or merged together?

Other than the one comment above, all  the changes look pretty reasonable to me.
As for the workflow, I think you should be able to merge the files or leave them seperate, I don't think it will matter.

I made the structure cast change to avoid the IFDEF  @jjshoots @benblack769
I merged the ms windows build into your workflow file (it works on a copy but please test on your original one) @jjshoots
There was a little commit problem on the fork which I hoped I fixed with the uncommit above (git5001 force-pushed the master branch from bf786ff to fe5263b) @git5001

So I would say everything works now. Please check :-)

@benblack769 @git5001 the changes look pretty good to me (as in I can't see it breaking things with Linux and MacOS). If Ben gives the green light then I'll merge this. Thanks for the help Git.


Much of the profile dominated by unknown_java

As requested a new issue for this issue:

If you run the Aeron Archiving Media Driver for example you get this profile
When I run my own program about half the stack is unknown_java
I'm running with the Oracle 17 jdk :
java version "17.0.4" 2022-07-19 LTS
Java(TM) SE Runtime Environment (build 17.0.4+11-LTS-179)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.4+11-LTS-179, mixed mode, sharing)
(Also tried with openjdk -same result)
ProductName: macOS
ProductVersion: 12.6
BuildVersion: 21G115

Walking the stack during ‘System.nanoTime’ is for some reason difficult for AGCT. You can use a JMH workload to demonstrate.

Thanks for your reply.
That's not altogether surprising that a lot of stack traces would be lost, because System.nanotime() is a in the busy spin loop - but a shame nevertheless.  In your experience is there a workaround to this e.g. would it be better to use a C call from JNI to get the time (rather than the Agrona OffsetEpochNanoClock strategy to get wall time)? Although I notice that the stack gets to mach_absolute_time so not sure if even that would help? Sorry being lazy here but do you know if this is particularly problematic on osx or have you seen it on other oss as well?

Interestingly this is the same Aeron Archive Media Driver profiled under Flight Recorder (also AGCT?) - it doesn't seem to have any issues processing the stack traces (or at least it doesn't admit to any...) - although it doesn't tell you where in the method it got stuck i.e. it doesn't tell you it got stuck in the System.nanotime call.

Thank you for your excellent detailed answer - I suspected JFR might be being a bit sneaky...
I will try on Linux.

@vans239 --cstack vm makes use of DWARF unwinding info on Linux, so async-profiler should be able to get stack traces of System.nanoTime on Linux_x64 (a quick check confirms it does). If you still see an issue, please submit a bug or reopen this one. There is a known issue with nanoTime/currentTimeMillis intrinsics on AArch64 (#819) - I will create a workaround for it.

critical JNI and nalim would have same problem

Critical JNI should not be a problem: JVM saves last Java frame anchor when calling native methods, whether JNICritical or not. Again, if you see an issue with critical natives, please submit a bug report.
Nalim is a different story: it generates a small frameless trampoline to call target native function. async-profiler will show as if this native function is called directly from the parent Java method. However, if an execution sample hits the trampoline itself, it will likely yield [unknown_Java].


added redis authentication support

@AmitKannaujiya thanks for your contribution, please follow the suggestion from @gkorland and possibly also add some tests!

Hello @palicao  & @gkorland : thankyou for the comments... I had added changes suggested. Please review it .


Adds ignite plugin new to CLI

This adds basic plugin generation to Ignite 2.0.
$ ignite plugin new ignite-foo

This will almost certainly need improvement before we release, but that's probably best discovered by using it.

w00t!