[Prototype] Gradle.

This PR is work in progress.
This PR is an attempt to use gradle to build some of Java SDK packages.

API change check for com.azure.resourcemanager:azure-resourcemanager-loganalytics
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-loganalytics

API change check for com.azure.resourcemanager:azure-resourcemanager-batch
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-batch

API change check for com.azure.resourcemanager:azure-resourcemanager-cognitiveservices
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-cognitiveservices

API change check for com.azure:azure-search-documents
API changes are not detected in this pull request for com.azure:azure-search-documents

API change check for com.azure:azure-identity
API changes are not detected in this pull request for com.azure:azure-identity

API change check for com.azure:azure-messaging-servicebus
API changes are not detected in this pull request for com.azure:azure-messaging-servicebus

API change check for com.azure:azure-security-keyvault-administration
API changes are not detected in this pull request for com.azure:azure-security-keyvault-administration

API change check for com.azure:azure-security-keyvault-certificates
API changes have been detected in com.azure:azure-security-keyvault-certificates. You can review API changes here
API changes
-         opens com.azure.security.keyvault.certificates to com.azure.core, com.fasterxml.jackson.databind;
-         opens com.azure.security.keyvault.certificates.implementation to com.azure.core, com.fasterxml.jackson.databind;
-         opens com.azure.security.keyvault.certificates.models to com.azure.core, com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.certificates to com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.certificates.implementation to com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.certificates.models to com.fasterxml.jackson.databind;

