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

Blank cluster screen when running a build from source (6.3) #6829

Closed
joshualex opened this issue Dec 26, 2022 · 7 comments · Fixed by #6835
Closed

Blank cluster screen when running a build from source (6.3) #6829

joshualex opened this issue Dec 26, 2022 · 7 comments · Fixed by #6835
Assignees
Labels
bug Something isn't working p0
Milestone

Comments

@joshualex
Copy link

I'm trying to build an run the source locally (running on macOS Ventura 13.1) - and I used the official v.6.3.0 release archive.
Building via make build works flawlessly, but when I try to go to one of my cluster configs - the main pane comes out blank. The developer tools don't show any console errors or suspicious logs. Any idea why this could be?

@joshualex joshualex added the bug Something isn't working label Dec 26, 2022
@aleksfront
Copy link
Contributor

Hi @joshualex! I can't reproduce it locally. Can you provide any kind of extra information on this? What type of clusters do you have?

Can you please start an app from the terminal and see logs there?

@alebcay
Copy link
Contributor

alebcay commented Dec 27, 2022

Might be related: MuhammedKalkan/OpenLens#81.

@aleksfront aleksfront self-assigned this Dec 27, 2022
@jansav
Copy link
Contributor

jansav commented Dec 27, 2022

Could you verify if developer tools shows any failed network calls? We managed to reproduce this by blocking network calls to OpenLens.js and now we are thinking if this is something that you might encounter.

image

@jansav
Copy link
Contributor

jansav commented Dec 27, 2022

Update: Hypothesis over network failure is overruled with new hypothesis for race-condition during application start. #6690 removes a lot from application start so maybe it also introduces race-condition that causes this.

At least the behaviour is exactly same when there's non resolving promise in initClusterFrame.

@joshualex could you test against latest version from master? I'd like to double check that this hasn't been fixed already.

FYI @Nokel81

@jansav
Copy link
Contributor

jansav commented Dec 27, 2022

Update: Found out the issue and resolving it with a top priority. More details when issue has been resolved.

@joshualex
Copy link
Author

Thanks! Will test it out and report back

@joshualex
Copy link
Author

@jansav Seems to work fine off of master. Thanks!

@Nokel81 Nokel81 modified the milestones: 6.3.1, 6.4.0 Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working p0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants