[galaxy-dev] Random failed job after update 18.05 -> 19.01
Hello all, After updating our galaxy instance (18.05 ->19.01) we have a strange problem. When we run or re-run a job from a history the job failed randomly. We have no errors in log file (level_log DEBUG) but in the dataset we see "cannot import name find_instance_nested" Cheers Edouard ___ 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: %(web_page_url)s To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/
[galaxy-dev] LDAP and valid username
Hi, I configure authentication with the LDAP (Active Directory) of my compagny. But the username (sAMAccoutName) contains a dot (eg : e.hirchaud). And that was a problem because the dot is not allow in galaxy username and auto-registration fails because of that. For testing I change the regex in "security/validate_user_input.py" and authorize character dot and it's work ! I know its not a good practice to change core code so I want to know if they are known "risks" or sides effects if I keep this change and if you have a best solution ? Thanks! Edouard -- Édouard Hirchaud ANSES Laboratoire de Ploufragan-Plouzané Unité Génétique Virale et Biosécurité 22440 Ploufragan Tel : (33) 02 96 01 62 71 ___ 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/
