#galaxyproject

/

      • Arthricyn joined the channel
      • Arthricyn has quit
      • Arthricyn joined the channel
      • Arthricyn has quit
      • Arthricyn joined the channel
      • Arthricyn has quit
      • Arthricyn joined the channel
      • Arthricyn has quit
      • Arthricyn joined the channel
      • Arthricyn has quit
      • g2roboto
        [mvdbeek] @AjitPS this is not how this works. One run will not start before the next one is finished, and it will only walk the path to your tool data table files (by default somewhere in `galaxy/tool-data`). But as I mentioned, it is not very likely to be the problem, since this should happen only once during startup.
      • zipho joined the channel
      • wbla
        bgruening: I'm excited to hear that it might run under swarm-- how would that work with docker-in-docker. Last I tried this, I couldn't get it to work well in swarm... Do the SLURM/HTCondor/queue working containers support Docker-in-Docker by passing through the docker socket?
      • also, is it possible to scale windows pulsar job distribution by scaling a docker service and allowing for docker/a load balancer to pass out sessions? I know nothing about how pulsar/galaxy sessions are made/maintained throughout jobs... am I barking up the wrong tree on that?
      • shellac joined the channel
      • zipho has quit
      • Ferris has quit
      • Ferris joined the channel
      • Ferris has quit
      • Ferris joined the channel
      • g2roboto
        [bgruening] @natefoo all I can do from here is triggering a rebuild, sorry.
      • [bgruening] I did this last night, new image is here: https://quay.io/repository/bgruening/docker-jup...
      • [bgruening] just repull 17.5.1
      • guerler joined the channel
      • guerler has quit
      • shellac joined the channel
      • [glormph] Gah, why is file.extension not a valid collection identifier?
      • [glormph] In `RelabelFromFileTool`
      • [glormph] Typical uploaded file collection identifier, but in this tool it is filtered out by not matching `re.match('^[\w\-_]+$' ...`
      • [glormph] I assume there is a valid reason for this regex but if not I wouldnt mind doing a minimal PR. Including only a `\.`
      • [glormph] Otherwise not a big deal for my workflow but inconsistent with what I expected or have seen before.