Cannot login - Chromedriver not found

Just like the title says. It's been working for a few days with no issues. I used it 12 hours ago and it worked fine. Now I am getting a Chromedriver not found error after attempting the following script:  /usr/local/bin/python3 /Users/xxx/insta-likecom-bot/ilcbot.py -u xxx -p xxx  -t xxx -np 3 -nc -ff -mr --delay 2,20
The error is as follows:
[*] => Script started [*] => Downloading webdriver for your version of Chrome [*] => Loading Instagram [*] => Script ended with error [*] => Error: [ValueError] - There is no such driver by url https://chromedriver.storage.googleapis.com/115.0.5790/chromedriver_mac64.zip Traceback (most recent call last):   File "/Users/xxx/insta-likecom-bot/ilcbot.py", line 49, in <module>     insta = Insta(             ^^^^^^   File "/Users/xxxx/insta-likecom-bot/modules/instafunc.py", line 132, in __init__     executable_path=ChromeDriverManager(path=os.path.join(self.driver_baseloc, 'chrome')).install(),                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/webdriver_manager/chrome.py", line 39, in install     driver_path = self._get_driver_path(self.driver)                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/webdriver_manager/core/manager.py", line 30, in _get_driver_path     file = self._download_manager.download_file(driver.get_url())            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/webdriver_manager/core/download_manager.py", line 28, in download_file     response = self._http_client.get(url)                ^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/webdriver_manager/core/http.py", line 33, in get     self.validate_response(resp)   File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/webdriver_manager/core/http.py", line 16, in validate_response     raise ValueError(f"There is no such driver by url {resp.url}") ValueError: There is no such driver by url https://chromedriver.storage.googleapis.com/115.0.5790/chromedriver_mac64.zip [*] => Total time taken: 0.8177 seconds

same issue here

might be related to this https://stackoverflow.com/questions/76724939/there-is-no-such-driver-by-url-https-chromedriver-storage-googleapis-com-lates

