I am not using job splitting, because I am implementing this for a client
with a small (one machine) galaxy setup.
Implementing a query limit feature in galaxy core would probably be the
best idea, but that would also probably require an admin screen to edit
those limits, and I don't think I can
On Wed, Jun 18, 2014 at 12:04 PM, Jan Kanis jan.c...@jankanis.nl wrote:
I am not using job splitting, because I am implementing this for a client
with a small (one machine) galaxy setup.
Ah - this also explains why a job size limit is important for you.
Implementing a query limit feature in
Hi,
we'd like to host a version of Galaxy, but our security team have identified
some potential areas that could be subjected to attack. I was wondering if
Galaxy had mechanism in place to avoid the following issues:
Cross site scripting
Description
Cross site scripting (also referred to as
Hi Neil,
Galaxy definitely takes this sort of thing very seriously. I'll take a
look at the possible XSS locations identified in the report and verify
whether or not they're actually vulnerable.
For Denial of Service attacks, I'd suggest that this should be handled by
the upstream proxy.
You
I've filed this bug in the Twill test framework on Trello:
https://trello.com/c/XG3KemZE/1732-gzipped-input-to-twill-functional-tests-fails-with-multiple-true
Peter
On Fri, Jun 13, 2014 at 10:12 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
Hi all,
I think I've found a bug in the Galaxy
One more detail I need -- which version of galaxy was your test suite run
against?
On Wed, Jun 18, 2014 at 8:59 AM, neil.burd...@csiro.au wrote:
Thanks Dannon,
The team gave this example (regarding
XSS), Hope it helps
Example: open firefox, log into
Hmm. You are probably very similar to my setup (ubuntu 12.04, Postgres
9.1), and my Postgres install did manage to use the system timezone. I
would check two things:
1) /etc/timezone
2) run psql and execute 'show timezone;'
If those values look reasonable, then I'm out of suggestions.
-Will
On
I don't know all the subtleties of the galaxy workflow syntax. My goal
is to specify the default input file names for a number of tools in a
workflow. Is this possible, or am I limited to only providing the file
type or extension?
If possible, can you provide an example?
Thanks,
-Evan Bollig
Hi Greg,
I used the toolshed bootstrapping script and was able to get capsules from
testtoolshed to import. Here are a couple of notes that you may find
interesting.
1) In a few places you reference the directory
~/lib/tool_shed/scripts/api/bootstrap_from_toolshed/ and these should be
changed to
Thanks for the corrections Will, and I'm glad this worked for you.
Greg Von Kuster
On Jun 18, 2014, at 12:22 PM, Will Holtz who...@lygos.com wrote:
Hi Greg,
I used the toolshed bootstrapping script and was able to get capsules from
testtoolshed to import. Here are a couple of notes that
Hi All,
I am using the API (posting to 'http://localhost:8080/api/workflows' )
and running 8 workflows in a row.
I use submit function imported from common.
First call to submit takes few seconds to return from submit()
second takes a few more seconds, but in the fifth submit it gets hanged.
To clarify, I want to specify the default selected file name for an
Input Dataset block in the workflow, but I'd like to keep the option
open to select other input names with the same type.
When I specify a file type for a tool's input, it is not enough. The
input dataset can end up finding
12 matches
Mail list logo
