-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature metadata tables not loading #155
Comments
I have 3 example datasets:
Only for the latter 2 I get warnings in R that the output will contain list-cols. I'll look deeper in to this. |
Getting rid of the list-cols didn't solve the problem. @bnovotny can you send me your database in a zip file? I don't have a dataset where the feature meta table is not working in the data table tab. @ergonyc I tracked the problem down to this piece of code:
This piece of javascript is causing the data.table to hang on processing. If I leave this out of This didn't work.
|
PR #165 should fix this problem. The reason why I didn't see the issue in the data table tab is that I was only showing the first 25 rows and the first NA appears later. |
Thanks! I can't send my database but I will try it with the changes you implemented. |
I'm going to leave this open for now and see what kind of crazy tables might get rendered and if the JavaScript is robust. Great work @bnovotny @ricoderks !! |
Describe the bug
Tables for feature metadata on both the "Playground/Table" tab and the "Data Table/Feature Meta" tab perpetually display "Processing..." and never load.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Table with feature metadata from "var_annot" should display.
Screenshots
Desktop (please complete the following information):
Additional context
Could be a format rendering issue in datatable, however I don't think it's a problem with attempting to format PubChem IDs (numeric IDs that need to be displayed as character in the table), because the issue persists when I remove the PubChem ID column in my data frame.
The text was updated successfully, but these errors were encountered: