Initial version of 2.0 version

This is a preview of the 2.0 version if some people wants to give a try, it should be already functional, however there are few things that needs to be done before merging / releasing.
What's planned

This library will now follow semver and support multiple version of the docker api by using different namespaces
Generated code comes from the official swagger file from docker, however there is some glitches and bad specficiation that needs to be fixed (but it only consist of some bad new lines in the yaml and wrong nullable possibility)
It's fully BC break and unfortunately it's too much work to add a compatibility layer :/, unless someone wants to do it (as i use a different class name / functions / namespace, it can be added)

Basically you will be able to do the following :
$docker = Docker::create(Docker::VERSION_1_32);
$docker->image->imageBuild(....)

What's missing for a release (contributions welcome)

[ ] More tests
[x] Better test system (to test different version of the api on different version of docker)
[ ] Rewriting docs
[ ] Better code api docs (not sure if possible)
~Full Async support with Amp / Artax~ : too hard ATM will be done in a future version
[x] Symfony / PHP-HTTP Factory Client support: done

3400 modified files! :o
Are you just moving 2.x to master?
Which constraint should we use on composer if we want to try 2.x? Is it currently usable even if not stable?

Are you just moving 2.x to master?

Yes, and accept merge request on the 1.24 if there are good enough

That looks great :+1:
I've tried it out in our project and I'm experiencing some troubles with the services API. When I try to list or inspect a swarm service, I'm getting InvalidArgumentExceptions in the TaskSpecContainerSpecPrivilegesCredentialSpecNormalizer and TaskSpecContainerSpecPrivilegesSELinuxContextNormalizer because NULL is passed as $data to the denormalize() method.

yea same issue because i think this stuff is optional.
as example the credential is windows only
I have an other issue. I can not filter like:
$worker = $docker->service()->serviceList(['filters' => ['name' => 'worker']]);
or:
$worker = $docker->service()->serviceList(['filters' => ['label' => 'worker']]);

@mburtscher @boonkerz You may opened dedicated issue for that.

@joelwurtz I've provided some added tests in #276, the code coverage is pretty high even though test quality of some tests could be improved.
Can you be more specific in your goal / requirement before a release?
You mention rewriting docs before a release, is this a hard requirement?
While I understand that docs are needed, from a usage perspective what developers care about is that the API of the library doesn't have breaking changes.
The sooner the API is "frozen" for the initial 2.0 release the sooner people can start using this and that might increase the contributions.

Can you be more specific in your goal / requirement before a release?

Like any open source project, i mainly start working on docker-php for my own needs, and know my number one requirement is to have an async version of docker-php, however this can be done in a 2.1 release, so not so hard.

You mention rewriting docs before a release, is this a hard requirement?

Not really, but it must provide docs on how the installation is different from the last version (as you will be able to have a specific version, and also the dependent library is not semver so there should be some warnings)
In fact there is no real hard requirement, but i didn't have the time to test differents API point and i don't really want to create a release where i may break BC because it's not working

Not really, but it must provide docs on how the installation is different from the last version (as you will be able to have a specific version, and also the dependent library is not semver so there should be some warnings)

Can you elaborate on what you mean by will be able to have a specific version? I can't find references to that in the repository.

The 2.0 version will have a requiremend on docker-php/docker-php-api: 4.1.* this requirement define the docker api version, as an example you will be able to use the 1.25 api of docker by forcing the dependency on this library to 4.1.25.* or the 1.32 by having 4.1.32.*

actually i have notices:
Warning: Declaration of Docker\Resource\ImageResourceTrait::imageBuild($inputStream, array $parameters = Array, string $fetch = self::FETCH_OBJECT) should be compatible with Docker\API\Client::imageBuild(string $inputStream, array $queryParameters = Array, array $headerParameters = Array, string $fetch = self::FETCH_OBJECT) in /home/thomas/projekte/isc/vendor/docker-php/docker-php/src/Docker.php on line 16

Warning: Declaration of Docker\Resource\ImageResourceTrait::imageCreate($inputImage, array $parameters = Array, string $fetch = self::FETCH_OBJECT) should be compatible with Docker\API\Client::imageCreate(string $inputImage, array $queryParameters = Array, array $headerParameters = Array, string $fetch = self::FETCH_OBJECT) in /home/thomas/projekte/isc/vendor/docker-php/docker-php/src/Docker.php on line 16

Warning: Declaration of Docker\Resource\ImageResourceTrait::imagePush(string $name, array $parameters = Array, string $fetch = self::FETCH_OBJECT) should be compatible with Docker\API\Client::imagePush(string $name, array $queryParameters = Array, array $headerParameters = Array, string $fetch = self::FETCH_OBJECT) in /home/thomas/projekte/isc/vendor/docker-php/docker-php/src/Docker.php on line 16

Warning: Declaration of Docker\Resource\ExecResourceTrait::execStart(Docker\API\Model\ExecIdStartPostBody $execStartConfig, string $id, array $parameters = Array, string $fetch = self::FETCH_OBJECT) should be compatible with Docker\API\Client::execStart(string $id, Docker\API\Model\ExecIdStartPostBody $execStartConfig, string $fetch = self::FETCH_OBJECT) in /home/thomas/projekte/isc/vendor/docker-php/docker-php/src/Docker.php on line 16

@boonkerz please see https://github.com/docker-php/docker-php/issues/294


Session Detached (reason=timeout)

Opens on the first screen then constantly getting timeout error. App is open and running, but crashes when timeout error occurs.
iPhone6 - 12.5.2
frida 14.2.18

Make sure your iPhone was jailbreaked and install 'frida server' from Cydia ,  https://frida.re/docs/ios/#with-jailbreak

My phone is jailbroken, and I have frida  - 14.2.18

Please try to connect your jailbroken iPhone by running frida-trace command on your Mac.
frida-trace -U Cydia -m "+[NSURL URLWithString:]"
And check the output to make sure frida can connect your iPhone.
Currently, CatFrida use frida-core 14.2.3, maybe it needs upgrade.

Payload$ frida-trace -U Cydia -m "+[NSURL URLWithString:]"
Failed to spawn: ambiguous name; it matches: Cydia (pid: 12063), Cydia (pid: 12062), Cydia (pid: 12061), Cydia (pid: 12060), Cydia (pid: 12059), Cydia (pid: 12058), Cydia (pid: 12057), Cydia (pid: 12056), Cydia (pid: 12055), Cydia (pid: 12054), Cydia (pid: 12053), Cydia (pid: 12052), Cydia (pid: 12051), Cydia (pid: 11168)
Still getting session attached error

Payload$ frida-trace -U Cydia -m "+[NSURL URLWithString:]" Failed to spawn: ambiguous name; it matches: Cydia (pid: 12515), Cydia (pid: 12514), Cydia (pid: 12513), Cydia (pid: 12512), Cydia (pid: 12511), Cydia (pid: 12510), Cydia (pid: 12499) Payload$ frida-trace -U 12515 -m "+[NSURL URLWithString:]" Instrumenting...                                                         +[NSURL URLWithString:]: Auto-generated handler at "/Users/ben/Documents/__handlers__/NSURL/URLWithString_.js" Started tracing 1 function. Press Ctrl+C to stop.
Still getting session detached error

Sorry, I can't reproduce this error in my Mac. You can clone the repo and build by yourself. If you find a bug, any PR is welcome.

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook


mk:develop to upstream

Merge local develop branch to upstream

Pull Request just opened could be reviewed first before merging to the upstream

Pull Request just opened could be reviewed first before merging to the upstream

Wait for https://github.com/CosmoStat/sp_validation/pull/117


Update puppet-lint and fix the warnings that ensue.

We'd like to install a lint plugin so we need a newer version of
puppet-lint. This commit gives us that newer version

Yep, looks good :+1:

:+1:


Startup performance

I'd like to understand where we spend time when starting a container; I filed #40 since I assume we spend a non-trivial amount of time when starting, but I'm not sure if there is anywhere else we could look.
@jsturtevant — is the RUST_LOG implementation in the rust-extensions crate helping us with tracing here?

