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

Failure to load dropped Newick file #71

Open
michellescribner opened this issue Dec 5, 2023 · 3 comments
Open

Failure to load dropped Newick file #71

michellescribner opened this issue Dec 5, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@michellescribner
Copy link

Current Behavior

Hello, I am trying to load the attached Newick file in auspice.us, but am seeing the failure to load error shown below. (I am attempting to load the file with the file ending .nwk, but was not able to link that file time to this GitHub issue so have attached it as .txt instead.)

test_tree_20231205.txt

image

How to reproduce

Steps to reproduce the current behavior:

  1. Drag and dropped file into auspice.us in web browser

Your environment: if browsing Nextstrain online

  • Operating system: Windows
  • Browser: Chrome

Additional context

Tree was generated using the Snippy_Tree_PHB workflow on Terra and was successfully loaded in other tree visualization tools including iTol and MicroReact.

@michellescribner michellescribner added the bug Something isn't working label Dec 5, 2023
@jameshadfield
Copy link
Member

Thanks for the bug report! I don't have the time to fix this right at the moment but hopefully someone on the team can.

The tree parsing fails because of Error: InternalError: too much recursion, which is surprising for a 20 tip tree!

This error was introduced ~a month ago by #69

@michellescribner
Copy link
Author

Thank you so much for the quick answer @jameshadfield!

jameshadfield added a commit that referenced this issue Dec 6, 2023
Two recent issues (#71, #72) provide examples where the improved parsing
either didn't parse a valid newick tree or (much more worryingly)
returned an entirely incorrect tree structure, including nodes not
present in the newick. See those issues for details, including the tree
files. While this reversion will re-introduce bugs such as #66 and the
bug in
<https://discussion.nextstrain.org/t/displaying-trees-from-ncbi-pathogen-browser-in-auspice-us/1456/4>,
but they are lesser than the bugs introduced by #69.

This reverts commit cabba98, although
subsequent changes to package-lock.json mean it's not a clean revert.
jameshadfield added a commit that referenced this issue Dec 6, 2023
Two recent issues (#71, #72) provide examples where the improved parsing
either didn't parse a valid newick tree or (much more worryingly)
returned an entirely incorrect tree structure, including nodes not
present in the newick. See those issues for details, including the tree
files. While this reversion will re-introduce bugs such as #66 and the
bug in
<https://discussion.nextstrain.org/t/displaying-trees-from-ncbi-pathogen-browser-in-auspice-us/1456/4>,
but they are lesser than the bugs introduced by #69.

This reverts commit cabba98, although
subsequent changes to package-lock.json mean it's not a clean revert.
jameshadfield added a commit that referenced this issue Dec 6, 2023
Two recent issues (#71, #72) provide examples where the improved parsing
either didn't parse a valid newick tree or (much more worryingly)
returned an entirely incorrect tree structure, including nodes not
present in the newick. See those issues for details, including the tree
files. While this reversion will re-introduce bugs such as #66 and the
bug in
<https://discussion.nextstrain.org/t/displaying-trees-from-ncbi-pathogen-browser-in-auspice-us/1456/4>,
but they are lesser than the bugs introduced by #69.

This reverts commit cabba98, although
subsequent changes to package-lock.json mean it's not a clean revert.
@jameshadfield
Copy link
Member

This tree should now be correctly displayed in auspice.us (via #73)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants