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

Can't edit Edges in WebView (any more?) #8841

Closed
qohelet opened this issue Apr 24, 2019 · 8 comments

Comments

Projects
None yet
4 participants
@qohelet
Copy link

commented Apr 24, 2019

My Environment

  • ArangoDB Version: 3.4.1
  • Storage Engine: RocksDB
  • Deployment Mode: Single Server
  • Deployment Strategy: Manual Start in Docker
  • Operating System: Ubuntu 18.04
  • Disks in use: HDD
  • Used Package: Ubuntu

Component, Query & Data

Affected feature:
Graph Viewer

Problem:
Maybe my memory is playing tricks to me - but I have the feeling I used to be able to edit Edges in the Graph Viewer.
Right now (login as root) I'm just able to modify documents. A click on the Edge gives me on the bottom part information on the key and which attribute it has, but no option to do modifications.

The routeplanner-example for instance has this option.

On which parameter does it depend whether or not I'm able to edit it?

Thank you

@Simran-B

This comment has been minimized.

Copy link
Contributor

commented Apr 25, 2019

If you click on an edge, a radial menu with two options should pop up:

image

A click on the pencil icon opens the inline document editor.

Is is pencil option missing for you? Can you post a screenshot?
If it occurs with a specific graph only, can you share it?

You can try the latest version and another browser to see if it makes a difference.

@qohelet

This comment has been minimized.

Copy link
Author

commented Apr 25, 2019

This is getting more and more weird.

Test 1:
Regularly opening the graph and clicking on the edge: Pencil appears

Test 2:
Loading full graph: Pencil appears

Test 3:
Changing the Node-Label in the menu from "_key" to "Name": No pencil icon

Test 4:
Loading full graph witch changed Node-Labels: No pencil icon

Here's the image:
image

@Simran-B

This comment has been minimized.

Copy link
Contributor

commented Apr 25, 2019

I just saw some odd behavior as well, but I don't think it's related to the node label option.

At first, hovering an edge highlights it, and the radial menu works. However, it sometimes gets stuck. Loading the full graph or changing any of the options fix the hovering, but then the radial menu doesn't show up at all anymore. This odd behavior seems to persist even if you reopen the graph until you refresh the entire page.

Chrome 73 on Windows and ArangoDB 3.4.4

@hkernbach @KVS85 Have you seen this behavior before?

@qohelet

This comment has been minimized.

Copy link
Author

commented Apr 25, 2019

Is there any workaround or possible explanation for this yet?

This was referenced May 13, 2019

@hkernbach

This comment has been minimized.

Copy link
Contributor

commented May 13, 2019

Will be fixed in 3.4.X and devel : #8979 & #8980

@maxkernbach maxkernbach reopened this May 13, 2019

@maxkernbach maxkernbach added the 2 Fixed label May 13, 2019

@maxkernbach maxkernbach added this to the 3.4.6 milestone May 13, 2019

@qohelet

This comment has been minimized.

Copy link
Author

commented May 13, 2019

I'm running the Docker-Image of ArangoDB. What's the preferred way of updating it?

@hkernbach

This comment has been minimized.

Copy link
Contributor

commented May 13, 2019

It is not released yet. This patch will be included when we're publishing 3.4.6.

@maxkernbach

This comment has been minimized.

Copy link
Contributor

commented May 29, 2019

Hi @qohelet,

version 3.4.6, which includes a fix for this issue, has been released.
In case you are still facing this problem, please comment and we will reopen it.

Regarding the docker upgrade: One possible way is to pick the old database and use it as bounded /data volume for a new docker container (after old container is stopped). Start the new docker container with the option --server.upgrade-auto to perform the upgrade.

You could also use arangodump to create a backup in your old version docker deployment and restore this backup using arangorestore in your new version docker deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.