Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 14 09:42
    simonbray opened #32
  • Apr 08 14:12
    Travis galaxy-iuc/parsec (1.15.0) passed (129)
  • Apr 08 13:21
    Travis galaxy-iuc/parsec (1.15.0) errored (127)
  • Apr 08 13:19
    Travis galaxy-iuc/parsec (master) errored (125)
  • Jun 15 2020 08:42
    pcm32 opened #31
  • Feb 03 2020 08:17
    hexylena closed #30
  • Feb 02 2020 17:13
    pvanheus opened #30
  • Oct 09 2019 19:55
    erasche closed #29
  • Oct 09 2019 19:22
    innovate-invent opened #29
  • Aug 12 2019 09:13
    Travis galaxy-iuc/parsec (1.13.0) passed (122)
  • Aug 12 2019 09:13
    erasche closed #25
  • Aug 12 2019 09:12
    erasche closed #26
  • Aug 12 2019 09:12
    erasche closed #23
  • Aug 05 2019 13:52
    bernt-matthias closed #28
  • Aug 05 2019 13:33
    erasche synchronize #26
  • Aug 05 2019 13:23
    bernt-matthias opened #28
  • Jul 31 2019 07:26
    bernt-matthias closed #27
  • Jul 30 2019 14:00
    erasche synchronize #26
  • Jul 30 2019 12:59
    bernt-matthias opened #27
  • May 15 2019 09:31
    erasche opened #26
Helena Rasche
@erasche
https://github.com/galaxy-iuc/parsec parsec 1.0.0 is out! New features include: better command structuring, updated bioblend (0.9.0), new docs, new utilities!
Manabu ISHII
@manabuishii
hello I use parsec 1.0.0 . very cool.
I want to specify path of parsec.yml , set PARSEC_GLOBAL_CONFIG_PATH is one solution.
Do you have any plan set via command line option like -f ?
And is there any plan non interactive mode support at parsec init ?
If I can , I want to use parsec init --url MYGALAXYURL --key MYKEY -f ./my.parsec.yml .
Helena Rasche
@erasche
Hi @manabuishii, those features are easy to implement! I've opened two issues for this, #12 and #13.
Manabu ISHII
@manabuishii
Thanks I start implement .
I want to replace my bioblend code with parsec .
Helena Rasche
@erasche
oh, wonderful. If you open a PR when you're done I'll be happy to make a new release
(Just seeing now that you've opened #14, thanks! This is great!)
Manabu ISHII
@manabuishii
Thanks . On my local environment , it works well .
Brad Langhorst
@bwlang
hi ... just trying out parsec... i'm using galaxy 17.05 I get this error during parsec init...: Please entry your Galaxy's URL: http://galaxy.neb.com
Please entry your Galaxy API Key: 092c57446e76725e61c6b9f629e92b59
Testing connection...
Error, we could not access the configuration data for your instance.
Do I need to enable anything in galaxy.ini? I didn't see anything ...
(in case you were worried, I just regenerated api key ... after posting it here ;)
Helena Rasche
@erasche
yes, thank you for regenning api key, was just about to say that. :)
no, you shouldn't need to enable anything
you can override the warning, maybe it will still works?
Brad Langhorst
@bwlang
hmm - tried to continue despite the error and i get AttributeError: 'module' object has no attribute 'JSONDecodeError'
do i have the URL right? need https? or trailing slash or somesuch?
Helena Rasche
@erasche
we do a "test" API call to https://fqdn/galaxy/api/configuration
Brad Langhorst
@bwlang
hmm - i don't respond to https this is an internal only server...
Helena Rasche
@erasche
http is fine
if you can curl http://galaxy.neb.com/galaxy/api/configuration from the command line, it should work
perhaps there is some networking issue where parsec is not resolving / not accessing galaxy.neb.com correctly? I assume that's internal + available to everyone on your internal network without a socks proxy or anything in the way?
Brad Langhorst
@bwlang
maybe i need to configure my proxy... that produces 401
Helena Rasche
@erasche
sounds promising!
I have to run to a meeting now, I'll be back in touch aftwards, sorry about this.
Brad Langhorst
@bwlang
no worries... i'll keep poking a bit.
Helena Rasche
@erasche
actually 401 sounds fine, probably needs an API key to access that.
anyway, back later.
Brad Langhorst
@bwlang
might be my proxy config... i think i need to allow unauthenticated access to that end point.
Helena Rasche
@erasche
you shouldn't need to
if you want auth'd access, you want auth'd access. That's just a "Is parsec working?" test, not necessary.
if you've gotten through that, try a parsec histories get_histories
Brad Langhorst
@bwlang
are you texting in your meeting ;) get_histories produces AttributeError: 'module' object has no attribute 'JSONDecodeError'
Helena Rasche
@erasche
ah both. that sounds like it's failing to access properly.