API change check for com.azure:azure-messaging-eventhubs
API changes have been detected in com.azure:azure-messaging-eventhubs. You can review API changes here
API changes
-     public class EventData extends MessageContent {
-         public EventData()
+     public class EventData {
-         @Override public BinaryData getBodyAsBinaryData()
-         @Override public EventData setBodyAsBinaryData(BinaryData binaryData)
+         public BinaryData getBodyAsBinaryData()

API change check for com.azure:azure-sdk-template
API changes are not detected in this pull request for com.azure:azure-sdk-template

API change check for com.azure:azure-messaging-eventgrid
API changes are not detected in this pull request for com.azure:azure-messaging-eventgrid

API change check for com.azure:azure-security-keyvault-jca
API changes are not detected in this pull request for com.azure:azure-security-keyvault-jca

API change check for com.azure:azure-messaging-eventhubs-checkpointstore-blob
API changes are not detected in this pull request for com.azure:azure-messaging-eventhubs-checkpointstore-blob

API change check for com.azure:azure-sdk-template-two
API changes are not detected in this pull request for com.azure:azure-sdk-template-two

API change check for com.azure.resourcemanager:azure-resourcemanager-mediaservices
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-mediaservices

API change check for com.azure:azure-messaging-eventgrid-cloudnative-cloudevents
API changes are not detected in this pull request for com.azure:azure-messaging-eventgrid-cloudnative-cloudevents

API change check for com.azure:azure-security-keyvault-keys
API changes have been detected in com.azure:azure-security-keyvault-keys. You can review API changes here

API change check for com.azure:azure-ai-textanalytics
API changes are not detected in this pull request for com.azure:azure-ai-textanalytics

API change check for com.azure.resourcemanager:azure-resourcemanager-eventgrid
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-eventgrid

API change check for com.azure:azure-sdk-template-three
API changes are not detected in this pull request for com.azure:azure-sdk-template-three

API change check for com.azure:azure-security-keyvault-secrets
API changes have been detected in com.azure:azure-security-keyvault-secrets. You can review API changes here
API changes
-         opens com.azure.security.keyvault.secrets to com.azure.core, com.fasterxml.jackson.databind;
-         opens com.azure.security.keyvault.secrets.implementation to com.azure.core, com.fasterxml.jackson.databind;
-         opens com.azure.security.keyvault.secrets.models to com.azure.core, com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.secrets to com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.secrets.implementation to com.fasterxml.jackson.databind;
+         opens com.azure.security.keyvault.secrets.models to com.fasterxml.jackson.databind;

API change check for com.azure.resourcemanager:azure-resourcemanager-mysql
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-mysql

API change check for com.azure.resourcemanager:azure-resourcemanager-recoveryservices
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-recoveryservices

API change check for com.azure.resourcemanager:azure-resourcemanager-sqlvirtualmachine
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-sqlvirtualmachine

API change check for com.azure:azure-core
API changes are not detected in this pull request for com.azure:azure-core

API change check for com.azure:azure-core-amqp
API changes are not detected in this pull request for com.azure:azure-core-amqp

API change check for com.azure.resourcemanager:azure-resourcemanager-healthbot
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-healthbot

API change check for com.azure.resourcemanager:azure-resourcemanager-costmanagement
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-costmanagement

API change check for com.azure:azure-core-amqp-experimental
API changes are not detected in this pull request for com.azure:azure-core-amqp-experimental

API change check for com.azure.resourcemanager:azure-resourcemanager-postgresql
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-postgresql

API change check for com.azure:azure-core-experimental
API changes are not detected in this pull request for com.azure:azure-core-experimental

API change check for com.azure:azure-core-http-jdk-httpclient
API changes are not detected in this pull request for com.azure:azure-core-http-jdk-httpclient

API change check for com.azure:azure-core-http-netty
API changes are not detected in this pull request for com.azure:azure-core-http-netty

API change check for com.azure.resourcemanager:azure-resourcemanager-relay
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-relay

API change check for com.azure:azure-core-http-okhttp
API changes are not detected in this pull request for com.azure:azure-core-http-okhttp

API change check for com.azure:azure-data-tables
API changes are not detected in this pull request for com.azure:azure-data-tables

API change check for com.azure:azure-core-serializer-avro-apache
API changes are not detected in this pull request for com.azure:azure-core-serializer-avro-apache

API change check for com.azure:azure-monitor-opentelemetry-exporter
API changes are not detected in this pull request for com.azure:azure-monitor-opentelemetry-exporter

API change check for com.azure:azure-digitaltwins-core
API changes are not detected in this pull request for com.azure:azure-digitaltwins-core

API change check for com.azure:azure-core-serializer-json-gson
API changes are not detected in this pull request for com.azure:azure-core-serializer-json-gson

API change check for com.azure:azure-ai-anomalydetector
API changes are not detected in this pull request for com.azure:azure-ai-anomalydetector

API change check for com.azure:azure-data-schemaregistry-apacheavro
API changes have been detected in com.azure:azure-data-schemaregistry-apacheavro. You can review API changes here

API change check for com.azure:azure-analytics-synapse-artifacts
API changes are not detected in this pull request for com.azure:azure-analytics-synapse-artifacts

API change check for com.azure.resourcemanager:azure-resourcemanager-hybridkubernetes
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-hybridkubernetes

API change check for com.azure:azure-ai-metricsadvisor
API changes are not detected in this pull request for com.azure:azure-ai-metricsadvisor

API change check for com.azure.resourcemanager:azure-resourcemanager-digitaltwins
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-digitaltwins

API change check for com.azure:azure-monitor-query
API changes are not detected in this pull request for com.azure:azure-monitor-query

API change check for com.azure.resourcemanager:azure-resourcemanager-resourcemover
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-resourcemover

API change check for com.azure.resourcemanager:azure-resourcemanager-confluent
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-confluent

API change check for com.azure.resourcemanager:azure-resourcemanager-redisenterprise
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-redisenterprise

API change check for com.azure:azure-data-appconfiguration
API changes have been detected in com.azure:azure-data-appconfiguration. You can review API changes here
API changes
-         opens com.azure.data.appconfiguration.implementation to com.azure.core, com.fasterxml.jackson.databind;
-         opens com.azure.data.appconfiguration.models to com.azure.core, com.fasterxml.jackson.databind;
+         opens com.azure.data.appconfiguration.implementation to com.fasterxml.jackson.databind;
+         opens com.azure.data.appconfiguration.models to com.fasterxml.jackson.databind;

API change check for com.azure.resourcemanager:azure-resourcemanager-hdinsight
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-hdinsight

API change check for com.azure:azure-core-test
API changes are not detected in this pull request for com.azure:azure-core-test

API change check for com.azure:azure-analytics-synapse-monitoring
API changes are not detected in this pull request for com.azure:azure-analytics-synapse-monitoring

API change check for com.azure:azure-core-tracing-opentelemetry
API changes are not detected in this pull request for com.azure:azure-core-tracing-opentelemetry

API change check for com.azure.spring:azure-spring-cloud-appconfiguration-config-web
API changes are not detected in this pull request for com.azure.spring:azure-spring-cloud-appconfiguration-config-web

API change check for com.azure.spring:azure-spring-cloud-feature-management
API changes are not detected in this pull request for com.azure.spring:azure-spring-cloud-feature-management

API change check for com.azure:azure-mixedreality-authentication
API changes are not detected in this pull request for com.azure:azure-mixedreality-authentication

API change check for com.azure.spring:azure-spring-cloud-feature-management-web
API changes are not detected in this pull request for com.azure.spring:azure-spring-cloud-feature-management-web

API change check for com.azure.spring:spring-cloud-azure-service
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-service

API change check for com.azure.resourcemanager:azure-resourcemanager-attestation
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-attestation

API change check for com.azure.spring:spring-cloud-azure-resourcemanager
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-resourcemanager

API change check for com.azure.spring:spring-cloud-azure-trace-sleuth
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-trace-sleuth

API change check for com.azure.spring:spring-messaging-azure-eventhubs
API changes are not detected in this pull request for com.azure.spring:spring-messaging-azure-eventhubs

API change check for com.azure.spring:spring-messaging-azure-servicebus
API changes are not detected in this pull request for com.azure.spring:spring-messaging-azure-servicebus

API change check for com.azure.spring:spring-messaging-azure-storage-queue
API changes are not detected in this pull request for com.azure.spring:spring-messaging-azure-storage-queue

API change check for com.azure.resourcemanager:azure-resourcemanager-storagecache
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-storagecache

API change check for com.azure:azure-quantum-jobs
API changes are not detected in this pull request for com.azure:azure-quantum-jobs

API change check for com.azure.spring:spring-integration-azure-core
API changes are not detected in this pull request for com.azure.spring:spring-integration-azure-core

API change check for com.azure.spring:spring-integration-azure-eventhubs
API changes are not detected in this pull request for com.azure.spring:spring-integration-azure-eventhubs

API change check for com.azure.spring:spring-integration-azure-servicebus
API changes are not detected in this pull request for com.azure.spring:spring-integration-azure-servicebus

API change check for com.azure.spring:spring-cloud-azure-autoconfigure
API changes have been detected in com.azure.spring:spring-cloud-azure-autoconfigure. You can review API changes here
API changes
-         public static final String DEFAULT_CREDENTIAL_TASK_EXECUTOR_BEAN_NAME = "springCloudAzureCredentialTaskExecutor";
-         public static final String DEFAULT_CREDENTIAL_THREAD_NAME_PREFIX = "az-identity-";
-     @AutoConfigureAfter

API change check for com.azure.spring:spring-cloud-azure-actuator
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-actuator

API change check for com.azure.spring:spring-cloud-azure-actuator-autoconfigure
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-actuator-autoconfigure

API change check for com.azure.spring:spring-cloud-azure-stream-binder-servicebus
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-stream-binder-servicebus

API change check for com.azure.resourcemanager:azure-resourcemanager-netapp
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-netapp

API change check for com.azure.spring:spring-cloud-azure-stream-binder-eventhubs
API changes are not detected in this pull request for com.azure.spring:spring-cloud-azure-stream-binder-eventhubs

API change check for com.azure:azure-iot-deviceupdate
API changes are not detected in this pull request for com.azure:azure-iot-deviceupdate

API change check for com.azure.resourcemanager:azure-resourcemanager-kubernetesconfiguration
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-kubernetesconfiguration

API change check for com.azure.resourcemanager:azure-resourcemanager-changeanalysis
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-changeanalysis

API change check for com.azure.resourcemanager:azure-resourcemanager-datadog
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-datadog

API change check for com.azure.resourcemanager:azure-resourcemanager-apimanagement
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-apimanagement

API change check for com.azure.resourcemanager:azure-resourcemanager-resourcehealth
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-resourcehealth

API change check for com.azure.resourcemanager:azure-resourcemanager-azurestackhci
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-azurestackhci

API change check for com.azure.resourcemanager:azure-resourcemanager-delegatednetwork
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-delegatednetwork

API change check for com.azure.resourcemanager:azure-resourcemanager-advisor
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-advisor

API change check for com.azure.resourcemanager:azure-resourcemanager-azurestack
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-azurestack

API change check for com.azure.resourcemanager:azure-resourcemanager
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager. You can review API changes here

API change check for com.azure:azure-spring-data-cosmos
API changes are not detected in this pull request for com.azure:azure-spring-data-cosmos

API change check for com.azure.resourcemanager:azure-resourcemanager-appplatform
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-appplatform. You can review API changes here

API change check for com.azure:azure-cosmos-encryption
API changes are not detected in this pull request for com.azure:azure-cosmos-encryption

API change check for com.azure:azure-containers-containerregistry
API changes are not detected in this pull request for com.azure:azure-containers-containerregistry

API change check for com.azure.resourcemanager:azure-resourcemanager-resourcegraph
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-resourcegraph

API change check for com.azure.resourcemanager:azure-resourcemanager-authorization
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-authorization. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-compute
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-compute. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-containerinstance
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-containerinstance

API change check for com.azure.resourcemanager:azure-resourcemanager-consumption
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-consumption

API change check for com.azure.resourcemanager:azure-resourcemanager-batchai
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-batchai

API change check for com.azure.resourcemanager:azure-resourcemanager-containerregistry
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-containerregistry. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-containerservice
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-containerservice. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-cosmos
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-cosmos

API change check for com.azure.resourcemanager:azure-resourcemanager-keyvault
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-keyvault. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-monitor
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-monitor

API change check for com.azure.resourcemanager:azure-resourcemanager-network
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-network. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-privatedns
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-privatedns

API change check for com.azure.resourcemanager:azure-resourcemanager-redis
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-redis

API change check for com.azure.resourcemanager:azure-resourcemanager-samples
API review is created for com.azure.resourcemanager:azure-resourcemanager-samples. You can review APIs here.

API change check for com.azure.resourcemanager:azure-resourcemanager-search
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-search

API change check for com.azure.resourcemanager:azure-resourcemanager-sql
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-sql

API change check for com.azure.resourcemanager:azure-resourcemanager-devspaces
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-devspaces

API change check for com.azure.resourcemanager:azure-resourcemanager-storage
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-storage. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-devtestlabs
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-devtestlabs

API change check for com.azure.resourcemanager:azure-resourcemanager-hanaonazure
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-hanaonazure

API change check for com.azure.resourcemanager:azure-resourcemanager-hybridcompute
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-hybridcompute

API change check for com.azure.resourcemanager:azure-resourcemanager-healthcareapis
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-healthcareapis

API change check for com.azure.resourcemanager:azure-resourcemanager-machinelearningservices
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-machinelearningservices

API change check for com.azure.resourcemanager:azure-resourcemanager-peering
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-peering

API change check for com.azure.resourcemanager:azure-resourcemanager-mariadb
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-mariadb

API change check for com.azure.resourcemanager:azure-resourcemanager-policyinsights
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-policyinsights

API change check for com.azure.resourcemanager:azure-resourcemanager-maintenance
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-maintenance

API change check for com.azure.resourcemanager:azure-resourcemanager-deploymentmanager
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-deploymentmanager

API change check for com.azure.resourcemanager:azure-resourcemanager-powerbidedicated
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-powerbidedicated

API change check for com.azure.resourcemanager:azure-resourcemanager-storageimportexport
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-storageimportexport

API change check for com.azure.resourcemanager:azure-resourcemanager-applicationinsights
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-applicationinsights

API change check for com.azure.resourcemanager:azure-resourcemanager-notificationhubs
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-notificationhubs

API change check for com.azure.resourcemanager:azure-resourcemanager-marketplaceordering
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-marketplaceordering

API change check for com.azure.resourcemanager:azure-resourcemanager-streamanalytics
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-streamanalytics

API change check for com.azure.resourcemanager:azure-resourcemanager-timeseriesinsights
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-timeseriesinsights

API change check for com.azure.resourcemanager:azure-resourcemanager-operationsmanagement
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-operationsmanagement

API change check for com.azure.resourcemanager:azure-resourcemanager-managedapplications
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-managedapplications

API change check for com.azure.resourcemanager:azure-resourcemanager-datalakeanalytics
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-datalakeanalytics

API change check for com.azure.resourcemanager:azure-resourcemanager-botservice
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-botservice

API change check for com.azure.resourcemanager:azure-resourcemanager-videoanalyzer
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-videoanalyzer

API change check for com.azure.resourcemanager:azure-resourcemanager-recoveryservicesbackup
API changes have been detected in com.azure.resourcemanager:azure-resourcemanager-recoveryservicesbackup. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-postgresqlflexibleserver
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-postgresqlflexibleserver

API change check for com.azure:azure-security-confidentialledger
API changes are not detected in this pull request for com.azure:azure-security-confidentialledger

API change check for com.azure.resourcemanager:azure-resourcemanager-mysqlflexibleserver
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-mysqlflexibleserver

API change check for com.azure.resourcemanager:azure-resourcemanager-elastic
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-elastic

API change check for com.azure.resourcemanager:azure-resourcemanager-maps
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-maps

API change check for com.azure:azure-verticals-agrifood-farming
API changes are not detected in this pull request for com.azure:azure-verticals-agrifood-farming

API change check for com.azure.resourcemanager:azure-resourcemanager-imagebuilder
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-imagebuilder

API change check for com.azure.resourcemanager:azure-resourcemanager-hybridnetwork
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-hybridnetwork

API change check for com.azure:azure-ai-documenttranslator
API changes are not detected in this pull request for com.azure:azure-ai-documenttranslator

API change check for com.azure:azure-aot-graalvm-support
API changes are not detected in this pull request for com.azure:azure-aot-graalvm-support

API change check for com.azure:azure-analytics-purview-catalog
API changes are not detected in this pull request for com.azure:azure-analytics-purview-catalog

API change check for com.azure:azure-aot-graalvm-support-netty
API changes are not detected in this pull request for com.azure:azure-aot-graalvm-support-netty

API change check for com.azure.resourcemanager:azure-resourcemanager-storagepool
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-storagepool

API change check for com.azure:azure-analytics-purview-scanning
API changes are not detected in this pull request for com.azure:azure-analytics-purview-scanning

API change check for com.azure.resourcemanager:azure-resourcemanager-dataprotection
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-dataprotection

API change check for com.azure.resourcemanager:azure-resourcemanager-automanage
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-automanage

API change check for com.azure.resourcemanager:azure-resourcemanager-loadtestservice
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-loadtestservice

API change check for com.azure.resourcemanager:azure-resourcemanager-edgeorder
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-edgeorder

API change check for com.azure.resourcemanager:azure-resourcemanager-desktopvirtualization
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-desktopvirtualization

API change check for com.azure.resourcemanager:azure-resourcemanager-dnsresolver
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-dnsresolver

API change check for com.azure.resourcemanager:azure-resourcemanager-securityinsights
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-securityinsights

API change check for com.azure.resourcemanager:azure-resourcemanager-communication
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-communication

API change check for com.azure:azure-communication-callingserver
API changes are not detected in this pull request for com.azure:azure-communication-callingserver

API change check for com.azure:azure-communication-identity
API changes are not detected in this pull request for com.azure:azure-communication-identity

API change check for com.azure:azure-communication-sms
API changes are not detected in this pull request for com.azure:azure-communication-sms

API change check for com.azure.resourcemanager:azure-resourcemanager-azureadexternalidentities
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-azureadexternalidentities

API change check for com.azure.resourcemanager:azure-resourcemanager-mobilenetwork
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-mobilenetwork

API change check for com.azure:azure-communication-chat
API changes are not detected in this pull request for com.azure:azure-communication-chat

API change check for com.azure.resourcemanager:azure-resourcemanager-servicelinker
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-servicelinker

API change check for com.azure.resourcemanager:azure-resourcemanager-vmwarecloudsimple
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-vmwarecloudsimple


CF seems to be restaging this bot because of failed health checks

the metrics number are getting inflated because of this

It looks like this is no longer happening due to fixes in the deploy.


Graph visualization

Finish code from #17 for visualizing graphs.
Basically just need to determine the right way to handle import errors for graphviz, since I don't want graphviz to be a requirement for ffmpeg-python.

try:
    import
except ImportError:
    doStuff()

?

Or you can put everything in a module named something like _view, then in the view module simply do from ._view import * in a try except.
This would be a cleaner solution, probably.

Yeah good ideas. I moved the import graphviz into the body of the view() function - that way it doesn't even attempt to import graphviz until it really needs it, and then fails with a helpful error message if it's unavailable.
See #21

Merged #18.


Updated Kubernetes Release to v1.15.1 for 1-27

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/hold Will need to rebase with a pending merge conflict


Ideas for Thaumic Potatoes 2.

If this isn't the right way to suggest things reply with what is. Twitch seems to think no one can read more than a paragraph these days.
I have some ideas for future content (and some lore to go with them) if you're interested:
Potatarmor = Constructing and armor set from Potato Alloy Ingots has some interesting properties the seem to come from infusing its bearer with the essence of life. Each unit of the armor has an effect of its own and the set unifies to nourish the user. The helmet grants Night Vision. The chestplate grants Strength. The leggings grant Jump Boost. The boots grant Speed. The full set together grants a Saturation effect. These effects seem low level at first. Maybe it's missing something?
Potaintarmor = Of course! Adding a Potainto to each piece was the answer! Now it seems chestplate, leggings, and boots are at double their previous power and additional effects are added. The helmet now grants Water Breathing. The chestplate now grants Invisibility. The leggings now grant Haste 2. The boots now grant Fire Resistance. Wearing it all grants defense above any mundane armor because the full set now protects the wearer with Resistance 2. I look like a walking Potainto now, but as intimidating as that it I'm probably better off that way.
Potaintools = Potatools granted the new Potainto treatment also seem enhanced. They have far better stats than previously and are now unbreakable. Do I need carry any other tools?
The "Seven Deadly Sins of Potatomancy." A lost art within thaumaturgy was once drawing power from the "Seven Deadly Sins" and was often used to make potent Baubles, which is also a lost art. I attempted to research both paths and they blended as well as perfectly Mashed Potatoes! I have created one for each basic Bauble location and two rings. Altogether they are quite the set!
The Crown of Envy allows me to view all the creatures that I envy for supplies. Worn on the head it causes all creatures within a wide radius to begin Glowing for easy discernment. No one evades the eyes of the Potatoes!
The Heart of Pride is worn over the heart as an amulet and definitely fills me with it. It provides a full Health Boost 5 effect and Regeneration 2 to heal wounds faster.
The Mantle of Wrath is worn on the body as a cloak. The combined forms of Potatoes lead to some serious deep-fried justice! Any creature that strikes the wearer takes Thorns damage and is set on fire, Poisoned, and Withered. This is better than armor since the Thorns can never break it.
The Ring of Gluttony provides a bonus while eating to any hunger and food saturation regained. It's also cheaper than a full set of Potatarmor so it may be more convenient, if not as effective.
The Ring of Greed grants the bearer two added levels of luckiness in whatever they do to fulfill their greed. Looting levels while bearing a weapon, Fortune levels while using anything else, and a Luck 2 effect constantly.
The Belt of Lust attracts some weird attention. All animals will follow the wearer and breed whenever they get the opportunity. Maybe because it's partially made from food?
The Lure of Sloth is most extraordinary. Worn as a charm it seems the constantly act like Bone Meal close to the wearer and any material capable of bearing an ore seems to sometimes spontaneously do so. It certainly makes standing between a Potato farm and a Stone generator much more interesting!
Like my Potato-themed ideas? I also have some cross-mod compatibility ideas if certain mods update to 1.12+.

Damn, these are really good. Most are out of my reach though, I still struggle with the most basic forge functions...
Anyway, the 7 sins theme fits it pretty well, as I want a total of 7 bosses in the "complete" version of Thaumic Potatoes 2, each representing one primal aspect from Thaumcraft(as of now, Jagaimo is Perditio and Ziemniak is Ordo) and one that stands above all(for now, Fry Cook). Each can be assigned a sin and have their exclusive baubles.
Still, sadly, I'm heading off to college next week. so I won't have much time working on my mod afterwards...Until the winter vacation I guess.  Even then I'm not sure if I have enough time for this. I guess I'll try my best, but don't expect a major update in months. I'll keep your suggestions in mind when I start working on the mod again. Thanks!


RFC: Direction of PGObject 2.0

This makes a number of incompatible changes which I think are better made now than later including separation of concerns between the db service locator and the Perl module locator, better checking on registration of types, and more.  Please review and offer feedback before we consider merging it.

Coverage decreased (-2.3%) to 91.824% when pulling 644df0d33ccb2b8a4ed568d7cc5df02df754f0b3 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage decreased (-2.3%) to 91.824% when pulling 644df0d33ccb2b8a4ed568d7cc5df02df754f0b3 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage decreased (-2.3%) to 91.824% when pulling 644df0d33ccb2b8a4ed568d7cc5df02df754f0b3 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

I am guessing that coveralls no longer supports Perl 5.8?
The drop in code coverage appears to be due to the fact that  the overall number of code lines has dropped.  Same number appear to be missed.

Coverage increased (+0.2%) to 94.34% when pulling c72000b8276270bcf15b1ad61b4a235be0d2302b on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.484% when pulling c0c0191bb91eab1cdaa117a880ee891ca8d8a642 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.484% when pulling 7b2f4a2095fd4aef0c1f7d744b827fb2d16f0ed8 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Note that this change will break PGObject::Type::Composite and cause the other PGObject::Type libraries to throw warnings until they can be updated (quickly), so merging should not mean imminent release.   It gives us a change to test both locally with 2.x and on travis.  Other service locators should not be affected.

Coverage increased (+3.4%) to 97.561% when pulling e067758603e297332c734e54327bb8028eda1355 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling 2280e5c19414fe870f84487d9d0cd94ae5b96617 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling 686dae74a3c5cb4b628c9476f837fc687ede8761 on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling db9de5b14d2a90224b5066aaf7506690fed7baae on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling db9de5b14d2a90224b5066aaf7506690fed7baae on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling db9de5b14d2a90224b5066aaf7506690fed7baae on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling db9de5b14d2a90224b5066aaf7506690fed7baae on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.

Coverage increased (+3.4%) to 97.561% when pulling db9de5b14d2a90224b5066aaf7506690fed7baae on einhverfr:master into a05113febdaba3f3bb469d1d906fe19d5b6580ec on ledgersmb:master.


DialogueBox.hx line 213 gives a Null Object Reference when loading third song dialogue

When modding a custom week into the game with dialogue, the third song always crashes immediately when the dialogue box would normally appear. The line specifically causing the error is
dropText.text = swagDialogue.txt;
Is there any way to fix this?

It should be dropText.text = swagDialogue.text; instead.

Oh, my bad, I wrote it incorrectly - it is .text. Sorry about that!

idk then lol


throw error if no file for recorded stream

don't really recall why this seemed imperative at the time... taking it off my brain plate


Timings: Tracks 'lookup', adds 'wait' time, fixes connection re-use

PR Checklist:

[x] I have run npm test locally and all tests are passing.
[x] I have added/updated tests for any new behavior.
[x] If this is a significant change, an issue has already been created where the problem / solution was discussed: Addresses some feedback from https://github.com/request/request/pull/2452

PR Description
Feedback from @mcorb in https://github.com/request/request/pull/2452 found a few items with the new .timings object.
Changes:

The net 'lookup' event is now tracked, which is the correct event to track DNS lookup time.
There is a new .timingStart property that is based on Date.now().
The .timings.* timestamps are relative to .timingStart (using now()).
The .timings object now only contains socket, lookup, connect, response and end (moving the durations to .timingPhases)
.timings.start is no longer needed, since it will always in effect be 0.
The other durations such as wait, dns, tcp, etc were moved to .timingPhases.
A new .timingPhases.wait delta is added, which tracks the time from start->socket
The .timingPhases.dns calculation is changed from start->socket to socket->lookup.
Documentation was updated to be clearer about the handling of HTTP redirects and for all of the new properties above.
For cases of connection re-use, the timings would have resulted in NaNs or negative numbers.  This is resolved by assuming any events (such as lookup) that did not happen (due to re-use) are "filled in" using the timestamp of the previous phase (such as socket), resulting in a 0 ms delta.

Here is an example of the current properties:
{
  elapsedTime: 143,                 // deprecated
  responseStartTime:<PHONE_NUMBER>161, // deprecated
  timingStart:<PHONE_NUMBER>018,       // Unix Epoch ms
  timings: {                        // relative to timingStart
     socket: 6.410719000000002,
     lookup: 7.299280000000001,
     connect: 46.287758000000004,
     response:<PHONE_NUMBER>0000001,
     end: 142.975414
  },
  timingPhases: {                   // durations
     wait: 6.410719000000002,
     dns: 0.8885609999999993,
     tcp: 38.988478,
     firstByte: 59.167255000000004,
     download: 37.52040099999999,
     total: 142.975414
  }
}

Tests have been added.

@Huachao and @FredKSchott would appreciate you taking a look!

Thanks for the work @nicjansma, I'll be mostly offline until Monday but would love to take a look at this once back

@mikeal Some fixes in here for https://github.com/request/request/issues/2575

Once CI passes I would like to get this in because it fixes a leak introduced in the last release. Is anyone still in the middle of reviews that would object?

Wow, there's a big falloff in code coverage.

-0.35% overall.  It seems like it's just due to 4 lines in the new patch that aren't run (which cover error conditions):
https://codecov.io/gh/request/request/compare/667e923d8d51a0f0fb4c66c91d94a40f3d3e575a...32232d91f86f16b20d76f21363d7ae4a22a0af45/diff
If you're worried about it, I can see if I can create test cases for those scenarios in a followup PR (though tomorrow at the earliest).

Oh i see, was reading that wrong. Merging this to fix the bug. Would love a followup with more tests :)

@mikeal KeepAlive test here: https://github.com/request/request/pull/2590


error on get_all_stations

Today in gmusicproxy I've found that the method get_all_stations of gmusicapi (9.0.0) raises an error:
  File "./GMusicProxy", line 251, in <lambda>
    stations = self._robust_retry(lambda:api.get_all_stations())
  File "/home/mario/.virtualenvs/gmusicproxy/local/lib/python2.7/site-packages/gmusicapi/clients/mobileclient.py", line 760, in get_all_stations
    updated_after=updated_after)
  File "/home/mario/.virtualenvs/gmusicproxy/local/lib/python2.7/site-packages/gmusicapi/clients/mobileclient.py", line 1069, in _get_all_items
    return [s for chunk in generator for s in chunk]
  File "/home/mario/.virtualenvs/gmusicproxy/local/lib/python2.7/site-packages/gmusicapi/clients/mobileclient.py", line 1082, in _get_all_items_incremental
    **kwargs)
  File "/home/mario/.virtualenvs/gmusicproxy/local/lib/python2.7/site-packages/gmusicapi/clients/shared.py", line 83, in _make_call
    return protocol.perform(self.session, self.validate, *args, **kwargs)
  File "/home/mario/.virtualenvs/gmusicproxy/local/lib/python2.7/site-packages/gmusicapi/protocol/shared.py", line 227, in perform
    raise CallFailure(err_msg, call_name)