agreed. I updated my Chromedriver via pip and now the error changed
[] => Script started
[] => Downloading webdriver for your version of Chrome
[] => Loading Instagram
[] => Script ended with error
[] => Error: [TypeError] - ChromeDriverManager.init() got an unexpected keyword argument 'path'
Traceback (most recent call last):
File "/Users/xxx/insta-likecom-bot/ilcbot.py", line 49, in
insta = Insta(
^^^^^^
File "/Users/xxx/insta-likecom-bot/modules/instafunc.py", line 132, in init
executable_path=ChromeDriverManager(path=os.path.join(self.driver_baseloc, 'chrome')).install(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: ChromeDriverManager.init() got an unexpected keyword argument 'path'
[] => Total time taken: 0.0064 seconds

@digitizesuccess @jakkul The latest version for Chrome webdriver available is ChromeDriver 114.0.5735.90, i.e., chrome web driver for v.115 isn't listed on https://chromedriver.chromium.org/downloads.
However, you could download it from https://googlechromelabs.github.io/chrome-for-testing/#stable for your operating system, and follow these steps:

Extract the compressed file and place the chromedriver in the same location as the script
Edit line # 131 of modules/instafunc.py and change it to
self.driver = webdriver.Chrome(executable_path='/path/of/the/chromedriver/',  options=options)

This should be able to let the script use the chromedriver you just downloaded.

It doesn't seem to be working. New error though so it getting somewhere.
[] => Script started
[] => Downloading webdriver for your version of Chrome
[] => Loading Instagram
[] => Script ended with error
[*] => Error: [WebDriverException] - Message: unknown error: cannot find Chrome binary
Stacktrace:
0   chromedriver                        0x0000000100b72a58 chromedriver + 4991576
1   chromedriver                        0x0000000100b69fa3 chromedriver + 4956067
2   chromedriver                        0x000000010071c607 chromedriver + 443911
3   chromedriver                        0x000000010074a4b7 chromedriver + 631991
4   chromedriver                        0x000000010074964c chromedriver + 628300
5   chromedriver                        0x000000010079224c chromedriver + 926284
6   chromedriver                        0x00000001007915af chromedriver + 923055
7   chromedriver                        0x0000000100788633 chromedriver + 886323
8   chromedriver                        0x00000001007546f9 chromedriver + 673529
9   chromedriver                        0x00000001007558de chromedriver + 678110
10  chromedriver                        0x0000000100b2e8a9 chromedriver + 4712617
11  chromedriver                        0x0000000100b338b4 chromedriver + 4733108
12  chromedriver                        0x0000000100b3a799 chromedriver + 4761497
13  chromedriver                        0x0000000100b3460a chromedriver + 4736522
14  chromedriver                        0x0000000100b0787c chromedriver + 4552828
15  chromedriver                        0x0000000100b52c08 chromedriver + 4860936
16  chromedriver                        0x0000000100b52d87 chromedriver + 4861319
17  chromedriver                        0x0000000100b62edf chromedriver + 4927199
18  libsystem_pthread.dylib             0x00007ff807f7c1d3 _pthread_start + 125
19  libsystem_pthread.dylib             0x00007ff807f77bd3 thread_start + 15
Traceback (most recent call last):
File "/Users/xxx/insta-likecom-bot/ilcbot.py", line 49, in
insta = Insta(
^^^^^^
File "/Users/xxx/insta-likecom-bot/modules/instafunc.py", line 131, in init
self.driver = webdriver.Chrome(executable_path='/Users/xxx/insta-likecom-bot/chromedriver-mac-x64/chromedriver',  options=options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/chrome/webdriver.py", line 81, in init
super().init(
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/chromium/webdriver.py", line 106, in init
super().init(
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/remote/webdriver.py", line 288, in init
self.start_session(capabilities, browser_profile)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/remote/webdriver.py", line 381, in start_session
response = self.execute(Command.NEW_SESSION, parameters)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/remote/webdriver.py", line 444, in execute
self.error_handler.check_response(response)
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/selenium/webdriver/remote/errorhandler.py", line 249, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: cannot find Chrome binary
Stacktrace:
0   chromedriver                        0x0000000100b72a58 chromedriver + 4991576
1   chromedriver                        0x0000000100b69fa3 chromedriver + 4956067
2   chromedriver                        0x000000010071c607 chromedriver + 443911
3   chromedriver                        0x000000010074a4b7 chromedriver + 631991
4   chromedriver                        0x000000010074964c chromedriver + 628300
5   chromedriver                        0x000000010079224c chromedriver + 926284
6   chromedriver                        0x00000001007915af chromedriver + 923055
7   chromedriver                        0x0000000100788633 chromedriver + 886323
8   chromedriver                        0x00000001007546f9 chromedriver + 673529
9   chromedriver                        0x00000001007558de chromedriver + 678110
10  chromedriver                        0x0000000100b2e8a9 chromedriver + 4712617
11  chromedriver                        0x0000000100b338b4 chromedriver + 4733108
12  chromedriver                        0x0000000100b3a799 chromedriver + 4761497
13  chromedriver                        0x0000000100b3460a chromedriver + 4736522
14  chromedriver                        0x0000000100b0787c chromedriver + 4552828
15  chromedriver                        0x0000000100b52c08 chromedriver + 4860936
16  chromedriver                        0x0000000100b52d87 chromedriver + 4861319
17  chromedriver                        0x0000000100b62edf chromedriver + 4927199
18  libsystem_pthread.dylib             0x00007ff807f7c1d3 _pthread_start + 125
19  libsystem_pthread.dylib             0x00007ff807f77bd3 thread_start + 15
[*] => Total time taken: 0.5417 seconds

Thanks! its fixed. Make sure you download the version of Chrome for automated testing and put it in the same folder.


Some buttons aren't supporting the dark theme. 😟

Light mode:

Dark mode:

Find such buttons and fix them.

i want to work on this issue please assign it to me @Spyware007

@Sapna127 Assigned to you

@Spyware007  I can contribute in this problem?

Assigned to you @amitkroutthedev

can assign this issue to me please

This ticket is not ready with the PR Buttons dark theme #210?


Clean up Terraform for the new transformer/adapter/reindexer with shared models

Follows #4918
We're passing in a bunch of config for the services that they no longer need (e.g. VHS table names and permissions). We should go through the Terraform and remove all of these.
Not urgent; I'd rather wait until we've been running this setup for a few weeks before turning it off.
Similar: #4903

Done.

Done.


Fix datasource dimensions sync bug

Pull request type
Jira Link: INT-

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other (please describe):

How to test this PR
To test the PR (pull request) that addresses this issue, you can perform a simple sync command with the type set as "datasources." Here's an example command:
storyblok sync --type datasources --source <SourceSpaceId> --target <TargetSpaceId>
What is the new behavior?
The new behaviour would be that all dimensions will be successfully synced from the source space to the target space, instead of just the first 25 dimensions.
Other information
While running the datasource sync command storyblok sync --type datasources --source <SourceSpaceId> --target <TargetSpaceId>, I observed that only the initial 25 dimensions are synchronized to the destination space.

I tested this solution and it didn't solve the problem completely, so yesterday I opened a new PR and fixed the problem, I published it in the version 3.25.1.
Thanks for the contribution, your PR helped me to understand the problem and fix, thank you so much my friend 😄


Move lint check to a job

Move pylint check to a job so it doesn't block
functional tests.

pylint is raising issues that were exposed before, not sure what is happening because the version is still 2.6.0.

pylint is raising issues that were exposed before, not sure what is happening because the version is still 2.6.0.

pylint is raising issues that were not exposed before, not sure what is happening because the version is still 2.6.0.

It was introduced from another patch that was passed checking before W0707 enabled.

pylint is raising issues that were not exposed before, not sure what is happening because the version is still 2.6.0.

It was introduced from another patch that was passed checking before W0707 enabled.

It was introduced from another patch that was passed checking before W0707 enabled.

Ah, so because there wasn't a conflict a previously passing PR merged that caused this new failure after it was rebased in GH? I guess that's an argument for not rebasing in GH but on the actual commit to retrigger CI... but it is very convenient.

It was introduced from another patch that was passed checking before W0707 enabled.

Ah, so because there wasn't a conflict a previously passing PR merged that caused this new failure after it was rebased in GH? I guess that's an argument for not rebasing in GH but on the actual commit to retrigger CI... but it is very convenient.


Bump version

#1071  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dongreenberg and the rest of your teammates on  Graphite


Hold onto rust-url Url in iron Url

Rather than doing so many conversions back and forth.
This builds on #452 and contains 3 commits more than that PR.
Commits eea2bbf and bef95ae are fairly straightforward. eea2bbf gets rid of the extra rust-url parse call needed since rust-url 1.0 to get back to a rust-url Url. bef95ae uses rust-url's display implementation on the stored rust-url Url for the iron Url's display trait-- all the tests still pass.
3a9b322 may be a step too far-- I'm happy to remove it if so. It changes the public API of iron Url to have methods instead of the struct fields, and those methods mostly just delegate to the rust-url Url. I'm not sure if this is what you had in mind or not!

Just gave this a more thorough read, and it looks fantastic! Thank you very much for making this change, it's something I've wanted to do for a long time.
There's only one major thing I think we should change: many of the methods return owned types (String, Vec<String>, etc.) by internally calling cloning methods when we could just return the borrowed variant. Wherever possible, I would like to avoid adding any allocations by just returning the borrowed type instead.
I think the only remaining refactor would be substituting String for a proper error type, but that can be left for another PR.

@reem awesome, done! That makes the implementations way nicer-- fewer .to_owned()s all over the place :)

Any progress on this? I am getting this warning when I try to build iron with latest cargo (5a26b65):
$ cargo build
warning: TOML file found which contains invalid syntax and will soon not parse
at `/home/onur/.cargo/registry/src/github.com-1ecc6299db9ec823/url-0.5.9/Cargo.toml`.

The TOML spec requires newlines after table definitions (e.g. `[a] b = 1` is
invalid), but this file has a table header which does not have a newline after
it. A newline needs to be added and this warning will soon become a hard error
in the future.

And I can't already build iron 0.3 with cratesfyi. We really need url 1 support soon I guess.

I'm going to spend sometime this weekend working on trying to update iron to work with hyper master, I'm basing my changes on this PR now because I believe this is just waiting to merged @reem

YAAAYY!!!! 🎆🎆🎆🎆🎆🎆 Thank you @reem !!! ❤ ❤ ❤ ❤


Making some minor fixes around basic auth

This PR tweaks some things about the basic auth implementation.

Modifies the login and register forms to look more like the rest of the application
Ensures that we don't advertise /login or /register API endpoints if we don't have dispatch-auth-provider-basic enabled.
Adds missing database migration for DispatchUser

Other considerations, should we add another config value to enable/disable registration? Given the nature of the app, I wouldn't expect most folks to allow registration without approval.
cc @stefanm8

Hi, looks really good, gg!
Disabling registration does make sense, as most probably it will be closed when this runs in production. This can be achieved with minimal effort on the backend side.


Added a How-To guide for qasm2

Summary
Documentation of use qasm to export and import qasm, taking as reference https://github.com/Qiskit/qiskit-terra/issues/8574
Details and comments
Using only qasm2  methods
consider the method qiskit.CircuitQuantum.qasm to export, because at this point qiskit.qasm only has load and loads method.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
23 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 85.895%

Files with Coverage Reduction
New Missed Lines
%

qiskit/extensions/quantum_initializer/squ.py
2
80.0%

crates/qasm2/src/lex.rs
9
90.63%

crates/qasm2/src/parse.rs
12
97.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
73065

Relevant Lines:
85063

💛  - Coveralls


S2 Tag non-color tokens

Description
New non-color tokens for S2 tag component added to both desktop and mobile layout.component sets. They include:

tag-minimum-width-multiplier

tag-maximum-width-multiplier

tag-label-to-clear-icon-small

tag-label-to-clear-icon-medium

tag-label-to-clear-icon-large

tag-edge-to-clear-icon-small

tag-edge-to-clear-icon-medium

tag-edge-to-clear-icon-large

Motivation and context

New values for tag component for S2. See Jira ticket.
Related issue

Types of changes

 [ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [X] Minor (add a new token, changing a value; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)
Checklist:

 [X] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [X] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.tag-minimum-width-multiplier
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.tag-maximum-width-multiplier
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-large

SPECTRUM SYNC SUMMARY
NEW TOKENS: (30) switch-handle-size-small/desktop, switch-handle-selected-size-small/desktop, switch-handle-selected-size-medium/desktop, switch-handle-selected-size-large/desktop, switch-handle-selected-size-extra-large/desktop, switch-handle-size-medium/desktop, switch-handle-size-large/desktop, switch-handle-size-extra-large/desktop, switch-handle-size-small/mobile, switch-handle-selected-size-small/mobile, switch-handle-selected-size-medium/mobile, switch-handle-selected-size-large/mobile, switch-handle-selected-size-extra-large/mobile, switch-handle-size-medium/mobile, switch-handle-size-large/mobile, switch-handle-size-extra-large/mobile, tag-minimum-width-multiplier, tag-maximum-width-multiplier, tag-label-to-clear-icon-small/desktop, tag-label-to-clear-icon-small/mobile, tag-label-to-clear-icon-medium/desktop, tag-label-to-clear-icon-medium/mobile, tag-label-to-clear-icon-large/desktop, tag-label-clear-icon-large/mobile, tag-edge-to-clear-icon-small/desktop, tag-edge-to-clear-icon-small/mobile, tag-edge-to-clear-icon-medium/desktop, tag-edge-to-clear-icon-medium/mobile, tag-edge-to-clear-icon-large/desktop, tag-edge-to-clear-icon-large/mobile
CHANGED VALUES: (14) switch-control-height-extra-large/desktop, switch-control-height-large/desktop, switch-control-height-medium/desktop, switch-control-height-small/desktop, switch-control-width-extra-large/desktop, switch-control-width-large/desktop, switch-control-width-small/desktop, switch-control-height-extra-large/mobile, switch-control-height-large/mobile, switch-control-height-medium/mobile, switch-control-height-small/mobile, switch-control-width-large/mobile, switch-control-width-medium/mobile, switch-control-width-small/mobile impacting 8 tokens

TEST COMPLETE

SYNCING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.tag-minimum-width-multiplier
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component.tag-maximum-width-multiplier
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-label-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-label-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-medium
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.tag-edge-to-clear-icon-large
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.tag-edge-to-clear-icon-large

SPECTRUM SYNC SUMMARY
NEW TOKENS: (14) tag-minimum-width-multiplier, tag-maximum-width-multiplier, tag-label-to-clear-icon-small/desktop, tag-label-to-clear-icon-small/mobile, tag-label-to-clear-icon-medium/desktop, tag-label-to-clear-icon-medium/mobile, tag-label-to-clear-icon-large/desktop, tag-label-clear-icon-large/mobile, tag-edge-to-clear-icon-small/desktop, tag-edge-to-clear-icon-small/mobile, tag-edge-to-clear-icon-medium/desktop, tag-edge-to-clear-icon-medium/mobile, tag-edge-to-clear-icon-large/desktop, tag-edge-to-clear-icon-large/mobile

WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/spectrum2/layout.component/desktop.json
WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/spectrum2/layout.component/mobile.json
WROTE: /spectrum-tokens/packages/tokens/src/layout-component.json
SYNC COMPLETE
Spectrum Tokens Pull Request
Tokens Studio Pull Request


[DeadlineQoSExample] Fail to compile because Asio not found

DeadlineQoSExample includes asio.hpp but doesn't find_package or find_eprosima_thirdparty asio it so it fails to compile on Windows:
fatal error C1083: Cannot open include file: 'asio.hpp': No such file or directory

Does the example fail when it is compiled inside FastRTPS compilation or separately?

It fails to compile when thirdparty packages are installed externally and by running:
cmake -DCOMPILE_EXAMPLES=ON ..
make

Note: if I clone Fast-RTPS recursively, it doesn't fail because it can find asio in the submodule

Can you try again with d20a5ca5d94a21b7ed9621126b67807ba58fa459? I think it should be enough. Thanks.

Thanks for the update, I tried the current state of master (including https://github.com/eProsima/Fast-RTPS/commit/d20a5ca5d94a21b7ed9621126b67807ba58fa459).
WIth this change the example now fails at cmake configure time rather than build time:
    25>CustomBuild:
         -- The CXX compiler identification is MSVC 19.0.24215.1
         -- Check for working C compiler using: Visual Studio 14 2015 Win64
         -- Check for working C compiler using: Visual Studio 14 2015 Win64 -- works
         -- Detecting C compiler ABI info
         -- Detecting C compiler ABI info - done
         -- Check for working CXX compiler using: Visual Studio 14 2015 Win64
         -- Check for working CXX compiler using: Visual Studio 14 2015 Win64 -- works
         -- Detecting CXX compiler ABI info
         -- Detecting CXX compiler ABI info - done
         -- Detecting CXX compile features
         -- Detecting CXX compile features - done
         -- Configuring DeadlineQoS example...
    25>CUSTOMBUILD : CMake error : The following variables are used in this project, but they are set to NOTFOUND. [C:\
       dev\sros2\build_isolated\fastrtps\examples\DeadlineQoSExample.vcxproj]
         Please set them or make sure they are set and tested correctly in the CMake files:
         ASIO_INCLUDE_DIR
            used as include directory in directory C:/dev/sros2/src/eProsima/Fast-RTPS/examples/C++/DeadlineQoSExample
            used as include directory in directory C:/dev/sros2/src/eProsima/Fast-RTPS/examples/C++/DeadlineQoSExample
         -- Configuring incomplete, errors occurred!
         See also "C:/dev/sros2/build_isolated/fastrtps/examples/C++/DeadlineQoSExample/CMakeFiles/CMakeOutput.log".

    25>Done Building Project "C:\dev\sros2\build_isolated\fastrtps\examples\DeadlineQoSExample.vcxproj" (default target
       s) -- FAILED.

Ok, I have the same error if I remove Asio from my path. Anyway, we have modified the CMakeLists again in 6f1cffe53499f27d2e6a5f2d924db928f85f4cd6, I hope it gets fixed now. Thanks.

@mikaelarguedas Did last changes solve the issue?

Last time I tried (June 2nd) it still failed to compile, I didn't test it
since then so maybe some of the recent changes fixed it. I'll try again
today and report here
On Wed, Jun 28, 2017 at 7:56 AM, Ricardo González<EMAIL_ADDRESS>wrote:

@mikaelarguedas https://github.com/mikaelarguedas Did last changes
solve the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eProsima/Fast-RTPS/issues/108#issuecomment-311685655,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVh8ATQaIhtxG5OzN0FrFbLpM4ReZ5vks5sImmxgaJpZM4NhcmU
.

I just tested this in a fresh VM and it built fine. Thanks! closing this


Generated preconditions not correctly formatted

What is the smallest, simplest way to reproduce the problem?
Look at the locally generated RedundantCallRecipe.java for https://github.com/openrewrite/rewrite-migrate-java/blob/c223f325b13c1deb96eb96d6a6c9ff7570e5563c/src/main/java/org/openrewrite/java/migrate/lang/StringRules.java#L29-L33.
What did you see instead?

It contains this precondition:
            return Preconditions.check(
                    Preconditions.or(
                        Preconditions.and(
                        new UsesMethod<>("java.lang.String substring(..)"),
                        new UsesMethod<>("java.lang.String length(..)")
                    ),
                        new UsesMethod<>("java.lang.String substring(..)"),
                        new UsesMethod<>("java.lang.String toString(..)")
                    ),
                    javaVisitor
            );

The indentation inside the nested "AND" is wrong. This doesn't break the rewrite functionality, but it made me look for an error in the precondition generation which is not even there (I read this as two times the same top level condition and looked for why the duplicate is not recognized). :/
Are you interested in contributing a fix to OpenRewrite?

Maybe.

Thanks for the report! Can see how this is frustrating when debugging the generated recipe. We seem to already pass in an indentation argument when we join preconditions, but it'll need a closer look to know exactly where we're missing a level of indentation.
https://github.com/openrewrite/rewrite-templating/blob/6fef1873bb63f3508a53cbc623dc58e1a49bd4c3/src/main/java/org/openrewrite/java/template/processor/RefasterTemplateProcessor.java#L545-L609

Just from a short look I would think that line 608 is wrong (specifically the String.join(...) part). For nested calls the elements of the preconditions collection can be multiline strings. Therefore each of those elements would have to be split to lines, indented and joined again, not just the collection as a whole. Right now only the first line of a multiline string would be indented.

Thanks yes looks like it; had a brief look at changing the indentation, but no immediate fix from a quick attempt yet.

This has been revised in #120


Bump arrow version to 6.0.0

conda-forge is bumping the supported range of Arrow versions to be 6-9 and dropping support for versions below 6 (xref https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/3203), so we need to bump our minimum pyarrow testing dependency to 6.
cc @galipremsagar

Looks like failures are Windows specific - looking into them now

The failures stemmed from an issue with MLFlow and older versions of the protobuf conda package that I opened in https://github.com/mlflow/mlflow/issues/6072; not really sure what can be done there but bumping from Arrow 6.0.0 -> 6.0.1 bumps our protobuf version to be new enough where it isn't a problem anymore.


Wjh/translations docs

pwa/ was renamed to template-retail-react-app, but I assume that the document is for users of generated projects, who won't even know about that directory, so I opted for just removing it.
Markdownlint autofixes.
Noticed a typo in the PR template when typing this.

Description

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

We set the en-US.json as the target file for defaultMessages, saying in their own JSON is not correct imo
 "extract-default-translations": "formatjs extract 'app/**/*.{js,jsx}' --out-file app/translations/en-US.json --id-interpolation-pattern [sha512:contenthash:base64:6]",

@alexvuong we did mention en-US.json in the 1st paragraph, and I think it makes sense in this case because the paragraph was talking about the current state of the files in the translations folder.
Then in one of the paragraphs below that, we were describing the purpose of the npm scripts. In that case, IMO we should be talking about things in general. It is possible that other developers replace the en-US in the npm scripts. So the purpose of the script is not to extract into en-US.json, but to whichever locale that the hardcoded strings are written in.


'slack_oauth_missing_state' error during OAuth Flow

Description
slack_oauth_missing_state error is being thrown. This does happen regularly but not all the time.
When I provide my redirect URL with /slack/oauth_redirect, sometimes it successfully redirects with the modal saying Open Slack. However, many times, it is giving me that slack_oauth_missing_state. I understand because when I checked the URL after pressing Allow button for the permission scope, state query string is empty.. But when it was working fine, state was there. I am not sure why it happens and it happens not sometimes...
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[ x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ x] I've read and agree to the Code of Conduct.
[x ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

I think found it... it's behaving really weird..
When I use the Add to Slack button in Manage Distribution page, it is throwing that slack_oauth_missing_state with the redirect url I provided (/slack/oauth_redirect).
However, when I just typed it in my browser https://mydomain.com/slack/install, it is not throwing slack_oauth_missing_state. My redirect URL works perfectly.

Hi @esphoenixc, thanks for asking the question.
Yes, as you found out, starting the OAuth flow at /slack/install is the recommended way. If you have a certain reason to disable the state parameter verification, you can installerOptions.legacyStateVerification: true when initializing your app. Refer to https://github.com/slackapi/bolt-js/releases/tag/%40slack%2Fbolt%403.11.0 for more details.
Let me close this issue now but please feel free to write in if you have any follow-up questions.

Thank you for the reply!
I found another weird behavior. The thing is like I said above and you said OAuth flow at /slack/install is the recommended way and I get that so I did that but after installing with the /slack/install flow, I used the Postman(thunder client) to send the post request to understand how to grab incoming webhook URLs programmatically. and I get an invalid code error
POST: https://slack.com/api/oauth.v2.access?code={AUTHORIZATION_CODE}&client_id={CLEINT_ID}&client_secret={CLIENT_SECRET}
I manually grabbed the Authorization code from the url itself and pasted it in and sent the post request but got an invaild code error but when I used the Add To Slack button in Manage Distribution tab, the button that is giving me "slack_oauth_missing_state" error since it is not the recommended OAuth flow (/slack/install), I get 200 OK with the incoming webhook url..
I don't know if I explained it sufficiently

Hi @esphoenixc, thanks for asking the question.
Yes, as you found out, starting the OAuth flow at /slack/install is the recommended way. If you have a certain reason to disable the state parameter verification, you can installerOptions.legacyStateVerification: true when initializing your app. Refer to https://github.com/slackapi/bolt-js/releases/tag/%40slack%2Fbolt%403.11.0 for more details.
Let me close this issue now but please feel free to write in if you have any follow-up questions.

Hi, when I disabled the state parameter verification installerOptions.legacyStateVerification: false, https://mydomian.com/slack/install is not working, throwing an error "An unhandled error occurred while Bolt processed a request to the installation path (StateStore is not properly configured)" I also did   installerOptions: {     stateVerification: false,   }, so did stateVerification change to legacyStateVerification? Is this correct? And, the button in Manage Distribution section and the recommended OAuth flow of https://mydomain.com/slack/install can't exist at the same time it seems without throwing an error while the other one is okay? That's what I've understood so far. I can have only one working not both.
Thank you again for your help

installerOptions.legacyStateVerification: false

This flag needs to be set to true if you would like to use the legacy verification. stateVerification: false completely disables the verification but we don't recommend doing so.

If I want to build a landing page for my app, how do I give users a button to install that doesn't require them clicking install twice? (1 in my page and 1 in /slack/install?)

Running into the same problem as @brunolm, any way to avoid having the users to click on "add to slack" twice? The only I have managed to do this is via setting directInstall: true and legacyStateVerification: true, but if legacyStateVerification: true is not recommended, what is the alternate way redirect users safely with a directInstall, @seratch ?


Add a before-dealloc lifecycle method (with args)

It appears that there is no safe way to support this feature.


Configure Prettier, ESLint and Formatting Tools

Looking forward for reporting a security issue:
Please report security issues by following our security policy: https://contribute.freecodecamp.org/#/security
Describe the bug
Whenever I hit the "Format with Prettier" shortcut in Visual Studio Code; it seems like the entire file is set as changed rather than just the new lines of code.
To Reproduce
Steps to reproduce the behavior:

Open up the repository in Visual Studio Code
Click on the american-british-translator app folder
Open the server file
Format the document with Prettier
See error

Expected behavior
Only the lines I added should have been modified via Prettier.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: FireFox
Version: 119.0

Additional context
I would rather not add the endpoint for this app before this issue is resolved.

Thanks for reporting. The repo is missing the tooling like lint-staged and a format script like we have on the other repositories.
Would you be interested in adding such a config? If you need inspiration, I think the main repo is a good place.


Feature Request: enable jest-cli to unset collectCoverageFrom config to undefined

My team wants whole codebase coverage reports, so we have collectCoverageFrom set in our package.json. When developing, I want the default jest behavior of collecting coverage from files that are tested by spec files. I cannot figure out how to override and unset the package.json:config with a command line flag.
Following: https://github.com/facebook/jest/issues/1932, I've tried setting a new value --collectCoverageFrom ["client/__tests__/**/*.{js,jsx}"], but that behaves quite differently than the default.
these also fail:
--collectCoverage '["undefined"]'
--collectCoverage '[undefined]'
--collectCoverage 'undefined'
Also, the content from this commit: https://github.com/facebook/jest/pull/2010/files has been dropped from the site: http://facebook.github.io/jest/docs/cli.html#content

At the moment I'm deleting lines from the package.json to generate my reports and then adding them back in before committing.

--collectCoverageFrom now overrides the one in package.json :)


Implement simpler hash function

Moved helper functions from the predicate into their own utils library and added a new helper function tx_script_bytecode_hash to easily get an unpadded script hash.
Note: there is a future issue to tweak this new function to use GTF in the future

If there isn't an issue in the Sway repo to warn on unused imports then please file one.

If there isn't an issue in the Sway repo to warn on unused imports then please file one.
Someone already made an issue for it: https://github.com/FuelLabs/sway/issues/1298

New versions of forc and fuels-rs are around the corner. Would it be better to wait a few days and do this properly with the new functions instead of hard-coding things that will have to get changed later?

Yeah, I think I'm gonna scrap this PR since I've started working with using the new GTF refactor. Merging this minor issue may not be worth the effort

Closing to prioritize new sway and sdk releases


Kibana 4.0.0 Release expects quoted string for elasticsearch value

Technically, this is a bug in Kibana 4.0.0 -- but its hopefully quicker and easier to fix in this cookbook.
It seems with the 4.0.0 release, they expect elasticsearch value to be quoted. I have attempted to work around this by setting my attribute to have escaped quotes within the value, but Ruby's YAML generator renders the value as "'http://mycluster:9200'" instead of 'http://mycluster:9200'

will try to fix it on next week.

There are few updates in configuration file.
bundledPluginIds renamed to bundled_plugin_ids,
elasticsearch renamed to elasticsearch_url.
For quick fix you can override these values in wrapper cookbook. Will create hotfix for that and test

Fixed in 8a1f932e2151db4e20fcfdca802356aba3dbe073
Tagged as v0.2.0, published to supermarket


feat: connect lobby to backend

Screens

Changes

load lobby information from backend
clean up loading screens
link to each song in Spotify

@thilan-tran what we could do is just take the repo you have and copy the files directly over


Use load path to normalize vendored gem filenames

Stack trace filenames are currently normalized based on the project root if they're under it, or the load path otherwise. This works for gems when they're installed globally, since they'll be outside the project root and the load path will be used. If the gems are installed into vendor/ under the project root however, the full relative path will be used - which includes the gem version, e.g:
vendor/bundle/ruby/2.1.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb

This means that if you update a gem, any backtraces that pass through it will change and Sentry will see them as new events. Ideally we would always normalize based on the load path for gems, but use the project root for application code.
Instead of introducing a special case for load paths under vendor/, I've used the in_app attribute to decide whether to ignore the load path.
With this change, there are now three cases:

When a path is under the project root and matches APP_DIRS_PATTERN, normalize it based on the project root.

When a path is under the project root but doesn't match the pattern, first try to normalize it based on the load path, but fall back to using the project root.

When a path is outside the project root, normalize it based on the load path.

Awesome. Nice job cleaning up that conditional too!


Make manpages in a container when creating deb/rpm

Yes, I noticed this this morning, but didnt test it was actually an issue.
LGTM.

LGTM

Just found out that this breaks make deb on ARM. 😁  I thought that hack/make/build-deb is already running inside a container and this calls make manpages. This step pulls golang:1.6.3-alpine from Docker Hub which is amd64 only(?) right now.

@StefanScherer can you open an issue for that? Do we have a workaround for that (other base image?)

@theJeztah Will do and also have a look how to fix it. What was wrong with man/generate.sh? Haven't followed the discussion.

@StefanScherer see https://github.com/docker/docker/pull/23825


The Enchanted Key (miniquest) - Steel key ring check is broken

The Item requirements list that displays the 1 x Enchanted Key is not properly checking the Steel key ring for possession. It's only checking if the key is in your bank or inventory. Usually the key is displayed as "yellow text" with a tool tip when it is in the Steel key ring. It would be nice if this was updated to check.
Enchanted key on the ring:

Enchanted key in inventory:

After applying the Steel key ring 'check', the first step should be "Remove the enchanted key from your Steel key ring."
It is not possible to operate the key while on the ring.

For this I'll need to see what the chatbox says when adding and removing the enchanted key. Hopefully I'll get an account eventually which can try it out.


Spending too much time when detecting exit opportunity

Hi,
first of all, I would like to say I really like the application, thank you for sharing it.
I have been going through the code and I'm wondering why we are getting the values of volumeLong and volumeShort by querying exchanges? Is there any reason? That querying introduces additional 100-300ms delay before executing the order(depending on exchange response time), increasing the risk of price slippage.
Here is the code I'm talking about: main.cpp link
When application goes into the market, why don't we save volumeLong and volumeShort to the Result and then use that value?

volumeLong and volumeShort are used to make sure there is enough liquidity on the exchanges before trading (getLimitPrice()  function). The limit price is adjusted to make sure we get an immediate execution on both exchanges. If the adjustments is too far from the original price then we don't trade the opportunity.

Yes @butor, I understand that part.
But we get values of volumeLong / volumeShort by querying exchange, instead of storing those values after executing entry trade, why?

Because these values will change between the entry trade and the exit trade. You need to query the order book just before sending orders, otherwise you deal with outdated values. Does that make sense?


Version 1.3.1 - Item Dropships go through floor in random spots on all maps.

On the latest version of LE, I can assume that the tweak to improve item dropships on custom maps broke the placements on official ones. When buying items on any map including the company the item dropship would go through the ground, leaving the items inaccessible.
While I don't have logs, I am pretty confident LE was the culprit as degrading the mod to version 1.2.16 fixed the issue altogether.

On the latest version of LE, I can assume that the tweak to improve item dropships on custom maps broke the placements on official ones. When buying items on any map including the company the item dropship would go through the ground, leaving the items inaccessible.
While I don't have logs, I am pretty confident LE was the culprit as degrading the mod to version 1.2.16 fixed the issue altogether.

Can you show me a screenshot please ?
This happen only in vanilla maps ?

I was just coming here to report this! This only occurs after visiting the Christmas Village map. I just finished some time testing to confirm this and that it was not due to a conflict in other mods. I tested this morning with and without other mods.
It appears after visiting the Christmas Village, a secondary dropship is spawned up above the map. Thanks to the Christmas lights it is currently adorned with, you can actually observe it from the ground, weather permitting. After visiting the Christmas Village, the second dropship will be used to deliver items, which always lands in an incorrect position.
One screenshot with other mods, and one without. The dropships are more visible with the HD mod installed, but I put arrows on both images.

i also have this bug. i'm not sure if it's because i have other moon mods or the issue is in the code itself. i have a few screen shots of multiple drop pods in the sky and a few of them land underground or floating in the air.
Orion mod by sfDesat moon:
multiple drop pods, the drop pod landed underground.

Peaches_Castle mod by TeamBridget moon:
multiple drop pods, the drop pod landed in the air.

Ducks_Moons mod by FireNoobsta moon:

Aquatis mod by sfDesat moon:

Yes i finally found the issue on my side too
Thanks @taarna23 and @HamedAlmanthari for contributions
The Item Drop Ship wasn't unloaded after leaved modded moons
I fixed it in 1.3.2 and about to release 1.3.3 with more fixes


Move and better document the Guest class

As agreed on the hacking meeting last week I've improved documentation of the essential Guest class methods and moved it from base to steps.provision. @pvalena, @thrix, @lukaszachy, please, review the method descriptions if they are more clear now. Thanks.

@pvalena, thanks for the review and comments. I believe all should now be addressed. Please, have another look. Thanks.

It looks good! Apart from that one you've probably missed.
Thanks!

Thanks for the review.


Fix Merge for ExtraLines in BarChart

Feature Request #975
It's almost 2 years and this is an important feature for those who use bar chart.

Commented in #975.


Fix controller mappings for OpenVR (and friends)

Overview
This PR:

Fixes the controller mapping type / axis mismatch introduced by #5874 for WMR, Vive, and the generic OpenVR mappings
Introduces a controller mapping profile updater to make serializing these changes into the profiles (and any custom profiles) easier without losing action mappings
Renames mixedRealityControllerMappingProfiles to mixedRealityControllerMappings, which is what it actually is
Reserializes the two input actions profiles to

Remove several instances of stale controller types (all were namespace changes of simulated hands)
Add some missing mappings for the generic OpenVR controller for one of the checked-in profiles
Update all instances of axis type, name, or keycode changing
Account for the mixedRealityControllerMappingProfiles rename

Changes

Fixes: #6164

Verification
Test WMR on OpenVR
Test Vive on OpenVR

/azp run


Feature/calendly integration

Description
Added calendly integration to handle scheduling appointments with groomers
Type

[ ] This is a bugfix.
[x] This is a new feature.
[x] This is part of a feature.

Organization

[x] Have you linked this pull request to a Trello card?
[ ] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[ ] Is this a work in progress?
[x] Is this ready to be reviewed?
[x] Have you added two reviewers to this pull request?

 Give cusomers the option to schedule appointments with groomers

 Give cusomers the option to schedule appointments with groomers


Fix attack optimization abstraction

What does this PR do?
This PR moves the optimizer from the Adversary and into the Perturber. Because the Perturber is also a Callback, this means it can take care of optimizing its perturbation.
The old abstraction use per-parameter options, or parameter groups, to accomplish this. However, it would also be nice to apply different optimizers (e.g., SGD and Adam) to different perturbations. This PR enables each perturbation to have its own optimizer, which is fine because https://discuss.pytorch.org/t/is-using-separate-optimizers-equivalent-to-specifying-different-parameter-groups-for-the-same-optimizer/95075.
In the process of doing this I also fixed some type hints.
Type of change
Please check all relevant options.

[ ] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[x] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

[ ] Test A
[ ] Test B

Before submitting

[ ] The title is self-explanatory and the description concisely explains the PR
[ ] My PR does only one thing, instead of bundling different changes together
[ ] I list all the breaking changes introduced by this pull request
[ ] I have commented my code
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have run pre-commit hooks with pre-commit run -a command without errors

Did you have fun?
Make sure you had fun coding 🙃

I might abandon this in favor of treating adversaries as just another LightningModule.

Closing this in favor of #103.


Add CPUUsage internal device class

Here's an implementation using the psutil module:
from gpiozero import InternalDevice
from psutil import cpu_percent

class CPUUsage(InternalDevice):
    def __init__(self, min_usage=0, max_usage=100):
        self.min_usage = min_usage
        self.max_usage = max_usage

    @property
    def usage(self):
        return cpu_percent()

    @property
    def value(self):
        usage_range = self.max_usage - self.min_usage
        return (self.usage - self.min_usage) / usage_range

Usage:
from gpiozero import LEDBarGraph, CPUUsage  # let's pretend CPUUsage is available

leds = LEDBarGraph(17, 27, 22, pwm=True)
cpu = CPUUsage()

leds.source_delay = 1  # it goes crazy if you don't slow it down
leds.source = cpu.values

I don't want to introduce a dependency on psutil so perhaps we could just include a borrowed implementation (like frozenset in #348). It's BSD licensed, so is that ok if we include their licence?
@waveform80 do you have any suggestions for the source delay issue?

Perhaps people would get confused between the LoadAverage class (see #532 and/or #614 ) and this CPUUsage class? :wink:
Or perhaps there could be a single class that could give you all the different CPU-related infos at once? *shrug*


Add libdeflate_zlib bindings

libdeflate exposes both libdeflate_gzip_compress and libdeflate_zlib_compress, but you only currently wrap the gzip one. Any plans to also wrap the zlib one?
Is this as simple as replacing libdeflate_gzip_compress with libdeflate_zlib_compress? Would seem straightforward (if verbose) to copy the bindings again for zlib?

For compression, yes, it would be pretty trivial to just use libdeflate's zlib API in the same way the gzip API is currently used. But for decompression, you need to allocate a buffer for libdeflate to write into. Gzip has the benefit of including the original decompressed size as a check at the end of an archive, so I can know exactly how much memory to allocate. For other decompression APIs, you would need to guess and potentially loop, or expose an optional buffer_size to the Python call (or both). It was just much simpler to only do gzip to start.
I'm not opposed to expanding the library to include support for all of libdeflate's APIs, but don't really have the time or inclination to do the work myself. So long as the Python APIs can be dropped in for gzip/zlib .compress(data) and .decompress(data) with no options, I'll accept PRs.

Thanks, that's great to know and makes a lot of sense. I don't know C very well, so I doubt I'll take a stab in the near future.

I got a PR for adding raw DEFLATE support, so I went ahead and added zlib support too based on it. Better late than never?


Publication to Maven Central

It has been released
<dependency>
    <groupId>io.github.pepperkit</groupId>
    <artifactId>retry</artifactId>
    <version>1.0.0</version>
</dependency>


Request for pretrained models

Can you kindly release pretrained models?

I am also interested in pre-trained models. It would be very kind and helpful if you could provide some.


Zaowang/liftr nginx/adding 2 24 09 01 preview

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Note: Just duplicating and publishing changes from: https://github.com/Azure/azure-rest-api-specs-pr/pull/19071

Breaking changes previously reviewed and approved in https://github.com/Azure/azure-rest-api-specs-pr/pull/19071

The CI lint diff check contradicts to our
previous conversation in the private PR. We've already implemented our code that way and we hope to publish the API in consistence with the private API repo. Please suppress it as we're hoping to get it merged soon. Thanks!

Hi,
Please verify my understanding. From what I see, the API change in the private repo follows your suggestion on separating request/response objects given secret data is passed from requests but not returned by responses (remove the secretText field in response)
https://github.com/Azure/azure-rest-api-specs-pr/pull/19071#discussion_r1744234166
The PR was approved in private repo several weeks ago. We've rollout the ARM manifest and have the API live and tested in production as well. The new portal blade that uses this API is also in preview.
The nature of this API is asymmetric in terms of request/response data given secret is write-only and the returned hash is read-only. So whether modeling request/response via the same entity or separate, either one works fine from user perspective as long as the annotation clarifies it. From this perspective, the lintdiff warning seems to more of an artificial side effect.
Revisiting and changing the API at this point will require changing the RP implementation, redeploying RP, changing the portal implementation alongside with extra time for API review in both private/public repos. And hence the estimated 2 weeks delay. We plan to demonstrate the feature in Ignite.
I'm wondering if we can expedite the public repo merge through an exception?

Hi,
Please verify my understanding. From what I see, the API change in the private repo follows your suggestion on separating request/response objects given secret data is passed from requests but not returned by responses (remove the secretText field in response) Azure/azure-rest-api-specs-pr#19071 (comment)
The PR was approved in private repo several weeks ago. We've rollout the ARM manifest and have the API live and tested in production as well. The new portal blade that uses this API is also in preview.
The nature of this API is asymmetric in terms of request/response data given secret is write-only and the returned hash is read-only. So whether modeling request/response via the same entity or separate, either one works fine from user perspective as long as the annotation clarifies it. From this perspective, the lintdiff warning seems to more of an artificial side effect.
Revisiting and changing the API at this point will require changing the RP implementation, redeploying RP, changing the portal implementation alongside with extra time for API review in both private/public repos. And hence the estimated 2 weeks delay. We plan to demonstrate the feature in Ignite.
I'm wondering if we can expedite the public repo merge through an exception?

Going by the previous private PR's approval. Could you add a suppression for this issues in readme?

@ramoka178 thanks for taking a look! I don't know how to do it, could you share a link / doc on how to do this?

@ramoka178 thanks for taking a look! I don't know how to do it, could you share a link / doc on how to do this?

@zaowang-ms  You could check any other swagger's read me that has suppressions.
e.g. ( no preference, just searched suppressions on the repo ) https://github.com/Azure/azure-rest-api-specs/blob/362baa4049e19f5a01c3d18760e17f5f22583276/specification/oep/resource-manager/readme.md?plain=1#L51

@ramoka178 added the suppression, please review. Thanks a lot!


Windows PC Health Check showing upgrade but not applicable

Brief description of your issue
winget upgrade shows:
Windows PC Health Check Microsoft.WindowsPCHealthCheck 3.2.2110.14001 3.3.2110.22002 winget

The upgrade is on a different build version.
It displays an upgrade available but it won't upgrade it.
C:\> winget upgrade Microsoft.WindowsPCHealthCHeck
No applicable update found.
C:\>

Steps to reproduce
having PC Health Check installed version  3.2.2110.14001
upgrading to 3.3.2110.22002
won't upgrade it.
Notice that is just a minor version build.
Expected behavior
Upgrade to the reported version.
Or it should not be shown as upgrade available.
Actual behavior
it won't install it, trying running winget will return with this message:
No applicable update found.
Environment
Windows Package Manager (Preview) v1.3.692-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1586
Package: Microsoft.DesktopAppInstaller v1.18.692.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Can you post the output of winget list Microsoft.WindowsPCHealthCheck?
Also, if you can provide the log files from winget upgrade Microsoft.WindowsPCHealthCheck --verbose-logs it would be appreciated

This is actually more related to https://github.com/microsoft/winget-cli/issues/1967 unless you're thinking of the InstallerType override
I believe this is a different kind of installation by Windows or a OEM (So its similar to our WebView2 issue)

Can you post the output of winget list Microsoft.WindowsPCHealthCheck? Also, if you can provide the log files from winget upgrade Microsoft.WindowsPCHealthCheck --verbose-logs it would be appreciated

PS C:\> winget list Microsoft.WindowsPCHealthCheck
Name                    Id                             Version        Source
-----------------------------------------------------------------------------
Windows PC Health Check Microsoft.WindowsPCHealthCheck 3.3.2110.22002 winget

PS C:\> winget upgrade Microsoft.WindowsPCHealthCheck --verbose-logs
No applicable update found.

I am stripping out some information from the logs ([SQL]) .
2022-03-31 08:56:14.909 [CORE] WinGet, version [1.3.692-preview], activity [{8505E5F7-8C54-4CB3-94B5-55DB970089B3}]
2022-03-31 08:56:14.909 [CORE] OS: Windows.Desktop v10.0.19044.1586
2022-03-31 08:56:14.909 [CORE] Command line Args: "C:[...]\Local\Microsoft\WindowsApps\winget.exe" upgrade Microsoft.WindowsPCHealthCheck --verbose-logs
2022-03-31 08:56:14.909 [CORE] Package: Microsoft.DesktopAppInstaller v1.18.692.0
2022-03-31 08:56:14.909 [CORE] IsCOMCall:0; Caller: winget-cli
2022-03-31 08:56:14.922 [CLI ] WinGet invoked with arguments: 'upgrade' 'Microsoft.WindowsPCHealthCheck' '--verbose-logs'
2022-03-31 08:56:14.922 [CLI ] Found subcommand: upgrade
2022-03-31 08:56:14.922 [CLI ] Leaf command to execute: root:upgrade
2022-03-31 08:56:14.924 [CORE] Setting action: Get, Type: Secure, Name: admin_settings
2022-03-31 08:56:14.925 [CORE] Admin settings was not found
2022-03-31 08:56:14.925 [CLI ] Executing command: upgrade
2022-03-31 08:56:14.925 [CORE] Setting action: Get, Type: Secure, Name: user_sources
2022-03-31 08:56:14.925 [CORE] Setting action: Get, Type: Standard, Name: sources_metadata
2022-03-31 08:56:14.925 [YAML] Detected UTF-8
2022-03-31 08:56:14.925 [REPO] GetCurrentSourceRefs: Source named 'microsoft.builtin.desktop.frameworks' from origin Default is hidden and is dropped.
2022-03-31 08:56:14.925 [REPO] Default source requested, multiple sources available, adding all to source references.
2022-03-31 08:56:14.925 [REPO] Adding to source references msstore
2022-03-31 08:56:14.925 [REPO] Adding to source references winget
2022-03-31 08:56:14.925 [CORE] Setting action: Get, Type: Secure, Name: user_sources
2022-03-31 08:56:14.925 [CORE] Setting action: Get, Type: Standard, Name: sources_metadata
2022-03-31 08:56:14.925 [YAML] Detected UTF-8
2022-03-31 08:56:14.926 [REPO] Multiple sources available, creating aggregated source.
2022-03-31 08:56:14.926 [REPO] Adding to aggregated source: msstore
2022-03-31 08:56:14.926 [REPO] Custom header not found.
2022-03-31 08:56:14.926 [REPO] Sending http GET request to: https://storeedgefd.dsx.mp.microsoft.com/v9.0/information
2022-03-31 08:56:14.926 [REPO] Http GET request details:
GET / HTTP/1.1

Content-Type: application/json

User-Agent: winget-cli WindowsPackageManager/1.3.692-preview DesktopAppInstaller/Microsoft.DesktopAppInstaller v1.18.692.0

2022-03-31 08:56:15.084 [REPO] Response status: 200
2022-03-31 08:56:15.084 [REPO] Response details:
HTTP/1.1 200 OK

Cache-Control: max-age=0, no-cache, no-store

Connection: keep-alive

Content-Length: 853

Content-Type: application/json; charset=utf-8

Date: Thu, 31 Mar 2022 07:56:13 GMT

Expires: Thu, 31 Mar 2022 07:56:13 GMT

MS-CV: 4y7iMavy90m63YP3.0

Pragma: no-cache

Server: Microsoft-HTTPAPI/2.0

X-OSG-Served-By: WESTEUROPE_LEGACY00000T_<IP_ADDRESS>

{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.PackageMetadataResponse, StoreEdgeFD","Data":{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.PackageMetadataData, StoreEdgeFD","SourceIdentifier":"StoreEdgeFD","SourceAgreements":{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.SourceAgreements, StoreEdgeFD","AgreementsIdentifier":"StoreEdgeFD","Agreements":[{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageManifest.AgreementDetail, StoreEdgeFD","AgreementLabel":"Terms of Transaction","AgreementUrl":"https://aka.ms/microsoft-store-terms-of-transaction"}]},"ServerSupportedVersions":["1.0.0","1.1.0"],"RequiredQueryParameters":["market"],"RequiredPackageMatchFields":["market"]}}
2022-03-31 08:56:15.084 [REPO] Custom header not found.
2022-03-31 08:56:15.084 [REPO] Sending http GET request to: https://storeedgefd.dsx.mp.microsoft.com/v9.0/information
2022-03-31 08:56:15.085 [REPO] Http GET request details:
GET / HTTP/1.1

Content-Type: application/json

User-Agent: winget-cli WindowsPackageManager/1.3.692-preview DesktopAppInstaller/Microsoft.DesktopAppInstaller v1.18.692.0

2022-03-31 08:56:15.131 [REPO] Response status: 200
2022-03-31 08:56:15.131 [REPO] Response details:
HTTP/1.1 200 OK

Cache-Control: max-age=0, no-cache, no-store

Connection: keep-alive

Content-Length: 853

Content-Type: application/json; charset=utf-8

Date: Thu, 31 Mar 2022 07:56:13 GMT

Expires: Thu, 31 Mar 2022 07:56:13 GMT

MS-CV: rDlBPVTf90WRaePO.0

Pragma: no-cache

Server: Microsoft-HTTPAPI/2.0

X-OSG-Served-By: WESTEUROPE_LEGACY000006_<IP_ADDRESS>

{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.PackageMetadataResponse, StoreEdgeFD","Data":{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.PackageMetadataData, StoreEdgeFD","SourceIdentifier":"StoreEdgeFD","SourceAgreements":{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageMetadata.SourceAgreements, StoreEdgeFD","AgreementsIdentifier":"StoreEdgeFD","Agreements":[{"$type":"Microsoft.Marketplace.Storefront.StoreEdgeFD.BusinessLogic.Response.PackageManifest.AgreementDetail, StoreEdgeFD","AgreementLabel":"Terms of Transaction","AgreementUrl":"https://aka.ms/microsoft-store-terms-of-transaction"}]},"ServerSupportedVersions":["1.0.0","1.1.0"],"RequiredQueryParameters":["market"],"RequiredPackageMatchFields":["market"]}}
2022-03-31 08:56:15.131 [REPO] Adding to aggregated source: winget
2022-03-31 08:56:15.146 [CORE] Examining extension: PFN = Microsoft.Winget.Source_8wekyb3d8bbwe, ID = IndexDB
2022-03-31 08:56:15.146 [CORE] Found matching extension.
2022-03-31 08:56:15.166 [REPO] Opening SQLite Index for ImmutableRead at 'C:\Program Files\WindowsApps\Microsoft.Winget.Source_2022.331.843.391_neutral__8wekyb3d8bbwe\Public\index.db'
2022-03-31 08:56:15.166 [SQL ] Opening SQLite connection: 'file:/C:/Program Files/WindowsApps/Microsoft.Winget.Source_2022.331.843.391_neutral__8wekyb3d8bbwe/Public/index.db?immutable=1' [1, 40]
2022-03-31 08:56:15.166 [SQL ] Enabling ICU
2022-03-31 08:56:15.167 [SQL ] Preparing statement #1: select [value] from [metadata] where [name] = ?
2022-03-31 08:56:15.167 [SQL ] Binding statement #1: 1 => majorVersion
2022-03-31 08:56:15.167 [SQL ] Stepping statement #1
2022-03-31 08:56:15.167 [SQL ] Statement #1 has data
2022-03-31 08:56:15.167 [SQL ] Preparing statement #2: select [value] from [metadata] where [name] = ?
2022-03-31 08:56:15.167 [SQL ] Binding statement #2: 1 => minorVersion
2022-03-31 08:56:15.167 [SQL ] Stepping statement #2
2022-03-31 08:56:15.167 [SQL ] Statement #2 has data
2022-03-31 08:56:15.167 [SQL ] Preparing statement #3: select [value] from [metadata] where [name] = ?
2022-03-31 08:56:15.167 [SQL ] Binding statement #3: 1 => lastwritetime
2022-03-31 08:56:15.167 [SQL ] Stepping statement #3
2022-03-31 08:56:15.167 [SQL ] Statement #3 has data
2022-03-31 08:56:15.167 [REPO] Opened SQLite Index with version [1.3], last write [2022-03-31 08:43:49.000]
2022-03-31 08:56:15.283 [CLI ] Checking Source agreements for source: msstore
2022-03-31 08:56:15.283 [CORE] Setting action: Get, Type: Secure, Name: user_sources
2022-03-31 08:56:15.283 [CORE] Setting action: Get, Type: Standard, Name: sources_metadata
2022-03-31 08:56:15.283 [YAML] Detected UTF-8
2022-03-31 08:56:15.284 [CLI ] Source agreements satisfied. Source: msstore
2022-03-31 08:56:15.284 [CLI ] Checking Source agreements for source: winget
2022-03-31 08:56:15.284 [CORE] Setting action: Get, Type: Secure, Name: user_sources
2022-03-31 08:56:15.284 [CORE] Setting action: Get, Type: Standard, Name: sources_metadata
2022-03-31 08:56:15.284 [YAML] Detected UTF-8
2022-03-31 08:56:15.284 [CLI ] Source agreements satisfied. Source: winget
2022-03-31 08:56:15.284 [CORE] Setting action: Get, Type: Secure, Name: user_sources
2022-03-31 08:56:15.284 [CORE] Setting action: Get, Type: Standard, Name: sources_metadata
2022-03-31 08:56:15.284 [YAML] Detected UTF-8
2022-03-31 08:56:15.284 [REPO] Creating PredefinedInstalledSource with filter [None]
2022-03-31 08:56:15.284 [REPO] Creating new SQLite Index [4294967295.4294967295] at ':memory:'
2022-03-31 08:56:15.285 [SQL ] Opening SQLite connection: ':memory:' [6, 0]
2022-03-31 08:56:15.285 [SQL ] Enabling ICU
[...]
Preparing statement #9154: SELECT [versions].[version], [channels].[channel] FROM [manifest] JOIN [versions] ON [manifest].[version] = [versions].[rowid] JOIN [channels] ON [manifest].[channel] = [channels].[rowid] WHERE [id] = ?
2022-03-31 08:56:16.256 [SQL ] Binding statement #9154: 1 => 1292
2022-03-31 08:56:16.256 [SQL ] Stepping statement #9154
2022-03-31 08:56:16.256 [SQL ] Statement #9154 has data
2022-03-31 08:56:16.256 [SQL ] Stepping statement #9154
2022-03-31 08:56:16.256 [SQL ] Statement #9154 has data
2022-03-31 08:56:16.256 [SQL ] Stepping statement #9154
2022-03-31 08:56:16.256 [SQL ] Statement #9154 has data
2022-03-31 08:56:16.256 [SQL ] Stepping statement #9154
2022-03-31 08:56:16.256 [SQL ] Statement #9154 has completed
2022-03-31 08:56:16.261 [CLI ] Terminating context: 0x8a15002b at D:\a\_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:7c

Since that log looks Chinese to me and @Trenly didn't reply, could you post your log without --verbose-logs?
Tip for posting logs:

Click for Log

Past log here

Not sure how this missed my notifs the first time. I think what is missing is that some of the SQL queries which were cut could be informational.


Hi i am Getting this Error

i gave outlet for tableView but still getting the error. I am using custom TableViewController

@Gantaios Please check SampleViewController's tableView why it was nil this line.
This is probably not PullToDismiss fault.


Calendar days are misaligned

Correct the css properties for calendar week days bar

Fixed the padding in weekdays.module.css


Add my first file

vale,vale,vale, mas o menos?????  I don't know

i am not sure, maybe you need to modificate them once again


Https

Add https handlers to remaining samples

LGTM

Please look at why travis failed.

It's an issue with sparkjava demo from Ajay on Ludo's team.

It looks like a flaky test because of a concurrency issue.  Since Travis does two builds for each PR when merging one upstream branch into another, there could be interleavings in interactions with Datastore that result in tests failing.  I will create a PR to fix this.


"Account is not whitelisted!" even the owner/organization is on whitelist

https://github.com/fedora-iot/zezere/issues/2#issuecomment-567045033
even fedora-iot has already been whitelisted

[2019-12-18 13:56:53,861: INFO/ForkPoolWorker-1] Github App installation 'created' event. id: 5807653
[2019-12-18 13:56:53,861: WARNING/ForkPoolWorker-1] Cannot obtain project from this event!
[2019-12-18 13:56:53,861: WARNING/ForkPoolWorker-1] Skipping private repository check!
[2019-12-18 13:56:55,268: INFO/ForkPoolWorker-1] User 'puiterwijk' is a packager in Fedora!
[2019-12-18 13:56:55,269: INFO/ForkPoolWorker-1] Organization fedora-iot whitelisted!

[2019-12-18 14:04:45,967: INFO/ForkPoolWorker-1] Github issue#2 comment: '/packit propose-update' 'created' event.
[2019-12-18 14:04:45,968: INFO/ForkPoolWorker-1] Target repo: fedora-iot/zezere.
[2019-12-18 14:04:46,884: ERROR/ForkPoolWorker-1] User puiterwijk is not approved on whitelist!


Avoid MiTM by downloading through https

📊 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-npm-selenium-binaries/
⚙ Description *
Resources where downloaded through insecure connection enabling an attacker to intercept communications and replacing with malicious data, downloaded files are intended for execution
💻 Technical Description *
Replace http url with https for downloading resources
🐛 Proof of Concept (PoC) *
Download is performed through insecure connection
🔥 Proof of Fix (PoF) *
After fix Secure conection is stablished for downloads
👍 User Acceptance Testing (UAT)
Resources can be downloaded normally

Congratulations alromh87 - your fix has been selected! 🎉
Thanks for being part of the community & helping secure the world's open source code.
If you have any questions, please respond in the comments section, or hit us up on Discord. Your bounty is on its way - keep hunting!
Come join us on Discord


How to make sure Registering notification is succeeded ?

I have download BLE test tools from github and successfully compiled it.
After I executed the later version of test tools (1.1.2 and 1.1.3 which have BLECertificationTool.exe), I found the test tools didn’t receive response of commands (PIN, Message, …). But after executing 1.0  test tool (BLETest.exe), the new test tools executed behind will successfully receive the responses and will go on for further testing items.
I checked the source codes and found almost no difference in major functions except the latest codes support only for visual studio 2015. And I guess the registering notifications is not succeeded because the request is received and replied in my BLE devices.
Maybe there are some difference between test tools in the very beginning process before first request. Please help me to find solution.
My working station is win10, 64-bit, build 14393. The bluetooth module is Qualcomm Atheros.

Hi,
is this problem resolved?


Update project to use latest stable bs and bs-webapi

Hey @jmorrell! I've updated the project as indicated. We've published a new version of bs-webapi which contains the canvas api you've wanted.
The significant part of the PR is in the second commit, https://github.com/jmorrell/playfulreason-terrain/pull/1/commits/d623ef09cdd68879242ed07d883c004d0d64315a (the first one is just remove lib/bs which shouldn't be checked in). Took just 5 minutes to fix all the errors after an upgrade.
Thanks to you checking in the js artifacts, the upgrade is provably correct. You can eyeball terrain/pointMap/app.js to see that there's no conversion bug (I still ran the demo just in case).
Would it be possible to include an online demo in the README? I'm thinking of adding this to http://facebook.github.io/reason/resources.html#cool-projects

Thanks for the update @chenglou! And I picked up some pointers from your changes :)
Good idea, I'll add a demo link to the readme 👍

Readme updated with demo


Pass target to compilation time.

Make sure these boxes are checked! 📦✅

[ x] You have the latest version of rustfmt installed

$ rustup component add rustfmt

[x ] You ran cargo fmt on the code base before submitting
[x ] You reference which issue is being closed in the PR text

This PR is to provide the function that we can pass the target to compilation time.
See #795

Hello,
Any news about merging that? I also need this feature, so I am stuck with using the branch of that PR, and cannot benefit from the recent bug fixes...


[BUG] ServiceFabricProcessor throws an unexpected OperationCanceledException exception

This bug is similar to https://github.com/Azure/azure-sdk-for-net/issues/7933
The difference is the type of the exception thrown (+ I have some more details now).

ProcessErrorAsync is called with the following exception:

System.OperationCanceledException: The operation was canceled.
   at Microsoft.Azure.Amqp.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.Azure.Amqp.ReceivingAmqpLink.EndReceiveMessages(IAsyncResult result, IEnumerable`1& messages)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.OnReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)
   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.OnReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)
   at Microsoft.Azure.EventHubs.PartitionReceiver.ReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)
   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.ReceivePumpAsync(CancellationToken cancellationToken, Boolean invokeWhenNoEvents)
{"Type":"System.OperationCanceledException", "CancellationToken":{"IsCancellationRequested":false, "CanBeCanceled":false, "WaitHandle":{"Handle":"2244", "SafeWaitHandle":{"IsInvalid":false, "IsClosed":false}}}, "TargetSite":"Void Throw()", "StackTrace":"   at Microsoft.Azure.Amqp.AsyncResult.End[TAsyncResult](IAsyncResult result)\r\n   at Microsoft.Azure.Amqp.ReceivingAmqpLink.EndReceiveMessages(IAsyncResult result, IEnumerable`1& messages)\r\n   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.OnReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)\r\n   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.OnReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)\r\n   at Microsoft.Azure.EventHubs.PartitionReceiver.ReceiveAsync(Int32 maxMessageCount, TimeSpan waitTime)\r\n   at Microsoft.Azure.EventHubs.Amqp.AmqpPartitionReceiver.ReceivePumpAsync(CancellationToken cancellationToken, Boolean invokeWhenNoEvents)", "Message":"The operation was canceled.", "Data":{}, "Source":"System.Private.CoreLib", "HResult":-2146233029}

CloseAsync is called with Reason = Cancelled

ServiceFabricProcessor.RunAsync throws

System.OperationCanceledException: The operation was canceled.
   at Microsoft.Azure.EventHubs.ServiceFabricProcessor.ServiceFabricProcessor.RunAsync(CancellationToken fabricCancellationToken)
   at MyClass.RunAsync(CancellationToken cancellationToken)

The important thing here is that the CancellationToken passed to ServiceFabricProcessor.RunAsync() is NOT cancelled.
@JamesBirdsall Does this information help in any way?

@dmytro-gokun Can you please provide information on what NuGet package you are using please?

@adrianhill Okay, now i see something interesting. I'm referencing Microsoft.Azure.EventHubs.ServiceFabricProcessor version 0.5.5. But. That version is not even listed at https://www.nuget.org/packages/Microsoft.Azure.EventHubs.ServiceFabricProcessor/
Have it been somehow revoked?

I'd have to check with the service team to be sure.  However, that does happen if we know of a major issue.  To get you going, I'd downgrade to 0.5.4 (the latest version listed on NuGet), and see if you still experience the problem.

@adrianhall Thanks. I'll try downgrading, give it a spin for a week or so and let you know if I see this again.

Thanks - will close on 11/15/2019 unless we hear something.

@dmytro-gokkun please confirm that this is working for you. @sjkwak @JamesBirdsall FYI.

@peterpogorski So far, I have not seen this exact scenario with 0.5.4. However, this kinds of situations happen rarely in general, so i want to give it some more time to run before closing the issue.

I can now confirm that this exact issue exists with 0.5.4. I've seen it happening several times over this last weekend.

Thanks for the update and validation.


Godot 4 crashes when opening a project on Pop_OS!

Tested versions
4.2.1
System information
Pop_OS! Razer Blade 17, NVIDIA 3070
Issue description
I am trying to open my projects using Godot 4.2.1 on Pop_OS!
The project selection window pops up, and when I select a project (any project) I get the following error:
jacques@pop-os:~$ godot4
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 470.199.02 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.238 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (TGL GT1)
X Error:  BadDrawable
  Request Major code 149 ()
  Request Minor code 4
  ResourceID 0x340000a
  Error Serial #196
  Current Serial #235
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketLargeE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools12BucketMediumE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketSmallE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: BUG: Unreferenced static string to 0: TextServerDummy
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: IPUnix
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatImporterSaver
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: MovieWriterMJPEG
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: interface_added
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: TextServerAdvanced
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ImageFormatLoader
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatSaver
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: GDScriptEditorTranslationParserPlugin
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: MovieWriterPNGWAV
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ScriptLanguage
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatLoader
   at: unref (core/string/string_name.cpp:129)

Steps to reproduce
Open a project using Godot 4.2.1 on Pop_OS!
Minimal reproduction project (MRP)
Any project on Pop_OS!

Does the bug occur in Godot4.1.3 or Godot4.3-dev3?
Downloads https://godotengine.org/download/archive/

Does this happen with --rendering-method gl_compatibility?

Does the bug occur in Godot4.1.3 or Godot4.3-dev3?
Downloads https://godotengine.org/download/archive/

I am using Godot 4.2.1

Does this happen with --rendering-method gl_compatibility?

I will try that!

Does the bug occur in Godot4.1.3 or Godot4.3-dev3?
Downloads https://godotengine.org/download/archive/

I am using Godot 4.2.1

I know, what you're asking is whether you've tested in different versions, because sometimes it's a problem that was fixed in version 4.3. Test to confirm (not in your project, create a new project for test).
I noticed is that although your GPU (RTX 3070) supports Vulkan, when opening the project instead of using the RTX 3070, the project tries to use "Intel(R) UHD", there is the possibility of RTX driver is not updated.

Vulkan API 1.3.238 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (TGL GT1)

Does the bug occur in Godot4.1.3 or Godot4.3-dev3?
Downloads https://godotengine.org/download/archive/

I am using Godot 4.2.1

I know, what you're asking is whether you've tested in different versions, because sometimes it's a problem that was fixed in version 4.3. Test to confirm (not in your project, create a new project for test).

I will try running on 4.3 to check.

I noticed is that although your GPU (RTX 3070) supports Vulkan, when opening the project instead of using the RTX 3070, the project tries to use "Intel(R) UHD", there is the possibility of RTX driver is not updated.

Vulkan API 1.3.238 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (TGL GT1)

Yes I noticed this too. I am not sure if there is a way to set it back? I uninstalled and reinstall the latest NVIDIA drivers for Pop_OS! and there was not any change to this.

Yes I noticed this too. I am not sure if there is a way to set it back? I uninstalled and reinstall the latest NVIDIA drivers for Pop_OS! and there was not any change to this.

When you create a new project, does it open with Intel UHD too?

Does the bug occur in Godot4.1.3 or Godot4.3-dev3?
Downloads https://godotengine.org/download/archive/

I have the following results to report:
Tested with:

Snap Install sudo snap install godot4 using Godot 4.2.1 stable.
Download Archive using Godot 4.1.3 stable
Download Archive using Godot 4.2 stable
Download Archive using Godot 4.3.1 dev

Test 1 Results (Original Install using Snap Store Godot 4.2.1 stable)
Error, Crash, from Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (TGL GT1)
For some reason it is not using my NVIDIA gpu
jacques@pop-os:~$ godot4
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

jacques@pop-os:~$ godot4
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.238 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (TGL GT1)
X Error:  BadMatch
  Request Major code 149 ()
  Request Minor code 4
  Error Serial #196
  Current Serial #235
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketLargeE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools12BucketMediumE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketSmallE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
ERROR: BUG: Unreferenced static string to 0: TextServerDummy
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: IPUnix
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatImporterSaver
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: MovieWriterMJPEG
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: interface_added
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: TextServerAdvanced
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ImageFormatLoader
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatSaver
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: GDScriptEditorTranslationParserPlugin
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: MovieWriterPNGWAV
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ScriptLanguage
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: ResourceFormatLoader
   at: unref (core/string/string_name.cpp:129)

Test 2 Results (Download Archive using Godot 4.1.3 stable)
Success, no issues.
jacques@pop-os:~/Downloads$ ./Godot_v4.1.3-stable_linux.x86_64
Godot Engine v4.1.3.stable.official.f06b6836a - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

WARNING: Detected another project.godot at /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer. The folder will be ignored.
     at: _should_skip_directory (editor/editor_file_system.cpp:2366)
Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.1.3.stable.official.f06b6836a - https://godotengine.org
Vulkan API 1.3.260 - Forward+ - Using Vulkan Device #2: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Test 3 Results (Download Archive using Godot 4.2 stable)
Success, no issues.
jacques@pop-os:~/Downloads$ ./Godot_v4.2-stable_linux.x86_64
Godot Engine v4.2.stable.official.46dc27791 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.2.stable.official.46dc27791 - https://godotengine.org
Vulkan API 1.3.260 - Forward+ - Using Vulkan Device #2: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Test 4 Results (Download Archive using Godot 4.3 dev3)
Success, no issues.
jacques@pop-os:~/Downloads$ ./Godot_v4.3-dev3_linux.x86_64
Godot Engine v4.3.dev3.official.36e943b6b - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.3.dev3.official.36e943b6b - https://godotengine.org
Vulkan API 1.3.260 - Forward+ - Using Vulkan Device #2: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

I use the snap store for a lot of my packages, I would prefer to keep using the snap store version so I can easily keep my godot install up-to-date with snap refresh as opposed to manually having to manage my godot versions.

Does this happen with --rendering-method gl_compatibility?

I will try that!

It looks like that works, but there is a warning as follows:
jacques@pop-os:~/Downloads$ godot4 --rendering-method gl_compatibility
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

Editing project: /home/jacques/Code/godot/udemy-gamedevtv-complete-godot-2d/projects/SpeedySaucer
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 545.29.06 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU

jacques@pop-os:~/Downloads$ WARNING: Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
     at: _editor_init (modules/gltf/register_types.cpp:63)
WARNING: Glow is not supported when using the GL Compatibility backend yet. Support will be added in a future release.
     at: environment_set_glow (servers/rendering/storage/environment_storage.cpp:387)

@frederickjjoubert These warnings are common, the first is because you didn't configure the tool to import from Blender (something that is optional), and the second warning is because the lighting in gl_compatibility does not support GLOW.
These warnings are common, the first is because you didn't configure the tool to import from Blender (something that is optional), and the second warning is because the lighting in gl_compatibility does not support GLOW.
Note that gl_compatibility still has several limitations: https://docs.godotengine.org/en/stable/contributing/development/core_and_modules/internal_rendering_architecture.html#compatibility

@frederickjjoubert These warnings are common, the first is because you didn't configure the tool to import from Blender (something that is optional), and the second warning is because the lighting in gl_compatibility does not support GLOW.
These warnings are common, the first is because you didn't configure the tool to import from Blender (something that is optional), and the second warning is because the lighting in gl_compatibility does not support GLOW.
Note that gl_compatibility still has several limitations: https://docs.godotengine.org/en/stable/contributing/development/core_and_modules/internal_rendering_architecture.html#compatibility

I think we should ignore these warnings as they are not related to the problem at hand as far as I can tell. I'm working on a 2D project, I am not working with anything blender or glow related.

Looks related to #93268