You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"message" : "Requested tree (25993 tips) is larger than currently allowed by this service (25000 tips). For larger trees, please download the full tree directly from: http://files.opentreeoflife.org/trees/",
"exception" : "BadInputException",
"fullname" : "org.neo4j.server.rest.repr.BadInputException",
"stacktrace" : [ "opentree.plugins.tree_of_life_v3.doSubtree(tree_of_life_v3.java:715)", "opentree.plugins.tree_of_life_v3.subtree(tree_of_life_v3.java:563)", "java.lang.reflect.Method.invoke(Method.java:498)", "org.neo4j.server.plugins.PluginMethod.invoke(PluginMethod.java:57)", "org.neo4j.server.plugins.PluginManager.invoke(PluginManager.java:168)", "org.neo4j.server.rest.web.ExtensionService.invokeGraphDatabaseExtension(ExtensionService.java:300)", "org.neo4j.server.rest.web.ExtensionService.invokeGraphDatabaseExtension(ExtensionService.java:122)", "java.lang.reflect.Method.invoke(Method.java:498)", "org.neo4j.server.rest.security.SecurityFilter.doFilter(SecurityFilter.java:112)" ]
}
Looks like we need to preserve this information in the RAM cache (not sure why it was lost, perhaps a redirect?) and show a sensible response to the user. Currently the webapp wrongly reports the problem:
This taxon is in our taxonomy but not in our tree synthesis database. This can happen for a variety of reasons, but the most probable is that is has a taxon flag (e.g. incertae sedis) that causes it to be pruned from the synthetic tree. See the taxonomy browser for more information about this taxon.
The text was updated successfully, but these errors were encountered:
Trying to browse to this taxon fails in the webapp: https://tree.opentreeoflife.org/opentree/opentree7.0@ott765489/Chrysomeloidea
If i copy the browser request as cURL, i just get the response ‘ERROR’. but if I bypass the cache, like so:
… I get a more helpful error message:
Looks like we need to preserve this information in the RAM cache (not sure why it was lost, perhaps a redirect?) and show a sensible response to the user. Currently the webapp wrongly reports the problem:
The text was updated successfully, but these errors were encountered: