az aks get-credentials fails to recognize aks-preview is installed

Describe the bug
I am trying to get the kubeconfig from an AKS cluster. It complains that aks-preview needs to be installed. I currently have the latest version of this package installed. It then doesn't find a suitable version to install because I have the latest and continues to fail. I have even tried downgrading that package and it doesn't work.
To Reproduce
az aks get-credentials -n {} -g {} --subscription {} --overwrite-existing -a
Expected behavior
This should make an entry in my kubeconfig for the AKS cluster specified.
Environment summary
Currently my environment:
zsh 5.8 (x86_64-apple-darwin20.0)
Python 3.9.0
Azure cli was installed using Brew
Homebrew 3.0.11
Homebrew/homebrew-core (git revision efa89684e9; last commit 2021-04-08)

azure-cli                         2.21.0

core                              2.21.0
telemetry                          1.0.6

Extensions:
aks-preview                        0.5.7

Python location '/usr/local/Cellar/azure-cli/2.21.0/libexec/bin/python'
Extensions directory '/Users/me/.azure/cliextensions'

Python (Darwin) 3.8.9 (default, Apr  3 2021, 01:51:00)
[Clang 12.0.0 (clang-1<IP_ADDRESS>)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy

Additional context
Here is the output when I run with --debug selected.
cli.knack.cli: Command arguments: ['aks', 'get-credentials', '-n', '{}', '-g', '{}', '--subscription', '{}', '--overwrite-existing', '-a', '--debug']
cli.knack.cli: __init__ debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x10e23d160>, <function OutputProducer.on_global_arguments at 0x10e2e6310>, <function CLIQuery.on_global_arguments at 0x10e302af0>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: No module found from index for '['aks', 'get-credentials', '-n', '{}', '-g', '{}', '--subscription', '{}', '--overwrite-existing', '-a', '--debug']'
cli.azure.cli.core: Loading all modules and extensions
cli.azure.cli.core: Discovered command modules: ['acr', 'acs', 'advisor', 'ams', 'apim', 'appconfig', 'appservice', 'aro', 'backup', 'batch', 'batchai', 'billing', 'botservice', 'cdn', 'cloud', 'cognitiveservices', 'config', 'configure', 'consumption', 'container', 'cosmosdb', 'databoxedge', 'deploymentmanager', 'dla', 'dls', 'dms', 'eventgrid', 'eventhubs', 'extension', 'feedback', 'find', 'hdinsight', 'interactive', 'iot', 'keyvault', 'kusto', 'lab', 'managedservices', 'maps', 'mo
nitor', 'natgateway', 'netappfiles', 'network', 'policyinsights', 'privatedns', 'profile', 'rdbms', 'redis', 'relay', 'reservations', 'resource', 'role', 'search', 'security', 'servicebus', 'servicefabric', 'signalr', 'sql', 'sqlvm', 'storage', 'synapse', 'util', 'vm']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: acr                       0.001         0         0
cli.azure.cli.core: acs                       0.001         0         0
cli.azure.cli.core: advisor                   0.001         0         0
cli.azure.cli.core: ams                       0.001         0         0
cli.azure.cli.core: apim                      0.001         0         0
cli.azure.cli.core: appconfig                 0.003         7        33
cli.azure.cli.core: appservice                0.170        62       220
cli.azure.cli.core: aro                       0.007         0         0
cli.azure.cli.core: backup                    0.001         0         0
cli.azure.cli.core: batch                     0.035         0         0
cli.azure.cli.core: batchai                   0.001         0         0
cli.azure.cli.core: billing                   0.003         0         0
cli.azure.cli.core: botservice                0.001         0         0
cli.azure.cli.core: cdn                       0.001         0         0
cli.azure.cli.core: cloud                     0.001         1         7
cli.azure.cli.core: cognitiveservices         0.001         0         0
cli.azure.cli.core: config                    0.001         2         7
cli.azure.cli.core: configure                 0.001         3         9
cli.azure.cli.core: consumption               0.001         0         0
cli.azure.cli.core: container                 0.001         0         0
cli.azure.cli.core: cosmosdb                  0.001         0         0
cli.azure.cli.core: databoxedge               0.003         5        27
cli.azure.cli.core: deploymentmanager         0.001         0         0
cli.azure.cli.core: dla                       0.001         0         0
cli.azure.cli.core: dls                       0.001         0         0
cli.azure.cli.core: dms                       0.001         0         0
cli.azure.cli.core: eventgrid                 0.001         0         0
cli.azure.cli.core: eventhubs                 0.004        14        51
cli.azure.cli.core: extension                 0.001         1         7
cli.azure.cli.core: feedback                  0.001         1         1
cli.azure.cli.core: find                      0.001         1         1
cli.azure.cli.core: hdinsight                 0.003         7        36
cli.azure.cli.core: interactive               0.000         1         1
cli.azure.cli.core: iot                       0.004        15        63
cli.azure.cli.core: keyvault                  0.006        11        68
cli.azure.cli.core: kusto                     0.001         0         0
cli.azure.cli.core: lab                       0.001         0         0
cli.azure.cli.core: managedservices           0.001         0         0
cli.azure.cli.core: maps                      0.001         0         0
cli.azure.cli.core: monitor                   0.001         0         0
cli.azure.cli.core: natgateway                0.001         3         0
cli.azure.cli.core: netappfiles               0.001         0         0
cli.azure.cli.core: network                   0.050       128       406
cli.azure.cli.core: policyinsights            0.001         0         0
cli.azure.cli.core: privatedns                0.004        14        66
cli.azure.cli.core: profile                   0.001         2         9
cli.azure.cli.core: rdbms                     0.002         0         0
cli.azure.cli.core: redis                     0.001         0         0
cli.azure.cli.core: relay                     0.001         0         0
cli.azure.cli.core: reservations              0.001         0         0
cli.azure.cli.core: resource                  0.008        36       128
cli.azure.cli.core: role                      0.004        17        55
cli.azure.cli.core: search                    0.001         0         0
cli.azure.cli.core: security                  0.004        36        81
cli.azure.cli.core: servicebus                0.001         0         0
cli.azure.cli.core: servicefabric             0.001         0         0
cli.azure.cli.core: signalr                   0.001         0         0
cli.azure.cli.core: sql                       0.001         0         0
cli.azure.cli.core: sqlvm                     0.001         0         0
cli.knack.cli: Event: CommandLoader.OnLoadCommandTable []
cli.azure.cli.core: storage                   0.032        42       154
cli.azure.cli.core: synapse                   0.007        33       142
cli.azure.cli.core: util                      0.001         2         4
cli.azure.cli.core: vm                        0.055        44       167
cli.azure.cli.core: Total (63)                0.442       488      1743
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: aks-preview               0.008         0         0  /Users/{}/.azure/cliextensions/aks-preview
cli.azure.cli.core: Total (1)                 0.008         0         0
cli.azure.cli.core: Loaded 480 groups, 1743 commands.
cli.azure.cli.core: Updated command index in 0.003 seconds.
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x10e866f70>]
az_command_data_logger: command args: aks get-credentials -n {} -g {} --subscription {} --overwrite-existing -a --debug
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to '/Users/{}/.azure/commands'.
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument.<locals>.add_subscription_parameter at 0x10e8a99d0>, <function register_global_query_examples_argument.<locals>.register_query_examples at 0x10eb035e0>]
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument.<locals>.add_ids_arguments at 0x10eb03670>, <function register_cache_arguments.<locals>.add_cache_arguments at 0x10eb03790>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs [<function _documentdb_deprecate at 0x10f7c04c0>]
cli.azure.cli.core.parser: The command requires the extension aks-preview. It will be installed first.
cli.azure.cli.core.extension.operations: Extension 'aks-preview' 0.5.7 is already installed.
cli.azure.cli.core.extension.operations: It will be updated if available.
urllib3.connectionpool: Starting new HTTPS connection (1): aka.ms:443
urllib3.connectionpool: https://aka.ms:443 "GET /azure-cli-extension-index-v1 HTTP/1.1" 301 0
urllib3.connectionpool: Starting new HTTPS connection (1): azcliextensionsync.blob.core.windows.net:443
urllib3.connectionpool: https://azcliextensionsync.blob.core.windows.net:443 "GET /index1/index.json HTTP/1.1" 200 873390
cli.azure.cli.core.extension._resolve: Candidates ['aks_preview-0.4.35-py2.py3-none-any.whl', 'aks_preview-0.4.36-py2.py3-none-any.whl', 'aks_preview-0.4.37-py2.py3-none-any.whl', 'aks_preview-0.4.38-py2.py3-none-any.whl', 'aks_preview-0.4.39-py2.py3-none-any.whl', 'aks_preview-0.4.40-py2.py3-none-any.whl', 'aks_preview-0.4.41-py2.py3-none-any.whl', 'aks_preview-0.4.42-py2.py3-none-any.whl', 'aks_preview-0.4.43-py2.py3-none-any.whl', 'aks_preview-0.4.44-py2.py3-none-any.whl', 'aks_p
review-0.4.45-py2.py3-none-any.whl', 'aks_preview-0.4.47-py2.py3-none-any.whl', 'aks_preview-0.4.49-py2.py3-none-any.whl', 'aks_preview-0.4.50-py2.py3-none-any.whl', 'aks_preview-0.4.51-py2.py3-none-any.whl', 'aks_preview-0.4.52-py2.py3-none-any.whl', 'aks_preview-0.4.53-py2.py3-none-any.whl', 'aks_preview-0.4.54-py2.py3-none-any.whl', 'aks_preview-0.4.55-py2.py3-none-any.whl', 'aks_preview-0.4.56-py2.py3-none-any.whl', 'aks_preview-0.4.57-py2.py3-none-any.whl', 'aks_preview-0.4.58-
py2.py3-none-any.whl', 'aks_preview-0.4.59-py2.py3-none-any.whl', 'aks_preview-0.4.60-py2.py3-none-any.whl', 'aks_preview-0.4.61-py2.py3-none-any.whl', 'aks_preview-0.4.62-py2.py3-none-any.whl', 'aks_preview-0.4.63-py2.py3-none-any.whl', 'aks_preview-0.4.64-py2.py3-none-any.whl', 'aks_preview-0.4.65-py2.py3-none-any.whl', 'aks_preview-0.4.66-py2.py3-none-any.whl', 'aks_preview-0.4.67-py2.py3-none-any.whl', 'aks_preview-0.4.68-py2.py3-none-any.whl', 'aks_preview-0.4.69-py2.py3-none-a
ny.whl', 'aks_preview-0.4.70-py2.py3-none-any.whl', 'aks_preview-0.4.71-py2.py3-none-any.whl', 'aks_preview-0.4.72-py2.py3-none-any.whl', 'aks_preview-0.4.73-py2.py3-none-any.whl', 'aks_preview-0.5.0-py2.py3-none-any.whl', 'aks_preview-0.5.1-py2.py3-none-any.whl', 'aks_preview-0.5.2-py2.py3-none-any.whl', 'aks_preview-0.5.3-py2.py3-none-any.whl', 'aks_preview-0.5.4-py2.py3-none-any.whl', 'aks_preview-0.5.5-py2.py3-none-any.whl', 'aks_preview-0.5.6-py2.py3-none-any.whl', 'aks_preview
-0.5.7-py2.py3-none-any.whl']
cli.azure.cli.core.extension._resolve: Candidates ['aks_preview-0.4.35-py2.py3-none-any.whl', 'aks_preview-0.4.36-py2.py3-none-any.whl', 'aks_preview-0.4.37-py2.py3-none-any.whl', 'aks_preview-0.4.38-py2.py3-none-any.whl', 'aks_preview-0.4.39-py2.py3-none-any.whl', 'aks_preview-0.4.40-py2.py3-none-any.whl', 'aks_preview-0.4.41-py2.py3-none-any.whl', 'aks_preview-0.4.42-py2.py3-none-any.whl', 'aks_preview-0.4.43-py2.py3-none-any.whl', 'aks_preview-0.4.44-py2.py3-none-any.whl', 'aks_p
review-0.4.45-py2.py3-none-any.whl', 'aks_preview-0.4.47-py2.py3-none-any.whl', 'aks_preview-0.4.49-py2.py3-none-any.whl', 'aks_preview-0.4.50-py2.py3-none-any.whl', 'aks_preview-0.4.51-py2.py3-none-any.whl', 'aks_preview-0.4.52-py2.py3-none-any.whl', 'aks_preview-0.4.53-py2.py3-none-any.whl', 'aks_preview-0.4.54-py2.py3-none-any.whl', 'aks_preview-0.4.55-py2.py3-none-any.whl', 'aks_preview-0.4.56-py2.py3-none-any.whl', 'aks_preview-0.4.57-py2.py3-none-any.whl', 'aks_preview-0.4.58-
py2.py3-none-any.whl', 'aks_preview-0.4.59-py2.py3-none-any.whl', 'aks_preview-0.4.60-py2.py3-none-any.whl', 'aks_preview-0.4.61-py2.py3-none-any.whl', 'aks_preview-0.4.62-py2.py3-none-any.whl', 'aks_preview-0.4.63-py2.py3-none-any.whl', 'aks_preview-0.4.64-py2.py3-none-any.whl', 'aks_preview-0.4.65-py2.py3-none-any.whl', 'aks_preview-0.4.66-py2.py3-none-any.whl', 'aks_preview-0.4.67-py2.py3-none-any.whl', 'aks_preview-0.4.68-py2.py3-none-any.whl', 'aks_preview-0.4.69-py2.py3-none-a
ny.whl', 'aks_preview-0.4.70-py2.py3-none-any.whl', 'aks_preview-0.4.71-py2.py3-none-any.whl', 'aks_preview-0.4.72-py2.py3-none-any.whl', 'aks_preview-0.4.73-py2.py3-none-any.whl', 'aks_preview-0.5.0-py2.py3-none-any.whl', 'aks_preview-0.5.1-py2.py3-none-any.whl', 'aks_preview-0.5.2-py2.py3-none-any.whl', 'aks_preview-0.5.3-py2.py3-none-any.whl', 'aks_preview-0.5.4-py2.py3-none-any.whl', 'aks_preview-0.5.5-py2.py3-none-any.whl', 'aks_preview-0.5.6-py2.py3-none-any.whl', 'aks_preview
-0.5.7-py2.py3-none-any.whl']
cli.azure.cli.core.extension._resolve: Candidates ['aks_preview-0.4.35-py2.py3-none-any.whl', 'aks_preview-0.4.36-py2.py3-none-any.whl', 'aks_preview-0.4.37-py2.py3-none-any.whl', 'aks_preview-0.4.38-py2.py3-none-any.whl', 'aks_preview-0.4.39-py2.py3-none-any.whl', 'aks_preview-0.4.40-py2.py3-none-any.whl', 'aks_preview-0.4.41-py2.py3-none-any.whl', 'aks_preview-0.4.42-py2.py3-none-any.whl', 'aks_preview-0.4.43-py2.py3-none-any.whl', 'aks_preview-0.4.44-py2.py3-none-any.whl', 'aks_p
review-0.4.45-py2.py3-none-any.whl', 'aks_preview-0.4.47-py2.py3-none-any.whl', 'aks_preview-0.4.49-py2.py3-none-any.whl', 'aks_preview-0.4.50-py2.py3-none-any.whl', 'aks_preview-0.4.51-py2.py3-none-any.whl', 'aks_preview-0.4.52-py2.py3-none-any.whl', 'aks_preview-0.4.53-py2.py3-none-any.whl', 'aks_preview-0.4.54-py2.py3-none-any.whl', 'aks_preview-0.4.55-py2.py3-none-any.whl', 'aks_preview-0.4.56-py2.py3-none-any.whl', 'aks_preview-0.4.57-py2.py3-none-any.whl', 'aks_preview-0.4.58-
py2.py3-none-any.whl', 'aks_preview-0.4.59-py2.py3-none-any.whl', 'aks_preview-0.4.60-py2.py3-none-any.whl', 'aks_preview-0.4.61-py2.py3-none-any.whl', 'aks_preview-0.4.62-py2.py3-none-any.whl', 'aks_preview-0.4.63-py2.py3-none-any.whl', 'aks_preview-0.4.64-py2.py3-none-any.whl', 'aks_preview-0.4.65-py2.py3-none-any.whl', 'aks_preview-0.4.66-py2.py3-none-any.whl', 'aks_preview-0.4.67-py2.py3-none-any.whl', 'aks_preview-0.4.68-py2.py3-none-any.whl', 'aks_preview-0.4.69-py2.py3-none-a
ny.whl', 'aks_preview-0.4.70-py2.py3-none-any.whl', 'aks_preview-0.4.71-py2.py3-none-any.whl', 'aks_preview-0.4.72-py2.py3-none-any.whl', 'aks_preview-0.4.73-py2.py3-none-any.whl', 'aks_preview-0.5.0-py2.py3-none-any.whl', 'aks_preview-0.5.1-py2.py3-none-any.whl', 'aks_preview-0.5.2-py2.py3-none-any.whl', 'aks_preview-0.5.3-py2.py3-none-any.whl', 'aks_preview-0.5.4-py2.py3-none-any.whl', 'aks_preview-0.5.5-py2.py3-none-any.whl', 'aks_preview-0.5.6-py2.py3-none-any.whl', 'aks_preview
-0.5.7-py2.py3-none-any.whl']
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.35-py2.py3-none-any.whl' as 0.4.35 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.36-py2.py3-none-any.whl' as 0.4.36 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.37-py2.py3-none-any.whl' as 0.4.37 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.38-py2.py3-none-any.whl' as 0.4.38 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.39-py2.py3-none-any.whl' as 0.4.39 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.40-py2.py3-none-any.whl' as 0.4.40 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.41-py2.py3-none-any.whl' as 0.4.41 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.42-py2.py3-none-any.whl' as 0.4.42 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.43-py2.py3-none-any.whl' as 0.4.43 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.44-py2.py3-none-any.whl' as 0.4.44 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.45-py2.py3-none-any.whl' as 0.4.45 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.47-py2.py3-none-any.whl' as 0.4.47 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.49-py2.py3-none-any.whl' as 0.4.49 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.50-py2.py3-none-any.whl' as 0.4.50 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.51-py2.py3-none-any.whl' as 0.4.51 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.52-py2.py3-none-any.whl' as 0.4.52 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.53-py2.py3-none-any.whl' as 0.4.53 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.54-py2.py3-none-any.whl' as 0.4.54 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.55-py2.py3-none-any.whl' as 0.4.55 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.56-py2.py3-none-any.whl' as 0.4.56 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.57-py2.py3-none-any.whl' as 0.4.57 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.58-py2.py3-none-any.whl' as 0.4.58 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.59-py2.py3-none-any.whl' as 0.4.59 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.60-py2.py3-none-any.whl' as 0.4.60 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.61-py2.py3-none-any.whl' as 0.4.61 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.62-py2.py3-none-any.whl' as 0.4.62 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.63-py2.py3-none-any.whl' as 0.4.63 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.64-py2.py3-none-any.whl' as 0.4.64 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.65-py2.py3-none-any.whl' as 0.4.65 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.66-py2.py3-none-any.whl' as 0.4.66 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.67-py2.py3-none-any.whl' as 0.4.67 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.68-py2.py3-none-any.whl' as 0.4.68 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.69-py2.py3-none-any.whl' as 0.4.69 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.70-py2.py3-none-any.whl' as 0.4.70 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.71-py2.py3-none-any.whl' as 0.4.71 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.72-py2.py3-none-any.whl' as 0.4.72 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.4.73-py2.py3-none-any.whl' as 0.4.73 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.0-py2.py3-none-any.whl' as 0.5.0 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.1-py2.py3-none-any.whl' as 0.5.1 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.2-py2.py3-none-any.whl' as 0.5.2 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.3-py2.py3-none-any.whl' as 0.5.3 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.4-py2.py3-none-any.whl' as 0.5.4 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.5-py2.py3-none-any.whl' as 0.5.5 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.6-py2.py3-none-any.whl' as 0.5.6 not greater than current version 0.5.7
cli.azure.cli.core.extension._resolve: Skipping 'aks_preview-0.5.7-py2.py3-none-any.whl' as 0.5.7 not greater than current version 0.5.7
cli.azure.cli.core.extension.operations: No suitable extensions found.
cli.azure.cli.core.extension.operations: No updates available for 'aks-preview'. Use --debug for more information.

route to appropriate team

@NeonOriginal you may be on a profile that does not support aks command. Please use the latest profile: az cloud set --name AzureCloud --profile latest

Thank you. Forgot I messed with that option after there was an issue our company was experiencing last week.


Manual connect during chain sync prevents channel from becoming active

Background
If a manual connection (lncli connect) to a peer with a channel is made after lnd has started but before it has caught up to the chain backend, the channel will remain inactive even after sync is complete. Other channels have connections established and become active automatically once chain sync is complete.
Your environment

0.4.2-beta commit=b5a228808b0446d6758a23e24d6c686aab9936fc
Linux instance-1 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux
bitcoind 0.16.1

Steps to reproduce

Open a channel in lnd
Shutdown lnd and let it stay offline for at least a few hours.
Start lnd, as soon as the grpc server becomes available (before chain sync is complete), run lncli connect to the peer node with which you made the channel in step 1.
The channel will remain inactive and stay that way even after the chain sync is complete.

I started up an lnd instance that had been offline for some time When coming online, it needed to catch up to the latest blocks. During this time, lnd had no active channels and no connections. I was impatient and wanted to try to make a payment right away, so I manually connected to a peer I had a channel with and tried to pay that peer. The payment failed because the channel was still inactive. listpeers showed my connection to that peer.
I waited for the chain sync to complete, and when it did it connected to all peers with which I had channels, and all those channels became active. However, the channel with the peer with whom I had manually connected to earlier remained inactive and stayed that way. Payment to the peer would fail. Attempts to reconnect/disconnect to the peer failed as well:
lncli disconnect 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115
[lncli] rpc error: code = Unknown desc = cannot disconnect from peer(026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115), all active channels with the peer need to be closed first

lncli connect 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115@<IP_ADDRESS>:9735
[lncli] rpc error: code = Unknown desc = already connected to peer: <IP_ADDRESS>:9735

Restarting lnd and waiting for the connections to happen automatically resolved this issue and the channel above became active.
From looking through the code and peer.go a bit, it looks like the cause might be that existing channels are only activated when a connection to a peer is established. If the channel can't become active during chain sync, then it remains inactive and since the connection is not reestablished after chain sync, it stays that way.
Expected behaviour
After chain sync on startup, channels to peers with which we already have connections should become active. Alternatively, connections should not be allowed during startup chain sync.
Actual behaviour
Channels to peers with which we already have connections do not become active on completion of startup chain sync.

If a manual connection (lncli connect) to a peer with a channel is made after lnd has started but before it has caught up to the chain backend, the channel will remain inactive even after sync is complete.

You shouldn't be able to to a manual connection, as the server isn't started up before the initial chain is actually synced. Peer connections won't succeed as well as the listening server hasn't been started up as well. Channels are only added to switch once a peer is connected, as before that it doesn't actually matter.
On being active: a channel is only active once the channel is "eligible to forward". This means connected, but also once they've sent the FundingLocked message. If they haven't sent this (for w/e reason), then the channel won't become active.

What did the logs w/ this peer show at the time as well?

Here's the logs from the rescan, you can see that the gRPC server started listening while the rescan was going on. I figure that's why I was able to do lncli connect. The logs don't show the manual connection happening, I figure my logging level isn't low enough.
2018-06-19 01:48:06.861 [INF] LNWL: Started rescan from block<PHONE_NUMBER>0000000038ee6ab784d62ae7654900960f2e26ef689fe4751ae144 (height 528059) for 141 addresses
2018-06-19 01:48:07.099 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2018-06-19 01:48:07.100 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2018-06-19 01:48:07.103 [INF] LNWL: Starting rescan from block<PHONE_NUMBER>0000000038ee6ab784d62ae7654900960f2e26ef689fe4751ae144
2018-06-19 01:48:07.801 [INF] LTND: Waiting for chain backend to finish sync, start_height=528149
2018-06-19 02:01:58.018 [INF] LNWL: Rescan finished at 528149<PHONE_NUMBER>0000000009381e7024d7385c514dc1f1c662760b66df532b5a9867)
2018-06-19 02:01:58.036 [INF] LNWL: Catching up block hashes to height 528149, this might take a while
2018-06-19 02:01:58.038 [INF] LNWL: Done catching up block hashes
2018-06-19 02:01:58.039 [INF] LNWL: Finished rescan for 141 addresses (synced to block<PHONE_NUMBER>0000000009381e7024d7385c514dc1f1c662760b66df532b5a9867, height 528149)
2018-06-19 02:01:59.090 [INF] LTND: Chain backend is fully synced (end_height=528149)!

Regarding FundingLocked, I found this:
2018-06-19 02:02:05.349 [ERR] SRVR: unable to send message to 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115, peer is not connected
2018-06-19 02:02:05.350 [WRN] FNDG: unable to send fundingLocked to peer 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115: peer is not connected. Will retry when online

So it's saying I'm not connected to peer 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115, however I did have a connection according to listpeers. You can also see from my first post that if I tried to connect to that peer again manually, I got a message saying I was already connected:
lncli connect 026a9cb86ff60b1f2eb8cc44068451266b8ad54a935db72762ca3484f9d73c3115@<IP_ADDRESS>:9735
[lncli] rpc error: code = Unknown desc = already connected to peer: <IP_ADDRESS>:9735

Yes the peer wasn't connected, so we weren't able to send the funding locked message to the remote peer.
If we connect, but then the peer disconnects before funding locked is exchanged, then there may have been a gap where we were connected, but the remote peer wasn't processing this message, so we couldn't continue w/ the process of the channel becoming active.
Until both sides send/recv the funding locked message. The channel cannot become active.

Your issue is that the remote peer isn't sending the channel sync message for some reason. Logs show that lnd is doing everything correctly. If the remote peer isn't responsive, then you'll have to close out the channel. When you try to close cooperatively, it disconnects.

Executing the following command:
lncli closechannel f5e7d14cf065071d7502a07bc102446e9c180ec70847e3cc61ef27826cc4adac --output_index 1 --force --sat_per_byte 150

Results in lncli blocking indefinitely, and the following on the log:
2018-07-17 08:31:32.396 [INF] HSWC: Removing channel link with ChannelID(acadc46c8227ef61cce34708c70e189c6e4402c17ba002751d0765f04cd1e7f4)
2018-07-17 08:31:32.396 [INF] CNCT: Attempting to force close ChannelPoint(f5e7d14cf065071d7502a07bc102446e9c180ec70847e3cc61ef27826cc4adac:1)

But no more information regarding the progress. I don't see any evidence that a commitment TX was sent to the p2p network.


problem library ruby 3

WSL2
UNBUNTU 22.04
Stderr:
Error: Could not initialize global default settings: The SortedSet class has been extracted from the set library.You must use the sorted_set gem or other alternatives.
Exit code: 1

This repo is clearly marked as unsupported and seeking a maintainer, and hasn't had a commit in 7 years. I have no idea if it even still works or is still relevant, but I'm not the least bit surprised that it has issues with Ruby 3.
I'll gladly accept a pull request with a confirmed fix for this, but otherwise it's just going to stay open.


Fix handling of existing parent in save_inventory and nil hash

In this PR:

fix persistency of has_one relationship when parent already exists
support nil hash in save_inventory_single

More information in the commit messages.

cc @Fryguy @blomquisg @chessbyte I think that at least one change is fixing a bug, can you quickly check if that's the case? Thanks.

@kbrock was looking into this as well.  I think his approach might be more accurate, but I think I need to understand what is being fix and what is being affected better.

This patch transforms "parent.type=" into "parent.update_attributes!" to automatically persist the new relationship.

We intentionally delay persisting things until the last minute to keep the number of database changes to a minimum...I'm concerned this introduces more database calls into the refresh when not necessary.

This patch adds the support for a nil hash in save_inventory_single, which is useful to destroy a has_one relationship when the child has been removed.

Let's discuss with @kbrock over in #1376

@simon3z For the second commit in particular, you'd be interested in https://github.com/ManageIQ/manageiq/pull/1376#issuecomment-77620135

@simon3z thanks. My momentum slowed down on this one. Please check out our previous conversation and see if we can get this in

@simon3z For the second commit in particular, you'd be interested in #1376 (comment)

@Fryguy @kbrock this patch is respecting https://github.com/ManageIQ/manageiq/pull/1376#issuecomment-77620135 for has_one: if e.g. :hardware => nil then delete

We intentionally delay persisting things until the last minute to keep the number of database changes to a minimum...I'm concerned this introduces more database calls into the refresh when not necessary.

Is there a way so that I can mark the parent as being "modified" (requires saving).

@simon3z Great thread. We had looked into using :autosave => true on the association but we speculated it would be too much of a performance hit. And it may introduce unintended consequences.
I want to rework that to use AR objects instead of id references. It would get the rest of the saves out of there. But yes, the code gets tricky because in the current configuration AR will auto save a new association, but not automatically save a change or delete.
OTOH, @Fryguy wants to use a builder and completely revamp that code.

@kbrock using :autosave => true would be indeed overkilling.
Anyway @Fryguy @kbrock overall my solution (current PR) would not impact performance because the new save affects only the single case of the initial creation of the relationship, it's respecting https://github.com/ManageIQ/manageiq/pull/1376#issuecomment-77620135 and more over it's improving correctness fixing a bug.

Ping @Fryguy, this is important for us because it's blocking #2975

Ping @Fryguy

@Fryguy @blomquisg Please review

Yeah, I'm testing other scenarios.  Since it affects a core component and is cross provider I want to verify a number of things.

This change highlights something we really need in our refresher tests:  We need to be able to test providers at different states.  Our current refresher tests test an environment that's in one state and verifies that state.
We need to be able to test an environment at a state, then test the same environment after it's changed state to make sure things like this (deleting a "has_one" relationship) works as expected.
I can't see holding up this PR for that, but something that needs to be on the backlog for testing.

@blomquisg Yeah, we've wanted that for a while, but it is REALLY hard to do.  Particularly if you have to re-record the cassettes.  The best way to do that is to do like we did with openstack where we have a script that can recreate an environment from scratch, then record a refresh from that, then modify the environment in various ways, and then record again.  It's really painful to do the latter though.

@Fryguy yeah we're experiencing the same problem with kubernetes/openshift as well. Even though it's slightly easier to reproduce the environment.

Assigning the association in the parent is there to get around this. It is also
I moved around a bunch of code in that method, but that code is basically unchanged.

Yea, at first glance save_inventory and save_inventory_with_savekey look almost identical
But if you look, only 2 of the 6 lines of code are the same. One week @tenderlove and I both put in a PR to simplify the conditionals in this 6 line method.
Thanks for diving in. We obviously have more changes to make here (e.g.: #2190)

@kbrock commented on May 29, 2015, 3:56 PM EDT
Not sure if the solution is to force more saves (e.g.: update_attributes!) or to introduce a more heavy handed saving mechanism to the association.
However, I am surprised to see this suggestion from @Fryguy as I know he has the dream of not saving anything to the db until the very end with an ems.save.

I think you're referring to:

@Fryguy added a note on May 29, 2015, 12:35 PM EDT
This one has been having me scratch my head...I think the following is much clearer and is the same...
if found.nil?
  found = parent.send("create_#{type}!", hash.except(:id))
else
  found.update_attributes!(hash.except(:id, :type))
end

That update_attributes! is an existing line in the else condition that's not part of this PR.  I think @Fryguy was highlighting the if block and incidentally including the else block.

@Fryguy @kbrock @blomquisg I addressed only comment https://github.com/ManageIQ/manageiq/pull/2976#discussion_r31340826 hash.blank? as IIUC the rest is still under discussion and it seems that update_attributes! is the only working solution ATM ("create_#{type}!" not working).

"create_#{type}!" not working o_O  That's really surprising to me.

"create_#{type}!" not working o_O That's really surprising to me.

I thought it was part of your findings in https://github.com/ManageIQ/manageiq/pull/2976#discussion_r31352424

@Fryguy let me know if there's anything else to address.

@blomquisg @Fryguy it seems that travis got stuck again. Can you restart the tests? Thanks.

@simon3z restarted. For future reference, you can close and reopen the pull request to make Travis restart. I'm working on a feature to the bot to detect and auto restart stalled builds.  I hope to get it live soon so we don't have to deal with the delay of stalled builds.

@Fryguy can you review/merge?

@simon3z In follow up to my long comment and you reply: ...right...but the current code does the second thing.  So, what is the specific thing you are trying to save that is not working?
I really would like to understand why this piece only fails in your case, because it works fine for everything else.

@Fryguy, no the current code is not doing the second thing if you have a ConfiguredSystem that was already saved (previous refresh) without any s.computer_system.
On the other hand if the ConfiguredSystem is a new entry (never saved before) it works correctly (real second case).

@Fryguy ping? This is holding up the important #2975

@Fryguy @blomquisg Please review


Improve test coverage

There are currently some minimal unit tests for the detect, build, release and run commands but it would definitely be good it improve the unit test coverage!

If you're here for hacktoberfest and have any questions, get in touch on our fabric-hacktoberfest Discord channel!

The testing is in much better now that #77 and #80 have been merged


UI Context menu should adapt to limited viewport space

If context menu has insufficient space to display all menu options, it must either display a scrollbar or wrap menu options .
Currently, menu disappears offscreen.

Haven't been able to reproduce this lately


MultiMC crash on loading screen

I installed the latest stable version of OpenTerrainGenerator and I got this crash. Full logs I am using the MultiMC launcher

Thanks for the report, have added this to the new bugs thread here https://www.reddit.com/r/openterraingen/comments/67uzha/mod_compatibility_bugs_report_them_here/

This should be fixed with v18, OTG now registers dimensions when it is creating them instead of reserving 100 dimensions at app start. A dev version of v18 is available here: https://cdn.discordapp.com/attachments/307111022257373185/313254639841705985/OpenTerrainGenerator-1.10.2-v18-2.jar
Please give it a try and tell me if that fixes the problems.
*A few notes for this version:
Should fix a whole bunch of dimension related bugs, mostly when creating/deleting dimensions and relogging and/or restarting the server. May also solve some biome registration related bugs when used with other mods that add biomes. Portal mechanics have been overhauled, dimensions should work much better now and each world can have its own portal frame materials defined in the worldconfig.
If you test the release and use the Dimensions pre-set or create/delete your own dimensions using /otg dim -l, /otg dim -c and /otg dim -d you'll want to change the portal material for each dimension in the world config. Otherwise they will all default to quartz and you'll only be able to visit the first two dimensions via a quartz portal.

IT WORKS!!,

Awesome, thanks for the report :D

By the way, the official v18 is now available here: https://minecraft.curseforge.com/projects/open-terrain-generator/files/2419946. It contains a few more fixes than the one you have.


Support TruffleRuby

Specs pass on rc6, can make it official once truffleruby-1.0.0 is released.

Supported as of 780ebef (v6.0.0)


Modal Close not firing LifeCycle Events on tab

Ionic version:  (check one with "x")
[ ] 1.x
[X] 2.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I have a tab set as root. When I push a modal over it and use navPop / dismiss it closes the modal but it doesn't fires the ionViewWillEnter event of Tab due to which the tab data is not reloaded.
Expected behavior:
Expecting ionViewWillEnter to fire so as to take the decision to reload data.

This is the expected behavior, a modal is like an alert, or an actionsheet, it does not fire lifecycle events in the main navigation stack.
Use onWillDismiss() or onDidDismiss() to update your data:
https://github.com/driftyco/ionic/blob/master/src/components/modal/test/basic/app-module.ts#L69-L84


Graph PB File

If possible can you please upload the Graph.pb file associated with this model ? And if not can you tell me how to create it from the checkpoints you have provided ?
And thank you so much for uploading these !

@samuel-davis
Sure!
I will upload the graph.pbtxt file in a day.
You would be able to generate the .pb file from it, if you need the compressed representation of the graph.

Uploaded!
I think this commit closes the issue. If there's anything else, feel free to re-open this or open a new issue.

Thanks definitely helped me out a ton.

I'm glad it did. Let me know if you need anything else!


qreader does not focus

Hey,
i have implemented your library into a small project of mine. The problem i am facing is that the camera does not focus automatically and therefor i never get a scan result. Any ideas on how i can fix that?
Thanks and greetings
Leo

@LeoUnglaub thats a really good catch.
I will give an option to enable autofocus in my library.
Should update my code tonight 😄

Thats awesome!
Big thanks and greetings from Vienna!
Leo

@LeoUnglaub it was a quick fix, so I updated my code. Have pushed the new version to maven central, should be available in a few hours.
The new version is 1.0.1

Hey,
thanks for fixing that issue. But sadly i still cannot scan anything on my phone. I use your code from the readme. I gave the app permissions to use the camera but i still dont get the value from the library. Is there anything else i have to do? installing the Google vision library on my phone? Or something else?
Thanks and greetings
Leo

I think i might found the problem:
Exception thrown from receiver.
android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
 at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:6566)
 at android.view.ViewRootImpl.invalidateChildInParent(ViewRootImpl.java:946)
 at android.view.ViewGroup.invalidateChild(ViewGroup.java:5081)
 at android.view.View.invalidateInternal(View.java:12723)
 at android.view.View.invalidate(View.java:12659)
 at android.widget.TextView.invalidateRegion(TextView.java:5185)
 at android.widget.TextView.invalidateCursor(TextView.java:5128)
 at android.widget.TextView.spanChange(TextView.java:8085)
 at android.widget.TextView$ChangeWatcher.onSpanAdded(TextView.java:10181)
 at android.text.SpannableStringBuilder.sendSpanAdded(SpannableStringBuilder.java:1053)
 at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:759)
 at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:658)
 at android.text.Selection.setSelection(Selection.java:76)
 at android.text.Selection.setSelection(Selection.java:87)
 at android.text.method.ArrowKeyMovementMethod.initialize(ArrowKeyMovementMethod.java:325)
 at android.widget.TextView.setText(TextView.java:4335)
 at android.widget.TextView.setText(TextView.java:4204)
 at android.widget.EditText.setText(EditText.java:84)
 at android.widget.TextView.setText(TextView.java:4179)
 at com.example.simpletest.simpletest.MainActivity$1.onDetected(MainActivity.java:35)
 at github.nisrulz.qreader.QREader$2.receiveDetections(QREader.java:115)
 at com.google.android.gms.vision.Detector.receiveFrame(Unknown Source)
 at com.google.android.gms.vision.CameraSource$zzb.run(Unknown Source)
 at java.lang.Thread.run(Thread.java:818)

