Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI and connection handling issues #180

Open
2 tasks
sirocchj opened this issue Nov 11, 2019 · 0 comments
Open
2 tasks

CLI and connection handling issues #180

sirocchj opened this issue Nov 11, 2019 · 0 comments
Labels
bug Something isn't working CLI Alternative cli to redis-cli

Comments

@sirocchj
Copy link
Member

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
    
@sirocchj sirocchj added bug Something isn't working CLI Alternative cli to redis-cli labels Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CLI Alternative cli to redis-cli
Projects
None yet
Development

No branches or pull requests

1 participant