Added failing workload

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

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
{'status': 500, 'logs': "Seems your pod isn't producing any logs. Instead providing you with other information.\nThe last conditions your pods went through were: \n1. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: Initialized\n2. 2023-08-20T03:27:43+00:00 - Reason: None \t Type: Ready\n3. 2023-08-20T03:27:43+00:00 - Reason: None \t Type: ContainersReady\n4. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: PodScheduled\n---- \nContainers launched under your pods with their stats: \n1. Container containerd://049ba4bbbf15f2a18e604bb879adb027eda975a87847852e81fe20756a3b6405 has restarted: 504 number of times.\n"} ----
Logs for pod liveliness-check-6bf98bd74-62626:
{'status': 500, 'logs': "Seems your pod isn't producing any logs. Instead providing you with other information.\nThe last conditions your pods went through were: \n1. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: Initialized\n2. 2023-08-20T03:24:31+00:00 - Reason: ContainersNotReady \t Type: Ready\n3. 2023-08-20T03:24:31+00:00 - Reason: ContainersNotReady \t Type: ContainersReady\n4. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: PodScheduled\n---- \nContainers launched under your pods with their stats: \n1. Container containerd://7b96dc5efa7313a2e698776a5d764bd2896dd69cc24f0b205a96f4c557c09172 has restarted: 504 number of times.\n"} ----
Logs for pod liveliness-check-6bf98bd74-sk9hz:
{'status': 500, 'logs': "Seems your pod isn't producing any logs. Instead providing you with other information.\nThe last conditions your pods went through were: \n1. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: Initialized\n2. 2023-08-20T03:27:39+00:00 - Reason: None \t Type: Ready\n3. 2023-08-20T03:27:39+00:00 - Reason: None \t Type: ContainersReady\n4. 2023-08-18T19:51:35+00:00 - Reason: None \t Type: PodScheduled\n---- \nContainers launched under your pods with their stats: \n1. Container containerd://cb54c007ab60a64b8de7052358bcca65c8bc8755bec07fc4414a4b2810bc0e57 has restarted: 504 number of times.\n"} ----

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:30:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T03:30:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://264ebc7be1a0a4eabbe7cb5b76f5044b630450dd3001e87b7c724f167ae7d7b1 has restarted: 505 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:32:01+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T03:32:01+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://4acfa20d7692fa944cb5dd4e5e11b4a8b517f85007fe4133ee011f122c4bcef0 has restarted: 506 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:30:06+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T03:30:06+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ffce0c3180eb6e11245a2f5e574ff2593a3e010d479eb83d4bda9ea86b0abff1 has restarted: 505 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:58:08+00:00 - Reason: None 	 Type: Ready
2023-08-20T03:58:08+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://50cc72f49ba7ae4c22693a946538d760e21ce797b30fcf4faece61237e7378bc has restarted: 513 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:59:44+00:00 - Reason: None 	 Type: Ready
2023-08-20T03:59:44+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://1b3021c53f7ed67ba38b6be957b5a6278c5b630bd776cf41c55cea0b1dafc07f has restarted: 513 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T03:58:05+00:00 - Reason: None 	 Type: Ready
2023-08-20T03:58:05+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://779ba5a9f9b11f3c8db85506b620acbb85b908b3a768f1d6319f439c27952173 has restarted: 513 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T04:59:14+00:00 - Reason: None 	 Type: Ready
2023-08-20T04:59:14+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://37770ab570076aeb30f4d579aa46a5dc922ac561842500c8c31f49ed2a0b73f0 has restarted: 528 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T04:55:16+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T04:55:16+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e688beba50fc098fed79b01476fdec13addbbd00cdedb09dd9101918974919f4 has restarted: 528 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T04:58:39+00:00 - Reason: None 	 Type: Ready
2023-08-20T04:58:39+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://054bfde71197bf72afe8ea7e6b8aeca0662b200d13367eaae1ef8ed7a92499be has restarted: 529 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T05:54:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T05:54:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e965629f135498abbc2c2725334d8088e606ca5035bdfc397c020365aec22b23 has restarted: 543 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T05:55:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T05:55:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://03e81b698233e25f2d76e7b9b69bdf3361ac28a46450414392d3420f4273bd9c has restarted: 544 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T05:59:29+00:00 - Reason: None 	 Type: Ready
2023-08-20T05:59:29+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a9906d5404467f5a292abc18834db103846fa10711a4551eb22cd1097adc4bbf has restarted: 544 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T06:55:26+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T06:55:26+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://b0b210d4936b4623dee5e7e86382770a06ec4829b12b606b1b6eb65d4735d078 has restarted: 559 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T06:56:31+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T06:56:31+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://4b76b09daabff2eed01fdf566c04e32bdf9f3fddbc2786ee3f7306b5a8254768 has restarted: 560 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T06:55:06+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T06:55:06+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://1afbdbf0f96f4df70d2804898eddb2512911c8d6ad426667a328f9a7ee0a9109 has restarted: 559 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T07:55:55+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T07:55:55+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://51a28fb84d6240ccc66c4774ff38eb234628bd042073b9dcfda21174503e3db0 has restarted: 575 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T07:57:26+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T07:57:26+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a96dc3b051bdc2b0ac2710d2c2f4182d07afed11e9ea06a9f34c821baa03ed8b has restarted: 576 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T07:56:01+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T07:56:01+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://98be0524bb63f9cd10ad3d35a94a88f3b0d4fe5385a36fed133001227ec544b4 has restarted: 575 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T08:56:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T08:56:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://cb7e198fd76fd07c1742e2fcf8875d36a33d2b74a75c66d1cb1cd6536a077ab3 has restarted: 591 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T08:57:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T08:57:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://48fc78d16a477fb2afb19290bb2183d0b4f33a1b15f29f2eb95eb53ca6b2ff6d has restarted: 592 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T08:56:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T08:56:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://985577148372132a7dd5f32f46cc3537af145ae08d5ae6a56f3ab672dd7907c6 has restarted: 591 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T09:57:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T09:57:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://3fc6e23a81c4770c3e4d0f614b5083535b9503eee1b94b624de8364ad8f0650b has restarted: 607 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T09:58:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T09:58:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://9085214ada1f36250ab0d72043cd7cfa960506b6299eff14cc615e46e10dea03 has restarted: 608 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T09:57:26+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T09:57:26+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ff3c0ba4d384a601610761d6ccbecf0b212f673bcefeb2735c9a9acb1278fd61 has restarted: 607 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T10:58:01+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T10:58:01+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://0734aa26031dc8a9d1ba99f3c3edeea327eec3c29d9a33f2bf1d99579c3d18b9 has restarted: 623 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T10:58:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T10:58:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://79f9644d95065d2acb186ae592992a6e0590ce46e9adc45f01e5be205d4f3567 has restarted: 624 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T10:58:06+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T10:58:06+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://70c8b345d35a65884773cd7da486f1a0643ce5e75a5c1da71b8b7cc49590229a has restarted: 623 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T11:58:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T11:58:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://df763a405a5a64005e2fd3ee33e4888341bea4494d38f933ea0818e041b34f45 has restarted: 639 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T11:59:31+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T11:59:31+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://d9b3258936fb125bb234bacd3d55b7e8f953758a48bd130c289cae561653d7a7 has restarted: 640 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T11:58:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T11:58:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://8f75f8cec4f5168bd112cbfd461383c4941a3c8e1a43e3a1e616d2fcacb0028e has restarted: 639 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T13:59:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T13:59:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://40f08cc7e877e6ae863954e0b1265dda0b01bebb22ebe06beb393751ea89c3a6 has restarted: 671 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T13:58:46+00:00 - Reason: None 	 Type: Ready
2023-08-20T13:58:46+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://eecb0a0e2f7bb942be93f05b8a3acecd1cc2814547e9d809fc2d4d3132af952a has restarted: 671 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T13:57:43+00:00 - Reason: None 	 Type: Ready
2023-08-20T13:57:43+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://359a54171d850bc49be061ed1f6b45dac76346f990d1e3b94081fbfdf76823a6 has restarted: 671 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T14:58:17+00:00 - Reason: None 	 Type: Ready
2023-08-20T14:58:17+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a075e583fd201240d3aa2a13fe71151da7cdacf812a2a53bab69d197f57b2656 has restarted: 687 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T14:59:15+00:00 - Reason: None 	 Type: Ready
2023-08-20T14:59:15+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://199e8e7d51b46c59c7ad98be9751aa69c46670babb3cb79e6415b6829481acbe has restarted: 687 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T14:58:17+00:00 - Reason: None 	 Type: Ready
2023-08-20T14:58:17+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://8747e3a5c941066e3b42ecc4072b70d45c621a4bcd52f32af593071c823f71b1 has restarted: 687 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T15:59:01+00:00 - Reason: None 	 Type: Ready
2023-08-20T15:59:01+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://d2ded37e593ab42f726e788ca174040081f4b45b00eb338cc89feacdfd7d95fa has restarted: 702 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T15:54:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T15:54:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a0885c62a64d4f24acf88924eb721379a9aad2ed1d3fc7b7107ff44aa60f1d3a has restarted: 702 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T15:58:55+00:00 - Reason: None 	 Type: Ready
2023-08-20T15:58:55+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://31c79f867ed299b46acf0198a1232f7c5e2cf3f3fa948e6d6498dfb9520525c3 has restarted: 702 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T16:59:47+00:00 - Reason: None 	 Type: Ready
2023-08-20T16:59:47+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://50c8a03c571dee4fe5b0481a75105df260755728cb6893d90bc038320f4b6071 has restarted: 718 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T16:55:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T16:55:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ee8def4c88e1fbe2308d39bdcc0b7950fa823b4c9ed5bc0467d84cd186bd084b has restarted: 718 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T16:59:25+00:00 - Reason: None 	 Type: Ready
2023-08-20T16:59:25+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://24a0763b55d128d26f261f7b4c28850dfcef47a480550d96f8a9ad1f72e91d79 has restarted: 718 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T17:55:46+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T17:55:46+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://529309f9610a66f620608abe40414ffd95ceaeb8304cd685267fe8d991f14a84 has restarted: 733 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T17:56:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T17:56:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://b70c0dbc9a00e1a0211405a85693dc17c6853349a385015094140838d19462a8 has restarted: 734 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T18:00:01+00:00 - Reason: None 	 Type: Ready
2023-08-20T18:00:01+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ad83bcbf2066526224c4d4a12ea6ee8d72312762540fed1195df1ea6d9b5dcc0 has restarted: 734 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T18:56:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T18:56:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://40e98edf12573e27a08a3c4431307a3ba340310b23da3ae9cf295999f4cbef02 has restarted: 749 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T18:56:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T18:56:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://38f5ed8e5d9bdbdd51b496e58b0384d0d054fc05be350517d486577fbe4c3438 has restarted: 750 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T18:55:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T18:55:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://208ad958ad252929887c730f8439cd5b9311cf0abdc53c1470ec9609ea920347 has restarted: 749 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T19:57:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T19:57:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://aef1bbaa956a99a038da5fc76a0ca39bc83ef86e5ae1338cc0b2a7c1182f8ee6 has restarted: 765 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T19:57:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T19:57:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://9dfc6320e45c87c43a0dd476d53a247fd979e5b5195e8f682c651df4b3b14826 has restarted: 766 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T19:56:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T19:56:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://912a236744111a9a3d27bc063c9bed992201cb2a343b89677c73403d11fa6493 has restarted: 765 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T20:58:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T20:58:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://9b32d1a300f7e51ce04a7be90617e235f8524bba288407cd3e2e6b21d5c4cd12 has restarted: 781 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T20:57:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T20:57:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6457fa3a3367097d79e1808e7e649feb9a443c62806af9f8a0de14b7e0aacab9 has restarted: 782 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T20:57:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T20:57:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://4ab8e02e9c9e61c69ed20990a463110e258393801d71061b4e53db807dcc9b6b has restarted: 781 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T21:58:31+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T21:58:31+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://1670982d0a25948c5f845053cffd13752579aa7f0b805e937e68e3d1d992a217 has restarted: 797 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T21:58:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T21:58:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://3552938b4198f21682a6a3dc49850811f0e8a5ca42b806df0a1516838389939a has restarted: 798 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T21:57:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T21:57:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://dc66bfba084f3c381fb1c62c21a97149e3320a0649b5955f4460201db1561fcc has restarted: 797 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T22:59:31+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T22:59:31+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://58720b2f8e91e06f14c8579397f264cb2d8975197b91dbe7c671171a41a1f972 has restarted: 813 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T22:58:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T22:58:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://0f310af34074d505bd6c062283e5e20b8accba4badc9986155450471e0606afb has restarted: 814 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T22:58:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T22:58:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://cda07e5a142323c4c8328f2f86b83fd3c242138cf5dc0a877744a11bfd0aaf1a has restarted: 813 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T23:59:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T23:59:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://2535b3892612d4325649cd4eef7a127bb7f58d3fa3fe4bea660ce7913f92ae34 has restarted: 829 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T23:59:16+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T23:59:16+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://638464d3a101c38ea7864d5ae6c38eccf2ca4013a23fad1189c6217a346ae022 has restarted: 830 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-20T23:58:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-20T23:58:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://f7581bd360114c5146976dce1094e8c111498a311d24b5d7545bab9dc18a5e90 has restarted: 829 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T00:57:52+00:00 - Reason: None 	 Type: Ready
2023-08-21T00:57:52+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a4c781bfb647a9250d3d7e48143c0d919fbad9fb1c9a422dc3ae50d1619102a3 has restarted: 845 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T00:59:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T00:59:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6fc3fa68efa42cf19b202e3c7311b98d32b6778e22974e6b45195289c8795e4b has restarted: 846 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T00:59:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T00:59:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e61049e3aea59c644cab9b5f8f085395723f33de234a07588d4b92eb8bac8b31 has restarted: 845 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T01:58:00+00:00 - Reason: None 	 Type: Ready
2023-08-21T01:58:00+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://fd09a7aaee9f108f98bcaa788de2220c0176441e3b82e9de7b68a3c4ff8c5b87 has restarted: 861 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T01:58:06+00:00 - Reason: None 	 Type: Ready
2023-08-21T01:58:06+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e7fed52fcfe3e527b068780c5659082dbde56f2da4913b06276516a5d88dc900 has restarted: 862 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T01:57:39+00:00 - Reason: None 	 Type: Ready
2023-08-21T01:57:39+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://92db987829edafa30722cf0301e012f882173e581e487ec7bf4533385b307f68 has restarted: 861 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T02:58:47+00:00 - Reason: None 	 Type: Ready
2023-08-21T02:58:47+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://d142cbf7b886753cd07e4ca11edcfd7020ab9371c199713717d99dca2f2c223e has restarted: 876 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T02:58:45+00:00 - Reason: None 	 Type: Ready
2023-08-21T02:58:45+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://7bf9c433997b123b32dffa9f5c7b5c615174f9d1f7af4b8785ddd8269d4fc262 has restarted: 878 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T02:58:24+00:00 - Reason: None 	 Type: Ready
2023-08-21T02:58:24+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://7192297d0a486e1470e374eb18abac949e71073688ec0ee4db88c08de5fedc8d has restarted: 877 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T03:59:15+00:00 - Reason: None 	 Type: Ready
2023-08-21T03:59:15+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://171b0ac8ac0d7ba9b72abae34c93b5e2176909a9a21d6df888d4da66aed0fa89 has restarted: 892 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T03:55:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T03:55:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a6be2ecb30985ea4eb0248fcc6b2ba44780e537b76dd717b04d2bd8051a36540 has restarted: 893 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T03:59:20+00:00 - Reason: None 	 Type: Ready
2023-08-21T03:59:20+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://0fdb5efe0a6280b5b3e345a10d4fee0a7d03eaa36dbd4851701cb69543e765ca has restarted: 892 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T04:59:46+00:00 - Reason: None 	 Type: Ready
2023-08-21T04:59:46+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6e5fb264a215e142ae5e9c6e4f349dcc81f386b12495bf74b23b91ad891722b1 has restarted: 908 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T04:56:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T04:56:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://c9801a449f239f1f005823d4749108bdc491012ae3284755a55647608dd1ec4a has restarted: 909 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T04:55:06+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T04:55:06+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://847dd9fb3e1ea17173c4a2dfddcbaa4b0356ab6cbe4a059824a61e32ceac1b98 has restarted: 907 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T05:55:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T05:55:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://8ebe7f2876c5a5f1088c70ae7fa247fe54e3aba974b8e4810156ca28df9c1c1e has restarted: 923 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T05:57:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T05:57:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://4a6c85370aa643b3f00213911f996b6005c77040b132aa43a731a9037e8c6475 has restarted: 925 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T05:55:46+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T05:55:46+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e7ac408792cb01f3c30218d78d0ad95e6f5645882a808bf2dde0afee954a5f71 has restarted: 923 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T06:55:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T06:55:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e6f63dbbdb6b7e8a4c072234cf478bac700a7e0120be9092133ec9cedef2fa63 has restarted: 939 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T06:57:46+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T06:57:46+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://b2aebfb6c86755a6a9f9645ad7944198420697d25016e00aa9a58f8a8c018efc has restarted: 941 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T06:56:36+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T06:56:36+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://cd21554f93be555febf62dcc7e8a4518778a4e0da51994acd3bb323006cfba98 has restarted: 939 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T07:56:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T07:56:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://9842c471deccdace62b8ccf36b53c63ffdd2adb834fea416437ace4678199f52 has restarted: 955 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T07:58:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T07:58:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://7bbe472a4c85bf0649804d1ba0d6f60ab591f6fa9858d73935494805dfd7485d has restarted: 957 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T07:57:06+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T07:57:06+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ff071c1276f76e8eadef8fd48b1cb5e3de8e2e4dfc9c34bbf9cac32361d49619 has restarted: 955 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T09:57:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T09:57:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6caf47aea8f3eb5ee5ea84a20030f1dec98a03f0f4195a17a5f5eca09158c65e has restarted: 987 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T09:59:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T09:59:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://cb86941302e06eb56583e9b6dffb8689e67584a1257831f142bd1d7ee2d9331f has restarted: 989 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T09:58:26+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T09:58:26+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a5e846d17e54c234c013f77f2163b0a6194abb63d345511cc8b1ce7a98f9669c has restarted: 987 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T10:58:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T10:58:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://7639906182b862866b7f3ddcc5753451dc6b261d9efa70004af7c7f106df0ade has restarted: 1003 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T10:58:12+00:00 - Reason: None 	 Type: Ready
2023-08-21T10:58:12+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a03e43632ce754f4d806397b1251dd3e0d5690ccb3b17d510aef1c6fcae5a820 has restarted: 1005 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T10:59:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T10:59:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6195a5a8b4348c308bb462a0288586a5a259d90235aed6defc850f3148692894 has restarted: 1003 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T11:59:25+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T11:59:25+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://5059c63b60f570bb1ee467e8c1c82c242780d2a3af6efc74ed28cf30334623f0 has restarted: 1019 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T11:59:14+00:00 - Reason: None 	 Type: Ready
2023-08-21T11:59:14+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://6487c5a30fe70b8b1193604c3d69d3c6d8d6727304c9b589edb18a032053f491 has restarted: 1020 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T11:59:41+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T11:59:41+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://1cd9e8e3d951e3432676dacfead136b7b68a805246125212ecb7c16de6d5b7b7 has restarted: 1019 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T14:59:01+00:00 - Reason: None 	 Type: Ready
2023-08-21T14:59:01+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://f47ff77c1f58fcbed0b62a6fac5ef43e669632aadc91f8ad58c32276ed7ed9a2 has restarted: 1066 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T14:55:56+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T14:55:56+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://a4b4aad46698837e260e9e6378b20aca3641c13468cf89d7b5a957064deb738e has restarted: 1067 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T14:59:32+00:00 - Reason: None 	 Type: Ready
2023-08-21T14:59:32+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://e05c3ca0dc1cd6fc2e793f89e6c2f3015f9766f0b06c15b19899dcff79192bb8 has restarted: 1066 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T15:59:51+00:00 - Reason: None 	 Type: Ready
2023-08-21T15:59:51+00:00 - Reason: None 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://d41357dbb7ed0c9703acafb6f044ee72e8f814941a7893c74a0ac4918d2b66a0 has restarted: 1082 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T15:56:31+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T15:56:31+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://237f86b0d6531fa327492297bb785094ad805be24963894732547dd57825628c has restarted: 1083 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T15:55:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T15:55:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://23d790b193ce47f0d4fc85c0de2d1e55d27feb02b687125a883b2dade552ff9f has restarted: 1081 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T16:55:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T16:55:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://cf1de0ed6471727bd3ecc029654202a8437816f5966e6ddc40b40931bea87b34 has restarted: 1097 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T16:57:11+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T16:57:11+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://55c7e732b10238f934ab8f5c364bff68a863cd336570126214c8e6a65ac359d9 has restarted: 1099 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T16:56:21+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T16:56:21+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://2505d73277115154b7af73cfe887c6636a7f91c6142162a600b0710426fd8eef has restarted: 1097 number of times.

