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
Concurrent event in Graph: NoSuchElementException in GraphListeners #293
Comments
We forgot to mention we are using v1.3. |
I am hitting the same issue, my background thread is replacing attributes on the Graph, which works fine until i hit this. Then the Graph stops updating on the screen. |
Hi, Can you confirm that this problem still exists in Graphstream 2.0 ? |
Could you upload 2.0 to Maven Central so I can test it? |
Graphstream 2 use jitpack.io, you can see how to use it in the readme. |
A similar exception occurs with Graphstream 2.0 (gs-core 2.0.0-beta, gs-ui-swing 2.0-alpha) Unfortunately, I'm unable to spend more time on this right now and provide a self-contained example. Here's the complete stacktrace:
|
Thank you for the confirmation, I will try to work on this issue |
@hichbra jitpack is missing the source artefacts for the latest versions, is there anyway for those to be available too? |
I'm sorry if I misunderstood your question, are you talking about javafx ? There no beta version released for the moment. |
@hichbra no, I'm talking about the maven source artefacts: https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html This is important when using a library that it is possible to explore its source code and not only depends on the binary jar. |
Indeed ! Can you open a new issue ? We will try to work around for the next release. |
A pull request is sended : #337 <dependency>
<groupId>com.github.hichbra</groupId>
<artifactId>gs-core</artifactId>
<version>Fix293Concurrent-SNAPSHOT</version>
<scope>compile</scope>
</dependency> |
@pigne sorry to disappoint, but I just tested with v2.0 (with the swing ui) and I still get the exception (but it seems it appears less often, while before it appeared every time). Here is the current stacktrace:
|
Hi,
I have a
Graph
,Node
s andEdge
s that are concurrently modified.Since the
Graph
is attached to aViewer
,GraphListeners
is responsible of piping the events from the graph to the viewer.Sometimes, when there are concurrent modification of the elements of the graph, I get the following exception:
I tried using
Graphs.synchronizedGraph
but it doesn't solve the problem, because this is not about concurrent modification of ONE element, but concurrent emission of events to theGraphListeners
.There seem to be no way to have this pipe behave correctly with concurrence.
Is there something I am missing or is this a bug?
The text was updated successfully, but these errors were encountered: