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

Console is inconsistent when displaying symlink to binary file #467

Closed
jbleuzen opened this issue Jan 5, 2017 · 2 comments
Closed

Console is inconsistent when displaying symlink to binary file #467

jbleuzen opened this issue Jan 5, 2017 · 2 comments

Comments

@jbleuzen
Copy link

jbleuzen commented Jan 5, 2017

In some cases the caret of console get out of the console view, inducing that you can't see what you are typing.

Open a new container console, then connect (I only have sh available on my containers)

  1. Create a symbolic link to file : ln -s /etc/hosts hosts
  2. ls the content of the folder -> Everything looks ok (step-1)
  3. Create a symbolic link to a binary file : ln -s /bin/ls test-ls
  4. ls the content of the folder -> the newly created symlink rendering have a carriage return before the > (steph-2)
  5. Type 2 characters and everything goes back to normal
    6.Type a third character and the error is back…

Why this is a bug ? Because once the full height of console is used the line where the caret goes on the white space (step-3)

Here a some screenshots :

step-1

step-2

step-3

Technical details:

This bug was not present on Safari

  • Portainer version: 1.1.0
  • Portainer Docker image tag (latest/arm/windows...): latest
  • Target Docker version (the host/cluster you manage): local
  • Target Swarm version (if applicable): n/a
  • Platform (windows/linux): linux
  • Browser: Chrome 53.0.2785.143 (64bits)

Thanks
Portainer is such a useful piece of software... Thanks, this is not a critical bug but sometimes it can be annoying to see the line where I'm typing goes up and down.

@deviantony
Copy link
Member

Hi @jbleuzen

I was unable to reproduce this in version 1.15.0. Could you tell me if this is still happening ?

@jbleuzen
Copy link
Author

jbleuzen commented Oct 19, 2017

Hello !

I can confirm that I can't reproduce the issue... And I'm in 1.13.5…

I'll close the issue, thanks !

chiptus added a commit that referenced this issue Aug 13, 2021
Co-authored-by: Tobias Holler <mail@toubs.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants