mitzen

 Android build error message: Configuration `:app:debugRuntimeClasspath` contains AndroidX dependencies, but the `android.useAndroidX` property is not enabled, which may cause runtime issues. Set `android.useAndroidX=true` in the `gradle.properties` file and retry. To resolve this add this to gradle.properties # Project-wide Gradle settings. # IDE (e.g. Android Studio) users: # Gradle settings configured through the IDE *will override* # any settings specified in this file. # For more details on how to configure your build environment visit # http://www.gradle.org/docs/current/userguide/build_environment.html # Specifies the JVM arguments used for the daemon process. # The setting is particularly useful for tweaking memory settings. org.gradle.jvmargs = -Xmx2048m -Dfile.encoding=UTF-8 # When configured, Gradle will run in incubating parallel mode. # This option should only be used with decoupled projects. For more details, visit # https://developer.android.com/r/tools/gradle-multi-...

This is my rust code to get a client credentials access token with the intention of doing performance test.  The client id, client secret and endpoint is configurable as environment variables. use chrono ::{ DateTime , Utc , Duration }; use indicatif ::{ ProgressBar , ProgressStyle }; use serde :: Deserialize ; use std :: env ; #[ derive ( Debug , Deserialize )] pub struct TokenResponse {     pub access_token : String ,     pub expires_in : i64 , } pub struct AuthClient {     client_id : String ,     client_secret : String ,     token_url : String ,     http_client : reqwest :: Client , } impl AuthClient {     pub fn new ( client_id : String , client_secret : String , token_url : String ) -> Self {         Self {             client_id ,             client_secret ,         ...

We can deploy ADK agent to google cloud with adk command line. This would be available when we install adk module as part of your deployment requirements. To deploy your applications run the following command and if you trying to deploy sample app when you're in the root folder $AGENT_PATH=.  $SERVICE_NAME would be the name for your cloud run.  adk deploy cloud_run \ --project=$GOOGLE_CLOUD_PROJECT \ --region=$GOOGLE_CLOUD_LOCATION \ --service_name=$SERVICE_NAME \ --app_name=$APP_NAME \ --with_ui \ $AGENT_PATH If you do not have an existing container registry, it will prompt if you want to be created. You will be prompted if you would allowed anonymous invocations.  And the output would be something like this:- After you have successfully deploy it, your agentic AI can be tested via the deployed URL.  If you click on the cloud run endpoint, this would appear. And you can type away.

To deploy to Agentic ADK to Agentic Platform (Vertex AI), we need to run setup our .env file.  Pre-requisite   https://github.com/GoogleCloudPlatform/agent-starter-pack GOOGLE_CLOUD_PROJECT = YOUR-PROJECT-ID GOOGLE_CLOUD_LOCATION = us-central1 GOOGLE_GENAI_USE_VERTEXAI = TRUE MAPS_API_KEY =YOUR-MAP-API-KEY You can change the name of your agentic application by modifying this file "app/app_utils/deploy.py" and then  @ click . option (     " --display-name " ,     default = " property-location-strategy-uat " , # change your application name here     help = " Display name for the agent engine " , ) There are other configuration like location and service account.  Run the following command:-  make deploy IAP=true Example output: Behind the scene, it is using Vertex AI's agent_engines.update to do its deployment remote_agent = client . agent_engines . update (             name = matching_agents [ 0 ]. api...

To uncover the connection being used in a postgres server and historical data, we can use the following query to uncover who is connected, the user and which database.  This handle query is illustrated here - notice that we are pulling out information of a specific point in time.  AzureDiagnostics | where Category == " PostgreSQLLogs " | where TimeGenerated between (datetime( 2026-04-23 15 : 02 : 00 ) .. datetime( 2026-04-23 15 : 09 : 00 )) | where Message contains " connection authorized " | extend DbUser = extract(@ " user=([^ \s ]+) " , 1 , Message) | extend DbName = extract(@ " database=([^ \s ]+) " , 1 , Message) | summarize ConnectionCount = count() by DbUser, DbName | order by ConnectionCount desc

To deploy blue green, we start off with deploying the following yaml. As you may have notice, we have 2 services here which we will create next apiVersion : argoproj.io/v1alpha1 kind : Rollout metadata :   name :     labels :     app : bluegreen-demo spec :   replicas : 3   revisionHistoryLimit : 1   selector :     matchLabels :       app : bluegreen-demo   template :     metadata :       labels :         app : bluegreen-demo     spec :       containers :       - name : bluegreen-demo         image : argoproj/rollouts-demo:blue         imagePullPolicy : Always         ports :         - name : http           containerPort : 8080           protocol : TCP         resources :...

In this example, we are going to use Google cloud run to update corpus Vertex AI RAG. So when we have a new document, we load it up into Cloud storage. This generates an event for Cloud Run and update RAG.  To setup our Cloud run with event trigger. We will give it a name and then configure the target resource name. As you can see we are using "tgoogle.cloud.storage.object.v1.finalized" which gets fired when we create a new object, or overwrite an existing object, and Cloud Storage creates a new generation of that object. This is code in our cloud run. import functions_framework import os from google.cloud import aiplatform from vertexai.preview import rag import vertexai # Configuration from Environment Variables PROJECT_ID = os.environ.get( "PROJECT_ID" ) LOCATION = os.environ.get( "LOCATION" , "us-central1" ) RAG_CORPUS_ID = os.environ.get( "RAG_CORPUS_ID" ) vertexai.init(project=PROJECT_ID, location=LOCATION) # Triggered by a...

When we setup multiple VNET and peer them, let's say we have marketing VNET and research VNET. then we created a storage account and setup private link in research VNET. At this point, VM trying to resolve our storage account in marketing vnet will get a public ip. How do we configure to ensure this VM in marketing would be able internal IP?  All we need to do is go to the Private dns zone that we have created and then add a " Virtual Network link " and we choose "marketing" vnet target network. And then in the VM that we have created in marketing VNET, you can see that we are resolving to a local ip address instead of public.  And then if we look at the subnet. there's no IP that has been taken up.

To use this we need to create a "ValidatingAdminisionPolicy" and "ValidatingAdmissionPolicyBinding".  This example will prevent pod from being created if it des not have "label called environment". apiVersion : admissionregistration.k8s.io/v1 kind : ValidatingAdmissionPolicy metadata :   name : " require-env-label " spec :   failurePolicy : Fail   matchConstraints :     resourceRules :     - apiGroups :   [ "" ]       apiVersions : [ " v1 " ]       operations :   [ " CREATE " , " UPDATE " ]       resources :   [ " pods " ]   validations :     - expression : " has(object.metadata.labels) && 'environment' in object.metadata.labels "       message : " The 'environment' label is required for all Pods. " And then we have ValidatingAdmissionPolicyBinding apiVersion : admissionregistration.k8s.io/v1 kind : ValidatingAdmissionPolicyBinding meta...

First we should create our VNET, in this context we are going to create 3 vnet - research, marketing and 3rd party.  Then we are going to create Network Manager and then add your management scope - which is your subscription accessible to this network manager. Please ensure you selected Feature => Connectivity Network Group Then we will create a network group. Then provide it with a name "Hub-Spoke-Network-Group".  After it is crated, click on Add Virtual Network manally. We will select the vnet here  Network Configuration   This is where we will create Hub-Spoke topology here. Then go next:- Click "Review and create" when ready Deployment Before you ca  have your hub and spoke network, we need to click on "Deployment".  And then click on " Deploy configuration " And then after we deploy it, it should look like this :-

First we are going to need the following files and apply them  apiVersion : v1 kind : Service metadata :   name : rollouts-demo spec :   ports :   - port : 80     targetPort : http     protocol : TCP     name : http   selector :     app : rollouts-demo And this is the rollout file and notice the image we are using is ' blue '  apiVersion : argoproj.io/v1alpha1 kind : Rollout metadata :   name : rollouts-demo spec :   replicas : 5   strategy :     canary :       steps :       - setWeight : 20       - pause : {}       - setWeight : 40       - pause : {}       - setWeight : 60       - pause : {}       - setWeight : 80       - pause : {}   revisionHistoryLimit : 2   selector :     matchLabels :       ...