To Reproduce
Steps to reproduce the behavior:
1.Spin up the client
Expected behavior
With version 1.14.0-SNAPSHOT, the members can be output to the console.
With version :2.0.0-SNAPSHOT and new configurations, with the same stream I got:
2024-02-14 20:31:28 _ ___ ___ ___ _ _ _
2024-02-14 20:31:28 | | | \ |_ _| o O O / _ \ _ _ __ | |_ ___ ___ | |_ _ _ __ _ | |_ ___ _ _
2024-02-14 20:31:28 | |__ | |) | | | o | (_) | | '_| / _| | ' \ / -_) (_-< | _| | '_| / _` | | _| / _ \ | '_|
2024-02-14 20:31:28 |____| |___/ |___| TS__[O] \___/ _|_|_ \__|_ |_||_| \___| /__/_ _\__| _|_|_ \__,_| _\__| \___/ _|_|_
2024-02-14 20:31:28 _|"""""|_|"""""|_|"""""| {======|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|_|"""""|
2024-02-14 20:31:28 "`-0-0-'"`-0-0-'"`-0-0-'./o--000'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'"`-0-0-'
2024-02-14 20:31:28
2024-02-14 20:31:28 Version
2024-02-14 20:31:28 Powered by Spring Boot 3.1.3
2024-02-14 20:31:28
2024-02-14 20:31:29 2024-02-14T19:31:29.016Z INFO 1 --- [ main] b.v.i.ldes.ldio.Application : Starting Application using Java 17.0.10 with PID 1 (/ldio/ldio-application.jar started by ldio in /ldio)
2024-02-14 20:31:29 2024-02-14T19:31:29.024Z INFO 1 --- [ main] b.v.i.ldes.ldio.Application : No active profile set, falling back to 1 default profile: "default"
2024-02-14 20:31:30 2024-02-14T19:31:30.955Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2024-02-14 20:31:30 2024-02-14T19:31:30.968Z INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2024-02-14 20:31:30 2024-02-14T19:31:30.969Z INFO 1 --- [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.12]
2024-02-14 20:31:31 2024-02-14T19:31:31.047Z INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2024-02-14 20:31:31 2024-02-14T19:31:31.048Z INFO 1 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1930 ms
2024-02-14 20:31:32 2024-02-14T19:31:32.193Z INFO 1 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator'
2024-02-14 20:31:32 2024-02-14T19:31:32.284Z INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2024-02-14 20:31:32 2024-02-14T19:31:32.385Z INFO 1 --- [ main] b.v.i.l.l.config.MemberSupplierFactory : Starting LdesClientRunner run setup
2024-02-14 20:31:32 2024-02-14T19:31:32.385Z INFO 1 --- [ main] b.v.i.l.l.config.MemberSupplierFactory : LdesClientRunner setup finished
2024-02-14 20:31:32 2024-02-14T19:31:32.392Z WARN 1 --- [ main] b.v.i.l.l.config.MemberSupplierFactory : Version-materialization in the LDES Client hasn’t been turned on. Please note that in the future, this will be the default output of the LDES Client and having version-objects as output will have to be configured explicitly.
2024-02-14 20:31:32 2024-02-14T19:31:32.399Z INFO 1 --- [ main] b.v.i.ldes.ldio.Application : Started Application in 3.853 seconds (process running for 4.338)
2024-02-14 20:31:32 2024-02-14T19:31:32.400Z WARN 1 --- [pool-3-thread-1] b.v.i.ldes.ldio.LdioLdesClient : No fragments to mutable or new fragments to process -> LDES ends.
Pre-requisites: ldes/ldi-orchestrator:2.0.0-SNAPSHOT With following configuration:
To Reproduce Steps to reproduce the behavior: 1.Spin up the client
Expected behavior With version 1.14.0-SNAPSHOT, the members can be output to the console. With version :2.0.0-SNAPSHOT and new configurations, with the same stream I got: