mitzen

In this example, we are going to pass properties down from parents to a child using the spread operator.  Basically any properties will be pass along.  Using the counter example, we will have the following child component code:- Counter.tsx import  {  useState  }  from   'react' ; type   ButtonProps  = {    children :  React . ReactNode ; }; export   const   Counter  = ( props :  ButtonProps )  =>  {    const  [ count ,  setCount ] =  useState ( 0 );    return  (      <>        < button   { ... props }   onClick = { ()  =>   setCount (( count )  =>   count  +  1 ) } >         mycount is  { count }        </ button > { ' ' }      </>   ); }; In my parent App.tsx, i have the following codes  import  {  Counter  }  from   './Counter' ; function   App () {    const  [ count ,  setCount ] =  useState ( 0 );    return  (      <>        < Counter   disabled = {true}   />      </>   ); } Example code  https://stackblitz

Bump into this issue and to see what causing it, you can try to use "kubectl describe pod/your-pod-name -n your-namespace". After that you should be able to see what is missing.

  to expose you can just use the following code. In this example, we are exposing a property called noOfEggs.  Please note: this can be properties or method. export   const   MyCounter  = ({  noOfEggs  })  =>  {      return  (      <>        < button > Component prop drilling -  { noOfEggs } </ button >      </>   ); }; From the parent component     < MyCounter   noOfEggs = "3"   /> You can achieve the same results via useRef/useImperativeHandle. To do this yiou need to declare useRef. Then you need to pass ref down to your child component as shown in the return block. import  {  useRef  }  from   'react' ; function   App () {    const   ref  =  useRef ( null );   const   handleClick  = ()  =>  {      ref . current . someMethod ();   };   return  (      <>        < div ></ div >         < div   className = "card" >          < MyCounterRef   ref = { ref }   />   < button   o

  To create a simple hello world react component, i used the following to create my component. import  {  useState  }  from   'react' ; type   ButtonProps  = {    children :  React . ReactNode ; }; export   const   MyCounter  = ( props :  ButtonProps )  =>  {    const  [ count ,  setCount ] =  useState ( 0 );    return  (      <>        < button   onClick = { ()  =>   setCount (( count )  =>   count  +  1 ) } >         mycount is  { count }        </ button > { ' ' }      </>   ); }; Then i wired it up using  import  {  MyCounter  }  from   './mycounter' ; function   App () {    return  (      <>                < MyCounter   />      </>   ); } Example code:  https://stackblitz.com/edit/vitejs-vite-fx2pxk

  Azure service bus duplicate detection works by using messageId as a unique identifier. If a sender tries to send messages with the same messageId, the first one gets into the queue. The other subsequent duplicate messageId will be ignored.  // create the sender ServiceBusSender sender = client . CreateSender ( queueName ); // create a message batch that we can send ServiceBusMessageBatch messageBatch = await sender . CreateMessageBatchAsync (); messageBatch . TryAddMessage (     new ServiceBusMessage ( "Session1-1" )     {         MessageId = "Session1"     }); messageBatch . TryAddMessage (     new ServiceBusMessage ( "Session1-3" )     {         MessageId = "Session1"     }); messageBatch . TryAddMessage (     new ServiceBusMessage ( "Session1-2" )     {         MessageId = "Session1"     }); // send the messages await sender . SendMessagesAsync ( messageBatch ); // Message Session1-1 gets into the queue /

 To check if your function app scales, you can goto your function app -> Monitoring -> Metrics -> And under the metrics select "Automatic Instance Count Scaling".

Under your Function app, goto "Help and support" ->  Support and Troubleshoot ->  Availability and Performance -> Here you can see various reporting about your function app.  Choose Function App Down or Reporting Error - to see if you're function app goes down for some reasons. There are others reporting that are of interest, like High CPU, High Memory.   

  Azure function app that uses time trigger needs to be configured correctly otherwise it will behave differently.  The crontab with 0 */5 * * * * runs as expected. It runs every 5 minutes. The crontab with 0 5 * * * * configuration. We notice it runs every hour instead of 5 minutes.  You can investigate further by using NCrontab library with the following codes. var cron = NCrontab . CrontabSchedule . Parse ( "5 * * * *" ); var start   = DateTime . Now ; var end = DateTime . Now . AddHours ( 1 ); var occurences =   cron . GetNextOccurrences ( start , end ); foreach ( var occurence in occurences ) {     Console . WriteLine ( occurence ); } And you will notice only 1 occurrences.  If you update it to as 0 */5 * * * *, you will typically get 11 occurrences. var cron = NCrontab . CrontabSchedule . Parse ( "*/5 * * * *" ); var start   = DateTime . Now ; var end = DateTime . Now . AddHours ( 1 ); var occurences =   cron . GetNextOccurrences (

The following workflow provides an example of using outputs. step1 generates the outputs. The name is defined by the outputs in job1.  Then job2 refers to it using job1.outputs.output1.  needs is use to define dependencies between jobs. jobs :   job1 :     runs-on : ubuntu-latest     # Map a step output to a job output     outputs :       output1 : ${{ steps.step1.outputs.test }}       output2 : ${{ steps.step2.outputs.test }}     steps :       - id : step1         run : echo "test=hello" >> "$GITHUB_OUTPUT"       - id : step2         run : echo "test=world" >> "$GITHUB_OUTPUT"   job2 :     runs-on : ubuntu-latest     needs : job1     steps :       - env :           OUTPUT1 : ${{needs.job1.outputs.output1}}           OUTPUT2 : ${{needs.job1.outputs.output2}}         run : echo "$OUTPUT1 $OUTPUT2"         After running, the output will be "hello world" as shown in diagram below:

What is github composite action allow you to host multiple commonly used task/steps/actions into a single actions. This prevents repetition of commonly used task. To get started, you create a repository that will host your actions/template. Create a file called action.yml For example, this can be your template  https://github.com/mitzenjeremywoo/hello-world-composite-action Next, to test out your composite repository, create another repository and create your workflow.  It should look like this. Notice how it refers to hello-world-composite-action@v1 on : [ push ] jobs :   hello_world_job :     runs-on : ubuntu-latest     name : A job to say hello     steps :       - uses : actions/checkout@v4             - id : foo         uses : mitzenjeremywoo/hello-world-composite-action@v1         with :           who-to-greet : 'Mona the Octocat'       - run : echo random-number "$RANDOM_NUMBER"         shell : bash         env :           RANDOM_NUMBER : ${{ steps.foo.outputs.r

To use github action to deploy to AKS cluster, you can try the following sample code. This approaches uses kubectl  To use helm file you can try the following sample  

While trying to deploy application to the target server installed with azure devops agent, we are getting this error message. If you get this error, this means it is not due to an issue trying to send instructions/tasks to the target agent but the issue with target server trying to download artifact or something from Azure Devops. So it is outgoing traffic and the ip number above, is probably going to be your proxy to get to Azure devops.  To resolve this, you need to check with your internal network admin to figure out which proxy to use and you need to update .proxy file. Updating the proxy file and restarting it, didn't work for me.  So i had to re-configure (re-install) my agent and using the right proxy. 

Sample bicep file to create Service bus  Because i am provisioning Basic service bus tier, there's a couple of properties that needs to be commented out. @ description ( 'Location for all resources.' ) param location string = resourceGroup ( ) . location @ description ( '' ) resource serviceBusNamespace 'Microsoft.ServiceBus/namespaces@2021-06-01-preview' = {   name : 'mytestservicebusjerwo'   location : location   sku : {     name : 'Basic'     capacity : 1     tier : 'Basic'   } } resource serviceBusQueue 'Microsoft.ServiceBus/namespaces/queues@2022-01-01-preview' = {   parent : serviceBusNamespace   name : 'myqueue'   properties : {     lockDuration : 'PT5M'     maxSizeInMegabytes : 1024     requiresDuplicateDetection : false     requiresSession : false     //defaultMessageTimeToLive: 'P10675199DT2H48M5.4775807S'     deadLetteringOnMessageExpiration : false     duplicateDetectionHistoryTimeW

  When you're trying to create a service bus queue but not entirely sure what are the schema/properties that you can tweak, please checkout this link here below  https://learn.microsoft.com/en-us/azure/templates/microsoft.servicebus/namespaces/queues?pivots=deployment-language-bicep

By using session of course, :)  For more info, please check out link below https://learn.microsoft.com/en-us/azure/service-bus-messaging/message-sessions  

  Quite a handy command to create key features for a service principal in Microsoft Entra. ✌ az ad sp create-for-rbac --name {app-name} --role contributor --scopes /subscriptions/{subscription-id}/resourceGroups/exampleRG --json-auth

Dotnet 6 cli does not really support "dotnet tool list -g <package-id>". When i ran this on a dotnet 6 build agent, it gives me 'unknown command or unrecognizable argument".  Running on dotnet 8 works for me.   

  https://github.com/actions/starter-workflows/tree/main/ci

To be able to run your workflow manually, you need to have this trigger configure ' workflow_dispatch ' for your default branch or main branch. If you have it in your feature branch, that won't work. You will either need to create a merge request to merge that into your default/main branch. Once you have done that, you should see the following and be able to trigger it.  

Github actions supports steps (task) and runner debugging mode. You can turn these on by  Step Debugging level  Set your environment variable to  ACTIONS_STEP_DEBUG  to true   build :         env :       MyEnvVar : Hello       ACTIONS_STEP_DEBUG : true Runner debugging level Set your environment variable to  ACTIONS_RUNNER_DEBUG   to true   build :         env :       MyEnvVar : Hello       ACTIONS_RUNNER_DEBUG : true After running the pipeline, if you goto your repository -> Actions -> Ensure you selected your workflow -> expand / open your job and then download your logs as shown here.  If you expand your logs file, you will be able to see additional logs compare to a normal logs (without debugging turned on)

 You can use the following to use bash for running a command for example, "source my-execution-file" and switch back to sh. SHELL [ "/bin/bash" , "-c RUN nvm install 17 SHELL [ "/bin/sh" , "-c" ] To find out more about bash vs sh https://stackoverflow.com/questions/5725296/difference-between-sh-and-bash