Looks like your deployment liveliness-check is failing.
Specifically, it looks like these pods are failing:

Pod: liveliness-check-6bf98bd74-2sgnw with the error listed below.
Pod: liveliness-check-6bf98bd74-62626 with the error listed below.
Pod: liveliness-check-6bf98bd74-sk9hz with the error listed below.

Logs for pod liveliness-check-6bf98bd74-2sgnw:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T17:56:01+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T17:56:01+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://fe83eb13a7a485c6579fee6e0de5d3b23842167bb2c2206ef30538d7842c0130 has restarted: 1113 number of times.

Logs for pod liveliness-check-6bf98bd74-62626:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T17:57:51+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T17:57:51+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://ad04e355c897ac2fa1f6876c4b1ef3774beab1fb4431aad8def3b21c8efebaec has restarted: 1115 number of times.

Logs for pod liveliness-check-6bf98bd74-sk9hz:
Seems your pod isn't producing any logs. Instead providing you with other information.
The last conditions your pods went through were:

2023-08-18T19:51:35+00:00 - Reason: None 	 Type: Initialized
2023-08-21T17:56:46+00:00 - Reason: ContainersNotReady 	 Type: Ready
2023-08-21T17:56:46+00:00 - Reason: ContainersNotReady 	 Type: ContainersReady
2023-08-18T19:51:35+00:00 - Reason: None 	 Type: PodScheduled

Containers launched under your pods with their stats:

Container containerd://623fb5e1024e461bf13fcb9526a027c8547f12f6aef6228f03207cd0f01af338 has restarted: 1113 number of times.


Change namespace to Yii\Arrays

I think we need to change namespace to Yii\Arrays. That would allow us adding more classes to the package that won't be helpers.

Would the repository/composer library be renamed to yiisoft/arrays too or not?
How would ArrayHelper be named/namespaced?

As for me:

yes: yiisoft/arrays
Yii\Arrays\ArrayHelper

@samdark can we move forward on this so I can resume the migration?

Renamed repository.

Namespace should be Yiisoft\Arrays

Done. Package should be republished to packagist using the new name.

Done.


answer build with meilisearch plugin failing.

When running
answer build --with github.com/apache/incubator-answer-plugins/search-meilisearch

If fails with
[go build -ldflags -X github.com/apache/incubator-answer/cmd.Version=1.2.1 -X github.com/apache/incubator-answer/cmd.Revision=3f696b6 -X github.com/apache/incubator-answer/cmd.Time=1702543995 -o /new_answer .]
# github.com/apache/incubator-answer-plugins/search-meilisearch
vendor/github.com/apache/incubator-answer-plugins/search-meilisearch/meilisearch.go:327:70: cannot use tagGroup (variable of type string) as []string value in argument to strings.Join
build failed exit status 1

