Skip to content

CLI and connection handling issues #180

@sirocchj

Description

@sirocchj

sbt --supershell=false or it will incur in sbt/sbt#5063 (thanks @barambani for finding this out)

However:

  • issuing quit does not terminate connection client-side (always been the case, not a new issue)
    localhost:6379> quit
    <<< OK - [5.06ms]
    localhost:6379>
    
  • Ctrl-C reports potential leak
    localhost:6379> ^C
    [warn] Canceling execution...
    [error] Total time: 124 s (02:04), completed 11-Nov-2019 08:45:47
    sbt:laserdisc> [warn] Thread[ioapp-compute-2,5,run-main-group-0] loading cats.syntax.EitherIdOps$ after test or run has completed. This is a likely resource leak
    2019-11-11 08:45:54,882 shutdown-hooks-run-all ERROR No Log4j 2 configuration file found. 
    Using default configuration (logging only errors to the console), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal initialization logging. 
    See https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions on how to configure Log4j 2
    

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIAlternative cli to redis-clibugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions