dstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
> I just reverted the changes done to this specific file, then
>
> built the management server, stopped and started again twice, issue is not
> reproducib
ers,
Funs
> -Original Message-
> From: Likitha Shetty [mailto:likitha.she...@citrix.com]
> Sent: Thursday, July 10, 2014 5:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
&
Shetty [mailto:likitha.she...@citrix.com]
> Sent: Thursday, July 10, 2014 5:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
> Are you guys are referring to the update method that is throwing the er
From: Funs Kessen [mailto:fkes...@schubergphilis.com]
Sent: Thursday, July 10, 2014 5:10 PM
To: dev@cloudstack.apache.org
Subject: RE: "Bug" introduced by part of commit
a600d8408ea86782318139c17cf346c8497943d0
Hi Santhosh,
You're right indeed, it's the update statement in the update itself
ku...@citrix.com]
> Sent: Thursday, July 10, 2014 1:22 PM
> To: dev@cloudstack.apache.org
> Subject: RE: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
> The mentioned issue by Funs was existing earlier as well but was hidden by
> just
From: Likitha Shetty [likitha.she...@citrix.com]
Sent: Thursday, July 10, 2014 7:18 AM
To: dev@cloudstack.apache.org
Subject: RE: "Bug" introduced by part of commit
a600d8408ea86782318139c17cf346c8497943d0
Santhosh, I pulled the latest code and unfortunately the issue still exis
al Message-
From: Funs Kessen [mailto:fkes...@schubergphilis.com]
Sent: Thursday, July 10, 2014 2:38 PM
To: dev@cloudstack.apache.org
Subject: RE: "Bug" introduced by part of commit
a600d8408ea86782318139c17cf346c8497943d0
Yeah I see that Ipasted the wrong bit of code *doh*, it was
ip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Thursday, July 10, 2014 11:00 AM
> To: dev@cloudstack.apache.org
> Subject: Re: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
> Fixed already, good job Santosh
>
> Cheers,
>
&
Fixed already, good job Santosh
Cheers,
Hugo
On 10 jul. 2014, at 10:58, Hugo Trippaers wrote:
> Doesn’t seem related to that particular commit, the function
> invalidateRunSession appears to be dead code.
>
> I’ll do some digging.
>
>
> Cheers,
>
> Hugo
>
> On 10 jul. 2014, at 10:40, Fun
Doesn’t seem related to that particular commit, the function
invalidateRunSession appears to be dead code.
I’ll do some digging.
Cheers,
Hugo
On 10 jul. 2014, at 10:40, Funs Kessen wrote:
> Hi Devs,
>
> I recently noticed on master that after starting, stopping and starting the
> manageme
rgphilis.com]
> Sent: Thursday, July 10, 2014 2:10 PM
> To: dev@cloudstack.apache.org
> Cc: Daan Hoogland
> Subject: "Bug" introduced by part of commit
> a600d8408ea86782318139c17cf346c8497943d0
>
> Hi Devs,
>
> I recently noticed on master that after sta
Hoogland
Subject: "Bug" introduced by part of commit
a600d8408ea86782318139c17cf346c8497943d0
Hi Devs,
I recently noticed on master that after starting, stopping and starting the
management server again I get stacktraces about every second.
After some digging with Daan we found that p
Hi Devs,
I recently noticed on master that after starting, stopping and starting the
management server again I get stacktraces about every second.
After some digging with Daan we found that part of the
a600d8408ea86782318139c17cf346c84979943d0 commit causes this. The problem is
however deeper r
13 matches
Mail list logo