Tried also different refs like  github.com/apache/incubator-answer-plugins/search-meilisearch@main, did not manage to get around the error.
answer -v:
answer version 1.2.1
revision: 3f696b6
build time:<PHONE_NUMBER>

build environment based on the official answer docker image:
FROM apache/answer:1.2.1 as builder

RUN apk --no-cache add \
    build-base git bash nodejs npm go && \
    npm install -g pnpm

RUN answer build \
    --with github.com/apache/incubator-answer-plugins/connector-basic \
    --with github.com/apache/incubator-answer-plugins/search-meilisearch \
    --output /usr/local/bin/answer_with_plugins

@LinkinStars Can you suggest Any workaround to build with meilisearch?

yes, the references are the same:

I'm testing within a docker build, so no caches at all.
thx for caring :heart_decoration:

Sounds good. We can fix what you said with the search-meilisearch/v1.2.1 tag. For example, for now you can do it via ./answer build --with<EMAIL_ADDRESS>command to pull this version of the plugin.

awesome, thx, @LinkinStars.
Can you create similar tags for the other plugins as well?

Thx so much!


Autorenewal of Lets Encypt is broken

This Bug Report affects these Traffic Control components:

Traffic Ops
Current behavior:

Autorenewal  (letsencrypt/autorenew) of Lets Encrypt is not working. POST letsencrypt/autorenew never returns and eventually taking the traffic ops down.
Expected behavior:

