8000 [3.8.0] aardvark switching navpoints quickly causes react error · Issue #14574 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

[3.8.0] aardvark switching navpoints quickly causes react error #14574

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.

Sign up for GitHub

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

Jump to bottom
Closed
coronabytes opened this issue Jul 31, 2021 · 3 comments
Closed

[3.8.0] aardvark switching navpoints quickly causes react error #14574

coronabytes opened this issue Jul 31, 2021 · 3 comments
Labels
1 Bug 2 Fixed Resolution 3 UI ArangoDB Web Interface (frontend/Aardvark)
Milestone
3.8.1

Comments

@coronabytes
Copy link
Contributor
coronabytes commented Jul 31, 2021 •
edited
Loading

My Environment

  • ArangoDB Version: 3.8.0
  • Deployment Mode: Single Server
  • Infrastructure: Own
  • Operating System: Ubuntu 20.04
  • Total RAM in your machine: 8GB
  • Disks in use: SSD
  • Used Package: Ubuntu .deb

Component, Query & Data

Affected feature:
Aardvark

Steps to reproduce

  1. Switch Navpoints rather quickly (Queries, Dashboard, Logs, ...)
  2. At least ten times

Problem:

After switching navigation entries a react error is thrown and the app becomes unresponsive

  | t.unmountComponentAtNode | @ | react-dom.production.min.js:7367
-- | -- | -- | --
  | execute | @ | router.js:111
  | (anonymous) | @ | backbone.js:1769
  | (anonymous) | @ | backbone.js:2025
  | Lt | @ | some.js:13
  | loadUrl | @ | backbone.js:2023
  | navigate | @ | backbone.js:2083
  | navigate | @ | backbone.js:1784
  | navigateByTab | @ | navigationView.js:159
  | dispatch | @ | jquery.js:4668
  | m.handle | @ | jquery.js:4488

</span></div><!--EndFragment-->
</body>
</html>

React
@MDAlFattah
Copy link
Contributor

Greetings @coronabytes,
Thank you for your kind insight into the Logs revisit the issue. Our developer team already addressed this issue and you may track the progress of the respective PR below which will also be included in the upcoming 3.8.1 release.

Fixed LogsView re-visit issue

@Simran-B Simran-B added this to the 3.8.1 milestone Sep 1, 2021
@Simran-B Simran-B added 1 Bug 2 Fixed Resolution 3 UI ArangoDB Web Interface (frontend/Aardvark) labels Sep 1, 2021
@maxkernbach
Copy link
Contributor

Hi @coronabytes,

Version 3.8.1, which includes the stated fix, has just been released.
Could you please upgrade and let us know whether the UI works as expected?

@coronabytes
Copy link
Contributor Author

yes works now as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 Bug 2 Fixed Resolution 3 UI ArangoDB Web Interface (frontend/Aardvark)
Projects
None yet
Milestone
3.8.1
Development

No branches or pull requests
4 participants
@coronabytes @Simran-B @maxkernbach @MDAlFattah
0