conf(VETS-CPC-126): Multi-Step Dockerfile setup

changed the docker file in order to reduce the size of the image after docker composing (this removes the need to build the service before doing a docker compose)

Results from docker-compose up vets and docker-compose up
:champlain_petclinic Christian$ docker-compose up vets [+] Running 2/0  ⠿ Container champlain_petclinic_mysql2_1  Created                                                                                0.0s  ⠿ Container champlain_petclinic_vets_1    Created                                                                                0.0s Attaching to vets_1 vets_1  |  vets_1  |   .   ____          _            __ _ _ vets_1  |  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \ vets_1  | ( ( )\___ | '_ | '_| | '_ \/ _ | \ \ \
vets_1  |  \/  )| |)| | | | | || (| |  ) ) ) )
vets_1  |   '  || .__|| ||| |_, | / / / /
vets_1  |  =========||==============|/=////
vets_1  |  :: Spring Boot ::        (v2.3.2.RELEASE)
vets_1  |
vets_1  | 2021-09-15 23:46:11.150  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Starting VetsServiceApplication on f7ed3464d5dd with PID 1 (/app.jar started by root in /)
vets_1  | 2021-09-15 23:46:11.156 DEBUG 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE
vets_1  | 2021-09-15 23:46:11.156  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : The following profiles are active: docker
vets_1  | 2021-09-15 23:46:13.167  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFERRED mode.
vets_1  | 2021-09-15 23:46:13.316  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 131ms. Found 1 JPA repository interfaces.
vets_1  | 2021-09-15 23:46:14.479  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
vets_1  | 2021-09-15 23:46:14.505  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
vets_1  | 2021-09-15 23:46:14.506  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.37]
vets_1  | 2021-09-15 23:46:14.660  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
vets_1  | 2021-09-15 23:46:14.660  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 3382 ms
vets_1  | 2021-09-15 23:46:15.087  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
vets_1  | 2021-09-15 23:46:15.855  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
vets_1  | 2021-09-15 23:46:16.051  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
vets_1  | 2021-09-15 23:46:16.208  INFO 1 --- [         task-1] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
vets_1  | 2021-09-15 23:46:16.358  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
vets_1  | 2021-09-15 23:46:16.528  INFO 1 --- [         task-1] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.4.18.Final
vets_1  | 2021-09-15 23:46:16.914  INFO 1 --- [         task-1] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
vets_1  | 2021-09-15 23:46:17.274  INFO 1 --- [         task-1] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
vets_1  | 2021-09-15 23:46:18.735  INFO 1 --- [         task-1] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
vets_1  | 2021-09-15 23:46:18.756  INFO 1 --- [         task-1] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
vets_1  | 2021-09-15 23:46:18.846  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
vets_1  | 2021-09-15 23:46:18.924  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
vets_1  | 2021-09-15 23:46:18.927  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Triggering deferred initialization of Spring Data repositories…
vets_1  | 2021-09-15 23:46:19.336  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Spring Data repositories initialized!
vets_1  | 2021-09-15 23:46:19.358  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Started VetsServiceApplication in 9.506 seconds (JVM running for 10.558)
^CGracefully stopping... (press Ctrl+C again to force)
[+] Running 0/0
[+] Running 0/1amplain_petclinic_vets_1  Stopping                                                                                0.1s
⠙ Container champlain_petclinic_vets_1  Stopping                                                                                0.2s
:champlain_petclinic Christian$ canceled
docker-compose up
[+] Running 7/0
⠿ Container champlain_petclinic_mysql3_1       Created                                                                                0.0s
⠿ Container champlain_petclinic_mysql1_1       Created                                                                                0.0s
⠿ Container champlain_petclinic_mysql2_1       Created                                                                                0.0s
⠿ Container champlain_petclinic_visits_1       Created                                                                                0.0s
⠿ Container champlain_petclinic_customers_1    Created                                                                                0.0s
⠿ Container champlain_petclinic_vets_1         Created                                                                                0.0s
⠿ Container champlain_petclinic_api-gateway_1  Created                                                                                0.0s
Attaching to api-gateway_1, customers_1, mysql1_1, mysql2_1, mysql3_1, vets_1, visits_1
mysql2_1       | 2021-09-15 23:51:36+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql1_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql3_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql2_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql2_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql1_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql1_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql3_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql3_1       | 2021-09-15 23:51:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.35-1debian10 started.
mysql2_1       | 2021-09-15T23:51:37.455091Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql2_1       | 2021-09-15T23:51:37.457087Z 0 [Note] mysqld (mysqld 5.7.35) starting as process 1 ...
mysql2_1       | 2021-09-15T23:51:37.461146Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql2_1       | 2021-09-15T23:51:37.461290Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql2_1       | 2021-09-15T23:51:37.461366Z 0 [Note] InnoDB: Uses event mutexes
mysql2_1       | 2021-09-15T23:51:37.461503Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql2_1       | 2021-09-15T23:51:37.461583Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql2_1       | 2021-09-15T23:51:37.461647Z 0 [Note] InnoDB: Using Linux native AIO
mysql2_1       | 2021-09-15T23:51:37.461982Z 0 [Note] InnoDB: Number of pools: 1
mysql2_1       | 2021-09-15T23:51:37.462252Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql2_1       | 2021-09-15T23:51:37.465854Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql2_1       | 2021-09-15T23:51:37.479267Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql2_1       | 2021-09-15T23:51:37.482760Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql1_1       | 2021-09-15T23:51:37.480510Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql1_1       | 2021-09-15T23:51:37.482633Z 0 [Note] mysqld (mysqld 5.7.35) starting as process 1 ...
mysql1_1       | 2021-09-15T23:51:37.491611Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql1_1       | 2021-09-15T23:51:37.491705Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql1_1       | 2021-09-15T23:51:37.491724Z 0 [Note] InnoDB: Uses event mutexes
mysql1_1       | 2021-09-15T23:51:37.491737Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql1_1       | 2021-09-15T23:51:37.491760Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql1_1       | 2021-09-15T23:51:37.491782Z 0 [Note] InnoDB: Using Linux native AIO
mysql1_1       | 2021-09-15T23:51:37.493529Z 0 [Note] InnoDB: Number of pools: 1
mysql1_1       | 2021-09-15T23:51:37.494271Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql1_1       | 2021-09-15T23:51:37.506913Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql2_1       | 2021-09-15T23:51:37.511227Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql2_1       | 2021-09-15T23:51:37.517570Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12704809
mysql2_1       | 2021-09-15T23:51:37.517883Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 12704818
mysql2_1       | 2021-09-15T23:51:37.518141Z 0 [Note] InnoDB: Database was not shutdown normally!
mysql2_1       | 2021-09-15T23:51:37.518519Z 0 [Note] InnoDB: Starting crash recovery.
mysql1_1       | 2021-09-15T23:51:37.560784Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql1_1       | 2021-09-15T23:51:37.573413Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql1_1       | 2021-09-15T23:51:37.602035Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql1_1       | 2021-09-15T23:51:37.606193Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12670382
mysql1_1       | 2021-09-15T23:51:37.606237Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 12670391
mysql1_1       | 2021-09-15T23:51:37.606250Z 0 [Note] InnoDB: Database was not shutdown normally!
mysql1_1       | 2021-09-15T23:51:37.606262Z 0 [Note] InnoDB: Starting crash recovery.
mysql2_1       | 2021-09-15T23:51:37.646619Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql2_1       | 2021-09-15T23:51:37.646987Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql2_1       | 2021-09-15T23:51:37.647874Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql3_1       | 2021-09-15T23:51:37.670477Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql3_1       | 2021-09-15T23:51:37.679677Z 0 [Note] mysqld (mysqld 5.7.35) starting as process 1 ...
mysql3_1       | 2021-09-15T23:51:37.688325Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql3_1       | 2021-09-15T23:51:37.688461Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql3_1       | 2021-09-15T23:51:37.688473Z 0 [Note] InnoDB: Uses event mutexes
mysql3_1       | 2021-09-15T23:51:37.688483Z 0 [Note] InnoDB: GCC builtin atomic_thread_fence() is used for memory barrier
mysql3_1       | 2021-09-15T23:51:37.688497Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql3_1       | 2021-09-15T23:51:37.688505Z 0 [Note] InnoDB: Using Linux native AIO
mysql3_1       | 2021-09-15T23:51:37.689469Z 0 [Note] InnoDB: Number of pools: 1
mysql3_1       | 2021-09-15T23:51:37.690064Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql3_1       | 2021-09-15T23:51:37.698442Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql3_1       | 2021-09-15T23:51:37.728178Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql3_1       | 2021-09-15T23:51:37.731022Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql2_1       | 2021-09-15T23:51:37.732068Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql2_1       | 2021-09-15T23:51:37.733769Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
mysql2_1       | 2021-09-15T23:51:37.733872Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
mysql2_1       | 2021-09-15T23:51:37.734737Z 0 [Note] InnoDB: Waiting for purge to start
mysql3_1       | 2021-09-15T23:51:37.758415Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql3_1       | 2021-09-15T23:51:37.761955Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12715315
mysql3_1       | 2021-09-15T23:51:37.762006Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 12715324
mysql3_1       | 2021-09-15T23:51:37.762025Z 0 [Note] InnoDB: Database was not shutdown normally!
mysql3_1       | 2021-09-15T23:51:37.762033Z 0 [Note] InnoDB: Starting crash recovery.
mysql1_1       | 2021-09-15T23:51:37.768045Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql1_1       | 2021-09-15T23:51:37.768088Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql1_1       | 2021-09-15T23:51:37.768132Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql2_1       | 2021-09-15T23:51:37.785238Z 0 [Note] InnoDB: 5.7.35 started; log sequence number 12704818
mysql2_1       | 2021-09-15T23:51:37.785923Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql2_1       | 2021-09-15T23:51:37.786237Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql2_1       | 2021-09-15T23:51:37.792145Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210915 23:51:37
mysql2_1       | 2021-09-15T23:51:37.810178Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
mysql2_1       | 2021-09-15T23:51:37.810349Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
mysql2_1       | 2021-09-15T23:51:37.810414Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
mysql2_1       | 2021-09-15T23:51:37.810534Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
mysql2_1       | 2021-09-15T23:51:37.811594Z 0 [Warning] CA certificate ca.pem is self signed.
mysql2_1       | 2021-09-15T23:51:37.811775Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
mysql2_1       | 2021-09-15T23:51:37.812646Z 0 [Note] Server hostname (bind-address): ''; port: 3306
mysql2_1       | 2021-09-15T23:51:37.812820Z 0 [Note] IPv6 is available.
mysql2_1       | 2021-09-15T23:51:37.812957Z 0 [Note]   - '::' resolves to '::';
mysql2_1       | 2021-09-15T23:51:37.813100Z 0 [Note] Server socket created on IP: '::'.
mysql2_1       | 2021-09-15T23:51:37.817420Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
mysql2_1       | 2021-09-15T23:51:37.835395Z 0 [Note] Event Scheduler: Loaded 0 events
mysql2_1       | 2021-09-15T23:51:37.836998Z 0 [Note] mysqld: ready for connections.
mysql2_1       | Version: '5.7.35'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
mysql1_1       | 2021-09-15T23:51:37.853557Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql1_1       | 2021-09-15T23:51:37.855495Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
mysql1_1       | 2021-09-15T23:51:37.855604Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
mysql1_1       | 2021-09-15T23:51:37.856765Z 0 [Note] InnoDB: Waiting for purge to start
mysql1_1       | 2021-09-15T23:51:37.907578Z 0 [Note] InnoDB: 5.7.35 started; log sequence number 12670391
mysql1_1       | 2021-09-15T23:51:37.908394Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql1_1       | 2021-09-15T23:51:37.908545Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql1_1       | 2021-09-15T23:51:37.933646Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
mysql1_1       | 2021-09-15T23:51:37.933711Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
mysql1_1       | 2021-09-15T23:51:37.933727Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
mysql1_1       | 2021-09-15T23:51:37.933737Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
mysql1_1       | 2021-09-15T23:51:37.938968Z 0 [Warning] CA certificate ca.pem is self signed.
mysql1_1       | 2021-09-15T23:51:37.939032Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
mysql1_1       | 2021-09-15T23:51:37.941364Z 0 [Note] Server hostname (bind-address): ''; port: 3306
mysql1_1       | 2021-09-15T23:51:37.941423Z 0 [Note] IPv6 is available.
mysql1_1       | 2021-09-15T23:51:37.941450Z 0 [Note]   - '::' resolves to '::';
mysql1_1       | 2021-09-15T23:51:37.941538Z 0 [Note] Server socket created on IP: '::'.
mysql3_1       | 2021-09-15T23:51:37.946198Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql3_1       | 2021-09-15T23:51:37.946244Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql3_1       | 2021-09-15T23:51:37.946298Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql1_1       | 2021-09-15T23:51:37.949228Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
mysql1_1       | 2021-09-15T23:51:37.953968Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210915 23:51:37
mysql3_1       | 2021-09-15T23:51:38.164687Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql3_1       | 2021-09-15T23:51:38.167577Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
mysql3_1       | 2021-09-15T23:51:38.167683Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
mysql1_1       | 2021-09-15T23:51:38.168909Z 0 [Note] Event Scheduler: Loaded 0 events
mysql1_1       | 2021-09-15T23:51:38.169850Z 0 [Note] mysqld: ready for connections.
mysql3_1       | 2021-09-15T23:51:38.169709Z 0 [Note] InnoDB: 5.7.35 started; log sequence number 12715324
mysql1_1       | Version: '5.7.35'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
mysql3_1       | 2021-09-15T23:51:38.171174Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql3_1       | 2021-09-15T23:51:38.172584Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql3_1       | 2021-09-15T23:51:38.205730Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
mysql3_1       | 2021-09-15T23:51:38.205782Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
mysql3_1       | 2021-09-15T23:51:38.205796Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
mysql3_1       | 2021-09-15T23:51:38.205808Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
mysql3_1       | 2021-09-15T23:51:38.208584Z 0 [Warning] CA certificate ca.pem is self signed.
mysql3_1       | 2021-09-15T23:51:38.208647Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
mysql3_1       | 2021-09-15T23:51:38.210331Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
mysql3_1       | 2021-09-15T23:51:38.210516Z 0 [Note] IPv6 is available.
mysql3_1       | 2021-09-15T23:51:38.210541Z 0 [Note]   - '::' resolves to '::';
mysql3_1       | 2021-09-15T23:51:38.210565Z 0 [Note] Server socket created on IP: '::'.
mysql3_1       | 2021-09-15T23:51:38.214159Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210915 23:51:38
mysql3_1       | 2021-09-15T23:51:38.215623Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
mysql3_1       | 2021-09-15T23:51:38.278422Z 0 [Note] Event Scheduler: Loaded 0 events
mysql3_1       | 2021-09-15T23:51:38.279097Z 0 [Note] mysqld: ready for connections.
mysql3_1       | Version: '5.7.35'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
vets_1         |
vets_1         |   .   ____          _            __ _ _
vets_1         |  /\ / ' __ _ () __  __ _ \ \ \
vets_1         | ( ( )_ | ' | '| | '_ /  | \ \ \ \ vets_1         |  \\/  ___)| |_)| | | | | || (_| |  ) ) ) ) vets_1         |   '  |____| .__|_| |_|_| |_\__, | / / / / vets_1         |  =========|_|==============|___/=/_/_/_/ vets_1         |  :: Spring Boot ::        (v2.3.2.RELEASE) vets_1         |  visits_1       |  visits_1       |   .   ____          _            __ _ _ visits_1       |  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \ visits_1       | ( ( )\___ | '_ | '_| | '_ \/ _ | \ \ \
visits_1       |  \/  )| |)| | | | | || (| |  ) ) ) )
visits_1       |   '  || .__|| ||| |_, | / / / /
visits_1       |  =========||==============|/=////
visits_1       |  :: Spring Boot ::        (v2.3.2.RELEASE)
visits_1       |
customers_1    |
customers_1    |   .   ____          _            __ _ _
customers_1    |  /\ / ' __ _ () __  __ _ \ \ \
customers_1    | ( ( )__ | '_ | '| | ' /  | \ \ \ \ customers_1    |  \\/  ___)| |_)| | | | | || (_| |  ) ) ) ) customers_1    |   '  |____| .__|_| |_|_| |_\__, | / / / / customers_1    |  =========|_|==============|___/=/_/_/_/ customers_1    |  :: Spring Boot ::        (v2.3.2.RELEASE) customers_1    |  vets_1         | 2021-09-15 23:51:55.742  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Starting VetsServiceApplication on f7ed3464d5dd with PID 1 (/app.jar started by root in /) vets_1         | 2021-09-15 23:51:55.771 DEBUG 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE vets_1         | 2021-09-15 23:51:55.772  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : The following profiles are active: docker visits_1       | 2021-09-15 23:51:56.164  INFO 1 --- [           main] c.p.visits.VisitsServiceApplication      : Starting VisitsServiceApplication on 9d55961eaa45 with PID 1 (/app.jar started by root in /) visits_1       | 2021-09-15 23:51:56.199 DEBUG 1 --- [           main] c.p.visits.VisitsServiceApplication      : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE visits_1       | 2021-09-15 23:51:56.200  INFO 1 --- [           main] c.p.visits.VisitsServiceApplication      : The following profiles are active: docker api-gateway_1  |  api-gateway_1  |   .   ____          _            __ _ _ api-gateway_1  |  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \ api-gateway_1  | ( ( )\___ | '_ | '_| | '_ \/ _ | \ \ \
api-gateway_1  |  \/  )| |)| | | | | || (| |  ) ) ) )
api-gateway_1  |   '  || .__|| ||| |_, | / / / /
api-gateway_1  |  =========||==============|/=////
api-gateway_1  |  :: Spring Boot ::        (v2.3.2.RELEASE)
api-gateway_1  |
customers_1    | 2021-09-15 23:51:56.647  INFO 1 --- [           main] c.p.c.CustomersServiceApplication        : Starting CustomersServiceApplication on 85fc2b8b228c with PID 1 (/app.jar started by root in /)
customers_1    | 2021-09-15 23:51:56.672 DEBUG 1 --- [           main] c.p.c.CustomersServiceApplication        : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE
customers_1    | 2021-09-15 23:51:56.672  INFO 1 --- [           main] c.p.c.CustomersServiceApplication        : The following profiles are active: docker
api-gateway_1  | 2021-09-15 23:51:57.195  INFO 1 --- [           main] c.p.b.BFFApiGatewayApplication           : Starting BFFApiGatewayApplication on 06bf9d07333f with PID 1 (/app.jar started by root in /)
api-gateway_1  | 2021-09-15 23:51:57.213 DEBUG 1 --- [           main] c.p.b.BFFApiGatewayApplication           : Running with Spring Boot v2.3.2.RELEASE, Spring v5.2.8.RELEASE
api-gateway_1  | 2021-09-15 23:51:57.213  INFO 1 --- [           main] c.p.b.BFFApiGatewayApplication           : The following profiles are active: docker
vets_1         | 2021-09-15 23:52:02.507  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFERRED mode.
vets_1         | 2021-09-15 23:52:02.880  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 323ms. Found 1 JPA repository interfaces.
visits_1       | 2021-09-15 23:52:03.171  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFERRED mode.
visits_1       | 2021-09-15 23:52:03.523  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 288ms. Found 1 JPA repository interfaces.
customers_1    | 2021-09-15 23:52:03.625  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFERRED mode.
customers_1    | 2021-09-15 23:52:03.970  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 294ms. Found 2 JPA repository interfaces.
vets_1         | 2021-09-15 23:52:05.941  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
vets_1         | 2021-09-15 23:52:06.002  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
vets_1         | 2021-09-15 23:52:06.010  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.37]
vets_1         | 2021-09-15 23:52:06.539  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
vets_1         | 2021-09-15 23:52:06.541  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 10267 ms
customers_1    | 2021-09-15 23:52:06.953  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
customers_1    | 2021-09-15 23:52:07.035  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
customers_1    | 2021-09-15 23:52:07.046  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.37]
visits_1       | 2021-09-15 23:52:07.267  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
visits_1       | 2021-09-15 23:52:07.331  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
visits_1       | 2021-09-15 23:52:07.332  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.37]
customers_1    | 2021-09-15 23:52:07.506  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
customers_1    | 2021-09-15 23:52:07.506  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 10600 ms
visits_1       | 2021-09-15 23:52:07.841  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
visits_1       | 2021-09-15 23:52:07.844  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 11106 ms
vets_1         | 2021-09-15 23:52:08.075  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
customers_1    | 2021-09-15 23:52:08.940  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
api-gateway_1  | 2021-09-15 23:52:08.997  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
visits_1       | 2021-09-15 23:52:09.373  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
vets_1         | 2021-09-15 23:52:10.105  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
vets_1         | 2021-09-15 23:52:10.966  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
customers_1    | 2021-09-15 23:52:11.240  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
vets_1         | 2021-09-15 23:52:11.440  INFO 1 --- [         task-1] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
api-gateway_1  | 2021-09-15 23:52:11.466  INFO 1 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port(s): 8080
api-gateway_1  | 2021-09-15 23:52:11.586  INFO 1 --- [           main] c.p.b.BFFApiGatewayApplication           : Started BFFApiGatewayApplication in 18.881 seconds (JVM running for 21.781)
visits_1       | 2021-09-15 23:52:11.624  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
customers_1    | 2021-09-15 23:52:12.003  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
visits_1       | 2021-09-15 23:52:12.142  INFO 1 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
vets_1         | 2021-09-15 23:52:12.232  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
vets_1         | 2021-09-15 23:52:12.529  INFO 1 --- [         task-1] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.4.18.Final
customers_1    | 2021-09-15 23:52:12.566  INFO 1 --- [         task-1] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
visits_1       | 2021-09-15 23:52:12.588  INFO 1 --- [         task-1] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
visits_1       | 2021-09-15 23:52:13.100  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
customers_1    | 2021-09-15 23:52:13.202  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
visits_1       | 2021-09-15 23:52:13.366  INFO 1 --- [         task-1] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.4.18.Final
customers_1    | 2021-09-15 23:52:13.434  INFO 1 --- [         task-1] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.4.18.Final
vets_1         | 2021-09-15 23:52:14.018  INFO 1 --- [         task-1] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
customers_1    | 2021-09-15 23:52:14.649  INFO 1 --- [         task-1] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
visits_1       | 2021-09-15 23:52:14.952  INFO 1 --- [         task-1] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
vets_1         | 2021-09-15 23:52:15.202  INFO 1 --- [         task-1] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
customers_1    | 2021-09-15 23:52:15.626  INFO 1 --- [         task-1] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
visits_1       | 2021-09-15 23:52:15.938  INFO 1 --- [         task-1] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
vets_1         | 2021-09-15 23:52:18.311  INFO 1 --- [         task-1] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
vets_1         | 2021-09-15 23:52:18.411  INFO 1 --- [         task-1] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
vets_1         | 2021-09-15 23:52:18.578  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
visits_1       | 2021-09-15 23:52:18.678  INFO 1 --- [         task-1] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
visits_1       | 2021-09-15 23:52:18.712  INFO 1 --- [         task-1] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
vets_1         | 2021-09-15 23:52:18.743  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
vets_1         | 2021-09-15 23:52:18.747  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Triggering deferred initialization of Spring Data repositories…
customers_1    | 2021-09-15 23:52:18.860  INFO 1 --- [         task-1] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
customers_1    | 2021-09-15 23:52:18.897  INFO 1 --- [         task-1] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
visits_1       | 2021-09-15 23:52:18.974  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
customers_1    | 2021-09-15 23:52:19.132  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
visits_1       | 2021-09-15 23:52:19.304  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
visits_1       | 2021-09-15 23:52:19.307  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Triggering deferred initialization of Spring Data repositories…
customers_1    | 2021-09-15 23:52:19.414  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
customers_1    | 2021-09-15 23:52:19.419  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Triggering deferred initialization of Spring Data repositories…
vets_1         | 2021-09-15 23:52:19.593  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Spring Data repositories initialized!
vets_1         | 2021-09-15 23:52:19.631  INFO 1 --- [           main] c.petclinic.vets.VetsServiceApplication  : Started VetsServiceApplication in 29.006 seconds (JVM running for 31.316)
visits_1       | 2021-09-15 23:52:20.493  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Spring Data repositories initialized!
visits_1       | 2021-09-15 23:52:20.523  INFO 1 --- [           main] c.p.visits.VisitsServiceApplication      : Started VisitsServiceApplication in 29.516 seconds (JVM running for 32.115)
customers_1    | 2021-09-15 23:52:21.007  INFO 1 --- [           main] DeferredRepositoryInitializationListener : Spring Data repositories initialized!
customers_1    | 2021-09-15 23:52:21.036  INFO 1 --- [           main] c.p.c.CustomersServiceApplication        : Started CustomersServiceApplication in 29.594 seconds (JVM running for 32.546)
`

Added .DS-STORE to the .gitignore

did what you told me either-way just incase for other underlying .DS_Store that were accidentally pushed to this branch


Improve PHPUnit fixtures and CI setting

Changed log

Add EOF (end of file) for build.yml file and composer.json file.
Add pull_request to trigger GitHub action for upcoming PRs.
According to the PHPUnit doc, it should be protected setUp(): void method.

Codecov Report

Merging #88 (4424db4) into master (663751d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #88   +/-   ##
=========================================
  Coverage     84.40%   84.40%
  Complexity      128      128
=========================================
  Files            27       27
  Lines           327      327
=========================================
  Hits            276      276
  Misses           51       51

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 663751d...4424db4. Read the comment docs.

Hey @peter279k, thanks for this first contribution to TerryApiBundle. This is highly appreciated 😃 !!! Good catch with the protected setUp(). Thank you! Best, Simon


Only the first collection by any author appears in search results

It looks like only the first collection by any author is appearing

The checkboxes should filter on the Record Type, which is at the admin level

The data appears to be all correct, but the search is simply not functioning correctly

If you look at Titles in admin and search for Comedies, histories, and tragedies (the Shakespeare collection) or The Works (the Jonson collection), you get one result for each item of those titles (instead of one result for each as Titles should work). Interestingly, in each case, the later editions are mislabeled with the date of the first edition. This also lends support to the idea that the problem with later editions of Collections, Latin plays, and some other records not appearing in search results is related to the problem with how Title level is handled in the data model

This is still not working -- just in case it's not a matter of rebuilding the database. Second edition of COmedies, HIstories, and Tragedies ought to be showing up here. Compare old and new DEEP.
Before, we were only getting the first result (Whole Contention) so something has improved. But it still is catching only the first edition of each Title per author, I think, when it comes to collections.
Screen Shot 2023-01-26 at 11.55.04 AM.pdf
Screen Shot 2023-01-26 at 11.55.54 AM.pdf

The problem here seems related to a faulty integration of Item -> Edition -> Title perhaps. When you select Record View, the other records do appear (some are variants and should indeed be excluded in Edition View, but others are genuine different Editions that should appear).
https://user-images.githubusercontent.com/40445411/214934864-587591dd-7ff5-4637-b07b-5e37956042c2.mov


Pixracer: MANUAL CONTROL LOST on param save

When landing, the flight duration param is set, leading to a param save. On pixracer, this causes a manual control loss and failsafe mode switch. The following shows the order of events (timestamps in ms), on #6901 branch:
nsh> WARN  [land_detector] param land set 24929
WARN  [land_detector] param land set 24929 done
INFO  [commander] Landing detected
WARN  [modules__systemlib] entering param_save_default 25229
WARN  [commander] MANUAL CONTROL LOST (at t=25739ms)
INFO  [commander_tests] no RC
WARN  [commander] failsafe mode on
INFO  [commander] Takeoff detected
WARN  [modules__systemlib] param_save_default done 26424
WARN  [commander] failsafe mode off

And this shows the sampling is thrown off during param save (timestamps do not match the above output):

Happens both on master (8810f70fdcf036b with nuttx semaphore patch) and with https://github.com/PX4/Firmware/pull/6901
This is not a prio inversion/inheritance problem, all task priorities stay the same. The problem is that we disable interrupts during save, apparently for too long, throwing off RC and sensor sampling, done here: https://github.com/PX4/Firmware/blob/master/src/modules/systemlib/param/param.c#L922. If I comment out this lock, the problem disappears.
@davids5 can you look into that?

@bkueng https://github.com/PX4/Firmware/pull/7036 - would you please test as suggested.

Closing as the fix was merged.


CRLF

There's a mix of CRLF in the source files which is not good... Source files usually by convention us LF, and CRLF only locally on Windows machine if git is configured correctly. Regardless, any IDE supports LF so no reason for CR.

Thanks mathieu, I have removed CR's from the sourcecode locally and will update git soon.


ERROR  Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.

Description
tried to update react-native version 0.69.1  getting this error   ERROR  Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
CodeSandbox/Snack link
NA
Steps to reproduce
No response
NativeBase Version
3.4.9
Platform

[X] Android
[x] CRA
[X] Expo
[X] iOS
[x] Next

Other Platform
No response
Additional Information
No response

Hey @harish-narra, Thanks for reporting the issue. We'll look into it.

Thanks, @ankit-tailor, if possible please look into ASAP, we are using this library, and we need to release the app with a new update without any patches. hope you understand

Hi, same error here. Is there a workaround for this?

@harish-narra you found any patch or something? this is a huge incompatibility for expo sdk 46

This bug is still there in native-base@latest and acts as a blocker for me while migrating to new architecture react-native. @ankit-tailor  Please look this.

Same issue here

Check this: https://www.reddit.com/r/reactnative/comments/11lay13/invariant_violation_viewproptypes_has_been/
My answer is the last one and worked for me as a solution.

Is this still an issue with the latest version Native Base V3.4.28?

Guys! You understand the hassle with the upgrade from v2 to v3 right? Tell me what should I do? Should I upgrade the whole app from 6 years ago manually updating latest versions of all dependencies for NativeBase to work or can I expect a new 2.x.x version to solve this issue?


Zooming in on a specified element

Possibly similar to another ticket (see description), but I cannot find it.
From Shaun Densberger: "I think a feature that'd be nice is where the zoom or rotate center is based on where the mouse pointer is currently."

We have a pick mode called "Swivel focus" that is controlled in the pick window, that causes the view to get centered on the picked point and the center of rotation to be set to the picked point. I noticed a bug that if you have panned the view, that it doesn't center the view correctly.
Here is the setting on the "Pick" window.


Manage influxDB Batches avoiding OutOfMemory Exception

Description

After a few hours running cloudstack <IP_ADDRESS> and with InfluxDB configured, CloudStack hangs due to OutOfMemoryException raised. The exception happens at com.cloud.server.StatsCollector.writeBatches(StatsCollector.java:1510):
2020-08-12 21:19:00,972 ERROR [c.c.s.StatsCollector] (StatsCollector-6:ctx-0a4cfe6a) (logid:03a7ba48) Error trying to retrieve host stats
java.lang.OutOfMemoryError: unable to create new native thread
        ...
        at org.influxdb.impl.BatchProcessor.<init>(BatchProcessor.java:294)
        at org.influxdb.impl.BatchProcessor$Builder.build(BatchProcessor.java:201)
        at org.influxdb.impl.InfluxDBImpl.enableBatch(InfluxDBImpl.java:311)
        at com.cloud.server.StatsCollector.writeBatches(StatsCollector.java:1510)
        at com.cloud.server.StatsCollector$AbstractStatsCollector.sendMetricsToInfluxdb(StatsCollector.java:1351)
        at com.cloud.server.StatsCollector$HostCollector.runInContext(StatsCollector.java:522)

Context on InfluxDB Batch: Enabling batch on InfluxDB is great and speeds writing but it requires caution to avoid Zombie threads.
Solution: This happens because the batching feature creates an internal thread pool that needs to be shut down explicitly; therefore, it is important to add: influxDB.close().
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

How Has This Been Tested?

The OutOfMemoryException happens in less than 10 hours on the staging environment.
After patching the proposed fix on the same test environment with the same workload I spend a week waiting and the exception was not thrown. All looking good with memory consumption.

@blueorangutan package

@GabrielBrascher a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✖centos8 ✔debian. JID-1830

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2585)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 40151 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4291-t2585-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Smoke tests completed. 76 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_02_vpc_privategw_static_routes
Failure
343.46
test_privategw_acl.py

test_03_vpc_privategw_restart_vpc_cleanup
Failure
240.27
test_privategw_acl.py

test_04_rvpc_privategw_static_routes
Failure
331.27
test_privategw_acl.py

LGTM, merging based on smokettests and confirmation from @wido


fix max int generation on web to use -1 >> 0

What and why?
When running flutter apps compiled to JS, 1 << 32 results in 0 instead of the max int allowed for random number generation.
How?
According to this we can use -1 >> 0 to achieve what is needed.
Review checklist

[ ] This pull request has appropriate unit and / or integration tests
[ ] This pull request references a Github or JIRA issue

Hi @a-h-mzd ,
Thanks for taking the time to create a PR.
Are you seeing something behave incorrectly? I'm pretty sure this tracer is actually only used in native platforms, not in Web where we rely on the Datadog Browser SDK's tracing implementation.

@fuzzybinary thank you for the quick response.
TracingContext.generateTracingContext is actually used by the plugins(like datadog_gql_link and datadog_grpc_interceptor). I have also created a new package which contains an interceptor for Dio based on the implementation found in datadog_gql_link. I will create a PR for it soon.

👍 I'll still have to double check that the Browser SDK doesn't handle those calls internally anyway. It would be better if we had a failing test or repro case to work from to start.

It’s actually pretty easy to test. Just try to print 1 << 32 and run the code in the browser or just compile it to JS. You’ll see that 1 << 32 is converted to 0.

Yes, I'm more referring to showing that using the grpc or gql interceptors on web does not produce the desired results. The actual feature is that distributed tracing in these packages works on web. 1 << 32 is an implementation detail and the cause of the bug.


[DRAFT 2 times slower] Multiple group by optimization

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

I plan to review this PR carefully tomorrow, as I ran out of time today

Another approach https://github.com/apache/datafusion/pull/10976 though still beaten by trivial Row approach but the time is close compare to https://github.com/apache/datafusion/pull/10937


Peer to peer code review by Team-65-The-Labradors

Peer to peer code review: Team-65-The-Labradors :service_dog:
Hello Oscar and Carlos :wave:
Great job so far, your project looks very professional and you've managed to handle eager loading very well so you should feel very proud of yourselves :medal_sports: :medal_sports:
I only have one suggestion:  to make your create method in the Event controller less crowded put the date formatting code that you have in your @event.date in a private method
That's all so far :clap:
Continue a great job :100:

Thanks for your suggestion @euqueme . We have moved the time formatting logic to a private method! :+1:
The changes can be seen here: 0176a11aff9dd764e9466fa1e721eb9e70fa74fe


FUSETOOLS2: Provide command to run camel file with JBang

WIP: need to provide tests

currently there is UI test to check the presence of new command in command palette in case the camel file is opened
to test also the command execution itself I've created https://issues.redhat.com/browse/FUSETOOLS2-2018

in the commit message, ther eis only FUSETOOLS2 without the issue number

fixed! good catch, thanks


Hotfix - Unable to use table bulk action component

Documents mentioned that we can choose a component for the table bulk action, however, that does not work because the component is hard-coded to use the update status action. This request fixes that and properly allows for the component mentioned when adding the bulk action to a table to be used.

Fixed #644

Thanks for sorting this @maurice-ellis I had a quick look and it looks good 👍  Just need @glennjacobs to have a look then we can get this merged in


Start using optimization (-O0/-O2/-O3/-Os) and debug (-g) flags from CMAKE_CXX_FLAGS_${CFLAGS_BUILD_TYPE}

I want to point out that this changes one of the optimization levels. The CMake defaults are:
CMAKE_CXX_FLAGS_DEBUG = -g
CMAKE_CXX_FLAGS_MINSIZEREL = -Os -DNDEBUG
CMAKE_CXX_FLAGS_RELEASE = -O3 -DNDEBUG
CMAKE_CXX_FLAGS_RELWITHDEBINFO = -O2 -g -DNDEBUG

While currently Swift forces -O2 on Release. So this will be a change to -O3 here.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - cb5de39c4715e9b74efed0486f80ca68b1026a41

Build failed
Swift Test OS X Platform
Git Sha - cb5de39c4715e9b74efed0486f80ca68b1026a41

@swift-ci please test macOS platform

@swift-ci please test macOS platform

@gottesmm @airspeedswift @aschwaighofer Any more feedback here? Any concerns about the switch to -O3 for Release (not for RelWithDebInfo though)?

We really need to do a benchmark run and see the impact on that.

Isn't -O3 clang's benchmarking mode? By that I mean the kitchen sink that is used when compiling . And -Os/-O2 is meant to be more sane.
What are the code size impacts of using -O3 over -Os on the c++ part of the standard library?
I seemed to remember the loop vectorizer for example inserts speculative code aggressively in the highest opt mode.

Okay, so it sounds like there are concerns. @compnerd how about I do something like:
set(CMAKE_CXX_FLAGS_RELEASE "-O2 -DNDEBUG")

to turn this PR into a NFC, and we can discuss separately whether we should switch to the CMake's default?

Ok, this is now a NFC change only.

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test Windows platform

Hm, the Windows bot failure looks like a real regression: https://ci-external.swift.org/job/swift-PR-windows/6268/console. @compnerd any ideas what's causing it?

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - cd2c471f4a18d510bd298cc6ce3ded2f3963a377

Build failed
Swift Test OS X Platform
Git Sha - cd2c471f4a18d510bd298cc6ce3ded2f3963a377

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 5066bea4330e405cade0880a5603cb3c67823d3c

Build failed
Swift Test OS X Platform
Git Sha - 5066bea4330e405cade0880a5603cb3c67823d3c

@kubamracek leaving swift at -O2 is the correct thing to do here! Thanks for keeping it like that!


CI builds fail when installing node-sass

The Netlify build for Bexar County's Storefront instance is failing with the error:
7:47:55 PM: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=12". Got "10.24.1"
7:47:55 PM: error Found incompatible module.

For a sample failing build see: https://app.netlify.com/sites/bexar-food/deploys/62b1150a446d523ba2d29f5a
Cloning this locally to see if I can reproduce, and will likely upgrade node-sass.

Checked out this repo out locally and ran through the setup notes in README.md. Got an error:
Failed to compile.

./src/index.scss
Node Sass version 6.0.1 is incompatible with ^4.0.0 || ^5.0.0.

Per this SO post, swapped out node-sass in favor of sass. The build script seems to be running now 🎉

Still getting the same Netlify error. It seems to be happening because Netlify is building using Node 10.x and both node-sass and sass expect at least 12.x. Per the Netlify docs, created a .nvmrc file pegging Node to 16.x (current active LTS).

The Node version error seems to be resolved.  See here for a sample failing build.
Disabling all linting for now; most of the errors seem to be minor/style-related. Not sure how this code base was passing previously 🤷


cmd/go: build with vendor fails when go.mod doesn't record dependencies

What version of Go are you using (go version)?

$ go version
go version go1.17 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/william/.cache/go-build"
GOENV="/home/william/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/william/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/william/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17"
GCCGO="gccgo"
AR="ar"
CC="x86_64-pc-linux-gnu-gcc"
CXX="x86_64-pc-linux-gnu-g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build78892724=/tmp/go-build -gno-record-gcc-switches"

What did you do?
$ git clone https://github.com/energicryptocurrency/energi3.git
$ cd energi3
$ git checkout v3.0.8
$ go build ./cmd/geth
What did you expect to see?
Successful build of the geth binary
What did you see instead?
$ go build ./cmd/geth
go: updates to go.mod needed, disabled by -mod=vendor
        (Go version in go.mod is at least 1.14 and vendor directory exists.)
        to update it:
        go mod tidy

Then, go mod tidy doesn't update anything.
This builds with go 1.16.x, so something changed in 1.17. I don't know if it is a bug in Go or something needs to be changed in the package.
Thanks much for your time.
Cc: @candrews

That go.mod doesn't look right, it doesn't actually list any dependencies.
go mod tidy fails due to incompatible version upgrades because the go.mod doesn't actually record any info about dependencies.
go 1.15

module energi.world/core/gen3

Not sure if this is a supported way of doing things?
cc @jayconrod @bcmills @matloob

originally reported at https://bugs.gentoo.org/808829
I've also reached out to the energi3 developers via email at<EMAIL_ADDRESS>

I think this is working correctly. 1.16 should have reported an error. vendor/modules.txt must be consistent with go.mod, and here, the requirements aren't listed in go.mod at all.
go mod tidy can generally fix problems like this, but here, it reports an error:
energi.world/core/gen3/cmd/geth imports
        github.com/gizak/termui: module github.com/gizak/termui@latest found (v3.1.0+incompatible), but does not contain package github.com/gizak/termui
energi.world/core/gen3/internal/build imports
        github.com/Azure/azure-storage-blob-go/2018-03-28/azblob: module github.com/Azure/azure-storage-blob-go@latest found (v0.14.0), but does not contain package github.com/Azure/azure-storage-blob-go/2018-03-28/azblob
energi.world/core/gen3/node imports
        github.com/prometheus/prometheus/util/flock: module github.com/prometheus/prometheus@latest found (v2.5.0+incompatible), but does not contain package github.com/prometheus/prometheus/util/flock

Since there aren't any pre-existing requirements, go mod tidy will look up the latest version of each module to try to satisfy imports. From the errors, it sounds like those packages have been deleted upstream.


Update try-v3-python-sdk.md

Fixed indentation which caused error
"document_analysis_client = DocumentAnalysisClient(endpoint=endpoint, credential=AzureKeyCredential(key))
IndentationError: unexpected indent"

@laujan,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.
#label:"aq-pr-triaged"


Bug fix: make dismiss during export not fire success toast

Fixes #3542 by moving the toast firing logic out of the ModelingMachineProvider and into the export helper functions. We can do this thanks to react-hot-toast's helpfully React-agnostic API, and exportMake was already doing this to fire custom toast.error's. By doing this, we can simply dismiss the toast on cancellation during desktop export.
Demo
https://github.com/user-attachments/assets/bf2f98d6-f7f9-412f-af12-78118c1c544d

Need a bit of tweaking to make playwright tests behave nicely

Need a bit of tweaking to make playwright tests behave nicely

I guess that makes sense, the toast sits there for slightly longer now right?

Makes me think if this should even be time-based, or any of our modals. What if the user misses it while they are away? A modal should be an occasional occurrence, right? Having the user dismiss could have benefits.

Makes me think if this should even be time-based, or any of our modals. What if the user misses it while they are away? A modal should be an occasional occurrence, right? Having the user dismiss could have benefits.

It's a good thought. I think having some toasts require dismissal is a good idea, but I do believe some are just like yeah you successfully did the thing, such as changing a setting, that I don't think we'd want to require a click to dismiss.
If we made the toasts smaller/more subtle, I think we could have the timer on them a fair bit longer, and show a loading bar for how much longer it'll appear. I think Sanity does this well, I could get a video of it at some point.

Good lord finally, my CI struggle has been real


UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 4823: character maps to

Hi, correctly installed swift and would like to launch the UI, when after enter swift web-ui I get this error : UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 4823: character maps to <undefined> Any solutions please ?

If you are not using the eval page, try to uninstall evalscope please.


Issue https://gitcoin.co/tranvanlap95: 1. Open 2. Started 3. Submitted 4. Done

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 33083.0404 XTZ (121414.76 USD @ $3.68/XTZ) has been submitted by:

@jojo0-07
@tranvanlap95
@faithful1ofall

@jantinine please take a look at the submitted work:

PR by @faithful1ofall
PR by @tranvanlap95
PR by @jojo0-07

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$3,645,302.01 more funded OSS Work available on the Gitcoin Issue Explorer

Originally posted by @gitcoinbot in https://github.com/tezos-contrib/gitcoin-bounties/issues/1#issuecomment-900682083

https://gitcoin.co/tranvanlap95


Refactoring

!!! This PR is a draft DO NOT MERGE IT !!!
Refactoring...
Today Changelog (Main changes)

Add Test.gd
Start splitting definitions in values and glossary
Start removing use of loading files everytime (cost a lot)
Start removing use of folder structure file

EditorView.gd

Add class_name to use autocompletion
Add res_values directonary (contain editor's dialogic_values)
Add save_button (the greatest one, in futur add shortcut too)

MasterTree.gd

Add values_tree
new funcs to create trees and items
Disable renaming item for now

ValueEditor.gd

Renaming just when press enter

DialogicResources.gd

Add const working_dirs and cgf_files to increase perfomance and remove func get_working_dirs and get_cfg_files (call to func cost)
Move init_dialogic_files in dialogic.gd (call to func cost)
Add funcs to load and save values.json

Hey @theludovyc, thanks for your contribution. I know this PR is not finished but here are some tips from me:

please try to make your PR's as small as possible. If there are two seperate things to be done, do two PR's. This will highly increase the chances of your PR getting merged and not being stopped by one of the implementations being not finished or not how it's wanted.
Another good thing is, to first name the problem and then discuss it. If you don't do it there is a high chance of you doing a lot of work just to find out, we discussed that before and decided otherwise. If you want to help, that's super cool. Either explain the problems you see in the PR or create issues for them before or join emilios discord to have a discussion about it.

While I like some of the changes you made, there are others where we already decided against. One is the use of match where it is not necessary. As it seems, match is slightly slower then a series of if statements (in godot), and it often even doesn't make things shorter.
Anyways, I look forward to you contributing to this plugin. Just wanted to give you these tips, before you put in a lot of effort.

"As it seems, match is slightly slower then a series of if statements (in godot), and it often even doesn't make things shorter." I look at it. If it's true, it's really serious.

"please try to make your PR's as small as possible. If there are two seperate things to be done, do two PR's. This will highly increase the chances of your PR getting merged and not being stopped by one of the implementations being not finished or not how it's wanted."
I made a huge refactor and split it when you like something. See the changelog and sources :) !

It is true. It was confirmed by the devs. It is a small difference, but there is. Not a big deal though.

"Another good thing is, to first name the problem and then discuss it. If you don't do it there is a high chance of you doing a lot of work just to find out, we discussed that before and decided otherwise. If you want to help, that's super cool. Either explain the problems you see in the PR or create issues for them before or join emilios discord to have a discussion about it."
Ok, i'm coming on the discord :)

It is true. It was confirmed by the devs. It is a small difference, but there is. Not a big deal though.

It's a big deal, beacause in any languages, match(switch) is there to increase performance and simplify code.
I'm sad to hear that.

I believe the issue is that the match statement also compares type. I'm sure it will be faster in the 4.X branch with the new GDScript, but even if so, the increase in performance in such a small if/elif/else statement vs a match is negligible.


Delegate move events

Create touch event listeners within MapController class
Fix map scrolling.

This request solves #13


Issues with the Erase shard

Describe the bug

Issue 1: Erase gives an error if the input to it doesn't match the data structure of its :Name entity or the indices/keys passed to it.
Issue 2: When erasing elements from a sequence Erase gives an error if the indices sequence is not in descending order

To Reproduce
Issue 1
{:k1 100 :k2 200 :k3 300} >= .tab
"Hello World"
(Erase ["k3" "k1"] .tab)
;; => [error] [2022-07-13 21:36:34.538] [T-10164] [runtime.cpp::1090] Error composing shard: Erase, invalid indices or malformed input., wire: main

Issue 2: case 1 (indices sequence sorted in ascending order)
[10 20 30 40 50] >= .seq
(Erase [1 2 3] .seq) ;; indices sorted in ascending order => error
;;[error] [2022-07-13 21:46:33.026] [T-16264] [runtime.cpp::791] Shard activation error, failed shard: Erase, error: Comparison < between two different value types

Issue 2: case 2 (indices sequence randomly sorted)
[10 20 30 40 50] >= .seq
(Erase [3 1 2] .seq) ;; indices sequence randomly sorted
.seq (Log) ;; .seq incorrectly filtered => [10, 30] ; expected .seq => [10, 50]

Expected behavior

Issue 1: Erase should not validate the input as it does not use the input value for processing.
Issue 2: Erase should work correctly for  indices sequence sorted by ascending order (case 1) as well as sorted randomly (case 2)

😭😭 @satendrapalsingh .
Erase USES Input, it manipulates INPUT

Skip this block for now as it's confusing me 😄
Will try to review this soon.

Skip this block for now as it's confusing me 😄 Will try to review this soon.

Yeah, sure - no worries!

Hey team! Please add your planning poker estimate with ZenHub @inabe-a @Kryptos-FR @sinkingsugar


Tutorial page is offline

Sorry for using the issues page to report this but the page where the tutorial was hosted has been offline for a few days.

Hi Rodrigo.
Thank you for letting me know. I wasn't aware of the problems with XamarinExpert and MauiExpert.
Problems with the hosting provider. It's all solved now and the websites and the guides are available again.
Closing this issue.


Develop Analog pin interface for beaglebone black

Since we have a smaller list of analog i/o for the solar car, we will not be using an external ADC. This means that all of our analog inputs will be used to read i/o instead. This task focuses on developing an interface for us to read these pins in our main program.
The raw values can be read from /sys/bus/iio/devices/iio:device0/in_voltage<pin>_raw
There are 7 total analog pins on the beaglebone black.
The BBB adc has a range of 1.8V and is read as a 12 bit number.
We will also need to account for a scaling factor that will be determined by low voltage

This was tested successfully


Reproduce CoH on alpaca

Thanks for this great work first! And I am trying to reproduce CoH on alpaca model, so if it is necessary for me to have the access to the Jax weight of alpaca first?

You will need an initial model to begin with, e.g. a LLaMA or alpaca model.
For training CoH using this Jax codebase, you can use coh/scripts/convert_checkpoint.py to convert PyTorch weights to Jax format.
If you would like to use PyTorch training codebase (e.g. FastChat), you can use coh/data/pack_hf.py to pack human feedback data into CoH format.


Quality selection

Hello!
When will be make "quality selection"? And if it is't realized in the code  tham how to play HD quality video?

[x ] Issue does not already exist
[ ] Issue observed on https://plyr.io

Environment

Browser: Opera
Version:  last
Operating System: Win
Version:  10

Players affected:

[ ] HTML5 Video
[ ] HTML5 Audio
[x ] YouTube
[ x] Vimeo

In progress already.

But how can play in HD quality in tcurrently version? May I canged it in code manualy?

Too hard to explain here or I’d have released the feature already?

Ok. will be wait! Thank you for great web app!


Subsetting (partially) outside the coverage's extent

20200902: Coverages SWG call:
Factoring out from https://github.com/opengeospatial/ogc_api_coverages/issues/84
Use case: Fill a GeoPackage from Coverages API with coverage tiles
Proposal: Allow subsetting outside of the extent/domainSet of a coverage and document the options, potentially make a recommendation but don't mandate one or the other.
Options are:

Recommended: Fill the extent with no-data values at least for partially outside requests
Respond with an http error 501 "Not implemented"
Not recommended: Respond with a subset that is smaller than the requested one

This partly addresses https://github.com/opengeospatial/ogc_api_coverages/issues/27 (although a Tiles API may also be another mechanism).

20200907: Coverages SWG call: Decided to relax the requirement of WCS 2 that the min and max values used with the subset parameter have to be contained within the axis range defined in the domainSet. A partially outside subset should be filled with no-data values whereas a fully outside subset should return with http status code 204 (cf. https://github.com/opengeospatial/OGC-API-Tiles/issues/21).

I believe the changes have been applied and merged and this issue can now be closed.

Coverages SWG call: Agreed to close.


position adjustment for icon button on appbar

Am I the first one find it out?
v1-beta2 AppBar
If there is an icon button on the left the title, the icon button margin-left is large than margin-top and margin-bottom.
I don't know if it is a issue.

Duplicate of #7517


Publication logo size issue

MY LOGO dimensions are 600x72px but stil it looks very small!

That was already discussed here: https://github.com/eddiesigner/liebling/issues/233
You can inject the following code in the Ghost Admin:
<style>
.m-logo {
	height: 25px; /* Change the height as you prefer */
}

.m-logo img {
	max-width: 150px; /* Change the max-width as you prefer */
}
</style>

Btw, I wouldn’t recommend to use a logo of that size. it's just too big, it won’t look good.


Question about isContainerBucketRoot()

@igorpisarev @axtimwalde @constantinpape
I am trying to use your new version of this library and have some issues.
Here:
https://github.com/saalfeldlab/n5-aws-s3/blob/master/src/main/java/org/janelia/saalfeldlab/n5/s3/N5AmazonS3Reader.java#L209
There has been this added:
&& (isContainerBucketRoot() || exists("/"))

Could you  please explain what that does and what the purpose is?
This evaluates to false for us in this case:

where key is what you are calling containerPath.
The other issue that the call exists("/") in above line internally calls s3.listObjectsV2(listObjectsRequest) which, for us, takes forever to complete (many seconds, sometimes fails with timeout); not sure why. Do you know what the listObjectsV2 call is doing?

Thanks for reporting this.  To me this looks as if that needs fixing.  How do you create the N5AmazonS3Reader?
is key meant to be the containerPath or do you double use it as a dataset?  "/" datasets are legal but considered a bit of an edge case that we haven't tested much.  I could imagine that, if this is how you use N5, you are listing into a dataset which will take a while because it would have to filter through all the block subdirectories.  A quick fix for this would be to test datasetExists first?  @igorpisarev has moved on to a new job and I am not sure if he is still following this.  Can you detail your application a bit more?

I create like this:
new N5AmazonS3Reader( s3, bucketName, key )

with, e.g.
bucketName = "platyBrowser"
key = "rawdata/sbem-6dpf-1-whole-raw.n5"

I am not sure about our data structure beneath, but @constantinpape can probably tell.

you are listing into a dataset which will take a while because it would have to filter through all the block subdirectories.

Does that mean that this
final ListObjectsV2Request listObjectsRequest = new ListObjectsV2Request()
				.withBucketName(bucketName)
				.withPrefix(prefix)
				.withMaxKeys(1);
final ListObjectsV2Result objectsListing = s3.listObjectsV2(listObjectsRequest);

interprets the / slashes in the keys as directories and then goes into them? I always thought object stores do not have a folder structure? If that's the case maybe we should reconsider the whole code in exists( pathName )?

What is your definition of a "dataset" vs. "containerPath==key"?
I have the feeling we are using them as synonyms, maybe you had something else in mind?
I think the way we are currently using the API this makes not much sense: https://github.com/saalfeldlab/n5-aws-s3/blob/master/src/main/java/org/janelia/saalfeldlab/n5/s3/N5AmazonS3Reader.java#L385
because it would always be false.
Sorry, I need to call it a day for now, can work more on it tomorrow!

Hi @tischi, @axtimwalde,
looking at the code now, I remember that it would check the container version only if it's a non-empty directory tree. isBucketContainerRoot() was thought to be a special case when a bucket is itself an N5 container (i.e. attributes.json is hosted at the root of the bucket).
I'm also not sure anymore if this check is really needed, you can try to simplify or remove it and validate with unit tests, they should cover everything pretty well.
There was another consideration for the case when the constructor of N5AmazonS3Reader is called as a result of creating an instance of N5AmazonS3Writer, and because it's a superclass, the constructor of the reader runs before the constructor of the writer, so the container may not exist yet. The unit tests also cover this.
That said, I'm not sure why it evaluates to false in your case -- perhaps there is indeed a bug somewhere. Hope the above helps to figure it out! As @axtimwalde mentioned, I've recently left Janelia and will not be involved in modifying this code.

What is your definition of a "dataset" vs. "containerPath==key"?
I have the feeling we are using them as synonyms, maybe you had something else in mind?

These are actually a bit different: containerPath is a path to the root of the N5 container in the given bucket, while dataset is another path within the N5 container to an N5 dataset (a group with valid dataset attributes).
In your example, rawdata/sbem-6dpf-1-whole-raw.n5 is correctly a container path, and setup0 could be a dataset (depending on the contents of its attributes.json).

only if it's a non-empty directory tree

I think that's fine in theory, but in practice this call s3.listObjectsV2(listObjectsRequest); seems not performant.
I could be we would need another way to figure out whether a path exists.

@constantinpape Where do we currently specify the version (I guess that's a small file called version or something)? For each dataset or only at the bucket root? I guess we should have it for each dataset, right?

Where do we currently specify the version (I guess that's a small file called version or something)? For each dataset or only at the bucket root? I guess we should have it for each dataset, right?

Are you referring to the n5 version?
Each dataset (=each file with '.n5' extension) has it stored in the root level in the attributes.json. See the n5 specification point 3.

@axtimwalde
For us, it works to simply remove the additional checks. I created a PR for this: https://github.com/saalfeldlab/n5-aws-s3/pull/9
Would that work for you or do you think they are needed?

Are you referring to the n5 version?
Each dataset (=each file with '.n5' extension) has it stored in the root level in the attributes.json. See the n5 specification point 3.

Each N5-container has one n5 attribute in its root group.  An N5-container is NOT a dataset, it can be a dataset if it has only one dataset whose name is "" or "/".  Datasets are the chunked n-dimensional data, they are also groups in how they have attributes but they can not contain other groups.  So the above statement is confusing and partially wrong.

Datasets are the chunked n-dimensional data, they are also groups in how they have attributes but they can not contain other groups. So the above statement is confusing and partially wrong.

Yes, you are right. I am mixing up the terms here because in our use-case we always only have a single dataset per n5 container so we tend to use the terms as synonyms.
I will update my comment to make that clear.

Great!  Unrelated to this issue which I consider fixed by @tischi's pull request, do you think that this is good practice?  We made N5 a container format, so datasets can be hierarchically sorted inside the container.  This is also why we started AWS-S3 and Google-Cloud support with bucket==container, because we assumed that you can pack everything you want into the hierarchy of a container.  Of course this does not include any non-N5 files if you have any...

I agree, the single dataset per container is not good practice in general.
For the project at hand, we started out with the bdv.hdf5 format which only supported up to 100 setup ids per file, which was not sufficient for us, and @tischi wrote a gui on top of bdv to deal with multiple files. We have switched to the bdv.n5 format now, which would allow for an unlimited number of setup ids, but haven't switched this layout, because this would require some changes in the gui and there is not really an obvious mapping of datasets to setups.

@axtimwalde
Yes all of this is historical as we came from bdv.h5 where having everything in one giant h5 file has, imho, a couple of disadvantages, including the difficulty of parallel writing into it.
Now, using n5, what do you think should be best practice?
one container (OC)
Using only one bdv.n5 container would look like this, right?
myProject.n5
  /setup0
  /setup1
  ...

multiple containers (MC)
What we do looks like this:
myProject
  /em-raw-highres.n5
  /geneXYZ.n5
  /geneABC.n5

At first glance MC seems to have the advantage that one can immediately, from the container names, get a sense of the data that's in there. While for OC one would have to go into the attributes.json to get more information on the data content, right? Working with biological end-users on a daily basis I made the experience that it is useful if there is  information in the "filenames".
Also, the way BigDataViewer currently works, it would open all the setups at once, which could be slow, overwhelming, and would explode its brightness and contrast UI which used to be limited to 10 setups (this should now be better since version 9.*, but I have not tested it yet).
But those are not very strong arguments. I would be curious what you think are the main advantages of having everything in one container?

If your intention is to make each container a BDV project, then MC makes most sense, and there is nothing wrong with that.  I was assuming that you have some custom structure that you open with a dedicated frontend that uses bigdataviewer-vistools to display a bunch of sources.  That would also free you from the setup naming convention and allow arbitrary human readable names.  We are currently working on making the n5-viewer plugin more flexible so you can do exactly that, open arbitrary single- or multi-scale datasets from arbitrary locations in an N5 container.  Late for your launch I guess :).

We are currently working on making the n5-viewer plugin more flexible so you can do exactly that, open arbitrary single- or multi-scale datasets from arbitrary locations in an N5 container.

This sounds good and is indeed what I would need to make the OC version work for me.
Frankly, I have never tried the n5-viewer. Could you briefly describe what the differences are and why it was necessary to branch from the normal bigdataviewer?

N5-viewer was created when we had just created the first N5 draft and BDV proper was unaware of it.  Its purpose was to visualize large multi-scale exports of cloud-stitched multi--channel LLSM data.  It also has a crop tool which is handy for users in Fiji who want to work on some Fiji-size crop from the large volume.  It is BDV with other assumptions about the source format and other sources, and also a crop tool.  We are currently generalizing this into an all purpose N5 viewer which includes HDF5, Zarr and the cloud backends supported through the N5-API.


Running Windows containers? Or Linux containers? Confused

When specifying vmImage: 'windows-latest' as the build pipeline agent, I was half expecting the image to be running Linux containers.
But it is fails:
failed to build: image operating system "linux" cannot be used on this platform

Digging about the documentation, I can't seem to find a vmImage that has a Windows agent host, but is running Linux containers. As this is my desktop experience, I was kind of half expecting a prebaked build agent image to do the same?
As per this article:
> By default, Docker for Windows is configured to use Linux Containers.
As per this article:
> You must specify "Hosted Ubuntu 1604" as the pool name in order to run Linux containers. Other pools won't work.
Would help if it was a bit clearer.

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

ID: b31d4f6c-d16d-2ba1-1294-6aa94e328046
Version Independent ID: 88aec599-4410-697d-1002-1c41b1c17bb6
Content: Running a self-hosted agent in Docker - Azure Pipelines
Content Source: docs/pipelines/agents/docker.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliobbv
Microsoft Alias: juliobv

@thomps23 @steved0x Please re-assign.

Also including @mijacobs

@azooinmyluggage This is the issue I referenced. I'm running into the same issue as the customer during testing.

Windows containers will only run on a Windows vmImage. I'm updating the article.


Inconsistent output of mitochondrial SNPs in Ancestry/23andme merge

Ancestry reports mitochondrial (MT/Chr26) SNPs as diploid (e.g. "GG", with two identical alleles), even though there is just one mitochondrial genome, with multiple copies. 23andme reports as haploid (e.g. "G"). When 23andme and Ancestry files are merged in lineage, the csv output has a single allele for all 23andme SNPs but two alleles for any that are present on Ancestry (including SNPs present on both).
Suggest that, for consistency, all MT SNPs be reported with a single allele, and any heterozygosity in Ancestry calls (due to heteroplasmy, which I've never yet seen) be reported as an error.

Like deduplicate_XY_chrom, this could be addressed in a similar manner with deduplicate_MT_chrom (new parameter to SNPs).


move release build details from Dockerfile to Makefile

so they can be used more easily for other binary release like brew
https://github.com/Homebrew/homebrew-core/pull/26653#issuecomment-391075797

started, it’s cleaner except for the flag passing doesn’t quite work from Makefile yet

brew change: https://github.com/Homebrew/homebrew-core/pull/29091


Fix SSO; fix JS errors on login page; fix method name error

Fixing a few issues found during testing. See comments in code for details.

@rob3000 - Can you take a look at this and make sure everything looks good? Tagged you on a specific change that I wasn't sure works or not. Ran vendor/bin/phpcs modules/auth0/src --standard=Drupal and only saw the one error for verify_email


[Feature request] - Map View query mechanism should be able to filter by properties

As I mentioned in #255, I think it would be very useful to allow queries such as [propertyname:propertyvalue] in the Map View Filters section. It should be in a way that resembles the Obsidian query syntax, so, e.g., if property foo has value [[Bar]] or a list of values, one of which is [[Bar]], then [foo:Bar] should consider it.
If this is too much to implement, perhaps it would be easier to allow linkedto: to also read from property values (e.g., if the property foo has value [[Bar]] or a list of values, one of which is [[Bar]], then linkedto:"Bar" should consider it.

@esm7 Would you be open to a PR here? I put together a quick hack that seems to work: https://github.com/esm7/obsidian-map-view/compare/master...zakj:obsidian-map-view:property-queries. Looks like I'd also need think about updating the query suggester.

Would definitely love a PR here. I'm unsure about the most suitable syntax that would be both consistent with the rest of the Map View queries and how Obsidian properties work. I understand you went for a syntax of the form [property:value], I never used these searches in Obsidian but it seems like Obsidian supports (and suggests by default to use) quotes -- ["property":"value"], I think it should at least be supported even if not the default.

Yes, Obsidian uses quoted property name or value to indicate an exact match—unquoted name or value can partially match. I'll factor that into my implementation.


Pawn hopping over pieces on file 3, to file 4 is not a legalMove.

method legalMoves is incorrectly implemented.
Consider position:
1st move for white: Na3
2nd move for white: a4 <- is not a valid but is provided as a legalMove from legalMoves.
Same issue exists for all pawns, pawns seem to be able to hop past pieces on file 3 to file 4.
For example: d4, d5; Qd3, c5; Qf3 cxd4; !!!f4!!!! illegal move.

Oh yeah that's a big miss, looks like the pawn moves doesn't account for pieces in the way when they're first starting out so I'll implement a fix.
Thanks for reporting that!

In case someone wants to generate all possible moves on top of your package in san (along with promotion) here's a dirty implementation with the bug fix:
func CKS_GenerateAllValidNotations(isBlack: Bool = false) -> [String] {
var notations:[String] = []
let targetColor: Piece.Color = isBlack ? .black : .white
    board.position.pieces.forEach { piece in
        var tempboard = board

        // Temp bug fix.
        if piece.color == targetColor {
            if targetColor == .white {
                if piece.kind == .pawn {
                    if piece.square.rank == 2 {
                        //let intermediateSquare = Square(file, 3)
                        if tempboard.position.piece(at: piece.square.up) != nil {
                            return
                        }
                    }
                }
            } else {
                if piece.kind == .pawn {
                    if piece.square.rank == 6 {
                        //let intermediateSquare = Square(file, 3)
                        if tempboard.position.piece(at: piece.square.down) != nil {
                            return
                        }
                    }
                }
            }

            let legalMoves = tempboard.legalMoves(forPieceAt: piece.square)

            for legalMove in legalMoves {
                // Attempt the move on a copy of the board
                var boardCopy = tempboard
                guard let move = boardCopy.move(pieceAt: piece.square, to: Square(legalMove.notation)) else {
                    continue
                }

                // Check if this move requires promotion
                if shouldPromote(piece: piece, endSquare: Square(legalMove.notation)) {
                    // Try all promotion possibilities
                    for promotionKind in [Piece.Kind.queen, .rook, .bishop, .knight] {
                        var promotionBoard = boardCopy
                        let promotedMove = promotionBoard.completePromotion(of: move, to: promotionKind)
                        notations.append(promotedMove.san)
                    }
                } else {
                    // Normal move (no promotion)
                    notations.append(move.san)
                }
            }
        }
    }
    return notations
}

private func shouldPromote(piece: Piece, endSquare: Square) -> Bool {
    // Determine if a pawn is reaching the last rank
    // White pawns promote when reaching rank 8, black pawns promote when reaching rank 1
    return piece.kind == .pawn && ((piece.color == .white && endSquare.rank == 8) || (piece.color == .black && endSquare.rank == 1))
}


add https://github.com/lenvm/SercomSPISlave update

Updated library name to a name without spaces

With this PR I would like to ensure the latest version with the updated name will be available in the Library Manager.

OK @lenvm. We have now updated the name as requested. It should be available from Library Manager within a day.
You can continue to monitor your library's indexing logs at the same URL as before:
http://downloads.arduino.cc/libraries/logs/github.com/lenvm/SercomSPISlave/
They are currently outdated, but will be automatically updated to reflect the name change after the next time the scheduled job runs.


[Extension] Added Hide label btn in user preferences

Description

Added Hide label in user preferences

Signed commits

[x] Yes, I signed my commits.

@NikhilSharma03 please close when this has transitioned to the remote provider.

@leecalcote I think I am a bit confused here. That is if we want to land that Hide Label Button here in user preferences

Then we have to made those changes here in meshery repo where UserPreference.js file resides.
If we want all changes in remote provider then the Hide Label Button button should reside in MeshMap then.

@NikhilSharma03 be sure that you follow up with @Abhishek-kumar09


docs: outdated palenight upstream link

The link to the upstream link is outdated

[X] I searched the issue tracker and this hasn't been PRed before.
[X] My changes are not on the do-not-PR list for this project.
[X] My commits conform to Doom's git conventions.

Should we use this instead https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you ?


Cherry-Pick Skill Validation to 4.7 (#1375)

This was force pushed due that only fails in 3.8 (not specifically supported at that time) and fails on tests that has nothing to do with this change.


[Component Proposal] usePopoverPosition - hook to improve contextual awareness rendering for tooltip, flyout, etc

This is a proposal for a hook or wrapper component that can be used to detect proximity to window edge in order to handle replacement of "pop in" elements like tooltip or overflow menus.
This could calculate children size and its placement on window. If children/component ref go off window we need to feed back the information to the children/component ref that will allow them to reposition themselves using the props available from Carbon.
Is complete when:

[ ] Hook or wrapper component that can calculate placement logic
[ ] Update "pop in" components to use hook/wrapper internally behind a prop to handle positioning for downstream consumers:

[ ] Tooltip
[ ] Overflow
[ ] Flyout

This will additionally need to support the Flyout, which is a Tooltip under the hood #1266

This will fix #802

An alternative to placing this behind a prop would be to export the hook and allow consumers to compose it together themselves as needed. It may only support certain components though (tooltip, flyout, etc) so documentation will be important.

A couple layout positioning specs from @lukefirth originally from the Flyout spec https://github.com/carbon-design-system/carbon-addons-iot-react/issues/1266:


Android Basics: SQL Basics

Downloaded the project and imported to android studio as instructions indicate , but project refuses to build with a " Failed to find Build Tools revision 30.0.3" what does this mean for me ?

Did you check if all your SDK is up to date?

Did you check if all your SDK is up to date?

It works fine now. Thanks


Link to External Pages with Anchor Elements

Challenge Link to External Pages with Anchor Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

Please provide details in comments below for the exact issue you are facing to re-open.
Please consult the Help Chat Room for any assistance to Coding.
Happy Coding!


chore: make instSMulRealComplex scoped

This scopes and moves to Complex.SMul the instance instSMulRealComplex.
Rationale: This instance is used in Data.Complex.{Basic|Module} to bootstrap SMul instances from the reals, but afterwards, instances SMul R ℂ should not need to rely on that (rather be obtained via Algebra R ℂ, for example). This speeds up the two mentioned files a bit and does not seem to have any adverse effects.
See here on Zulip.

!bench

Does scoping an instance actually do anything?

Does scoping an instance actually do anything?

Yes:
import Mathlib

variable (a b : ℂ)

#check a ≤ b -- failed to synthesize instance LE ℂ

open scoped ComplexOrder

#check a ≤ b -- a ≤ b : Prop

I had a previous experiment where I tried to retroactively scope some parent projections which didn't work. But the problem was the instance erasure and not the scoping.
I think scoped instances are a very good idea as another lever to guide typeclass synthesis.
bors merge


Fix FR inverse function and add test case

Hello, I am using this library for implementing threshold encryption.
I need to get inverse of some FR element, but I experienced infinitely loop in inverse().
so I modified logic for getting inverse, and I got a result what I want.
Please review my code.
Thank you for good library. :-)

Looks good! Thank you for the contribution!


⚠ ClamAV has degraded performance

In 7242b2f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in c64e77b.


Contribute

HTML, CSS and Javascript / React.js

Got it ready but need to get write permissions enabled for the repo


Atom doesn't run after november Windows 10 update...

Atom was working fine, windows was working fine.. until an automatic update of windows 10 last night. It messed up not only my task bar (which is fixed now by booting in safe mode), but Atom is still a mess.. All I get is a blank window with the path to the file I tried to open. Re-install doesn't fix the problem, neither does running Atom with a previous windows' settings. Did anyone else encounter similar problems or might have an idea on how to get things working properly again?

OK, apparently clicking on the empty window out of frustration directs you to where you want to be :) However, you must really want it and hold that thought only lightly in your head.