POST letsencrypt/autorenew should result in renewal of Lets encrypt.
Steps to reproduce:
topost /letsencrypt/autorenew  -k -a 2.0 --to-url https://traffic-ops.net --to-user ****--to-password ****--request-payload --request-headers
Ported 6184 to 4.1.x which ended up in this issue
This should be an issue in 6.x as well:
Given below is the code which initializes LE Request during POST:
https://github.com/apache/trafficcontrol/blob/308484ddfb37952901d8b138087d4b8f0c7b007d/traffic_ops/traffic_ops_golang/deliveryservice/acme.go#L478
The above snippet shows that we are initializing Key, But the flow for autorenew is missing this:
https://github.com/apache/trafficcontrol/blob/308484ddfb37952901d8b138087d4b8f0c7b007d/traffic_ops/traffic_ops_golang/deliveryservice/autorenewcerts.go#L239
Because of this, autorenew might not work well this INSERT
https://github.com/apache/trafficcontrol/blob/308484ddfb37952901d8b138087d4b8f0c7b007d/traffic_ops/traffic_ops_golang/deliveryservice/acme.go#L102
Code which sets the Key:
https://github.com/apache/trafficcontrol/blob/308484ddfb37952901d8b138087d4b8f0c7b007d/traffic_ops/traffic_ops_golang/deliveryservice/acme.go#L613

not working
LE is hard to test; can you be more specific about what's broken?

not working

LE is hard to test; can you be more specific about what's broken?

I have added more details. Please let me know if more details are required.


/proc/self/cmdline returns zygote64 in nativeForkAndSpecializePost

It should return the app name right?

nvm it takes couple seconds to return the real app name.
Guess it's better to put a note?

Process name is set here, I don't know where the delay comes from.
By the way, if you want the process name, you should read niceName in nativeForkAndSpecializePre instead.
Process should never be used as "real app name" since it is fully customizable (use a name without the lead ":" for android:process). To get package name , it's better to read appData. Here is an example, https://github.com/RikkaApps/Riru-LocationReportEnabler/blob/master/jni/main/main.cpp#L28-L46. Note packageName only exists in beta versions of Android 10, so it has been removed in Riru. It is not updated because the project has been archived.
Even "package name" in appData is not 100% reliable.  Multiple apps use android:sharedUserId plus android:process could run in the same process.
The best solution should be to maintain a "uid -> packages" map by self.

Thanks for the detailed explanation! I'm doing the following:
static bool isApp = false;

EXPORT void nativeForkAndSpecializePre(
        JNIEnv *env, jclass clazz, jint *_uid, jint *gid, jintArray *gids, jint *runtimeFlags,
        jobjectArray *rlimits, jint *mountExternal, jstring *seInfo, jstring *niceName,
        jintArray *fdsToClose, jintArray *fdsToIgnore, jboolean *is_child_zygote,
        jstring *instructionSet, jstring *appDataDir, jboolean *isTopApp, jobjectArray *pkgDataInfoList,
        jobjectArray *whitelistedDataInfoList, jboolean *bindMountAppDataDirs, jboolean *bindMountAppStorageDirs) {
    isApp = checkIsApp(env, appDataDir);
}

EXPORT int nativeForkAndSpecializePost(JNIEnv *env, jclass clazz, jint res) {
    if (res == 0) {
        // in app process
        if (isApp) {
            isApp = false;
            do::my_stuff();
        }
    } else {
        // in zygote process, res is child pid
        // don't print log here, see https://github.com/RikkaApps/Riru/blob/77adfd6a4a6a81bfd20569c910bc4854f2f84f5e/riru-core/jni/main/jni_native_method.cpp#L55-L66
    }
    return 0;
}

What I found weird is I'm getting multiple calls on do::my_stuff(); and later I found it's the child process that zygote64 forked. Thus I'm trying to get a "real name" to distinguish if I'm in the main process(in my understanding). I found the main process will have the app's package name WITH SOME DELAY. Currently I'm just waiting for 10 seconds and read /proc/self/cmdline

What makes you think do::my_stuff() is called multiple times?

I have LOGD in it and it's fired multiple times


[Question] How to open browser development tools?

What OS are you using?
Windows 10 x64
What programming language are you using (C/C++/Go/Rust)?
C#
What did you expect to see and what you saw instead?
I'd like to be able to open dev tools in the executable (the regular browser dev tools with console, DOM access, ...). However, I can't find information on how to achieve that.
Edit: Seems that the issue was that I was using https://github.com/webview-cs/webview-cs bindings which don't use the new Edge/Chromium stuff and instead only use the old IE/Edge.
Switching to https://github.com/webview/webview-csharp now allows me to press F12, which opens Microsoft Edge DevTools Preview for some reason but works as expected.
Switching has made me stuck at https://github.com/webview/webview_csharp/issues/8 though ;)

Even using the old stuff, you can get the external Microsoft dev tools (or find your f12chooser.exe) and run that directly.
https://www.microsoft.com/en-us/p/microsoft-edge-devtools-preview/9mzbfrmz0mnj?activetab=pivot:overviewtab
https://www.westerndevs.com/Development/f12-chooser-is-dev-tool-thing/


Multi-view fusion in nuscenes

Thanks for your excellent wrok! Additionally, I would like to know which images among 'CAM_FRONT', 'CAM_FRONT_RIGHT', 'CAM_BACK_RIGHT', 'CAM_BACK', 'CAM_BACK_LEFT', and 'CAM_FRONT_LEFT' are used for multi-view fusion in nuscenes.

You can check the feature fusion code for nuscenes here. We used all directions for multi-view feature fusion.


ModuleNotFoundError with Cryptodome in PasswordEncryption.py

When running PasswordEncryption.py, an error is prompted: ModuleNotFoundError: No module named 'Cryptodome'.
The error disappears when I replace all instances of from Cryptodome with from Crypto in the PasswordEncryption.py file.

i'll look into this issue and find a better alternative to cryptodome.

Installing pycryptodomex solved it for me.

i've replaced pycryptodome with cryptography. now, everything should work smoothly.


Update libcec-daemon for libcec-4.0.5

Thanks for this. It allows building against the current libcec...


FIX: install is requiring sklearn 0.23

