[2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Quarkus Common - Parent .............. SUCCESS [  0.058 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Common - Reactive Messaging .......... SUCCESS [  0.541 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Messaging - Parent ................... SUCCESS [  0.050 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Messaging - Common ................... SUCCESS [ 50.196 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Messaging ............................ SUCCESS [  1.306 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: gRPC:: Runtime .... SUCCESS [  1.934 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Workitems :: RestWorkItem ................ SUCCESS [ 15.387 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: rest:: Runtime .... SUCCESS [  0.272 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Kubernetes Service Catalog .... SUCCESS [  4.226 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Kubernetes .................... SUCCESS [ 21.564 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Parent SUCCESS [  0.070 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog Tests Utils SUCCESS [  5.146 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog ... SUCCESS [02:17 min][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Kubernetes - Parent .................. SUCCESS [  0.050 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Kubernetes ........................... SUCCESS [ 56.149 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension .... SUCCESS [  0.030 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Runtime SUCCESS [  8.720 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Common .. SUCCESS [  9.339 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Generated SUCCESS [  0.408 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: gRPC:: Parser ..... SUCCESS [  0.519 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Serverless Workflow :: Rest:: Parser ..... SUCCESS [  7.712 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Common - Deployment .................. SUCCESS [  6.976 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Kubernetes - Deployment .............. SUCCESS [ 30.636 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Messaging - Deployment ............... SUCCESS [  2.068 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Workflows Extension :: Deployment  SUCCESS [  5.312 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: Parent ......... SUCCESS [  0.031 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: JDBC ........... SUCCESS [03:13 min][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Quarkus Persistence .................. SUCCESS [  0.023 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence JDBC - Parent ............ SUCCESS [  0.026 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence JDBC ..................... SUCCESS [  5.963 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Events ............. SUCCESS [  0.046 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Process - Parent .............. SUCCESS [  0.026 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Process ....................... SUCCESS [  1.049 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Test Utilities :: Quarkus ................ SUCCESS [ 18.543 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence JDBC - Deployment ........ SUCCESS [  2.128 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Process - Deployment .......... SUCCESS [  1.236 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Workflows Extension :: Integration Tests SUCCESS [04:36 min][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Workflows Extension :: Image Integration Tests SUCCESS [  02:44 h][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests SUCCESS [01:19 min][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests (Hot Reload) SUCCESS [02:00 min][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Decisions Extension :: Integration Tests SUCCESS [02:05 min][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Decicions Extension :: Integration Tests (Hot Reload) SUCCESS [01:36 min][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Predictions Extension :: Integration Tests SUCCESS [ 33.929 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Quarkus Test List ........................ SUCCESS [  2.068 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: Infinispan ..... SUCCESS [01:13 min][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Infinispan - Parent ...... SUCCESS [  0.062 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Infinispan ............... SUCCESS [  1.727 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Infinispan - Deployment .. SUCCESS [  1.325 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Infinispan Health Check .. SUCCESS [02:06 min][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Kafka Streams - Parent ... SUCCESS [  0.048 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Kafka Streams ............ SUCCESS [ 54.026 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Kafka Streams - Deployment SUCCESS [  1.225 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: File System .... SUCCESS [ 12.338 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence FileSystem - Parent ...... SUCCESS [  0.041 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence FileSystem ............... SUCCESS [  0.679 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence FileSystem - Deployment .. SUCCESS [  1.005 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: MongoDB ........ SUCCESS [ 54.222 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence MongoDB - Parent ......... SUCCESS [  0.053 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence MongoDB .................. SUCCESS [  3.383 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence MongoDB - Deployment ..... SUCCESS [  1.918 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: PostgreSQL ..... SUCCESS [ 34.802 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence PostgreSQL - Parent ...... SUCCESS [  0.051 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence PostgreSQL ............... SUCCESS [  5.524 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence PostgreSQL - Deployment .. SUCCESS [  3.133 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Persistence :: RocksDB ........ SUCCESS [ 14.175 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Rocksdb - Parent ......... SUCCESS [  0.051 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Quarkus Add-On Persistence Rocksdb .......... SUCCESS [  0.813 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Persistence Rocksdb - Deployment ..... SUCCESS [  1.935 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Common ......... SUCCESS [ 12.489 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process SVG - Parent ................. SUCCESS [  0.031 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process SVG .......................... SUCCESS [ 13.098 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process SVG - Deployment ............. SUCCESS [  1.917 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Process Management :: Common .. SUCCESS [  9.804 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process Management - Parent .......... SUCCESS [  0.028 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process Management ................... SUCCESS [ 13.315 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Process Management - Deployment ...... SUCCESS [  1.517 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Source Files :: Common ........ SUCCESS [  5.242 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Source Files - Parent ................ SUCCESS [  0.026 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Source Files ......................... SUCCESS [ 41.031 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Source Files - Deployment ............ SUCCESS [ 10.002 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Knative :: Parent ............. SUCCESS [  0.027 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Knative :: Eventing ........... SUCCESS [ 10.377 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative - Parent ..................... SUCCESS [  0.056 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.024 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Eventing ..................... SUCCESS [  1.516 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Eventing - Deployment ........ SUCCESS [ 15.524 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Serving - Parent ............. SUCCESS [  0.029 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Serving ...................... SUCCESS [01:13 min][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Knative Serving - Deployment ......... SUCCESS [  6.180 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Events :: Parent .............. SUCCESS [  0.027 s][2023-05-22T19:13:09.784Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions SUCCESS [ 17.004 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Decisions - Parent ............ SUCCESS [  0.023 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Decisions ..................... SUCCESS [  1.683 s][2023-05-22T19:13:09.784Z] [INFO] Kogito Add-On Events Decisions - Deployment ........ SUCCESS [  1.367 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions SUCCESS [ 10.347 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events Predictions - Parent .......... SUCCESS [  0.074 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events Predictions ................... SUCCESS [  1.389 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events Predictions - Deployment ...... SUCCESS [  1.034 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules .. SUCCESS [  9.673 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events Rules - Parent ................ SUCCESS [  0.098 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Quarkus SUCCESS [  1.382 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events Rules - Deployment ............ SUCCESS [  1.356 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: MongoDB ............. SUCCESS [ 21.210 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events MongoDB - Parent .............. SUCCESS [  0.035 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events MongoDB ....................... SUCCESS [ 58.062 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Events MongoDB - Deployment .......... SUCCESS [  0.773 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Marshallers :: Parent ......... SUCCESS [  0.025 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Marshallers:: Avro ............ SUCCESS [  9.911 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers :: Parent SUCCESS [  0.048 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Parent SUCCESS [  0.023 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro .. SUCCESS [  0.773 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Deployment SUCCESS [  0.888 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Parent .... SUCCESS [  0.024 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Runtimes .. SUCCESS [  3.049 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Deployment  SUCCESS [ 15.530 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Integration Tests SUCCESS [ 59.538 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Deployment SUCCESS [  0.180 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Explainability ................ SUCCESS [ 14.334 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Explainability - Parent .............. SUCCESS [  0.030 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Explainability ....................... SUCCESS [  4.031 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Explainability - Deployment .......... SUCCESS [  2.068 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Explainability - Integration tests ... SUCCESS [ 35.646 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Jobs .......................... SUCCESS [  0.026 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Jobs :: API ................... SUCCESS [  8.510 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Parent ................. SUCCESS [  0.062 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Parent ........ SUCCESS [  0.040 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Messaging ..... SUCCESS [  8.454 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus - Rest Callback ............. SUCCESS [ 13.196 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management Common ..... SUCCESS [  5.538 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Parent .... SUCCESS [  0.036 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs - Management ........... SUCCESS [ 16.710 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Deployment  SUCCESS [ 10.627 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Parent ..... SUCCESS [  0.036 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs - Messaging ............ SUCCESS [ 16.437 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Deployment . SUCCESS [ 12.760 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Parent SUCCESS [  0.061 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs - Knative Eventing ..... SUCCESS [ 15.900 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Deployment SUCCESS [ 16.094 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Common .............. SUCCESS [  8.093 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Mail - Parent ........................ SUCCESS [  0.024 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Mail ................................. SUCCESS [ 46.380 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Mail - Deployment .................... SUCCESS [  3.364 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Monitoring .................... SUCCESS [  0.025 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Monitoring Core ............... SUCCESS [ 17.658 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring - Parent .................. SUCCESS [  0.024 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Core ...................... SUCCESS [ 17.662 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Common .. SUCCESS [  1.616 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Prometheus - Parent ....... SUCCESS [  0.032 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Prometheus ................ SUCCESS [  7.012 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Prometheus - Deployment ... SUCCESS [  4.566 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Common ..... SUCCESS [  8.136 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Elastic - Parent .......... SUCCESS [  0.024 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Elastic ................... SUCCESS [  0.954 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Monitoring Elastic - Deployment ...... SUCCESS [  3.335 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Notification - Parent ........... SUCCESS [  0.052 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Notification .................... SUCCESS [  3.871 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Notification - Deployment ....... SUCCESS [  2.945 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Tracing ....................... SUCCESS [  0.025 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: TypedValue API ................ SUCCESS [  8.749 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Tracing :: API ................ SUCCESS [  8.756 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Tracing :: Common ............. SUCCESS [ 17.321 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Tracing Decision - Parent ............ SUCCESS [  0.026 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Tracing Decision ..................... SUCCESS [ 23.022 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Tracing Decision - Deployment ........ SUCCESS [  2.554 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Tracing Decision - Integration tests . SUCCESS [01:31 min][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Task Management :: Common ..... SUCCESS [  0.873 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Management - Parent ............. SUCCESS [  0.035 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Management ...................... SUCCESS [  5.254 s][2023-05-22T19:13:09.785Z] [INFO] Kogito Add-On Task Management - Deployment ......... SUCCESS [  1.570 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus ............. SUCCESS [  0.072 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus :: OpenAPI Client Codegen SUCCESS [  02:43 h][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Rules .... SUCCESS [ 55.160 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Decisions  SUCCESS [ 55.286 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Classic SUCCESS [ 42.109 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Reactive SUCCESS [ 47.143 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Maven Plugin ............................. SUCCESS [  9.870 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Integration Tests :: Maven Plugin ........  SUCCESS [01:02 min][2023-05-22T19:13:09.785Z] [INFO] Kogito :: DB Scripts Collection .................... SUCCESS [  0.444 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Predictions ................... SUCCESS [  0.026 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Predictions :: API ............ SUCCESS [  7.252 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Predictions :: SMILE .......... SUCCESS [  6.075 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Parser .. SUCCESS [  8.472 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Fluent ............ SUCCESS [  1.152 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Core ... SUCCESS [  9.858 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Rest ... SUCCESS [ 10.585 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Service  SUCCESS [  7.831 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor .......... SUCCESS [  0.041 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: gRPC ... SUCCESS [  0.366 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Kafka event implementation SUCCESS [ 11.419 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Tests .. SUCCESS [  9.544 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Spring Boot .............................. SUCCESS [  0.088 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Spring Boot :: BOM ....................... SUCCESS [  0.156 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Spring Boot ................... SUCCESS [  0.159 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: CloudEvents :: Spring Boot .... SUCCESS [  0.025 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot ...... SUCCESS [  1.315 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Events - Parent  SUCCESS [  0.026 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions :: Spring Boot SUCCESS [  0.435 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions :: Spring Boot SUCCESS [  0.804 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Spring Boot SUCCESS [  0.525 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events :: SprintBoot :: Process :: Kafka SUCCESS [  1.356 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Events ::  MongoDB :: SprintBoot SUCCESS [ 14.326 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Spring Boot :: Starters Parent ........... SUCCESS [  6.042 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Spring Boot :: Starter :: Decisions ...... SUCCESS [  0.215 s][2023-05-22T19:13:09.785Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot (ITs)  SUCCESS [01:00 min][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Monitoring :: Parent SUCCESS [  0.025 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Monitoring Core Springboot .... SUCCESS [ 19.055 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Springboot SUCCESS [  0.757 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Springboot . SUCCESS [  0.629 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Explainability :: Spring Boot Addon SUCCESS [ 12.693 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Spring Boot :: Starter :: Rules .......... SUCCESS [  0.346 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Spring Boot :: Starter :: Processes ...... SUCCESS [  1.034 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Spring Boot :: Starter :: Predictions .... SUCCESS [  0.525 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Spring Boot :: Starter ................... SUCCESS [  0.092 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management SprintBoot Addon SUCCESS [ 10.092 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Spring Boot Addon ... SUCCESS [  0.329 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Task notification :: Spring Boot Addon SUCCESS [  0.720 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Tracing :: Spring Boot ........ SUCCESS [ 15.556 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Rest Exception Handler:: Spring Boot ..... SUCCESS [  9.153 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Spring Boot Addon SUCCESS [ 12.169 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Process Management :: Spring Boot Addon SUCCESS [ 11.399 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Task Management :: Spring Boot Addon SUCCESS [  1.144 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Kubernetes ..... SUCCESS [ 27.168 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Persistence :: Parent SUCCESS [  0.024 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Persistence File System :: Springboot SUCCESS [  0.451 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Persistence Infinispan :: Springboot SUCCESS [  1.476 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Persistence JDBC :: Springboot  SUCCESS [  0.549 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Persistence MongoDB :: Springboot SUCCESS [  1.415 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Add-Ons :: Persistence PostgreSQL :: Springboot SUCCESS [  1.518 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Spring Boot :: Maven Archetype ........... SUCCESS [03:07 min][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Test Utilities :: Spring Boot ............ SUCCESS [ 19.396 s][2023-05-22T19:13:09.786Z] [INFO] Kogito :: Integration Tests :: Spring Boot ......... SUCCESS [06:00 min][2023-05-22T19:13:09.786Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:13:09.786Z] [INFO] BUILD SUCCESS[2023-05-22T19:13:09.786Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:13:09.786Z] [INFO] Total time:  02:56 h (Wall Clock)[2023-05-22T19:13:09.786Z] [INFO] Finished at: 2023-05-22T15:13:01-04:00[2023-05-22T19:13:09.786Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:13:09.786Z] [command]/usr/bin/docker system prune -f[2023-05-22T19:13:09.786Z] Deleted Containers:[2023-05-22T19:13:09.786Z] b2ed81f16f284ae1a3d80d63588be07b86bb212f1b7bdb29a05e7f72b0e715a6[2023-05-22T19:13:09.786Z] 1464af2d90fbe38cc18adca948ca21da85f18465f07e76eb55ad3550dcdb7059[2023-05-22T19:13:09.786Z] 9377a6a80a27da0929363abda997ddda7197c12902a359a6cb5751c59541a599[2023-05-22T19:13:09.786Z] [2023-05-22T19:13:09.786Z] Deleted Networks:[2023-05-22T19:13:09.786Z] b9cce54c-0d18-468d-afda-1dd0c8ed2018[2023-05-22T19:13:09.786Z] [2023-05-22T19:13:09.786Z] Total reclaimed space: 23.61kB[2023-05-22T19:13:09.786Z] [INFO] Execution summary for kiegroup/kogito-runtimes[2023-05-22T19:13:09.786Z] # [BEFORE] [kiegroup/kogito-runtimes] export INTEGRATION_BRANCH=[2023-05-22T19:13:09.786Z] [INFO] OK [Executed in 0.174908 ms][2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z] # [BEFORE] [kiegroup/kogito-runtimes] bash -c "if [ ! -z '' ] && [ -f .ci/environments/update.sh ]; then .ci/environments/update.sh  ; fi"[2023-05-22T19:13:09.786Z] [INFO] OK [Executed in 5.657402 ms][2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z] # [COMMANDS] [kiegroup/kogito-runtimes] export MVN_CMD=`bash -c "if [ '' = 'true' ]; then printf 'deploy  '; else printf 'install'; fi"`[2023-05-22T19:13:09.786Z] [INFO] OK [Executed in 5.232865 ms][2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z] # [COMMANDS] [kiegroup/kogito-runtimes] mvn dependency:tree clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config8401366233389701455tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B[2023-05-22T19:13:09.786Z] [INFO] NOT OK [Executed in 10600887.687249 ms][2023-05-22T19:13:09.786Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 143[2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z] # [AFTER] [kiegroup/kogito-runtimes] docker system prune -f[2023-05-22T19:13:09.786Z] [INFO] OK [Executed in 395.615764 ms][2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z]  [2023-05-22T19:13:09.786Z] # Uploading artifacts[2023-05-22T19:13:09.797Z] script returned exit code 143[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2023-05-22T19:13:09.864Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2023-05-22T19:13:09.971Z] Recording test results[2023-05-22T19:13:16.483Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2023-05-22T19:13:16.501Z] Archiving artifacts[Pipeline] script[Pipeline] {[Pipeline] sh[2023-05-22T19:13:17.595Z] + rm -rf console.log[Pipeline] sh[2023-05-22T19:13:17.888Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2552/consoleText[2023-05-22T19:13:17.888Z] + tail -n 300

(tests) - kogito-runtimes job #2553 was: ABORTED
Possible explanation: Most probably a timeout, please review

Reproducer
export BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage
build-chain build cross_pr -f 'https://raw.githubusercontent.com/kiegroup/kogito-pipelines/main/.ci/pull-request-config.yaml' -o 'bc' -p kiegroup/kogito-runtimes -u https://github.com/kiegroup/kogito-runtimes/pull/2988 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2553/display/redirect
Test results:

PASSED: 3331
FAILED: 0

Those are the test failures: none
See console log:

Console Logs
[2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Messaging - Common ................... SUCCESS [ 49.560 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Messaging ............................ SUCCESS [  1.217 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: gRPC:: Runtime .... SUCCESS [  2.542 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Workitems :: RestWorkItem ................ SUCCESS [ 15.333 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: rest:: Runtime .... SUCCESS [  0.323 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Kubernetes Service Catalog .... SUCCESS [  3.273 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Kubernetes .................... SUCCESS [ 25.357 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Parent SUCCESS [  0.026 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog Tests Utils SUCCESS [  6.720 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog ... SUCCESS [02:28 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Kubernetes - Parent .................. SUCCESS [  0.027 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Kubernetes ........................... SUCCESS [01:00 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension .... SUCCESS [  0.047 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Serverless Workflow Extension :: Runtime SUCCESS [  5.268 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Common .. SUCCESS [ 11.530 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Generated SUCCESS [  0.347 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: gRPC:: Parser ..... SUCCESS [  0.633 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Serverless Workflow :: Rest:: Parser ..... SUCCESS [  7.586 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Common - Deployment .................. SUCCESS [  5.785 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Kubernetes - Deployment .............. SUCCESS [ 38.968 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Messaging - Deployment ............... SUCCESS [  2.799 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Workflows Extension :: Deployment  SUCCESS [  5.136 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: Parent ......... SUCCESS [  1.166 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: JDBC ........... SUCCESS [03:17 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Quarkus Persistence .................. SUCCESS [  0.032 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence JDBC - Parent ............ SUCCESS [  0.054 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence JDBC ..................... SUCCESS [  7.646 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Events ............. SUCCESS [  0.057 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Process - Parent .............. SUCCESS [  0.048 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Process ....................... SUCCESS [  1.241 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Test Utilities :: Quarkus ................ SUCCESS [ 20.425 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence JDBC - Deployment ........ SUCCESS [  3.154 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Process - Deployment .......... SUCCESS [  1.057 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Workflows Extension :: Integration Tests SUCCESS [05:31 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Workflows Extension :: Image Integration Tests SUCCESS [  02:43 h][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests SUCCESS [01:31 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Rules Extension :: Integration Tests (Hot Reload) SUCCESS [02:08 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Decisions Extension :: Integration Tests SUCCESS [02:08 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Decicions Extension :: Integration Tests (Hot Reload) SUCCESS [01:38 min][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Predictions Extension :: Integration Tests SUCCESS [ 37.129 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Quarkus Test List ........................ SUCCESS [  1.527 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: Infinispan ..... SUCCESS [01:14 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Infinispan - Parent ...... SUCCESS [  0.530 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Infinispan ............... SUCCESS [  3.918 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Infinispan - Deployment .. SUCCESS [  1.275 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Infinispan Health Check .. SUCCESS [02:07 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Kafka Streams - Parent ... SUCCESS [  0.033 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Kafka Streams ............ SUCCESS [ 50.753 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Kafka Streams - Deployment SUCCESS [  1.740 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: File System .... SUCCESS [ 12.166 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence FileSystem - Parent ...... SUCCESS [  0.031 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence FileSystem ............... SUCCESS [  0.597 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence FileSystem - Deployment .. SUCCESS [  0.887 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: MongoDB ........ SUCCESS [ 51.419 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence MongoDB - Parent ......... SUCCESS [  0.165 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence MongoDB .................. SUCCESS [  3.986 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence MongoDB - Deployment ..... SUCCESS [  0.801 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: PostgreSQL ..... SUCCESS [ 35.794 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence PostgreSQL - Parent ...... SUCCESS [  0.048 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence PostgreSQL ............... SUCCESS [  3.862 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence PostgreSQL - Deployment .. SUCCESS [  2.366 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Persistence :: RocksDB ........ SUCCESS [ 13.644 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Rocksdb - Parent ......... SUCCESS [  0.063 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Quarkus Add-On Persistence Rocksdb .......... SUCCESS [  0.651 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Persistence Rocksdb - Deployment ..... SUCCESS [  0.963 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Common ......... SUCCESS [ 11.154 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process SVG - Parent ................. SUCCESS [  0.026 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process SVG .......................... SUCCESS [ 17.896 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process SVG - Deployment ............. SUCCESS [  1.666 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Process Management :: Common .. SUCCESS [  9.195 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process Management - Parent .......... SUCCESS [  0.025 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process Management ................... SUCCESS [ 12.222 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Process Management - Deployment ...... SUCCESS [  1.748 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Source Files :: Common ........ SUCCESS [  4.094 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Source Files - Parent ................ SUCCESS [  0.029 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Source Files ......................... SUCCESS [ 49.860 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Source Files - Deployment ............ SUCCESS [  7.459 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Knative :: Parent ............. SUCCESS [  0.035 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Knative :: Eventing ........... SUCCESS [ 12.678 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative - Parent ..................... SUCCESS [  0.032 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Eventing - Parent ............ SUCCESS [  0.043 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Eventing ..................... SUCCESS [  4.149 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Eventing - Deployment ........ SUCCESS [ 18.710 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Serving - Parent ............. SUCCESS [  0.032 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Serving ...................... SUCCESS [01:14 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Knative Serving - Deployment ......... SUCCESS [  2.181 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: Parent .............. SUCCESS [  0.038 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions SUCCESS [ 17.565 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Decisions - Parent ............ SUCCESS [  0.045 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Decisions ..................... SUCCESS [  1.461 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Decisions - Deployment ........ SUCCESS [  1.163 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions SUCCESS [  9.298 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Predictions - Parent .......... SUCCESS [  0.039 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Predictions ................... SUCCESS [  1.504 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Predictions - Deployment ...... SUCCESS [  2.246 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules .. SUCCESS [  9.459 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Rules - Parent ................ SUCCESS [  0.039 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Quarkus SUCCESS [  1.286 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events Rules - Deployment ............ SUCCESS [  2.722 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Events :: MongoDB ............. SUCCESS [ 19.680 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events MongoDB - Parent .............. SUCCESS [  0.032 s][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events MongoDB ....................... SUCCESS [01:03 min][2023-05-22T19:32:30.174Z] [INFO] Kogito Add-On Events MongoDB - Deployment .......... SUCCESS [  2.337 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Marshallers :: Parent ......... SUCCESS [  0.032 s][2023-05-22T19:32:30.174Z] [INFO] Kogito :: Add-Ons :: Marshallers:: Avro ............ SUCCESS [ 11.728 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers :: Parent SUCCESS [  0.036 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Parent SUCCESS [  0.030 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro .. SUCCESS [  0.857 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus:: Marshallers:: Avro:: Deployment SUCCESS [  1.161 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Parent .... SUCCESS [  0.052 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Runtimes .. SUCCESS [  2.722 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Deployment  SUCCESS [ 15.190 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Quarkus :: Camel :: Integration Tests SUCCESS [ 56.509 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Fabric8 Kubernetes Service Catalog - Deployment SUCCESS [  0.237 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Explainability ................ SUCCESS [ 15.981 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Explainability - Parent .............. SUCCESS [  0.032 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Explainability ....................... SUCCESS [  4.485 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Explainability - Deployment .......... SUCCESS [  2.526 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Explainability - Integration tests ... SUCCESS [ 45.456 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Jobs .......................... SUCCESS [  0.046 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Jobs :: API ................... SUCCESS [  7.843 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Parent ................. SUCCESS [  0.051 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Parent ........ SUCCESS [  0.036 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Common - Messaging ..... SUCCESS [  8.878 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus - Rest Callback ............. SUCCESS [ 15.454 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management Common ..... SUCCESS [  5.260 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Parent .... SUCCESS [  0.059 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs - Management ........... SUCCESS [ 15.432 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Management - Deployment  SUCCESS [  7.259 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Parent ..... SUCCESS [  0.040 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs - Messaging ............ SUCCESS [ 16.847 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Messaging - Deployment . SUCCESS [  8.356 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Parent SUCCESS [  0.037 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs - Knative Eventing ..... SUCCESS [ 15.101 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-Ons Quarkus Jobs Knative Eventing - Deployment SUCCESS [ 19.764 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Common .............. SUCCESS [  8.824 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Mail - Parent ........................ SUCCESS [  0.074 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Mail ................................. SUCCESS [ 47.697 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Mail - Deployment .................... SUCCESS [  1.927 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring .................... SUCCESS [  0.032 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Core ............... SUCCESS [ 20.064 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring - Parent .................. SUCCESS [  0.040 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Core ...................... SUCCESS [ 17.762 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Common .. SUCCESS [  1.382 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Prometheus - Parent ....... SUCCESS [  0.037 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Prometheus ................ SUCCESS [  6.417 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Prometheus - Deployment ... SUCCESS [  1.640 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Common ..... SUCCESS [  9.523 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Elastic - Parent .......... SUCCESS [  0.052 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Elastic ................... SUCCESS [  1.401 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Monitoring Elastic - Deployment ...... SUCCESS [  0.825 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Notification - Parent ........... SUCCESS [  0.040 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Notification .................... SUCCESS [  6.913 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Notification - Deployment ....... SUCCESS [  0.694 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Tracing ....................... SUCCESS [  0.025 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: TypedValue API ................ SUCCESS [  8.652 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Tracing :: API ................ SUCCESS [ 11.937 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Tracing :: Common ............. SUCCESS [ 19.662 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Tracing Decision - Parent ............ SUCCESS [  0.032 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Tracing Decision ..................... SUCCESS [ 24.089 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Tracing Decision - Deployment ........ SUCCESS [  3.983 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Tracing Decision - Integration tests . SUCCESS [01:25 min][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Task Management :: Common ..... SUCCESS [  0.474 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Management - Parent ............. SUCCESS [  0.039 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Management ...................... SUCCESS [  6.551 s][2023-05-22T19:32:30.175Z] [INFO] Kogito Add-On Task Management - Deployment ......... SUCCESS [  1.087 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus ............. SUCCESS [  0.081 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus :: OpenAPI Client Codegen SUCCESS [01:20 min][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Rules .... SUCCESS [ 53.527 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus :: Decisions  SUCCESS [01:01 min][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Classic SUCCESS [ 44.745 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Quarkus :: RESTEasy Reactive SUCCESS [ 46.964 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Maven Plugin ............................. SUCCESS [  8.063 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Integration Tests :: Maven Plugin ........  SUCCESS [01:25 min][2023-05-22T19:32:30.175Z] [INFO] Kogito :: DB Scripts Collection .................... SUCCESS [  0.832 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Predictions ................... SUCCESS [  0.024 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Predictions :: API ............ SUCCESS [  6.328 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Predictions :: SMILE .......... SUCCESS [  7.206 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: OpenAPI:: Parser .. SUCCESS [  8.035 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Fluent ............ SUCCESS [  0.932 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Core ... SUCCESS [ 11.299 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Rest ... SUCCESS [ 10.433 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Service  SUCCESS [  7.876 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor .......... SUCCESS [  0.038 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: gRPC ... SUCCESS [  0.272 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Kafka event implementation SUCCESS [ 11.910 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Serverless Workflow :: Executor:: Tests .. SUCCESS [  9.856 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot .............................. SUCCESS [  0.082 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: BOM ....................... SUCCESS [  0.037 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Spring Boot ................... SUCCESS [  0.038 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: CloudEvents :: Spring Boot .... SUCCESS [  0.076 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot ...... SUCCESS [  0.953 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Events - Parent  SUCCESS [  0.029 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Decisions :: Spring Boot SUCCESS [  0.884 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Predictions :: Spring Boot SUCCESS [  1.546 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Events :: Event-Driven Rules :: Spring Boot SUCCESS [  0.510 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Events :: SprintBoot :: Process :: Kafka SUCCESS [  2.798 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Events ::  MongoDB :: SprintBoot SUCCESS [ 15.160 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starters Parent ........... SUCCESS [  6.580 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starter :: Decisions ...... SUCCESS [  0.201 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Messaging :: Spring Boot (ITs)  SUCCESS [01:00 min][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Monitoring :: Parent SUCCESS [  0.037 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Core Springboot .... SUCCESS [ 19.104 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Prometheus Springboot SUCCESS [  0.959 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Monitoring Elastic Springboot . SUCCESS [  0.573 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Explainability :: Spring Boot Addon SUCCESS [ 13.079 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starter :: Rules .......... SUCCESS [  0.289 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starter :: Processes ...... SUCCESS [  0.524 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starter :: Predictions .... SUCCESS [  0.204 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Spring Boot :: Starter ................... SUCCESS [  0.090 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Jobs :: Management SprintBoot Addon SUCCESS [  9.004 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: E-Mail :: Spring Boot Addon ... SUCCESS [  0.902 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Task notification :: Spring Boot Addon SUCCESS [  1.860 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Tracing :: Spring Boot ........ SUCCESS [ 17.165 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Rest Exception Handler:: Spring Boot ..... SUCCESS [ 10.509 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Process SVG :: Spring Boot Addon SUCCESS [ 12.930 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Process Management :: Spring Boot Addon SUCCESS [ 10.483 s][2023-05-22T19:32:30.175Z] [INFO] Kogito :: Add-Ons :: Task Management :: Spring Boot Addon SUCCESS [  1.226 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Kubernetes ..... SUCCESS [ 30.708 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Spring Boot :: Persistence :: Parent SUCCESS [  0.051 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Persistence File System :: Springboot SUCCESS [  0.331 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Persistence Infinispan :: Springboot SUCCESS [  1.840 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Persistence JDBC :: Springboot  SUCCESS [  0.401 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Persistence MongoDB :: Springboot SUCCESS [  1.761 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Add-Ons :: Persistence PostgreSQL :: Springboot SUCCESS [  1.592 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Spring Boot :: Maven Archetype ........... SUCCESS [03:17 min][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Test Utilities :: Spring Boot ............ SUCCESS [ 21.723 s][2023-05-22T19:32:30.176Z] [INFO] Kogito :: Integration Tests :: Spring Boot ......... SUCCESS [05:55 min][2023-05-22T19:32:30.176Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:32:30.176Z] [INFO] BUILD SUCCESS[2023-05-22T19:32:30.176Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:32:30.176Z] [INFO] Total time:  02:56 h (Wall Clock)[2023-05-22T19:32:30.176Z] [INFO] Finished at: 2023-05-22T15:32:18-04:00[2023-05-22T19:32:30.176Z] [INFO] ------------------------------------------------------------------------[2023-05-22T19:32:30.176Z] [command]/usr/bin/docker system prune -f[2023-05-22T19:32:30.176Z] Deleted Containers:[2023-05-22T19:32:30.176Z] fc340d424678fca43b6f05bf0158e49cb698331583feba715420ad591d8af1dc[2023-05-22T19:32:30.176Z] [2023-05-22T19:32:30.176Z] Deleted Networks:[2023-05-22T19:32:30.176Z] fe3bee65-4557-4203-9d4c-fb5e7fb9b799[2023-05-22T19:32:30.176Z] [2023-05-22T19:32:30.176Z] Total reclaimed space: 7.866kB[2023-05-22T19:32:30.176Z] [INFO] Execution summary for kiegroup/kogito-runtimes[2023-05-22T19:32:30.176Z] # [BEFORE] [kiegroup/kogito-runtimes] export INTEGRATION_BRANCH=[2023-05-22T19:32:30.176Z] [INFO] OK [Executed in 0.185588 ms][2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] # [BEFORE] [kiegroup/kogito-runtimes] bash -c "if [ ! -z '' ] && [ -f .ci/environments/update.sh ]; then .ci/environments/update.sh  ; fi"[2023-05-22T19:32:30.176Z] [INFO] OK [Executed in 6.92531 ms][2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] # [COMMANDS] [kiegroup/kogito-runtimes] export MVN_CMD=`bash -c "if [ '' = 'true' ]; then printf 'deploy  '; else printf 'install'; fi"`[2023-05-22T19:32:30.176Z] [INFO] OK [Executed in 5.234759 ms][2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] # [COMMANDS] [kiegroup/kogito-runtimes] mvn dependency:tree clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config17893415573414937895tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B[2023-05-22T19:32:30.176Z] [INFO] NOT OK [Executed in 10585256.451118 ms][2023-05-22T19:32:30.176Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 143[2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] # [AFTER] [kiegroup/kogito-runtimes] docker system prune -f[2023-05-22T19:32:30.176Z] [INFO] OK [Executed in 316.218183 ms][2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] # Uploading artifacts[2023-05-22T19:32:30.176Z] [INFO] Will not upload any artifacts in CLI environment[2023-05-22T19:32:30.176Z]  [2023-05-22T19:32:30.176Z] [ERROR] Failed to execute commands for kiegroup/kogito-runtimes[2023-05-22T19:32:30.176Z] [ERROR] Failed to execute mvn dependency:tree clean install  -s /home/jenkins/workspace/KIE/kogito/main/pullrequest/kogito-runtimes.tests.kogito-runtimes@tmp/config17893415573414937895tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -T 1C -Dvalidate-formatting -Prun-code-coverage  -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B :[2023-05-22T19:32:30.176Z] [ERROR] The process '/opt/tools/apache-maven-3.8.7/bin/mvn' failed with exit code 143[2023-05-22T19:32:30.193Z] script returned exit code 143[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[2023-05-22T19:32:30.261Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] junit[2023-05-22T19:32:30.362Z] Recording test results[2023-05-22T19:32:37.273Z] [Checks API] No suitable checks publisher found.[Pipeline] archiveArtifacts[2023-05-22T19:32:37.290Z] Archiving artifacts[Pipeline] script[Pipeline] {[Pipeline] sh[2023-05-22T19:32:38.430Z] + rm -rf console.log[Pipeline] sh[2023-05-22T19:32:38.721Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.kogito-runtimes/2553/consoleText[2023-05-22T19:32:38.721Z] + tail -n 300

jenkins run kogito-runtimes tests


kube: values: Describe role names in the sizing section

This adds a comment in the sizing section to describe how the role names are generated (since those are not literally the names of the roles).

This PR now has merge conflicts because the sizing.{cpu,memory} settings have been moved. Please rebase PR on top of master.


Make flashinfer kernels cuda graphs friendly

Thanks for creating these awesome kernels! I am trying to get flashinfer kernels to work with cuda graphs. But it appears that several parallelism decisions (block size, num_q_tiles, etc.) are made on the fly based on the input data in the forward function. This makes it difficult to capture flashinfer kernels in cuda graphs in a generic manner. I think one solution to the problem would be to introduce a launcher kernel which would factor in the input metadata and launch the actual the actual cuda kernel using dynamic parallelism. Towards that, following are the items I have identified --
1. BatchPrefillWithPagedKVCachePyTorchWrapper::Forward -- handle return lse?
2. BatchPrefillWithPagedKVCachePyTorchWrapper::Forward -- paged_kv_t batch_size should not be on cpu side
3. BatchPrefillWithPagedKVCacheWrapperDispatched -- make cuda device function or get rid of it
4. BatchPrefillWithPagedKVCacheWrapperDispatched -- num_frags_x, num_qo_tiles, batch size need to be
5. BatchPrefillWithPagedKVCacheWrapperDispatched -- do not access handler state directly in the function
6. BatchPrefillWithPagedKVCacheDispatched -- make cuda device function
7. BatchPrefillWithPagedKVCacheDispatched -- put num_qo_tiles on device accessible memory
8. BatchPrefillWithPagedKVCacheDispatched -- Make validations gpu friendly
9. Batch size should be explicit input parameter not be based on length of indptr, so that inputs can be padded.

@yzh119 please let me know what would be the best way to proceed?

Hi @AgrawalAmey , thanks for bringing this up, I have some ideas about the CUDA graph integration with flashinfer:
The kernels to be executed can be determined before the a decode/prefill step (for all layers) by analyze the shapes, we can compile the CUDA Graph for all possible combinations (not too many) ahead of time, and dispatch to one of them according to the shapes.
Regarding dynamic parallelism:

introduce a launcher kernel which would factor in the input metadata and launch the actual the actual cuda kernel using dynamic parallelism

It sounds tricky to me because the required shared memory size/grid size varies for different schedules.

Hi @yzh119!
I have one implementation in sarathi-serve which tries to list different combinations, and capture them. But with increasing batch size and big variance in input sequences, the number of possibilities seemed explode. Plus, prefill + decode requests clubbed together makes it further more challenging. The memory cost of cuda graphs becomes too high as the number of combinations increases.
The child kernel/dynamic parallelism proposal is aimed to solve the challenge with different grid size etc. Essentially, the launcher kernel will be triggered with a single warp. Inside the launcher kernel, we can determine all the launch params and launch the actual attention kernel.

A sample program to explain what I mean:
#include <cuda_runtime.h>
#include <iostream>

__global__ void subKernel(int *data) {
    printf("Data before sub kernel: %d\n", *data);
    (*data) -= 1;
}

__global__ void addKernel(int *data) {
    printf("Data before add kernel: %d\n", *data);
    (*data) += 1;
}

struct UserData {
    int data;
    bool op;
};

__global__ void launchChildKernelFromDevice(void *_userData) {
    UserData *userData = (UserData *)_userData;
    bool op = userData->op;

    if (op) {
        addKernel<<<1, 1>>>((int*)userData);
    } else {
        subKernel<<<1, 1>>>((int*)userData);
    }
}

int main() {
    cudaStream_t stream;
    cudaStreamCreate(&stream);

    UserData *userData;
    cudaMallocHost(&userData, sizeof(UserData));

    userData->data = 10;
    userData->op = true;

    // run add kernel for sanity check

    cudaStreamSynchronize(stream);
    std::cout << "Data before kernel: " << userData->data << std::endl;
    launchChildKernelFromDevice<<<1, 1, 0, stream>>>(userData);
    cudaStreamSynchronize(stream);
    std::cout << "Data after kernel: " << userData->data << std::endl;

    cudaGraph_t graph;
    cudaGraphExec_t instance;

    // Begin graph capture
    cudaStreamSynchronize(stream);
    cudaStreamBeginCapture(stream, cudaStreamCaptureModeGlobal);

    // Use cuda host function to launch child kernel
    launchChildKernelFromDevice<<<1, 1, 0, stream>>>(userData);

    // End graph capture
    cudaStreamEndCapture(stream, &graph);
    cudaGraphInstantiate(&instance, graph, NULL, NULL, 0);

    cudaStreamSynchronize(stream);

    printf("Data after graph: %d\n", userData->data);

    // Run the graph
    cudaGraphLaunch(instance, stream);
    cudaStreamSynchronize(stream);

    printf("Data after graph replay: %d\n", userData->data);

    userData->op = false;
    cudaGraphLaunch(instance, stream);
    cudaStreamSynchronize(stream);

    printf("Data after graph replay with different op: %d\n", userData->data);

    cudaGraphExecDestroy(instance);
    cudaGraphDestroy(graph);
    cudaStreamDestroy(stream);
    cudaFree(userData);

    return 0;
}

Thanks for your explaination, that's sounds reasonable.
To proceed, I'd love to write some documentations on our dispatching rules and see if we can describe them in dynamic parallelism. Before that I have to make #75 done because it will affect our dispatching strategy.
Glad to catch up next week and we can schedule a meeting on zoom (you can drop me an email at  zhye@cs.washington.edu).

Yes, that would be great, I will send out a when2meet link on email, thank you!

Hey @ZSL98, we are working with the vLLM team to get Sarathi-Serve scheduler support inside vLLM

The CUDA graph compatibility was resolved in https://github.com/flashinfer-ai/flashinfer/releases/tag/v0.0.5
The current strategy is:

If batch size is large enough, we don't use split-k and the kernel can be traced properly (we need to reuse the indptr/indices/last_page_len buffer, this was properly handled in PyTorch wrapper APIs).
If batch size is small, we use split-k, but the grid size must be fixed. We set the grid size to a fix value which is computed from the number of SMs in GPU, and we have a kernel argument block_valid_mask to determine whether to skip one threadblock's computation to achieve runtime dynamism.

@yzh119  thanks a lot for all the amazing work! I wanted to understand split-k behaves when the sequence length is significantly different between capture and replay time. For instance, if during capture we have seq length of 1k and during replay we have a seq of length 100k, would the parallelization parameters get applied appropriately?

Yes, they will be properly handled.
When cudagraph is enabled, we decides whether to split-k only on batch size (for decode) and query lengths (for append), not on kv-cache length, that said, so it's safe to capture when kv-cache length is small (we have test cases for capturing for small kv-length and replay with long: https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/python/tests/test_batch_decode_kernels.py#L136-L286). once batch-size/query lengths are determined, the kernel grid size are fixed and we use block valid mask for dynamic parallelism:

decode

defined: https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/include/flashinfer/attention/handler.cuh#L389-L401
used https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/include/flashinfer/attention/decode.cuh#L542

prefill/append

defined: https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/include/flashinfer/attention/handler.cuh#L749-L753
used: https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/include/flashinfer/attention/prefill.cuh#L1365-L1367

There is one tricky part about prefill kernels, we pass kv_chunk_size as input arguments and it doesn't work in CUDA graph mode because the input argument is fixed at capture time. So we pass a pointer to a global memory address that stores this value instead: https://github.com/flashinfer-ai/flashinfer/blob/231b1dc89cd5cdaa485ac3c701cbd93ab9c05a90/include/flashinfer/attention/prefill.cuh#L1362
and we will change its value in BeginForward functions during the generation process.

This is great! Thanks a lot for the in-depth description. I will go ahead and add cuda graph support in sarathi-serve based on this.


Implement arm sim

Since .mp4 files are generated by Python scripts, that extension should probably be added to the .gitignore and the generated .mp4 should be removed from this PR.


Issue 45 Debug (NOT for MERGING)

Closes/fixes/resolves issue(s)?
nothing
What was added/changed/fixed?
creds rendering with proper policies
Related issue(s)? [Optional]
Others [Optional]
Checklist (after created PR)

[ ] Added reviewers
[ ] Added assignee(s)
[ ] Added label(s)
[ ] Added to project
[ ] Added to milestone

Thanks for testing this 😃 Got fixed in #47


[Bug][Azure Devops] Invalid Personal Access Token

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I want to set up an Azure Devops connection, and I have encountered these questions:

I don't know to generate a PAT. After clicking the link,

go to https://devlake.apache.org/docs/v0.19/Configuration/AzureDevOps/#auth-tokens , there is no efficent guide, only some text like this:

I generate a PAT following https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows, my token is like this:

and I paste it to devlake connection page, it turns out something wrong.

I have noticed that "Please select ALL ACCESSIBLE ORGANIZATIONS for the Organization field when you create the PAT.", but  my personal access token cannot change this field. I don't know why.
What do you expect to happen

An clear way to help me to generate PAT.
My token works well.

How to reproduce
Just try to use Azure Devops connection, and you will reproduce it.
Anything else
No response
Version
main
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@keon94  @CamilleTeruel  Can you help me?

@CamilleTeruel Thanks, it helps.


Add mdb.bin support.

Since mdbdump can decode mdbe.bin, is it possible to decode and encode mdb.bin as well? Thank you.

Hey! Yes I think this is possible, but honestly I am so far away from this project at this point that I have no intent to go back to it. I believe there are some people actively working to re-encode mdb.bin with new data but I don't really have a good idea of where this work is being done sorry. Honestly, I should archive this project. I'll leave it up so people can grab the code, but I won't be working on it anymore.


Does python wrapper support Multi-class  classification?

Does python wrapper support Multi-class  classification?

Yes
Steven Du writes:

Does python wrapper support Multi-class classification?
—
Reply to this email directly or view it on GitHub.*

thanks


Added 3 waste collector sensors

3 sensors for waste collection. 2 in the Netherlands and 1 in Belgium

  "pippyn/Home-Assistant-Sensor-Groningen-Afvalwijzer",
  "pippyn/Home-Assistant-Sensor-Groningen-Afvalwijzer"

These are identical.

 I'm sorry 😐


Raw SQL documentation (FromSql method) doesn't mention the assembly and namespace

Where is FromSql? The documentation should mention what assembly, namespace and class contains this method.

@diego-pathmatics Which documentation are you referring to? Can you provide a link?

Sure. It's this document:
https://docs.microsoft.com/en-us/ef/core/querying/raw-sql
On Fri, Feb 15, 2019 at 9:55 AM Arthur Vickers<EMAIL_ADDRESS>wrote:

@diego-pathmatics https://github.com/diego-pathmatics Which
documentation are you referring to? Can you provide a link?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/EntityFrameworkCore/issues/14683#issuecomment-464140803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApYUnNrNJyAfxZObinm2j9p1Kk-eW5FNks5vNvSlgaJpZM4a4YzL
.

--
http://www.pathmatics.com/
Diego Fulgueira
Principal Engineer
Pathmatics, Inc.
e<EMAIL_ADDRESS><EMAIL_ADDRESS>


181032483 - Increase deform triangle transparency

Increase deformation triangle transparency  (0.8 → 0.5)
Before:

After:

PT Story:
[#181032483]
https://www.pivotaltracker.com/n/projects/2441249/stories/181032483/comments/229210903

@mklewandowski  this is my first single 8-bit PR.  :D


Dynamic Incremental Versioning

The current evaluation process uses the configuration versions in the "configuration sets" folder. This allows RRE to run the evaluation against those versions and therefore make useful comparisons between them.
Another option could be (see issue #54) to version the evaluation process itself; that is: each time the evaluation is executed, it will be persisted (again, see #54) and versioned.
Subsequently, some external BI/Reporting tool could use that data in order to make comparisons between different executions (which in this case could be called "versions")

Hi @binarymax,
I think #54 it's the issue you're looking for. Ideally the target persistence model should be pluggable (in this case Elasticsearch but in another scenario a customer wanted to have that data in relational database).
Then yes, once data is in ES you can query it using Kibana.
This issue is specific for "versioning" the persisted data. I added that after #54 trying to figure out how to compare different evaluation executions.
So, just to give some explanation about my reasoning,  at the moment you have (example) three folders 1.1, 1.2 and 1.3. Each time RRE executes, it will evaluate all of them so the versioning is implicit (i.e. the json output file contains, for each metric, three values).
If you

leave the configuration folders
change the output model from locale FS to Elasticsearch

then versioning is not a problem, because the evaluation output always contains those three versions. In other words: each time you run RRE it will evaluate all versions.
The reason behind this issue was related to a customer who didn't want to maintain the configuration sets: I had just one configuration folder with the last version; so, the RRE output didn't compare anything because only one version was in the JSON output.
So the idea was: for each execution, the output is persisted somewhere and is tagged with a version (with a timstamp for example). So after n executions, you will have n comparable versions.
Sorry for the disgression: the short answer is #54 :D

Thanks for the quick reply!  I was thinking of using the reporting plugin and adding a new output there to send the evaluation to elastic, that can be queried by kibana...but now I see your point about persistence  (we shouldn't overwrite/repost the old evaluations that already exist).


date formatting

days of the month shouldn't have the leading zero:

It's in a few places, I've corrected it on the homepage, I'll go through the templates

PR to remove the leading 0 in displayed dates - https://github.com/alistapart/AListApart/pull/412


request

please add some mirai commands 😄, idk how to code 🥹

there are many commands, please be specific

uhm economy like slot and other

and the video and audio command is not working


what is license type of this repo?

thank you :)

The project is under The BSD 3-Clause License, and I add the license file.


Remove invalid build constraint

As fas as the git history can tell, the constraint was never referenced
by any script, never used.
$ go vet test/integration/integration_test.go
test/integration/integration_test.go:1: invalid non-alphanumeric build
constraint: integration,!no-docker

@bparees PTAL

i think it was probably a travis thing back when travis couldn't run tests that needed docker?
[merge]

i think it was probably a travis thing back when travis couldn't run tests that needed docker?

I don't know, maybe. Currently we don't run integration tests in Travis. (and to be sure, are we running it with our bot on merge?)

and to be sure, are we running it with our bot on merge?

yes, the vagrant plugin run_sti_tests command is running them explicitly, though they aren't a part of our Makefile.


Change dependency and delete patch that was fixed upstream in gumyr/build123d

build123d does not depend on cadquery but it does depend on cadquery-ocp which is just called ocp on conda. I also deleted a patch file that is no longer needed as it was fixed upstream.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11981089975. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ requirements: run: ocp >= 7.7.2 should not contain a space between relational operator and the version, i.e. ocp >=7.7.2

For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12528103293. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12528127724. Examine the logs at this URL for more detail.

Thank you! I missed that the cadquery part wasn't used.


Update monaco 0.43.0

The bug in version 0.41 from monaco editor appears to be fixed, as it's also stated in their changelog.  In additions, this adds:

Add new option renderSideBySideInlineBreakpoint to Java wrapper
Add mdx to monaco languages + showcase sample

#1297

Ahh sorry when I merged the other pull request it automatically closed this one and i can't reopen it it says it was part of a base branch or something like that?


[AIRFLOW-238] fix flask-admin==1.4.1 breaks the build

The new flask-admin==1.4.1 release on 2016-06-13 breaks the Airflow
release currently in Pypi (<IP_ADDRESS>). This fixes the edge case triggered
by this new release.
Note that <IP_ADDRESS> was fixed by pinning flask-admin to 1.4.0.

Are we going to cut a new release for this?

Derp, just saw the release note. Disregard comment above.

LGTM

@mistercrunch you ar pinning against 1.4.1 I assume that is correct, but your message states 1.4.0


Can hprox Loging authentication information?

I tried your hprox. Very nice project. Usage is simple. I feel it reacts quickly.
I have a question.
Can  hprox write the username (authentication information) to the log?
I use hprox with --loglevel with each all loglevel option. but user information did not appear.
Caddy can log the authenticate information by using  Base64, and Shadowsocks can write the authenticate information in plaintext to the log.
Do you have similar functionality? If not, are there any plans to implement it in the future?

Can hprox write the username (authentication information) to the log?

Currently hprox will only show name of authentication files in log, but not detailed user information, whether base64-encoded or in plaintext. What's the purpose of reading such informations from logging?

Caddy can log the authenticate information by using Base64, and Shadowsocks can write the authenticate information in plaintext to the log.

hprox support HTTP basic authentications with option -a/--auth userpass.txt, it's a text file with multiple lines (for multiple user support), each line contains a user:pass pairs in plaintext. In addition, all failed authentication will be logged with WARN log level, and that's all.

Thanks for the quick reply.

What's the purpose of reading such informations from logging?

(1)
I want to provide my server to multiple users. So I want to know which users used the server and when.
(2)
In addition, if the user name is included in log like as ...
unauthorized request (username):,
it can help to see which user has trouble with the wrong password.
I sincerely hope for this feature. Is this a difficult request?

You can now enable --loglevel trace to see all proxy authentication outcomes, something like
[TRACE] authorized request (credential: user:pass) from X.X.X.X

You can also find statically linked binary of git master at circleci artifacts page, once the compilation is finished.

Thank you so so much.
I really appreciate your work.
I will try the new version.

I compiled from source code and tried it.
I was able to log in exactly the format I wanted.
Thanks so much!


'Chat' is not translated into Spanish in the add icon while it is shown as 'Chatear' in other places

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open web chrome
Change language to spanish
Go to profile > Settings >Go to workspace > Click on the ? icon on top. Notice that Chat with Concierge displays 'Chatear con Concierge' where the word 'Chat' has been translated.
Click on the + add icon and see that it displays 'Nuevo Chat' where the word chat has not been translated.

Expected Result:
The word 'Chat' should be translated into Spanish on the add icon menu
Actual Result:
The word 'Chat' is not translated on the add icon menu but has been translated in 'Chat with Concierge' section
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.88-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/227258279-3d4bfbc4-4271-4910-a8aa-50a0a1a21cde.mp4

Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679569095656399
View all open jobs on GitHub

Triggered auto assignment to @maddylewis (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

I believe that's simply the verb (chatear) vs the noun (chat), so this would be considered expected behavior.

Agree, I don't think this is a bug but tagging @JmillsExpensify for quick confirmation.


Unable to match Discord channel using their id

Hi,
I have a channel in Discord named as :crown:-help
Because I can't paste that in the config file, i have used #:crown:-help command to retrieve its ID.
The bot doesnt join the channel.

@bothoem try alternative texts instead of paste this emoji: https://www.fileformat.info/info/unicode/char/1f451/index.htm

Pasting the emoji should work, as far as I know, but if it doesn't, the ID fallback should also work. Would you be able to provide a snippet of your config, if this is still a problem?


Correct dead arg elimination

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.25%. Comparing base (b7c96de) to head (fccac36).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1421      +/-   ##
==========================================
- Coverage   69.95%   67.25%   -2.70%
==========================================
  Files          29       29
  Lines       10488    10122     -366
==========================================
- Hits         7337     6808     -529
- Misses       3151     3314     +163

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix uninstall not working when version changes.

Changes to the core

[x] Followed hacking.md.

https://github.com/caskroom/homebrew-cask/issues/2988
https://github.com/caskroom/homebrew-cask/issues/14058

I think a change of this magnitude warrants some new tests. Once those are added and the currently failing tests are fixed, I'm all for merging this 👍

@jawshooah, what exactly is PERSISTENT_METADATA_SUBDIRS? Is the gpg sub-directory used for anything else than signature.asc?
According to fetch_sig in gpg.rb, this is only used for caching. Wouldn't  Hbc.cache be a better place for signature.asc files?

@reitermarkus I'm not sure. Looks like it was added in https://github.com/caskroom/homebrew-cask/pull/6117 "to provide persistent per-distribution locations to for GPG data". I'd be fine with moving the signature file to Hbc.cache

Ah, I had an error in thinking:
I thought the gpg directory would be incaskroom/cask/.metadata/gpg, which would result in a conflict when globbing the .metadata directory to retreive timestamped versions.
But actually it's stored in caskroom/cask/.metadata/version/timestamp/gpg, so there's no conflict.

@jawshooah, could you take a look at the test I have added (and the one I have altered)?
Also, not sure what would be the best way to reuse the code from the uninstalls one version at a time. MiniTest doesn't have a before(:each), right?
Or should I simply add the test for the cask 1.2.3 is still installed message into the existing one?

Ok, apparently after and before are equivalent to teardown and setup. Strange this is, after and before are working, teardown and setup are not.

@reitermarkus LGTM, merge when ready 👍

This pull request was merged in 36a98c5a4639f62cad6ecd82f896cbc080c0969e...1835d6d5bd415da0d32924416e2e6edb8fa585b7.


Fixes gradle autocomplete so it includes subproject tasks

This fixes the gradle plugin. The regular expression used to pull task names didn't include a colon. Subprojects in gradle are of the form foo:fooTask, so they weren't being included. This fixes the bug.

Can we get a few +1s here to confirm this works?


CSGPolygon add interpolation

This new feature come from my proposal:
Add Scaling/Modify a CSG Polygon in PathFollow when PathNode is drawing the mesh
godotengine/godot-proposals#1062
This pull request supersede #41499 where is now updated with the last PR.
3.x version is here --> #53462
This new pull request can interpolate in all CSGPolygon mode.
The interpolation work using a Curve who interpolate between two polygon array. If both polygons are equal, a single scaling mode is active.

If the polygon2 is empty, when you active the interpolation bool, you make a copy of the first polygon to the second. Is a way to reset or help you for editing the polygons.
No interpolation are happening if the curve is null and if the size of polygon2 is different of the polygon.
The interpolation make 3 styles of modification, like a scaling, moving or expanding.
Those video show how that work for depth mode, spin mode and path mode. All videos is in 5 fps.
Mode Depth :
Doesn't use the avantage of path_interval. The interpolation is straight up from point to point of the curve.
https://user-images.githubusercontent.com/26193340/135149868-f7e1d897-661f-4d4f-9fb4-38775ad79819.mp4
Mode Path :
In a expand mode, to modify when you modifie x axis only in polygon2, you can for exemple make larger a racing/road in some point of your race.
https://user-images.githubusercontent.com/26193340/135149999-d6d5793e-4998-46bf-a76d-460f5b29e541.mp4
Mode Spin :
In mode spin I add a new property " spin_fix_neg ". When interpolation is enable, that will reverse/remove faces if the curve is negative. I don't like to add this additional property, but it's a constraint in mode spin if the user want set a negative position in the interpolate_curve.
https://user-images.githubusercontent.com/26193340/135150035-2080356b-1811-44eb-946f-b52d9c9281ac.mp4
I am waiting the 3.x merge of #52509 before to pull request the version 3.x.
I need a revision for the documentation. English is not my first language.

Of course I would rename the simplifiaction angle to "path_simplify_angle" and now it's being used for more than just that.  Wonder if it should be just "simplify_angle"?
I feel like "interpolation" is maybe not the best way to describe this.  Blender calls it a "profile" when you use a curve to define the bevel shape.  Wonder what the shape is called on things like crown moulding.

Note to me:
Conflict invert_faces to flip_faces. #60838
To fix in same time interpolation to do_interpolate and fix soustraction -1 on spin.

This was auto-closed by GitHub, probably because you pushed a state with no mergeable change (e.g. master branch) to your fork's csg_interpolation branch. AFAIK it can't be reopened when that happens so you'll have to open a new PR.

That will be easier, because I am stock with bugs.
icudt71l.dat still always recognized as modified.
Git include random other file too.
I use Git from ubuntu 16.04 lts. Maybe this version of Git is broke.

I use Git from ubuntu 16.04 lts. Maybe this version of Git is broke.

This is likely what's causing the "file is always recognized as modified" issue.
Ubuntu 16.04 is EOL, and Ubuntu 18.04 will be soon, so I recommend upgrading to Ubuntu 20.04 or later. In your case, you'll probably need to reinstall to upgrade, so you might as well install Ubuntu 22.04 and get 5 years of support this way.

Ubuntu 16.04 is end-of-life, and Ubuntu 18.04 will be soon, so I recommend upgrading to Ubuntu 20.04 or later
Sure, I am thinking about since long time. It's a big job, lot databases to migrate etc. I waited to buy a new computer, but the pression will force me to migrate before that.


assume_role() in certain circumstances can break deterministic instance ids

Moto Version: 4.1.14
Issue:
Stopping all running mocks doesn't seem to completely reset moto. As a result unique identifiers can vary between runs. This is particularly frustrating in the context of unit testing. Where I can run all the tests individually and get one set of values, but once I try to run them sequentially I get another set of values. This is despite setting the seed and as far as I know telling moto to clean everything up.
The following minimal example demonstrates the issue I found when two unit tests were run back to back. If you run the code as is you will see the assert at the bottom fail. However, if you remove the "Unit Test 1" section and run the code it will pass. This doesn't seem to make any intuitive sense since we are "stop()"ing the relevant mocks and creating them anew between each test. (Original code was using python unittest but I got rid of that to hopefully simplify / minimize the code for you all)
#!/usr/bin/python3
import moto
import boto3
import requests

mock_sts = None
mock_ec2 = None

def setUp():
    mock_sts = moto.mock_sts()
    mock_sts.start()

    mock_ec2 = moto.mock_ec2()
    mock_ec2.start()

    requests.post("http://motoapi.amazonaws.com/moto-api/seed?a=42")

    sts_client = boto3.client("sts")

    session_client = sts_client.assume_role(
        RoleArn="arn:aws:iam::111111111111:role/my-role",
        RoleSessionName="role-session-name"
    )

    session = boto3.session.Session(
        aws_access_key_id=session_client["Credentials"]["AccessKeyId"],
        aws_secret_access_key=session_client["Credentials"]["SecretAccessKey"],
        aws_session_token=session_client["Credentials"]["SessionToken"]
    )

    return mock_sts, mock_ec2, session

def tearDown():
    mock_sts.stop()
    mock_ec2.stop()

# Begin: Unit Test 1
mock_sts, mock_ec2, session = setUp()
sts_client = boto3.client("sts")

sts_client.assume_role(
    RoleArn="arn:aws:iam::111111111111:role/my-role",
    RoleSessionName="role-session-name"
)

mock_sts.stop()
mock_ec2.stop()
# End: Unit Test 1

# Begin: Unit Test 2
mock_sts, mock_ec2, session = setUp()
ec2_client = session.client("ec2")
instances = ec2_client.run_instances(
    MaxCount=1,
    MinCount=1
)["Instances"]

instance_ids = [instance["InstanceId"] for instance in instances]

print(f"instance_ids: {instance_ids}")

expected = ["i-9bd53fc993d07650f"]
print(f"expected: {expected}")

assert (instance_ids == expected)

mock_sts.stop()
mock_ec2.stop()
# End: Unit Test 2

What you see when you just run the above code as is:
./my_test2.py
instance_ids: ['i-2c04eb577967c8182']
expected: ['i-9bd53fc993d07650f']
Traceback (most recent call last):
  File "./my_test2.py", line 66, in <module>
    assert (instance_ids == expected)
AssertionError

What you see when you remove "Unit Test 1":
./my_test2.py
instance_ids: ['i-9bd53fc993d07650f']
expected: ['i-9bd53fc993d07650f']

I would of expected that it shouldn't matter if "Unit Test 1" was run or not since I was cleaning up after myself with each run.
Am I just missing some other stop() somewhere? Some sort of reset moto entirely kind of thing?

Hi @mwmix! Thanks for the repro - that made it very easy to see the problem.
I think this behaviour is somehow related to the fact that Moto generates some static data when calling start(). When test_2 is run on it's own, the start() doesn't know about the second account,<PHONE_NUMBER>11.
If test_1 is run first, by the time test_2 executes start() it does know about the second account, so it will create the static data for it. And that additional data would explain the difference in 'unique' identifiers.
I'm not quite sure what a fix for this would look like, to be honest. But as a workaround, you could create the second account explicitly before seeding:
from moto.iam import iam_backends
iam_backends["111111111111"]

requests.post("http://motoapi.amazonaws.com/moto-api/seed?a=42")

That would keep the instance ID's in test2 persistent.

Hi @mwmix and @adammiller1152, this should be fixed in the upcoming v5 release.
We've just released an alpha version to gather some early feedback, moto==5.0.0alpha1. Are you able to verify that this version fixes your issue?
Note that there are breaking changes in this release: all service-specific decorators have been replaced with a single @mock_aws decorator.
See the full release announcement here: https://github.com/getmoto/moto/issues/7198

Moto V5 has now been released with a fix for this bug, so I'll close this.
Release: https://pypi.org/project/moto/5.0.0/


Defect: Video player error

When selecting the video "USING OUR GENUINE PARTS CATALOG" an error displays:

@dkuntze we used a 340MB version of the video and we see the bot increased the size of the file. It works in pre-production but live it does not show:
Franklin Bot
APP  3 hours ago
Done:

https://main--vg-partsasist--hlxsites.hlx.page/media_1538518e52214aeca24cb64ac235a729eec6f0203.mp4
Compressed from 9.9 megabytes original to 26 megabytes for

I can't reproduce this. Is it still an issue?

This issue is still present and it is present on live partsasist.com website

At the moment this seems to be fixed on partsasist.com as well

confirmed as fixed on partsasist.com


Add type param to search

Add "type" to accepted params list for place search, "types" is marked as deprecated (https://developers.google.com/places/web-service/search)
Do not set default value for radius, when specified - it affects nearbysearch results/ranking

Cleaned .idea/ files from request.


Add rust bolivia!

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

r? @steveklabnik

Nice! Thanks :D


GrafanaDashboard is ignored silently if the dashboard content has invalid json

If the json content of a GrafanaDashboard CR has some invalid json, there is no way for the CR creator to know about this, or that Grafana is not accepting it.
There are errors in the Grafana logs (e.g. see below) but the CR creator may not have access to the Grafana logs
t=2019-07-03T14:39:39+0000 lvl=eror msg="failed to load dashboard from " logger=provisioning.dashboard type=file name=default file=/etc/grafana-dashboards/middleware-monitoring_resources-by-namespace.json error="invalid character '(' after object key:value pair"

Suggestion to do basic json validation on the content of the dashboard in the CR before adding it to the grafana-dashboards configmap for Grafana to pickup.
If validation fails, the status field of the CR can be updated with the validation error message.

fixed in https://github.com/integr8ly/grafana-operator/releases/tag/v1.2.0