Bug#900066: gitlab: 500 error on merge request creation

2018-05-28 Thread Simon Vetter
Thanks. I applied the update earlier this morning and can confirm that the bug is fixed. Cheers, -Simon -- Simon Vetter Embedded Software Engineer - EDF store & forecast Phone: +33 7 83 40 26 11 On 05/26/2018 03:36 PM, Salvatore Bonaccorso wrote: Hi, On Sat, May 26, 2018 at 06:25:40PM

Bug#900066: gitlab: 500 error on merge request creation

2018-05-26 Thread Salvatore Bonaccorso
Hi, On Sat, May 26, 2018 at 06:25:40PM +0530, Pirate Praveen wrote: > On Saturday 26 May 2018 03:34 PM, Simon Vetter wrote: > > Awesome, thank you for your prompt reply. > > > > In the meantime and assuming the fix is in non-compiled code (i.e. > > ruby), would you mind sharing a patch here so I

Bug#900066: gitlab: 500 error on merge request creation

2018-05-26 Thread Pirate Praveen
On Saturday 26 May 2018 03:34 PM, Simon Vetter wrote: Awesome, thank you for your prompt reply. In the meantime and assuming the fix is in non-compiled code (i.e. ruby), would you mind sharing a patch here so I can apply it and get merge requests up and running again? Sure, here is the

Bug#900066: gitlab: 500 error on merge request creation

2018-05-26 Thread Simon Vetter
Awesome, thank you for your prompt reply. In the meantime and assuming the fix is in non-compiled code (i.e. ruby), would you mind sharing a patch here so I can apply it and get merge requests up and running again? -- Simon Vetter Embedded Software Engineer - EDF store & forecast Phone: +33

Bug#900066: gitlab: 500 error on merge request creation

2018-05-26 Thread Pirate Praveen
Control: tags -1 pending On Friday 25 May 2018 09:03 PM, Simon Vetter wrote: Processing by ProjectsController#autocomplete_sources as JSON   Parameters: {"type"=>"MergeRequest", "namespace_id"=>"operations", "id"=>"ems"} Completed 200 OK in 502ms (Views: 169.8ms | ActiveRecord: 53.2ms)

Bug#900066: gitlab: 500 error on merge request creation

2018-05-25 Thread Simon Vetter
Package: gitlab Version: 8.13.11+dfsg1-8+deb9u2 Severity: normal    * What led up to the situation? I upgraded to the latest security update (8.13.11+dfsg1-8+deb9u2) and rebooted the box.    * What exactly did you do (or not do) that was effective (or ineffective)? I tried creating a new