binance GET starting error

Hello,
I have an issue when i want to start binance (for trading paper)
here is the error message
An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=IOTABTC&startTime=1513625832410&endTime=1513669032410 request timed out (10000 ms)
at timeout.catch.e (/mnt/c/zenbot/node_modules/ccxt/js/base/Exchange.js:266:27)
at  constructor: [Function: RequestTimeout] }
For info i'm using bash on windows
thanks in advance for your help

same issue here.. URL loads in browser

Please re-open your ticket using the issue template.

same here. opens in browser perfectly
$ docker-compose exec server zenbot trade
fetching pre-roll data:
api running on <IP_ADDRESS>:20003/trades
An error occurred { Error: binance GET https://api.binance.com/api/v1/exchangeInfo request timed out (10000 ms)
    at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:276:27)
    at <anonymous> constructor: [Function: RequestTimeout] }
An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=TRXBTC&startTime=1513716541092&endTime=1513759741092 request timed out (10000 ms)
    at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:276:27)
    at <anonymous> constructor: [Function: RequestTimeout] }

Same Here
api running on <IP_ADDRESS>:20029/trades Fri, 22 Dec 2017 02:26:57 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:635:30 An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=XRPBTC&startTime=1513823217672&endTime=1513866417672 request timed out (10000 ms)     at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:280:27)     at <anonymous> constructor: [Function: RequestTimeout] } An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=XRPBTC&startTime=1513823217672&endTime=1513866417672 request timed out (10000 ms)     at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:280:27)     at <anonymous> constructor: [Function: RequestTimeout] }

api running on <IP_ADDRESS>:20029/trades
Fri, 22 Dec 2017 02:26:57 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:635:30
An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=XRPBTC&startTime=1513823217672&endTime=1513866417672 request timed out (10000 ms)
at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:280:27)
at  constructor: [Function: RequestTimeout] }
An error occurred { Error: binance GET https://api.binance.com/api/v1/aggTrades?symbol=XRPBTC&startTime=1513823217672&endTime=1513866417672 request timed out (10000 ms)
at timeout.catch.e (/app/node_modules/ccxt/js/base/Exchange.js:280:27)
at  constructor: [Function: RequestTimeout] }

i think The bug is here but i don't know how to fix it
` var args = {};
if (opts.from) {
args.startTime = opts.from
}
if (opts.to) {
args.endTime = opts.to
}
if (args.startTime && !args.endTime) {
// add 12 hours
args.endTime = args.startTime + 43200000
  }
  else if (args.endTime && !args.startTime) {
    // subtract 12 hours
    args.startTime = args.endTime - 43200000
  }

`

Please re open!

I fixed it just by setting a bigger timeout. The response body is huge therefore needs a lot of time to retreive and parse.
https://github.com/carlos8f/zenbot/blob/master/extensions/exchanges/binance/exchange.js#L14
changed to:
new ccxt.binance({ 'apiKey': '', 'secret': '', timeout: 50000 })

I am not sure if there is a global way to fix the timeout with exchanges that use cctx.
Hope it helps


Feat enhance connuri crawling

instead of crawling all the connection uris directly and only returning the ones we actually want we just get all the connectionUris from a need, and then storing the closed ones similar to the process we will implement for deactivated needs (in the local storage) so we do not ever crawl a closed connection again on reload/login etc... the connection is marked as closed if the connection is added to the redux state and has a state of WON.Closed, or when the connectionState itself changes
Fixes in this branch:
-removed an unused method
-called the executeCrawlableQuery with the right set of parameters (3 instead of 2)
-omit further crawling for a connUri that has already been deemed as closed (from the localStorage)
This should enhance the login speed for users with alot of needs and connections tremendously in the future (first time and incognito access will not go any faster as we will not know which connections are already closed, but everybody else will hopefully experience a huge performance enhancement on the second reload and or login)
happy happy joy joy
ps: @fkleedorfer please don't be mad, that i did this, i needed a palate cleanser after the gui fixes
One should see the change by looking into the localStorage and finding a set of connectionUris that have already been closed, and also on login/reloads after the first one has been completed you should find the following logentry for connecitons that have been omitted in crawling  "[connUri] closed, ommit further crawl for this uri" (without the [])
calling won.clearClosedConnUris()  in the debug console, resets this localStorage element to nothing again (for testing purposes)

there is still an issue in this one, as it seems, even with these last commits
i will block this pr until further notice

pr can be rechecked, is not yet on integration-test  though

app. there was a commit that was necessary that i seemed to forget to push and therefore it did not work (utils.js) -> last commit fixed a wrong expression

seems to work now...


NFL Roster Error(s)

While processing many of the Rosters, many come back with the error:
ParserError: Document is empty
This happens over a wide range of years and teams.
from sportsreference.nfl.roster import Roster
r=Roster('CIN',1990)

Hello @denutza, thanks for the issue! I actually just ran into this myself and created a small patch to resolve this issue. It looks like this is due to some player pages being invalid/missing/incomplete, especially for some of the earlier seasons, which causes the ParserError as there is no information to pull. I will create a PR and get the patch merged shortly so it can be resolved for my next release which should come relatively soon.
Thanks again!


az login fails: OSError: [WinError -2146893813]

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
The command failed with an unexpected error. Here is the traceback:
[WinError -2146893813] : ''
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 657, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 691, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/profile/custom.py", line 145, in login
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line 155, in login
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/auth/identity.py", line 121, in login_with_auth_code
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 1488, in acquire_token_interactive
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 280, in obtain_token_by_browser
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 660, in obtain_token_by_browser
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 135, in obtain_token_by_auth_code_flow
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 204, in obtain_token_by_auth_code_flow
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 548, in obtain_token_by_auth_code_flow
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 714, in _obtain_token_by_authorization_code
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 115, in _obtain_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 771, in _obtain_token
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 523, in <lambda>
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 307, in add
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 113, in add
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 184, in __add
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line 44, in modify
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line 35, in _reload_if_necessary
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/persistence.py", line 172, in load
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/windows.py", line 111, in unprotect
OSError: [WinError -2146893813] : ''

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az login

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.30.0

Additional Context

@jiasli for awareness

Same as #20231

+ MSAL developer @rayluo
@vperala, have you copied .azure from/to another computer? Could you share the detailed steps you followed to trigger this error? Thanks.

Agree with @jiasli 's triage. By the way, a suggestion to @jiasli : you can convert this issue into a Q&A in Az CLI's Github Discussion, and then select your answer as "chosen answer". This way, it remains visible to future customers, therefore you can safely close those stale issues like #17186.
Or even better, either Az CLI or MSAL EX could perhaps catch that exception and convert it to something like RuntimeError: Unable to decrypt token cache. Did you copy token cache from another computer?

Hi Jiasli,
My issue was resolved after deleting all the files and folders under C:\Users<username>.azure folder and tried to reinstall Azure CLI from windows powershell(run as Administrator) with the below command. It's working fine now.
Command:
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Thanks!!

My issue was resolved after deleting all the files and folders under C:\Users.azure folder and tried to reinstall Azure CLI from windows powershell(run as Administrator) with the below command. It's working fine now.

Congrats @vperala for recovering from the issue. Can you tell us more on the history of that C:\Users\username\.azure folder? Did you manually copy it from a different computer?

If your answer is yes, then the error is expected (it is a security feature), although @jiasli and I may still consider some User eXperience (UX) improvement here.
If your answer is no, then it could be a sequence of operation causing our token cache file to be created unencrypted (by older version of Az CLI?), and then upgrading to Az CLI v2.30+ would attempt to decrypt that file and failed. This would become a migration faq, then.

it could be a sequence of operation causing our token cache file to be created unencrypted (by older version of Az CLI?)

The old ADAL-based Azure CLI saves tokens to ~/.azure/accessTokens.json, while the new MSAL-based Azure CLI saves tokens to ~/.azure/msal_token_cache.json or ~/.azure/msal_token_cache.bin (enrypted), so they work independently.

Hi,
I get the same error.
Here are my repro steps:

was working in version 2.31.0,
upgraded using az upgrade to 2.32.0
az login produced the error
Uninstalled Azure CLI
installed version 2.31.0 again, the eror persisted

full log is here:
The command failed with an unexpected error. Here is the traceback: [WinError -2146893813] : '' Traceback (most recent call last):   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 658, in execute   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 692, in _run_job   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/profile/custom.py", line 149, in login   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line 155, in login   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/auth/identity.py", line 171, in login_with_auth_code   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 1546, in acquire_token_interactive   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 280, in obtain_token_by_browser   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 640, in obtain_token_by_browser   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 678, in _obtain_token_by_browser   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 135, in obtain_token_by_auth_code_flow   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 204, in obtain_token_by_auth_code_flow   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 548, in obtain_token_by_auth_code_flow   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 732, in _obtain_token_by_authorization_code   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 115, in _obtain_token   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 789, in _obtain_token   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 581, in <lambda>   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 307, in add   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 113, in add   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 184, in __add   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line 67, in modify   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line 58, in _reload_if_necessary   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/persistence.py", line 180, in load   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/windows.py", line 114, in unprotect OSError: [WinError -2146893813] : ''

Update:
I tried using the command with a different windows user account and it worked fine.
So i deleted the C:\Users\<user>\.azure
And it works.
Maybe, upgrade comand should be updated to remove the conflictual configuration.

@lucianbalaban, I don't think this is related to upgrade, as we didn't change any code for token encryption between 2.31.0 and 2.32.0.

Workaround
First, you may try to clear the credential cache and re-login:
az account clear
az login

If this still doesn't help, you may temporarily turn off token cache encryption. (⚠ This is an internal experimental config option. We may change it or drop it anytime.)
az config set core.encrypt_token_cache=false
az login

Hi,
my error was solved by deleting the .azure folder.
I cannot replicate it anymore.
If it happens again, I will try the az account clear
Thanks!
On Fri, Jan 7, 2022 at 8:40 AM Jiashuo Li @.***> wrote:

Workaround
First, you may try to clear the credential cache and re-login:
az account clear
az login
If this still doesn't help, you may temporarily turn off token cache
encryption. (⚠ This is an internal experimental config option. We may
change it or drop it anytime.)
az config set core.encrypt_token_cache=false
az login
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/20231#issuecomment-1007176901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLLTVRONZ7QBWPC7JJV6NLUU2DG5ANCNFSM5HPZWHLQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

For anyone who deleting the .azure folder doesn't work for, have a look at this discussion: https://github.com/AzureAD/microsoft-authentication-library-for-python/discussions/446.
Re-synchronising my machine time solved my login issue.

@Christopher-Balnaves, "RuntimeError: 0. The ID token is not yet valid." is irrelevant to this issue.

I was able to catch this after local user password reset. Deletion of the .azure solve it.

Got this error from terraform plan in SSH session.
Full error:
Error: obtaining Authorization Token from the Azure CLI: parsing json result from the Azure CL I: waiting for the Azure CLI: exit status 1: ERROR: Decryption failed: [WinError -2146893813] Ke y not valid for use in specified state.. App developer may consider this guidance: https://githu b.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError

PS F:> (New-Object System.Net.WebClient).Proxy.Credentials = `
[System.Net.CredentialCache]::DefaultNetworkCredentials
PS F:> az login
az : WARNING: A web browser has been opened at
https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web
browser. If no web browser is available or if the web browser fails to open, use device code flow with az  login --use-device-code.
At line:1 char:1

az login

  + CategoryInfo          : NotSpecified: (WARNING: A web ...e-device-code`.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: [WinError 0] : ''
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py",
line 658, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py",
line 721, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py",
line 692, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py",
line 328, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operat
ion.py", line 121, in handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/profile/cust
om.py", line 139, in login
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/_profile.py", line
155, in login
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/auth/identity.py",
line 171, in login_with_auth_code
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 1546, in
acquire_token_interactive
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 280, in
obtain_token_by_browser
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 640,
in obtain_token_by_browser
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 678,
in _obtain_token_by_browser
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 135, in
obtain_token_by_auth_code_flow
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 204, in
obtain_token_by_auth_code_flow
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 548,
in obtain_token_by_auth_code_flow
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 732,
in _obtain_token_by_authorization_code
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oidc.py", line 115, in
_obtain_token
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/oauth2cli/oauth2.py", line 789,
in _obtain_token
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/application.py", line 581, in

File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 307, in add
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 113, in add
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal/token_cache.py", line 184, in
__add
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line
67, in modify
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/token_cache.py", line
58, in _reload_if_necessary
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/persistence.py", line
180, in load
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msal_extensions/windows.py", line
114, in unprotect
OSError: [WinError 0] : ''
To open an issue, please run: 'az feedback'
PS F:> $ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
PS F:> az account clear
PS F:> az login
az : WARNING: A web browser has been opened at
https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web
browser. If no web browser is available or if the web browser fails to open, use device code flow with az  login --use-device-code.
At line:1 char:1

