chore(kafka): Add kafka broker pod failure experiment in litmus-go

Signed-off-by: Udit Gaurav<EMAIL_ADDRESS>Issue:

fixes: https://github.com/litmuschaos/litmus/issues/1919

logs:
udit@ubuntu ~/g/s/g/l/litmus-go> go run experiments/kafka/kafka-broker-pod-failure/kafka-broker-pod-failure.go --kubeconfig=$HOME/.kube/config
INFO[2020-09-29T23:57:06+05:30] [PreReq]: Getting the ENV for the kafka-broker-pod-failure
INFO[2020-09-29T23:57:06+05:30] [PreReq]: Updating the chaos result of kafka-broker-pod-failure experiment (SOT)
INFO[2020-09-29T23:57:08+05:30] The application informations are as follows   Kafka Label= Ramp Time=0 Kafka Namespace=default
INFO[2020-09-29T23:57:08+05:30] [Status]: Verify that the Kafka cluster is healthy(pre-chaos)
INFO[2020-09-29T23:57:08+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-09-29T23:57:08+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-09-29T23:57:08+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=kafka-node-exporter
INFO[2020-09-29T23:57:10+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:57:11+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:11+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:57:11+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-09-29T23:57:13+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-09-29T23:57:13+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:57:13+05:30] The running status of container are as follows  Status=Running container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0
INFO[2020-09-29T23:57:13+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-1 Status=Running container=kubernetes-zookeeper
INFO[2020-09-29T23:57:13+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-2 Status=Running container=kubernetes-zookeeper
INFO[2020-09-29T23:57:15+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:57:16+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-09-29T23:57:16+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-1
INFO[2020-09-29T23:57:16+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-09-29T23:57:18+05:30] [Status]: Obtain pod name of any one of the zookeeper pods
INFO[2020-09-29T23:57:18+05:30] [Status]: Obtain the desired replica count of the Kafka statefulset
INFO[2020-09-29T23:57:21+05:30] [Status]: All Kafka brokers are alive
INFO[2020-09-29T23:57:21+05:30] [Liveness]: Set the kafka topic name
INFO[2020-09-29T23:57:21+05:30] [Liveness]: Generate the kafka liveness spec from template
INFO[2020-09-29T23:57:22+05:30] [Liveness]: Confirm that the kafka liveness pod is running
INFO[2020-09-29T23:57:22+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:57:29+05:30] The running status of container are as follows  Status=Running container=kafka-consumer Pod=kafka-liveness
INFO[2020-09-29T23:57:29+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness Status=Running
INFO[2020-09-29T23:57:31+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:57:31+05:30] The running status of Pods are as follows     Pod=kafka-liveness Status=Running
INFO[2020-09-29T23:57:33+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-09-29T23:57:38+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-09-29T23:57:39+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-09-29T23:57:39+05:30] [Chaos]:Number of pods targeted: 1
INFO[2020-09-29T23:57:39+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-1
INFO[2020-09-29T23:57:40+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-09-29T23:57:50+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-09-29T23:57:50+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:57:50+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-09-29T23:57:50+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:52+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-09-29T23:57:54+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-09-29T23:57:54+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-09-29T23:57:57+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-2
INFO[2020-09-29T23:57:59+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:57:59+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-0
INFO[2020-09-29T23:57:59+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:57:59+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-2
INFO[2020-09-29T23:58:01+05:30] [Chaos]: Time is up for experiment: kafka-broker-pod-failure
INFO[2020-09-29T23:58:01+05:30] [Completion]: kafka-broker-pod-failure chaos is done
INFO[2020-09-29T23:58:01+05:30] [Confirmation]: The application pod has been deleted successfully
INFO[2020-09-29T23:58:01+05:30] [Status]: Verify that the Kafka cluster is healthy(post-chaos)
INFO[2020-09-29T23:58:01+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-09-29T23:58:01+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=k8skafka
INFO[2020-09-29T23:58:01+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=kafka-node-exporter
INFO[2020-09-29T23:58:03+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:58:04+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-0
INFO[2020-09-29T23:58:04+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-09-29T23:58:04+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-09-29T23:58:06+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-09-29T23:58:06+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:58:06+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-09-29T23:58:06+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-1 Status=Running container=kubernetes-zookeeper
INFO[2020-09-29T23:58:06+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-09-29T23:58:08+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:58:08+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-09-29T23:58:08+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-09-29T23:58:08+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-09-29T23:58:10+05:30] [Status]: Obtain pod name of any one of the zookeeper pods
INFO[2020-09-29T23:58:11+05:30] [Status]: Obtain the desired replica count of the Kafka statefulset
INFO[2020-09-29T23:58:14+05:30] [Status]: All Kafka brokers are alive
INFO[2020-09-29T23:58:14+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-09-29T23:58:14+05:30] The running status of container are as follows  Status=Running container=kafka-consumer Pod=kafka-liveness
INFO[2020-09-29T23:58:14+05:30] The running status of container are as follows  Status=Running container=kafka-producer Pod=kafka-liveness
INFO[2020-09-29T23:58:16+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-09-29T23:58:17+05:30] The running status of Pods are as follows     Pod=kafka-liveness Status=Running
INFO[2020-09-29T23:59:06+05:30] [The End]: Updating the chaos result of kafka pod delete experiment (EOT)

Choas Result:
Name:         kafka-broker-pod-failure
Namespace:    default
Labels:       name=kafka-broker-pod-failure
Annotations:  <none>
API Version:  litmuschaos.io/v1alpha1
Kind:         ChaosResult
Metadata:
  Creation Timestamp:  2020-09-29T13:11:39Z
  Generation:          25
  Resource Version:    160732
  Self Link:           /apis/litmuschaos.io/v1alpha1/namespaces/default/chaosresults/kafka-broker-pod-failure
  UID:                 8a17c70f-8f95-4d24-ab2f-c3af8cfafd86
Spec:
  Experiment:  kafka-broker-pod-failure
Status:
  Experimentstatus:
    Fail Step:  N/A
    Phase:      Completed
    Verdict:    Pass
Events:
  Type    Reason   Age    From  Message
  ----    ------   ----   ----  -------
  Normal  Summary  14m          kafka-broker-pod-failure experiment has been Passed
  Normal  Awaited  3m11s        experiment: kafka-broker-pod-failure, Result: Awaited
  Normal  Pass     80s          experiment: kafka-broker-pod-failure, Result: Pass

When the pod-delete chaos is iterated, can we ensure we select the latest partition leader each time?

Case-1
Liveness: enabled  Broker Pod Name: empty
INFO[2020-10-12T14:13:46+05:30] Experiment Name: kafka-broker-pod-failure
INFO[2020-10-12T14:13:46+05:30] [PreReq]: Getting the ENV for the kafka-broker-pod-failure
INFO[2020-10-12T14:13:46+05:30] [PreReq]: Updating the chaos result of kafka-broker-pod-failure experiment (SOT)
INFO[2020-10-12T14:13:49+05:30] The application informations are as follows   Ramp Time=0 Kafka Namespace=default Kafka Label="app=kafka"
INFO[2020-10-12T14:13:49+05:30] [Status]: Verify that the Kafka cluster is healthy(pre-chaos)
INFO[2020-10-12T14:13:49+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:13:49+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:13:50+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-2
INFO[2020-10-12T14:13:52+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:13:52+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:13:52+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:13:52+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:13:54+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:13:54+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:13:55+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-0 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:13:55+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-1 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:13:55+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-2 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:13:57+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:13:57+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-0
INFO[2020-10-12T14:13:57+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-1
INFO[2020-10-12T14:13:57+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:13:59+05:30] [Liveness]: Set the kafka topic name
INFO[2020-10-12T14:13:59+05:30] [Liveness]: Generate the kafka liveness spec from template
INFO[2020-10-12T14:14:00+05:30] [Liveness]: Confirm that the kafka liveness pod is running
INFO[2020-10-12T14:14:00+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:14:07+05:30] The running status of container are as follows  container=kafka-consumer Pod=kafka-liveness-qhdpgq Status=Running
INFO[2020-10-12T14:14:07+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-qhdpgq Status=Running
INFO[2020-10-12T14:14:09+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:14:10+05:30] The running status of Pods are as follows     Pod=kafka-liveness-qhdpgq Status=Running
INFO[2020-10-12T14:14:12+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:14:16+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:14:16+05:30] Kafka Broker is kafka-kafka-2
INFO[2020-10-12T14:14:17+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-2
INFO[2020-10-12T14:14:17+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:14:27+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:14:27+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:14:28+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-10-12T14:14:28+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:14:28+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:28+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:30+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:30+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:14:30+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:30+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:14:33+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:33+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:33+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:33+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:14:35+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-10-12T14:14:35+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:35+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:35+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:37+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:14:37+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:14:37+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=k8skafka
INFO[2020-10-12T14:14:37+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:14:40+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:14:42+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:14:42+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:42+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:14:42+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:14:45+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-2
INFO[2020-10-12T14:14:45+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:14:55+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:14:55+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:14:56+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:14:56+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:14:56+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:14:56+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:14:58+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:14:58+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:14:58+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=k8skafka
INFO[2020-10-12T14:14:58+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:00+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:02+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:15:03+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:03+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:03+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:06+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-2
INFO[2020-10-12T14:15:06+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:15:16+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:15:16+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:15:17+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-10-12T14:15:17+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:15:17+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:17+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:19+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:19+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:19+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:19+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:21+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:15:21+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:21+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-10-12T14:15:21+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=k8skafka
INFO[2020-10-12T14:15:24+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:26+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:15:26+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:26+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:26+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:28+05:30] [Chaos]: Time is up for experiment: kafka-broker-pod-failure
INFO[2020-10-12T14:15:28+05:30] [Completion]: kafka-broker-pod-failure chaos is completed
INFO[2020-10-12T14:15:28+05:30] [Confirmation]: The application pod has been deleted successfully
INFO[2020-10-12T14:15:28+05:30] [Status]: Verify that the Kafka cluster is healthy(post-chaos)
INFO[2020-10-12T14:15:28+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:15:28+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:28+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:30+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:15:31+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:15:31+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:15:31+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:15:33+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:15:33+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:15:33+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:15:33+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:15:33+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-2 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:15:35+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:15:35+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-0
INFO[2020-10-12T14:15:35+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-1
INFO[2020-10-12T14:15:35+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-2
INFO[2020-10-12T14:15:37+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:15:38+05:30] The running status of container are as follows  Pod=kafka-liveness-qhdpgq Status=Running container=kafka-consumer
INFO[2020-10-12T14:15:38+05:30] The running status of container are as follows  Status=Running container=kafka-producer Pod=kafka-liveness-qhdpgq
INFO[2020-10-12T14:15:40+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:15:40+05:30] The running status of Pods are as follows     Pod=kafka-liveness-qhdpgq Status=Running
INFO[2020-10-12T14:16:27+05:30] [The End]: Updating the chaos result of kafka pod delete experiment (EOT)

Case 2
Liveness : enabled and Broker Pod Name: non-empty

INFO[2020-10-12T14:42:01+05:30] Experiment Name: kafka-broker-pod-failure
INFO[2020-10-12T14:42:01+05:30] [PreReq]: Getting the ENV for the kafka-broker-pod-failure
INFO[2020-10-12T14:42:01+05:30] [PreReq]: Updating the chaos result of kafka-broker-pod-failure experiment (SOT)
INFO[2020-10-12T14:42:04+05:30] The application informations are as follows   Kafka Namespace=default Kafka Label="app=kafka" Ramp Time=0
INFO[2020-10-12T14:42:04+05:30] [Status]: Verify that the Kafka cluster is healthy(pre-chaos)
INFO[2020-10-12T14:42:04+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:42:04+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=k8skafka
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:42:05+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-2
INFO[2020-10-12T14:42:07+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:42:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:42:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:42:07+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-2
INFO[2020-10-12T14:42:09+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:42:09+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:42:09+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:42:09+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-1 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:42:09+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:42:11+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:42:12+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-0
INFO[2020-10-12T14:42:12+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:42:12+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:42:14+05:30] [Liveness]: Set the kafka topic name
INFO[2020-10-12T14:42:14+05:30] [Liveness]: Generate the kafka liveness spec from template
INFO[2020-10-12T14:42:15+05:30] [Liveness]: Confirm that the kafka liveness pod is running
INFO[2020-10-12T14:42:15+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:42:22+05:30] The running status of container are as follows  Status=Running container=kafka-consumer Pod=kafka-liveness-lwcysv
INFO[2020-10-12T14:42:22+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-lwcysv Status=Running
INFO[2020-10-12T14:42:24+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:42:24+05:30] The running status of Pods are as follows     Pod=kafka-liveness-lwcysv Status=Running
INFO[2020-10-12T14:42:26+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:42:31+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:42:31+05:30] The Liveness pod gets established
INFO[2020-10-12T14:42:31+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:42:35+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:42:36+05:30] Kafka Broker is kafka-kafka-0
INFO[2020-10-12T14:42:37+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-0
INFO[2020-10-12T14:42:37+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:42:47+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:42:47+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:42:52+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:42:54+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:42:55+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:42:55+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:42:55+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:42:58+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-0
INFO[2020-10-12T14:42:58+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:43:08+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:43:08+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=k8skafka
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-2
INFO[2020-10-12T14:43:15+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:43:17+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:43:18+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:18+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:43:18+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-2
INFO[2020-10-12T14:43:21+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-0
INFO[2020-10-12T14:43:21+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:43:31+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:43:31+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:43:39+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-2
INFO[2020-10-12T14:43:41+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:43:41+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:41+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:43:41+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-2
INFO[2020-10-12T14:43:43+05:30] [Chaos]: Time is up for experiment: kafka-broker-pod-failure
INFO[2020-10-12T14:43:43+05:30] [Completion]: kafka-broker-pod-failure chaos is completed
INFO[2020-10-12T14:43:43+05:30] [Confirmation]: The application pod has been deleted successfully
INFO[2020-10-12T14:43:43+05:30] [Status]: Verify that the Kafka cluster is healthy(post-chaos)
INFO[2020-10-12T14:43:43+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:43:43+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=k8skafka
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-2
INFO[2020-10-12T14:43:43+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:43:45+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:43:46+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:43:46+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:43:46+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-2
INFO[2020-10-12T14:43:48+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:43:48+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:43:48+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-0 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:43:48+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:43:48+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-2 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:43:50+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:43:50+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:43:50+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-1
INFO[2020-10-12T14:43:50+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-2
INFO[2020-10-12T14:43:52+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:43:53+05:30] The running status of container are as follows  Pod=kafka-liveness-lwcysv Status=Running container=kafka-consumer
INFO[2020-10-12T14:43:53+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-lwcysv Status=Running
INFO[2020-10-12T14:43:55+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:43:55+05:30] The running status of Pods are as follows     Pod=kafka-liveness-lwcysv Status=Running
INFO[2020-10-12T14:44:33+05:30] [The End]: Updating the chaos result of kafka pod delete experiment (EOT)

Case-3
Liveness: disabled broker pod name: non-empty
 INFO[2020-10-12T14:31:51+05:30] Experiment Name: kafka-broker-pod-failure
INFO[2020-10-12T14:31:51+05:30] [PreReq]: Getting the ENV for the kafka-broker-pod-failure
INFO[2020-10-12T14:31:51+05:30] [PreReq]: Updating the chaos result of kafka-broker-pod-failure experiment (SOT)
INFO[2020-10-12T14:31:54+05:30] The application informations are as follows   Kafka Namespace=default Kafka Label="app=kafka" Ramp Time=0
INFO[2020-10-12T14:31:54+05:30] [Status]: Verify that the Kafka cluster is healthy(pre-chaos)
INFO[2020-10-12T14:31:54+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:31:54+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=k8skafka
INFO[2020-10-12T14:31:55+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:31:57+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:31:57+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-0
INFO[2020-10-12T14:31:57+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:31:57+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:31:59+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:31:59+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:32:00+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:32:00+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-1 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:32:00+05:30] The running status of container are as follows  Status=Running container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-2
INFO[2020-10-12T14:32:02+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:32:02+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-0
INFO[2020-10-12T14:32:02+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-1
INFO[2020-10-12T14:32:02+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:32:04+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-10-12T14:32:04+05:30] [Liveness]: Set the kafka topic name
INFO[2020-10-12T14:32:04+05:30] [Liveness]: Generate the kafka liveness spec from template
INFO[2020-10-12T14:32:05+05:30] [Liveness]: Confirm that the kafka liveness pod is running
INFO[2020-10-12T14:32:05+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:32:12+05:30] The running status of container are as follows  Pod=kafka-liveness-owouhm Status=Running container=kafka-consumer
INFO[2020-10-12T14:32:12+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-owouhm Status=Running
INFO[2020-10-12T14:32:14+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:32:15+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-liveness-owouhm
INFO[2020-10-12T14:32:17+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:32:21+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:32:21+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-10-12T14:32:22+05:30] [Chaos]:Number of pods targeted: 1
INFO[2020-10-12T14:32:22+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-0
INFO[2020-10-12T14:32:22+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:32:32+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:32:32+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:32:35+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:32:37+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:32:37+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:32:37+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:32:37+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:32:39+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:32:43+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:32:44+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-10-12T14:32:44+05:30] [Chaos]:Number of pods targeted: 1
INFO[2020-10-12T14:32:44+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-1
INFO[2020-10-12T14:32:45+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:32:55+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:32:55+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:32:55+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:32:55+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:32:57+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:32:57+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=k8skafka
INFO[2020-10-12T14:33:00+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:33:02+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:33:02+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:02+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:02+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:33:04+05:30] [Chaos]: Time is up for experiment: kafka-broker-pod-failure
INFO[2020-10-12T14:33:04+05:30] [Completion]: kafka-broker-pod-failure chaos is completed
INFO[2020-10-12T14:33:04+05:30] [Confirmation]: The application pod has been deleted successfully
INFO[2020-10-12T14:33:04+05:30] [Status]: Verify that the Kafka cluster is healthy(post-chaos)
INFO[2020-10-12T14:33:04+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:33:04+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=k8skafka
INFO[2020-10-12T14:33:04+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:33:06+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:33:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:33:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:33:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:33:09+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:33:09+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:33:09+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:33:09+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:33:09+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-2 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:33:11+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:33:11+05:30] The running status of Pods are as follows     Status=Running Pod=zookeeper-instance-zookeeper-0
INFO[2020-10-12T14:33:11+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:33:11+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:33:13+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:33:14+05:30] The running status of container are as follows  Status=Running container=kafka-consumer Pod=kafka-liveness-owouhm
INFO[2020-10-12T14:33:14+05:30] The running status of container are as follows  Status=Running container=kafka-producer Pod=kafka-liveness-owouhm
INFO[2020-10-12T14:33:16+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:33:16+05:30] The running status of Pods are as follows     Pod=kafka-liveness-owouhm Status=Running
INFO[2020-10-12T14:33:56+05:30] [The End]: Updating the chaos result of kafka pod delete experiment (EOT)

Case 4
Liveness: disabled Broker Pod Name: empty
INFO[2020-10-12T14:37:48+05:30] Experiment Name: kafka-broker-pod-failure
INFO[2020-10-12T14:37:48+05:30] [PreReq]: Getting the ENV for the kafka-broker-pod-failure
INFO[2020-10-12T14:37:48+05:30] [PreReq]: Updating the chaos result of kafka-broker-pod-failure experiment (SOT)
INFO[2020-10-12T14:37:52+05:30] The application informations are as follows   Kafka Label="app=kafka" Ramp Time=0 Kafka Namespace=default
INFO[2020-10-12T14:37:52+05:30] [Status]: Verify that the Kafka cluster is healthy(pre-chaos)
INFO[2020-10-12T14:37:52+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:37:52+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:37:52+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:37:54+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:37:55+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-0
INFO[2020-10-12T14:37:55+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:37:55+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:37:57+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:37:57+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:37:57+05:30] The running status of container are as follows  Pod=zookeeper-instance-zookeeper-0 Status=Running container=kubernetes-zookeeper
INFO[2020-10-12T14:37:57+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:37:57+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:37:59+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:37:59+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:37:59+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:37:59+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:38:02+05:30] [Liveness]: Set the kafka topic name
INFO[2020-10-12T14:38:02+05:30] [Liveness]: Generate the kafka liveness spec from template
INFO[2020-10-12T14:38:02+05:30] [Liveness]: Confirm that the kafka liveness pod is running
INFO[2020-10-12T14:38:02+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:38:10+05:30] The running status of container are as follows  Pod=kafka-liveness-qhrvex Status=Running container=kafka-consumer
INFO[2020-10-12T14:38:10+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-qhrvex Status=Running
INFO[2020-10-12T14:38:12+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:38:12+05:30] The running status of Pods are as follows     Pod=kafka-liveness-qhrvex Status=Running
INFO[2020-10-12T14:38:14+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:38:18+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:38:19+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-10-12T14:38:19+05:30] [Chaos]:Number of pods targeted: 1
INFO[2020-10-12T14:38:19+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-1
INFO[2020-10-12T14:38:19+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:38:29+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:38:29+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:38:30+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:38:30+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:38:32+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-0
INFO[2020-10-12T14:38:32+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:38:34+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:38:34+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:38:37+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:38:37+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:38:39+05:30] The running status of container are as follows  Pod=kafka-kafka-2 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:38:41+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:38:41+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:38:41+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-1
INFO[2020-10-12T14:38:41+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:38:44+05:30] [Liveness]: Obtain the leader broker ordinality for the topic (partition) created by kafka-liveness
INFO[2020-10-12T14:38:48+05:30] [Liveness]: Determine the leader broker pod name
INFO[2020-10-12T14:38:48+05:30] kafka broker will be selected randomly across the cluster
INFO[2020-10-12T14:38:49+05:30] [Chaos]:Number of pods targeted: 1
INFO[2020-10-12T14:38:49+05:30] [Info]: Killing the following pods            PodName=kafka-kafka-2
INFO[2020-10-12T14:38:49+05:30] [Wait]: Wait for the chaos interval 10s
INFO[2020-10-12T14:38:59+05:30] [Status]: Verification for the recreation of application pod
INFO[2020-10-12T14:38:59+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:39:00+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:39:00+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:39:00+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-10-12T14:39:00+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-1
INFO[2020-10-12T14:39:02+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:39:02+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:39:02+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:39:02+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:04+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:06+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:39:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-0 Status=Running
INFO[2020-10-12T14:39:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:39:07+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:09+05:30] [Chaos]: Time is up for experiment: kafka-broker-pod-failure
INFO[2020-10-12T14:39:09+05:30] [Completion]: kafka-broker-pod-failure chaos is completed
INFO[2020-10-12T14:39:09+05:30] [Confirmation]: The application pod has been deleted successfully
INFO[2020-10-12T14:39:09+05:30] [Status]: Verify that the Kafka cluster is healthy(post-chaos)
INFO[2020-10-12T14:39:09+05:30] [Status]: Verify that all kafka pods are running
INFO[2020-10-12T14:39:09+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  Pod=kafka-kafka-0 Status=Running container=k8skafka
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  Status=Running container=kafka-node-exporter Pod=kafka-kafka-0
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  Status=Running container=k8skafka Pod=kafka-kafka-1
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  Pod=kafka-kafka-1 Status=Running container=kafka-node-exporter
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  container=k8skafka Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:09+05:30] The running status of container are as follows  container=kafka-node-exporter Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:11+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:39:12+05:30] The running status of Pods are as follows     Status=Running Pod=kafka-kafka-0
INFO[2020-10-12T14:39:12+05:30] The running status of Pods are as follows     Pod=kafka-kafka-1 Status=Running
INFO[2020-10-12T14:39:12+05:30] The running status of Pods are as follows     Pod=kafka-kafka-2 Status=Running
INFO[2020-10-12T14:39:14+05:30] [Status]: Verify that all zookeeper pods are running
INFO[2020-10-12T14:39:14+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:39:14+05:30] The running status of container are as follows  container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:39:14+05:30] The running status of container are as follows  Status=Running container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-1
INFO[2020-10-12T14:39:14+05:30] The running status of container are as follows  Status=Running container=kubernetes-zookeeper Pod=zookeeper-instance-zookeeper-2
INFO[2020-10-12T14:39:16+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:39:16+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-0 Status=Running
INFO[2020-10-12T14:39:16+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-1 Status=Running
INFO[2020-10-12T14:39:16+05:30] The running status of Pods are as follows     Pod=zookeeper-instance-zookeeper-2 Status=Running
INFO[2020-10-12T14:39:18+05:30] [Status]: Checking whether application containers are in running state
INFO[2020-10-12T14:39:19+05:30] The running status of container are as follows  container=kafka-consumer Pod=kafka-liveness-qhrvex Status=Running
INFO[2020-10-12T14:39:19+05:30] The running status of container are as follows  container=kafka-producer Pod=kafka-liveness-qhrvex Status=Running
INFO[2020-10-12T14:39:21+05:30] [Status]: Checking whether application pods are in running state
INFO[2020-10-12T14:39:21+05:30] The running status of Pods are as follows     Pod=kafka-liveness-qhrvex Status=Running
INFO[2020-10-12T14:39:58+05:30] [The End]: Updating the chaos result of kafka pod delete experiment (EOT)


AMFIPass.kext

It is possible to add the kext AMFIPass.kext so that it can be updated in the list of extensions to be downloaded and would better be the kext needed for OCPL

Yes there's a way to do it by adding it to kexts.plist

Thank you, let's see if it is translated into Spanish for the next version


TypeError: 'NoneType' object is not iterable

Hello,
As I try pynonymizer, and I have this issue
Traceback (most recent call last):
  File "fake-username.py", line 2, in <module>
    pynonymizer.run(input_path="stg-top-dashboard.sql", strategyfile_path="fake-accounts_user-username.yml",
  File "/home/abc/.local/lib/python3.8/site-packages/pynonymizer/pynonymize.py", line 109, in pynonymize
    strategy = strategy_parser.parse_config(
  File "/home/abc/.local/lib/python3.8/site-packages/pynonymizer/strategy/parser.py", line 196, in parse_config
    table_strategies = [
TypeError: 'NoneType' object is not iterable

I also attached my code
fake-username.zip
What should I do for passing the above issue?
Many thanks
An,

Hello,
As I try pynonymizer, and I have this issue
Traceback (most recent call last):
  File "fake-username.py", line 2, in <module>
    pynonymizer.run(input_path="stg-top-dashboard.sql", strategyfile_path="fake-accounts_user-username.yml",
  File "/home/abc/.local/lib/python3.8/site-packages/pynonymizer/pynonymize.py", line 109, in pynonymize
    strategy = strategy_parser.parse_config(
  File "/home/abc/.local/lib/python3.8/site-packages/pynonymizer/strategy/parser.py", line 196, in parse_config
    table_strategies = [
TypeError: 'NoneType' object is not iterable

I also attached my code
What should I do for passing the above issue?
An,
fake-username.zip

Hi, I havent investigated this much but from a quick look, I think it might be that your strategyfile is not indented correctly.
This error is not very descriptive, though!
It is currently
tables:
accounts_user:
columns:
username: fake_username

when it should be:
tables:
  accounts_user:
    columns:
      username: fake_username

Thanks rwnx,
I will try follow your recommendation

Hi,
As I update and run again, I received this alert
How can I define this function?

File "/home/nda/.local/lib/python3.8/site-packages/pynonymizer/strategy/parser.py", line 141, in __parse_update_column
return FakeUpdateColumnStrategy(
File "/home/nda/.local/lib/python3.8/site-packages/pynonymizer/strategy/update_column.py", line 72, in init
raise UnsupportedFakeTypeError(fake_type, fake_args)
pynonymizer.fake.UnsupportedFakeTypeError: Unsupported Fake type: fake_username: dict_keys([])

Hi, This is some kind of syntax error in the strategyfile. likely something in yaml is a dictionary rather than a string like it's expecting. it's difficult to say without the updated strategyfile.

I dont have a direct fix for this but I have improved some of the error reporting in this area a lot. Closing as this is now a tech support problem. You could look into the discussion feature https://github.com/rwnx/pynonymizer/discussions if you're looking for more help.


compound indexes

great idea in including indexing options at field level.
Although it will serve every day needs, I wonder how this could be extended to manage compound indexes and Index intersection for more advanced apps that aim to use covered queries for better performance.
I guess it should be at collection level?

+1, we also have a need to define compound unique key. For example, fields 'foo' and 'bar' are both non-optional and we want the combination to be unique.

or perhaps specify the name of the index on each field and then define the index at the collection level, including the same name. E.g.
Schema = new SimpleSchema {
 compoundField1: {
  type: Number,
  name: 'Compound Field 1',
  index: 'compound_index_1'
},
compoundField2: {
  type: Number,
  name: 'Compound Field 2',
  index: ['compound_index_1', 'index2'] //<-- note MULTIPLE indexes on the same field
}
...
}
Collection = new Mongo.Collection('collection');
Collection.attachSchema(Schema);
Collection.attachIndex('compound_index_1', {
  unique: true,
  background: false,
  //sparse: false,
  //partialFilterExpression: xxx
  //expireAfterSeconds: xxx
  //storageEngine: xxx
  //and so on
  //basically all the mongo properties could be passed through to createIndex
});
Collection.attachIndex('index2'); //just use the deafults.  e.g. simple, ascending index

That's the very first issue, but it hasn't been resolved yet. Did anyone try to implement this yet? We have a use-case where compound indexes are important.

If I recall, I did add it @derwaldgeist but in my own fork.  I don't know that it was ever merged.  It's hard for me to remember as it was 9 years ago and I've been out of the meteor community for a while.
It might be worthwhile to diff my branch against its base and see what was changed.  I wish I could be more helpful.  Sorry.

I wish I could be more helpful. Sorry.

No prob. I solved this by setting the index using collection._ensureIndex() now, and it worked fine, both locally and on MongoDB ATLAS. I just hope this undocumented function will be upwards compatible, especially when upgrading to Meteor 3.0.


Job description page

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
for job description page
Test URLs:

Before: https://main--tlcgrp--hlxsites.hlx.page/
After: https://job-description-page--tlcgrp--hlxsites.hlx.page/

What is the .default-content-wrapper file for?

Please remove this empty file from the PR.

Note: For linting to pass, you need to fix #67 as well.

Please review

Please review


Canonical Url not updating the sitemap

Umbraco version 12.3.3
SEO Toolkit version 3.4.0
When I set my /home page to have the canonical of / this does not update the sitemap.xml file
I was under the impression that anything put into the Canonical URL field this would take priority. At the moment it is only showing the fallback value.

I am fairly certain that the canonical url is only used in the meta fields portion of the library, and has no impact on the sitemap. Each of these components were designed to run somewhat independently, though why I am not entirely sure.


Allow comments in module JSON

That's great, but it only works for the CornerCombiner module. Could you also enable comments for the rest of the modules? If you put the "comment" schema inside #/definitions, then this would be as simple as adding "comment": { "$ref": "#/definitions/comment"} to each of the module schemas.

Sure. Thanks for the help!

Comment for `"cache"' required??

Yes.

Check it now perhaps...

Thanks! I see why you asked about those four modules - they haven't been added to the #/modules schema. If you fix that bug, this will be ready to merge.

Done! :+1:

Reordered reciprocal

Thanks, great work. Merged.

Thanks to you as well! This was absolutely amazing!


python310Packages.cython_3: 3.0.0 -> 3.0.2

Description of changes
https://github.com/cython/cython/blob/master/CHANGES.rst#302-2023-08-27
There looks to be some good bugfixes to pick up (and one breaking change that I hope does not impact any packages yet).
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

pythonPackages.rapidfuzz breaks due to requiring Cython==3.0.0.  I have no idea why it's so strict.  maintainer: @dotlambda  /cc #253854


Define the namespace for the UCO ontology.

This is an issue that needs to be decided upon for the July 12th release of version 0.3.0 (June CASE Workshop action items)
UCO clean-up (July 12, 2019)
I.	Namespaces for CASE (and UCO)
A.	Base URI(s), Version, Hash or Slash?
1.	Ryan H, Sean B, Ryan G, and Vik

Agreement on call today was that pre-1.0 the namespaces would be structured as follows:
https://unifiedcyberontology.org/ontology/core#UcoObject
Post 1.0 we will possibly incorporate some kind of version identifier but many issues still need to be discussed to have consensus on the right approach.
For now, all namespaces across uco ontology ttl files will need the"ontology/" inserted

I agree that that was the structure we agreed upon. The actual URI for the UCO ontology was not agreed upon in today's meeting. I'm hoping for a consensus on the following, or something very similar:
https://unifiedcyberontology.org/ontology/uco/uco#
Which in turn would import:
https://unifiedcyberontology.org/ontology/uco/core#
https://unifiedcyberontology.org/ontology/uco/observable#
https://unifiedcyberontology.org/ontology/uco/types#
https://unifiedcyberontology.org/ontology/uco/action#
https://unifiedcyberontology.org/ontology/uco/identify#
https://unifiedcyberontology.org/ontology/uco/investigation#
https://unifiedcyberontology.org/ontology/uco/location#
https://unifiedcyberontology.org/ontology/uco/pattern#
https://unifiedcyberontology.org/ontology/uco/role#
https://unifiedcyberontology.org/ontology/uco/tool#
https://unifiedcyberontology.org/ontology/uco/victim#
Then, the CASE ontology  can import the  https://unifiedcyberontology.org/ontology/uco/uco# to get access to all.

The topic of namespaces and URIs is controversial and at times heated. I have my opinions, much like all of the others do. Some people like Fords, others Chevys. But if I want to get somewhere, the make of the car is of lesser importance than getting in and going.

Let's talk about the concept and approach of namespacing outside of this ticket and keep this ticket focused on what is needed to change in the current namespaces to be ready for v0.3.0

Ryan & Sean,
A "Hatlo Tip of the Hat"  to both of you for working your way through these topics and advancing our game!
Let's us know if you need the community to chip and "get you a room" ;-)
Pat Maroney
On Jul 12, 2019, at 11:49 AM, Sean Barnum<EMAIL_ADDRESS>wrote:
Let's talk about the concept and approach of namespacing outside of this ticket and keep this ticket focused on what is needed to change in the current namespaces to be ready for v0.3.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/ucoProject/UCO/issues/103?email_source=notifications&email_token=AAYSFYKN6BGUVW3LEGN2C2LP7CRYVA5CNFSM4H5AJNMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ2EPGY#issuecomment-510936987, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYSFYKSGD5TELOYG3BJWNTP7CRYVANCNFSM4H5AJNMA.

I am going to create a branch/PR with "ontology/uco/" added to the namespaces and "http" changed to "https"

Addressed in PR #124

Resolved in PR #124


fix tcp read unstable stuck

fix tcp read sometimes stuck on android platform.
cause by sometimes sendReceiveEvent() are un-ordered.
sendReceiveEvent(new PluginResult(Status.OK, info));
sendReceiveEvent(new PluginResult(Status.OK, recvBytes));

Can you explain your logic here?  You're calling readyToRead at least twice for each packet.  Once should be enough, if it needs to be called at all.
I find that not calling readyToRead at all seems to solve #26.

fix the same issue on android as @mcelrath at #27 .
exec(null, readyToRead, 'ChromeSocketsTcp', 'readyToRead', [socketId])
Call js function readyToRead only when exec failed, not twice for each packet.
Just make sure native readyToRead will be called once.

I found the bug with steam corruption in the master branch, without your patch. AFAICT it is not necessary to call readyToRead at all on Android. (At least, my patch without it works perfectly) Why do you call it?
On March 4, 2017 10:24:26 AM EST, cs8425<EMAIL_ADDRESS>wrote:

fix the same issue on android as @mcelrath at #27 .
exec(null, readyToRead, 'ChromeSocketsTcp', 'readyToRead', [socketId])
Call js function readyToRead only when exec failed, not twice
for each packet.
Just make sure native readyToRead will be called once.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MobileChromeApps/cordova-plugin-chrome-apps-sockets-tcp/pull/25#issuecomment-284158093
!DSPAM:58badc35191181728019888!

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@mcelrath
If not call native readyToRead,
nio will never go to read any new data from socket,
but you still can sent data (can write, can't read).
You can try it on a bidirectional, keep sending tcp socket, then you will know what I said.

Try my patch... I am able to read and write...
On March 5, 2017 10:47:31 AM EST, cs8425<EMAIL_ADDRESS>wrote:

@mcelrath
If not call native readyToRead,
nio will never go to read any new data from socket,
but you still can sent data (can write, can't read).
You can try it on a bidirectional, keep sending tcp socket, then you
will know what I said.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MobileChromeApps/cordova-plugin-chrome-apps-sockets-tcp/pull/25#issuecomment-284237850
!DSPAM:58bc331c63431952020848!

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@mcelrath
your patch can't work...
only signature and /assets/www/plugins/cordova-plugin-chrome-apps-sockets-tcp/sockets.tcp.js are different.
you can unzip/disassembling apk file to check it.
app source: https://github.com/cs8425/tcp-test-app
pre-build apk
mine: google drive
your: google drive

Yes, that's intended. The fix is entirely in sockets.tcp.js... Just diff it.
On March 7, 2017 2:31:39 PM EST, cs8425<EMAIL_ADDRESS>wrote:

@mcelrath
your patch can't work...
only signature and
/assets/www/plugins/cordova-plugin-chrome-apps-sockets-tcp/sockets.tcp.js
are different.
you can unzip/disassembling apk file to check it.
app source:
https://github.com/cs8425/tcp-test-app
pre-build apk
mine: google
drive
your: google
drive
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MobileChromeApps/cordova-plugin-chrome-apps-sockets-tcp/pull/25#issuecomment-284832398
!DSPAM:58bf0aa3211331626613455!

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


[ "useCaveFog": true ] makes the sun and moon disappear when shaders is enabled.

for some reason the vanilla sun and moon dissapear when useCaveFog is set to true while playing with shaders. If set to false both vanilla sun and moon reappear normally to the sky with shaders enabled.

Confirmed. Happens with Fabric counterpart as well so I guess that's a bug from the original Forge mod

Probably fixable but I'm not sure what causing it

Fixed in 1.2.0

Please make sure you are using version 1.2.0 and latest Oculus. Does the bug still occur with only Oculus and FLMN installed?

Figured it out. Oculus 1.6.9 had two modids: iris and oculus. iris modid was removed in Oculus 1.6.13 so only oculus left. The fix only works if mod with iris modid is loaded - that's why it stopped working. I'll post a hotfix soon


Incorrect Import Path in Documentation

The example code in the documentation at https://ownego.github.io/polaris-vue/documentation#appprovider incorrectly imports the locales file directly from the @ownego/polaris-vue/locales directory. This path does not reflect the actual location of the locales file in the distributed package.

I have submitted a pull request to correct the import path in the example code. The PR updates the path to @ownego/polaris-vue/dist/locales/en.json, aligning it with the actual location in the distributed package. You can find the PR here: #370
This change should resolve the issue by ensuring the documentation accurately reflects the correct import statement for the locales file. Please feel free to review and merge at your convenience.

Hi @KarDev, thanks for reaching us. According to your report, we just have a quick check and realize there's still another missing import path. So i will create a new PR and you can close your PR.
You can check to my PR here https://github.com/ownego/polaris-vue/pull/371
Thank you.

Thank you for the prompt review and for identifying the additional issue with the import path. I'm glad to contribute to the improvement of the documentation. I will close my PR [#370] as suggested and take a look at the changes proposed in your PR [#371].


[CLI]:

Describe the bug

Last 3 lines of dict_from_config_file(filename, must_exist=False): function expects ["value"] as second level key in config.yml files. I believe that's a bug as removing ["value"] part in the code got it working.

os.environ["WANDB_API_KEY"] = "XXXXXXXXXXXXXXXX"
os.environ["WANDB_MODE"] = "offline"

wandb.init(project="GAN", entity="anil-gurbuz", config="./config.yml")

Traceback (most recent call last):
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_init.py", line 996, in init
    wi.setup(kwargs)
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_init.py", line 186, in setup
    init_config = parse_config(
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_helper.py", line 13, in parse_config
    params = config_util.dict_from_config_file(params, must_exist=True)
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\lib\config_util.py", line 120, in dict_from_config_file
    data[k] = v["value"]
KeyError: 'value'
wandb: ERROR Abnormal program exit
Traceback (most recent call last):
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_init.py", line 996, in init
    wi.setup(kwargs)
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_init.py", line 186, in setup
    init_config = parse_config(
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_helper.py", line 13, in parse_config
    params = config_util.dict_from_config_file(params, must_exist=True)
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\lib\config_util.py", line 120, in dict_from_config_file
    data[k] = v["value"]
KeyError: 'value'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "C:\Users\gurbuza\Anaconda3\envs\DL\lib\site-packages\wandb\sdk\wandb_init.py", line 1037, in init
    raise Exception("problem") from error_seen
Exception: problem

Additional Files
config.yml file below
config.zip
Environment
WandB version: 0.12.17
OS: Windows 10
Python version: 3.9.12
Versions of relevant libraries:
Additional Context
No response

HI @anil-gurbuz thank you for reporting. I believe this is because we expect the config.yml to be in the following single-nested format with value as a key in the second level:
epochs:
  desc: Number of epochs to train over
  value: 100
batch_size:
  desc: Size of each mini-batch
  value: 32

Are you able to correctly access all of your config values with your edit to the codebase? For example, does wandb.config.global.data.real_batch_size return 128? I would imagine you cannot access these deeper nested parameters this way but I may be wrong.
Thank you,
Nate

Hi Nate,
Thanks for the response. I see what you mean.
I can access up to final level with "." notation -- i.e wandb.config.test_unit --  though final key value pair is only accessiable as a dictionary i.e -- wandb.config.test_unit["model"] --
Also, it logs those configs correctly to project page as well.

Hi @anil-gurbuz,
You're welcome! I wanted to follow up on this and ask if you found that reformatting your sweep.yaml solved the issue for you or if you still feel that we should address this as a bug?
Thank you,
Nate

duplicates #1913


Add TravisCI support

@idegtiarov will you update requirements.txt in this PR or in new one?

Good catch. Remove all odd packages from the requirements


Event Page Progress 🏔

We created the layout for the /events page and rendered the ICAL data from the Google Calendar.
We also fixed some styles that conflicted with the event card that originated in the call-to-action.svelte component, so we added those fixes where needed.

[ ] We need a button on either side to increment the scroll-offset slightly in its respective direction.
[ ] We need to make it more mobile-friendly, so let's add some media queries.
[x] Create a drag gesture/interaction to increment the scroll-offset smoothly. (https://github.com/EthanThatOneKid/acmcsuf.com/pull/91/commits/1bf4961b34369e20e8c27f782bf027a283bcb807)
[ ] Automatically scroll to event with the URL's fragment.
[ ] Hide buttons for mobile dimensions.
[ ] Hide the scrollbar.

I was looking into ways to accomplish the fading effect for the horizontal edges of the event carousel. One possible solution I've found is CSS linear gradients. With linear gradients, we could set the background image of an overlayed element to two linear gradients.
The definition of the linear gradients would look something like the code snippet below.
background-image: linear-gradient(to right, rgba(0, 0, 0, 0), var(--acm-light) 75%),
  linear-gradient(to left, rgba(0, 0, 0, 0), var(--acm-light) 75%);

Continued efforts on #99 due to an early merge of this pull request.


Version not corresponding to the documentation

version 1.1.4 has default checktype as true not false as given in the documentation!

Also, reinstalling version 1.1.4 / installing 1.1.5 makes the default checkType as false. Pretty weird!

I can confirm that v1.1.4 has default checkType:false in defParam.js file

Close due to no activity


Added admin/lessons page test

It looks like you've deleted __tests__/pages/profile/username.test.js altogether, that's why CI checks are failing. No need to do that, if you want to remove an obsolete snapshot you use yarn test testName.test.js -u or jest testName.test.js -u if you installed jest globally.

too many files changed, closing request


[EASI-2713] Email Notification:  Model Plan Dates Changed

EASI-2713
Changes and Description

Add email notifications when model plan dates change

How to test this change

Run scripts/dev down && scripts/dev up && scripts/dev db:seed
Assert that the following database table is created: config.model_plan_date_changed_email_recipients
Assert that the database table contains the following test recipients<EMAIL_ADDRESS><EMAIL_ADDRESS>Open Mailcatcher at http://localhost:1085/
Navigate to the Model basics task list section in the model plan Plan with Basics
Assign any Model Category selection
Click Next
Assert that no email is generated

Faulty Date Change processing would generate a data as Plan Basics is updated here

Click Next
Permutation Testing

Assign various different dates for testing purposes

There are two types of dates - individual dates and date ranges. Ensure they work both independently and together.

Assert that you receive an email in Mailcatcher with changes according to your test and that the To column contains all recipients in your config.model_plan_date_changed_email_recipients table<EMAIL_ADDRESS><EMAIL_ADDRESS>by default)

PR Author Review Checklist

[x] Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
[ ] Added or updated tests for backend resolvers or other functions as needed.
[ ] Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
[x] Updated the Postman Collection if necessary.

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
Always make comments, even if it's minor, or if you don't understand why something was done.

In order to avoid merge issues, this PR contains changes from the feature branch EASI-3000/read_view_users_contribute_discussions. Please ignore changes related to user roles as those changes will disappear once the feature branch is merged to main.

Thanks @OddTomBrooks , I had some weird behavior when I was testing this locally. It doesn't always recognize that a date is different than it was previously. For example, if I have a complete ICIP date set, and I change it again to another date in the future, no email fires. I also confirmed with breakpoints in the code that the no date changes register.
The email that did fire off looks like it might be getting the wrong data (eg providing the same date twice?)

Could you please take a look at the date comparison logic? I think that would be a good place to add Unit tests to verify that this functionality is behaving as expected.
Also, to verify, are all the store functions referencing an earlier approach which stored users in the database?

Strange, I have not seen such behaviour during local testing. Thank you for identifying this problem, I will go through this thoroughly to determine the root cause. Perhaps it will be exposed during construction of unit tests.

Tested locally - looks like, at least for the ICIP date, it's showing the new date in both the old and new fields. Not sure if this is in the tested functions or not, or if it's cropping up somewhere else (like in the templates?)

@ClayBenson94
I'm struggling to reproduce this issue.

Can you repro it? If so, can you provide the repro steps?
It might be based on initial values. In that case, which model plan are you modifying?
Also, as a sanity check, do you have latest and did you rebuild your containers?


memoize camelCase conversion

Converting keys from dashed-case to camelCase has a nontrivial perf impact

If implemented, does it enable using dashed-case for custom methods inside the component?

This is already implemented (just not memoized), so dashed-case should already work for custom methods. I do this a bunch in maria: https://github.com/mhuebert/maria/blob/master/editor/src/maria/editors/code.cljs#L147

My bad, I misunderstood it. Even though the custom method can be declared in dash-case, it must be called with camelCase, right? I thought you were saying that we could call the method using dash-case too.

Oh, I see. Yeah I doubt it would ever work to use host-interop syntax with invalid javascript names, like (.my-key obj)

Right, I see now.

Added in 2a8c9173


Correctly resolve tags for function overloads

Fixes #30181

There's a common thing people do where they only add JSDoc to the first overload. My feeling is that we should first try to get JSDoc for the applicable overload, and if we don't find anything, we should try to find JSDoc for any other overload. Thoughts @mjbvz @RyanCavanaugh?

I typically don't add jsdoc comments, but when I do, I use it to deprecate a single overload.

@ajafff please post future comments in the form of a meme if possible.

@DanielRosenwasser That's a good point. I'm going to look at Definitely Typed.
So far, it looks like the numbers are really low compared to compared to the total number of overloads. Admittedly, I'm only looking at d.ts and DT is relatively well-documented.
Some super early numbers:
Two-overload sets: 50 of 1,000,000 only document the first overload.
Three-overload sets: 25 of 5000.
I'll run over all of DT (and its dependencies) but right now I think this is a good change.

Actually, looks like I was asking the wrong question. Turns out the number of first-jsdoc-only overloads is quite high, of the overloads with jsdoc:

The yellow line is overloads with any jsdoc; the red line is overloads with jsdoc only on the first signature. Blue is all overloads. X=size of overload set; Y=number of each size of set.
Looks like @DanielRosenwasser is right; the jsdoc for the first signature of the overload should be applied to all others that do not themselves have jsdoc. The same is not true for non-first signatures.

@sandersn Pushed a better fix and added more unit tests


Add a new agent scenario and a tool to query weather online.

Thank you for providing the scenario for the agent.
To better support the agent scenario and ensure isolation, I have refactored the code and added an example called "WikipediaAgent".
You can use this example to create a "weather_agent" directory and a "WeatherAgent" under the "src/langchain_lab/scenarios/agents" directory.
After that, you can register it at https://github.com/coolbeevip/langchain-lab/blob/main/src/langchain_lab/scenarios/agents/init.py.
This way, you will be able to select it in the interface and ask questions, just like in the screenshot provided at https://github.com/coolbeevip/langchain-lab/blob/main/docs/image-agent.png.


Triage finschia-sdk#857

The subject of the triage:

Finschia/finschia-sdk#857

This PR needed to be abandoned.
The PR's problem is solved by

cosmos/cosmos-sdk #12895
cosmos/cosmos-sdk #13168
But the change of client/context.go can contribute to upstream. (very little change)
And we also need to migration README and our original module's change to new branch.