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

Kibana Console does not render properly and can not get used at all #156485

Closed
holy-moly-555 opened this issue May 3, 2023 · 6 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@holy-moly-555
Copy link

Kibana version:
8.6.1

Elasticsearch version:
8.6.1

Server OS version:
Ubuntu 22.04.2 LTS

Browser version:
Chromium 112.0.5615.49 snap

Browser OS version:
Ubuntu 20.04.6 LTS

Original install method (e.g. download page, yum, from source, etc.):
Official Elastic Docker Images

Describe the bug:
The Kibana Console does not "render" properly so that it can not be used at all.
My last content must have broken it because the Console works fine when I'm opening it in a private browser session.

I don't know how to clear the Console at this point. Deleting my browser cookies didn't help. Restarting the Kibana container neither.

Steps to reproduce:
I don't know the last contents in the Console...

Expected behavior:
I'm able to use the Kibana Console.

Screenshots (if relevant):
image

Errors in browser console (if relevant):

n-ui-shared-deps-npm.dll.js:398 Error: The range has to be at least 2 characters width
    at h.addFold (kbn-ui-shared-deps-npm.dll.js:350:703321)
    at console.chunk.1.js:12:197915
    at Array.forEach (<anonymous>)
    at legacy_core_editor_LegacyCoreEditor.addFoldsAtRanges (console.chunk.1.js:12:197900)
    at console.chunk.1.js:12:270381
    at console.chunk.1.js:12:270402
    at qu (kbn-ui-shared-deps-npm.dll.js:398:106314)
    at t.unstable_runWithPriority (kbn-ui-shared-deps-npm.dll.js:406:3768)
    at $i (kbn-ui-shared-deps-npm.dll.js:398:44909)
    at Uu (kbn-ui-shared-deps-npm.dll.js:398:105759)
ms | @ | kbn-ui-shared-deps-npm.dll.js:398
caught (in promise) Error: The range has to be at least 2 characters width
    at h.addFold (kbn-ui-shared-deps-npm.dll.js:350:703321)
    at console.chunk.1.js:12:197915
    at Array.forEach (<anonymous>)
    at legacy_core_editor_LegacyCoreEditor.addFoldsAtRanges (console.chunk.1.js:12:197900)
    at console.chunk.1.js:12:270381
    at console.chunk.1.js:12:270402
    at qu (kbn-ui-shared-deps-npm.dll.js:398:106314)
    at t.unstable_runWithPriority (kbn-ui-shared-deps-npm.dll.js:406:3768)
    at $i (kbn-ui-shared-deps-npm.dll.js:398:44909)
    at Uu (kbn-ui-shared-deps-npm.dll.js:398:105759)

Any additional context:
None

@holy-moly-555 holy-moly-555 added the bug Fixes for quality problems that affect the customer experience label May 3, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label May 3, 2023
@holy-moly-555
Copy link
Author

Clearing the local storage via the browser dev tools did the job but this is definitely a bug.

@jsanz jsanz added Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more labels May 4, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 4, 2023
@jsanz
Copy link
Member

jsanz commented May 4, 2023

@holy-moly-555 so the issue then is that an invalid or corrupt state saved in the local storage prevents the console to render and leaves it unusable; and some form of "purge" would be needed to reset the state, right?

Can you update the issue description to present better the issue and request?

Also related to #93909

@holy-moly-555
Copy link
Author

@jsanz, thanks for your reply.
Would you please be more precise about which information I should provide?
As I stated in the issue, I don't know what was in my console last that may caused the error.
I noticed the error after I opened a new tab/window or something else. So I couldn't "experience" the error in real time.

Regards

@yuliacech
Copy link
Contributor

Hi @holy-moly-555,
that was a known issue and it was fixed in #152366 for v8.8.0

@holy-moly-555
Copy link
Author

Thanks @yuliacech!
I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

4 participants