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

Gene symbol restoration does not alway take #56

Open
dkulp2 opened this issue Jul 4, 2018 · 2 comments
Open

Gene symbol restoration does not alway take #56

dkulp2 opened this issue Jul 4, 2018 · 2 comments
Assignees
Labels

Comments

@dkulp2
Copy link
Contributor

dkulp2 commented Jul 4, 2018

Sometimes, particularly I think with a new or slow instance, the gene symbol restoration does not occur. But it is not reproducible. filter.vals$user.genes gets set correctly during onRestore, but input$user.genes does not get set during onRestored. Almost certainly this is a timing issue where valid values for user.genes have not been updated before onRestored is called. It may be related to the amount of work for display.

Is there a workaround? There's no way to know whether input$user.genes is blank because the user removed the values or because the values were not restored. This is almost certain related to starting the choices as NULL and then updating to use server side choices. Is there someway to prime the choices with a small set of values that will match?

http://dropviz.org/?_state_id_=0a8d584a242ae544

@dkulp2 dkulp2 added the bug label Jul 4, 2018
@dkulp2 dkulp2 self-assigned this Jul 4, 2018
@dkulp2
Copy link
Contributor Author

dkulp2 commented Jul 6, 2018

Maybe use the same hack as for comparison.cluster #55 ?

@dkulp2
Copy link
Contributor Author

dkulp2 commented Jul 6, 2018

Another regular http://dropviz.org/?_state_id_=808251cb3173eb85

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