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

Provenance Graph loading error #2372

Closed
scottx611x opened this issue Nov 14, 2017 · 5 comments
Closed

Provenance Graph loading error #2372

scottx611x opened this issue Nov 14, 2017 · 5 comments

Comments

@scottx611x
Copy link
Member

  • Specific code commit: 7e8847f
  • Version of the web browser and OS: Chrome Ubuntu 16.04
  • Environment where the error occurred (Vagrant VM and site conf mode or AWS instance):
    test.stemcellcommons.org

Steps to reproduce

Please list all the actions and the input data used:

  1. Upload the hg-19-metadata-s3.txt Dataset
  2. Navigate to the file browser and click on the Provenance tab

Observed behavior

  • Saw the following Console Error
    screen shot 2017-11-14 at 11 41 46 am

Expected behavior

  • No console Error, Provenance Graph to load
@scottx611x
Copy link
Member Author

scottx611x commented Nov 14, 2017

I've also seen the following error on the same dataset after running an analysis on it:
screen shot 2017-11-14 at 12 19 18 pm

@jkmarx
Copy link
Member

jkmarx commented Nov 14, 2017

Just uploaded a fresh hg-19, with no error. I remember in the past we've had issues with deleted analyses.
screen shot 2017-11-14 at 12 39 01 pm

@jkmarx jkmarx self-assigned this Nov 14, 2017
@scottx611x
Copy link
Member Author

Potentially related to #2292

@scottx611x
Copy link
Member Author

@jkmarx So I uploaded a clean hg-19-metadata-s3.txt ran FastQC on it and got a working Prov Graph.
screen shot 2017-11-14 at 2 45 08 pm

I then ran an RNA-Seq on it and am now seeing the can't read property: 'children' error:
screen shot 2017-11-14 at 3 15 15 pm

Just trying to gather as much info around the issue as I can

@jkmarx jkmarx removed this from the Next milestone Mar 14, 2018
@mccalluc
Copy link
Member

I think this is a duplicate of #2501, which also has a lot more activity: The screen shots here show the same error messages. Closing.

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

No branches or pull requests

3 participants