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

[2.0] Sometimes the status of node is not started when started #1447

Closed
julien-duponchelle opened this issue Aug 25, 2016 · 2 comments
Closed
Assignees
Labels
Milestone

Comments

@julien-duponchelle
Copy link
Contributor

Move the node on the topology will refresh data and fix the issue

@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Aug 25, 2016
@julien-duponchelle julien-duponchelle changed the title [2.0] Sometimes the status of VPCS node is not started when started [2.0] Sometimes the status of node is not started when started Aug 26, 2016
@julien-duponchelle julien-duponchelle self-assigned this Aug 31, 2016
@julien-duponchelle
Copy link
Contributor Author

This is only when you have multiple nodes

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Aug 31, 2016
julien-duponchelle added a commit that referenced this issue Aug 31, 2016
This use a different signal to detect that data is downloaded.
With that, detection of new notification is instant when you
have multiple notifications.

Fix #1447
@julien-duponchelle
Copy link
Contributor Author

I found the issue. Qt was not raising signal to avoid spam us each time we received new data on the notification. But in our case we want to process them immediately. So we just need to use a lower level signal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant