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.

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

Dancing nodes when nodes are added/removed #1033

Closed
2opremio opened this issue Feb 25, 2016 · 5 comments
Closed

Dancing nodes when nodes are added/removed #1033

2opremio opened this issue Feb 25, 2016 · 5 comments
Assignees
@davkal
Labels
bug Broken end user or developer functionality; not working as the developers intended it component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer dogfood Important for the developer's own use of the project
Milestone
n/a

Comments

@2opremio
Copy link
Contributor

Report: service_report.json.gz

It would be good if we could reduce the layout impact when removing/adding nodes.
@2opremio 2opremio added the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label Feb 25, 2016
@2opremio 2opremio added this to the 0.14.0 milestone Mar 4, 2016
@tomwilkie tomwilkie removed this from the 0.14.0 milestone Mar 17, 2016
@rade rade added bug Broken end user or developer functionality; not working as the developers intended it dogfood Important for the developer's own use of the project labels Jul 4, 2016
@rade rade added this to the July2016 milestone Jul 4, 2016
@rade rade changed the title Dancing nodes in detailed view Dancing nodes Jul 4, 2016
@rade rade changed the title Dancing nodes Dancing nodes when nodes are added/removed Jul 4, 2016
@rade
Copy link
Member

rade commented Jul 4, 2016

This is especially visible when there is node churn, i.e. lots of short-lived nodes.

@rade rade mentioned this issue Jul 4, 2016
Closed
@rade rade modified the milestones: July2016, August2016 Jul 5, 2016
@rade rade mentioned this issue Jul 17, 2016
Open
@rade rade modified the milestones: 0.18/1.0, October2016 Sep 15, 2016
@davkal davkal self-assigned this Oct 14, 2016
@davkal davkal mentioned this issue Nov 7, 2016
Merged
@2opremio 2opremio modified the milestones: December2016, Backlog Dec 5, 2016
@rade
Copy link
Member

rade commented Dec 12, 2016

@davkal so is #1993 supposed to fix this? Looks like we feature-flagged that; what's the follow-up?

@davkal
Copy link
Contributor

davkal commented Dec 12, 2016

The followup: @2opremio and @pidster, could you please alert me if you see any more dancing? And then while you see it, we can turn on the new heuristics. This requires a bit of interactivity, I'm afraid.

If nothing comes up in the next 30 days, we should close this issue.

@2opremio
Copy link
Contributor Author

I haven't seen this in a while. These days I am more concerned about the lack of danceability ( #1935 ). In demos systematically find myself pressing the refresh button.

@davkal davkal modified the milestones: December2016, EOY 2016 Dec 13, 2016
@rade
Copy link
Member

rade commented Jan 10, 2017

If nothing comes up in the next 30 days, we should close this issue.

30 days is up.

@rade rade closed this as completed Jan 17, 2017
@rade rade modified the milestones: n/a, EOY 2016 Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davkal davkal

Labels
bug Broken end user or developer functionality; not working as the developers intended it component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer dogfood Important for the developer's own use of the project
Projects
None yet
Milestone
n/a
Development

No branches or pull requests
4 participants
@rade @tomwilkie @davkal @2opremio