February 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned ARQ-1653: ---------------------------------- Assignee: Aslak Knutsen > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1653: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/35 > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1654: ---------------------------------- Summary: Expose an ExecutorService to help Extension with multithreading Key: ARQ-1654 URL: https://issues.jboss.org/browse/ARQ-1654 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.3.Final Reporter: Aslak Knutsen Expose a Service to execute Callable's and Runnable's within a Inherited context. The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. The submit(*) methods should probably be enough. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned ARQ-1654: ---------------------------------- Assignee: Aslak Knutsen > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit\(\*\) methods should probably be enough. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1654: ------------------------------- Fix Version/s: 2.0.0.Beta1 > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit(*) methods should probably be enough. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1654: ------------------------------- Description: Expose a Service to execute Callable's and Runnable's within a Inherited context. The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. The submit\(\*\) methods should probably be enough. was: Expose a Service to execute Callable's and Runnable's within a Inherited context. The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. The submit(*) methods should probably be enough. > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit\(\*\) methods should probably be enough. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1653?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1653: ------------------------------------ I have a patch in the works that fix it in Drone using a similar technique as used by the ServletProtocol; https://github.com/arquillian/arquillian-core/blob/master/container/test-... Tho, I think a long term fix is to expose a ExecutorService service in Core that can handle this internally, to avoid leaking to much impl details into the extensions. > Drone use concurrent.ExecutorService without Context inheritance on Threads > ---------------------------------------------------------------------------- > > Key: ARQ-1653 > URL: https://issues.jboss.org/browse/ARQ-1653 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.3.Final, 1.1.3.Final > Reporter: Aslak Knutsen > > Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. > Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. > https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQ-1653) Drone use concurrent.ExecutorService without Context inheritance on Threads

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1653: ---------------------------------- Summary: Drone use concurrent.ExecutorService without Context inheritance on Threads Key: ARQ-1653 URL: https://issues.jboss.org/browse/ARQ-1653 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: 1.1.3.Final, drone_1.2.3.Final Reporter: Aslak Knutsen Context's in Arquillian are bound to ThreadLocals within their lifecycle. In Core 1.0.4.Final this was changed to use InheritableThreadLocal to fix an issue with the TestFramework not finding Core when executing multiple threads. This had some unforeseen consequences and in the end reverted in 1.1.3.Final. Somewhere inbetween those versions, Drone started to use a Threaded WebDriver creation to allow timeout control. This is now failing, since the InstanceCallable is called on a 'empty' Thread. https://github.com/arquillian/arquillian-extension-drone/blob/master/dron... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-420) Port unified screenshooter implementation for Graphene into Graphene project itself

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-420?page=com.atlassian.jira.plugin... ] Stefan Miklosovic commented on ARQGRA-420: ------------------------------------------ [~lfryc] any idea where you want to put that extension in graphene source tree? I was thinking about placing it into root, besides api / impl / spi but I am not sure about your preferencies. https://community.jboss.org/message/856219#856219 > Port unified screenshooter implementation for Graphene into Graphene project itself > ----------------------------------------------------------------------------------- > > Key: ARQGRA-420 > URL: https://issues.jboss.org/browse/ARQGRA-420 > Project: Arquillian Graphene > Issue Type: Task > Components: api, build, core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Stefan Miklosovic > Fix For: 2.1-Tracking > > > Port screenshooter implementation from unified screenshooter repository, [here|https://github.com/smiklosovic/arquillian-unified-recorder/tree/mast...], > into Graphene project repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ARQGRA-423) Provide a way to intercept in some order

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-423?page=com.atlassian.jira.plugin... ] Juraj Húska updated ARQGRA-423: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/95 > Provide a way to intercept in some order > ---------------------------------------- > > Key: ARQGRA-423 > URL: https://issues.jboss.org/browse/ARQGRA-423 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.1.Final > Reporter: Juraj Húska > Assignee: Juraj Húska > > Currently all registered interceptors are invoked in non defined order. > It would be handy to provide a way how to define such order. > It is mainly because on of the Graphene interceptors: {{SearchContextInterceptor}} blocks intercepting of {{findBy}} method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2014