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

fix:(jans-cli) error in application liveliness status #3008

Closed
manojs1978 opened this issue Nov 16, 2022 · 1 comment · Fixed by #3293
Closed

fix:(jans-cli) error in application liveliness status #3008

manojs1978 opened this issue Nov 16, 2022 · 1 comment · Fixed by #3293
Assignees
Labels
comp-jans-cli-tui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Milestone

Comments

@manojs1978
Copy link
Contributor

Describe the bug
error in application liveliness status in jans-cli

To Reproduce
Steps to reproduce the behavior:

  1. launch jans-cli
  2. add 10 then 1 thne to check
  3. Scroll down to '....'

Expected behavior
should not get any error

Screenshots
image

Desktop (please complete the following information):

  • OS: ubuntu
  • Browser [e.g. chrome, safari]
  • Version 20
  • DB postgresSQL

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@manojs1978 manojs1978 added kind-bug Issue or PR is a bug in existing functionality comp-jans-cli-tui Component affected by issue or PR labels Nov 16, 2022
@moabu moabu added this to the 1.0.5 milestone Nov 18, 2022
@moabu moabu modified the milestones: 1.0.5, 1.0.6 Dec 1, 2022
@devrimyatar
Copy link
Contributor

Duplication of #2966

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-cli-tui Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants