Cassandra failed to start up

On the new minikube deployment, while trying to deploy cassandra using ./k8s-install-tb.sh, I get to the point where ThingsBoard installs the cql file in Cassandra:
Installing Cassandra DataBase schema part: schema-ts.cql

but it hangs, and after a long while, I get these logs in the cassandra pod:
cassandra 20:47:19.18
cassandra 20:47:19.18 Welcome to the Bitnami cassandra container
cassandra 20:47:19.18 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-cassandra
cassandra 20:47:19.18 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-cassandra/issues
cassandra 20:47:19.18
cassandra 20:47:19.19 INFO  ==> ** Starting Cassandra setup **
cassandra 20:47:19.21 INFO  ==> Validating settings in CASSANDRA_* env vars..
cassandra 20:47:19.21 WARN  ==> You set the environment variable CASSANDRA_PASSWORD=cassandra. This is the default value when bootstrapping Cassandra and should not be used in production environments.
cassandra 20:47:19.29 INFO  ==> Initializing Cassandra database...
cassandra 20:47:19.56 INFO  ==> Deploying Cassandra from scratch
cassandra 20:47:19.56 INFO  ==> Starting Cassandra
cassandra 20:47:19.57 INFO  ==> Checking that it started up correctly
cassandra 20:47:39.71 INFO  ==> Found CQL startup log line
grep: Unmatched ( or \(
grep: Unmatched ( or \(
grep: Unmatched ( or \(
grep: Unmatched ( or \(
grep: Unmatched ( or \(
cassandra 20:48:16.60 ERROR ==> Cassandra failed to start up

And I get these logs in tb-db-setup.
2021-11-08 20:43:28,951 [background-preinit] INFO  o.h.validator.internal.util.Version - HV000001: Hibernate Validator 6.0.13.Final
2021-11-08 20:43:30,866 [background-preinit] WARN  o.s.h.c.j.Jackson2ObjectMapperBuilder - For Jackson Kotlin classes support please add "com.fasterxml.jackson.module:jackson-module-kotlin" to the classpath
2021-11-08 20:43:33,782 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
2021-11-08 20:43:33,783 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2021-11-08 20:43:34,926 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 1093ms. Found 39 JPA repository interfaces.
2021-11-08 20:43:34,938 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
2021-11-08 20:43:34,938 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2021-11-08 20:43:35,016 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 78ms. Found 1 JPA repository interfaces.
2021-11-08 20:43:35,021 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
2021-11-08 20:43:35,021 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2021-11-08 20:43:35,053 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 32ms. Found 1 JPA repository interfaces.
2021-11-08 20:43:36,211 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Multiple Spring Data modules found, entering strict repository configuration mode!
2021-11-08 20:43:36,215 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2021-11-08 20:43:36,353 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.rule.RuleChainRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,356 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.rule.RuleNodeRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,356 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sqlts.latest.TsKvLatestRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,360 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.relation.RelationRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,361 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.rule.RuleNodeStateRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,363 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.deprecated.OAuth2ClientRegistrationInfoRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,363 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.resource.TbResourceRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,364 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.OAuth2ClientRegistrationTemplateRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,364 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.tenant.TenantProfileRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,364 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.deprecated.OAuth2ClientRegistrationRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,365 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.audit.AuditLogRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,365 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.dashboard.DashboardRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,365 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.usagerecord.ApiUsageStateRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,366 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.widget.WidgetTypeRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,366 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sqlts.dictionary.TsKvDictionaryRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,366 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.OAuth2ParamsRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,368 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.device.DeviceRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,368 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.event.EventRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,368 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.user.UserCredentialsRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,371 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.ota.OtaPackageRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,375 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sqlts.ts.TsKvRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,376 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.settings.AdminSettingsRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,376 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.widget.WidgetsBundleRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,389 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.OAuth2RegistrationRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,395 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.device.DeviceCredentialsRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,396 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.attributes.AttributeKvRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,396 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.OAuth2DomainRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,396 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.resource.TbResourceInfoRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,396 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.rpc.RpcRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,398 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.dashboard.DashboardInfoRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,415 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.alarm.AlarmRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,416 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.tenant.TenantRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,416 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.asset.AssetRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,417 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.device.DeviceProfileRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,417 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.oauth2.OAuth2MobileRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,417 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.edge.EdgeRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,418 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.user.UserRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,418 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.component.ComponentDescriptorRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,418 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.customer.CustomerRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,419 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.entityview.EntityViewRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,419 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.edge.EdgeEventRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,419 [main] INFO  o.s.d.r.c.RepositoryConfigurationExtensionSupport - Spring Data Redis - Could not safely identify store assignment for repository candidate interface org.thingsboard.server.dao.sql.ota.OtaPackageInfoRepository. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
2021-11-08 20:43:36,419 [main] INFO  o.s.d.r.c.RepositoryConfigurationDelegate - Finished Spring Data repository scanning in 177ms. Found 0 Redis repository interfaces.
2021-11-08 20:43:37,211 [main] INFO  o.s.i.c.DefaultConfiguringBeanFactoryPostProcessor - No bean named 'errorChannel' has been explicitly defined. Therefore, a default PublishSubscribeChannel will be created.
2021-11-08 20:43:37,244 [main] INFO  o.s.i.c.DefaultConfiguringBeanFactoryPostProcessor - No bean named 'taskScheduler' has been explicitly defined. Therefore, a default ThreadPoolTaskScheduler will be created.
2021-11-08 20:43:37,293 [main] INFO  o.s.i.c.DefaultConfiguringBeanFactoryPostProcessor - No bean named 'integrationHeaderChannelRegistry' has been explicitly defined. Therefore, a default DefaultHeaderChannelRegistry will be created.
2021-11-08 20:43:38,313 [main] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'org.springframework.integration.config.IntegrationManagementConfiguration' of type [org.springframework.integration.config.IntegrationManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-11-08 20:43:38,352 [main] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'integrationChannelResolver' of type [org.springframework.integration.support.channel.BeanFactoryChannelResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-11-08 20:43:38,356 [main] INFO  o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'integrationDisposableAutoCreatedBeans' of type [org.springframework.integration.config.annotation.Disposables] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-11-08 20:43:39,279 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat initialized with port(s): 8080 (http)
2021-11-08 20:43:39,320 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-<IP_ADDRESS>-8080"]
2021-11-08 20:43:39,320 [main] INFO  o.a.catalina.core.StandardService - Starting service [Tomcat]
2021-11-08 20:43:39,321 [main] INFO  o.a.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.46]
2021-11-08 20:43:39,504 [main] INFO  o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
2021-11-08 20:43:39,504 [main] INFO  o.s.b.w.s.c.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 10414 ms
2021-11-08 20:43:40,390 [main] INFO  o.h.jpa.internal.util.LogHelper - HHH000204: Processing PersistenceUnitInfo [name: default]
2021-11-08 20:43:40,583 [main] INFO  org.hibernate.Version - HHH000412: Hibernate ORM core version 5.4.32.Final
2021-11-08 20:43:41,101 [main] INFO  o.h.annotations.common.Version - HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
2021-11-08 20:43:41,346 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2021-11-08 20:43:41,517 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2021-11-08 20:43:41,557 [main] INFO  org.hibernate.dialect.Dialect - HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
2021-11-08 20:43:44,445 [main] INFO  o.h.e.t.j.p.i.JtaPlatformInitiator - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2021-11-08 20:43:44,485 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'default'
2021-11-08 20:43:48,076 [nosql-dispatcher-1-thread-1] INFO  o.t.s.d.u.AbstractBufferedRateExecutor - Buffered rate executor thread started
2021-11-08 20:43:48,092 [nosql-dispatcher-1-thread-2] INFO  o.t.s.d.u.AbstractBufferedRateExecutor - Buffered rate executor thread started
2021-11-08 20:43:49,094 [main] INFO  o.t.s.d.a.CachedAttributesService - Going to use directExecutor for the local cache type caffeine
2021-11-08 20:43:50,512 [main] INFO  o.s.b.a.w.s.WelcomePageHandlerMapping - Adding welcome page: class path resource [public/index.html]
2021-11-08 20:43:52,258 [main] INFO  o.s.s.web.DefaultSecurityFilterChain - Creating filter chain: any request, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@22cce199, org.springframework.security.web.context.SecurityContextPersistenceFilter@8de8b07, org.springframework.security.web.header.HeaderWriterFilter@59509393, org.springframework.security.web.csrf.CsrfFilter@3dd27116, org.springframework.security.web.authentication.logout.LogoutFilter@6b64921f, org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestRedirectFilter@1028a747, org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestRedirectFilter@613ba54e, org.springframework.security.oauth2.client.web.OAuth2LoginAuthenticationFilter@24890021, org.springframework.security.web.authentication.ui.DefaultLoginPageGeneratingFilter@1fe37d27, org.springframework.security.web.authentication.ui.DefaultLogoutPageGeneratingFilter@14b4b25e, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@3fc7abf6, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@3a720ae3, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@4babe06f, org.springframework.security.oauth2.client.web.OAuth2AuthorizationCodeGrantFilter@7205a8b7, org.springframework.security.web.session.SessionManagementFilter@7ec75228, org.springframework.security.web.access.ExceptionTranslationFilter@345af277, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@6d387e9b]
2021-11-08 20:43:52,678 [main] INFO  o.s.b.a.e.web.EndpointLinksResolver - Exposing 1 endpoint(s) beneath base path '/actuator'
2021-11-08 20:43:52,837 [main] INFO  o.s.s.c.ThreadPoolTaskScheduler - Initializing ExecutorService 'taskScheduler'
2021-11-08 20:43:52,982 [main] INFO  o.s.i.endpoint.EventDrivenConsumer - Adding {logging-channel-adapter:_org.springframework.integration.errorLogger} as a subscriber to the 'errorChannel' channel
2021-11-08 20:43:52,983 [main] INFO  o.s.i.c.PublishSubscribeChannel - Channel 'application.errorChannel' has 1 subscriber(s).
2021-11-08 20:43:52,988 [main] INFO  o.s.i.endpoint.EventDrivenConsumer - started bean '_org.springframework.integration.errorLogger'
2021-11-08 20:43:52,988 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-<IP_ADDRESS>-8080"]
2021-11-08 20:43:53,063 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat started on port(s): 8080 (http) with context path ''
2021-11-08 20:43:53,192 [main] INFO  o.t.s.i.ThingsboardInstallService - Starting ThingsBoard Installation...
2021-11-08 20:43:53,193 [main] INFO  o.t.s.i.ThingsboardInstallService - Installing DataBase schema for entities...
2021-11-08 20:43:53,194 [main] INFO  o.t.s.s.i.SqlAbstractDatabaseSchemaService - Installing SQL DataBase schema part: schema-entities.sql
2021-11-08 20:43:53,460 [main] INFO  o.t.s.s.i.SqlAbstractDatabaseSchemaService - Installing SQL DataBase schema indexes part: schema-entities-idx.sql
2021-11-08 20:43:53,499 [main] INFO  o.t.s.s.i.PsqlEntityDatabaseSchemaService - Installing SQL DataBase schema PostgreSQL specific indexes part: schema-entities-idx-psql-addon.sql
2021-11-08 20:43:53,528 [main] INFO  o.t.s.i.ThingsboardInstallService - Installing DataBase schema for timeseries...
2021-11-08 20:43:53,529 [main] INFO  o.t.s.s.i.CassandraAbstractDatabaseSchemaService - Installing Cassandra DataBase schema part: schema-ts.cql
2021-11-08 20:43:53,552 [main] WARN  c.d.o.d.internal.core.ContactPoints - Ignoring invalid contact point cassandra:9042 (unknown host cassandra)
2021-11-08 20:43:53,789 [main] INFO  c.d.o.d.i.c.DefaultMavenCoordinates - DataStax Java driver for Apache Cassandra(R) (com.datastax.oss:java-driver-core) version 4.10.0
2021-11-08 20:43:54,151 [Thingsboard Cluster-admin-0] INFO  c.d.o.d.internal.core.time.Clock - Could not access native clock (see debug logs for details), falling back to Java system clock
2021-11-08 20:43:54,153 [Thingsboard Cluster-admin-0] INFO  c.d.o.d.i.c.metadata.MetadataManager - [Thingsboard Cluster] No contact points provided, defaulting to /<IP_ADDRESS>:9042
2021-11-08 20:43:54,436 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:43:57,471 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:44:02,772 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:44:15,279 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:44:37,868 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:45:29,321 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:47:15,909 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))
2021-11-08 20:50:29,850 [Thingsboard Cluster-admin-1] WARN  c.d.o.d.i.c.c.ControlConnection - [Thingsboard Cluster] Error connecting to Node(endPoint=/<IP_ADDRESS>:9042, hostId=null, hashCode=28b26998), trying next node (ConnectionInitException: [Thingsboard Cluster|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (io.netty.channel.StacklessClosedChannelException))

Version of TB: 3.3.1
Commit: 80d6e8d9b9330baa57bc1570b444e05a6d99ab9d

It may or may not be calico.


go-libjpeg error jpeglib.h not found

When I run the following I get this error:
jerald$ go get github.com/pixiv/go-libjpeg/jpeg
go/src/github.com/pixiv/go-libjpeg/jpeg/compress.go:6:10: fatal error: 'jpeglib.h' file not found
#include "jpeglib.h"
Any advice?
Edit: Never mind. It was an oversight on my part. I just ran brew install jpeg and the issue was fixed.

Yes, go-libjpeg needs libjpeg.


fix(all): Clean up macOS Privacy Manifests

Description
Clean up macOS manifests
Related Issues

Fix #3263

Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I titled the PR using Conventional Commits.
[X] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[ ] All existing and new tests are passing.
[X] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[X] No, this is not a breaking change.

Thanks for the contribution @kjxbyz !


Larger File is not able to be encrypted

Got a File with 21k words. tryin to encrypt file but file does not get encrypted, is there a limit for purpose?!

Tracking down the issue to:
EncryptedFileContentView.ts:230 RangeError: Maximum call stack size exceeded
    at CryptoHelperV2.eval (CryptoHelper.ts:59:35)
    at Generator.next (<anonymous>)
    at fulfilled (tslib.es6.js:73:58)

which is this line
//convert array to base64
const base64Text = btoa( String.fromCharCode(...finalBytes) );

will work on a fix

I suspect the error is to do with the String.fromCharCode call.
To workaround the problem I'll need to batch the calls to String.fromCharCode and concatenate the results.


istioctl describe provide info on a pod without sidecar ready for mesh

Describe the feature request
A good user flow is while user moves their existing deployment to Istio:

istioctl describe pod
(check if the pod is ready to be added and take action if needed)

istioctl add-to-mesh service

Describe alternatives you've considered
Currently it doesn't output much useful info other than the pod doesn't have a sidecar.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x ] User Experience
[ ] Developer Infrastructure
@esnible @irisdingbj i noticed inconsistency between add-to-mesh cmd that takes a service name and describe takes a pod name.  Is this something we could generate consistency among the two?

@esnible Thank you - I think handling at deployment or/and service level is easier than pod.
for describe service, I 'm not sure if I'm interested in how many pods implement the service.  I would only want to know if there is issue for adding to istio first.
Once user feels confident and have added service to the mesh, then user may start debug traffic issue, that is where subset and mTLS strict/permissive etc can be useful.

@linsun I'm trying to understand the use case.
If I do istioctl x describe pod <pod> I get several messages such as WARNING: <pod> is part of mesh; no Istio sidecar.
These messages are low-level because the tool tried to get the Envoy config and failed.
What kind of feedback does the user expect?  There are several cases to consider:

The pod shouldn't be added to the mesh because it doesn't belong in the mesh.  For example istio-citadel.istio-system pods, or kube-dns.kube-system pods.
The pod has annotations because the user didn't want it in the mesh.  In that case, telling the user to add-to-mesh doesn't help
The pod is in a namespace that has been tagged for inject, but it didn't get restarted and will get the sidecar on restart.
The pod is in a namespace without auto-inject, and we want to inject it anyway, to gradually join the mesh.

  Is there a way to simplify this?


Update README with conda/mamba install

This pull-request updates the README.rst with simple instructions to the user community on how to install pytest-pyvista using conda or mamba from the newly hatched package on conda-forge.

Add it to this PR, please.  I will review it. Thanks!

Codecov Report

Merging #84 (b6cfd08) into main (42f771b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   92.13%   92.13%
=======================================
  Files           2        2
  Lines          89       89
=======================================
  Hits           82       82
  Misses          7        7

@tkoyama010 and @MatthewFlamm
The badges now look like this ...


Allow for users to categorise secrets

E.g., "Personal", "Work", "Company X", "Firm Y", or even if they want to keep browsers separated.
Tasks:

[x] Add category field to Metadata
[x] Add --category flag to list subcommand (only show)
[ ] Add --category flag to export subcommand (only export)
[ ] Add --category flag to import subcommand (only import)
[ ] Add show categories subcommand (with show cats alias)

Note for more general, flatter, one-to-many "categorisation", flags will be offered:

#67

Gonna save the filtering for #71 and #72 ...

Done.


Atomically creating in-order keys without first creating a directory

According to the documentation, "Using POST on a directory, you can create keys with key names that are created in-order". It would be very helpful if it was possible to both create the directory (if it doesn't exist) and create the in-order key in one POST request.

My bad: I didn't notice that the ordinary setting of keys uses PUT and not POST, so there is no ambiguity and it already works!


Use Apache Spark 3.0.1

Hi, @maropu . Could you review and merge this? :)

oh, I forgot to update it! Thanks, @dongjoon-hyun ~

Thank YOU! :)


Manage users

-Add API endpoint to manage user by id PATCH /users/:id/manage
-Expand updateUserById service to handle isAdmin, isBanned, and isActive
-Create separate controller for user management (manageUserById)
-Add corresponding tests
Will need to address sub-tickets in the future:
- As a banned user, I can't log in.
- As an inactive user, logging in will reactivate my account.

-Add API endpoint to manage user by id PATCH /users/:id/manage
-Expand updateUserById service to handle isAdmin, isBanned, and isActive
-A banned user is automatically and silently deactivated
-Future backlog ticket is to create a validation step that allows request to fail fast when user tries
to ban and reactivate at the same time.
-Create separate controller for user management (manageUserById)
-Add corresponding tests


Fixed 'async' depracated tag on Python 3.7.2.

Fixes bug where the word async is reserved specifically for Python's asynchronous functionalities.

Renamed async within the project to asynchro.

Going to make modifications to the Readme.


Document how to get code actions working like in your blog video example

TypeScript Version:  2.2.1
The typescript blog shows a VS code video of "goodness to your editor. This release introduces some more useful quick fixes (also called code actions) which can guide you in fixing up pesky errors".
It is not clear how to enable the shown behavior and listed quick fixes in VS Code ? Which specific plugin(s) should be installed ?

You can see all the new quickfixes if you are using VSCode insiders (https://code.visualstudio.com/insiders); or by setting your VSCode to use TS 2.2. (see Using Newer TypeScript Versions documentation for more details on updating your VSCode to use a different version of TypeScript).


[DOCS] <keep everything simple, let's stick to npm for now>

Description
let's keep the instructions for running the frontend simple, so keep npm instructions only.
Screenshots
No response

as we discussed let's keep npm related instructions only in the documentation.

closing this issue as it fixed now 🍻


Not a reusable app -> Repository is dead

If I understand correctly, this app has following unjustifiable assumptions:

a FSMField is called status (e.g. in my case I call it state)
one cannot use different identifier (pk must be used)
transition must have by argument

Some of it seems to be PRed already.

Agree. It seems this repository in unmaintained. I've therefore created a new package and addressed the issues above and some other issues I've encountered as well.
https://github.com/27medkamal/djangorestframework-fsm

I encourage the author @jacobh to archive this repository or archive it and redirect to the above fork.

@27medkamal Issues are not available at your repo though. Don't you wanna create a fresh one instead of fork?

@hnykda thanks for letting me know. I've updated the repository


Can not achieve model-50.eval.0.txt document

Hi,
I type the command:
$ python CapsE.py --embedding_dim 100 --num_epochs 31 --num_filters 50 --learning_rate 0.0001 --name FB15k-237 --useConstantInit --savedEpochs 30 --model_name fb15k237
But I did not achieve .txt docoments, like model-50.eval.0.txt, model-50.eval.1.txt,...,model-50.eval.7
.txt.(These txt documents are needed when executing eval.py )
Is there any problem with CapsE.py?
BTW, I have the same problem with ConvKB.

You can see the "Evaluation metrics" section in README.

Hi,
I type the command:
$ python CapsE.py --embedding_dim 100 --num_epochs 31 --num_filters 50 --learning_rate 0.0001 --name FB15k-237 --useConstantInit --savedEpochs 30 --model_name fb15k237
But I did not achieve .txt docoments, like model-50.eval.0.txt, model-50.eval.1.txt,...,model-50.eval.7
.txt.(These txt documents are needed when executing eval.py )
Is there any problem with CapsE.py?
BTW, I have the same problem with ConvKB.

i have same question ,could you help me

my mail<EMAIL_ADDRESS>

You can see the "Evaluation metrics" section in README.

the CapsE.py do not save the .txt docoments, like model-50.eval.0.txt, model-50.eval.1.txt,...,model-50.eval.7.txt.

You can see examples in command.sh

You can see examples in command.sh

Problem solved! Thank you


Unmarshaling malicious data with variable-length array without specified size can lead to extensive memory usage

There is a bug in go-xdr (I wasn't able to create an issue there) when trying to unmarshal variable-length array without specified size. Take a look at this union:
union StellarMessage switch (MessageType type)
{
  // ...

case GET_PEERS:
    void;
case PEERS:
    PeerAddress peers<>;

  // ...
}

We can create a special StellarMessage that looks like:
Base64:
AAAABX///9AAAAAAAAECAwAAAFAAAABk

Hex:
00000000  00 00 00 05 7f ff ff d0  00 00 00 00 00 01 02 03  |................|
                      ^^^^^^^^^^^
00000010  00 00 00 50 00 00 00 64                           |...P...d|
00000018

Bytes marked with ^ represent the size of an array, which should be 1 since it contains only one address, but it has been changed to some very large number. As a result go-xdr is trying to allocate a large chunk of memory for the array that in reality is really small. Here's a little proof-of-concept:
package main

import (
  "github.com/stellar/go/xdr"
)

func main() {
  var message xdr.StellarMessage
  xdr.SafeUnmarshalBase64("AAAABX///9AAAAAAAAECAwAAAFAAAABk", &message)
}

A fix should check if the number of remaining bytes is less than or equal the specified size before allocating memory (you can check how it's works in xdrpp).

Let's move this to go-xdr.  Issues being disabled on that repo was an accident.


arm64 temporal-operator

Please add the architecture arm64 image ghcr.io/alexandrevilain/temporal-operator. This will greatly increase versatility. Thank you

Good idea!
New kubebuilder projects are coming with the "docker-buildx" make target which does the job.
See: https://github.com/kubernetes-sigs/kubebuilder/blob/master/testdata/project-v4/Makefile#L96
We have to take this for this feature and update the github workflow accordingly.

Can I count on arm64 additions because my entire project is on arm ?

Hi @abratanich ! Image for v0.15.0 is available for linux/arm64 :)


Dockerize the project

use Docker and Spring Webhook for microservices architecture

Nothing is preventing you from creating a Docker version of this project. The goal is to provide a simple set of code to show how to use the platform to send and receive responses. Additionally, this project is designed around Node.js rather than Spring/Java.


('A'..'Z') === nil must return nil if it can’t match the value instead of give a compilation error.

Bug Report
For more details, check discuss on https://forum.crystal-lang.org/t/in-case-statement-case-nil-and-range/2623/2
Following code not work on Crystal 1.7.2
ch : Char? = nil

case ch
when 'A'..'Z'
  puts "ch is capital"
when Nil
  puts "ch is nil"
end

 Click me to see back trace
In 1.cr:13:6

 13 | when 'A'..'Z'
           ^-
Error: instantiating 'Range(Char, Char)#===(Nil)'

In /home/zw963/Crystal/share/crystal/src/range.cr:327:5

 327 | includes?(value)
       ^--------
Error: instantiating 'includes?(Nil)'

In /home/zw963/Crystal/share/crystal/src/range.cr:298:32

 298 | (begin_value.nil? || value >= begin_value) &&
                                  ^
Error: undefined method '>=' for Nil

Nil trace:

  /home/zw963/Crystal/share/crystal/src/range.cr:298

        (begin_value.nil? || value >= begin_value) &&

  /home/zw963/Crystal/share/crystal/src/range.cr:293

      def includes?(value) : Bool

I guess this error raised because compiler translate above code into following:
ch : Char? = nil

if ('A'..'Z') === ch
  puts "ch is capital"
elsif Nil === ch
  puts "ch is nil"
end

===  in ('A'..'Z') === ch must return nil if it can’t match the value, never give a compilation error.

You're comparing against Nil the class, not nil the type.

Object#===(other) is defined for every argument type (it just returns false by default). It's not expected to be type-save. And so must Range#===(other).
Fixing the generic implementation is a bit tricky, though. It needs to check whether the comparison between other and begin/end are allowed.


break iteration on pages

Hi, thanks for the nice API!
I ran into a simple paging issue.
The following code
p = a.search(SearchIndex='Books', Author='john grisham', Power='pubdate:after 2014 and pubdate:before 2016')
for pp in p:
  print pp.release_date, '========', pp.title

seems to fail to understand paging, ultimately I get a 503.  Here's more info though.  I added some code in bottlenose/api.py, more specifically in _call_api() to print the first api_url param, and here's what I get (I stripped the noise in the URLs after the first one to highlight the problem):

http://ecs.amazonaws.com/onca/xml?AWSAccessKeyId=...&AssociateTag=...&Author=john grisham&ItemPage=1&Operation=ItemSearch&Power=pubdate%3Aafter 2014 and pubdate%3Abefore 2016&ResponseGroup=Large&SearchIndex=Books&Service=AWSECommerceService&Timestamp=...&Version=2011-08-01&region=US&Signature=...
2015-05-12 ======== Theodore Boone: The Fugitive
2015-05-19 ======== Theodore Boone Box Set
2015-02-21 ======== The man from the fog
http://ecs.amazonaws.com/onca/xml?...ItemPage=2&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=3&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=4&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=5&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=6&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=7&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=8&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=9&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=10&...
http://ecs.amazonaws.com/onca/xml?...ItemPage=11&...
Traceback (most recent call last):
File "amzn.py", line 4, in
for pp in p:
File "/usr/lib/python2.6/site-packages/amazon/api.py", line 234, in iter
for page in self.iterate_pages():
File "/usr/lib/python2.6/site-packages/amazon/api.py", line 250, in iterate_pages
yield self._query(ItemPage=self.current_page, **self.kwargs)
File "/usr/lib/python2.6/site-packages/amazon/api.py", line 263, in _query
response = self.api.ItemSearch(ResponseGroup=ResponseGroup, **kwargs)
File "/usr/lib/python2.6/site-packages/bottlenose/api.py", line 243, in call
{'api_url': api_url, 'cache_url': cache_url})
File "/usr/lib/python2.6/site-packages/bottlenose/api.py", line 204, in _call_api
return urllib2.urlopen(api_request, timeout=self.Timeout)
File "/usr/lib64/python2.6/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib64/python2.6/urllib2.py", line 397, in open
response = meth(req, response)
File "/usr/lib64/python2.6/urllib2.py", line 510, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib64/python2.6/urllib2.py", line 435, in error
return self._call_chain(*args)
File "/usr/lib64/python2.6/urllib2.py", line 369, in _call_chain
result = func(*args)
File "/usr/lib64/python2.6/urllib2.py", line 518, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 503: Service Unavailable
So somehow amazon/api.py keeps iterating forever (it even goes beyond the hard page limit 10) even though the first ItemPage returned only 3 results (as I can tell by copy/pasting the first URL in my browser) and that should be the end.
I see there's search_n() but ultimately all I want is to return all the results of my search query, not the top N.

Took a quick glance at the code, looks like https://github.com/yoavaviram/python-amazon-simple-product-api/pull/54 fixes exactly this issue.
@yoavaviram -- I see it's been merged into master, any chance this can be released?  Thanks!


Improve mobile version

This https://github.com/KennethLuczko/myroutebuddy/pull/50 PR improved the mobile experience, but it is still not very responsive and has issues.

https://github.com/KennethLuczko/myroutebuddy/pull/56 really nice job


Adding objects to AnnData from R with reticulate

Hi,
I'm using scanpy from R with reticulate and I'm creating several R data.frames  (e.g. my_df below) that I would like to add to the AnnData object (e.g., under obsm) and save that modified AnnData as an h5ad file.
If for example, I read an existing AnnData h5ad file (in.h5ad.fn below) in R with reticulate using:
library(reticulate)
sc <- import("scanpy")
adata <- sc$read(in.h5ad.fn)

Then created:
my_df <- data.frame(cell = rownames(adata$obs), value = rnorm(nrow(adata$obs))
I thought that:
adata$obsm['my_df'] <- my_df
would work but I get this error:
Error in adata$obsm["my_df"] = my_df :
  object of type 'environment' is not subsettable

What's the proper way to add my_df to adata?
And what would be the command to save that modified adata object to an h5ad file?

Reticulate doesn’t wrap __getitem__/__setitem__ with R’s [ and [<- methods directly. For the getitem case, it instead uses some complex code that tries to do something smart (mostly a bad idea):
https://github.com/rstudio/reticulate/blob/6e44eff5fe8f7f1cad9d9c96f23fe9d79e9f8189/R/python.R#L277-L355
What’s missing is the setitem case for [], as only the $<-.python.builtin.object and [[<-.python.builtin.object are defined. You can just use (py_get_item)[https://rstudio.github.io/reticulate/reference/py_get_item.html]/py_set_item directly, or define the missing method:
`[<-.python.builtin.object` <- py_set_item

I filed this bug in the correct repo accordingly: rstudio/reticulate#803

Thank you very much for the quick response.
I need to make a small correction to my post above. The proper slot for my_df in adata should adata.uns rather than adata.obsm.
Following your answer, in R I did:
adata$uns <- reticulate::py_set_item(adata$uns, 'my_df' ,my_df)
But I get this error:
Error in py_set_item_impl(x, name, value) :
  Unable to access object (object is from previous session and is now invalid)

When I try to do the same in python (first reading in the my_df data.frame from an RDS file I saved it to in R):
import pandas as pd
import scanpy as sc
import pyreadr
my_df = pyreadr.read_r(my_df_fn)
adata.uns['my_df'] = my_df

It works fine - adata already had neighbors and pca under uns and my_df gets added.
Any idea what am I doing wrong?
Thanks

You don’t need to do an assignment. Python objects are by-reference, so you just do py_set_item(adata$uns, ...) and adata$uns will be updated

Sorry for being persistent but I'm still getting the same error.
The adata object I'm working with is the one from scanpy's pbmc3k tutorial.
Either saving the adata object as an h5ad (adata.h5ad) before running PCA (hence when adata only has the var and obs slots) or after (when it has the uns slot), then reading it in R and trying to add my_df:
library(reticulate)
import pandas as pd
import scanpy as sc
adata <- sc$read('adata.h5ad')
set.seed(1)
my_df <- data.frame(x = rnorm(100), y = rnorm(100))
reticulate::py_set_item(adata$uns, 'my_df', my_df)

I get:
Error in py_set_item_impl(x, name, value) :
  Unable to access object (object is from previous session and is now invalid)

Hmm, I think the reticulate people can help you better with that than I can.

Thanks.
One last small question. which you may also find to be relevant to reticulate:
If I add my_df to adata$uns in python:
adata.uns['my_df'] = my_df
I see it properly added as a data.frame along with the column names:
>>> type(adata.uns['my_df'])
<class 'pandas.core.frame.DataFrame'>

and:
>>> adata.uns['my_df']
           x         y
0   0.299158 -0.514339
1  -1.994057 -0.905130
2   1.536284 -1.090005

Then, if I save it as an h5ad using adata.write('adata_my_df.h5ad'), and then read it in R using reticulate, I see that adata$uns$my_df is now a matrix and the column names are not there:
pd <- import("pandas")
sc <- import("scanpy")
adata <- sc$read("adata_my_df.h5ad")
> class(adata$uns$my_df)
[1] "matrix"
> head(adata$uns$my_df)
           [,1]       [,2]
[1,]  0.2991581 -0.5143395
[2,] -1.9940568 -0.9051297
[3,]  1.5362842 -1.0900054

Any idea?

There’s a few parts here:

adding the data frame to uns (it doesn’t get converted here)
writing the AnnData object to disk
reading it from disk
converting the Python data structure to R by reticulate

You can try reading the file from Python. If it’s already been converted then, the conversion happens during reading or writing, but not in reticulate. If it happens during reading or writing, you can use HDF5 tools to inspect the file and check if the thing is stored as a data frame or a matrix.

Sorry for not being specific.
This is happening independently of reticulate, completely in python.
For the sake of clarity here's the complete process.

Read adata that does not include my_df:

>>> import pandas as pd
>>> import scanpy as sc
>>> import pyreadr
>>> adata = sc.read('adata.h5ad')
>>> adata
AnnData object with n_obs × n_vars = 2638 × 13714
    obs: 'n_genes', 'n_genes_by_counts', 'log1p_n_genes_by_counts', 'total_counts', 'log1p_total_counts', 'total_counts_mt', 'log1p_total_counts_mt', 'pct_counts_mt'
    var: 'gene_ids', 'n_cells', 'mt', 'n_cells_by_counts', 'mean_counts', 'log1p_mean_counts', 'pct_dropout_by_counts', 'total_counts', 'log1p_total_counts', 'highly_variable', 'means', 'dispersions', 'dispersions_norm'
    uns: 'pca'
    obsm: 'X_pca'
    varm: 'PCs'

Read my_df from the RDS file I saved it to in R:

>>> my_df = pyreadr.read_r('my_df.RDS')
>>> my_df = my_df[None]
>>> type(my_df)
<class 'pandas.core.frame.DataFrame'>
>>> my_df
           x         y
0   0.299158 -0.514339
1  -1.994057 -0.905130
2   1.536284 -1.090005
3  -0.825919 -0.165101

Add my_df to adata.uns and make sure it's added as a pandas dataframe with the column names:

>>> adata.uns['my_df'] = my_df
>>> adata
AnnData object with n_obs × n_vars = 2638 × 13714
    obs: 'n_genes', 'n_genes_by_counts', 'log1p_n_genes_by_counts', 'total_counts', 'log1p_total_counts', 'total_counts_mt', 'log1p_total_counts_mt', 'pct_counts_mt'
    var: 'gene_ids', 'n_cells', 'mt', 'n_cells_by_counts', 'mean_counts', 'log1p_mean_counts', 'pct_dropout_by_counts', 'total_counts', 'log1p_total_counts', 'highly_variable', 'means', 'dispersions', 'dispersions_norm'
    uns: 'pca', 'my_df'
    obsm: 'X_pca'
    varm: 'PCs'
>>> type(adata.uns['my_df'])
<class 'pandas.core.frame.DataFrame'>
>>> adata.uns['my_df']
           x         y
0   0.299158 -0.514339
1  -1.994057 -0.905130
2   1.536284 -1.090005

Save this modified adata to an h5ad file:
adata.write('adata_my_df.h5ad')

Quit this python session, start a new one, and read adata_my_df.h5ad:

>>> import pandas as pd
>>> import scanpy as sc
>>> adata = sc.read('adata_my_df.h5ad')

First make sure that my_df is indeed in in adata's uns slot:

>>> adata
AnnData object with n_obs × n_vars = 2638 × 13714
    obs: 'n_genes', 'n_genes_by_counts', 'log1p_n_genes_by_counts', 'total_counts', 'log1p_total_counts', 'total_counts_mt', 'log1p_total_counts_mt', 'pct_counts_mt'
    var: 'gene_ids', 'n_cells', 'mt', 'n_cells_by_counts', 'mean_counts', 'log1p_mean_counts', 'pct_dropout_by_counts', 'total_counts', 'log1p_total_counts', 'highly_variable', 'means', 'dispersions', 'dispersions_norm'
    uns: 'my_df', 'pca'
    obsm: 'X_pca'
    varm: 'PCs'

Show that my_df is actually numpy.ndarray (which I guess is why reticulate reads reads it as a matrix in R) and the column names are gone:

>>> adata.uns['my_df']
array([[ 2.99158071e-01, -5.14339494e-01],
       [-1.99405676e+00, -9.05129703e-01],
       [ 1.53628424e+00, -1.09000536e+00],
       [-8.25918690e-01, -1.65100861e-01],
       [-4.19977424e-01,  1.22236926e+00],

as said: it’s unclear if the file is stored on disk as data frame or as array. between 4 and 5 you should figure out what’s the case here, then we can see if the problem is in the write function or the read function

This is what I see when inspecting the adata_my_df.h5ad file:
>>> import h5py
>>> import scipy
>>> import scanpy
>>> import pandas
>>> f = h5py.File("/home/nrubinstein/Downloads/adata_my_df.h5ad", "r")
>>> list(f.keys())
['X', 'obs', 'obsm', 'uns', 'var', 'varm']
>>> f["uns"].visititems(print)
my_df <HDF5 dataset "my_df": shape (100, 2), type "<f8">
pca <HDF5 group "/uns/pca" (2 members)>
pca/variance <HDF5 dataset "variance": shape (50,), type "<f4">
pca/variance_ratio <HDF5 dataset "variance_ratio": shape (50,), type "<f4">

I couldn't really tell from the HDF5 inspection documentation you referred me to whether this output means that my_df is a dataframe or a dense array.
This probably doesn't matter, but indexing my_df before adding it to the uns slot in adata doesn't change much other than the dimensions and type of my_df that f["uns"].visititems(print) reports.

it’s stored as a dataset, so it’s a dense array. data frames are stored as groups (think folders)
therefore the problem is in the write function.


fix for live merge #1009

Fixes preventing live merge for PR 1009 -

Prelude.md: The file had two uid entries in the metadata. I removed the one that was not accessed by any other files (verified with Grep)
Relnotes.md: Fixed the double-indentation of a numbered list and code sample
Glossary-qml.md: Under machine-learning/, glossary-qml.md and intro.md had the same title in the metadata (probably a cut/paste oversight). I modified the glossary title.
redirection.json: numerous typos and misnamed URL paths. It's possible these suggestions don't appear when someone builds the file and merges to master, but get trapped when going to live.

Docs Build status updates of commit 0791cf0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/resources/relnotes.md
:white_check_mark:Succeeded
View

articles/user-guide/libraries/machine-learning/glossary-qml.md
:white_check_mark:Succeeded
View

articles/user-guide/libraries/standard/prelude.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


High CPU utilization, followed by stop of event processing and total outage of all nodes

Please read the CONTRIBUTING.md guidelines to learn on which channels you can
seek for help and ask general questions:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#where-to-seek-for-help
Summary
note:
I can help with additional data/diagnostics within my reach, but this is prod env and many manipulations simply is not an option.
kong cluster, consists of 3 nodes, one in each AZ, AWS cloud.
Flaky upstream, returning HTTP 429.
API host is upstream with 3 targets, passive healthcheck is on.
 {
      "healthchecks": {
        "active": {
          "unhealthy": {
            "http_statuses": [
              429,
              404,
              500,
              501,
              502,
              503,
              504,
              505
            ],
            "tcp_failures": 0,
            "timeouts": 0,
            "http_failures": 0,
            "interval": 0
          },
          "http_path": "/",
          "healthy": {
            "http_statuses": [
              200,
              302
            ],
            "interval": 0,
            "successes": 0
          },
          "timeout": 1,
          "concurrency": 10
        },
        "passive": {
          "unhealthy": {
            "http_failures": 5,
            "http_statuses": [
              429,
              500,
              502,
              503
            ],
            "tcp_failures": 3,
            "timeouts": 3
          },
          "healthy": {
            "successes": 1,
            "http_statuses": [
              200,
              201,
              202,
              203,
              204,
              205,
              206,
              207,
              208,
              226,
              300,
              301,
              302,
              303,
              304,
              305,
              306,
              307,
              308
            ]
          }
        }
      },
      "created_at":<PHONE_NUMBER>687,
      "hash_on": "none",
      "id": "8c228567-2ceb-43f7-8bb4-14e2ef76600c",
      "hash_on_cookie_path": "/",
      "name": "upstream",
      "hash_fallback": "none",
      "slots": 1000
    }

error log is full of:
[lua] healthcheck.lua:988: log(): [healthcheck] (xxxx) unhealthy HTTP increment (1/5)
[lua] healthcheck.lua:988: log(): [healthcheck] (xxxx) unhealthy HTTP increment (2/5)
...
[lua] healthcheck.lua:988: log(): [healthcheck] (xxxx) healthy SUCCESS increment (1/1)

and so on.
observed high CPU utilization and within 10 min complete out of service of the node, similar issues happened on other nodes within 20 min, rendering the whole cluster nonoperational. Reboot of all servers helped to restore service.
notable errors:
2019/03/10 18:18:17 [error] 3668#0: *13573499 [lua] events.lua:254: post(): worker-events: failed posting event "healthy" by "lua-resty-healthcheck [upstream]";
no memory while logging request, client: <IP_ADDRESS>, server: kong, request: "GET /xxxx", host: "api.xxxx.com"

2019/03/10 18:19:56 [warn] 3668#0: *13576878 [lua] socket.lua:152: tcp(): no support for cosockets in this context, falling back to LuaSocket while logging request, client: 10.*.*.*, server: kong, request: "GET /xxxxx", host: "api.xxx.com"

Steps To Reproduce
Don't have clear way to reproduce.
Additional Details & Logs
0.14.1
2019/03/13 04:06:17 [verbose] Kong: 0.14.1
2019/03/13 04:06:17 [debug] ngx_lua: 10013
2019/03/13 04:06:17 [debug] nginx: 1013006
2019/03/13 04:06:17 [debug] Lua: LuaJIT 2.1.0-beta3
2019/03/13 04:06:17 [verbose] reading config file at /etc/kong/kong.conf
2019/03/13 04:06:17 [debug] reading environment variables
2019/03/13 04:06:17 [debug] admin_access_log = "logs/admin_access.log"
2019/03/13 04:06:17 [debug] admin_error_log = "logs/error.log"
2019/03/13 04:06:17 [debug] admin_listen = {"<IP_ADDRESS>:8001"}
2019/03/13 04:06:17 [debug] anonymous_reports = true
2019/03/13 04:06:17 [debug] cassandra_consistency = "LOCAL_QUORUM"
2019/03/13 04:06:17 [debug] cassandra_contact_points = {"cassandra-1pkong-cass-3x-slot1","cassandra-1pkong-cass-3x-slot2","cassandra-1pkong-cass-3x-slot3"}
2019/03/13 04:06:17 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2019/03/13 04:06:17 [debug] cassandra_keyspace = "kong"
2019/03/13 04:06:17 [debug] cassandra_lb_policy = "RequestDCAwareRoundRobin"
2019/03/13 04:06:17 [debug] cassandra_local_datacenter = "us-west-2"
2019/03/13 04:06:17 [debug] cassandra_port = 9042
2019/03/13 04:06:17 [debug] cassandra_repl_factor = 1
2019/03/13 04:06:17 [debug] cassandra_repl_strategy = "SimpleStrategy"
2019/03/13 04:06:17 [debug] cassandra_schema_consensus_timeout = 10000
2019/03/13 04:06:17 [debug] cassandra_ssl = false
2019/03/13 04:06:17 [debug] cassandra_ssl_verify = false
2019/03/13 04:06:17 [debug] cassandra_timeout = 15000
2019/03/13 04:06:17 [debug] cassandra_username = "kong"
2019/03/13 04:06:17 [debug] client_body_buffer_size = "8m"
2019/03/13 04:06:17 [debug] client_max_body_size = "0"
2019/03/13 04:06:17 [debug] client_ssl = false
2019/03/13 04:06:17 [debug] database = "cassandra"
2019/03/13 04:06:17 [debug] db_cache_ttl = 0
2019/03/13 04:06:17 [debug] db_resurrect_ttl = 30
2019/03/13 04:06:17 [debug] db_update_frequency = 5
2019/03/13 04:06:17 [debug] db_update_propagation = 5
2019/03/13 04:06:17 [debug] dns_error_ttl = 1
2019/03/13 04:06:17 [debug] dns_hostsfile = "/etc/hosts"
2019/03/13 04:06:17 [debug] dns_no_sync = false
2019/03/13 04:06:17 [debug] dns_not_found_ttl = 30
2019/03/13 04:06:17 [debug] dns_order = {"LAST","SRV","A","CNAME"}
2019/03/13 04:06:17 [debug] dns_resolver = {}
2019/03/13 04:06:17 [debug] dns_stale_ttl = 4
2019/03/13 04:06:17 [debug] error_default_type = "text/plain"
2019/03/13 04:06:17 [debug] headers = {"server_tokens","latency_tokens"}

{
  "plugins": {
    "enabled_in_cluster": [
      "oauth2",
      "rate-limiting",
      "key-auth",
      "acl",
      "statsd",
      "correlation-id",
      "aws-lambda",
      "request-transformer",
      "cors",
      "prometheus",
      "response-transformer"
    ],
    "available_on_server": {
      "correlation-id": true,
      "pre-function": true,
      "cors": true,
      "rate-limiting": true,
      "loggly": true,
      "hmac-auth": true,
      "zipkin": true,
      "request-size-limiting": true,
      "azure-functions": true,
      "request-transformer": true,
      "oauth2": true,
      "response-transformer": true,
      "ip-restriction": true,
      "statsd": true,
      "basic-auth": true,
      "key-auth": true,
      "http-log": true,
      "bot-detection": true,
      "datadog": true,
      "tcp-log": true,
      "post-function": true,
      "jwt": true,
      "acl": true,
      "prometheus": true,
      "syslog": true,
      "response-ratelimiting": true,
      "udp-log": true,
      "file-log": true,
      "aws-lambda": true,
      "auth-plugin": true,
      "ldap-auth": true,
      "request-termination": true
    }
  },
  "tagline": "Welcome to kong",
  "configuration": {
    "plugins": [
      "bundled"
    ],
    "admin_listen": [
      "<IP_ADDRESS>:8001"
    ],
    "proxy_access_log": "logs/access.log",
    "trusted_ips": [
      "<IP_ADDRESS>/0",
      "::/0"
    ],
    "prefix": "/usr/local/kong",
    "loaded_plugins": {
      "correlation-id": true,
      "cors": true,
      "rate-limiting": true,
      "loggly": true,
      "hmac-auth": true,
      "zipkin": true,
      "bot-detection": true,
      "azure-functions": true,
      "request-transformer": true,
      "oauth2": true,
      "response-transformer": true,
      "ip-restriction": true,
      "statsd": true,
      "basic-auth": true,
      "key-auth": true,
      "http-log": true,
      "syslog": true,
      "datadog": true,
      "tcp-log": true,
      "ldap-auth": true,
      "post-function": true,
      "jwt": true,
      "acl": true,
      "request-size-limiting": true,
      "pre-function": true,
      "response-ratelimiting": true,
      "udp-log": true,
      "file-log": true,
      "aws-lambda": true,
      "auth-plugin": true,
      "prometheus": true,
      "request-termination": true
    },
    "cassandra_username": "kong",
    "admin_ssl_cert_csr_default": "/usr/local/kong/ssl/admin-kong-default.csr",
    "ssl_cert_key": "/usr/local/kong/ssl/kong-default.key",
    "dns_resolver": {},
    "pg_user": "kong",
    "mem_cache_size": "128m",
    "cassandra_data_centers": [
      "dc1:2",
      "dc2:3"
    ],
    "nginx_admin_directives": {},
    "custom_plugins": [
    ],
    "pg_host": "<IP_ADDRESS>",
    "nginx_acc_logs": "/usr/local/kong/logs/access.log",
    "proxy_listen": [
      "<IP_ADDRESS>:8000",
      "<IP_ADDRESS>:8443 ssl"
    ],
    "client_ssl_cert_default": "/usr/local/kong/ssl/kong-default.crt",
    "ssl_cert_key_default": "/usr/local/kong/ssl/kong-default.key",
    "dns_no_sync": false,
    "db_update_propagation": 5,
    "nginx_err_logs": "/usr/local/kong/logs/error.log",
    "cassandra_port": 9042,
    "dns_order": [
      "LAST",
      "SRV",
      "A",
      "CNAME"
    ],
    "dns_error_ttl": 1,
    "headers": [
      "server_tokens",
      "latency_tokens"
    ],
    "dns_stale_ttl": 4,
    "nginx_optimizations": true,
    "database": "cassandra",
    "pg_database": "kong",
    "nginx_worker_processes": "auto",
    "lua_package_cpath": "",
    "admin_acc_logs": "/usr/local/kong/logs/admin_access.log",
    "lua_package_path": "./?.lua;./?/init.lua;",
    "nginx_pid": "/usr/local/kong/pids/nginx.pid",
    "upstream_keepalive": 60,
    "cassandra_contact_points": [
      "cassandra-1pkong-cass-3x-slot1",
      "cassandra-1pkong-cass-3x-slot2",
      "cassandra-1pkong-cass-3x-slot3"
    ],
    "client_ssl_cert_csr_default": "/usr/local/kong/ssl/kong-default.csr",
    "proxy_listeners": [
      {
        "ssl": false,
        "ip": "<IP_ADDRESS>",
        "proxy_protocol": false,
        "port": 8000,
        "http2": false,
        "listener": "<IP_ADDRESS>:8000"
      },
      {
        "ssl": true,
        "ip": "<IP_ADDRESS>",
        "proxy_protocol": false,
        "port": 8443,
        "http2": false,
        "listener": "<IP_ADDRESS>:8443 ssl"
      }
    ],
    "proxy_ssl_enabled": true,
    "lua_ssl_verify_depth": 1,
    "admin_access_log": "logs/admin_access.log",
    "enabled_headers": {
      "latency_tokens": true,
      "X-Kong-Proxy-Latency": true,
      "Via": true,
      "server_tokens": true,
      "Server": true,
      "X-Kong-Upstream-Latency": true,
      "X-Kong-Upstream-Status": false
    },
    "cassandra_ssl": false,
    "cassandra_local_datacenter": "us-west-2",
    "db_resurrect_ttl": 30,
    "admin_ssl_enabled": false,
    "cassandra_consistency": "LOCAL_QUORUM",
    "client_max_body_size": "0",
    "admin_error_log": "logs/error.log",
    "pg_ssl_verify": false,
    "dns_not_found_ttl": 30,
    "pg_ssl": false,
    "client_ssl": false,
    "db_update_frequency": 5,
    "cassandra_repl_strategy": "SimpleStrategy",
    "cassandra_repl_factor": 1,
    "nginx_kong_conf": "/usr/local/kong/nginx-kong.conf",
    "cassandra_lb_policy": "RequestDCAwareRoundRobin",
    "nginx_http_directives": [
      {
        "value": "prometheus_metrics 5m",
        "name": "lua_shared_dict"
      }
    ],
    "kong_env": "/usr/local/kong/.kong_env",
    "cassandra_schema_consensus_timeout": 10000,
    "dns_hostsfile": "/etc/hosts",
    "log_level": "notice",
    "real_ip_header": "X-Real-IP",
    "ssl_cert": "/usr/local/kong/ssl/kong-default.crt",
    "error_default_type": "text/plain",
    "admin_ssl_cert_key_default": "/usr/local/kong/ssl/admin-kong-default.key",
    "cassandra_ssl_verify": false,
    "ssl_ciphers": "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256",
    "ssl_cipher_suite": "modern",
    "real_ip_recursive": "off",
    "proxy_error_log": "logs/error.log",
    "client_ssl_cert_key_default": "/usr/local/kong/ssl/kong-default.key",
    "nginx_daemon": "on",
    "anonymous_reports": true,
    "nginx_proxy_directives": {},
    "cassandra_timeout": 15000,
    "pg_port": 5432,
    "admin_listeners": [
      {
        "ssl": false,
        "ip": "<IP_ADDRESS>",
        "proxy_protocol": false,
        "port": 8001,
        "http2": false,
        "listener": "<IP_ADDRESS>:8001"
      }
    ],
    "client_body_buffer_size": "8m",
    "lua_socket_pool_size": 30,
    "admin_ssl_cert_default": "/usr/local/kong/ssl/admin-kong-default.crt",
    "db_cache_ttl": 0,
    "cassandra_keyspace": "kong",
    "ssl_cert_default": "/usr/local/kong/ssl/kong-default.crt",
    "ssl_cert_csr_default": "/usr/local/kong/ssl/kong-default.csr",
    "nginx_conf": "/usr/local/kong/nginx.conf"
  },
  "version": "0.14.1",
  "node_id": "6222e65c-6e45-4791-b8c5-73f011ac1257",
  "lua_version": "LuaJIT 2.1.0-beta3",
  "prng_seeds": {
    "pid: 32110":<PHONE_NUMBER>81,
    "pid: 32109":<PHONE_NUMBER>19
  },
  "timers": {
    "pending": 5,
    "running": 0
  },
  "hostname": "ip-10-152-39-133"
}

I've analyzed logs, this is definitely nginx worker CPU usage
2019-03-11 00:03:17.754
UID        PID  PPID  C STIME TTY          TIME CMD
nobody   14771 14770  0 Mar10 ?        00:01:21 nginx: worker process
nobody   14772 14770  0 Mar10 ?        00:01:08 nginx: worker process

2019-03-11 20:05:28.487
UID        PID  PPID  C STIME TTY          TIME CMD
nobody   14771 14770  1 Mar10 ?        00:15:05 nginx: worker process
nobody   14772 14770 49 Mar10 ?        11:52:37 nginx: worker process

2019-03-12 02:42:23.986
UID        PID  PPID  C STIME TTY          TIME CMD
nobody   14771 14770  9 Mar10 ?        02:45:25 nginx: worker process
nobody   14772 14770 60 Mar10 ?        18:28:22 nginx: worker process

The error line

no memory while logging request

Indicates a memory allocation error, either due to the system being out of memory, or the Lua VM reaching the 2GB limit inside the worker process. What class of AWS instance is Kong running on in your environment?

this was t2.large, 8GB, we had 2 worker per node, each worker memory utilization was  ~1.23GB per worker, total memory usage was flat before 100% CPU spike and during.
as I stated in the report, all metrics were fine, except CPU. I can provide more detailed statistics about the system, if needed.

I don't recommend running on burstable t2 instances, as AWS throttling really causes a headache ;) Are you able to check to see if that instance(s) in question had available CPU credits to burn through? Are you able to replicate this behavior now?

this was the first metric I checked, CPU credits, yes, there was enough, at least according to AWS.
we moved to m5.xlarge regardless immediately, but previous setup was working for months without any problems. No, we don't see anything yet, and I'm going to  try to reproduce the behavior.
I have a good but unproven suspicion about passive healthcheck, specifically when it trips instance on/off based on response.

got the similar issue last weekend, this time that we set instance autoreplacement and it wasn't that disruptive, this was m3.xlarge instance.
Still no clue, probably need to set debug log on one and see.

have similar issue, high memory usage in db-less mode when using t2.xlarge instance.

@HsinHeng you probably have different issue, as db-less more is version 1.x, I have 0.14.1 also I don't see much of the memory utilization, but CPU usage max-out

ok, I'm closing this for now, we didn't see anymore failures, following was done:

file handlers 8096
new instance type: m5.xlarge
change in nginx-kong.conf, that reduced # of buffered responses

proxy_buffer_size 128k;
proxy_buffers 8 128k;
proxy_busy_buffers_size 256k;


Could not get the latest source version for repository

@setuc  /mlops/devops-pipelines/deploy-model-training-pipeline.yml: Could not get the latest source version for repository Azure/mlops-templates hosted on https://github.com/ using ref refs/heads/main. GitHub reported the error, "Bad credentials"

Thank you ..

@yogidosalwar Can you provide more details on the issue? how have you deployed the pipeline? How have you setup the service connection? Does the connection have access to your repository where you are hosting it?

@setuc  issue resolved .....
Solution :
It was GitHub connection error in Devops. My previous Github token was expired.
New Github connection created using new token in Devops.
Thank you

Thank you for the update.


const params

Why const x : byte ?  On some architectures that might be by ref.

The "Buffer" input parameter to both FileRead and FileWrite is a "formal const" anyways, so I don't think that this one ultimately matters. What architectures did you have in mind? Also note that const is not the same as constref.

I read it at Lazarus forum, don’t know

I think I'll leave this one is, for the time being at least.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1424

Questions ?
Please refer to the Backport tool documentation


Enhancing instrction page looks

Fixes Issue🛠
Closes #158
Description👨💻

Type of change📄

[] New feature (non-breaking change which adds functionality)

How this has been tested✅

Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I am an Open Source Contributor

Screenshots/GIF📷

Merged!! 🎉 @kamalsritha


Rate limit for deletes in InfluxDB Cloud

Add new rate limit for deletes in Cloud. Reach out to @bpalani for details.
https://docs.influxdata.com/influxdb/cloud/account-management/pricing-plans/

This issue was resolved by https://github.com/influxdata/docs-v2/pull/3015.


WIP: Add support for multiple ips to resolve slow steam downloads

Background
Steam uses a connection pool to manage download it's files. The library it uses appears to obey the full http spec and limit it's connection pool to 2-4 connections per IP (Not per host). The standard lancache container only has one IP per cdn and as such steams ability to download using multiple connections is restricted resulting in a slower initial download speed.
Changes
This PR allows multiple IP's to be set for any of the _IP environment variables, for example STEAMCACHE_IP="<IP_ADDRESS> <IP_ADDRESS>".
Testing
This is currently a testing image. If you wish to help out testing please change your steamcache-dns docker command to pull from steamcache/steamcache-dns:multiple-ips then carefully follow the tuning guide below. Let us know your results in the comments.
Tuning your cache
The limitations seen in steam download speed are highly dependent on the latency between your server and the steam cdn servers. In the event you find your initial download speed with the default settings is slow this can be resolved by allocating more IP's to your steamcache. We suggest adding one IP at a time to see how much gain can be had (4 seems to work for a number of people)
Step 1: Adding IP's to your docker host
Consult your OS documentation in order to add additional IP addresses onto your docker cache host machine
Step 2: Adding IP's to your cache container
In order for this to work you need to add the port maps onto the relevant cdn container (for example steam).

If you are using steamcache/monolithic then using -p 80:80 should be sufficient as per the documentation.
If you are using steamcache/generic or steamcache/steamcache then add multiple -p <IPadddress>:80:80 for each IP you have added. For example -p <IP_ADDRESS>:80:80 -p <IP_ADDRESS>:80:80

Step 3: Informing steamcache-dns of the extra IP's
Finally we need to inform steamcache-dns that STEAM is now available on multiple IP addresses. This can be done on the command line using the following command -e STEAMCACHE_IP="<IP_ADDRESS> <IP_ADDRESS>". Note the quotes surrounding the multiple IP addresses.
Step 4: Testing
Choose a game which has not been seen by the cache before (or clear your /data/cache folder) and start it downloading. Check to see what the maximum speed seen by your steam client is. If necessary repeat steps 1-3 with additional IPs until you see a download equivalent to your uncached steam client or no longer see an improvement vs the previous IP allocation.

@JasonRivers fyi, I've made some slight changes and this now uses RPZ for the zone files as it's cleaner for the multiple IP allocations

I can confirm this does fix my performance issue. Even seems to scale almost linearly with extra IPs allocated (going from 1 to 11 IP addresses boosted my through-cache downloads from 25MBit to 250MBit).
Still not resource constrained on anything as far as I can see, will experiment with even more IPs.

Can confirm adding 10 IP's has no restrictions and i am able to download at full rate of my internet connection as a single user downloader!

@fisheke did u add several ip's to the same network card ? (so its like 1 NIC for steam that has several ip's assigned to it) , thank you

How did you get it to work?

Approved via uklans discord

Hi,
Thanks for this useful piece of software.
When will there be a complete updated quide available? Ive even tried HAProxy to roundrobin inbound connections to port80, still 1 PC cant get max speed out of the cache server.
Peon

@Peon-SouthAfrica you shouldn't need haproxy anymore, if you switch to using monolithic and then follow the readme including "tuning your cache"

HAProxy was just an attempt to try and get more speed. It didnt work sadly.
Should I post the commands im issuing?

@Peon-SouthAfrica if you are still seeing this issue can you create a new issue on generic or monolithic as appropriate

Well, i dont know what exactly, but i am doing something wrong.
I gave my Server a few more Ip-adresses and started everything, but somehow, it is insanely slow, and i dont know why.
My average download speed on Steam is about 11.5mbps and with everything setup as below, i only get about 1mbps
docker run
--restart unless-stopped -d
--name Mono_Cache
-p 80:80
-v /volume1/Steamcache/cache:/data/cache/cache
-v /volume1/Steamcache/logs:/data/logs
steamcache/monolithic:latest
docker run
--restart unless-stopped -d
--name Sniproxy
-p 443:443
steamcache/sniproxy:latest
docker run
--restart unless-stopped -d
--name Steamcache-DNS
-p <IP_ADDRESS>:53:53/udp
-e STEAMCACHE_IP="<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>"
steamcache/steamcache-dns:multiple-ips
i also tried it with less Ip´s but that didnt work either and i cannot give my server 100 Ip-adresses.
The Main ip-adress of my server is the one with 200 at the end, the other ones are the ones, i assigned additionally to the Server


Support shadow table for pressure test.

What would you like to be added:
Why is this needed:
Support shadow table for pressure test.

ref: #303

ref #364  #365


Sync only prefix related ip-addresses

Is your feature request related to a problem? Please describe.
We must manually fill up ip-list IPV4-ALLOWED (IPV6-ALLOWED)
Describe the solution you'd like
In some environment like own I already have fill up ip-prefixes in netbox. We can automate it and do not fill up ip-list manually.

@inetman28 Hello! How would you prefer this is automated? Are you suggesting that all prefixes which exist already inside the NetBox instance would be permitted and anything not created there would be ignored?

@inetman28 Hello! How would you prefer this is automated? Are you suggesting that all prefixes which exist already inside the NetBox instance would be permitted and anything not created there would be ignored?

Yes, you are right.
I mean something like this:
import pynetbox

IPV4_ALLOWED = []
IPV6_ALLOWED = []
all_prefixes = nb.ipam.prefixes.all()
for prefix in all_prefixes:
    if prefix.family.value == 4:
        IPV4_ALLOWED.append(prefix.prefix)
    elif prefix.family.value == 6:
        IPV6_ALLOWED.append(prefix.prefix)


Code refactoring - Removed unnecessary usings, added regions and comments

Closing the PR as we don't need the suggested changes

Closing the PR as we don't need the suggested changes


Misc cmake updates

Thanks for your contributions, Chuck.  We'll take a look at your PR.  I'll be on travel this coming week, so I likely won't get to it until some time after I return.


:robot: triggering CI on branch 'release-next' after synching from upstream/main

Codecov Report

Merging #634 (7ff36c4) into release-next (7ff36c4) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 7ff36c4 differs from pull request most recent head 618fe80. Consider uploading reports for the commit 618fe80 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##           release-next     #634   +/-   ##
=============================================
  Coverage         49.06%   49.06%
=============================================
  Files                96       96
  Lines             13104    13104
=============================================
  Hits               6429     6429
  Misses             6041     6041
  Partials            634      634

OCF Webhook is merging this PR


Completion rewrite

The current module is a horror, so it's being rewritten. Some of the following points might not be included in the initial rewrite.

[x] Rewrite module
[x] Add source ordering (#153)
[ ] Add mini.completion
[x] Add luasnip

#404