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
Error 500 from the g:Profiler server. I sent in a support ticket, and the issue was fixed on the g:Profiler server.
Warning: Error in : Empty reply from server. Support ticket submitted.
Error 400 from the server.
The issue is entirely on the g:Profiler side of the server, which points to the larger issue of relying on a large chunk of code for the gene ontology enrichment analysis portion of MetaNetwork's workflow that we don't maintain ourselves. There's no way that we can port a version of g:Profiler into the MetaNetwork Docker container.
The text was updated successfully, but these errors were encountered:
I think the best course of action would be to submit a small list of genes to g:Profiler when MetaNetwork is initializing, then awaiting a response. If it goes through, then MetaNetwork functions normally. Otherwise, MetaNetwork should disable the functional annotation enrichment portions and display an error message without killing the program.
In the meantime, I'm going to create a docker container without the functional annotation enrichment and that should serve as a stop-gap until I'm done working with the g:Profiler people.
User currently experiencing a series of errors.
The issue is entirely on the g:Profiler side of the server, which points to the larger issue of relying on a large chunk of code for the gene ontology enrichment analysis portion of MetaNetwork's workflow that we don't maintain ourselves. There's no way that we can port a version of g:Profiler into the MetaNetwork Docker container.
The text was updated successfully, but these errors were encountered: