containerapp ingress access-restriction set fails when Azure Portal has added ingress source with empty name

Describe the bug
Bug:
Unable to add call az containerapp ingress access-restriction set with valid input parameters, when empty rule-name already exists on containerapp
Rootcause:
One or mulitple ingress rule-name is empty for container app
Solution:
Either handle empty access-restriction names in cli or force azure portal UI to have --rule-name field required
When someone from azure portal UI has added a containerapp ingress source without a name (which is allowed there)
Related command
az containerapp ingress access-restriction set -n capp -g rg-cenv--rule-name foobarlife --ip-address <IP_ADDRESS> --action Allow
Errors
2024-02-16T15:19:11.7795244Z Traceback (most recent call last):
2024-02-16T15:19:11.7795716Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
2024-02-16T15:19:11.7796298Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
2024-02-16T15:19:11.7796899Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
2024-02-16T15:19:11.7797474Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 721, in _run_job
2024-02-16T15:19:11.7798132Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_client_factory.py", line 28, in _polish_bad_errors
2024-02-16T15:19:11.7799232Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 698, in _run_job
2024-02-16T15:19:11.7799907Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
2024-02-16T15:19:11.7800514Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
2024-02-16T15:19:11.7801146Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/custom.py", line 2585, in set_ip_restriction
2024-02-16T15:19:11.7801982Z   File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_utils.py", line 1740, in set_ip_restrictions
2024-02-16T15:19:11.7802574Z KeyError: 'name'
2024-02-16T15:19:11.7804980Z To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
Issue script & Debug output
cli.knack.cli: Command arguments: ['containerapp', 'ingress', 'access-restriction', 'set', '-n', 'capp', '-g', 'rg-capp', '--rule-name', 'foobar', '--ip-address', '<IP_ADDRESS>/32', '--action', 'Allow', '--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 0x000001FD8F8BB920>, <function OutputProducer.on_global_arguments at 0x000001FD8FA460C0>, <function CLIQuery.on_global_arguments at 0x000001FD8FA73C40>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'containerapp': ['azext_containerapp', 'azure.cli.command_modules.containerapp', 'azure.cli.command_modules.serviceconnector']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: containerapp              0.275        36       115
cli.azure.cli.core: serviceconnector          0.057        16       244
cli.azure.cli.core: Total (2)                 0.332        52       359
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_ai_examples', 'azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: containerapp              0.013        30        81  C:\Users\hellm.azure\cliextensions\containerapp
cli.azure.cli.core: Total (1)                 0.013        30        81
cli.azure.cli.core: Loaded 70 groups, 416 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : containerapp ingress access-restriction set
cli.azure.cli.core: Command table: containerapp ingress access-restriction set
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x000001FD9294AAC0>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to 'C:.azure\commands\2024-02-16.16-35-33.containerapp_ingress_access-restriction_set.33116.log'.
az_command_data_logger: command args: containerapp ingress access-restriction set -n {} -g {} --rule-name {} --ip-address {} --action {} --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument..add_subscription_parameter at 0x000001FD929A5080>]
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument..add_ids_arguments at 0x000001FD929A5120>, <function register_cache_arguments..add_cache_arguments at 0x000001FD929A5260>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
cli.knack.cli: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x000001FD8FA46160>, <function CLIQuery.handle_query_parameter at 0x000001FD8FA73CE0>, <function register_ids_argument..parse_ids_arguments at 0x000001FD929A51C0>]
cli.azure.cli.core.commands.client_factory: Getting management service client client_type=ResourceManagementClient
cli.azure.cli.core.auth.persistence: build_persistence: location='C:\Users\hellm\.azure\msal_token_cache.bin', encrypt=True
cli.azure.cli.core.auth.binary_cache: load: C:\Users\hellm.azure\msal_http_cache.bin
urllib3.util.retry: Converted retries value: 1 -> Retry(total=1, connect=None, read=None, redirect=None, status=None)
msal.authority: openid_config = {'token_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/token', 'token_endpoint_auth_methods_supported': ['client_secret_post', 'private_key_jwt', 'client_secret_basic'], 'jwks_uri': 'https://login.microsoftonline.com/REDACTED/discovery/v2.0/keys', 'response_modes_supported': ['query', 'fragment', 'form_post'], 'subject_types_supported': ['pairwise'], 'id_token_signing_alg_values_supported': ['RS256'], 'response_types_supported': ['code', 'id_token', 'code id_token', 'id_token token'], 'scopes_supported': ['openid', 'profile', 'email', 'offline_access'], 'issuer': 'https://login.microsoftonline.com/REDACTED/v2.0', 'request_uri_parameter_supported': False, 'userinfo_endpoint': 'https://graph.microsoft.com/oidc/userinfo', 'authorization_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/authorize', 'device_authorization_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/devicecode', 'http_logout_supported': True, 'frontchannel_logout_supported': True, 'end_session_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/logout', 'claims_supported': ['sub', 'iss', 'cloud_instance_name', 'cloud_instance_host_name', 'cloud_graph_host_name', 'msgraph_host', 'aud', 'exp', 'iat', 'auth_time', 'acr', 'nonce', 'preferred_username', 'name', 'tid', 'ver', 'at_hash', 'c_hash', 'email'], 'kerberos_endpoint': 'https://login.microsoftonline.com/REDACTED/kerberos', 'tenant_region_scope': 'EU', 'cloud_instance_name': 'microsoftonline.com', 'cloud_graph_host_name': 'graph.windows.net', 'msgraph_host': 'graph.microsoft.com', 'rbac_url': 'https://pas.windows.net'}
msal.application: Broker enabled? True
cli.azure.cli.core.auth.credential_adaptor: CredentialAdaptor.get_token: scopes=('https://management.core.windows.net//.default',), kwargs={}
cli.azure.cli.core.auth.msal_authentication: UserCredential.get_token: scopes=('https://management.core.windows.net//.default',), claims=None, kwargs={}
msal.application: Cache hit an AT
msal.telemetry: Generate or reuse correlation_id: 49243406-41ab-4327-8ddc-45df41a2df3b
cli.azure.cli.core.sdk.policies: Request URL: 'https://management.azure.com/subscriptions/REDACTED/providers/Microsoft.App?api-version=2022-09-01'
cli.azure.cli.core.sdk.policies: Request method: 'GET'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '05b982d6-cce1-11ee-b3dd-c0b6f9fb93dd'
cli.azure.cli.core.sdk.policies:     'CommandName': 'containerapp ingress access-restriction set'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '-n -g --rule-name --ip-address --action --debug'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.57.0 (MSI) azsdk-python-azure-mgmt-resource/23.1.0b2 Python/3.11.7 (Windows-10-10.0.22631-SP0)'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: This request has no body
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool: https://management.azure.com:443 "GET /subscriptions/REDACTED/providers/Microsoft.App?api-version=2022-09-01 HTTP/1.1" 200 1910
cli.azure.cli.core.sdk.policies: Response status: 200
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Content-Encoding': 'gzip'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'Vary': 'Accept-Encoding'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-reads': '11979'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': 'aacb3f11-f09f-403b-8d09-935a22e8b524'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': 'aacb3f11-f09f-403b-8d09-935a22e8b524'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'SWEDENCENTRAL:20240216T153534Z:aacb3f11-f09f-403b-8d09-935a22e8b524'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'Date': 'Fri, 16 Feb 2024 15:35:34 GMT'
cli.azure.cli.core.sdk.policies:     'Content-Length': '1910'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"id":"/subscriptions/REDACTED/providers/Microsoft.App","namespace":"Microsoft.App","authorizations":[{"applicationId":"7e3bc4fd-85a3-4192-b177-5b8bfc87f42c","roleDefinitionId":"39a74f72-b40f-4bdc-b639-562fe2260bf0"},{"applicationId":"3734c1a4-2bed-4998-a37a-ff1a9e7bf019","roleDefinitionId":"5c779a4f-5cb2-4547-8c41-478d9be8ba90"},{"applicationId":"55ebbb62-3b9c-49fd-9b87-9595226dd4ac","roleDefinitionId":"e49ca620-7992-4561-a7df-4ed67dad77b5","managedByRoleDefinitionId":"9e3af657-a8ff-583c-a75c-2fe7c4bcb635"},{"applicationId":"1459b1f6-7a5b-4300-93a2-44b4a651759f","roleDefinitionId":"3c5f1b29-9e3d-4a22-b5d6-9ff4e5a37974"}],"resourceTypes":[{"resourceType":"managedEnvironments","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SystemAssignedResourceIdentity, SupportsTags, SupportsLocation"},{"resourceType":"managedEnvironments/certificates","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SupportsTags, SupportsLocation"},{"resourceType":"managedEnvironments/managedCertificates","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SupportsTags, SupportsLocation"},{"resourceType":"containerApps","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SystemAssignedResourceIdentity, SupportsTags, SupportsLocation"},{"resourceType":"jobs","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SystemAssignedResourceIdentity, SupportsTags, SupportsLocation"},{"resourceType":"locations","locations":[],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/managedEnvironmentOperationResults","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/managedEnvironmentOperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/containerappOperationResults","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/containerappOperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/containerappsjobOperationResults","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/containerappsjobOperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/sourceControlOperationResults","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/sourceControlOperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/usages","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview"],"defaultApiVersion":"2023-05-02-preview","capabilities":"None"},{"resourceType":"operations","locations":["Central US EUAP","East US 2 EUAP","West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2023-02-01","2022-11-01-preview","2022-10-01","2022-06-01-preview","2022-03-01"],"defaultApiVersion":"2023-08-01-preview","capabilities":"None"},{"resourceType":"connectedEnvironments","locations":["North Central US","East US","East Asia","West Europe","Southeast Asia"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SupportsTags, SupportsLocation"},{"resourceType":"connectedEnvironments/certificates","locations":["North Central US","East US","East Asia","West Europe","Southeast Asia"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SupportsTags, SupportsLocation"},{"resourceType":"locations/connectedEnvironmentOperationResults","locations":["North Central US","East US","East Asia","West Europe","Southeast Asia"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/connectedEnvironmentOperationStatuses","locations":["North Central US","East US","East Asia","West Europe","Southeast Asia"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/managedCertificateOperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/billingMeters","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"locations/availableManagedEnvironmentsWorkloadProfileTypes","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview","2023-05-01","2023-04-01-preview","2022-11-01-preview","2022-10-01","2022-06-01-preview"],"defaultApiVersion":"2023-05-01","capabilities":"None"},{"resourceType":"getCustomDomainVerificationId","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview","2023-05-02-preview"],"defaultApiVersion":"2023-05-02-preview","capabilities":"None"},{"resourceType":"builders","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview"],"defaultApiVersion":"2023-08-01-preview","capabilities":"CrossResourceGroupResourceMove, CrossSubscriptionResourceMove, SystemAssignedResourceIdentity, SupportsTags, SupportsLocation"},{"resourceType":"builders/builds","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview"],"defaultApiVersion":"2023-08-01-preview","capabilities":"None"},{"resourceType":"locations/OperationResults","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview"],"defaultApiVersion":"2023-08-01-preview","capabilities":"None"},{"resourceType":"locations/OperationStatuses","locations":["West US 2","Southeast Asia","Sweden Central","Canada Central","West Europe","North Europe","East US","East US 2","East Asia","Australia East","Germany West Central","Japan East","UK South","West US","Central US","North Central US","South Central US","Korea Central","Brazil South","West US 3","France Central","South Africa North","Norway East","Switzerland North","UAE North","Canada East","West Central US","UK West","Central India"],"apiVersions":["2023-11-02-preview","2023-08-01-preview"],"defaultApiVersion":"2023-08-01-preview","capabilities":"None"}],"registrationState":"Registered","registrationPolicy":"RegistrationRequired"}
cli.azure.cli.core.util: Found subscription ID REDACTED in the URL https://management.azure.com/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/containerApps/REDACTED?api-version=2023-05-01
cli.azure.cli.core.util: Retrieving token for resource https://management.core.windows.net/, subscription REDACTED
urllib3.util.retry: Converted retries value: 1 -> Retry(total=1, connect=None, read=None, redirect=None, status=None)
msal.authority: openid_config = {'token_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/token', 'token_endpoint_auth_methods_supported': ['client_secret_post', 'private_key_jwt', 'client_secret_basic'], 'jwks_uri': 'https://login.microsoftonline.com/REDACTED/discovery/v2.0/keys', 'response_modes_supported': ['query', 'fragment', 'form_post'], 'subject_types_supported': ['pairwise'], 'id_token_signing_alg_values_supported': ['RS256'], 'response_types_supported': ['code', 'id_token', 'code id_token', 'id_token token'], 'scopes_supported': ['openid', 'profile', 'email', 'offline_access'], 'issuer': 'https://login.microsoftonline.com/REDACTED/v2.0', 'request_uri_parameter_supported': False, 'userinfo_endpoint': 'https://graph.microsoft.com/oidc/userinfo', 'authorization_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/authorize', 'device_authorization_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/devicecode', 'http_logout_supported': True, 'frontchannel_logout_supported': True, 'end_session_endpoint': 'https://login.microsoftonline.com/REDACTED/oauth2/v2.0/logout', 'claims_supported': ['sub', 'iss', 'cloud_instance_name', 'cloud_instance_host_name', 'cloud_graph_host_name', 'msgraph_host', 'aud', 'exp', 'iat', 'auth_time', 'acr', 'nonce', 'preferred_username', 'name', 'tid', 'ver', 'at_hash', 'c_hash', 'email'], 'kerberos_endpoint': 'https://login.microsoftonline.com/REDACTED/kerberos', 'tenant_region_scope': 'EU', 'cloud_instance_name': 'microsoftonline.com', 'cloud_graph_host_name': 'graph.windows.net', 'msgraph_host': 'graph.microsoft.com', 'rbac_url': 'https://pas.windows.net'}
msal.application: Broker enabled? True
cli.azure.cli.core.auth.msal_authentication: UserCredential.get_token: scopes=('https://management.core.windows.net//.default',), claims=None, kwargs={}
msal.application: Cache hit an AT
msal.telemetry: Generate or reuse correlation_id: ccfe6e8a-5e4f-4ab1-9b24-7dcbc91f217c
cli.azure.cli.core.util: Request URL: 'https://management.azure.com/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/containerApps/REDACTED?api-version=2023-05-01'
cli.azure.cli.core.util: Request method: 'GET'
cli.azure.cli.core.util: Request headers:
cli.azure.cli.core.util:     'User-Agent': 'python/3.11.7 (Windows-10-10.0.22631-SP0) AZURECLI/2.57.0 (MSI)'
cli.azure.cli.core.util:     'Accept-Encoding': 'gzip, deflate'
cli.azure.cli.core.util:     'Accept': '/'
cli.azure.cli.core.util:     'Connection': 'keep-alive'
cli.azure.cli.core.util:     'x-ms-client-request-id': 'bb87267e-fea7-4a13-86f1-92470400bacc'
cli.azure.cli.core.util:     'CommandName': 'containerapp ingress access-restriction set'
cli.azure.cli.core.util:     'ParameterSetName': '-n -g --rule-name --ip-address --action --debug'
cli.azure.cli.core.util:     'Authorization': 'Bearer eyJ0eXAiOiJKV...'
cli.azure.cli.core.util: Request body:
cli.azure.cli.core.util: None
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool: https://management.azure.com:443 "GET /subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/containerApps/REDACTED?api-version=2023-05-01 HTTP/1.1" 200 None
cli.azure.cli.core.util: Response status: 200
cli.azure.cli.core.util: Response headers:
cli.azure.cli.core.util:     'Cache-Control': 'no-cache'
cli.azure.cli.core.util:     'Pragma': 'no-cache'
cli.azure.cli.core.util:     'Transfer-Encoding': 'chunked'
cli.azure.cli.core.util:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.util:     'Content-Encoding': 'gzip'
cli.azure.cli.core.util:     'Expires': '-1'
cli.azure.cli.core.util:     'Vary': 'Accept-Encoding,Accept-Encoding'
cli.azure.cli.core.util:     'x-ms-ratelimit-remaining-subscription-reads': '11973'
cli.azure.cli.core.util:     'api-supported-versions': '2022-03-01, 2022-06-01-preview, 2022-10-01, 2022-11-01-preview, 2023-04-01-preview, 2023-05-01, 2023-05-02-preview, 2023-08-01-preview, 2023-11-02-preview, 2024-02-02-preview'
cli.azure.cli.core.util:     'Server': 'Microsoft-IIS/10.0'
cli.azure.cli.core.util:     'X-Powered-By': 'ASP.NET'
cli.azure.cli.core.util:     'x-ms-request-id': 'dddd3034-9324-4560-804a-4c37911297ab'
cli.azure.cli.core.util:     'x-ms-correlation-request-id': 'dddd3034-9324-4560-804a-4c37911297ab'
cli.azure.cli.core.util:     'x-ms-routing-request-id': 'SWEDENCENTRAL:20240216T153535Z:dddd3034-9324-4560-804a-4c37911297ab'
cli.azure.cli.core.util:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.util:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.util:     'Date': 'Fri, 16 Feb 2024 15:35:35 GMT'
cli.azure.cli.core.util: Response content:
cli.azure.cli.core.util: {"id":"/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/containerapps/REDACTED","name":"REDACTED","type":"Microsoft.App/containerApps","location":"West Europe","systemData":{"createdBy":"REDACTED","createdByType":"User","createdAt":"2024-02-14T07:04:41.9547226","lastModifiedBy":"REDACTED","lastModifiedByType":"User","lastModifiedAt":"2024-02-16T15:34:21.4480765"},"properties":{"provisioningState":"Succeeded","runningStatus":"Running","managedEnvironmentId":"/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/managedEnvironments/REDACTED","environmentId":"/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.App/managedEnvironments/REDACTED","workloadProfileName":"Consumption","outboundIpAddresses":["<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>","<IP_ADDRESS>"],"latestRevisionName":"REDACTED--3a62ugb","latestReadyRevisionName":"REDACTED--3a62ugb","latestRevisionFqdn":"REDACTED--3a62ugb.ashyocean-6f9bbb29.westeurope.azurecontainerapps.io","customDomainVerificationId":"52EBD3C44BA5EE43331A39A07CCA7C76407D8A63E962781211183AAE86667D9D","configuration":{"secrets":[{"name":"cr-password"}],"activeRevisionsMode":"Single","ingress":{"fqdn":"REDACTED.ashyocean-6f9bbb29.westeurope.azurecontainerapps.io","external":true,"targetPort":8080,"exposedPort":0,"transport":"Auto","traffic":[{"weight":100,"latestRevision":true}],"customDomains":null,"allowInsecure":true,"ipSecurityRestrictions":[{"name":"rule1","ipAddressRange":"<IP_ADDRESS>/24","action":"Allow"},{"ipAddressRange":"<IP_ADDRESS>","action":"Allow"}],"corsPolicy":null,"clientCertificateMode":"Ignore","stickySessions":{"affinity":"none"}},"registries":[{"server":"REDACTED.azurecr.io","username":"REDACTED","passwordSecretRef":"cr-password","identity":""}],"dapr":null,"maxInactiveRevisions":null,"service":null},"template":{"revisionSuffix":"","terminationGracePeriodSeconds":null,"containers":[{"image":"REDACTED.azurecr.io/REDACTED:v<IP_ADDRESS>f3cb","name":"REDACTED","env":[{"name":"ConfigurationKeyVault__Name","value":"REDACTED"}],"resources":{"cpu":0.5,"memory":"1Gi","ephemeralStorage":"2Gi"},"probes":[]}],"initContainers":null,"scale":{"minReplicas":0,"maxReplicas":10,"rules":[{"name":"http-requests","http":{"metadata":{"concurrentRequests":"10"}}}]},"volumes":[],"serviceBinds":null},"eventStreamEndpoint":"https://westeurope.azurecontainerapps.dev/subscriptions/REDACTED/resourceGroups/REDACTED/containerApps/REDACTED/eventstream"},"identity":{"type":"SystemAssigned","principalId":"493432c3-4d48-480f-be8c-d14a09d8559e","tenantId":"REDACTED"}}
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 721, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_client_factory.py", line 28, in _polish_bad_errors
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 698, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/custom.py", line 2585, in set_ip_restriction
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_utils.py", line 1740, in set_ip_restrictions
KeyError: 'name'
cli.azure.cli.core.azclierror: The command failed with an unexpected error. Here is the traceback:
az_command_data_logger: The command failed with an unexpected error. Here is the traceback:
cli.azure.cli.core.azclierror: 'name'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 721, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_client_factory.py", line 28, in _polish_bad_errors
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 698, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/custom.py", line 2585, in set_ip_restriction
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_utils.py", line 1740, in set_ip_restrictions
KeyError: 'name'
az_command_data_logger: 'name'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 664, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 721, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_client_factory.py", line 28, in _polish_bad_errors
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 698, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 334, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/custom.py", line 2585, in set_ip_restriction
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/containerapp/_utils.py", line 1740, in set_ip_restrictions
KeyError: 'name'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x000001FD9294AD40>]
az_command_data_logger: exit code: 1
cli.main: Command ran in 2.107 seconds (init: 0.265, invoke: 1.842)
cli.azure.cli.core.decorators: Suppress exception:
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/main.py", line 62, in
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/main.py", line 55, in
SystemExit: 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/decorators.py", line 79, in _wrapped_func
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/telemetry.py", line 532, in _get_secrets_warning_config
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/config.py", line 147, in getboolean
ValueError: Not a boolean: None
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 7111 in cache
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\azure\cli\telemetry_init_.pyc C:\Users.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.
Expected behavior
cli command should alter container app so new ingress is added even if empty rule names exists
Environment Summary
2024-02-16T15:23:52.2476551Z [command]/usr/bin/az --version
2024-02-16T15:23:53.5156641Z azure-cli                         2.57.0
2024-02-16T15:23:53.5172567Z
2024-02-16T15:23:53.5173257Z core                              2.57.0
2024-02-16T15:23:53.5173779Z telemetry                          1.1.0
2024-02-16T15:23:53.5174017Z
2024-02-16T15:23:53.5280541Z Extensions:
2024-02-16T15:23:53.5280965Z azure-devops                      0.26.0
2024-02-16T15:23:53.5281030Z
2024-02-16T15:23:53.5281146Z Dependencies:
2024-02-16T15:23:53.5281264Z msal                              1.26.0
2024-02-16T15:23:53.5281452Z azure-mgmt-resource             23.1.0b2
2024-02-16T15:23:53.5281898Z
2024-02-16T15:23:53.5282071Z Python location '/opt/az/bin/python3'
2024-02-16T15:23:53.5282289Z Extensions directory '/opt/az/azcliextensions'
2024-02-16T15:23:53.5282374Z
2024-02-16T15:23:53.5282614Z Python (Linux) 3.11.7 (main, Jan 31 2024, 05:29:49) [GCC 11.4.0]
2024-02-16T15:23:53.5282714Z
2024-02-16T15:23:53.5282842Z Legal docs and information: aka.ms/AzureCliLegal
2024-02-16T15:23:53.5282926Z
2024-02-16T15:23:53.5282969Z
2024-02-16T15:23:53.5283116Z Your CLI is up-to-date.
Additional context
No response

Thank you for opening this issue, we will look into it.

Hi @fredrik-hellmangroup
Thanks for reporting this bug.
In portal create a IP Restrictions not reqired name:

But in CLI az containerapp ingress access-restriction set, the rule-name is required, because we need to make sure which rule to update or create without UI.
Currently the logic has some bug when the exiting ip Restrictions do not contain rule name as you report. I will fix it.
Thanks.


Updating README.md

Codecov Report

Merging #3784 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3784      +/-   ##
============================================
- Coverage     67.17%   67.03%   -0.14%
  Complexity        4        4
============================================
  Files          1027     1027
  Lines         50812    50812
  Branches       7091     7091
============================================
- Hits          34135    34064      -71
- Misses        14343    14420      +77
+ Partials       2334     2328       -6

Impacted Files
Coverage Δ
Complexity Δ

...apache/pinot/common/metrics/ValidationMetrics.java
20.28% <0%> (-59.43%)
0% <0%> (ø)

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-50%)
0% <0%> (ø)

...er/validation/BrokerResourceValidationManager.java
31.57% <0%> (-42.11%)
0% <0%> (ø)

...ller/validation/OfflineSegmentIntervalChecker.java
26.37% <0%> (-25.28%)
0% <0%> (ø)

...e/operator/dociditerators/SortedDocIdIterator.java
55.55% <0%> (-8.34%)
0% <0%> (ø)

