You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Raymond Auge <ra...@liferay.com> on 2016/05/26 03:21:08 UTC
may have found a resolver bug
Hello everyone,
I'm not completely sure, but I think I have found a bug in the felix
resolver.
It's a little hard to reproduce, but I have done so in a test I've
submitted in this PR [1] to bnd (because I was trying to use the resolver
through bndlib and so it was far simpler to reproduce there).
You'll note that the travis failure is actually the test reproducing the
exact failure scenario.
The problem "seems" to stem from a scenario where a set of duplicated
resources results in miss handling of a capability index (I speculate
during the second iteration of the duplicated resource).
The issue is in resolver code that is far more complex than I have a
stomach for, but I would appreciate if someone could take a look at it.
Sincerely,
- Ray
[1] https://github.com/bndtools/bnd/pull/1472
Re: may have found a resolver bug
Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 5/26/16 08:48 , Raymond Auge wrote:
> I didn't because I wasn't sure it was even a real issue.
>
> but I can if you like.
Always a good idea, since it is more likely to get seen. Thanks.
-> richard
>
> On Thu, May 26, 2016 at 8:06 AM, Richard S. Hall <he...@ungoverned.org>
> wrote:
>
>> Did you open an issue in JIRA?
>>
>>
>> On 5/25/16 23:21 , Raymond Auge wrote:
>>
>>> Hello everyone,
>>>
>>> I'm not completely sure, but I think I have found a bug in the felix
>>> resolver.
>>>
>>> It's a little hard to reproduce, but I have done so in a test I've
>>> submitted in this PR [1] to bnd (because I was trying to use the resolver
>>> through bndlib and so it was far simpler to reproduce there).
>>>
>>> You'll note that the travis failure is actually the test reproducing the
>>> exact failure scenario.
>>>
>>> The problem "seems" to stem from a scenario where a set of duplicated
>>> resources results in miss handling of a capability index (I speculate
>>> during the second iteration of the duplicated resource).
>>>
>>> The issue is in resolver code that is far more complex than I have a
>>> stomach for, but I would appreciate if someone could take a look at it.
>>>
>>> Sincerely,
>>> - Ray
>>>
>>> [1] https://github.com/bndtools/bnd/pull/1472
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: may have found a resolver bug
Posted by Raymond Auge <ra...@liferay.com>.
https://issues.apache.org/jira/browse/FELIX-5263
On Thu, May 26, 2016 at 8:48 AM, Raymond Auge <ra...@liferay.com>
wrote:
> I didn't because I wasn't sure it was even a real issue.
>
> but I can if you like.
>
> On Thu, May 26, 2016 at 8:06 AM, Richard S. Hall <he...@ungoverned.org>
> wrote:
>
>> Did you open an issue in JIRA?
>>
>>
>> On 5/25/16 23:21 , Raymond Auge wrote:
>>
>>> Hello everyone,
>>>
>>> I'm not completely sure, but I think I have found a bug in the felix
>>> resolver.
>>>
>>> It's a little hard to reproduce, but I have done so in a test I've
>>> submitted in this PR [1] to bnd (because I was trying to use the resolver
>>> through bndlib and so it was far simpler to reproduce there).
>>>
>>> You'll note that the travis failure is actually the test reproducing the
>>> exact failure scenario.
>>>
>>> The problem "seems" to stem from a scenario where a set of duplicated
>>> resources results in miss handling of a capability index (I speculate
>>> during the second iteration of the duplicated resource).
>>>
>>> The issue is in resolver code that is far more complex than I have a
>>> stomach for, but I would appreciate if someone could take a look at it.
>>>
>>> Sincerely,
>>> - Ray
>>>
>>> [1] https://github.com/bndtools/bnd/pull/1472
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
> (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
> (@OSGiAlliance)
>
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
Re: may have found a resolver bug
Posted by Raymond Auge <ra...@liferay.com>.
I didn't because I wasn't sure it was even a real issue.
but I can if you like.
On Thu, May 26, 2016 at 8:06 AM, Richard S. Hall <he...@ungoverned.org>
wrote:
> Did you open an issue in JIRA?
>
>
> On 5/25/16 23:21 , Raymond Auge wrote:
>
>> Hello everyone,
>>
>> I'm not completely sure, but I think I have found a bug in the felix
>> resolver.
>>
>> It's a little hard to reproduce, but I have done so in a test I've
>> submitted in this PR [1] to bnd (because I was trying to use the resolver
>> through bndlib and so it was far simpler to reproduce there).
>>
>> You'll note that the travis failure is actually the test reproducing the
>> exact failure scenario.
>>
>> The problem "seems" to stem from a scenario where a set of duplicated
>> resources results in miss handling of a capability index (I speculate
>> during the second iteration of the duplicated resource).
>>
>> The issue is in resolver code that is far more complex than I have a
>> stomach for, but I would appreciate if someone could take a look at it.
>>
>> Sincerely,
>> - Ray
>>
>> [1] https://github.com/bndtools/bnd/pull/1472
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
Re: may have found a resolver bug
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Did you open an issue in JIRA?
On 5/25/16 23:21 , Raymond Auge wrote:
> Hello everyone,
>
> I'm not completely sure, but I think I have found a bug in the felix
> resolver.
>
> It's a little hard to reproduce, but I have done so in a test I've
> submitted in this PR [1] to bnd (because I was trying to use the resolver
> through bndlib and so it was far simpler to reproduce there).
>
> You'll note that the travis failure is actually the test reproducing the
> exact failure scenario.
>
> The problem "seems" to stem from a scenario where a set of duplicated
> resources results in miss handling of a capability index (I speculate
> during the second iteration of the duplicated resource).
>
> The issue is in resolver code that is far more complex than I have a
> stomach for, but I would appreciate if someone could take a look at it.
>
> Sincerely,
> - Ray
>
> [1] https://github.com/bndtools/bnd/pull/1472
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org