There isn't a ton of logs in the underlying shim that would help.
@Mossaka has been working on adding open telemetry tracing to runwasi.  That would be able to show more details on where we are spending time.  We has some early results and I think we found it was in the setting up the container NS's that we were spending time.
Cleaning up the disk operations in #40 will add some improvements.  I saw an improvement in the wasmtime shim after avoiding disk reads/writes with the OCI artifacts but it was not where were spending most of our time.

yeah this is the work @jsturtevant's referring to: https://github.com/containerd/runwasi/issues/10

I think even only being able to set the RUST_LOG level for tracing throughout the shim dependencies would be a very good start in starting to diagnose this.

A quick update on the findings of the startup performance -
After adding traces to runwasi, I found that runwasi isn't deleting the shim socket after the shim gets deleted. (e.g. /run/containerd/<hash>). This socket address causes the shim::spawn function from rust-extensions to hang for over 1 second (e.g. issue https://github.com/containerd/rust-extensions/issues/263), which could be a reason why it takes so much time to start a container using runwasi.
Jeager tracing

The wait_socket_working() function loops connection to the ttrpc client using the undeleted socket address from last run 200 times and each time waits for 5ms, which contribtues to the 1s hang on start_shim function.
What's next?
I am following up with rust-extension folks to figure out why exactly are we waiting for such a long time to establish a connection with a socket address. I am also investigating how to properly delete the shim socket address in runwasi after the shim gets deleted, which in turn could make the startup much faster.
In theory, I think start_shim should take less time than task_create request which takes about 40ms.

This is excellent info, @Mossaka, thank you so much for digging into this!

A quick update:
Abel's comment at https://github.com/containerd/rust-extensions/issues/263 answers why we have to wait for the socket. So the only question remains: why doesn't the runwasi shim delete it's socket address after its get closed?
After digging more into the syscalls, I found that the shim::wait() actually unlinks the entire bundle path (e.g. /run/containerd/io.containerd.runtime.v2.task/<namespace>/<id>) which contains the address file for reading the socket address. This means that the runwasi shims actually crash every time right before they terminate. This explains why the socket address isn't deleted before shim close.
But why does the bundle path gets deleted? I am not sure at the moment. Still trying to figure it out. It might related to youki's libcontainer (e.g. https://github.com/containers/youki/issues/2772).

@Mossaka is https://github.com/containers/youki/pull/2780 going to affect the startup performance we're seeing here?
Thanks!

@Mossaka is containers/youki#2780 going to affect the startup performance we're seeing here?
Thanks!

Yes, that will make the startup performance much faster

https://github.com/containerd/runwasi/pull/601 once this PR is merged, we can do a release of runwasi and then bump the version in the spin shim. It should make start up much faster

i just bump the newest release version of the runwasi, will do some tests to see the perf gain

Test is performed using spin command trigger on a simply rust program that outputs the system timestamp. if you are interested the script can be found here
Before
#########################################
Containerd + RUNWASI with Spin SHIM
#########################################

Running experiment 1
Start timestamp in milis:<PHONE_NUMBER>777 milliseconds
End timestamp in milis:<PHONE_NUMBER>917 milliseconds
Time difference: 1140 milliseconds

Running experiment 2
Start timestamp in milis:<PHONE_NUMBER>086 milliseconds
End timestamp in milis:<PHONE_NUMBER>240 milliseconds
Time difference: 1154 milliseconds

Running experiment 3
Start timestamp in milis:<PHONE_NUMBER>307 milliseconds
End timestamp in milis:<PHONE_NUMBER>432 milliseconds
Time difference: 1125 milliseconds

Running experiment 4
Start timestamp in milis:<PHONE_NUMBER>533 milliseconds
End timestamp in milis:<PHONE_NUMBER>661 milliseconds
Time difference: 1128 milliseconds

Running experiment 5
Start timestamp in milis:<PHONE_NUMBER>079 milliseconds
End timestamp in milis:<PHONE_NUMBER>217 milliseconds
Time difference: 1138 milliseconds

Mean: 1137 milliseconds
Median: 1138 milliseconds
Mode: 1154 milliseconds
Standard Deviation: 10.19 milliseconds
Minimum Time: 1125 milliseconds
Maximum Time: 1154 milliseconds

After
#########################################
Containerd + RUNWASI with Spin SHIM
#########################################

Running experiment 1
Start timestamp in milis:<PHONE_NUMBER>599 milliseconds
End timestamp in milis:<PHONE_NUMBER>736 milliseconds
Time difference: 137 milliseconds

Running experiment 2
Start timestamp in milis:<PHONE_NUMBER>817 milliseconds
End timestamp in milis:<PHONE_NUMBER>948 milliseconds
Time difference: 131 milliseconds

Running experiment 3
Start timestamp in milis:<PHONE_NUMBER>988 milliseconds
End timestamp in milis:<PHONE_NUMBER>117 milliseconds
Time difference: 129 milliseconds

Running experiment 4
Start timestamp in milis:<PHONE_NUMBER>152 milliseconds
End timestamp in milis:<PHONE_NUMBER>273 milliseconds
Time difference: 121 milliseconds

Running experiment 5
Start timestamp in milis:<PHONE_NUMBER>309 milliseconds
End timestamp in milis:<PHONE_NUMBER>435 milliseconds
Time difference: 126 milliseconds

Mean: 128 milliseconds
Median: 129 milliseconds
Mode: 137 milliseconds
Standard Deviation: 5.29 milliseconds
Minimum Time: 121 milliseconds
Maximum Time: 137 milliseconds

To close this issue, I am working on a PR to add opentelemetry capability to runwasi and its shims, which helped me to discover suprises and trace where we spend more time on.


Add imagePullPolicy config for executors

I'm customizing some features of Argo with minikube and want to use locally built controller and executor images. I'd like to specify executor image pull policy along with executor image. Could you consider adding this feature?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Remove version: Google.Chrome.Canary version 127.0.6500.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://dl.google.com/release2/chrome/ad7ftikjruwppdnbozlkjxkijcmq_127.0.6500.0/127.0.6500.0_chrome_installer.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


uninitialized value by static analysis tools

random.cpp 131
 uint32_t tmp;  //'tmp' is not uninitialized
    do {
        GetRandBytes((unsigned char*)&tmp, 4);  //used here for first loop
    } while (tmp == 0 || tmp == 0x9068ffffU);

False positive as it will be initialized in the first loop iteration.


Odd whitespace as part of the field

Python accepts "odd" whitespace when parsing numbers (e.g. newlines, nonbreakable space, etc.).  We currently only accept spaces (except for the special "whitespace delimiter").  This is a mild regression when compared to loadtxt.
This could be fixed in the float parser core.

Changed now to support any whitespace for the moment.  But we could decide to swap that back.

Should be tested sufficiently well now.


DOM lib is missing Intersection Observer API on window global

TypeScript Version:  2.3.4
Code
The browser Intersection Observer API defines these on the window:
window.IntersectionObserver
window.IntersectionObserverEntry

Expected behavior:
These should be defined in the DOM lib typings.
Actual behavior:
They are not defined, so I get type errors.

PRs welcomed. You can find more information about contributing lib.d.ts fixes at https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md#contributing-libdts-fixes.

Can this issue be closed? Looks like the change has already been merged into master?

Aha, looks like they are in the typings, just not exposed on the window interface:
new IntersectionObserver(() => {}); // no error
window.IntersectionObserver // error

As a temporary fix
export {}
declare global {
  interface Window {
    IntersectionObserver: typeof IntersectionObserver
  }
}

IntersectionObserverEntry lacks isVisible property.
Chrome Version 87.0.4280.88

This has been added in 3.6, the issue can be closed


use go mod to build videoroom

Description
Reference issue
Fixes #...

Sorry missed this! go.mod is in the repo now :)
thanks @feixiao


perf: prioritize package version type checks

The rare edge case should be checked last.

Changes are visible to end-users: no
Test plan

Covered by existing test cases

... or not


getTreeNode(...) is undefined

🐛 Bug Report

Hello. I am trying to replicate the Select component in the official TypeScript example so I can then modify it for my application, but I get an error when clicking the dropdown button.
🤔 Expected Behavior

The popover should appear on button click.
😯 Current Behavior

I click the dropdown button and my page crashes with this error:
Uncaught TypeError: $9bf71ea28793e738$export$d06fae2ee68b101e.getTreeNode(...) is undefined
    useRestoreFocus FocusScope.tsx:516
    React 14
    onFocus useSelect.ts:161
    onFocus useFocus.ts:64
    e08e3b67e392101e chain.ts:20
    React 14
    focus useFocusVisible.ts:128
    $7215afc6de606d6b$export$de79e2c695e052f3 focusWithoutScrolling.ts:33
    onPointerDown usePress.ts:342
    React 23
    <anonymous> main.tsx:6
[FocusScope.tsx:516:19](http://localhost:5173/WebCV/node_modules/<EMAIL_ADDRESS>    useRestoreFocus FocusScope.tsx:516
    React 9
    performSyncWorkOnRoot self-hosted:1406
    React 5
    dispatchSetState self-hosted:1518
    onFocus useSelect.ts:161
    onFocus useFocus.ts:64
    e08e3b67e392101e chain.ts:20
    React 14
    bind_applyFunctionN self-hosted:1683
    dispatchDiscreteEvent self-hosted:1640
    focus useFocusVisible.ts:128
    $7215afc6de606d6b$export$de79e2c695e052f3 focusWithoutScrolling.ts:33
    onPointerDown usePress.ts:342
    React 15
    bind_applyFunctionN self-hosted:1683
    dispatchDiscreteEvent self-hosted:1640
    React 4
    forEach self-hosted:4909
    React 4
    <anonymous> main.tsx:6

💁 Possible Solution

No idea sadly. I couldn't find anything about this error online.
🔦 Context

First, I copied ListBox.tsx, Select.tsx and Popover.tsx into my working TypeScript + React + Tailwind project and remove the icons.
However, when I try to use it in my application I get an error on click.

💻 Code Sample

I couldn't reproduce this issue in a sandbox. Here's close representation of my code without working tailwind.
https://codesandbox.io/s/sweet-hooks-b3fpwx
If this gets any attention, I can link to my public repo and a broken branch for testing.
🌍 Your Environment

Software
Version(s)

vite
4.1.0

react
18.2.0

react-aria
3.22.0

react-stately
3.20.0

react-spectrum
N/A

Browser
Firefox 109.0.1

Operating System
Windows 11

🧢 Your Company/Team

I'm not an Adobe employee. I'm a Software Engineer using React Aria for my own projects.
🕷 Tracking Issue (optional)

N/A

Quick question. Are you using React StrictMode in your app?

I happen to have the same issue when using react 18.2.0.
I can confirm that it does happen only in strict mode.

We've addressed StrictMode in https://github.com/adobe/react-spectrum/pull/4564
Can you tell us what version of our packages you're using or try upgrading and see if the problem goes away?
Otherwise a codesandbox reproducing it would be very helpful in debugging this.

I am far from latest versions. Will upgrade and get back to this thread. thanks!

Closing due to this likely be handled by Strict Mode work in https://github.com/adobe/react-spectrum/pull/4564, feel free to re-open if this is still an issue.


Add MTE token

官方公告
https://twitter.com/MeteoriteQT/status/1496849398302527491
团队背景：
The MTE team has several developers with over 10 years of Internet experience and has focused on blockchain development in recent years.
项目基本情况：
MTE is the only official token of Meteorite,  Meteorite is a decentralized quantitative strategy platform with full DAO management, a robust ecosystem, high-quality data services and a limited NFT series.
官网：https://www.mte.cool
Telegram：https://t.me/meteorite_official
Twitter：https://twitter.com/MeteoriteQT
媒体报道：
收录的交易所：
转账所需 Gas Limit：60000

Parsing error in line 1:

Please use the official Twitter @@imTokenOfficial

Parsing error in line 1:

parsing error in json file？

Please use the official Twitter @imTokenOfficial，Then send me the link

how can i do this？which link should I send a twitter?


Fix and unskip broken tests

ValidateLogoutUri_FailsIfTheUriIsRelative and ValidateRedirectUri_FailsIfTheUriIsRelative were failing, they're skipped for preview2 so we can get a passing build of identity as a whole.

@javiercn do you have an update on this?

These are related to identity as a service, they only fail on Linux because of System.Uri having a different behavior. Given that we are not shipping it on 2.1 I'm moving it out the milestone.

We removed the code


config list still prints env variables

→ bacalhau-1.5.0 config list
 KEY                                               ENVIRONMENT VARIABLE                                       DESCRIPTION
 api.auth.accesspolicypath                         BACALHAU_API_AUTH_ACCESSPOLICYPATH                         AccessPolicyPath is the path to a file or directory that will be loaded as the p...
 ...

Acceptance Criteria here is to not print the env vars.


Fixing TransformerXL bool issue #1169

Fixing #1169 regarding using uint or bool masks in Transformer-XL and PyTorch 1.1.0 and 1.2.0.
Hopefully, this solution will be compatible upward with the future PyTorch releases.

Codecov Report

Merging #1199 into master will decrease coverage by 0.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #1199      +/-   ##
==========================================
- Coverage   80.83%   80.81%   -0.02%
==========================================
  Files          46       46
  Lines        7878     7881       +3
==========================================
+ Hits         6368     6369       +1
- Misses       1510     1512       +2

Impacted Files
Coverage Δ

pytorch_transformers/modeling_transfo_xl.py
56.9% <33.33%> (-0.1%)
: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 0b52642...38b79b5. Read the comment docs.

Codecov Report

Merging #1199 into master will decrease coverage by 0.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #1199      +/-   ##
==========================================
- Coverage   80.83%   80.81%   -0.02%
==========================================
  Files          46       46
  Lines        7878     7881       +3
==========================================
+ Hits         6368     6369       +1
- Misses       1510     1512       +2

Impacted Files
Coverage Δ

pytorch_transformers/modeling_transfo_xl.py
56.9% <33.33%> (-0.1%)
: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 0b52642...38b79b5. Read the comment docs.

Looks great to me!


Added a note to warn against branching outside of Studio Pro.

I asked a question about branching in the forum @ https://forum.mendixcloud.com/link/questions/97437 and was told to modify the documentations to note my finding.

@ppqn-as Please sign the CLA.

@ppqn-as Thanks for the PR!


reboot loop with id_open code

Hi there,
I was success with running france example and scanner as well. However I have got a reboot loop when trying to run the finland code and any other open_id example with the following stack trace. Tried on two different ESP32 board, both ESP32-S and one ESP32-WROOM-32. Im using board "Esp32 Dev Module" included in library esp 1.0.6 with Arduino IDE 1.8.9 with the following params:
240MHZ Wifi/BT, Flash Mode QIO, Flash size 32Mb, Partition scheme 2MB/NO OTA/2MB SPIFF, PSRAM disabled.
Decoding stack results
0x4008f088: invoke_abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c line 156
0x4008f305: abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/panic.c line 171
0x4019ed64: esp_phy_rf_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/phy_init.c line 197
0x4019efce: esp_phy_load_cal_and_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/phy_init.c line 673
0x4010ff4f: esp_bt_controller_enable at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/bt/bt.c line 1528
0x400d6106: btStart at /Users/syn/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/cores/esp32/esp32-hal-bt.c line 45
0x400d37f5: BLEDevice::init(std::__cxx11::basic_string, std::allocator >) at /Users/syn/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/libraries/BLE/src/BLEDevice.cpp line 339
0x400d142d: init2(char*, int, unsigned char*, unsigned char) at /Users/syn/Documents/Arduino/libraries/id_open/id_open_esp32.cpp line 212
0x400d0b0c: ID_OpenDrone::init(UTM_parameters*) at /Users/syn/Documents/Arduino/libraries/id_open/id_open.cpp line 253
0x400d081d: setup() at /var/folders/pp/t4fyr3yn03957kjjm25g393w0000gn/T/arduino_modified_sketch_51192/finland.ino line 27
0x400d6402: loopTask(void*) at /Users/syn/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/cores/esp32/main.cpp line 18
0x4009037a: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c line 143

Are you trying to transmit both WiFi and Bluetooth? If so, see issue #18 and the last paragraph of the id_ipen readme.

Yes, you can close this same as #18. Thanks

Close