galaxyproject / galaxyproject/usegalaxy-tools

Error with interactive_tool_pavian at UseGalaxy.org

Open
#1,502 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
22
Forks
70
Avg merge
1d 3h
Merged PRs (30d)
25

Description

> Workaround for End Users
>
> 1. Create an account at [UseGalaxy.eu](http://usegalaxy.eu/) if you do not have one yet.
> 2. Go back to [UseGalaxy.org](http://usegalaxy.org/). You will be creating an exported version of your history [following this FAQ](https://galaxyproject.github.io/training-material/faqs/galaxy/histories_transfer_entire_histories_from_one_galaxy_server_to_another.html).
* Note for those **not** working in a tutorial (tutorial data will transfer fine!): When your history is very large, you may want to [copy only some datasets](https://galaxyproject.github.io/training-material/faqs/galaxy/histories_copy_dataset.html) into a **new** smaller history and move that over instead!
> 4. Capture the link from [UseGalaxy.org](http://usegalaxy.org/) and input it over at the [UseGalaxy.eu](http://usegalaxy.eu/) server.
> 5. Allow your archive to fully load. It may take a few minutes so please be patient!
> 6. Everything will be intact, look the same, and you can continue with your work.
> 7. This works in both directions to/from any public Galaxy servers. You can also [download this history archive](https://galaxyproject.github.io/training-material/faqs/galaxy/account_reduce_quota_usage.html), then load it up later!

**interactive_tool_pavian**

Details

Image

Image

https://usegalaxy.org/u/jen-galaxyproject/h/test-kraken-kraken2
https://usegalaxy.org/datasets/f9cad7b01a4721358a0c176c7e6f6622/details

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the interactive_tool_pavian failure at UseGalaxy.org using the linked history and dataset details. Then locate the interactive_tool_pavian configuration or entry point in this repository and compare its behavior with the reported screenshots; done means the tool runs successfully on the provided example.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.