by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Marius van den Beek
@mvdbeek
but you're not getting the wheels we're testing with, and I don't think that the exact dependency versions match either (case in point mercurial wasn't installed)
jhl667
@jhl667
ahh, ok, well that's a good reason
:-)
selten
@selten
I'm curious, how does https://usegalaxy.org/ handle inode usage? Or is that no issue?
Ieva
@Le_ieva__twitter
Is Galaxy slow today or is there something wrong on my end? :/
Björn Grüning
@bgruening
usegalaxy.org or another server?
pvanheus
@pvanheus
@mvdbeek I'm trying to use the https://github.com/ARTbio/GalaxyKickStart with the standard galaxy.yml and inventory as per https://gist.github.com/pvanheus/24615ececac112937b706d87dfb5b846 - but it seems to not configure supervisor - the supervisor stuff is meant to come from galaxyprojectdotorg.galaxy-os right?
pvanheus
@pvanheus
ah no - supervisor is from galaxyprojectdotorg.galaxy-extras - seems the default galaxy.yml doesn't include that.
Marius van den Beek
@mvdbeek
Right, supervisor setup is in ansible-galaxy-extras
Vahid
@VJalili
@jmchilton raising exceptions such as RequestParameterMissingException in places other than api/controller causes 500 error. Any thoughts?
Marius van den Beek
@mvdbeek
do you have an example ?
I think MessageExceptions are caught in the ErrorMiddleware, so if they don't leave galaxy that makes sense
Marius van den Beek
@mvdbeek
Sure, that makes sense, that's what the ErrorMiddleware does
but if you call this from somewhere where it doesn't pass through the middleware it won't do that
at least that's my understanding
Vahid
@VJalili
Sounds reasonable. Any suggestion for throwing exceptions behind the middleware? (e.g., in the authnz I linked)
Marius van den Beek
@mvdbeek
huh, that depends on who needs to react to the exception I guess
Vahid
@VJalili
I used to return errors to the caller api/controller. However, I think we're moving from that practice.
its the caller of API that needs to react
Marius van den Beek
@mvdbeek
like this is still going through the HTTP API ?
Vahid
@VJalili
correct
Marius van den Beek
@mvdbeek
then it should actually be caught
Vahid
@VJalili
caught in api/controller?
I think
I'm not entirely sure on this, I just recently looked into this for the py3 porting
sorry, gotta run
Vahid
@VJalili
good hint anyway, thanks.
Slugger70
@Slugger70

Hey there! I'm running Galaxy 18.05 on a server, I have a tool that creates some javascript html output which I have whitelisted. I still get

javascript is needed to display data.
If you try to view this data on galaxy please contact your administrator to authorise javascript or download the file to view.

If I donwload the file it displays no problem.. I checked the whitelist config file and the tool that produced it is listed there. FastQC works fine.

Nicola Soranzo
@nsoranzo
Does the tool id have "strange" characters?
Slugger70
@Slugger70
It has Capital letters and an underscore. "-" is in the name
And the tool id doesn't match the xml name.
Marius van den Beek
@mvdbeek
if you guys are ever debugging a bug that happens occasionally and you can't reproduce it by looping over the test it might be worth setting PYTHONHASHSEED to a couple of different values, and see if the error becomes reproducible. Definitely helped narrow down 2 bugs with random dictionary order
wish I'd known that months ago ...
scholtalbers
@scholtalbers
hey all I'm writing a test (as requested by @bgruening .. ;)) for bismark. The first tool of the bunch generates a qname_input_sorted.bam and the subsequent tools will require that as input. However, it seems galaxy will not accept this format for upload(?) - i.e. i don't know how to write a test that has this param: <param name="mapping_output" value="mapped_reads.bam" ftype="qname_input_sorted.bam"/> - the error message I get is: `An invalid option was selected for file_type qname_input_sorted please verify'
Marius van den Beek
@mvdbeek
yeah -- that's on purpose. set the uploaded filetype to qnamed_sorted.bam. qname_input_sorted.bam is for aligners that were run in galaxy and that output the reads in the order that they were read in. This isn't the official "SO:queryname", but qname_sorted.bam is compatible with qname_input_sorted.bam , so there will be no additional conversion
scholtalbers
@scholtalbers
so that would be the tool input parameter to accept format="qname_sorted.bam,qname_input_sorted.bam" or just format="qname_sorted.bam"? and for the test the input file will also be typed with format "qname_sorted.bam"?
Marius van den Beek
@mvdbeek
just qname_input_sorted.bam as parameter type (qname_sorted.bam subclasses qname_input_sorted.bam, so that would be the same as qname_sorted.bam,qname_input_sorted.bam). Correct, the test file should be qname_sorted.bam
it's a little tricky unfortunately, but that's the best that avoids unnecessary conversions while still being correct :/
scholtalbers
@scholtalbers
it is indeed, but thanks for the explanation - lets see if i can get the tests right
Marius van den Beek
@mvdbeek
in what sense ?
scholtalbers
@scholtalbers
ah sorry, still get the invalid input - just a sec and I can paste the error message
scholtalbers
@scholtalbers
u"An invalid option was selected for file_type, u'qname_sorted.bam', please verify."
Marius van den Beek
@mvdbeek
is that locally ?
(I think the PR might be missing a .shed.yml file, nothing got tested)