Re: [galaxy-dev] sender address of galaxy tool report
Hello, That was quite easy; Just changing: diff lib/galaxy/tools/errors.py.orig lib/galaxy/tools/errors.py 116c116 frm = to_address --- #frm = to_address 119a120,123 if email is not : frm = email else: frm = to_address Best, Remy 2015-05-06 10:28 GMT+02:00 Rémy Dernat remy...@gmail.com: Hi, We run a galaxy server locally. When a user want to send an error through galaxy GUI Report this error to the Galaxy Team . We do not have any anonymous/guest users (not allowed). So we are sure that the content of the email textbox is always effective. The problem is that we use a remote helpdesk program that is using email piping to retrieve the email and convert it to a ticket. When we want to process galaxy ticket GALAXY TOOL ERROR REPORT the sender address is always the address error_email_to from the configuration file galaxy.ini / universe.ini So we can not replay into our helpdesk program, because the answer would be send to the address error_email_to and not to the user. Is there a way to get the real email address from the user who reported the error instead of this address ? Or, if it is not possible, could it be plan in the future galaxy release ? Or, eventually, if this is easy to do, what python file should I modify ? Best regards, Remy ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] sender address of galaxy tool report
Hello Remy, Thanks for publishing your workaround. When I was in a my former position at MSI - I believe we made the same modification to Galaxy to enable this behavior I think. I have expanded your work around and made it optional with the with following commit (https://github.com/jmchilton/galaxy/commit/8a508f24c1cb1c2edf00a816e434ad9a17737877). If you test it out and it works for you - I would be happy to open a pull request to add this behavior to Galaxy core. Thanks again! -John On Thu, May 7, 2015 at 5:07 AM, Rémy Dernat remy...@gmail.com wrote: Hello, That was quite easy; Just changing: diff lib/galaxy/tools/errors.py.orig lib/galaxy/tools/errors.py 116c116 frm = to_address --- #frm = to_address 119a120,123 if email is not : frm = email else: frm = to_address Best, Remy 2015-05-06 10:28 GMT+02:00 Rémy Dernat remy...@gmail.com: Hi, We run a galaxy server locally. When a user want to send an error through galaxy GUI Report this error to the Galaxy Team . We do not have any anonymous/guest users (not allowed). So we are sure that the content of the email textbox is always effective. The problem is that we use a remote helpdesk program that is using email piping to retrieve the email and convert it to a ticket. When we want to process galaxy ticket GALAXY TOOL ERROR REPORT the sender address is always the address error_email_to from the configuration file galaxy.ini / universe.ini So we can not replay into our helpdesk program, because the answer would be send to the address error_email_to and not to the user. Is there a way to get the real email address from the user who reported the error instead of this address ? Or, if it is not possible, could it be plan in the future galaxy release ? Or, eventually, if this is easy to do, what python file should I modify ? Best regards, Remy ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
[galaxy-dev] How to get the dynamically loaded select menus to work in workflows?
Hi, We have our own local instance of Galaxy from the 15.03.2 release. I have developed a tool that works perfectly well normally but cannot get it integrated into a workflow as we would like. My tool's input form has 3 select menus that use a .loc file (using “from_file” in the options tag) to dynamically load the select options depending on the selected option in the previous field . The problem we see in the workflows happens in the following manner: For the choice of input1 (A or B), there should be a subsequent menu with options for input2 (1,2,3 or 4,5,6 respectively). The select menu input1 is automatically populated with A as this is the first option in the file, and thus the second menu is automatically populated with 1, 2, and 3. However, when you try to select B as input1 the following message is shown: An invalid option was selected for input2, u’1, please verify. The select menu for input1 is then immediately reverted back to A. I can never select B. Is there a way to get the dynamically loaded select menus to work in workflows? Many thanks. Joanna ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
[galaxy-dev] Questions about deploying galaxy on Azure
Dear developer, I’m trying to deploy the local galaxy on a VM on Azure cloud. But I have encountered a problem. When I set up the galaxy local on the cloud VM, I couldn’t find the right url to access the web interface. Can you help in any way? Regards, Marc ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/