CallFailure: ListStations: 500 Server Error: Internal Server Error
(requests kwargs: {u'url': u'https://mclients.googleapis.com/sj/v1.11/radio/station', u'headers': {u'Content-Type': u'application/json', u'Authorization': u'<omitted>'}, u'data': '{"max-results": "20000"}', u'method': u'POST', u'params': {u'alt': u'json', u'updated-min': 0, u'include-tracks': u'true'}})
(response was: '{\n "error": {\n  "errors": [\n   {\n    "domain": "global",\n    "reason": "internalError",\n    "message": "Internal Error"\n   }\n  ],\n  "code": 500,\n  "me
ssage": "Internal Error"\n }\n}\n')

These 500s are often temporary. Are you still seeing the problem now?

I can use the other gmusicproxy methods, like get_collection or even get_song, but get_all_stations regularly raises error. I guess it is working for you.

I haven't tried it manually, but there haven't been any test failures.

I tried it on 2 accounts. Successful on both.

It looks that BubbleUPnP had a similar problem with stations few weeks ago: http://forum.xda-developers.com/showpost.php?p=68106096&postcount=11314
They recently released version 2.7.4 with this changelog: "fixed failure to load Google Music Stations folder".
The problem looks related to the state of the account. I got just few stations selected from the pool. I renamed them: maybe this is related.

I'm having the same error in the same call (CallFailure: ListStations: 500 Server Error: Internal Server Error).

Definitely an issue with something in my account. Switched account to one with only a handful of radios and it works.

@simon-weber , is there any way to report useful information to fix this issue. It is clearly related to the actual state of the account. I could remove all stations list and it could fix the problem but this would not improve the gmusicapi/gmusicproxy support for their users.

Same issue here.  I removed all of the radio stations from my account and it still 500s.  I then added just one and same 500 error.
If there's anything I can do to help debug, I'm happy to do it.
Some things that may be related:
I'm using a OTP for google.
I tried without a device id and by spoofing my phone's ID without a difference.

Are you noticing problems loading other items like playlists or playlist contents? I'm wondering if this is load-related (like https://github.com/simon-weber/Autoplaylists-for-Google-Music/issues/104) and would be improved by the change suggested in https://github.com/simon-weber/gmusicapi/issues/513.

I usually don't use playlists but I tried to subscribe a couple of playlists in my account. The method get_all_playlists correctly reports the name and urls of them. When I try to stream one of them, gmusicproxy reports 'playlist not found', the debug output (with some messages from gmusicapi) is:
request path: /get_playlist?id=14b8a041-1da5-4e95-8334-2b73ec54576d
<IP_ADDRESS> - - [25/Nov/2016 21:06:31] "GET /get_playlist?id=14b8a041-1da5-4e95-8334-2b73ec54576d HTTP/1.1" 200 -
Getting tracks from playlist with id '14b8a041-1da5-4e95-8334-2b73ec54576d'
ListPlaylists(args=[], kwargs={'start_token': None, u'max_results': 20000})
{u'kind': u'sj#playlistList', u'data': {u'items': [u'<3 playlists>']}}
ListPlaylistEntries(args=[], kwargs={'start_token': None, u'max_results': 20000, 'updated_after': None})
{u'kind': u'sj#playlistEntryList', u'data': {u'items': [u'<0 plentries>']}}
[]
ListTracks(args=[], kwargs={'start_token': None, u'max_results': 20000})
{u'kind': u'sj#trackList', u'data': {u'items': [u'<128 tracks>']}}
generated playlist:
#EXTM3U
Playlist not found!

It doesn't work but it's not a 500 error.

I feel stupid: switching on a recent release of gmusicapi fixed the problem...
Sorry for the noise.

No worries! Glad we got it figured out.


Support for splitting buffers M1/M2/M3

Hi,
The @ggerganov guy implement a solution for whisper that solve M1/M2/M3 problems about splitting buffers:

https://github.com/ggerganov/ggml/issues/647
https://github.com/ggerganov/whisper.cpp/pull/1763/files

It can be applied to SD too.
Can anyone help with this fix?
Thanks.

Hi,
It was done?


Start work on a minimal admin client.

This is part of the fixes for #79.  While this is not needed for the MVP milestone it might help us with some of our integration tests.  In this PR we just introduce the AdminClient and TableAdmin classes, and TableAdmin has a single ListTables member function.
Future PRs will introduce additional member functions to implement the full API for TableAdmin.

PTAL.  Rebased, addressed comments, and opened bug to do the thread safety right the next time.

PTAL.

Now for realsies.  The builds passed.  Note to self: do not add dependencies in the middle of a PR.
PTAL.


Unit tests for _post_process_results

Description

Add unit tests for the _post_process_results function:
https://github.com/WordPress/openverse-api/blob/v2.5.10/api/catalog/api/controllers/search_controller.py#L107
Additional context

Part of a series of unit test issues (see WordPress/openverse-api#871 & WordPress/openverse#683)
Implementation

[ ] 🙋 I would be interested in implementing this feature.

@sarayourfriend and @AetherUnbound I believe this is resolved as we have many new tests related to _post_process_results in https://github.com/WordPress/openverse/blob/main/api/test/unit/controllers/test_search_controller.py now which didn't exist when this issue was created.
If I am mistaken, or our current tests need further enhancement, please reopen. Thanks!


Clear 'tmp' dir after each test

Now all tests leave tmp dir untouched. We have to add teardown() function to make each test clear tmp dir after execution.

It'll be great to configure teardown() for all scripts in one place.


Add csv to unarchive processor

Apologies for not making an issue first, but it's pretty simple

Turns out when you run make lint, golangci-lint doesn't run if golint returns an error, so I wasn't seeing the golangci-lint errors 🤦

Haha no worries, looks great, thanks @greysond!


Look into fixing Java crash errors

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #android-development.

So what was the verdict here? @tneotia

Hopefully fixed with my changes but I don't know for sure

@zlshames 1.5.0 has been out for a bit, are we still getting crashes?

i think we're good


Error code 514 - Data entry on the legal status of adopters shows a single adopter but data entry for the numbers of adopters shows it as a couple.

Error information
Error code
514
Description to display
Data entry on the legal status of adopters shows a single adopter but data entry for the numbers of adopters shows it as a couple.
DfE Long-form description of error
If reporting legal status of adopters is L0 then the genders of adopters should be coded as M1 or F1.  M1 = the single adopter is male; F1 = the single adopter is female.
DfE suggested coding
If <LS_ADOPTR> = 'L0' then <SEX_ADOPTR> should be 'M1', or 'F1'
For further info, refer to the DfE validation document here

@OgileOze are you working on this?

Hello Tambe,
I started working on it but someone mistakenly completed it. I stand to be corrected but the rule should be done. It might still be under my name though. No idea why.
With regards,
Oze Ogile Madux

On 9 Dec 2021, at 3:58 pm, Tambe Tabitha Achere @.***> wrote:

@OgileOze are you working on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Hi Oze,
Hope you've been well. No further updates have actually been made to this rule, the pull request is still open:
https://github.com/SocialFinanceDigitalLabs/quality-lac-data-beta-validator/pull/388
It might have caused some confusion that on the spreadsheet I've been marking as 'done' rules that have been submitted in pull requests?
Also I was meaning to reach out and ask if you're still interested in doing some rule coding? Very happy for you to finish this rule off if so! I think the PR has all the necessary changes requested.
We're also looking for people to test the tool with their own data, if you'd be up for that (i'll be sending out a group email about this soon)
All the best,
Desi

Thanks Desi.
Yes, I’ll be fine with this and pick up a few from the the ones left if there are any. I thought it was done which is why I did not complete it.
Happy to test with some of our data as well. I was unable to join today’s meeting as we had the Regional Meeting.
Thank you.
With regards,
Oze Ogile Madux

On 9 Dec 2021, at 4:31 pm, dezog @.***> wrote:

Hi Oze,
Hope you've been well. No further updates have actually been made to this rule, the pull request is still open:
#388
It might have caused some confusion that on the spreadsheet I've been marking as 'done' rules that have been submitted in pull requests?
Also I was meaning to reach out and ask if you're still interested in doing some rule coding? Very happy for you to finish this rule off if so! I think the PR has all the necessary changes requested.
We're also looking for people to test the tool with their own data, if you'd be up for that (i'll be sending out a group email about this soon)
All the best,
Desi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Great !

Awesome, glad to hear it. In retrospect I should have added a 'in progress' category...

Closed by https://github.com/SocialFinanceDigitalLabs/quality-lac-data-beta-validator/pull/388


listMaxHeight does not work and no scroll in Fixed mode

The  listMaxHeight does not work and no scroll in Fixed mode.
This problem also like : https://github.com/MoePlayer/APlayer/issues/277#issue-456161855
config:


To confirm miden::sat::tx::get_block_number is referring to the block number for the latest known block.  We will need to define the block header format to support his.  On a similar note do we want to provide a geter for the block hash itself?  get_block_hash?

How do we intend the get_output_notes_hash procedure to be used.  Can this be called at any point in the transaction lifetime?  E.g. get_output_notes_hash reflects the output_notes_hash at the current point in time but may change as additional notes are created?

Do we want to also provide: miden::sat::account::get_initial_nonce?

I'm not sure this is needed. Ideally, nonce should be updated only once and the procedure which updates it can get the value of initial nonce before making an update. If it does turn out that it could be useful for something, we could add it later on.

To confirm miden::sat::tx::get_block_number is referring to the block number for the latest known block. We will need to define the block header format to support his.

Correct! Regarding the block header format, we have the preliminary layout described in https://github.com/0xPolygonMiden/miden-base/discussions/17#discussioncomment-4975996 (though this will probably be updated at some point).

On a similar note do we want to provide a geter for the block hash itself? get_block_hash?

Yes, I think this a good idea.

How do we intend the get_output_notes_hash procedure to be used. Can this be called at any point in the transaction lifetime? E.g. get_output_notes_hash reflects the output_notes_hash at the current point in time but may change as additional notes are created?

Yes, this is how I was thinking about it. We can either re-compute the hash every time or come up with a strategy which is more efficient (i.e., having a flag which indicates whether the hash is outdated).

Once #74 gets merged, I'm thinking we can add another procedure to the kernel: miden::sat::note::get_sender.

Once #74 gets merged, I'm thinking we can add another procedure to the kernel: miden::sat::note::get_sender.

How do you expect this to work. Would the user provide a note index as argument or should the procedure be context aware such that it can work out the current consumed / created note currently being executed and return the sender accordingly?

I was thinking this would be in the context of the currently executing note, and if there is no note (i.e., a call is being made from the tx script) then ZERO would be returned.

I've updated the table with what is currently implemented. It seems like we can implement 3 more procedures (miden::sat::account::set_code, miden::sat::note::get_assets, miden::sat::note::get_sender) but everything else is blocked on other components.

I believe miden::sat::tx::get_block_hash is already implemented @bobbinth.

miden::sat::tx::get_block_number implemented as part of #82 - pending review and merge.

I believe miden::sat::tx::get_block_hash is already implemented @bobbinth.

Ah, yes! I missed it. Marked as implemented now.

How do you expect the miden::sat::note::get_assets procedure to work?

I was thinking the transition would be like so:
[dest_ptr, ...] -> [num_assets, dest_ptr, ...]

Internally, the procedure would write all assets of the currently executing note into memory starting at the specified address (this would involve passing the hash of the note's assets via the stack and then un-hashing them using the advice provider).
But I'm open to other suggestions too.

@bobbinth I've removed the block status from create_note as from what we've discussed I don't think the procedure has a dependency on the vault.  Please let me know if I'm missing something.  I'm currently working on the implementation for create_note.

Adding procedure add_asset_to_created_note which is responsible for adding an asset to a created note.

I've removed the blocked status from create_note as from what we've discussed I don't think the procedure has a dependency on the vault.

Yes, if we build the tx output vault in the epilogue, there should be no dependency here.

I am marking this as complete. I have created a new issue #228 for the one outstanding procedure which is not on the critical path for the pioneers testnet.


Why flyway cannot execute sql again when last time execution failed?

We are using flyway 7.0.0 and mysql 8.0.25, when I tried to create sql and reverse sql to be executed by flyway, I did the complete opposite.

Then I reversed the content of the two sql files and recommit, expecting to execution again for the last execution log is tagged as fail. However,  the sql file did not be executed by flyway just because this version have been executed (even if the execution was actually failed).I seached on Internet and the solutions are just delete the failed history or update the filename to update the version. That's not a good experience.
I agree that we should not repeatedly execution sql when it was executed successfully and should create new sql file to do afterwards operations. However, when flyway check if a sql file was executed, shall we considered if it was executed successfully instead?Yeah , I mean check if the latest execution history log success=1.
ps : I readed the latest source code and I'm suprised to see that if a sql version was executed failed , flyway will return a fail state and immediately throw a FlywayValidateException in Flyway.migrate() method. Is it an operation to force developers to delete the failed history in database or update a new version? I don't think that's a good choice. May be a repeated execution on the failed version should be allowed even it is not marked as repeatable?

Thank you for your issue. Do you get this same issue with the latest version of Flyway?

I'm sorry that I can't change the unified version used in our company. However, as I mentioned before, the latest source code shows if a sql version was executed failed , flyway will return a fail state and immediately throw a FlywayValidateException. In other words, there's similar issue with the latest version of Flyway.

Hi @FloriaLI ,
From the issue description, we know that you're using mysql, which does not support DDL Transactions. In this case, a rollback is not an option for Flyway.
The suggested approach for your case is to run repair https://documentation.red-gate.com/fd/repair-184127461.html

Hi @JasonLuo-Redgate ,
I've tried to run repair before migrate in my CI?CD script and it worked !  I'll close this issue later.
Thank you so much !!


Stations controller should have tests

Bad josh, writing code without tests. Needs fixing.

Stubbed in joshproehl/bdd
Blocked by #33

@joshproehl has written some tests for the stations controller and all but one of the tests are currently passing, #46 was opened in response to the test that was not passing. At this point i'm not sure if the tests we have are enough or if we need more, and if we should wait to close this issue until we think we are done writing tests.

Once the creating tests branch is added to master this issue can be closed :)

testing branch has been merged to master, closing this issue :)


Login signin

register function
login function

Note: no logout function in this issue

It seems no problems after I tested with different cases


CLI-Installer seems absent starting with v<IP_ADDRESS>

PHP Version
8
Shopware Version
<IP_ADDRESS> and up
Expected behaviour
Installing Shopware via the CLI-Installer should work as it did in <IP_ADDRESS>.
e.g. like in https://github.com/shopware/platform/issues/2171
php public/recovery/install/index.php
--no-interaction
--db-user=dbuser
--db-password=dbpassword
--db-name="dbname"
--db-host=localhost
--db-port=3306
--shop-locale=de-DE
--shop-country=DEU
--shop-host=example.de
--shop-path=""
--shop-name='Shopname'
--shop-currency=EUR
<EMAIL_ADDRESS>--admin-username=admin
--admin-password=shopware
<EMAIL_ADDRESS>--admin-locale=de-DE
--admin-firstname=Admin
--admin-lastname=Admin
Actual behaviour
public/recovery/install/index.php does not exist and cannot be restored using bin/console assets:install which worked in <IP_ADDRESS>.
Am I missing something here, or is the CLI-Installer not available anymore?
How to reproduce
Try installing Shopware >= <IP_ADDRESS>  using bin/console assets:install and then php public/recovery/install/index.php ...

the whole recovery directory was removed.
@keulinho can tell you more about it

@mitelg is right the whole installer was removed, you can still install it over the CLI with the documented
bin/console system:setup

and
bin/console system:install

commands.


Correction for raw affiliation CR2P UMR 7207 MNHN CNRS SU, F-75005 Paris France; MCAM UMR 7245 MNHN CNRS, F-75005 Paris France

Correction needed for raw affiliation CR2P UMR 7207 MNHN CNRS SU, F-75005 Paris France; MCAM UMR 7245 MNHN CNRS, F-75005 Paris France
raw_affiliation_name: CR2P UMR 7207 MNHN CNRS SU, F-75005 Paris France; MCAM UMR 7245 MNHN CNRS, F-75005 Paris France
new_rors: 05pchb838;02feahw73;05ax2x637
previous_rors: 05pchb838;02feahw73
works_examples: W4385649909
contact: ac8b1bfbe1edf8cd374681d4e5f55660:dde1897c23c4e94327c7aa7973 @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Note in documentation that non-numerical values don't work for max/min

Documentation addition for #2552!

Coverage remained the same at 96.867% when pulling 136eb0d9483e324a28f0bc44cdcf8515d46a0393 on jdelbello:master into ec7689ad9380dcaa96cb5ec9c738474118a32fe4 on jashkenas:master.

Coverage remained the same at 96.867% when pulling 563755108a9705ba9231c0d894fd12455fbe4a04 on jdelbello:master into ec7689ad9380dcaa96cb5ec9c738474118a32fe4 on jashkenas:master.

I'll cherry-pick this to gh-pages later today when I get in front of a computer.

Cherry-picked: http://underscorejs.org/#max


[API,CLI] Not taking multiple cluster names during creation and deletion

I executed a command to create a few demo clusters by providing multiple cluster names as arguments, but it created the single cluster provided as the first in the CLI, the same goes for the delete-cluster command as well tried to delete multiple clusters at the same time only the first cluster name provided was deleted, I'm not sure if that's how it works
`~ # ksctl create-cluster local -c demo3 demo4
Building...
To use this cluster set this environment variable
export KUBECONFIG='/root/.ksctl/config/local/demo3/config'
CREATED!
~ # ksctl get
[
{
"cluster_name": "demo3",
"region": "N/A",
"provider": "local"
}
]
`

@KiranSatyaRaj the create and delete are for single cluster so the above

creating >1 clusters increase the complexity its more intutive to go by single cluster

If you have any suggestion we can discuss in the #ksctl  in kubesimplify discord channel

@KiranSatyaRaj if issue is resolved then you can close it

@KiranSatyaRaj if issue is resolved then you can close it

I'll close this issue for now and get back to you on discord.


Native mobile app example

Is there any example of the Native mobile app?

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

ID: d63dfde8-e0f4-7607-ed47-9a3eeefb42a1
Version Independent ID: e7f8c59b-78ef-79c5-73f2-672fbe5ab7d9
Content: Embed a bot in an app - Bot Service - Bot Service
Content Source: articles/bot-service-design-pattern-embed-app.md
Service: bot-service
GitHub Login: @matvelloso
Microsoft Alias: mateusv

There is no example for a native app because of how broad the concept is. For example, how to code a bot for a java-based android app would look different the objective-c based ones for ios.
The underlying concepts for both the examples above would the be same, however. A native app is going to need a handbuilt 'channel', and to enable communications using directline. The directline documentation here explains how to use the directline, and it would be up to the app developer to code the calls to the API.


Fix crash in genpkey app when -pkeyopt digest:name is used for DH/DSA

By the time the keygen is called the references to strings inside the
gen ctx are floating pointers. A strdup solves this problem.
Found whilst checking that truncated SHA worked for keygen.

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

This pull request is ready to merge

Thanks. Merged to master.


ValueError thrown if label value is too high

Description
When trying to run the function in lumbar FOV, if specifying a starting point at label =19 (corresponding to T11-T12 disc), the code crashes with a ValueError. The reason being that the labels on the template are not going high enough.
Steps to Reproduce
# here we use sct_testing_data/t2.nii.gz image, even if it is centered in the cervical cord, but the crash is independent from the image content anyways.
cd sct_testing_data/t2
sct_label_vertebrae -i t2.nii.gz -s t2_seg.nii.gz -c t2 -initz 25,19
...
Current disc: 19 (z=50). Direction: superior
.. Peak found: z=0 (correlation = 0.24951264940910967)
.. Switching to inferior direction.
Traceback (most recent call last):
  File "/Users/julien/code/sct/scripts/sct_label_vertebrae.py", line 427, in <module>
    main()
  File "/Users/julien/code/sct/scripts/sct_label_vertebrae.py", line 372, in main
    verbose=verbose, path_template=path_template, path_output=path_output, scale_dist=scale_dist)
  File "/Users/julien/code/sct/spinalcordtoolbox/vertebrae/core.py", line 222, in vertebral_detection
    current_z = init_disc[0] - list_distance[list_disc_value_template.index(current_disc)]
ValueError: 20 is not in list

Possible solution
Increase the number of labels from the template.

I could not replicate the issue with the parameters above.
From the history, the commit that I referenced above seems to have fixed the edge case (I checked out to the previous commit and then I was able to replicate).
@jcohenadad  I did not understand if your Possible solution suggests that more entries need to be added to the respective info_labels.txt, but as far as the bug is concerned, I think the issue can be closed.

I was able to replicate the error.
sct version:
Spinal Cord Toolbox (git-master-ca92ce39b85716419527b8ccab9819bd3c99f484)
I looked into it a bit and I think that these lines do not work.
The reason for that would be that
 approx_distance_to_next_disc = list_distance[list_disc_value_template.index(current_disc)] throws a ValueError and not an IndexError as suggested. I will look into it but it does seems to fix this, I'll open a PR if I think that this will fix this.
This avoids modifying our current template.

Thank you for looking into this, @lrouhier!