az login

  + CategoryInfo          : NotSpecified: (WARNING: A web ...e-device-code`.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

ERROR: Decryption failed: [WinError 0] None. App developer may consider this guidance: h
ttps://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/Persistenc
eDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20278
PS F:> az config set core.encrypt_token_cache=false
az : WARNING: Command group 'config' is experimental and under development. Reference and support levels:
https://aka.ms/CLI_refstatus
At line:1 char:1

az config set core.encrypt_token_cache=false

  + CategoryInfo          : NotSpecified: (WARNING: Comman...s/CLI_refstatus:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

PS F:> az login
az : WARNING: A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize.
Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use
device code flow with az login --use-device-code.
At line:1 char:1

az login

  + CategoryInfo          : NotSpecified: (WARNING: A web ...e-device-code`.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

ERROR: ('Cannot connect to proxy.', NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x0522DCD0>:
Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
PS F:> $env:HTTP_PROXY
http://proxy.prv:80
PS F:>

I ran in to the same issue today.  I had a password change several days ago, needed to run an az command today which prompted me that the grant was no longer valid.  Was able to az login again and work as expected.  Several hours later, I started seeing this issue with any az command.  I was able to move forward by deleting msal_token.cache.bin and msal_http_cache.bin and relogging in.

Hi Jiasli, My issue was resolved after deleting all the files and folders under C:\Users.azure folder and tried to reinstall Azure CLI from windows powershell(run as Administrator) with the below command. It's working fine now.
Command:
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Thanks!!

This solution worked for me properly with 'az cli v2.38.0' thanks!

For me worked removing .azure folder:
C:\users<your user>.azure
Before it I've executed the command too:
az upgrade
But removing folder just could works,
The problem I think was when I used Az Cloud Shell and Powershell togheter

Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20231

Here same error:
az login
A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with az login --use-device-code.
Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20231

Also facing this issue after rotating the password for a Service Principal.
usage:
az login --service-principal -u $env:AZ_NAME -p $env:AZ_PWD --tenant $env:AZ_TENANT

Here is the error:
Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
azure-cli                         2.46.0

core                              2.46.0
telemetry                          1.0.8

Dependencies:
msal                              1.20.0
azure-mgmt-resource             21.1.0b1

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\buildadmin\.azure\cliextensions'

Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:05:00) [MSC v.1929 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

deleting the 'msal_http_cache.bin', 'msal_token_cache.bin', 'service_principal_entries.bin' files fixed the problem.

Also facing this issue after rotating the password for a Service Principal.
usage:
az login --service-principal -u $env:AZ_NAME -p $env:AZ_PWD --tenant $env:AZ_TENANT

@jiasli, unlike most other reports here, this report provided repro steps. Do you think that code path would alter the token cache file?

Yes. az login --service-principal saves the service principal credential to service_principal_entries.bin and access tokens to `msal_token_cache.bin'.

After I changed my windows 11 password, I couldn't use my az cli anymore. For whatever command I'm getting: "Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError"
After deleting in the .azure folder msal_*.bin and relogging it works like a charm again

Token cache is protected by DPAPI, which seems to be affected by a password reset. @jiasli, do we consider adding this as a hint in our error message?

Can confirm that deleting your C:\users.azure folder and reinstalling the Azure CLI solves the problem. No obvious explanation as to why this problem occurs in the first place.

I ran into this as well on a Windows VM where I ran az login --tenant {tenant name} for the first time after reseting my password on the VM through the Azure portal (maybe that has the same affect of resetting the password from computer management which causes this issue?).
In addition to what kierke-gaard got, I got a message with a bit more info when I passed the "--debug" option:
msal_extensions.persistence.PersistenceDecryptionError: [Errno -2146893813] Decryption failed: [Errno -2146893813] Key not valid for use in specified state. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError: 'C:\\Users\\myuser\\.azure\\msal_token_cache.bin
Based on that github wiki in the error message, I figured that the file it printed at the end was the file it was having trouble with (and likely got corrupted with the password reset), so I moved that to my home directory, ran the "az login --tenant {tenant name}" command again, and everything worked! It looks like it regenerated that file with the new login.

This happened after a routine password reset via AD sync. Lots of Windows internal credential caches were messed up. Based on some advice from Dell based on Windows TPM Error 80090016, I ended up moving the AAD BrokerPlugin directory out of the way and letting Windows repopulate it via a sizable number of manual logins. I suspect this contributed to the MSAL auth failures.
I tried selectively clearing bad login tokens by using "az logout" but this just showed the same error.
Finally, like so many others before me, I moved the .azure directory out of the way and logged back in, which worked.

This happened after a routine password reset via AD sync. Lots of Windows internal credential caches were messed up. Based on some advice from Dell based on Windows TPM Error 80090016, I ended up moving the AAD BrokerPlugin directory out of the way and letting Windows repopulate it via a sizable number of manual logins. I suspect this contributed to the MSAL auth failures.
I tried selectively clearing bad login tokens by using "az logout" but this just showed the same error.
Finally, like so many others before me, I moved the .azure directory out of the way and logged back in, which worked.

The token cache file is encrypted on Windows. Presumably, the password reset also implicitly changes the encryption/decryption key, so, the entire token cache file is no longer usable. Individual "az logout" won't work in this case because it would still require a successful decryption (and then encryption) to the token cache file.
This would perhaps become an FAQ (if it hasn't already).

I would agree that the issue is caused by DPAPI, which changes keys if passwords are reset by administrators.
If DPAPI doesn't have the key anymore az login will have to start over, it makes sense to just prompt before deleting the un-decryptable file(s) since 99% of the time it will never be decryptable again. Even az account clear fails with this error in this scenario, it seems like it should be able to truly start over.

I would agree that the issue is caused by DPAPI, which changes keys if passwords are reset by administrators.
If DPAPI doesn't have the key anymore az login will have to start over, it makes sense to just prompt before deleting the un-decryptable file(s) since 99% of the time it will never be decryptable again. Even az account clear fails with this error in this scenario, it seems like it should be able to truly start over.

I'll leave it to this issue's assignee (@jiasli) to decide whether Azure CLI's az account clear shall remove the token file without attempting to decrypt it.

I am getting this error on a transient basis.
This is on a new installation, I have not upgraded or moved any /.azure folder.

a python script so the VM can deallocate itself under some condition, and my logs show this error prevented that from happening. It failed many times consecutively throughout the night as the condition was met, but as soon as I tried the commands in a new Powershell window, they worked.

Was your script running without a user logs in? On some other platforms, the token encryption/description does not work without an active user login session. This may or may not be the case on Windows, though.

You need to reticulate your splines.

Probably. Yes it was running as an account that didn't necessarily log in and I didn't think that should be a requirement? I switched to Linux to solve this problem :)

I had the same issue with az version 2.49.0. I'm running Windows 10. I did not change my password in the past few weeks, and I never used the azure client on this computer.
This is a company device, and I also didn't use the azure client on my previous ones. Until now, I connected to a jumphost via ssh that had the azure cli installed, but now I can't because our infra department changed their MFA policy, and I can only use azure cli on the same computer on which I opened the browser and logged in.
I deleted the .azure folder and reinstalled azure cli. az account clear produced the same error. Nothing helped, except for
az config set core.encrypt_token_cache=false
Now it works. But it keeps me wondering what else is broken or will be in the future. It's an "experimental feature" anyway.
Microsoft, why can't we have nice tools? Or proper error messages? Or our problems taken care of?

set core.encrypt _token_cache=false is always the answer. Every time it happens to me or anyone i know, anyway

Hi all,
I have an error executing az login today:
PS C:\WINDOWS\system32> Az login --use-device-code
To sign in, use a web browser to open the page https://microsoft.com/deviceloginchina and enter the code E9XKMQJQF to authenticate.
Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20231

az login

A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with az login --use-device-code.

It did open in the browser all ok, and got this in the console

Decryption failed: [WinError -2146893813] Key not valid for use in specified state.. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError

The solution was to delete files in $HOME/.azure

clibot unresolve the issue

#23828 relies on msal_token_cache.bin to retrieve MSAL accounts and log out from WAM:
https://github.com/Azure/azure-cli/blob/b00483c1a1cd17053af5c483f62b11c829f4c27d/src/azure-cli-core/azure/cli/core/auth/identity.py#L208-L216
If msal_token_cache.bin can't be accessed, even az account clear will fail with OSError: [WinError -2146893813].
@rayluo, I think we do need a way to log out of WAM even when msal_token_cache.bin is broken/lost/cannot be accessed.

#23828 relies on msal_token_cache.bin to retrieve MSAL accounts and log out from WAM:
https://github.com/Azure/azure-cli/blob/b00483c1a1cd17053af5c483f62b11c829f4c27d/src/azure-cli-core/azure/cli/core/auth/identity.py#L208-L216
If msal_token_cache.bin can't be accessed, even az account clear will fail with OSError: [WinError -2146893813]. We have to manually delete ~/.azure/msal_token_cache.bin, but this will leave those accounts still in WAM.
@rayluo, I think we do need a way to log out of WAM even when msal_token_cache.bin is broken/lost/cannot be accessed.

How about MSAL Python switch its internal order to remove the WAM accounts first, and then attempt removing accounts from msal_token_cache.bin? That way, you will still see the same exception, but at least the WAM account would have been purged.

Az login failing with:
az login
A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with az login --use-device-code.
Decryption failed: [WinError -2146893813] Key not valid for use in specified state. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20231

This error is also occurring for me in two different Azure DevOps pipelines.

Gettings this from Azure DevOps (windows) using pwsh task
steps:
  - pwsh: |
      az login `
        --service-principal `
        -u "$($ApplicationId)" `
        -p "$($ApplicationSecret)" `
        --tenant "$($TenantId)"

error:
ERROR: Decryption failed: [WinError -2146893813] Key not valid for use in specified state. App developer may consider this guidance: https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/PersistenceDecryptionError
Please report to us via Github: https://github.com/Azure/azure-cli/issues/20231

Also seeing this issue in ADO pipelines when attempting to deploy ARM templates using AzureResourceManagerTemplateDeployment (3.240.0)

MSFT folks, I created an IcM for Azure DevOps to investigate this on their end, as well: https://portal.microsofticm.com/imp/v5/incidents/details/518493207/summary

For now, switching to AzureCLI@2 + service connection seems to work for us
see our PR: https://github.com/Azure/azure-dev/pull/4059/files#diff-0d3b6413c574b41f329a04185bb8eb2edea3b7eefa65d8ddcaf81a613129a92eR96

On my laptop this was fixed by removing $env:USERPROFILE\.azure\msal*.bin and then az account clear && az login


Move getNodeInfo() from DABOM to PITcleanr

Seeing as the function uses a parent-child table and configuration file as inputs, seems to make more sense to house this within the PITcleanr package. In general, it makes sense to me to make PITcleanr as independent of other packages like STADEM or DABOM as possible, but I'm fine if DABOM or STADEM relies on PITcleanr.

getNodeInfo() is not really used in any other PITcleanr functions. In addition, it does contain a call to defineDabomColNms(). One suggestion might be to include a function defineCapHistCols() (using the second_node = T argument) in PITcleanr, and have getNodeInfo call that, and therefore make it easier to move getNodeInfo into PITcleanr.
Then perhaps defineDabomColNms could either be replaced by defineCapHistCols in DABOM, or modified to make use of defineCapHistCols with perhaps a few other options to help with DABOM models.

Everything in the previous comment has been done.


Broken link for Demo on the README page

Describe the bug
Broken link on "What is Yor trace?" paragraph.
To Reproduce
Steps to reproduce the behavior:

Go to 'What is Yor trace?' paragraph on README.md
Click the demo link

Expected behavior
Redirect to demo page on yor.io

Thanks! i just pushed a fix :)


Wrong serialization of AuthenticatedContent

TLS serialization of AuthenticatedContent appears to be wrong. The wire_format is missing in the type and it's not serialized as the first value in FramedContentTbs.
cc @kkohbrok

Thanks for bringing this up. I'll take a look.

Ah, I see what's going on. FramedContentTbs includes the version, but AuthenticatedContent doesn't. So it turns out my construction where we just include FramedContentTbs in AuthenticatedContent doesn't quite work without a manual serialization of AuthenticatedContent. I'll try to find a solution.


Update Composer dependencies (2021-10-15-00-03)

Visual regression test passed!
View the visual regression test report


Support for auto generation of spec objects from a spec dir and misc changes

Add support for parsing application specs from a spec dir
Add missing support for Service
Change torpedo k8s deployment to use pod instead of jobs to avoid restart issue
Add postgres and nginx apps support
Add missing hostkey issue for ssh node driver
Perform deep copy of spec objects in factory and modify clones during schedule

I have kept the PR open but merged the changes to hasten the process.


semantic-release changelog before semantic-release --noop version

Hi,
Thank you for the python-semantic-release project,
I noticed that when I use semantic-release changelog to generate changelogs (after creating many commits) and  before bumping new version with semantic-release --noop version , python-semantic-release will not show changelogs,
I want to know if it's possible de generate changelogs with semantic-release changelog before bumping new version with semantic-release --noop version

Open to PRs for showing unreleased things in the changelog with a flag --unreleased to the changelog command.


SqlilteDataReader GetBytes NotSupportedException

Recently i tried to retrieve a BLOB from a table which fires a NotSupportedException.
The method GetBytes of the SqliteDataReader or to be more specific SqliteDataRecord is not implemented yet. Why is the functionallity absent? I can see that internally reading a blob is supported by the method GetBlobCore. The native stuff like raw.sqlite3_column_blob and raw.sqlite3_column_bytes is available, so it could work. Is there another way available?
Will this be supported in the upcoming 2.1 release?

Use GetFieldValue<byte[]>()

(Or GetValue() as byte[])

Still not implemented as of 2.1.0.  Be nice Microsoft would implement this functionality like other packages such as System.Data.Sqlite.

@jpfreyen if you look at #18 it is planned for 2.2.0

You can try it out using the nightly builds

Thanks for the nightly builds link; I'll look into it :-).


Add unit tests on Planar Joint

Planar Joint is not tested at all and it will be mandatory for the integration of Pinocchio in HPP.
For kinematics checking, one idea is to create a serial chain with same one DOF joints than in the planar one.
For dynamics computation, we can check against RBDL.

Solved by #148.


A first implementation of userdata in callbacks.

A first implementation of userdata in callbacks. Just an example in set_on_click_listener, see its usage in simple_app.py

@nzjrs Give a look at simple_app.py. I implemented the usedata only for set_on_click_listener, just for an example. Is this ok?

Ok for the widget retrieved in the callback, I will do this. But It's not clear for me the problem of mixing userdata and standard parameter. You showed two code examples:
def my_clicked_callback(self, widget_that_was_clicked, *userdata):
    pass

def my_onmousemove_callback(self, widget, x, y, *userdata):
    pass

Are these the desired callbacks prototypes? In this case *userdata is not unpacked. For me could be ok.

Yeah, it's clear, it just reminded me to mention this....
On 18 October 2016 at 11:02, Davide Rosa<EMAIL_ADDRESS>wrote:

@dddomodossola commented on this pull request.
In remi/gui.py https://github.com/dddomodossola/remi/pull/137:

@@ -537,7 +538,7 @@ def set_on_mousedown_listener(self, listener, funcname):
def onmouseup(self, x, y):
"""Called when the user releases left or right mouse button over a Widget.
"""

   return self.eventManager.propagate(self.EVENT_ONMOUSEUP, [x, y])

   return self.eventManager.propagate(self.EVENT_ONMOUSEUP, (x, y))

Yeah, I've not passed yet userdata in other callbacks, it is just
implemented for set_on_click_listener. The change you highlighted is just a
conversion from list to tuple and is not directly related to the userdata.
Is this clear?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjo9inX29geUumGSQ2LUYzJ-04UOGcks5q1IspgaJpZM4KZc6S
.

The usual convention is that userdata is always unpacked when calling the
callback, and if the user passes userdata parameters, he is responsible for
making his prototype API compatible.
IMO the API is nicer and It is easier to work with if the eventmanager
unpacks userdata - but it can make the implementation more complicated.
On 18 October 2016 at 11:05, Davide Rosa<EMAIL_ADDRESS>wrote:

Ok for the widget retrieved in the callback, I will do this. But It's not
clear for me the problem of mixing userdata and standard parameter. You
showed two code examples:
def my_clicked_callback(self, widget_that_was_clicked, *userdata):
pass
def my_onmousemove_callback(self, widget, x, y, *userdata):
pass
Are these the desired callbacks prototypes? In this case *userdata is not
unpacked. For me could be ok.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254449764,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjoyZ0DRbmqRlOL5YmKBErXQEZG9LIks5q1IvqgaJpZM4KZc6S
.

The changes to pass unpacked userdata to callbacks are already implemented in EventManager.
i.e.:
self.bt.set_on_click_listener(self, 'on_button_pressed', 'userdata1', 2)
and:
def on_button_pressed(self, userdata1, userdata2):
    pass

As you can see the 'userdata1' and '2' are additional userdata parameters to the listener registration. The listener receives userdata1 and userdata2 unpacked.
This should be conformant. Isn't  it?
The missing thing is the widget emitter parameter that should be passed to the listener. So the result of this should be:
self.bt.set_on_click_listener(self, 'on_button_pressed', 'userdata1', 2)
and:
def on_button_pressed(self, widget, userdata1, userdata2):
    pass

Is this right? Or I misunderstood something?

I think a more interesting test is to see how the API works for a callback
that passes it''s own parameters in addition. Maybe it is clearer what I
mean if you try to implement the onmouseup / onmousedown callbacks, with
optional userdata, in the simple_app demo. I hope that clarifies things a
bit.
On 18 October 2016 at 11:17, Davide Rosa<EMAIL_ADDRESS>wrote:

The changes to pass unpacked userdata to callbacks are already implemented
in EventManager.
i.e.:
self.bt.set_on_click_listener(self, 'on_button_pressed', 'userdata1', 2)
and:
def on_button_pressed(self, userdata1, userdata2):
pass
As you can see the 'userdata1' and '2' are additional userdata parameters
to the listener registration. The listener receives userdata1 and userdata2
unpacked.
This should be conformant. Isn't it?
The missing thing is the widget emitter parameter that should be passed to
the listener. So the result of this should be:
self.bt.set_on_click_listener(self, 'on_button_pressed', 'userdata1', 2)
and:
def on_button_pressed(self, widget, userdata1, userdata2):
pass
Is this right? Or I misunderstood something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254452462,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjo1vRjfMQf8pEYOq1UXEvkr1HfeSNks5q1I6kgaJpZM4KZc6S
.

@nzjrs Ok I test it ;-)

Take a look at the last commit. This is an example with onmousedown and onmouseup. Seems ok to me. What about this?

How do you feel about breaking API and pass the widget that sent the event
as the first parameter to all callbacks?
On 18 October 2016 at 11:34, Davide Rosa<EMAIL_ADDRESS>wrote:

Take a look at the last commit. This is an example with onmousedown and
onmouseup. Seems ok to me. What about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254456529,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjoyHJd58qphRBE8wOl0VowprdN0E3ks5q1JKVgaJpZM4KZc6S
.

I feel ok with this. It will be usefull in different use cases. Can I proceed on implementing this additional change?

I added another example. Can you quickly prototype passing the sender as
the first argument?
If we are breaking API, how about instead of passing the function name, we
pass the actual function, or is there a reason this is not currently done?
On 18 October 2016 at 11:44, Davide Rosa<EMAIL_ADDRESS>wrote:

I feel ok with this. It will be usefull in different use cases. Can I
proceed on implementing this additional change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254458987,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjo0DiWVrnS7m-V9L7SgqVepFCTorwks5q1JT3gaJpZM4KZc6S
.

Yeah, I will try to make it soon.
You mean passing the "function pointer"? This causes serious difficulties in the Editor application, but maybe I can solve this. Let me check this evening about this.

Yeah. Passing the function by name is quite weird when compared to other
gui toolkits
On 18 Oct 2016 12:00, "Davide Rosa"<EMAIL_ADDRESS>wrote:

Yeah, I will try to make it soon.
You mean passing the "function pointer"? This causes serious difficulties
in the Editor application, but maybe I can solve this. Let me check this
evening about this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254462654,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjowTTQYOg4b3mnsFlxtTf_VegAZzXks5q1JipgaJpZM4KZc6S
.

This is true. I will do the best to implement this. It allows also the error checking and autocompletion by IDEs.

@nzjrs Is the last commit conformant to what you suggested?

I changed the example a bit to be idiomatic of the benefits of passing
userdata and the sender as the first argument.
I had forgotten that one can only have one callback per signal. Do you
think it would be possible to also fix this limitation too?
then, all the functions get renamed from set_XXX_listener ->
add_XXX_listener
On 18 October 2016 at 12:00, Davide Rosa<EMAIL_ADDRESS>wrote:

Yeah, I will try to make it soon.
You mean passing the "function pointer"? This causes serious difficulties
in the Editor application, but maybe I can solve this. Let me check this
evening about this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dddomodossola/remi/pull/137#issuecomment-254462654,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjowTTQYOg4b3mnsFlxtTf_VegAZzXks5q1JipgaJpZM4KZc6S
.

I think that this is not feasible John. I feel it logically wrong and I think this is not allowed by the architecture of the library. ,Consider that some callbacks could return a value to the page, acting as ajax does...

John, what about new changes? :-D

I think that this is not feasible John. I feel it's logically wrong and I think this is not allowed by the
architecture of the library. ,Consider that some callbacks could return a value to the page, acting as
ajax does...

As you wish. It's a common pattern to have multiple callbacks in other GUI frameworks, but if it's not possible then I will just do it in the code on my side.
The rest of the changes look good. I would say you could squash the branch and merge it.


The import language affect the benchmark result

Describe the bug
I try the following code and run vitest bench
import { bench, describe } from "vitest";
import { after as afterToolkit } from "es-toolkit/function";

const after = afterToolkit;
const add = (a: number, b: number) => a + b;
const n = 10;
describe("after", () => {
  bench("es-toolkit/after - reassign", () => {
    after(n, add);
  });

  bench("es-toolkit/after", () => {
    afterToolkit(n, add);
  });
});

Here's what I got:

You can see that a direct import statement using import is significantly slower than reassigning values
However, when I try tinybench like this:
import { Bench } from "tinybench";
import { after as afterToolkit } from "es-toolkit";

const bench = new Bench({ time: 100 });
const add = (a: number, b: number) => a + b;
const n = 10;
const after = afterToolkit;
bench
  .add("es-toolkit/after - reassign", () => {
    after(n, add);
  })
  .add("es-toolkit/after", () => {
    afterToolkit(n, add);
  });

await bench.warmup();
await bench.run();

console.table(bench.table());

There is no difference between them:

Reproduction
Use the code above
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-13400F
    Memory: 16.18 GB / 31.82 GB
  Binaries:
    Node: 20.13.1 - D:\nodejs\node.EXE
    Yarn: 1.22.22 - D:\nodejs\yarn.CMD
    npm: 10.5.2 - D:\nodejs\npm.CMD
    bun: 1.1.27 - D:\nodejs\bun.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    vitest: ^2.0.4 => 2.0.4

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The same issue arises when calling with the subpath as shown below, resulting in a performance difference.
Before
import { bench, describe } from 'vitest';
import { after as afterToolkit } from 'es-toolkit'; // This is difference.
import { after as afterLodash } from 'lodash';

describe('after', () => {
 bench('es-toolkit/after', () => {
   const add = (a: number, b: number) => a + b;
   const n = 10;
   const afterFn = afterToolkit(n, add);
   for (let i = 0; i < n + 1; i++) {
     afterFn(1, 2);
   }
 });

 bench('lodash/after', () => {
   const add = (a: number, b: number) => a + b;
   const n = 10;
   const afterFn = afterLodash(n, add);
   for (let i = 0; i < n + 1; i++) {
     afterFn(1, 2);
   }
 });
});

Bench Result

Using subpath
import { bench, describe } from 'vitest';
import { after as afterToolkit } from 'es-toolkit/function'; // This is difference.
import { after as afterLodash } from 'lodash';

describe('after', () => {
  bench('es-toolkit/after', () => {
    const add = (a: number, b: number) => a + b;
    const n = 10;
    const afterFn = afterToolkit(n, add);
    for (let i = 0; i < n + 1; i++) {
      afterFn(1, 2);
    }
  });

  bench('lodash/after', () => {
    const add = (a: number, b: number) => a + b;
    const n = 10;
    const afterFn = afterLodash(n, add);
    for (let i = 0; i < n + 1; i++) {
      afterFn(1, 2);
    }
  });
});

Bench Result

Additional
You can see our barrel files in here(src/index.ts, src/function/index.ts.
Thanks

This is likely due to how Vite/Vitest transform and import modules. You can roughly see that by VITE_NODE_DEBUG_DUMP=1 and import/export are transformed as Object.defineProperty, which might be causing perf hit when benchmarking simple enough functions.
For example, in this reproduction https://stackblitz.com/edit/vitest-dev-vitest-br64n3?file=src%2Fbasic.bench.ts,
// basic.ts
export const squared = (n: number) => n * n

// basic.bench.ts
import { squared } from './basic.js';

squared(2)

will be transformed to something like
const viteSsrExports = Object.create(null);

const viteSsrExportsSquared = (n: number) => n * n;

Object.defineProperty(viteSsrExports, 'squared', {
  enumerable: true,
  configurable: true,
  get() {
    return viteSsrExportsSquared;
  },
});

viteSsrExports.squared(2)

To avoid this, you need to benchmark without transforming, so you need to use pre-built version of es-toolkit.

Is there a workaround for this bug (without modifying code in src)? It appears to occur when importing anything from another file, whether from node_modules or local project files.

@crimx Here's how we handle it in es-toolkit:

Use deps.optimizer.ssr to bundle the source files, thus eliminating the import overhead inside the modules

deps: {
  optimizer: {
    ssr: {
      enabled: true,
      include: ['es-toolkit', 'es-toolkit/compat'],
    },
  },
}

Re-assign values to imported variables, thus eliminating import overhead in the bench file

import { bench, describe } from 'vitest';
import { chunk as chunkToolkit_ } from 'es-toolkit';
import { chunk as chunkCompatToolkit_ } from 'es-toolkit/compat';
import { chunk as chunkLodash_ } from 'lodash';

const chunkToolkit = chunkToolkit_;
const chunkCompatToolkit = chunkCompatToolkit_;
const chunkLodash = chunkLodash_;

describe('chunk', () => {
  bench('lodash/chunk', () => {
    chunkLodash([1, 2, 3, 4, 5, 6], 3);
  });

  bench('es-toolkit/chunk', () => {
    chunkToolkit([1, 2, 3, 4, 5, 6], 3);
  });

  bench('es-toolkit/compat/chunk', () => {
    chunkCompatToolkit([1, 2, 3, 4, 5, 6], 3);
  });
});

After all this effort, our results are not too far off from tinybench (although there are still some gaps)
before
   name                                hz     min     max    mean     p75     p99    p995    p999     rme  samples
   · lodash/chunk              7,786,900.20  0.0000  0.4533  0.0001  0.0001  0.0003  0.0003  0.0005  ±0.73%  3893461   slowest
   · es-toolkit/chunk         10,678,422.00  0.0000  0.9141  0.0001  0.0001  0.0002  0.0002  0.0003  ±0.46%  5339211   fastest
   · es-toolkit/compat/chunk   7,789,212.00  0.0000  1.2057  0.0001  0.0001  0.0003  0.0003  0.0005  ±0.52%  3894606

after
  name                                hz     min     max    mean     p75     p99    p995    p999     rme  samples
   · lodash/chunk             17,114,118.00  0.0000  1.3395  0.0001  0.0001  0.0001  0.0001  0.0003  ±1.21%  8557059   fastest
   · es-toolkit/chunk         15,336,056.93  0.0000  0.7054  0.0001  0.0001  0.0001  0.0002  0.0002  ±0.47%  7668030   slowest
   · es-toolkit/compat/chunk  15,599,688.00  0.0000  0.4493  0.0001  0.0001  0.0001  0.0002  0.0002  ±0.30%  7799844

tinybench
┌─────────┬─────────────────────┬──────────────┬────────────────────┬──────────┬─────────┐
│ (index) │ Task Name           │ ops/sec      │ Average Time (ns)  │ Margin   │ Samples │
├─────────┼─────────────────────┼──────────────┼────────────────────┼──────────┼─────────┤
│ 0       │ 'lodash'            │ '17,132,909' │ 58.36720090166528  │ '±2.20%' │ 1713291 │
│ 1       │ 'es-toolkit'        │ '16,746,723' │ 59.71317402670255  │ '±0.67%' │ 1674674 │
│ 2       │ 'es-toolkit/compat' │ '16,974,469' │ 58.912001376214626 │ '±0.54%' │ 1697447 │
└─────────┴─────────────────────┴──────────────┴────────────────────┴──────────┴─────────┘

We hope our efforts have inspired you.


Update RackConnect v3 heat file to support new overlord repository

Can you please squash all of these commits into a single one before i merge it?

Sure, sorry
Le Thu Jan 08 2015 at 16:40:14, Mike Metral<EMAIL_ADDRESS>a
écrit :

Can you please squash all of these commits into a single one before i
merge it?
—
Reply to this email directly or view it on GitHub
https://github.com/metral/corekube/pull/8#issuecomment-69196714.


Roll Engine from ace1f5f2997b to e6821345d27e (1 revision)

https://github.com/flutter/engine/compare/ace1f5f2997b...e6821345d27e
2021-11-17<EMAIL_ADDRESS>Roll Dart SDK from 46934d8475ff to 6e6558437a09 (4 revisions) (flutter/engine#29774)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


updated .after file to set window to the context instead of doing not…

changed the var.after file so that i could be plopped into a build system and build for whatever window it was currently being executed for. (useful when dealing with multiple windows)

realized that i needed to do it for all the other files.

OK, innerHTML might indeed be broken after last changes but I wonder why instead of fixing just that you are modifying all other templates?

sorry? i did not know that innerhtml was broken. all of the tests passed for me when i built. i may be a bit confused regarding how to actually use this shim, but i do know, that in order for this to work in the middle of a larger script or in environments with a different than default setup, the this keyword should be used so that at least something can be understood from the context rather than a variable that may or may not exist

The build folder is the one that contains scripts:
https://github.com/WebReflection/document-register-element/tree/master/build
If you use the node module, it uses global already:
https://github.com/WebReflection/document-register-element/blob/master/build/document-register-element.node.js#L1423
If you use the regular DOM env, it passes window because it's global too.
When you use this you are doing nothing different than using window because you'll expect all other things retrieved per realm (Object, document, etc) to be in that context .
On AMD builds the context might be asynchronous and not bound to a use strict executed function so this would break while window won't.
There are no environment where window is not available but this is, since we are talking about a DOM related polyfill, so while this can be ambiguous, window never is (beside the node module that uses global indeed).
Accordingly, since this polyfill has always worked on production, I was wondering why instead of adjusting the only file that indeed has problems due latest changes, you decided that this was a better choice.
Since like I've explained, this is not actually necessarily the case, I was thinking maybe you had some issue but AFAICT the only issue you had was with the innerHTML file, right?
In such case I won't accept this PR as is because it does a bit too much.
Please confirm innerHTML was the only issue, thank you.

Actually, now that I look at files in src ... what is again the problem here?
Maybe I misunderstood this PR entirely ... I don't see any error in the current build.
Also you shouldn't edit build files directly, these get overwritten every time I publish new versions.

P.S. if your goal is to install the script in an iframe, like Google AMP is doing already, you might want to use the official approach require('document-register-element').installCustomElements(window)

that's ok. i didn't notice problems with innerhtml either. for me, all 39 tests worked. i committed any changes that were made by myself plus any changes that the build process made (by running: make) this was so i could make sure that all of the tests were still running. the build files were not excluded with a gitignore so i assumed they were part of the commit. do you have instructions regarding how you would like pull requests done somewhere? maybe i missed it. but regarding your other point about async environments not working, if you would be so kind as to open the code on my next comment, you will see that browsers do indeed ser the context if the context is not already bound on the callback passed into the async methods of settimeout and raf.

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title></title>
    <link rel="stylesheet" href="">
</head>
<body>
    <script>
        setTimeout(function (argument) {
            console.log(this);
        });
        requestAnimationFrame(function () {
            console.log(this);
        });
    </script>
</body>
</html>

i am loading in these scripts without the use of requires and have to expand their use to multiple iframes below the single one they are loaded from.

You said you have problems with your build process, I say you can have problems with this with other build processes too.
setTimeout(function(){'use strict';(function(){console.log(this)}())});
That one logs undefined
If any 3rd parts wrapper execute this code outside the global scope there's no gian, just a bet, on what the context will be and it won't solve any problem at all cross realm because if you have window reference on the top level script of an iframe, that is the global window of that iframe.
this in nodejs is the module itself, it can be anything ... window can, and should be never ambiguous.
So I'll ask again> what real-world problem are you trying to solve?

fair enough. goodbye


Disable the network connection in non-live tests

Resolves #138.

I decided not to take the implementation in:
https://github.com/best-doctor/pytest_network
as is, mainly for these issues:

https://github.com/best-doctor/pytest_network/issues/12
https://github.com/best-doctor/pytest_network/issues/13


data labels in grid

Hello,
is there any way to add text labels in the grid (not the axis), above or below the data coordinates?

Hi, this is possible in v2 now!


[BEAM-9199] Require Dataflow --region in Python SDK.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Portable_Python PreCommit

Run Python PreCommit

I found quite a few more examples where --region needed to be added. Because this is a breaking change and it's very likely I've missed places, I will send an email to the dev list so that everyone is aware of this change (and the upcoming changes to Java and Go).

Still LGTM. Thanks for the other updates.

Failure in hdfsIntegrationTest looks like known flake (BEAM-7405 et al): docker-credential-gcloud not installed or not available in PATH


File specific rule not getting applied

Hi team, thanks for this awesome plugin 🙏
Describe the bug
The plugin is not taking into account [per-file-ignores]
To Reproduce
Steps to reproduce the behavior:

Create a ruff file like below (name it ruff.toml

# Enable this list of rules.
select = [
    "S",  # flake8-bandit
]
ignore = []
target-version = "py311"

# Rules to Ignore for matching files.
[per-file-ignores]
# "test files" (i.e. unit tests)
"test_*.py" = [
    "S101",  # Use of assert detected
    "S311",  # Standard pseudo-random generators are not suitable for cryptographic purposes
    "SLF001",  # Private member accessed: {access}
]

Create python file and name it test_ruff_rule_in_pycharm.py

def test_something() -> None:
    """Ruff will highlight the below assert in PyCharm."""
    assert True

Expected behavior
The assert in test_ruff_rule_in_pycharm.py should NOT be highlighted like the one shown in Screenshots section. CLI works perfectly fine.
Screenshots

Environments

IDE: PyCharm 2023.2.1 (Professional Edition)
OS: Fedora Linux 35
Ruff Version 0.0.290
Plugin version 0.0.20

@fenilgmehta
Thank you for reporting the issue.
Unfortunately, I can't reproduce the problem.
Would you happen to have the additional information to find the root cause?
Other users have shared similar problems, but I can't reproduce them in my environment. https://github.com/koxudaxi/ruff-pycharm-plugin/issues/291

https://github.com/koxudaxi/ruff-pycharm-plugin/issues/291
This is a duplicate of this one and will be closed.


relationalai 0.2.9 :snowflake:

relationalai 0.2.9 :snowflake:
Destination channel: Snowflake
Links

PKG-4599
dev_url: :warning: not available, see comments in the ticket
conda-forge:
pypi: https://pypi.org/project/relationalai/0.2.9
pypi inspector: https://inspector.pypi.io/project/relationalai/0.2.9

Explanation of changes:

new feedstock, patch to remove debugger CLI command.
⚠ ~license not known~ LICENSE in the recipe/ folder, Apache-2.0.
a repository is not available yet, no home, no dev_url, no doc_url.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_32fy41v96s/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:78: missing_license_file: The recipe is missing the about/license_file or about/license_url key.

===== ERRORS =====

clone/recipe/meta.yaml:78: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:78: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:78: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:78: missing_license: The recipe is missing the about/license key.
clone/recipe/meta.yaml:78: missing_home: The recipe is missing a homepage URL
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_4fgvsp5qf8/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:78: missing_license_file: The recipe is missing the about/license_file or about/license_url key.

===== ERRORS =====

clone/recipe/meta.yaml:78: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:78: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:78: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:78: missing_license: The recipe is missing the about/license key.
clone/recipe/meta.yaml:78: missing_home: The recipe is missing a homepage URL
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_b9cczfcfi9/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:82: missing_license_file: The recipe is missing the about/license_file or about/license_url key.

===== ERRORS =====

clone/recipe/meta.yaml:82: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:82: missing_license: The recipe is missing the about/license key.
clone/recipe/meta.yaml:82: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:82: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:82: missing_home: The recipe is missing a homepage URL
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_45qscxzxow/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:91: missing_license_file: The recipe is missing the about/license_file or about/license_url key.

===== ERRORS =====

clone/recipe/meta.yaml:91: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:91: missing_home: The recipe is missing a homepage URL
clone/recipe/meta.yaml:91: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:91: missing_license: The recipe is missing the about/license key.
clone/recipe/meta.yaml:91: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d20il1exhn/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:90: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:90: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:90: missing_home: The recipe is missing a homepage URL
===== Final Report: =====
3 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_c9cgcsdvu_/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:91: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:91: missing_home: The recipe is missing a homepage URL
clone/recipe/meta.yaml:91: missing_documentation: The recipe is missing a doc_url or doc_source_url
===== Final Report: =====
3 Errors and 0 Warnings were found

@lorepirri As you build v0.3.4 I updated the PR's title and links

@lorepirri As you build v0.3.4 I updated the PR's title and links

Ah thank you, I forgot about that 👍

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_9fp3jg99yx/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:88: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_914ebm8ayg/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:88: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_c60r0e90a6/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:88: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
1 Error and 0 Warnings were found


Implement per-instance custom bounding box

Allows to set custom bounding box for GeometryInstances. An example use case is when shader displacement is used, like with particles or heightmaps.
Note: this PR only implements the feature on VisualServer API.
Fixes https://github.com/godotengine/godot/issues/9544
This is the first time I modify VisualServer, tell me if I did anything wrong.
Note: I see that Particles already have customizable AABB for the same reason, however it is stored in RasterizerStorageGLES3... should I remove it now?

Made it a single function and rebased


Argument 1: cannot convert from

I get a compile error in:
Argument 1: cannot convert from 'BrandApplication.DataAccess.Interfaces.IGenericRepository<BrandApplication.DataAccess.Models.Brand>' to 'BrandApplication.DataAccess.Interfaces.IUnitOfWork'	BrandApplication.Business
Cheers

Hi MrBjorn, thanks for logging the issue and sorry for the late answer.
I just checked the app, built it and tested the apis and successfuly got the expected answers
Let me know the steps that you followed
Cheers


[Hotfix] Fix pos_corr2 property name

Codecov Report

Merging #334 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #334   +/-   ##
=======================================
  Coverage   89.63%   89.63%
=======================================
  Files          26       26
  Lines        3897     3897
=======================================
  Hits         3493     3493
  Misses        404      404

Impacted Files
Coverage Δ

lightkurve/lightcurvefile.py
92.18% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks, that makes sense!


Allow using a custom HttpClient

What steps will reproduce the problem?
Symfony is very opinionated and uses their own HttpClient implementation and interfaces.
Since there are perfectly fine PSR standards for this and other implementations of the Symfony HttpClientInterface exist, we should allow the user to configure it.
What's expected?
The Yii2 component should use the Yii2 DI container to retrieve dependencies, this allows for using configuration in the usual way.
What do you get instead?
I can't define my own http client configuration.
Proposed solution
Add a property public $httpClient = null and use it in the call to Transport::getDefaultFactories().

Also fixed in #27, pick whichever solution you prefer!


don't crash when using a CNAME ALIAS with zone.record_sets

This will solve issue #8, i tested this with a CNAME ALIAS and also tried to use record_set.is_alias_record_set()
when you try to print a record_set that is a CNAME ALIAS you will get:
TypeError: init() got an unexpected keyword argument 'alias_hosted_zone_id'

Wonderful, thanks! Maybe you could open an issue to nag me to release this to PyPi before I forget :)


Created Hannah's treasure hunt post!

Made a post with a program where you find Tina's treasure :crown: !

@nataliele Can you look this over and merge for me, please? Thanks!

@hannahlwang hey for the yaml author, do you have to use your github id?

@nataliele Yes! Thank you for catching that. I accidentally used my Onyen instead


[FEATURE] Elastic 8 Client - Stores Enums as Strings

Is your feature request related to a problem? Please describe.
Before enums were stored as integers, which allowed us to do range queries.
Ex: we have a Rating Enum, and sometimes we like to search above a certain rating.
Describe the solution you'd like
Options:

Go back to enums defaulting to integers.
Add a way to configure an enum field as integer or string.

Good to know, we can leverage the System.Text features.
However, these changes have other impacts:

Range Queries are not supported. (as stated above)
For Everyone, Upgrading from Nest to 8, All Term Queries will no longer work, and will have to go to ".keyword"
Text & Keyword is much larger than Int, so when having a large search db with a bunch of enums. This will now increase the size and slow down the index speed.
Responses will also be slower, with larger text to be sent over the network. some enum names can be really long.
Also, C# has flags, which are designed to store attributes in the smallest format, which would break the purpose of this.
https://dev.to/ayodejii/enum-flags-in-c-20a6
most nosql stores keep enums as int format.

Example of some Enum Values we use, that would be too wordy to store as strings.
        SuccessorAdditionalOrChangeInTrustee = 52,
        UnscheduledDrawCreditEnhancement = 53,
        SubstitutionCreditLiquidityProvider = 54 ,
        FinancialObligationIncurrence = 55,
        FinObligEventReflectingFinancialDifficulties = 56 ,
        FinancialObligationIncurrenceDebtObligation  = 57 ,
        FinancialObligIncurrenceGuaranteeDebtOblig = 58 ,
        FinanObligIncurrenceGuaranteeDerivativeInstr = 59,
        FinancialObligIncurrenceDerivativeInstrument = 60,
        FinanObligEventReflectFinDifficultiesDefault = 61,
        FinObligEventReflectFinDiffEventOfAccel = 62,
        FinObligEventReflectFinDiffTerminationEvent = 63,
        FinanObligEventReflectFinDiffModifOfTerms = 64 ,
        FinanObligEventReflectFinanDiffOther = 65,
        InitialAssetBackedSecuritiesDisclosure = 66 ,
        QuarterlyAssetBackedSecuritiesDisclosure = 67 ,
        AnnualAssetBackedSecuritiesDisclosure = 68,
        OtherAssetBackedSecuritiesDisclosure = 69 ,
        BankLoanAlternativeFinancingFilings = 70

The new default behavior was decided before I joined the team and there probably are as well good arguments in favor of this change. Maybe @Mpdreamz @stevejgordon can remember these?

Range Queries are not supported. (as stated above)

Range queries on enum fields is a nieche use-case and probably even indicates a wrong type. Enums are not intended to cover a continuous range of values.

For Everyone, Upgrading from Nest to 8, All Term Queries will no longer work, and will have to go to ".keyword"

Term query is the wrong thing to use for enum values anyways. A match query would be more approriate imo, because you are looking for an exact match and not a semantic term.
However, your point is completely valid. This is a breaking change and could mess with existing data, if not carefully handled (like e.g. using the workaround I mentioned above). I have to check, if this point is part of the migration guide..
The other arguments do all boil down to some advances/disadvantages of the underlaying data type. I still think the current default is good as it minimizes surprises (especially for rather inexperienced developers or new users who don't think about the underlaying types). For the more advances users there still is the option to customize this behavior like using a custom converter like mentioned above.
Maybe I could make the default configurable to make it a little bit easier to switch back to ordinal values.

I remember we did this because we got a lot of bug reports where this caught people off guard.
For sure [Flag] enums should be serialised as integers (if they aren't already).
With https://github.com/elastic/elastic-ingest-dotnet we don't default to writing enums as strings because System.Text.Json also doesn't.
The one argument for sending them as integers is to allow people to rename enums values provided they maintain the enum ordering.
We should align  https://github.com/elastic/elastic-ingest-dotnet with the client behaviour though.

@Mpdreamz there are also performance benefits to using int over string.

less network overhead
less serialization
faster indexing (text & keyword need larger indexes partial/tokenized matching). Integers only need to be indexed for terms.

I have a few objects where we save with over 100 different enums in each object, with batches of 10k models. The change to will impact performance heavily.
Also updating each and every field that uses an enum would take a very long time. Can we just make this configurable by the framework?


Implement a test case using individual steps to build the whole ramclust.R workflow

Since the main ramclustR.R file has become somewhat obsolete with the new individual components, it would be good to mark it as deprecated or even remove the functionality from the package after making sure that everything is kept where it actually should be. Another option would be to have this function as a default workflow running the fundamental steps of RAMClustR, so keeping it intact as a main wrapper @cbroeckl ?
To make sure that the functionality is kept or equivalent, we need a test case which runs the individual steps and then we can make a comparison to the results created by the old ramclustR function.

I am reluctant to deprecate unless we know how people are using it.  It would be good to keep it around until we can cofirm that we can get similar output using the rc.ramclustr.R or further 'chunked' function.  Correct me if i am wrong, but you have been using the original ramclustR.R function, correct?

I am reluctant to deprecate unless we know how people are using it.  It would be good to keep it around until we can cofirm that we can get similar output using the rc.ramclustr.R or further 'chunked' function.  Correct me if i am wrong, but you have been using the original ramclustR.R function, correct?

Yeah, our Galaxy tool actually also uses this. Then let's agree on providing it as a wrapper and let's try to get the same output using the individual rc. functions?

i think that what makes the most sense is to keep it as the main function, but as a wrapper.  once we can get the old and new chunked version to get the same output, we can start working on building in the functionality in the rc.### functions.

So lets replace the ramclustR function code with the calls to those steps - we have already implemented a test and the results are the same within the tolerance.

what is the 'tolerance'?

+- 10 values on intensity of detected features and mz differences in 5th digit after the comma in deconvoluted spectra - and in our test data one extra deconvoluted spectrum appears (569 instead of 568). Number of peaks in each spectrum is excatly the same - so mostly small numeric differences.


Email Configuration Help

I cant seem to get the email functioning. I have read everything I can find. I am behind a firewall at work and want to use our corporate email server which support smtp and exchange. I am running kanboard on windows and under Xampp. I can get Xampp to send emails from itself using an external smtp server (hotmail).
Can someone give me some assistance?

Solved


Blueprint unassignment misnomer

The statement in the "Unassigning Assignments" section is a little confusing as Blueprints can be stored at the management group level but not assigned.

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

ID: 49c280c4-169c-a375-9242-87d5418f578b
Version Independent ID: 904b3b7a-9c8a-97d8-a2c1-acdf8b84cca2
Content: Understand the lifecycle of a blueprint - Azure Blueprints
Content Source: articles/governance/blueprints/concepts/lifecycle.md
Service: blueprints
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

#assign:DCtheGeek

@OxHobbs Thanks for the feedback.  Reviewing the wording with the PM and will address shortly.
@MicrosoftDocs/azure-cxp-triage Please label 'doc-enhancement' and #in-progress.

@OxHobbs The text is correct as a the blueprint assignment can exist at the management group, even though it still only applies to a subscription. This is available in REST (https://docs.microsoft.com/rest/api/blueprints/assignments/createorupdate#assignment-with-system-assigned-managed-identity-at-management-group-scope). I have an action to update other mentions in the docs to acknowledge and provide more details on this.  I'm going to close this issue now.  Thanks again for the feedback!
@MicrosoftDocs/azure-cxp-triage #please-close


[Snyk] Security upgrade npmconf from 0.0.24 to 2.1.3

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json
package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Uninitialized Memory Exposure npm:npmconf:20180512
  286

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Wrong content of ListBox after ItemSource change

Describe the bug
In a ListBox with the default settings for ItemsPanel modifications of the binded ItemsSource may lead to the some elements are not re-creaded and are shown in the list several times.
Note: seems the presence of non-null SelectedItem is mandatory to reproduce the problem
To Reproduce
Steps to reproduce the behavior:

Build and run the attached project.
AvaloniaApplication1.zip

Click the "Step 1" button.

Click the "Step 2" button.

Carefully compare the lists on the screen.

Note: some elements are different!

Resize the window as small as possible and resise it back (to force VirtualizingStackPanel recreate items)

Note: the contents of the lists are identical

Expected behavior
The contents of the lists should not depend on used ItemPanel.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows
Version 11.0.0-rc1.1

Additional context
Add any other context about the problem here.

great sample to test and great comparison 👍

Additional hint: if one resizes the window, the item is updated correctly.

Caused by AutoScrollToSelectedItem: if you set AutoScrollToSelectedItem="False" on the affected ListBox then the problem doesn't occur. What's happening is that the anchor index is updated when the item is inserted before the list of realized items is updated. When SelectingItemsControl.AutoScrollToSelectedItemIfNecessary tries to bring the item into view, because the realized item list isn't up-to-date with the actual state of the items, it re-realizes an item that already exists. #11418 should fix this, but I'm not totally happy with that solution as it requires on the dispatcher to delay scrolling to the selected item, which kinda feels unnecessary.


Merge pull request #1 from lightning0125/development

install apollo-server

No syntax highlighting (everything is either green or red).


feat: added queuer banner

The button link get knocked off on mobile. Let's simplify and leave off the button part and instead center what is currently left justified.

The button link get knocked off on mobile. Let's simplify and leave off the button part and instead center what is currently left justified.

I removed the Button on mobile because it feels cramped. But the text still links to review site same as the button.
but centered works too, also adding underline to make it more obvious


Support multiple choice for Delete Branch command.

This is for issue #60799

There are a few issues with this:

This new behavior changes expectations of existing users, who simply execute the command, then press Up and Down to pick the branch and finally hit Enter to delete the branch. This change will force everyone to additionally press Space for this command to actually do anything.
We could also track the focus and simply delete the branch which was last focused, in case the selection is empty. But this would change the multi-select paradigm and users used to it would definitely find it unexpected if an empty selection would delete branches.
We could simply add a new command Git: Delete Branches... but would that really be useful for people? Just sounds like bloat. Convince me otherwise, if you have some arguments.

Will close this for now.
Thanks for the PR anyway!


Step passed messages no longer in console output

Upgraded from v0.1.7 to 0.2.1 and the "Step Passed" console messages are no longer showing during spec execution.   Having step status messages on by default, rather than having to turn on the the verbose tag would be better.
Example from 0.1.7:   Step Passed => * Verify score is "4"

Hi,
We have received a few questions about this particular issue. There are a
few issues that need fixing in the console output area.

Colour schemes - we are looking into another library
Amount of information shown by default - this is especially hard because
a lot of people we speak to want varying amounts of information. We have
tried to handle this by providing flags so each user can get the kind of
output they prefer. A lot of users asked for even lesser information on the
console. I hope this makes sense.

For now,using the flag will give you the information you need. We're
working on this issue, we will have something soon.
On 19 October 2015 at 23:20, ocary<EMAIL_ADDRESS>wrote:

Upgraded from v0.1.7 to 0.2.1 and the "Step Passed" console messages are
no longer showing during spec execution. Having step status messages on by
default, rather than having to turn on the the debug or verbose tags would
be better.
Example from 0.1.7: Step Passed => * Verify score is "4"
—
Reply to this email directly or view it on GitHub
https://github.com/getgauge/gauge/issues/239.

My team has the same complaint. We have no way of knowing where in the execution we are. Are we on the second to last? Did it freeze on the first? How do we know? Many of our specs run for several minutes, so we want to know how far we've gotten.
I should also add that our primary use case is working with specs in Intellij IDEA. Right now, all execution is shown in the Run output, which is identical to the command line. If the Intellij plugin were made to be more like JUnit in that it graphically lists execution and their status, then we wouldn't care what the default output and the command line is.
To us, it seems obvious that knowing where in the spec we are should be shown be default. I'm curious why some have wanted even less default information though. Do they think it clogs up their log files? If so, that might be a different use case where they don't care where they are in a spec (perhaps they are doing an automated run in a continuous integration tool?).
Regarding color schemes, I personally don't care about them and see nothing wrong with the current output. It just seems kind of inappropriate for a console that is always white text on black. I would like colors in Intellij though, again, like JUnit.

We will definitely move to JUnit like execution results in IDEs. But it will take us some time to release it since it requires design change.

This is being taken care of as part of fixing #212. It will take some time before this is released because it needs a good amount of internal changes. We're on it :smile:

@ocary We have released Gauge v0.3.0 with support for colored console reporting. To see step details, please run with --verbose flag.


\Sabre\HTTP\ClientHttpException is not caught in WebDAVAdapter->getMetadata() method

My WebDAV service returns http 404 code when file does not exist (it's ok), so Sabre\DAV\Client throws \Sabre\HTTP\ClientHttpException but League\Flysystem\WebDAV\WebDAVAdapter->getMetadata() method catchs only Sabre\DAV\Exception.

Yes, i have the same problem.
I think it depends on that

ClientHttpException extends from \Exception
Exception extends from \Exception

But in the catch condition it matches only Exception not \Exception, and so on respectively NOT ClientHttpException

I met a same problem, could we fix this problem asap ?

👍 Thank you very much for the hotfix, it works like a charm now

@khanhicetea welcome :)


WInUI3 Gallery - link to documentation Button - API is broken

Describe the bug
In Button Example - click on link for  documentation link Button -API
get browser link of:
https://docs.microsoft.com/en-nz/windows/winui/api/microsoft.ui.xaml.controls.button
The page is not found  =error 404 Page not Found
Steps to reproduce the bug

As above
Expected behavior
Expect to see the doucumentation for Button API
Actual behavior
get browser link of:
https://docs.microsoft.com/en-nz/windows/winui/api/microsoft.ui.xaml.controls.button
The page is not found  =error 404 Page not Found
Screenshots

Version Info

Gallery version (found on Settings page):
 Version: <IP_ADDRESS>
WinUI version:

[ ] WinUI3 / WinAppSDK 1.1
[ ] WinUI3 / WinAppSDK 1.0
[ ] WinUI2

Windows 11 version:

[ ] Insider Build (xxxxx)
[ ] Windows 11 22H2 (22621)
[ ] Windows 11 21H2 (22000)

Windows 10 version:

[ ] November 2021 Update/21H2 (19044)
[ ] May 2021 Update/21H1 (19043)
[ ] October 2020 Update/20H2 (19042)
[ ] October 2018 Update/RS5 (17763)

Device form factor:

[ ] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

This seems to be a duplicate of #987, @RossCoeH please let me know if my I understood the bug report correctly :)

The issue is the same and still persisting on new updated version.

To make tracking of this easier, I'll be closing this as duplicate of #987 since that is a catch all for that bug.