@LeoUnglaub yes the result returned is on a different thread. You need to post the data. Check the sample app in the repo.


Fix #476

Hello ! :smile:
I think I have solved the issue #476.
However, I am not sure that ignoring the error is the right solution. I have the impression that the sentinel.catch() earlier in the code makes it safe to do so, but am I wrong?
Thank you very much in advance!

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

Sorry for the forced push, I made a mistake in the commit message...


WIP: url stlib module for parsing url struct

Pull request
Description
This pull request includes new functionality for working with URLs in the Tremor.
The following functions have been added:

url::construct: This function allows for the construction of a URL from its individual components, such as scheme, host, path, query, and fragment.

url::set_scheme: This function allows for the changing of the scheme of a given URL.

url::set_host: This function allows for the changing of the host of a given URL.

url::set_path: This function allows for the changing of the path of a given URL.

url::set_query: This function allows for the changing of the query of a given URL.

url::set_fragment: This function allows for the changing of the fragment of a given URL.

These functions are implemented using the url crate. I've attached tests but i am not able to properly verify.

Related

RFC
Related Issues: fixes #2181
Related docs PR

Checklist

[ ] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[ ] The code is tested
[ ] Use of unsafe code is reasoned about in a comment
[ ] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[ ] The performance impact of the change is measured (see below)

Performance

Heya nice! that was super quick
A few suggestions:

it'd be nice to have a deconstruct or parse function that returns a struct with fields like

{
 "scheme": "https",
 "path": "/path",
...

I love the set_* functions!  I didn't even think of that but it's sure very helpful :) it would be nice to have the opposite get_*
it'd be nice to have the option to construct as well as parse, that takes the struct and creates a string (watch out for urlencoding ;) )
the set_query / construct function would be nice to have the option to take a map as well as a string for the query to build a query string from it :)

@0xquark are you still working on this?

Hi @Licenser!  I'm swamped right now with my work, so I couldn't move forward with this PR.
Could you please assign another person to handle it?
Apologies and Thanks!

Closing this as there is no time to finish the PR


Revert "Support windows (#128)"

This reverts commit 11b3564ce0bd146db92ae968adfd2fd888a85785.
Crossterm backend does not support MacOS + zsh yet

That's strange. It should have full support for both of those.


Error handling api design doesn't allow determining whetger getAttribute operation failed

Let's say we have code like this:
client.getAttribute(mbean, attrib, data => {
      ...do something with the data..
});

The way the api is designed there seems to be no way to change this code so that it can properly handle errors arising from that operation.
Yes, we can do something like this:
client.on('error', (error) => ...handle error..);

But... the error handler can not know what operation caused the error. Even if we use client.on in combination with client.of to only attach error handlers for the duration of an operation, we will still have issues to accurately determine which operation caused the error when more than one operation is executed in parallel.
So, to make story short, the api should really allow for something like this:
client.getAttribute(mbean, attrib, (data, err) => {
    if (error) {
      ..handle error...
   } else {
     ..do something with the data..
   }
});

Note: if the api was designed like this from the start, I would probably put the 'err' parameter before the 'data' parameter as that seems to be the prevailing convention for asynchronous callbacks in nodejs libraries.
But seeing as the api was not designed to work like this initially, putting the 'err' parameter second means that it will not break existing code that assumes the first parameter is the data.

Ah I discovered there is already another bug ticket that seems to cover this problem:
https://github.com/zuazo/node-jmx/issues/8
I'll close this ticket then.


Move symbol to doesn't work in typed context

VSCode info
Version: 1.86.2
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:41:37.860Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-0.deb12.4-amd64
Python extension info
Name: Python
Id: ms-python.python
Version: 2024.0.1

Dupe of https://github.com/microsoft/pylance-release/issues/5449. Please try the latest VS Code Insiders build. It's fixed there.

Still doesn't work after update. I would like to emphasize that Move symbol to ... doesn't work with typed variables only. It works correctly with untyped variables, as it was shown in the gif in the first post.
VSCode info
Version: 1.87.0
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:16.599Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-0.deb12.4-amd64
Python extension info
Name: Pylance
Id: ms-python.vscode-pylance
Version: 2024.2.3

