mitzen

 Kotlin launch is a co-routine operating under the model 'fire-and-forget'. It returns a Job object that we can use to see if it is active or cancel it. It is also non-blocking.  import kotlinx.coroutines.* fun main () = runBlocking {     // Launch a background coroutine     val job = launch {         delay ( 1000L )         println ( " World! " )     }         println ( " Hello, " ) // This prints immediately while 'World!' is waiting     job . join ()         // (Optional) Wait for the launch block to finish } If you want to fetch user data from a network API and use that data, launch won't cut it because it can't return the data. You must use async , which is where await() comes into play: This is a good example of launch use-case  class ProfileViewModel : ViewModel () {     // viewModelScope automatically cancels the launch if ...

When we create a function we generally allow user to pass in parameter. Sometimes this parameter can be a simple integer or it can be a function. In this implementation we are going to look at passing it as a function.  This is our sample function  fun calculate ( a : Int , b : Int , operation : ( Int , Int ) -> Int ): Int {       return operation(a, b) // Call it like a regular function   } In order to pass in our function, we use the ::  (double colon) operator  fun existing_calculate ( x : Int , y : Int ) = x + y  val result = calculate( 10 , 5 , ::existing_calculate)

How do you get all the permission granted to an AWS resources for example a storage s3 bucket? We can use the following commands. For the ACL, it asks AWS to tell you the legacy permissions attached directly to that bucket. It shows who owns the bucket and which AWS accounts or public groups have been granted specific read or write permissions via the ACL system. // To get bucket access control list aws s3api get-bucket-acl --bucket appjerwo-demo-test aws s3api get-bucket-policy --bucket appjerwo-demo-test This is an example of the bucket policy :- Unfortunately there is no clean way of reusing the command across different resources such as SQS.  So for sqs you probably need to use  aws sqs get-queue-attributes  --queue-url https://sqs.ap-southeast-2.amazonaws.com/xxxxxxxxxxxx/mytestsqs --attribute-names Policy  --query Attributes.Policy     --output text --region ap-southeast-2

Sometimes i think we type too much to get the same info again and again. Here are some shortcust whenever we are working with flux resources.  Full Resource Kind kubectl Shortcut Example Command Kustomization ks kubectl get ks -n flux-system HelmRelease hr kubectl get hr -n cert-manager HelmChart (Internal) hc kubectl get hc -n flux-system  And if you're keep to know more about other resources, run this command :-  kubectl api-resources | grep source.toolkit.fluxcd.io

How to create oauth 2.0 client for signing into google. You have to login to https://console.cloud.google.com/ and the go under API & Services . Then you will need to click on " Create credentials " as shown here.  And the next steps are pretty straight forward. Please download and copy your google-service.json file to your android app folder. Using the Android studio to paste this in to ensure Android studio is able to recognized your new file. 

The by keyword, however, is a native feature built directly into core Kotlin . It is called Property Delegation , and its main job is to let you hand over the responsibility of reading and writing a variable to a helper class. Here is a simple, real-world example of how by can be used to automatically format a string (like capitalizing a user's name) every time you save a value to it. import kotlin.reflect. KProperty // 1. Create the Delegate class that handles the background work class CapitalizeDelegate { private var actualValue : String = "" // Intercepts whenever someone reads the variable: "println(name)" operator fun getValue ( thisRef : Any ?, property : KProperty <*>): String { return actualValue } // Intercepts whenever someone updates the variable: "name = 'alex'" operator fun setValue ( thisRef : Any ?, property : KProperty <*>, newValue : String ) { // Automatically capitalize th...

After turning on localdns on your specific nodepool, we can use the following method to test if it is turned on.  Let's use the yaml here to place our pod into the nodepool.  apiVersion: v1 kind: Pod metadata:   name: dnstest-specific-node spec:   nodeName: <your-node-name> # Forces the pod onto this specific node   containers:   - name: test     image: busybox:1.28     command: ["sleep", "3600"] And then run kubectl apply -f <file-above>  kubectl apply -f dns-test-node.yaml kubectl exec -it dnstest-specific-node -- nslookup kubernetes.default Check the Server field in the output: 169.254.10.10 or 169.254.10.11 : The native AKS LocalDNS feature is enabled and actively working. 169.254.20.10 : The open-source NodeLocal DNSCache (DaemonSet) is enabled and working. 10.0.0.10 (or similar 10.x.x.10 ): Local DNS is not enabled . The pod is talking directly to the cluster's centralized CoreDNS service over the networ

 In Jetpack Compose, both mutableStateOf and rememberSaveable are used to manage state, but they operate on completely different levels of the Android lifecycle. The Problem: Recomposition Wipes the Slate Clean In traditional Android (XML), a UI element like an EditText stays on the screen forever, holding onto its own text. In Jetpack Compose, UI elements are just functions . When data changes, Compose runs those functions all over again from the top to draw the updated screen. This process is called Recomposition . The intention is to trigger an update to the UI if anything changes.  mutableStateOf makes your data reactive (updates the UI), while rememberSaveable protects that data from being wiped out when the user rotates the screen or switches apps. 1. remember In Jetpack Compose, remember is a built-in memory guard. Its sole job is to protect a variable from being destroyed and reset when your UI redraws itself. To understand why it is absolutely necessary, you fir...