...pache/pinot/core/util/SortedRangeIntersection.java
83.82% <0%> (-7.36%)
0% <0%> (ø)

.../impl/dictionary/LongOffHeapMutableDictionary.java
80% <0%> (-7.28%)
0% <0%> (ø)

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
67.27% <0%> (-7.28%)
0% <0%> (ø)

.../impl/dictionary/FloatOnHeapMutableDictionary.java
86.66% <0%> (-6.67%)
0% <0%> (ø)

...troller/helix/core/retention/RetentionManager.java
74.02% <0%> (-3.9%)
0% <0%> (ø)

... and 23 more

Continue to review full report at Codecov.

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


Skip topic and control buttons disappearing

Originally had 2 topics. added a 3rd topic when 2nd topic was in progress. the skip topic and the other 2 buttons did not appear again. They re-appeared on clicking the up arrow next to the topic queue.

Fixed the logic to control the QueueUp button. The app is now working with sequence and current topic to decide which Queue Up buttons to present.


[RFR] Add optional selection column to list

Is it now RFR? Can you update the screenshot?

Don't display the action button if there are no selected items

Saucelabs is drunk, tests are green on my side. I'm merging. Thanks for your work!


Sandbox Section: Red Error Message remaining on screen indefinitely

As seen here, even after fixing and re-executing, the message stays on screen.

I can try to fix this. It shouldn't be too hard.

Bug's been fixed.


Inquiry about running a demo using a custom trained model

After following the training instructions, I have successfully trained my own model using my custom dataset. I would like to use the trained model to perform a demo and generate CT images. Could you please provide some guidance on how to proceed?
Thank you in advance for your assistance.

Hi, thanks for your interest. During training, the predicted CT image, ground-truth CT image, and some slice demos will be saved in logs/*/eval/epoch_*. You can easily write a script to visualize and perform a demo. Unfortunately, we do not have a specific test script, but you can look at lines 77-90 in train.py for reference.


Error: Head "http://<IP_ADDRESS>:11434/": dial tcp <IP_ADDRESS>:11434: connectex:

What is the issue?
The last windows version of ollama didnt work on my laptop. It cant connect to 11434 anymore - even if it is free or block the port itself.
C:\Users\XXX>ollama list
Error: Head "http://<IP_ADDRESS>:11434/": dial tcp <IP_ADDRESS>:11434: connectex: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.

C:\Users\XXX>netstat -ano | find  "11434"

C:\Users\XXX>ollama list
Error: Head "http://<IP_ADDRESS>:11434/": dial tcp <IP_ADDRESS>:11434: connectex: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung  verweigerte.

The older version works ... until it selfupdatet.
The new ollama (0.1.32) didnt work in docker too.
The Chat in the console window works some times but server command never.
OS
Windows
GPU
AMD onboard
CPU
Ryzen 7000 Mobile APU
Ollama version
0.1.32 (non-docker)

Please give the latest 0.1.33 RC build a try, and hopefully your issue will be resolved.  We've fixed a number of bugs related to windows subprocess handling recently.
https://github.com/ollama/ollama/releases

Thx for the feedback.
ollama list works now.
But the serve funktion still doesnt.
If i quite the ollama app in the taskbar with rightclick i can start the serve funktion in the console.
But my Webinterface still cant connnect to ollama.

Ollama is a client-server architecture, and binds to a TCP port.  Only one process can bind to a port at a time, so you can't run two servers on the same default port.  You can run it on a different port with the OLLAMA_HOST variable, but I don't think that's what you're trying to do.  If you're trying to run a web UI and it is failing to connect this might be cross-origin related.  Check out the FAQ here for guidance.

I only use one instance. The problem didnt ocur with older versions of ollama - starting with 1.32. (Win 11 Laptop). I testet it today on an Win 10 Pro Desktop PC that never had ollama installed - same problem with the port binding on newer version.

@jannoname I'm not quite understanding your scenario.  If ollama list works, that requires the client to talk to the server to produce output.  That indicates the server IS running on your system.  It sounds like you are trying to run ollama serve again while the existing one is running and that is expected to fail as you can't have 2 servers running on the same port.  If the system tray icon is present, that indicates the Ollama server is running.  On Windows and MacOS, we try to make the server run automatically.
If that doesn't help answer your question, can you elaborate a little more what you're trying to do?  Can you check Task Manager for running Ollamas, and explain if the tray app is running or not?

@dhiltgen On Windows, the user experience should be improved.
Here a W11 example with Docker desktop and pulling latest Ollama.

The issue has been reported in https://github.com/ollama/ollama/issues/4146

I believe the problem has been resolved here on the latest version(s) of Ollama.  @jannoname if you're still having problems, please share more information on what's going wrong.

I run into this as well. The solution is to start olama with ollama serve which hosts the server, then run your wanted ollama run <model name>.


Tern does not account for modifications to existing methods

Say if tern processes package information and could not get one set of metadata, it will store the package information in the cache with empty data. If next time around, there is an addition to the command library that allows tern to get said metadata, it will not run it because it will read the incomplete information from the cache.

When loading form cache, check for missing metadata. If it finds missing metadata, then run through the retrieval steps again
When saving to the cache, do a deep comparison of all the package metadata rather than the layer. In python one can override the class's inherited eq(self, other) to do the check. If the layers are not equal, save the layer with the packages again

We can just add an option in the command line (--redo, -r) to overwrite the data that is in the cache if it exists.
This would mean writing a function to erase cached data for a particular layer.
This would also mean rewriting the flow to check if the redo flag is not set to then load data from the cache, and if yes then erase data from the cache before loading (load_from_cache function)


Add comments to structs

https://github.com/wso2-ballerina/package-twitter/blob/ca818368b62ab7f314179fa315e2dd17bcd2b5d7/twitter/twitter_structs.bal#L19

Fixed in [1].
[1] https://github.com/wso2-ballerina/package-twitter/pull/20


Turbo red/yellow

Unsure how to implement. CSceneVehicleVisState::IsTurbo is just a boolean, so there's no info on turbo level. I could check if the acceleration is fast enough for red, but that wouldn't work at full speed or with Cruise Control.

done #11


Show place holder till image loads

I want to show a place holder image( as a background or any other way) till main image downloads. I am using picasso lib to load images. I tried to use app:civ_fill_color but didn't work. is there any way to achieve it?

Specially CircleImageView in listview.

Picasso.with(context).load("http://...").placeholder(R.drawable.foobar).noFade().into(imageView)

I didn't used noFade() method. as of know its working good.

Just be aware that there might be some issues with fading as described here: #3, #5.


LinearGauss Model added in StateSpaceModel

Chapter 10, page 163: LinearGauss model seems to be assumed that the model can be imported from state_space_models, but it actually was not defined. The model is defined in Page 162.

Hi,
I moved linear Gaussian state-space models to the kalman module. The rationale is that, once you have defined such a model, you can pass it to class Kalman to perform Kalman filtering; see here for more information:
https://particles-sequential-monte-carlo-in-python.readthedocs.io/en/latest/kalman.html
However, you're right, I forgot to update the book when I made that change... Sorry.
It's not good practice to have the same class defined in two different places, so I will discard this PR.  However, if you think it's a problem, you can open an issue, and I will try to think of a way to make the same LinearGaussian class available in both modules. (Should be possible, but I need to check, especially regarding circular dependencies).

Hi,
Sorry, I did not notice that and I agree with you its not a good practice
to have same class in different places.
I will try to be more careful next time before I request any modification.
Thanks for your time.
Best regards,
Sakira
On Thu, May 27, 2021 at 6:42 PM Nicolas Chopin @.***>
wrote:

Hi,
I moved linear Gaussian state-space models to the kalman module. The
rationale is that, once you have defined such a model, you can pass it to
class Kalman to perform Kalman filtering; see here for more information:
https://particles-sequential-monte-carlo-in-python.readthedocs.io/en/latest/kalman.html
However, you're right, I forgot to update the book when I made that
change... Sorry.
It's not good practice to have the same class defined in two different
places, so I will discard this PR. However, if you think it's a problem,
you can open an issue, and I will try to think of a way to make the same
LinearGaussian class available in both modules. (Should be possible, but I
need to check, especially regarding circular dependencies).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nchopin/particles/pull/30#issuecomment-849739147, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGX3KCGZ2JZKZOVEWKYO3TTPZR6PANCNFSM45RV5ZEQ
.

no probs!


Default ssl opts to verify_peer

Forces client to either pass a list of trusted CA certificates (e.g. from the certifi package), or explicitly opt out of server certificate verification by passing verify: :verify_none.
Let's encourage safe defaults, and not make the same mistake made by many HTTP clients (cough httpc cough), giving users a false sense of security.

Pull Request Test Coverage Report for Build 191

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 79.649%

Totals

Change from base Build 190:
0.04%

Covered Lines:
454

Relevant Lines:
570

💛  - Coveralls


odd parentage for GO:2000144    positive regulation of DNA-templated transcription, initiation

GO:2000144    positive regulation of DNA-templated transcription, initiation
has the parent
GO:0031334    positive regulation of protein complex assembly?
@pgaudet  Is that intentional?
for example all mediator subunis become annotated to
GO:0031334    positive regulation of protein complex assembly
which look very odd?

I haven't much touched the Process branch yet. This parent has been there since 2010. I thik it related to the synonym 'positive regulation of DNA-dependent RNA polymerase complex assembly at promoter', which is more or less what transcription initiation is.  To be discussed with the transcription group.

Is this true though? We recently said that  members of a complex were not involved in assembly.  Isn't the assembly autonomous?

To be discussed with @colinlog

Concerning assembly and transcription: perhaps the naming 'GO:0031334 positive regulation of protein complex assembly' is confusing, but indeed, the gist of it is what Pascal stated above on Sept. 2018. As literature support I would like to invoke a passage from the summary of a chapter written by Patrick Cramer, a famed structural biologist in the field of transcription. The reference is a book:   "Molecular Biology of Assemblies and Machines by Alasdair Steven, Wolfgang Baumeister, Louise N. Johnson, Richard N. Perham". The passage reads: "In eukaryotes, the TATA box is recognized by a subunit of General Transcription Factor TFIID. TFIID and other General Transcription Factors combine with RAN polymerase II to form the pre-initiation complex (PIC) on promoter DNA. The mediator complex stabilizes the PIC and communicates signals from gene-specific transcription factors, which mainly bind upstream from the start site and can act positively (activators) or negatively (repressors)."  So, G0031334 could be re-described as  'positive regulation of protein complex formation'?  OR, perhaps much better? GO:0031334 could have a child that is defined as  'positive regulation of protein-DNA complex formation' and that could be linked to GO:2000144, breaking the  direct link between 31334 and 2000144 that rightly offends Val? Of course, a 'negative regulation ...' would then be expected as well.

@ValWood I dont see that relation- can you please check ?

I have no idea what I was looking at!


[MINOR] Log more info for closing session

Why are the changes needed?

To provide more insights that the session is closed by requests or because of idle more than timeout.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merging to 1.7.2


automatically increment bwc version

Is your feature request related to a problem? Please describe
We need to bump the bwc version in every release (example: https://github.com/opensearch-project/anomaly-detection/pull/775) because only the latest N-1.x will be upgradable to N.0 (e.g., from 2.x to 3.0) when that ships.
Known issue: https://github.com/opensearch-project/OpenSearch/issues/5076
latest development: https://github.com/opensearch-project/OpenSearch/issues/5091
Describe the solution you'd like
Could you automate bumping bwc version similar to release version (e.g., https://github.com/opensearch-project/anomaly-detection/pull/774)?
Describe alternatives you've considered
No response
Additional context
No response

Hi @kaituo,
You can do that by updating the updateVersion task in your build.gradle file. You can tell the task what all it needs to update https://github.com/opensearch-project/anomaly-detection/blob/main/build.gradle#L793-L802

I think we could use opensearch_version from gradle properties for this one. Our current version bump workflow is incrementing this version everytime and this is pretty much the same as the version used for bwc. Only difference I'm thinking right now would be the -SNAPSHOT suffix.
I could elaborate this PR https://github.com/opensearch-project/anomaly-detection/pull/778 to accommodate the changes.

Related open issue https://github.com/opensearch-project/opensearch-build/issues/2373

@prudhvigodithi @zelinh Whats the next step to move forward?

A solution added by k-nn team https://github.com/opensearch-project/k-NN/blob/2.x/build.gradle#L327, that can increment the bwc version in the same existing gradle task updateVersion, sample PR for incrementing BWC version https://github.com/opensearch-project/k-NN/pull/826/files.
@ankitkala @peternied

Closing this issue as no action item is pending from this repo. Please feel free to update the updateVersion task in order to accommodate more updates you version number in your repo. All the build-repo does is runs that tasks.


fix disks-images-provider error in ubuntu host

In ubuntu host, selinux is not enabled by default.
When starting disks-images-provider, following failure
would appear:
"can't apply partial context to unlabeled file".
Check if file selinux tag exist before use chcon.

ping @EdDev @oshoval
Can you review this PR when you have time? Thanks

/retest

/retest

/test pull-kubevirt-e2e-k8s-1.16-ceph

@oshoval I saw the PR is keep fail in "pull-kubevirt-e2e-k8s-1.16-ceph" test. Is it my PR's problem? I do not get much useful imformation from the test log file.

@zhlhahaha
Hi,
pull-kubevirt-e2e-k8s-1.16-ceph is totally broken, disregard please

@zhlhahaha
Hi,
pull-kubevirt-e2e-k8s-1.16-ceph is totally broken, disregard please

Ok, Thanks.

/approve
/retest

/release-note-none


Lua error at multiline strings in util.lua: 'Column value outside range'

Warnings that refer to the position where a multiline string ends causes errors when hover in Trouble buffer and goto doesn't work.
Small example, create a python file with following content:
1
"""
"""

To get the following warnings in the Trouble buffer:
   banana.py  3
 │     [pointless-statement] Statement seems to have no effect pylint (W0104) [1, 1]
 │     [pointless-string-statement] String statement has no effect pylint (W0105) [3, 0]
 │     [missing-module-docstring] Missing module docstring pylint (C0114) [1, 1]

When placing the cursor on the middle warning this is the error output:
Error executing vim.schedule lua callback: /home/david/.vim/plugged/trouble.nvim/lua/trouble/view.lua:465: Column value outside range
stack traceback:
        [C]: in function 'nvim_win_set_cursor'
        /home/david/.vim/plugged/trouble.nvim/lua/trouble/view.lua:465: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

When pressing <enter> on that entry, this is the error output:
E5108: Error executing lua /home/david/.vim/plugged/trouble.nvim/lua/trouble/util.lua:18: Column value outside range
stack traceback:
        [C]: in function 'nvim_win_set_cursor'
        /home/david/.vim/plugged/trouble.nvim/lua/trouble/util.lua:18: in function 'jump_to_item'
        /home/david/.vim/plugged/trouble.nvim/lua/trouble/view.lua:443: in function 'jump'
        /home/david/.vim/plugged/trouble.nvim/lua/trouble/init.lua:177: in function 'action'
        [string ":lua"]:1: in main chunk

It works fine to hover and "go to" on other warnings, it's just errors referring to last line of multiline string it seems like.

This issue appears when a language server publishes a diagnostic which has an unsupported range.position.start.character value.
In my case this diagnostic field was set to -1 when golangci-lint-langserver would report specific diagnostics, usually related to the relevant file as a whole (e.g. when said file hadn't been go fmted yet).
I resolved this by attaching a custom textDocument/publishDiagnostics handler specifically to golangci-lint-langserver during the nvim-lspconfig setup call. The custom handler changes any range.position.(start|end).character value of -1 to 0 before passing it back to the original handler:
local lspconfig = require("lspconfig")
local on_publish_diagnostics = vim.lsp.handlers["textDocument/publishDiagnostics"]
lspconfig.golangci_lint_ls.setup({
  -- <...>
  handlers = {
    -- stops an out-of-range column error when viewing diagnostics with Trouble.nvim
    ["textDocument/publishDiagnostics"] = function(_, result, ctx, config)
      for idx, diag in ipairs(result.diagnostics) do
        for position, value in pairs(diag.range) do
          if value.character == -1 then
            result.diagnostics[idx].range[position].character = 0
          end
        end
      end

      return on_publish_diagnostics(_, result, ctx, config)
    end,
  },
})

@snoord I just recently found this error too when using golangci-lint-ls. Your solution works flawlessly!

Development on the main branch is EOL.
Trouble has been rewritten and will be merged in main soon.
This issue/feature either no longer exists or has been implemented on dev.
For more info, see https://github.com/folke/trouble.nvim/tree/dev


0 candidates for SRL and SMALL for {A,B.C}LUT (in CLBM)

The 018-clbram fuzzer seems unable to find candidates for the following;
::::::::::::::
build/segbits_clbx.db
::::::::::::::
CLB.SLICE_X0.ALUT.RAM 31_16
CLB.SLICE_X0.ALUT.SMALL <0 candidates>
CLB.SLICE_X0.ALUT.SRL <0 candidates>
CLB.SLICE_X0.BLUT.RAM 31_17
CLB.SLICE_X0.BLUT.SMALL <0 candidates>
CLB.SLICE_X0.BLUT.SRL <0 candidates>
CLB.SLICE_X0.CLUT.RAM 31_46
CLB.SLICE_X0.CLUT.SMALL <0 candidates>
CLB.SLICE_X0.CLUT.SRL <0 candidates>
CLB.SLICE_X0.DLUT.RAM 31_47
CLB.SLICE_X0.DLUT.SMALL 01_59
CLB.SLICE_X0.DLUT.SRL 30_47
CLB.SLICE_X0.WA7USED 00_40
CLB.SLICE_X0.WA8USED 01_27
CLB.SLICE_X0.WEMUX.CE 01_23

Previously these seem to have been;
CLBLM_R.SLICEM_X0.ALUT.SMALL 00_04
CLBLM_R.SLICEM_X0.ALUT.SRL 30_16
CLBLM_R.SLICEM_X0.BLUT.SMALL 00_24
CLBLM_R.SLICEM_X0.BLUT.SRL 30_17
CLBLM_R.SLICEM_X0.CLUT.SMALL 00_28
CLBLM_R.SLICEM_X0.CLUT.SRL 30_46

All these bits seem to be unused by anything else in the file?

Strangely the DLUT.SMALL and DLUT.SRL are found.

FYI this is breaking prjxray-quick


Task sequence support for boundary groups vs Prefer distribution points over peers

[Enter feedback here]
Task sequence support for boundary groups
When a device runs a task sequence and needs to acquire content, it now uses boundary group behaviors similar to the Configuration Manager client.
The section states a TS behaves like a client. It seems the Boundary Group option “Prefer distribution points over peers within the same subnet" only works for a “full client”, NOT for a Task Sequence

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

ID: 2dd4b289-bd23-a3ef-f778-9d7030d6f499
Version Independent ID: b0bcb635-b4b8-ee2f-14d7-ce9f65d52982
Content: What's new in version 1810 - Configuration Manager
Content Source: sccm/core/plan-design/changes/whats-new-in-version-1810.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @franckmi for the feedback. We also need to note that behavior in the target article, https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/boundary-groups#bkmk_bgr-osd

This is fixed in the boundary groups article, closing


Update READ.ME

clarify on 1st Important note to call out that there are 2 methods for running the database generator, updated quick run header to instructions, fixed typo refert.

Thanks!


PMID:17948055

increased spatial extent of centromeric heterochromatin

increased spatial extent of centromeric heterochromatin FYPO:0004948

the 2 terms "heterochromatin assembly beyond boundary element IRC..." should be children of this? (there is also a term for the mating cassette heterochromatin boundary element IRR)

I've done those 2 as process phenotypes under "abnormal heterochromatin assembly". Want me to do the same with this new term?

it may not even be important to keep them, at least not the specific boundary element? I.e. either merge into FYPO:0004948 or merge the two terms and call it "beyond centromeric boundary element"?

oh, I really don't know if it is best to call it a "process" phenotype, or whatever the option is (structural?)

I guess maybe safer if the process is "abnormal assembly or dissassembly"?

I'm reluctant to make a process phenotype using "assembly or disassembly" -- there isn't a corresponding GO BP term, and if you can't distinguish between assembly and disassembly, it seems safest just to define the phenotype in structural terms.
It also looks like it would make sense to retain both of the existing terms, because in the session for the paper there are 3 genes annotated to FYPO:0003045, but only bdf2 is annotated to FYPO:0003046. I can either leave them pointing to the heterochromatin assembly process (which doesn't look wildly out of whack from my quick glance through the paper), or change them to structure phenotypes; no strong pref.
http://curation.pombase.org/pombe/curs/72d734a43394b9a9/ro/

I'll stick the new term in as structural for now, just so I can get the FYPO release done. Not a big deal to change it later.

aha - the GO term I was thinking of was for chromatin, not heterochromatin (GO:0006333 chromatin assembly or disassembly).
The main reason I think these term should be "together" in the ontology is if a reasearcher queries for all genes where mutants display "increased spatial extent of centromeric heterochromatin", then I think that the mutants annotated to ""heterochromatin assembly beyond boundary element IRC..." should be caught in this query too.

Would it be a huge problem if we just put assembly for the new term? That seems the likeliest anyway (even if the heterochromatin would be disassembled in wt, it has to get assembled in the first place, or it wouldn't exist).

I don't think so? Im not sure about dissambly though but I think there is a whole field about maintenance of heterochromatin (different genes etc). but I'm not sure! this part of biology is a bit meh.

OK, let's do it and see if anybody squawks ;)

edit files: fedad3dc05dbea79bf554eff4835023ad8a5ab61 & ea90b0d781dc92bfa897fd698e15197fe3b607d4
release: 154d4089fe3156b9a93a5cd829b2c555ac49371b


MsBot: Remove duplicate app insights short param, leave as-is consistent

Fixes #749

Pull Request Test Coverage Report for Build 1888

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.697%

Totals

Change from base Build 1884:
0.0%

Covered Lines:
4036

Relevant Lines:
5570

💛  - Coveralls

Other connect commands jsut receive the service name in the --serviceName parameter, without short version, so we leave all of them consistent and we reserve the possibility to add a short name for all later on as needed.


Convoy not starting, nothing in the logs

I might be having devicemapper issues, but I am getting this error when trying to start convoy.
I am just giving a summary because I am unable to copy paste right now:
driver: devicemapper, msg: "", reason: "prepare"
msg: Found created pool, skip pool reinit
msg: Cleaning up environment, pkg: daemon
msg: EOF

I have dedicated block devices for metadata and data.
Any clue what I can do to resolve this with devicemapper? Is there any way to check or rebuild the metadata ?
Running version 0.4.3

I think the data volumes might be corrupted. Is there any way to test them? Should I be able to mount the separate metadata and data volumes? I tried but that is failing. Are they ext4 ?

data volume and metadata volume are not ext4 fs, so you won't able to mount them.
You can try
dmsetup remove convoy-pool

Then try again.
Also, includes the full log may help.

Thanks for the comment. I did try removing the convoy-pool device but it appears there was some low level corruption in this pool along with a thin pool i was using for docker. In fact the docker thin pool corruption was so bad it caused a kernel panic when starting docker. I wiped the convoy pool and just started from scratch.
One comment is that LVM thin pools are the way docker recommends now. They no longer recommend devicemapper thin pool in their documentation. They appear to be better supported than devicemapper thin pools (they appear to be different somehow). There are a few tools for LVM thin pool repair but there are no such tools from devicemapper thin pool repair.
Thanks for the product!


[Feature][Transform] Source lifecycle acquisition

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
How does Transform know if the source has been executed? Because I want to use the newly added FlatMap multi line output function of Transform to achieve aggregation effect, that is, after the source is completed, the result of Transform and aggregation is output line by line to the destination
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

come here

I am not get your question.
The lifecycle is source -> transform -> sink
Only source can generate data, transform only receive the data from source.

How does Transform know if the source has been executed?
When transfrom recived data, it means sourcce has been executed.

Do you want to ask how to judge source job total complete, has read all data?

it seem can't solve it with flatmap.  It seems to be multi-line data processing.
@corgy-w cc

I am not get your question. The lifecycle is source -> transform -> sink
Only source can generate data, transform only receive the data from source.

How does Transform know if the source has been executed?

When transfrom recived data, it means sourcce has been executed.
My requirement is to customize a tansform component for grouping aggregation. Aggregate operations will be carried out after each row of data comes in, and the aggregate results will be output to sink after the source is completed

Recently I saw that tansform supports multiple lines of output, so I'm trying to see if I can implement an aggregate transform

Is there a better solution to implement aggregation operations on seatunnel, even if the parallelism is set to 1，Because I am currently facing many requirements that require aggregation operations to be implemented on the portal instead of the database side @liunaijie cc

@corgy-w is implementing multi-line transform and aggregation , You can communicate the progress

Is there a better solution to implement aggregation operations on seatunnel, even if the parallelism is set to 1，Because I am currently facing many requirements that require aggregation operations to be implemented on the portal instead of the database side @liunaijie cc

No, SeaTunnel is focus on Data integration, the flatMap  function recently support is use to explode data from one row to multiple rows.
From your description, you want the aggregation function, it's compute function, I think we are not going to support it.
cc @Hisoka-X

Is there a better solution to implement aggregation operations on seatunnel, even if the parallelism is set to 1，Because I am currently facing many requirements that require aggregation operations to be implemented on the portal instead of the database side @liunaijie cc

No, SeaTunnel is focus on Data integration, the flatMap function recently support is use to explode data from one row to multiple rows.
From your description, you want the aggregation function, it's compute function, I think we are not going to support it. cc @Hisoka-X

Yes, there is no way to solve data sharing between multiple degrees of parallelism, possibly on different nodes.


For loop never ending

Hello,
I'm using dask to analyse some images, my code looks like this :
somefunc(n):
    try:
        long calculation
        return result
    except:
         return to be filtered result

def main():
    num_image = 268828
    X = np.empty((num_image,7), dtype=np.float32)
    cluster = SLURMCluster(cores=32,
                           processes=32,
                           interface ="ib0",
                           walltime="04:10:00",
                           memory = "80GB")
    cluster.scale(600)
    client = Client(cluster)

    with tqdm (total = num_image) as pbar:
        future = client.map(somefunc, range(num_image))
        for future,result in as_completed(future,with_results = True):
            X[result[0],:] = result
            pbar.update(1)
            future.release()

    return X

if __name__ == '__main__':

    x = main()
    io.savemat('/gpfs/home/savedata.mat', {'data': x})

The scripts very well excepts for some iterations and it stays stuck without doing some iterations
100%|█████████▉| 268711/268828 [3:40:11<00:31,  3.68it/s]
Looking at the log files I found that it first looped on a first error :
Traceback (most recent call last):
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/tornado/ioloop.py", line 743, in _run_callback
    ret = callback()
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/tornado/ioloop.py", line 767, in _discard_future_result
    future.result()
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/worker.py", line 875, in heartbeat
    metrics=await self.get_metrics(),
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/core.py", line 747, in send_recv_from_rpc
    comm = await self.pool.connect(self.addr)
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/core.py", line 874, in connect
    connection_args=self.connection_args,
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/comm/core.py", line 227, in connect
    _raise(error)
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/comm/core.py", line 204, in _raise
    raise IOError(msg)
OSError: Timed out trying to connect to 'tcp://<IP_ADDRESS>:16892' after 10 s: in <distributed.comm.tcp.TCPConnector object at 0x2b1a8a2bc630>: ConnectionRefusedError: [Errno 111] Connection refused
tornado.application - ERROR - Exception in callback functools.partial(<bound method IOLoop._discard_future_result of <tornado.platform.asyncio.AsyncIOLoop object at 0x2b1a32811c88>>, <Task finished coro=<Worker.heartbeat() done, defined at /gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/worker.py:866> exception=OSError("Timed out trying to connect to 'tcp://<IP_ADDRESS>:16892' after 10 s: in <distributed.comm.tcp.TCPConnector object at 0x2b1a8a346c50>: ConnectionRefusedError: [Errno 111] Connection refused",)>)
Traceback (most recent call last):
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/comm/core.py", line 215, in connect
    quiet_exceptions=EnvironmentError,
tornado.util.TimeoutError: Timeout

And then I think it's when the wall time as been reached it loops on another one :
Traceback (most recent call last):
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/tornado/ioloop.py", line 907, in _run
    return self.callback()
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/worker.py", line 857, in <lambda>
    lambda: self.batched_stream.send({"op": "keep-alive"}),
  File "/gpfs/home/maxlavaud/miniconda3/envs/env_dask/lib/python3.6/site-packages/distributed/batched.py", line 117, in send
    raise CommClosedError
distributed.comm.core.CommClosedError

Also I've been warned that there is some process emited by dask that are using a lot of memory (10-100MB)  on the login node, I don't quit understand where do they come from.

I don't have any suggestions of the top of my head. Can you post the dask, distributed and dask-jobqueue versions for future references?
If you are able to reproduce with LocalCluster (or with SLURMCluster but a ) that might help other people debug the problem further. Also something I would try (just in case) would be to make sure to use the latest releeased versions of dask, distributed and dask-jobqueue.

Also I've been warned that there is some process emited by dask that are using a lot of memory (10-100MB) on the login node, I don't quit understand where do they come from.

If you are running your main script on the login node, that may be expected. Your X is already 7MB big, plus your dask scheduler lives on the same node as you are launching your main script. 10-100MB does not seem a lot but if it is too much for your cluster policy, an easy work-around is to launch your main script from an interactive job.

I have the 2.3.0 version of dask (installed from conda) and 0.6.3 version of dask-jobqueue.
This problem seems to arise when i do a lot of iterations so it might not be possible with LocalCluster

an easy work-around is to launch your main script from an interactive job.

I don't find any documentations on that, when i try to lunch it from an interactive node i get the error : sbatch: error: Batch job submission failed: Access/permission denied
So i understand that we can't use the sbatch command inside a computing node, do we have to replace this command by another one ? Or is this that we have to change :shebang: "#!/usr/bin/env bash" ?

I don't find any documentations on that, when i try to lunch it from an interactive node i get the error : sbatch: error: Batch job submission failed: Access/permission denied

This indeed sounds like submissions from compute nodes are not possible.  Are you in touch with any of your cluster admins about this?

So i understand that we can't use the sbatch command inside a computing node, do we have to replace this command by another one ? Or is this that we have to change :shebang: "#!/usr/bin/env bash" ?

No, the shebang doesn't have any impact here.  As the job script that contains it isn't even submitted.

If you are running your main script on the login node, that may be expected. Your X is already 7MB big, plus your dask scheduler lives on the same node as you are launching your main script. 10-100MB does not seem a lot but if it is too much for your cluster policy, an easy work-around is to launch your main script from an interactive job.

I miss spelled it's using 10-100**GB** of memory (event when jobs are still pending).

I don't find any documentations on that, when i try to lunch it from an interactive node i get the error : sbatch: error: Batch job submission failed: Access/permission denied

This indeed sounds like submissions from compute nodes are not possible. Are you in touch with any of your cluster admins about this?

Indeed i talk with an admin today, they've got some problems with some code which generated infinite loops of sbatch so we don't have the permission to use it from the compute nodes.

Indeed i talk with an admin today, they've got some problems with some code which generated infinite loops of sbatch so we don't have the permission to use it from the compute nodes.

Wow yet another possible quirk in the phase-space of cluster configurations ... sorry to hear that ... A work-around you could do (this comes from OAR where the submission command is not installed on computing nodes):
cluster = SLURMCluster(...)
cluster.submit_command = 'ssh your_login_node sbatch'
# Hopefully you can use qdel from a computing node otherwise uncomment the following line
# cluster.cancel_command = 'ssh your_login_node qdel'

This is a bit hacky but this could work ...

I miss spelled it's using 10-100GB of memory (even when jobs are still pending).

This is unexpected, probably not related to dask but to the objects you are creating in your script. If I was to debug this problem I would remove the dask-related part and see how much memory the script is using. If you still think that this is related to dask, a stand-alone snippet reproducing the problem is needed.

@eXpensia were you able to solve this problem?

@eXpensia did you find a solution to your Original Problem where some iterations were never ending?

Hello,
Actually no, I think it was due to a memory leak that I wasn't able to
find, used an another to compute what I needed and I don't need anymore
parallelization.
Le sam. 1 févr. 2020 à 22:38, Guillaume Eynard-Bontemps <
<EMAIL_ADDRESS>a écrit :

@eXpensia https://github.com/eXpensia did you find a solution to your
Original Problem where some iterations were never ending?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/issues/333?email_source=notifications&email_token=AK5DCZFZASHKXX42XWURKQTRAXTWNA5CNFSM4IUGH4O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRHITA#issuecomment-581071948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5DCZGTHAH23675RYTOIY3RAXTWNANCNFSM4IUGH4OQ
.

Out of curiosity, could you tell us what other thing did you use for your computation?

Sure, basically what i'm doing is fitting 2D images to track particles. And a group which is using the same technique implemented it with cython and cupy (or numba if no GPU available) which permits to do it as fast as 500 cores but with only one machine :)
You can find the code here :
https://github.com/davidgrier/pylorenzmie

Nice example of optimization !


Server Reports: Top 10 DB Space Usage graph is empty

Azure Data Studio Version:
1.14.1

Steps to Reproduce:

I have a SQL database hosted in Azure. (It is a Standard S0 instance).
I connect to the database (I can do all the normal ADS operations like query, edit etc)
I have installed the Server Reports extension (v0.2.1) and when I click Manage then Server Reports, Only the Top 10 DB Buffer Usage is filled in. The other tables on the page are not filled in.

Why won't it show the Top 10 DB Space Usage graph?
I installed Server Reports because I am trying to figure out the size of all the tables in my database since it seems to have jumped in total size recently.

First off - the Server Reports extension doesn't report table space usage. Just database level. So if you're specifically looking for which tables are the largest you'll need to use your own queries for that.
But if you still wanted to see the database size then currently you'll have to use some other method to determine that as the query used isn't compatible with SQL Azure. You can run your own query by following the instructions here though (modifying as desired to show the databases that you're interested in).


WIP: Fix compatibility gles3 driver loading GL_TEXTURE_2D_ARRAY and bptc rgba pixel size

fixes https://github.com/godotengine/godot/issues/91365
fix compatibility gles3 driver loading GL_TEXTURE_2D_ARRAY and bptc rgba pixel size.

probably has something to do with https://www.khronos.org/opengl/wiki/ASTC_Texture_Compression ?

still need to investigate a bit more on correct  get_format_pixel_size values


[BUG] External authentication with LinkedIn doesn't work

The deno-slack versions

"deno-slack-sdk/"<EMAIL_ADDRESS>"deno-slack-api/"<EMAIL_ADDRESS>
Deno runtime version

deno 1.42.1 (release, aarch64-apple-darwin)
v8 <IP_ADDRESS>
typescript 5.4.3

OS info

ProductName:            macOS
ProductVersion:         14.4.1
BuildVersion:           23E224
Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103

Describe the bug

When implementing DefineOAuth2Provider with LinkedIn, the authorization fails with
    oauth2_exchange_error
                scope_mismatch_error: provider and token scopes do not match

Steps to reproduce

My OAuth 2 provider is defined as follows:

import { DefineOAuth2Provider, Schema } from "deno-slack-sdk/mod.ts";

const LinkedInProvider = DefineOAuth2Provider({
  provider_key: "linkedin",
  provider_type: Schema.providers.oauth2.CUSTOM,
  options: {
    provider_name: "LinkedIn",
    authorization_url: "https://www.linkedin.com/oauth/v2/authorization",
    token_url: "https://www.linkedin.com/oauth/v2/accessToken",
    client_id: CLIENT_ID,
    scope: [
      "email",
      "openid",
      "profile",
      "w_member_social",
    ],
    authorization_url_extras: {
      prompt: "consent",
      access_type: "offline",
    },
    identity_config: {
      url: "https://api.linkedin.com/v2/userinfo",
      account_identifier: "$.sub",
      http_method_type: "GET",
    },
    use_pkce: false,
  },
});

export default LinkedInProvider;

I've configured a message trigger that sends a button in a chat. This button then triggers a workflow that has an input of
linkedin_access_token_id: {
      credential_source: "END_USER",
    },

The LinkedIn popup appears as expected, but when approving the request the console reports the following error

    oauth2_exchange_error
                scope_mismatch_error: provider and token scopes do not match

Expected result
The authentication should succeed.

Actual result
The authentication fails.

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Can you share your workflow and trigger definitions, please?

The workflow
import { DefineWorkflow, Schema } from "deno-slack-sdk/mod.ts";
import { LinkedInPostFunctionDefinition } from "../functions/_linkedin_post.ts";

const PostWorkflow = DefineWorkflow({
  callback_id: "_post",
  title: " a Post",
  description: " a Post",
  input_parameters: {
    properties: {
      message: {
        type: Schema.types.string,
        description: "The message",
      },
      user_id: {
        type: Schema.slack.types.user_id,
        description: "The user id",
      },
    },
    required: ["message", "user_id"],
  },
});

const Step = PostWorkflow.addStep(
  LinkedInPostFunctionDefinition,
  {
    linkedin_access_token_id: {
      credential_source: "END_USER",
    },
    message: PostWorkflow.inputs.message,
    user_id: PostWorkflow.inputs.user_id,
  },
);

PostWorkflow.addStep(Schema.slack.functions.SendDm, {
  user_id: PostWorkflow.inputs.user_id,
  message:
    `Finished with ${Step.outputs.data}, error: ${Step.outputs.error}`,
});

export default PostWorkflow;

The trigger
import { Trigger } from "deno-slack-api/types.ts";
import { TriggerContextData, TriggerTypes } from "deno-slack-api/mod.ts";
import PostWorkflow from "../workflows/_post_link.ts";

const trigger: Trigger<typeof PostWorkflow.definition> = {
  type: TriggerTypes.Shortcut,
  name: "Linkedin post",
  description: "Responds to a linkedin post",
  workflow: `#/workflows/${PostWorkflow.definition.callback_id}`,
  inputs: {
    message: {
      customizable: true,
    },
    user_id: {
      value: TriggerContextData.Shortcut.user_id,
    },
  },
};

export default trigger;

I can confirm this issue. I will engage the backend 3P Auth team at Slack to see what the issue is.

We have identified the problem. The response from LinkedIn's token-exchange API is not exactly to the OAuth RFC spec (the scopes field should be space delimited, whereas LinkedIn's response is comma-delimited). Thus the error around scope mismatch.
We are working on a fix! Will keep you posted as to progress there.

Hey @liorp , the fix was merged a couple hours ago and is deployed to production. I verified on my end that this now works 🎉
Going to close this, but if it's not working for you, feel free to re-open this issue or file a new one.


Relabeled button plus fixed some issues with Indigenous identity popup

Changed the label of the Go back button after Reconfirm interest.
I had some records that had a number for their history object. This was preventing the Are you Indigenous popup from closing, and locked me out of the PEOI portal. Included are some minor fixes that helped with that issue, but we should probably add the ability to close the popup to give the user the ability to get out if this issue shows up on prod.

@fwpushan Decided against making code changes for the history-as-integer issue as we didn't see any occurences of that data in prod.
I think leaving the form open with an error popping up is okay behaviour and updating the integers to nulls in your local db is the best option


Implement ADES web front-end to back-end HySDS cluster

Acceptance Criteria

Ability to deploy an algorithm to HySDS
Ability to request a job execution in HySDS
Ability to request job status from HySDS
Ability to see all jobs statuses in the hySDS for a given algorithm
Deployment diagram (e.g. what is needed for this to run, is it a per-tenant deployment, or shared across many tenants)

System tests being added at https://github.com/unity-sds/unity-system-test/pull/7

This Epic has been descoped to NOT include the deployment endpoint. A new Epic will be created for the next release to include that.

Job execution working. Improvements will be addresses in the next U-SPS release.


Add doctype for Contact

As we want Contacts#index to be powered for a Finder and want to put contacts into the search index, this commit adds a Contact doctype. There's probably more information we should add to this at a later
date when we better understand what Users might try searching to find a Contact.

This looks fine as far as I know, but I don't know what a "contact_group" is.  We don't have a clear place to put descriptions of fields - could you perhaps add a description of what the contact_group field contains and add it to the commit message?  That way we should be able to find the description of it in future.

@rboulton Done.


Expand species list to include all GRIIS species

Get data from cube

Make species list based on ...

T0, T1 => Spread

De cube wordt in dit script gesubset ?
https://github.com/inbo/IAS_Species_Dashboard/blob/3_version1.0/R-scripts/data_prep.Rmd
=> Na te kijken


style.css missing 'upvotable' and 'disabled' class

in client/templates/posts/post_item.js, you have:
    if (userId && !_.include(this.upvoters, userId)) {
      return 'btn-primary upvotable';
    } else {
      return 'disabled';

It looks like you might have dropped the upvotable and disabled classes from style.css. https://github.com/DiscoverMeteor/Microscope/commit/a6943412644b733ad4e17b3fd3f2c3b01df56bae``
  .post .upvote {
    display: block;
    margin: 7px 12px 0 0;
    float: left; }

(Apologies in advance if I am wrong or am looking at the wrong css file to look for those classes)

No bug.
Closing because I just didn't understand the css.
disabled is a default attribute of the button selector and doesn't need to be defined in style.css
upvotable is not in the style.css on purpose. It's just an extra class that doesn't change the display.


Create example and tests for Struct

Create test file for testing decode and encode methods with struct values.
Create example file for struct type

Resolved and merged with #119 .


Additional ARIA accessibility issues

The Accessibility Developer Tools for Chrome has reported these two issues. Running 4.0.0-rc1.
[Severe] ARIA attributes which refer to other elements by ID should refer to elements which exist in the DOM
<span class="select2-selection select2-selection--single" role="combobox" aria-autocomplete="list" aria-haspopup="true" aria-expanded="false" tabindex="0" aria-owns="select2-edit-select-service-results" aria-labelledby="select2-edit-select-service-container">
  ...
</span>

[Severe] Controls and media elements should have labels
See AX_TEXT_01 for more information.
<input class="select2-search__field" type="search" tabindex="0" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false" role="textbox">

As far as I can tell the solution for the first issue would be to remove the "aria-owns" attribute until the results container exists, or force the results container to always exist but show / hide it as required.
Second issue needs either aria-labelledby or aria-label.

I think if you remove the aria-owns attribute you also have to remove the aria-haspopup attribute. Maybe also the aria-expanded attribute.