@debonte

This issue has been fixed in prerelease version 2024.3.100, which we've just released. You can find the changelog here: CHANGELOG.md


support loading op_config

Each OP in process accepts a new op_config argument to load configurations from another YAML file.
Command line also allows OP-specific configuration, e.g., python tools/process_data.py --config configs/demo/process.yaml --language_id_score_filter op_conf.yaml --language_id_score_filter.min_score 0.6

The precedence for overrides is: command-line args from left to right > args in main YMAL >  args in sub-op YAML

Since similar functionality prepare_side_configs have been merged, close this pr for archival reference.


[Feature]: Create Email templates and connect them to the new email system

Description
Thanks to @yasinelabe , We now have email system setup but we don't have any email templates. Can someone create a folder for all the email templates, programmatically get the user data and connect to the new email sending system.
For example, We need "Welcome" email when someone sign up or "Forgot password" email (You can setup the template, we don't have the functionality for person to reset their password now).
Suggested Solution
Look into https://react.email/
Alternatives
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Contribution Guidelines

[X] I agree to follow this project's Contribution Guidelines.

Anyone who can design the UI of these components

forget password, email template
welcome message, email template
verify email, email template

refer to those reactmail examples https://demo.react.email/preview/stripe-welcome

@duraanali igu assign garee

@yasinelabe  are the Email Templates ready yet?

I got unassigned bro @mahamedmahad
You can work on it


Add Orochi Network's proposal for research and development MPC ECDSA

Project Abstract
Orosign is a self-managing custodial Mobile App base on MPC and ECDSA to provide high security in digital assets/identity management that suits all demands of Web3.
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[x] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @chiro-hiro:matrix.org (change the homeserver if you use a different one)

Hi @keeganquigley, the first part of our proposal moved here. After we complete the first part, I will provide the second part.

Thanks for the changes @chiro-hiro in addition to my minor corrections above, a few more questions:

Can you explain a bit more about what questions you are looking to answer as part of the research milestone? And integrate this into the deliverables? Currently the M1 delivery tables seem a bit vague.
With the Orosign app, are the MPC key shares stored on the physical device? I’ve read that signing a transaction needs direct access to the key shares, which could expose information from the device and render it vulnerable to hacks, creating a possible attack vector.
Will you look into other attack vectors as part of your research?
Can you elaborate on the data correctness section of your docs? What do you mean when you say that all data pipelines are stored in a black box?

Thanks!

Hi @keeganquigley, here is my answers, I will add to the proposal as well.

Can you explain a bit more about what questions you are looking to answer as part of the research milestone? And integrate this into the deliverables? Currently the M1 delivery tables seem a bit vague.

In this milestone, our team use cryptography to build a bridge from Digital Signature Algorithm (DSA especially ECDSA, EdDSA, Schnorr Signature) to Multi-Party Computation (MPC) allow the signing process to be performed without actual private key. There are 3 DSAs were used by Polkadot: secp256k1, ed25519, sr25519. Before we can build a MPC based DSA, we need to research the algorithm and figure out how we could fit MPC into it. You may notice that each curve have different parameters and different field, after the research we can specify how MPC should be implement without harm its security.

With the Orosign app, are the MPC key shares stored on the physical device? I’ve read that signing a transaction needs direct access to the key shares, which could expose information from the device and render it vulnerable to hacks, creating a possible attack vector.

We designed a threshold signature that required 3/5 to perform, here is how shares were distributed:

2 share on mobile device
1 backup share of users
2 share hold by Orochi Network server

If hacker get in to user's device he need to hack Orochi Network's server as well to collect enough share to perform the MPC. In this case the risk to be hacked still lower than other ordinary crypto wallet  since the ordinary crypto wallet access to private key directly.

Will you look into other attack vectors as part of your research?

Will do, I think it's nice to have.

Can you elaborate on the data correctness section of your docs? What do you mean when you say that all data pipelines are stored in a black box?

Right now all data pipelines are on centralized cloud services.
Thanks.

Hi @Noc2 Thank for your feedback, I will do check.

Something to be aware of is that we usually don't fund the initial research of teams to look into specific details of Polkadot, especially if they have their own business model. So your first milestone might be controversial for the team and you should try to point out how this is useful for everyone and if you have done upfront research on the topic already.

This research part is help other team understand our construction and trade-off in the implementation, any team can pick up our research and do the implement themselves, beside ed25519 and sr25519 aren't popular out there among existing blockchains. I hope our project could bring the security of Web3 for all retail users.

Thanks for the answers @chiro-hiro much appreciated. I am seeing that the website still doesn't work as David mentioned, are you planning to update this?

Could you tell me which link?, I have no idea which one.

@chiro-hiro yep its http://www.orochi.network/
I remember it did work a couple weeks ago when I initially looked at your application.

Thanks for the update here. In this case, I think you should only focus on the first milestone. I guess you don't know the exact implementation until you have researched it. Furthermore, one concern here I would have as a user is that I rely entirely on your solution. You control the app as well as 2 out of 5 keys by default, and Orosign doesn't seem to be open source. Correct me if I'm wrong. Additionally, could you please point out any previous relevant work that you have done and/or audits?

It's 3/5 to perform the transaction. The fact is, we can design tho make Orochi Network control 1 share instead of two shares. User will hold majority of shares in their device.
In this proposal, we supposed to implement an open-sourced crate in Rust (can be compiled to wasm) allow other team to reuse if they want to build a MPC solution for Polkadot. This grant is just focus on R&D on MPC DSA (ECDSA, EdDSA), it isn't include Orosign that's why we wasn't open-source it.
Here is our previous work in ERVRF https://github.com/orochi-network/orochimaru/tree/main/libecvrf
We do research in DKG and MPC ECDSA (secp256k1) https://docs.orochi.network/dkg/dkg-construction/dkg-construction.html. There is an technical report I could share via email. We want to expand to support ed25519 and sr25519. Just to make it clear, everything was implemented by consuming Web3 Foundation grant will be licensed under Apache-2.0 and C00.

Thanks for the update @chiro-hiro and sorry for the delay. So if I understand correctly, this grant is completely independent of Orosign and the R&D on the curves would benefit all substrate MPC wallet developers, is that correct?
I don't think that would be an issue policy-wise, but still might be worth mentioning that our guidelines state that not only must the code/research be open-sourced, but "also must not rely on closed-source software for full functionality". Just want to make sure we are on the same page here.
Regarding David's previous comment, I'm assuming this means you aren't willing to reduce the scope?

Since the proposed research includes security considerations, I will also ping my colleague @bhargavbh who has more of an expertise in the area of security. If he has time, perhaps he can also comment on the usefulness of the research for the different curves.

Hi @keeganquigley, thanks for your response.

So if I understand correctly, this grant is completely independent of Orosign and the R&D on the curves would benefit all substrate MPC wallet developers, is that correct?

Yes, this research benefit the Polkadot ecosystem and all developers who aimed to build MPC wallet solution for Polkadot.

What questions are you looking to find answers to?

In this milestone, our team use cryptography to build a bridge from Digital Signature Algorithm (DSA especially ECDSA, EdDSA, Schnorr Signature) to Multi-Party Computation (MPC) allow the signing process to be performed without actual private key. There are 3 DSAs were used by Polkadot: secp256k1, ed25519, sr25519. Before we can build a MPC based DSA, we need to research the algorithm and figure out how we could fit MPC into it. You may notice that each curve have different parameters and different field, after the research we can specify how MPC should be implement without harm its security.

@chiro-hiro, just to ping you here again. Would you be willing to reduce the scope to just the first milestone?

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

Hi @keeganquigley @Noc2,
I changed the proposal to match your request, please review our proposal.

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

@chiro-hiro could you please sign the terms (again)? I will merge the application once this is done.

Hi @Noc2, sorry for being late. I signed please check!.

Perfect. Thanks. I will merge the application.

@chiro-hiro, the postal address in the invoice does not match the one in the grant application. Could you modify one to match the other?

Hi @semuelle, I'm aware of this issue and updated both the invoice  address and payment address. Please check the latest invoice. More details can be found here https://github.com/w3f/Grant-Milestone-Delivery/pull/1007


Wrap Rust service errors with MUI Alert

Summary by CodeRabbit

New Features

Enhanced error message display in the Settings Manager for improved visibility and user experience.
Introduced <Alert> components to present error and success messages distinctly.

Bug Fixes

Resolved issues with the previous error message presentation that lacked clarity.

@coderabbitai, can you please validate the .coderabbit.yaml file for me?
# Specify the paths to include or exclude from the review
reviews:
  path_filters:
    include:
      - "**/*" # Include all files
    exclude: []

# Set language preferences (optional)
language: en-US

You mentioned: Validation error: Expected array, received object at "reviews.path_filters"

@coderabbitai, will you please look at this commit and tell me if it's correct or not?
https://github.com/jzombie/etf-matcher/pull/91/commits/b7eaa916b51f53770fb4c0428dc0d3c19bb120b3

@coderabbitai, I went ahead and removed it for now.  I haven't studied the schema yet, and assume the defaults are good enough at this point.  https://github.com/jzombie/etf-matcher/pull/91/commits/202e249bef8edd7ae553226ac200ee740da4dc30

@coderabbitai, this is a pretty simple PR.  Do you approve?

@coderabbitai, you mentioned earlier that you skipped the review.  I assume this is due to the problematic YAML file that was in place.  I'd like you to explicitly review all PRs.


CloudFormation error.

I'm getting the following error from cloud formation.
This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.
 ```

I was following: http://scaleio-framework.readthedocs.io/en/latest/user-guide/demo/

@depohmel can you give me a bit more info to help me and @dvonthenen debug this issue for you? I also want to verify you are using the US West N. California region.
I just ran it following the directions as laid out and all resources came up and were deployed as expected.

Hi @kacole2, yes i'm using US West N. California
So I was following the guide (thru ui part)
I uploaded  http://scaleio-framework.readthedocs.io/en/latest/user-guide/Framework_Testing_Cluster_RHEL7.json and clicked Create.
Everything was fine until instances creation.
Looks it failing to use AMIs form your account.
11:38:03 UTC-0800 | DELETE_COMPLETE | AWS::EC2::Instance | MesosAgent1 |
-- | -- | -- | -- | --
  | 11:37:43 UTC-0800 | ROLLBACK_IN_PROGRESS | AWS::CloudFormation::Stack | ScaleIO-Test | The following resource(s) failed to create: [ScaleIONode1, ScaleIONode2, MesosAgent2, MesosMaster, MesosAgent1]. . Rollback requested by user.
  | 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | ScaleIONode1 | This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.
  | 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosAgent2 | This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.
  | 11:37:42 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | ScaleIONode2 | This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.
  | 11:37:41 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosMaster | This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.
  | 11:37:41 UTC-0800 | CREATE_FAILED | AWS::EC2::Instance | MesosAgent1 | This account is currently blocked and not recognized as a valid account. Please contact<EMAIL_ADDRESS>if you have questions.

@depohmel Assuming it's trying to place it in us-west-1 because that seems to work for me. I just deployed it again without any issue
Here are the AMIs in use.
ami-64174404
ami-d51447b5
ami-65174405
ami-c21a4ba2
ami-441a4b24
ami-15184975
You can go to your EC2 console, click on AMIs, then hit the drop down for public images and you should see them available to you.


[Issue 5618] [docs]Correct python example

Fixes #5618
Motivation
The python example is not correct.
Modifications

Correct the python example.
Correct two link issues.

@tuteng @candlerb Shall we remove

This contents of the file https://github.com/apache/pulsar/blob/master/site2/website/versioned_docs/version-2.4.1/functions-develop.md also seem to need updating.

@tuteng Thanks for your reminder. If the content in this PR is correct, i'll update the one in version 2.4.1.

run java8 tests


Fix bug which is it doesn't raise exception if resource is not found

Fixed https://github.com/CanCanCommunity/cancancan/issues/456

Please look at my comment: https://github.com/CanCanCommunity/cancancan/issues/456#issuecomment-346081557 I think I misinterpreted partially your PR while reviewing it

@coorasse  Thanks for comments. I updated this PR. Could you review when you have time ❓
Also, I changed one test case on https://github.com/CanCanCommunity/cancancan/pull/461/commits/5c9d21df8c18e1befaa3699e72032cc04eafa841.
Is my understanding correct ❓

Following @terryyin comment (https://github.com/CanCanCommunity/cancancan/commit/8fc2a2dbefc542749650da6b957335e8075b34a3#commitcomment-25775734) we have a regression at the moment. I am restoring the old behaviour now through another PR and then we can look at a refactoring which would deprecate the existing behaviour and therefore fall into a major release

could you please check your PR and update it against the current develop branch? Thanks

The dynamic finders with ! is still supported in Rails 5 (http://edgeguides.rubyonrails.org/active_record_querying.html#dynamic-finders). Perhaps there's no need to change this to use "find_by!" now, because it still changes the current behaviour (people might have their dynamic finder override).

@terryyin Thanks for advice 😃
@coorasse I confirmed latest version 2.1.2 is released. I'll close it. Thanks for releasing.

Thanks!
Great work, BTW.

On 23 Nov 2017, at 11:02 AM, Masahiro Saito<EMAIL_ADDRESS>wrote:
@terryyin https://github.com/terryyin Thanks for advice 😃
@coorasse https://github.com/coorasse I confirmed latest version 2.1.2 is released. I'll close it. Thanks for releasing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/CanCanCommunity/cancancan/pull/461#issuecomment-346522967, or mute the thread https://github.com/notifications/unsubscribe-auth/AAwJYsh_SqqRHmBnu4SNEJtleYa4jr9dks5s5OBSgaJpZM4Qk3q4.

Thanks @coorasse for taking care of this


Add app notification sample

Issue type
sample request
Which version of the app?
WinUI 3 Gallery
Description
No response
Screenshots
No response
Windows version
No response
Additional context
No response

Is App notification a WASDK feature or WinUI3 controls feature? Should it be included in WinUI Gallery?


Cant find Pokemon Special Episodes link?

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.11.15. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.11.15

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

I just have some question about downloading pokemon episodes on pokemon.com
I can download regular episodes, but i cant download the special episodes (origins & generations episodes)
Unlike regular episodes that has its own webpage, these special episodes directly opens a stream/video window on the episode list.
How can i find the specific webpage for these episodes so we can download it?
thanks and have a nice day...

Not sure what's a "special episode". Could you give steps for how to get to a special episode? Better with screenshots.


Initial PR

This adds/adapts the patrols workflow from here into its own releasable repository.
TODO:

[x] Release ecoscope-workflows-core and ecoscope-workflows-ext-ecoscope to prefix.dev and pin them here
[x] Finish translating pixi.toml management tasks for the current repo layout
[x] Actually compile patrols into this repo
[ ] Add CI to pixi run docker-build on pushes to main and deploy and register the build container as a package with this repo tracking in #2
[x] Figure out how this translates to https://github.com/wildlife-dynamics/ecoscope-server/pull/80

What does the server need to know about the release? Ultimately, it just needs to know the service url the release is running on. But how will it know that? It could be the responsibility of this repo to just deploy to GCP, and register that deployment here with the Deployments API. Then, the server could read off the service url from the GitHub deployments API. The only problem I can see with that is that it means the full stack is not completely runnable without an internet connection.
Alternatively, the server could just know the URI of the container built for this repo, and then a subsequent step would be required to actually deploy that container (whether locally or to GCP). And in fact, what we are really talking about are two paired containers: an entrypoint/launcher, and a worker container. (Though at this exact moment, only the former is available.)

Follow-ons (can be separate issues):

Once this works, make it a template which can be reused for workflows. (What is the process for migrating templates as they evolve 🤔 ?) tracking in #3
https://pixi.sh/dev/advanced/updates_github_actions/ 🤷

Issues with ecoscope-workflows-core v0.0.2 that have surfaced as part of this work:

[ ] https://github.com/ecoscope-platform-workflows-releases/patrols/pull/1/commits/0083cbebf7f0a9a95940ad0a3a266c852790c27e - tmp release artifacts path should not be in the generated pixi.toml for a "production" build
[ ] generated file header doesn't list correct version of ecoscope-workflows-core

Figure out how this translates to https://github.com/wildlife-dynamics/ecoscope-server/pull/80

I think the most sensible thing is for the server to only know directly about the deployed service url of the workflow, and then for the service itself to publicize (via a /build-info endpoint or similar) its relationship to a github repo (for provenance).


[5.1] [5.2] updateOrCreate() crashes a server on a table without primary key

PHP Version 5.6.14-1+deb.sury.org~trusty+1
Laravel version: 5.1.27
Table without primary keys (postgresql):
CREATE TABLE "public"."demo" (
"marked_at" timestamptz(6),
"foo" int4
)
WITH (OIDS=FALSE)

;

INSERT INTO "public"."demo" VALUES ('2015-12-22 09:20:27+00',  '3');

Model:
<?php

use Illuminate\Database\Eloquent\Model;

class Demo extends Model
{
    protected $guarded = [];

    /**
     * The database table used by the model.
     *
     * @var string
     */
    protected $table = 'demo';

    /**
     * @var array
     */
    public $timestamps = false;

    /**
     * The primary key for the model.
     *
     * @var string
     */
    protected $primaryKey = null;

    /**
     * Indicates if the IDs are auto-incrementing.
     *
     * @var bool
     */
    public $incrementing = false;
}

Sample code:
Demo::updateOrCreate(['marked_at' => '2015-12-22 09:20:27+00'], ['foo' => mt_rand(0, 10000)]);
Basically, updating existing row crashes a server. In apache error log I can see:
PHP message: PHP Fatal error:  Maximum function nesting level of '256' reached, aborting!
Increasing this value (I mean nesting level) does not help. This error is related to xdebug. Adding primary key id is the solution in this case but in this situation, updateOrCreate shouldn't update row by marked_at field?

Not sure if this is actually meant to be supported by us. Ping @taylorotwell.

@adam-boduch  Eloquent always requires primary key for updating. Even normal update won't work without it.

@acasar I was pulling out my hair for hours over this, so definitely relieved to find this page. I was curious, when should we set primarykey to null then?
I thought this would be the exact use case for that?

@concept47 It's actually quite simple - if you need to update your model at any point or you want to use Eloquent relations, you'll need to define a primary key. In other cases feel free to set it to null.
That's because Eloquent needs to construct a where condition to update the record in the database and there is no way to do that without the primary key.

got it. Thanks!


feat: LU copy & paste & delete with unified CRUD lib

Description
Fix LU related copy / paste / delete behaviors.
Migrate to a unified CRUD lib to bring unified Action / LU / LG resources' Create / Read / Update / Delete / Copy / Paste / Move experience.
close #2273
close #2406
close #2726
refs #2699
refs #2312 (only applied to Visual Editor)
Changes:

Implemented several shared hooks as unified CRUD lib
Copy / Paste behavior will always invoke action constructor (#2406 )
Broke 'Move' operation into several atomic CRUD action
make Visual Editor consumes the shared CRUD lib

Implement Shared Hooks
External Resource API

useLgApi -> operate lgTemplate
useLuApi -> operate luIntent

Adaptive Dialog API

useActionApi -> construct / copy / destruct actions
(not included) useTriggerApi
useDialogApi -> operate dialog file

Editing API

useDialogEditApi -> copySelection; cutSelection; pasteSelection; deleteSelection; moveSelection

Task Item

Screenshots

@yeze322 when we Move a selected series of actions with .lu data into a new dialog we also should set the recognizer field on the new dialog to be the same as the recognizer field in current dialog.

@cwhitten I got it. the recognizer field in new dialog will be set to <dialogName>.lu

@yeze322 LG templates are not copied over appropriately when the using "Move"

@yeze322 LG templates are not copied over appropriately when the using "Move"

yes, with only this PR, new lg/lu/dialog file will not be updated correctly.
it depends on Leilei's PR #2742


BUG: Wasserstein distance with p=infinity or more concretely p=540 returns zero.

Describe your issue.
BUG: Wasserstein distance with p=infinity or more concretely p=540 returns zero, although it seems it should be a positive number. See how it suddenly changes between p=537 and p538.
I think it is a bug in code.
Reproducing Code Example
a, b = [1,2,3,54], [1,2,3,4]
from scipy.stats._stats_py import _cdf_distance as _cdf
for i in [_cdf(i, a,b) for i in range(1, 600)][500:538]:
    print(i)
# [0.25195974860982445, 0.2519558294971846, 0.2519519260280944, 0.2519480381090765, 0.2519441656473971, 0.25194030855105787, 0.25193646672878944, 0.2519326400900438, 0.2519288285449871, 0.25192503200449284, 0.2519212503801349, 0.25191748358418053, 0.2519137315295838, 0.2519099941299785, 0.2519062712996721, 0.25190256295363855, 0.2518988690075123, 0.25189518937758176, 0.2518915239807828, 0.2518878727346927, 0.25188423555752404, 0.2518806123681182, 0.2518770030859398, 0.2518734076310705, 0.25186982592420304, 0.25186625788663564, 0.25186270344026584, 0.25185916250758533, 0.2518556350116739, 0.25185212087619396, 0.2518486200253852, 0.2518451323840589, 0.25184165787759283, 0.25183819643192557, 0.25183474797355165, 0.251831312429516, 0.25182788972740905, 0.0]

Error message
it returns 0.0 instead of something like 0.2518...

SciPy/NumPy/Python version and system information
scipy 1.11.4 linux debian

_cdf_distance is a private function, and it called in the codebase with p=1 and p=2. If you cannot see the effects of this with a call to a public function, there is no need to fix it.


Add documentation for tsne visualisation to docs (README.md)

Following issue #27:

[ ]  Add code sample for test dictionaries in documentation (README.md)
[ ] Add a plot vor a simple example, showcasing the plotly plot (howering over a single datapoint for labels)

On that note: Maybe makes sense to have a more expressive example for the test file than the current one in case we want to use it for documentation.

On that note: Maybe makes sense to have a more expressive example for the test file than the current one in case we want to use it for documentation.

I already host the translated version of BIOFIND cohort on GitHub publicly. Does it make sense to utilize that?


add new predicate lib

added a predicate lib
added related mocha tests
fixed up some weirdness in package.json & updated a couple deps

notify @gmsewell6 when is merged so deps can be updated elsewhere


can't add camera - not visible

I have problem with addin camera.
When I start camera by test: node standalone.js, I see she in accessories in HomeKit. I dont add camera in this moment to my accessories
When I restart Pi again, camera is not availible (dont see her)
All commands for automation was done.
I choosed version without installation as homebridge plugin
Could you help me solving this problem ?

what is the output of journalctl -u hap-camera-rpi

Same issue
got
journalctl -u hap-camera-rpi
-- No entries --

Did you run sudo systemctl enable hap-camera-rpi?
What is the output of sudo systemctl status hap-camera-rpi?


fix(clerk-js): Use useEffectForceOnce to avoid firing useEffect twice in dev

Description

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.vd68f379

@clerk/clerk-js
4.68.2-snapshot.vd68f379

@clerk/clerk-expo
0.19.28-snapshot.vd68f379

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.v88ff6e0

@clerk/clerk-js
4.68.2-snapshot.v88ff6e0

@clerk/clerk-expo
0.19.28-snapshot.v88ff6e0

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@nikosdouvlis don't merge yet, this is not resolved yet. The best approach would be to either introduce a useMutation similar to useFetch or allow cancellation in our clerk-js methods for resources (Abort Controller)

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.v42e17ec

@clerk/clerk-js
4.68.2-snapshot.v42e17ec

@clerk/clerk-expo
0.19.28-snapshot.v42e17ec

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.vaf7adfd

@clerk/clerk-js
4.68.2-snapshot.vaf7adfd

@clerk/clerk-expo
0.19.28-snapshot.vaf7adfd

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

!snapshot

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.v6ca6305

@clerk/clerk-js
4.68.2-snapshot.v6ca6305

@clerk/clerk-expo
0.19.28-snapshot.v6ca6305

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.v8fcca55

@clerk/clerk-js
4.68.2-snapshot.v8fcca55

@clerk/clerk-expo
0.19.28-snapshot.v8fcca55

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
0.6.3-snapshot.va439d8e

@clerk/clerk-js
4.68.2-snapshot.va439d8e

@clerk/clerk-expo
0.19.28-snapshot.va439d8e

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@nikosdouvlis Do u mind taking another look ? Changes have been made since the first push

I'm having this issue until this day
Next.JS 14.2
Clerk next: 4.29.12


ZedBoard fail compilation

Hi everyone
Operating system: FreeBSD 9.3-RELEASE amd64
Source code in /usr/src: FreeBSD 11.0-CURRENT downloaded by the comand 'svn co "http://svn0.us-west.freebsd.org/base/head" /usr/src'
svn co "http://svn0.us-west.freebsd.org/base/head" /usr/src
So, when I try to compile, I obtain this:
root@root: /bin/sh crochet.sh -c config_zedboard.sh
Starting at Thu Feb 18 17:30:15 ART 2016
Loading configuration from config_zedboard.sh
Board: ZedBoard
Option: UsrPorts
Will install up-to-date /usr/ports from portsnap
Option: UsrSrc
Source Version is: 295757
Building FreeBSD version: 11.0
Image name is:
/home/FreeBSD_PC/Descargas/Crochet/work/FreeBSD-ZEDBOARD-ZedBoard-Src-Ports.img
Building FreeBSD version: 11.0
eval: 1: Syntax error: redirection unexpected
I've used a config file that I made. But I obtained the same error if I use the generic config file by the comand: /bin/sh crochet.sh -b ZedBoard
Hernán Malatini

I suspect this is an issue with FreeBSD 9.  Do you have a newer FreeBSD system around?

Closing, since we don't officially support running Crochet on FreeBSD 9.


Adding ffg/cost to upgrades and mining tie

Thanks!
When adding FFG ids please run the ffg2xws npm script so the map in data/ffg-xws.json is updated as well.


feat: add project config loading

closes #9
closes #11

Both issues from the PR description are handled in here.

Both issues from the PR description are handled in here.

But #11 is a PR :confused:

Both issues from the PR description are handled in here.

But #11 is a PR 😕

@lukashass True. I just removed it.


[BUG] Import doesn't work for saved tweets

Describe the bug
After importing an export file which includes saved tweets I cannot see my saved tweets in the app. (also thanks so much for you work on fritter, I love it!)
To Reproduce
Steps to reproduce the behavior:

Create an export file that includes saved tweets
Import the export file
The app will say it imported the data successfully
Go to the saved tweets tab
The following error message will show: type 'Null' is not a subtype of type 'String' in type cast
The following error is also found in logcat:
05-02 08:32:46.294 15410 32119 E CursorWindow: The size of (459, 1) is too big (3038392), so replace the value to NULL

Screenshots

Device

Android 12
device locale/language: en_CA
Fritter version: f-droid v2.16.3+202201232

@superjkl I think this might be fixed in the latest version. Please could you try with 3.0.0-beta1, or one of the CI builds from GitHub Actions?

Hi, so sorry for taking forever to reply here. I went ahead and updated to 3.0.0-beta3 and all the behavior is exactly the same including the logcat error. When I attempt to export my data everything exports properly except for my saved tweets. I hope my saved tweets aren't lost (but if they are that's my fault for continuing to use a broken version lol) so is there some other way I could access them though ADB?

OK, this looks like it's related to the maximum database cursor window, which appears to be limited inside Android itself, and the tweet that's trying to be loaded from the database is over that limit (3MB, wow!).
Are you able to send me the export via email, so I can try and fix it with a real use case? jonjo (at) jonjomckay.com will get it to the right place.
If not, I'm not sure I'll be able to fix your existing data, but I might be able to prevent it from happening with new saved tweets.

Okay, I've sent you the export.


Intellisense

Get it going for Scene, Camera, Renderer etc

Improved for v0.1.20.
By no means amazing. This isnt my forte, would love any help on it!


zip deploy a set of files into a virtual directory or physical directory in azure app service

Required Information
Question, Bug, or Feature?
Type: Question
Enter Task Name: Azure App Service Deploy
Environment

Server - Azure Pipelines
Agent - Hosted

Issue Description
How would you deploy a zip / set of files into a virtual directory in azure app service?
We have virtual directory on a different path than site/wwwroot, where would like to unzip or run from zip the content. That path site/somefolder is mapped to virtual directory in azure app service (some.azurewebsites.net/somefolder ).
I cant seem to find a way to configure zip deployment or run from zip for a virtual directory and be able tp deploy content to in using the  Azure App Service Deploy task.
Task has virtual application support, but doesnt work for virtual directories.

@melborp , it is a feature request to Azure App Service. Can you please post your query here?


Update file structure and use gRPC instead of unix sockets

This PR does several things:

Updates the file structure of the project so that each project is a crate instead of just a file. So now we have a littled crate and a little-cli crate.
Updates to use clap, which is the standard rust library for CLI tools. Comes with basic commands (help, version) out of the box.
Refactors to use gRPC connections instead of unix sockets, still maintains the http server concurrently. Based on a few conversations with ChatGPT, it seems gRPC is better to use than Unix Sockets because Unix Sockets are limited to local connections, and it's very conceivable that someone would want this to be running on a separate machine. gRPC seems to be modern goto for CLI tools to do this.

To give it a shot, run:
cargo run littled
cargo run --bin little-cli start

# to test http server
curl -X POST -H "Content-Type: application/json" -d '{"command": "test", "arguments": {"arg1": "value1"}}' http://<IP_ADDRESS>:3030/little/api/v1/command

To see a sample communication over gRPC from the little-cli to the littled

@sbddesign I apologize, I simply forgot to push the latest commit. It's pushed now and the warp server is there and you should be able to curl. Let me know if it works for you!

Great @thebrandonlucas thanks for fixing


Parse field Cluster From Resource.Extensions in CLI

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

pkg/kusionctl/cmd/apply
pkg/engine/states/local/
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

Parse field Cluster From Resource.Extensions in CLI
Rollback yaml.v3 to v2 for a known bug in v3

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Coverage decreased (-0.01%) to 72.622% when pulling 55f8a302a6f4cba7accb3fd10a10dbf4aa839cf5 on SparkYuan:add_cluster_in_cli into 182d1622a1ca0367d72d06ef3ff2f5a32ee6eaea on KusionStack:main.


Add target profile setting in VS Code

A new configuration setting for target profile.
Status bar item to show this setting.
Command to set this setting.
Language service update to consume this setting.

Just noticed a couple bugs in testing, the first to do with this PR, the second a more general one:

It doesn't set the profile on starting the language service, only when you change it. So if I have base profile set in my settings already, it doesn't take effect. I added this commit to my branch to fix it https://github.com/microsoft/qsharp/pull/621/commits/0077b387b24720c93058112a24fe2c39a9eb9294

In general, if you launch VS Code with a .qs file already loaded, no errors show up until you make an edit - be they profile errors, syntax errors, etc. Looks like we need to force a diagnostic pass if there are documents already open on launch. I can start looking into that too.

OK. The 2nd issue was pretty easy to fix (I think). Just needed to start listening for diagnostics earlier (before it adds the open diagnostics). Take a look at the below commit in my Azure branch and see if that looks right.
https://github.com/microsoft/qsharp/pull/621/commits/335d917c0e8a292dda9922bcfeccce0a679101fe

This work was merged in as part of #621 . Thanks!


Update metric computation to work with lat/lon region bounds

IceNet version: v0.2.9_dev
Python version: 3.11

Description
Please see details in #282 pull request.
In short, as of this post, forecast output generation (png, mp4) works with lat/lon region definition, but metrics generation such as sie, binary accuracy, etc within icenet/plotting/forecast.py needs changes to Mask class to allow bounding the mask output (e.g. active cell mask). Currently this is not done, hence the metric outputs will be incorrect if defining a region based on lat/lon.

In meantime, these metric plots should not be output to avoid confusing user!

In meantime, these metric plots should not be output to avoid confusing user!

Resolved by latest commit above.


asp.net 2.0 version

Hi there,
Firstly thanks for providing a great sample
I think there are a couple of changes that need to be made for asp.net 2.0 projects.
Namely the Authentication side of things IdentityCookieOptions:  https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/identity-2x
Also I noticed in your StopImpersonation method, you have decorated it with ** [Authorize(Roles = "Admin")]** but this can be problematic, since there could be situation where the user that you are impersonating isn't in the admin role to begin with so you can't stop the impersonation

Yeah, there are a couple of issues that I know of in that implementation and need to update to v2.0.
And good call on the Admin role for de-impersonation - I did not think of it.
I'll get these fixed when I have some spare time.

@dotnetshadow I've updated the blog post and the repo with the version for Core v2. See branch https://github.com/trailmax/AspNetCoreImpersonation/tree/CoreV2

@trailmax thanks you so much I'll give this a try and report back if there are any issues


CSV or TSV Dataset with double quotes doesn't work

System Information (please complete the following information):

Model Builder Version: 16.0.1911.1103
Visual Studio Version: 16.4.3

Describe the bug
Titanic dataset from kaggle.com
I can't process this data set, because data on the Name column between double quotes.
Screenshots

dup of #435


Problem with the '.ini'  importer

From @tbpassin :
All right, it installed in vsc and it did open an outline.  I saw a lot of errors like this:
reading settings in C:/Users/tom/.leo/workbook.leo
TypeError: Cannot read properties of undefined (reading 'trim')
at Ini_Importer.find_blocks (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1507413)
at Ini_Importer.gen_block (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1508153)
at Ini_Importer.gen_lines (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1511889)
at Ini_Importer.import_from_string (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1512400)
at exports.do_import (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1522910)
at LeoImportCommands.createOutline (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1338218)
at async AtFile.readOneAtAutoNode (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:955878)
at async AtFile.readFileAtPosition (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:954544)
at async AtFile.readAll (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:953359)
at async FileCommands.readExternalFiles (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1151896)
at async FileCommands._getLeoFileByName (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1151493)
at async FileCommands.getAnyLeoFileByName (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1149953)
at async LoadManager.openFileByName (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:937514)
at async LoadManager.loadLocalFile (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:936309)
at async SessionManager.load_session (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1439599)
at async LoadManager.doPostPluginsInit (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:932259)
at async LoadManager.load (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:931126)
at async runLeo (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1807739)
at async activate (c:\Users\tom.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1815070)
at async u.n (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:6255)
at async u.m (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:6218)
at async u.l (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:5675)

@tbpassin Can you provide me with the .ini file that your leo file is trying to refresh at startup?

I think this is related to Leo's issue: https://github.com/leo-editor/leo-editor/issues/3727  😄

@tbpassin Oh i had a mistranlation in the ini importer's regex. Will be fixed in next release tomorrow.

Here are the two external .ini files I have in the workbook. The errors must have come during processing them.
inifiles.zip

@tbpassin  I would have needed the ini files themselves zipped, not the leo file  alone that you zipped, for which the inner @auto and @clean nodes have nothing to pikup upon... and therefore endup almost empty 😢

Oops, sorry.  I forgot that.  Coming right up.
inifiles.zip

@tbpassin That did the trick! 👍  Today's new release has gotten rid of those errors!
Thanks for testing out and reporting what you find! Really very much appreciated!!
With your help, we'll get rid of the remaining bugs and get to a full LeoJS 1.0 release much more quickly! Thanks again Thomas!!

: )

I didn't get any error messages on opening leoJS with the new release.
LeoJS 0.2.7, master branch, build 1ae8764
2023-12-23 20:17:31 -0500
Node.js v18.15.0, VSCode version 1.85.1


GEODE-2644: Enable xml config for Alerting and Logging appenders

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

[This comment is a test for how resource checking works in our Concourse infrastructure.]