Add support for logback.xml configuration file #625

yschimke · 2021-03-17T08:23:55Z

$ ./gradlew bootBuildImage
...
    [creator]     javax.xml.parsers.FactoryFinder was unintentionally initialized at build time. org.slf4j.impl.StaticLoggerBinder caused initialization of this class with the following trace:
    [creator]           at javax.xml.parsers.FactoryFinder.<clinit>(FactoryFinder.java:46)
    [creator]           at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:147)
    [creator]           at ch.qos.logback.core.joran.event.SaxEventRecorder.buildSaxParser(SaxEventRecorder.java:79)
    [creator]           at ch.qos.logback.core.joran.event.SaxEventRecorder.recordEvents(SaxEventRecorder.java:57)
    [creator]           at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:151)
    [creator]           at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110)
    [creator]           at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53)
    [creator]           at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
    [creator]           at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
    [creator]           at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84)
    [creator]           at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)

The text was updated successfully, but these errors were encountered:

yschimke · 2021-03-17T08:24:47Z

I'm testing now without this but I believe the codepath is when it hit src/main/resources/logback.xml

sdeleuze · 2021-03-17T10:40:20Z

Not an easy one:

Error: Classes that should be initialized at run time got initialized during image building:
 javax.xml.parsers.FactoryFinder was unintentionally initialized at build time. org.slf4j.impl.StaticLoggerBinder caused initialization of this class with the following trace: 
	at javax.xml.parsers.FactoryFinder.<clinit>(FactoryFinder.java:45)
	at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:127)
	at ch.qos.logback.core.joran.event.SaxEventRecorder.buildSaxParser(SaxEventRecorder.java:79)
	at ch.qos.logback.core.joran.event.SaxEventRecorder.recordEvents(SaxEventRecorder.java:57)
	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:151)
	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110)
	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53)
	at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
	at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
	at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84)
	at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)

We do our best to limit build time initialization but with SLF4J that's hard to avoid and here SLF4J build time init trigger logback SaxEventRecorder which performs javax.xml.parsers.FactoryFinder static init at build time.

Trying to intialize javax.xml.parsers.FactoryFinder at build time requires to configure a lot of other classes initialized at build time too so that seems a dead end to me.

Any thoughts @aclement?

yschimke · 2021-03-17T13:08:05Z

It worked for me just by deleting the file (I got further), so I'm not blocked.

sdeleuze · 2021-03-17T17:41:17Z

I move this issue to 0.10 since solving that will require deeper changes.

cipley · 2021-03-19T02:17:53Z

Hi,

I stumble upon this issue as well, and want to add some points;
It seems like having the logback file logback-spring.xml will result in below error:

Logging system failed to initialize using configuration from 'null'
java.lang.IllegalStateException: Could not initialize Logback logging from classpath:logback-spring.xml
        at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:168)
        at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithConventions(AbstractLoggingSystem.java:80)
        at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:60)
        at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:132)
        at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:312)
        at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:281)
        at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:239)
        at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:216)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:203)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:196)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:170)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:148)
        at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:82)
        at org.springframework.boot.SpringApplicationRunListeners.lambda$environmentPrepared$2(SpringApplicationRunListeners.java:63)
        at java.util.ArrayList.forEach(ArrayList.java:1259)
        at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:117)
        at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:111)
        at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:62)
        at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:362)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:320)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1311)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
        at i.c.t.d.b.n.api.Application.main(Application.java:18)
Caused by: ch.qos.logback.core.LogbackException: Unexpected filename extension of file [resource:logback-spring.xml]. Should be either .groovy or .xml
        at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:58)
        at org.springframework.boot.logging.logback.LogbackLoggingSystem.configureByResourceUrl(LogbackLoggingSystem.java:191)
        at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:165)
        ... 22 more

Which is quite odd since the logback file is actually have the correct extensions.

While in my case, when using logback.xml logback file, it will result in build error (I'm using maven btw);

...
[INFO]     [creator]     Error: Classes that should be initialized at run time got initialized during image building:
[INFO]     [creator]      org.springframework.boot.ansi.AnsiOutput was unintentionally initialized at build time. To see why org.springframework.boot.ansi.AnsiOutput got initialized use --trace-class-initialization=org.springframework.boot.ansi.AnsiOutput
[INFO]     [creator]     org.springframework.boot.logging.logback.ColorConverter was unintentionally initialized at build time. To see why org.springframework.boot.logging.logback.ColorConverter got initialized use --trace-class-initialization=org.springframework.boot.logging.logback.ColorConverter
[INFO]     [creator]
[INFO]     [creator]     Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
[INFO]     [creator]     Error: Image build request failed with exit status 1
[INFO]     [creator]     unable to invoke layer creator
[INFO]     [creator]     unable to contribute native-image layer
[INFO]     [creator]     error running build
[INFO]     [creator]     exit status 1
[INFO]     [creator]     ERROR: failed to build: exit status 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:51 min
[INFO] Finished at: 2021-03-19T05:32:17+07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.4.3:build-image (default-cli) on project networkprofile-bs-api: Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:2.4.3:build-image failed: Builder lifecycle 'creator' failed with status code 145 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

and yes, deleting the logback file causes the issue to disappear.

sdeleuze · 2021-03-19T14:36:38Z

This temporary limitation is now documented.

When we fix that, let's make sure <springProperty /> is supported as described in #607.

sdeleuze · 2021-03-22T15:05:25Z

logback.xml support seems more complicated than I thought originally, especially with Janino (a java compiler) involved.

richvim · 2021-03-24T14:40:49Z

Ran into this one while upgrading to 0.9.x. Did not occur in previous versions.

celcius112 · 2021-03-31T15:36:56Z

I am wondering whether Spring Boot should add more documentation (or features) about Logback's Configurator which allows for programmatic configuration instead of XML configuration.
Favoring programmatic configuration would probably be a good way to mitigate this issue, but I'm having some problems finding good documentation for extending Spring Boot configuration.

What do you think ?

chenzhiguo · 2021-03-31T16:08:57Z

Has this task been scheduled in the plan?

sdeleuze · 2021-04-01T07:06:19Z

@snicoll @bclozel Any thoughts on @celcius112 comment?

bclozel · 2021-04-01T07:11:28Z

This should be discussed in: spring-projects/spring-boot#25847

cyraid · 2021-04-05T20:57:51Z

This was a blocker for me. I wanted to convert to native but our projects need the logback-spring.xml and springProperty and also the compiler (for if blocks/statements).

A way forward might be to implement a new configuration file format but with native 'if' support without using janino compiler? Perhaps a more lean method of setting your appenders (that is somewhat compatible with logback on a basic level).

christian-draeger · 2021-04-20T20:58:58Z

same error as @cipley over here with version "0.9.2"

ranma2913 · 2021-05-14T15:57:45Z

Having the same issues with my project. So far we've been able to copy a standard logback-spring.xml between our projects. This enables our Splunk HTTP Appender. We're using the follwoing code and other springProperty placeholders:

    <!-- Import Non-Production Spring Properties & Set Defaults -->
    <springProperty name="LOGGING_SPLUNK_URL" source="logging.splunk.url" defaultValue="---"/>
    <springProperty name="LOGGING_SPLUNK_TOKEN" source="logging.splunk.token" defaultValue="---"/>

    <springProfile name="prod">
        <!-- configuration to be enabled when the "prod" profile is active -->
        <!-- Import Production Spring Properties & Set Defaults -->
        <springProperty name="LOGGING_SPLUNK_URL" source="logging.splunk.url" defaultValue="----"/>
        <springProperty name="LOGGING_SPLUNK_TOKEN" source="logging.splunk.token" defaultValue="---"/>
    </springProfile>

joeyslalom · 2021-05-17T02:07:05Z

Also fails for me with version 0.9.2. After seeing Logback is supported, but not configuration with logback.xml
I wondered if configuration via logback.groovy would work. It does not build via ./gradlew bootBuildImage:

Error: Classes that should be initialized at run time got initialized during image building:
[snip]
quite a lot of org.codehaus.groovy.NAME was unintentionally initialized at build time. To see why 
[snip]

Not advocating for logback.groovy, but I would have used it to workaround this issue. The basic customization via application.properties is not sufficient. I'm forward to spring-projects/spring-boot#25847 , I always thought logback.xml was a weird way to configure logback.

celcius112 · 2021-05-19T08:29:15Z

@joeyslalom don't hesitate to add a 👍 to the issue spring-projects/spring-boot#25847. If we show that we would like this feature the spring boot team will be more motivated to do it :)

* And note that there is still an open issue to allow for XML-based configuration, spring-attic/spring-native#625 * Hide Log4j2 support behind a Maven profile

frankkimm · 2021-06-23T12:13:37Z

same error as @cipley over here with version "0.10.0"

@configuration

* Try to produce a native image * Updated to Spring Boot 2.5.1 and Spring Native 0.10.1-SNAPSHOT * Remove occurences of proxyBeanMethods=false from @configuration and @SpringBootApplication annotations * Need to exclude InventoryReportAggregator fom classpath when producing native image, otherwise fail to disambiguate mainClass. * Revert to default logging provider for Spring Boot apps - Logback * Note that there is still an open issue to allow for XML-based configuration, spring-attic/spring-native#625 * Hide Log4j2 support behind a Maven profile * Remove configuration-processor and context-indexer dependencies * Remove redundant exclusion from sendgrid-java * Update cloudfoundry dependencies to 5.5.0.RELEASE * Set spring-native.version as property * Update documentation * Fix broken links * Upgrade OpenJDK JRE used in Dockerfile to 11.0.11 dates * Add Spring Snapshot repositories * Update Github Actions to produce variant executable artifacts for each of the supported backends (Log4J2 is configured as logging provider in each case) * Fix startup issues by setting spring.sql.init.enabled to false * Update R2dbcConfig so that connectionFactory is correctly initialized for all runtime variants (e.g., local, Docker, and cf push) * manifest.yml updated to pickup artifact from target directory * Be explicit - clean before invoking mvn verify in ci and release yaml (Github Actions) * Make certain final artifacts do not include resources or impl from a prior build variant

phejl · 2021-07-01T18:11:50Z

Hm, now I'm wondering what is the reproducible case :) What I did is I enabled xml support removeXmlSupport = false added type hints to all the different logback's converters, encoders and policies my app is using and now I'm able to run app just fine with my xml config including springProfile using -Dlogging.config=/path/to/my/logback-config.xml. No error during build or runtime.

phejl · 2021-07-01T18:20:23Z

With janino on CP and janino if condition in xml file (as far as I can tell I've added necessary TypeHints) the generated image just exit without any message with exit code 1.

Hm, Janino creates class at runtime and loads it. That could be the cause.

phejl · 2021-07-02T09:59:12Z

Hm, now I'm wondering what is the reproducible case

I see now it happens in case logback.xml is embedded in the application.

sdeleuze · 2021-07-04T20:38:25Z

See #889 for a workaround.

yschimke · 2021-07-05T06:12:12Z

a9e661b assume this feeds here https://docs.spring.io/spring-native/docs/current/reference/htmlsingle/#_application_failed_to_start_when_running_code_mvn_spring_boot_run_code eventually

sdeleuze · 2021-07-06T09:44:56Z

See https://docs.spring.io/spring-native/docs/current-SNAPSHOT/reference/htmlsingle/#logback-workaround/

sdeleuze · 2021-12-06T06:49:13Z

See also my recent update of Logback support documentation with explain how to specify configuration with logback-config.xml at runtime.

- While project uses jdk8, you can do native build with jdk11 `./mvnw clean package -Pnative` - You can then run these spring-shell-samples/target/spring-shell-samples java -jar spring-shell-samples/target/spring-shell-samples-3.0.0-SNAPSHOT-exec.jar - Remove logback.xml in favour of spring config to workaround for spring-attic/spring-native#625 - For now remove jcommander command sample to get support for it spring-projects#340 - Relates spring-projects#323

- While project uses jdk8, you can do native build with jdk11 `./mvnw clean package -Pnative` - You can then run these spring-shell-samples/target/spring-shell-samples java -jar spring-shell-samples/target/spring-shell-samples-3.0.0-SNAPSHOT-exec.jar - Remove logback.xml in favour of spring config to workaround for spring-attic/spring-native#625 - For now remove jcommander command sample to get support for it #340 - Relates #323

13940344135 · 2022-02-25T05:24:11Z

I created ch.qos.logback.classic.spi.Configurator file, CustomConfigurator class, and added @InitializationHint annotation as described in the documentation below.
10.2.3. How can I configure programmatically Logback as a logback.xml alternative?
But anyway, when I build, I get the following error,

> Task :nativeCompile
Toolchain detection is disabled, will use GraalVM from C:\graalvm-ce-java11-21.3.0.
[native-image-plugin] Using executable path: C:\graalvm-ce-java11-21.3.0\bin\native-image.cmd
[mystore:14228]    classlist:   3,766.58 ms,  1.19 GB
[mystore:14228]        (cap):   2,916.83 ms,  1.19 GB
Warning: Could not register org.springframework.boot.liquibase.LiquibaseChangelogMissingFailureAnalyzer: allDeclaredConstructors for reflection. Reason: java.lang.NoClassDefFoundError: liquibase/exception/ChangeLogParseException.
[mystore:14228]        setup:   4,625.32 ms,  1.19 GB
The bundle named: org.apache.tomcat.util.threads.res.LocalStrings, has not been found. If the bundle is part of a module, verify the bundle name is a fully qualified class name. Otherwise verify the bundle path is accessible in the classpath.
To see how the classes got initialized, use --trace-class-initialization=org.springframework.boot.logging.logback.ColorConverter
[mystore:14228]     analysis:   7,318.84 ms,  2.98 GB
Error: Classes that should be initialized at run time got initialized during image building:
 org.springframework.boot.logging.logback.ColorConverter was unintentionally initialized at build time. To see why org.springframework.boot.logging.logback.ColorConverter got initialized use --trace-class-initialization=org.springframework.boot.logging.logback.ColorConverter

Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
[mystore:14228]      [total]:  15,945.31 ms,  2.98 GB
# Printing build artifacts to: C:\workspace\mystore\build\native\nativeCompile\mystore.build_artifacts.txt
Error: Image build request failed with exit status 1

> Task :nativeCompile FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':nativeCompile'.
> Process 'command 'C:\graalvm-ce-java11-21.3.0\bin\native-image.cmd'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 36s
10 actionable tasks: 10 executed

am I missing something?

sdeleuze · 2022-03-15T09:12:44Z

Indeed, I can reproduce. Since embedded logback-spring.xml is now a better way to solve this as discussed here, I will just remove this programmatic Logback configuration from the documentation.

sdeleuze · 2022-10-19T20:36:19Z

This will be supported in Spring Boot 3 RC1 to be released tomorrow via spring-projects/spring-boot@4a76fbf thanks to @wilkinsona.

sdeleuze added this to the 0.9.1 milestone Mar 17, 2021

sdeleuze mentioned this issue Mar 17, 2021

Allow JHipster sample to compile to native #600

Closed

sdeleuze added the type: compatibility Native image compatibility issue label Mar 17, 2021

sdeleuze self-assigned this Mar 17, 2021

sdeleuze modified the milestones: 0.9.1, 0.10.0 Mar 17, 2021

sdeleuze changed the title ~~logback config file seems to fail the build~~ Add support for logback.xml configuration file Mar 19, 2021

sdeleuze mentioned this issue Mar 19, 2021

Logback unable to resolve springProperty #607

Closed

sdeleuze modified the milestones: 0.10.0, Backlog Mar 22, 2021

celcius112 mentioned this issue Mar 31, 2021

Provide a hook for configuring Logback programatically spring-projects/spring-boot#25847

Open

ChunMengLu mentioned this issue May 9, 2021

添加对 spring-native 的支持 lets-mica/mica#38

Closed

joeyslalom mentioned this issue May 24, 2021

Spring Native support GoogleCloudPlatform/spring-cloud-gcp#379

Closed

phejl mentioned this issue Jul 1, 2021

Avoid confusing message when using logback.xml #877

Closed

sdeleuze mentioned this issue Jul 4, 2021

Document how to customize Logback configuration programmatically #889

Closed

phejl mentioned this issue Jul 19, 2021

Have better out of the box support for logback #895

Closed

phejl mentioned this issue Jul 27, 2021

Remove remaining build time initialization (logging, hibernate validator, netty, etc.) #927

Closed

BernhardBln mentioned this issue Nov 3, 2021

Consider Graal native image for CLI factcast/factcast#224

Open

jvalkeal mentioned this issue Dec 24, 2021

Make sample to work with spring-native spring-projects/spring-shell#341

Merged

sdeleuze removed their assignment Feb 3, 2022

sdeleuze mentioned this issue Mar 15, 2022

Remove programmatic Logback configuration documentation #1533

Closed

marceligrabowski mentioned this issue Sep 3, 2022

[FEATURE] Support for native image (Spring Native/GraalVM) skrapeit/skrape.it#201

Closed

sdeleuze closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2022

sdeleuze removed this from the Backlog milestone Oct 19, 2022

sdeleuze added the for: external-project For an external project and not something we can fix label Oct 19, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add support for logback.xml configuration file #625

Add support for logback.xml configuration file #625

yschimke commented Mar 17, 2021

yschimke commented Mar 17, 2021

sdeleuze commented Mar 17, 2021

yschimke commented Mar 17, 2021

sdeleuze commented Mar 17, 2021

cipley commented Mar 19, 2021 •

edited

sdeleuze commented Mar 19, 2021

sdeleuze commented Mar 22, 2021

richvim commented Mar 24, 2021

celcius112 commented Mar 31, 2021

chenzhiguo commented Mar 31, 2021

sdeleuze commented Apr 1, 2021

bclozel commented Apr 1, 2021

cyraid commented Apr 5, 2021 •

edited

christian-draeger commented Apr 20, 2021

ranma2913 commented May 14, 2021

joeyslalom commented May 17, 2021

celcius112 commented May 19, 2021 •

edited

frankkimm commented Jun 23, 2021

phejl commented Jul 1, 2021 •

edited

phejl commented Jul 1, 2021 •

edited

phejl commented Jul 2, 2021 •

edited

sdeleuze commented Jul 4, 2021

yschimke commented Jul 5, 2021

sdeleuze commented Jul 6, 2021

sdeleuze commented Dec 6, 2021

13940344135 commented Feb 25, 2022 •

edited

sdeleuze commented Mar 15, 2022

sdeleuze commented Oct 19, 2022 •

edited

Add support for logback.xml configuration file #625

Add support for logback.xml configuration file #625

Comments

yschimke commented Mar 17, 2021

yschimke commented Mar 17, 2021

sdeleuze commented Mar 17, 2021

yschimke commented Mar 17, 2021

sdeleuze commented Mar 17, 2021

cipley commented Mar 19, 2021 • edited

sdeleuze commented Mar 19, 2021

sdeleuze commented Mar 22, 2021

richvim commented Mar 24, 2021

celcius112 commented Mar 31, 2021

chenzhiguo commented Mar 31, 2021

sdeleuze commented Apr 1, 2021

bclozel commented Apr 1, 2021

cyraid commented Apr 5, 2021 • edited

christian-draeger commented Apr 20, 2021

ranma2913 commented May 14, 2021

joeyslalom commented May 17, 2021

celcius112 commented May 19, 2021 • edited

frankkimm commented Jun 23, 2021

phejl commented Jul 1, 2021 • edited

phejl commented Jul 1, 2021 • edited

phejl commented Jul 2, 2021 • edited

sdeleuze commented Jul 4, 2021

yschimke commented Jul 5, 2021

sdeleuze commented Jul 6, 2021

sdeleuze commented Dec 6, 2021

13940344135 commented Feb 25, 2022 • edited

sdeleuze commented Mar 15, 2022

sdeleuze commented Oct 19, 2022 • edited

cipley commented Mar 19, 2021 •

edited

cyraid commented Apr 5, 2021 •

edited

celcius112 commented May 19, 2021 •

edited

phejl commented Jul 1, 2021 •

edited

phejl commented Jul 1, 2021 •

edited

phejl commented Jul 2, 2021 •

edited

13940344135 commented Feb 25, 2022 •

edited

sdeleuze commented Oct 19, 2022 •

edited