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

ERROR TypeError: Cannot read properties of undefined (reading 'coordinates') #424

Open
adf-ncgr opened this issue May 25, 2022 · 1 comment
Assignees
Labels

Comments

@alancleary alancleary self-assigned this Jun 2, 2022
@alancleary alancleary added the bug label Jun 2, 2022
@adf-ncgr
Copy link
Contributor Author

this error seems to occur much more frequently than I'd care to admit. Here's a simpler example that seems to reproducibly trigger it:
https://gcv.legumeinfo.org/gcv2/gene;lis=glyma.Wm82.gnm4.ann1.Glyma.18G052800

I'm not sure if this helps debug at all, but from what I've seen, the problem seems to have something to do with the region of the genome that the query gene resides in, since neighboring genes tend to yield the same issue. For example:
https://gcv.legumeinfo.org/gcv2/gene;lis=glyma.Wm82.gnm4.ann1.Glyma.18G054600
manifests similarly, although now that I'm looking it actually reports a different error in the console:
main.fbb371a5cac15b03.js:1 ERROR RangeError: Invalid array length
at l (806.d35139a33f71c5b1.js:1:217593)
at 806.d35139a33f71c5b1.js:1:218100
at Array.forEach ()
at ew (806.d35139a33f71c5b1.js:1:217828)
at $h (806.d35139a33f71c5b1.js:1:218136)
at 806.d35139a33f71c5b1.js:1:219474
at Array.forEach ()
at Q0 (806.d35139a33f71c5b1.js:1:218998)
at sw (806.d35139a33f71c5b1.js:1:221703)
at 806.d35139a33f71c5b1.js:1:293420

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

2 participants