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

go from vid over * reversely leads graphd server to crash #1364

Closed
jievince opened this issue Dec 2, 2019 · 4 comments
Closed

go from vid over * reversely leads graphd server to crash #1364

jievince opened this issue Dec 2, 2019 · 4 comments
Assignees

Comments

@jievince
Copy link
Contributor

jievince commented Dec 2, 2019

No description provided.

@jievince jievince changed the title go from vid over * leads graphd server to crash go from vid over * leads graphd server to crash Dec 2, 2019
@amber-moe amber-moe changed the title go from vid over * leads graphd server to crash go from vid over * reversely leads graphd server to crash Dec 2, 2019
@jievince
Copy link
Contributor Author

jievince commented Dec 2, 2019

logs/nebula-graphd.ERROR

Log file created at: 2019/12/02 16:16:12
Running on machine: localhost.localdomain
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
F1202 16:16:12.468133 39624 GoExecutor.cpp:1316] Check failed: iter != edges_.end()

@amber-moe
Copy link
Contributor

go from vid over edge1, edge2
go form vid over *
both works. So I guess it's the REVERSELY that matters.

@jievince
Copy link
Contributor Author

jievince commented Dec 2, 2019

In my test, go from hash("叶莉") over relation reversely works well, while go from hash("叶莉") over * reversely will lead graphd server to crash.

@amber-moe
Copy link
Contributor

amber-moe commented Dec 2, 2019

image
There is no serve reverse so nothing is returned, but is it supposed to return 0 as the go from vid over edge1, edge2?
image

@monadbobo monadbobo self-assigned this Dec 9, 2019
monadbobo added a commit to monadbobo/nebula that referenced this issue Dec 9, 2019
dutor pushed a commit that referenced this issue Dec 19, 2019
* Issue #1364 Fixed crash caused when not specifying edge type (over *) and setting reversely.

* address CPWstatic's comments.

* 1 address laura's comments.
2 Fixed a bug in fetching the shortest path (when there are different types of edges between two points will cause one of them to be ignored).
tong-hao pushed a commit to tong-hao/nebula that referenced this issue Jun 1, 2021
* Issue vesoft-inc#1364 Fixed crash caused when not specifying edge type (over *) and setting reversely.

* address CPWstatic's comments.

* 1 address laura's comments.
2 Fixed a bug in fetching the shortest path (when there are different types of edges between two points will cause one of them to be ignored).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants