Kyo logging works at the Error level only

[halansary]

I am trying Kyo for the first time and may be doing something wrong here, but my expectation is that this should work (given my config) for all log levels except "debug":

object App extends KyoApp:
  run:

    for 
      _ <- Log.debug("debugging")
      _ <- Log.info("informing")
      _ <- Log.warn("warning")
      _ <- Log.error("erroring")
    yield ()

end App

Only the Log.error works despite that my logback level is set to "info", and the following is printed:

18:53:34.303 [kyo-scheduler-worker-2] ERROR kyo.logs -- [App.scala:16:33] erroring

Here is the complete config:

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE configuration>

<configuration>
  <import class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"/>
  <import class="ch.qos.logback.core.ConsoleAppender"/>

  <appender name="STDOUT" class="ConsoleAppender">
    <encoder class="PatternLayoutEncoder">
      <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} -%kvp- %msg%n</pattern>
    </encoder>
  </appender>

  <root level="info">
    <appender-ref ref="STDOUT"/>
  </root>
</configuration>

It seems to me that this piece of code in kyo.internatl.LogPlatformSpecific:

val level =
                if logger.isErrorEnabled() then Level.error
                else if logger.isWarnEnabled() then Level.warn
                else if logger.isInfoEnabled() then Level.info
                else if logger.isDebugEnabled() then Level.debug
                else Level.trace

... will always mean that the intended log level is error, because error is always isEnabled for all other levels (providing that i understand the isErrorEnabled function correctly).

[hearnadam]

This was a bug fixed in #1046. @fwbrasil perhaps we should cut a release?

@halansary you can try out the snapshot build. It should be: 0.16.1+39-96217015-SNAPSHOT I believe.

[fwbrasil]

Sounds good. I can make a release later today.

[fwbrasil]

Released: https://github.com/getkyo/kyo/releases/tag/v0.16.2

@halansary please let us know if you still see issues

[halansary]

@fwbrasil it works great now, thanks. And thank you so much for this amazing project