Doing a python setup.py develop makes me install an older scikit learn version, which is not nice.
Is this really necessary or can we change it to scikit-learn>=0.23.2 ? cc @DavidSabbagh

It’s due pyriemann

On 19 Apr 2021, at 15:55, Denis A. Engemann @.***> wrote:

Doing a python setup.py develop makes me install an older scikit learn version, which is not nice.
Is this really necessary or can we change it to scikit-learn>=0.23.2 ? cc @DavidSabbagh
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Shall we just change the requirements @agramfort ?

Another option to consider is add PyRiemann via externals folder and maintain our own soup of it.

I would remove pyriemann from setup.py until a new release in on pypi
and tell here to use pyriemann master

Ok. Will look into that.


Seeds, Openssl, Libdb upgrades

https://www.reddit.com/r/TaCoCoin/comments/3ed3cp/we_need_compilers/cthmz6u
I'll look into the splash screen when I get a chance. It's using the tacocoin logo instead of that awesome darker one for some reason.

tweaked some things to make the splash better and update copyright years.


Avoriaz migration

First, am i correct in assuming Avoriaz development will stop?
If so, do you plan on offering any sort of migration guide or tool to help Avoriaz users move to vue-test-utils?

I won't stop developing avoriaz, but my focus is on vue-test-utils.
Adding a migration guide is on my todo list, but it's pretty low down. I'm not sure when I'll get around to it.
If a lot of people would find one useful I'll raise the priority of it.

Doesn't have to be fancy, just some quick tips, even posting in this thread would be helpful.

Curious as to your decision to keep Avoriaz going? Won't it be confusing have two extremely similar testing libraries?
You often see in "Vue vs X framework" discussions, that developers opting for Vue, enjoy not having to make as many decisions around libraries as there are official offerings: vue-router, vuex and soon vue-test-utils.

@rssfrncs I don't want people who built projects using avoriaz to be stuck.
Developing was probably the wrong word. I'll keep maintaining it, fixing bugs.

The main difference between avoriaz and vue-test-utils is the find API.
In avoriaz there is one method to traverse the render tree—find. find returns an array of wrappers that match the selector.
// avoriaz
const wrapper = mount(Component)
wrapper.find('div')[0].is('div')

In vue-test-utils, there are two methods to traverse the render tree—find and findAll. find returns the first wrapper matching the selector, findAll returns an array-like object.
// vue-test-utils
const wrapper = mount(Component)
wrapper.find('div').is('div')
wrapper.findAll('div').at(0).is('div')

Another difference is the name of the mount options:

avoriaz
vue-test-utils

globals
mocks

'instance
localVue

@eddyerburgh Honestly, I think it that would be the best thing to do. As someone who is working on a project with over 100 test cases (majority importing Avoriaz), I was slightly concerned to see vue-test-utils announced with you, the creator of Avoriaz, developing it. However, comparing the APIs, it seems like a relatively harmless migration and extremely worth it to be adopting an "official" library.

Ok, I've thought more about it, and I agree.
I'll add a deprecation notice and a migration guide to avoriaz when vue-test-utils is released 🙂

I'll add a deprecation notice and a migration guide to avoriaz when vue-test-utils is released 🙂

This was my plan for vue-test too :)

I've added a migration guide page to the avoriaz docs — https://eddyerburgh.gitbooks.io/avoriaz/content/guides/migrating-to-vue-test-utils.html


Remove credstash

We now have Parameter Store with KMS encryption or AWS Secret Store. I'll change that with one of these.

Well this is done! I can go to sleep now :)


Undocumented breaking change : FromSqlRaw returning null entity if all column values are null on keyless entity

If you read the mitigation section for the breaking change Query types are consolidated with entity types you are lead to believe that you only need to change the type DbQuery to DbSet<> and to configure the entity with HasNoKey().
However, a DbQuery with an empty result was returning an object instance where all properties where null.
On EF Core 3.0 the keyless entity will simply be null. As part of the mitigation we need to make sure that those null values are properly handled.
https://github.com/dotnet/efcore/issues/19537

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

ID: e4d0e044-b0cb-21e2-19c1-2f137da671ac
Version Independent ID: 1cbedd95-8640-1649-9967-d0ef71633534
Content: Breaking changes in EF Core 3.0 - EF Core
Content Source: entity-framework/core/what-is-new/ef-core-3.0/breaking-changes.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @ajcvickers
Microsoft Alias: avickers

@Tri125 The breaking change is actually this one: https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.0/breaking-changes#de. That being said, I agree that this consequence of the change  is not clear from the docs.

Thank you for the clarification!