Closed rajaie-sg closed 1 year ago
Same here
Same.
@ErezWeiss thank you for cmd+r
, indeed helps
@mtomilov great! Let us know if you solved it somehow
cmd+r
made the UI come back, but it seems that I have to run it every time I open Lens. Another issue I discovered is that the "Exec into container" and "Logs" button is gone from Pods
Was it in the previous version?
Nope. With 6.2.5 I see the "Pod Logs" and "Pod Shell" and "Attach to Pod" buttons
seems related: https://github.com/lensapp/lens/issues/1690
I've managed to install 6.2.5 and it seems to be working
brew uninstall openlens
rm -rf ~/Library/Application Support/OpenLens
rm -rf ~/Library/Logs/OpenLens
vi openlens.rb and paste this:
cask "openlens" do
arch arm: "-arm64"
version "6.2.5"
sha256 arm: "673a4ad49bb108bd1b995bf0d3eda971254ab6da4f54ad65f067208c8cde99db",
intel: "e680ca5f0091663435696eff4da6666007d7bc8cb69078f56d1b7d7674cca296"
url "https://github.com/MuhammedKalkan/OpenLens/releases/download/v#{version}/OpenLens-#{version}#{arch}.dmg"
name "OpenLens"
desc "Open source build of Lens Kubernetes IDE"
homepage "https://github.com/MuhammedKalkan/OpenLens/"
auto_updates true
app "OpenLens.app"
zap trash: [
"~/Library/Application Support/OpenLens",
"~/Library/Logs/OpenLens",
]
end
brew install --cask openlens.rb
lensapp/lens#1690
Relevant issue https://github.com/lensapp/lens/issues/6823
https://github.com/lensapp/lens/issues/6819 Smells of revenue protection disguised as a technical fix. The arch package maintainer has got stuffed by this too. I expect a fork from 6.2.x will be the only solution.
yeah they killed it
https://github.com/lensapp/lens/issues/6823#issuecomment-1363736366
Reading PRs like https://github.com/lensapp/lens/pull/6722 feels like they also want to disable binaries at OpenLens at all.
Wow... Seems like I will change from Lens
Also additionally to the above experience, I cannot change the sync files and folders option to have a specific config file. Always get reset to the default one.
Also additionally to the above experience, I cannot change the sync files and folders option to have a specific config file. Always get reset to the default one.
With 6.2.5 dmg, things work as expected. Unfortunately ther is no brew support for installing this specific version.
@rajaie-sg Can you test if it's still an issue in latest master
?
The good news is, that 6.4.0-alpha.0 fixes this issue and #6834 as well. Tested with local build on macOS Big Sur (M1 silicon)
With 6.2.5 dmg, things work as expected. Unfortunately ther is no brew support for installing this specific version.
I've explained it above
@ErezWeiss, this only works for one time and the application is auto-updated to 6.3.0
. tried to brew cu pin openlens
and other methods but can't get it to stop updating... any ideas?
Lens decide to make the update non toggleable.
The good news is, that 6.4.0-alpha.0 fixes this issue and #6834 as well. Tested with local build on macOS Big Sur (M1 silicon)
Maybe we have to build this one
@ErezWeiss, this only works for one time and the application is auto-updated to
6.3.0
. tried tobrew cu pin openlens
and other methods but can't get it to stop updating... any ideas?
Hi, after installing version 6.2.5 you can block updates by changing the permissions of the pending folder:
sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending
same error here, on macOS with v6.3.0
Same here
Just my 2c, this kind of thing is typically "fork in the road" time to break off from upstream.
@djvs feel free to fork
@jkroepke To fork off from the main Lens I mean, not to fork OpenLens, sorry.
Im just using 6.2.5 binary until some new developments in this case, i dont want to pay for the features i dont use anyway
since i exec this command to block update, openlens is not launching anymore, no know how to fix this
since i exec this command to block update, openlens is not launching anymore, no know how to fix this
working for me...
sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending
Dude you can restore permissions with this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending
in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory
since i exec this command to block update, openlens is not launching anymore, no know how to fix this
I simply changed the permissions of the folder....if you want restore permissions run this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending
sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending
Dude you can restore permissions with this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending
in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory
Could you explain better, I can't follow you...
Anyway I can't see the pods menu in 6.3.0 😅😅 it's an error?
For 6.3.0, go to Extensions and install @alebcay/openlens-node-pod-menu
, then pods menu are back. Its way more easier then try to block to auto-update
Checkout README.md in this repository, because its documented.
sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending
Dude you can restore permissions with this command:
sudo chmod -R 755 ~/Library/Application\ Support/Caches/open-lens-updater/pending
in tshoot i've deleted this folder, after reinstalling openlens, this folder not recreate ~/Library/Application Support/Caches/open-lens-updater/pending: No such file or directory
Could you explain better, I can't follow you...
found how to fixed, brew uninstall didn't killed the lens process, so found it in monitor activity then kill it my self then workd, 6.2.5. Awesome thanks guys
@ErezWeiss, this only works for one time and the application is auto-updated to
6.3.0
. tried tobrew cu pin openlens
and other methods but can't get it to stop updating... any ideas?Hi, after installing version 6.2.5 you can block updates by changing the permissions of the pending folder:
sudo chmod -R 000 ~/Library/Application\ Support/Caches/open-lens-updater/pending
for Linux it's ~/.cache/open-lens-updater/pending
directory
For 6.3.0, go to Extensions and install
@alebcay/openlens-node-pod-menu
, then pods menu are back. Its way more easier then try to block to auto-update
thank you!
I confirm I'm experiencing the same issue on ARM using 6.3.0. No issues on 6.2.5
Seeing this here as well. I can put 6.2.5 back on, but the darn thing keeps auto-updating to 6.3.0 and breaking again.
I think 6.3.0 release should be withdrawn from stable channel
For anyone using 6.3.0 on Windows, it is CTRL+R that will show the cluster details. Thanks @ErezWeiss
CTRL+R does not consistently work for me. Moreover, sometimes when it shows the cluster, it shows corrupted or half-rendered data. 6.3.0 is just straight-up broken and should be yanked from stable channel.
Ok so that i understand. When i install extensions on 6.3.0 there is no issue. Are you guys talking about something else. Because i am not experiencing any missing behaviour
In my case I have just started using 6.3.0 on Windows today. Using it as is, straight after installing without any add-ons/extensions. Only run into the blank UI issue but with the CTRL+R fix it has worked for me so far. However only used a subset of the functionality and haven't used it long enough to be able to tell if 6.3.0 is a good release or not.
@MuhammedKalkan the issue is the blank page when accessing cluster, as others mentioned cmd+r relates the screen, but even after that it doesn't look like it fully loads the information. When clicking on a pod there's no option to get a shell of it or see logs. There might be more things, but I didn't explore more, because the above already makes the product unusable.
Also an option to disable upgrade is absolutely needed. The recommendation given by others don't work. For example changing permissions on pending folder prevents OpenLens from starting.
Making the app (in OS X) read only, seems to work, but then open lens nags periodically to enter password.
@MuhammedKalkan there's a screencap right at the top of this thread. That's what it looks like for me too.
(In my opinion) Basic install of app should 'work', i.e.
As a Kubernetes administrator with a functioning ~/.kube/config
and current authentication:
There should be no non-obvious steps required for basic functionality such as installing extensions or the cmd+R
/Ctrl+R
that I had to come here to find out about. Consider electron apps like:
6.2.5 acheived this
I upgraded from OpenLens 6.2.5 to 6.3.0 and now see a blank UI when I connect to any cluster
I was not experiencing this issue with 6.2.5. I tried opening and closing the application multiple times, but the same issue persisted. Anyone else having similar issues?