Comments (7)
starpit
commented on June 18, 2024
thanks for the bug report! are you on a) WSL2; b) powershell; c) git bash; d) other? (guessing powershell from the env vars?)
did you open from a terminal or by double clicking?
windows 10? 11?
if you have a chance, can you open up the dev tools (View -> Toggle Developer Tools) and see if there are any errors in the Console?
thanks!
edit: i just tried Kui 12.2.0 with both kubectl 1.20 and 1.25, launched from git bash and powershell and by double click. no problems, yet. hmm
from kui.
cosminilie
commented on June 18, 2024
I tried to open it by double clicking on it, by using Windows terminal, cmd.exe and git bash. Same behaviour across the board.
I'm using windows 10:
Edition Windows 10 Pro
Version 22H2
Installed on 10/14/2022
OS build 19045.2251
Experience Windows Feature Experience Pack 120.2212.4180.0
Seems like i was able to find something in the console, but it might be nothing, as it happens at startup not when i run any kube command.
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +0ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +20ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +53ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +51ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +52ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
53156.3fc17f1bb6a200c89ffe.bundle.js:1 Suspicious return value for current namespace true kubectl config view --minify --context rancher-desktop --output "jsonpath={..namespace}"
(anonymous) @ 53156.3fc17f1bb6a200c89ffe.bundle.js:1
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +63ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +64ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +61ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +60ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +52ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +52ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +0ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
33780.5b463f45261008792060.bundle.js:1 needle Making request #1 +53ms Object
33780.5b463f45261008792060.bundle.js:1 needle Request error +1ms Error: connect ECONNREFUSED 127.0.0.1:9000
at __node_internal_captureLargerStackTrace (node:internal/errors:465:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:643:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
from kui.
k8s-triage-robot
commented on June 18, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from kui.
n3wjack
commented on June 18, 2024
I'm seeing the same issue on Windows on 13.1.3.
What I think is causing the issue is the fact that after closing Kui, the kubectl processes it starts in the background aren't killed. They keep hanging around if you look with task manager or process explorer (from sysinternals). When I kill them and restart Kui, I can run kubectrl commands again.
In the screenshots below you can see the state when Kui is running, and after it's closed.
The kubectl & conhost processes have the same PIDs, and aren't killed with the app.
from kui.
k8s-triage-robot
commented on June 18, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
from kui.
k8s-triage-robot
commented on June 18, 2024
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
from kui.
k8s-ci-robot
commented on June 18, 2024
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from kui.
Related Issues (20)
- Annotations tab shows up even for kubernetes resources with no annotations HOT 5
- clicking on a row of `helm ls` does `helm get` that gives an error
- How to Load Bash Profile in Mac HOT 5
- Mobile friendly homepage HOT 4
- Logs doesn't show up in v 13.1.1 HOT 3
- Error starting up pty Error: node-loader after brew install HOT 3
- How to deploy kui hosted client-server in a k8s server ? HOT 7
- Commands autocompletion is not working HOT 8
- Uncaught TypeError exception after kubectl kui if kui window is already open HOT 3
- Logs tab should track initContainers HOT 4
- Flow Tab missing HOT 4
- kubectl get --watch tables should eventually remove terminated resources HOT 4
- Update kubectl Logs tab to use xterm's search, rather than our home-grown HOT 6
- kubectl Logs Previous does not pay attention to current container selection HOT 4
- Save Feature or Folder for Markdown Files in Windows HOT 8
- `top` not working HOT 8
- 'kubectl get' does not work as expected for some resources HOT 5
- deployment -> pods uses incorrect label selector HOT 1
- Unable to access logs or terminal on Linux via WSL
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kui.