[JBoss JIRA] (WFLY-12950) [EAT] Multiversion Asynchronous EJB test
by Panagiotis Sotiropoulos (Jira)
Panagiotis Sotiropoulos created WFLY-12950:
----------------------------------------------
Summary: [EAT] Multiversion Asynchronous EJB test
Key: WFLY-12950
URL: https://issues.redhat.com/browse/WFLY-12950
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Panagiotis Sotiropoulos
Assignee: Panagiotis Sotiropoulos
Multiversion Test for issue "Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-295) Credential store alias is generated from lower and upper case letter
by Farah Juma (Jira)
[ https://issues.redhat.com/browse/WFWIP-295?page=com.atlassian.jira.plugin... ]
Farah Juma commented on WFWIP-295:
----------------------------------
[~tterem] I've updated my PR to include the fix for this issue, i.e., only lower case characters and digits are now used when randomly generating an alias:
af4cbf0#diff-955e48598ef9f41cbfef3231e19871dbR128
> Credential store alias is generated from lower and upper case letter
> --------------------------------------------------------------------
>
> Key: WFWIP-295
> URL: https://issues.redhat.com/browse/WFWIP-295
> Project: WildFly WIP
> Issue Type: Bug
> Components: CLI, Security
> Reporter: Tomas Terem
> Assignee: Farah Juma
> Priority: Blocker
> Labels: cli, credential-reference, credential-store, management
>
> Credential store alias is generated from both lower and upper case letters which is unnecessary because aliases are case insensitive by default.
> When alias is generated, user is informed about the alias name and it consists of both lower and upper case characters, however, then when requested list of aliases from the credential store, it displays aliases in lower case. This could be confusing for users.
> Consider to use only lower case letters to be used for generating aliases.
> It should be only matter of changing https://github.com/wildfly/wildfly-core/pull/3925/files#diff-955e48598ef9...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-295) Credential store alias is generated from lower and upper case letter
by Farah Juma (Jira)
[ https://issues.redhat.com/browse/WFWIP-295?page=com.atlassian.jira.plugin... ]
Farah Juma edited comment on WFWIP-295 at 1/9/20 9:49 AM:
----------------------------------------------------------
[~tterem] I've updated my PR to include the fix for this issue, i.e., only lower case characters and digits are now used when randomly generating an alias:
https://github.com/wildfly/wildfly-core/pull/3925/commits/af4cbf0cec367c5...
was (Author: fjuma):
[~tterem] I've updated my PR to include the fix for this issue, i.e., only lower case characters and digits are now used when randomly generating an alias:
af4cbf0#diff-955e48598ef9f41cbfef3231e19871dbR128
> Credential store alias is generated from lower and upper case letter
> --------------------------------------------------------------------
>
> Key: WFWIP-295
> URL: https://issues.redhat.com/browse/WFWIP-295
> Project: WildFly WIP
> Issue Type: Bug
> Components: CLI, Security
> Reporter: Tomas Terem
> Assignee: Farah Juma
> Priority: Blocker
> Labels: cli, credential-reference, credential-store, management
>
> Credential store alias is generated from both lower and upper case letters which is unnecessary because aliases are case insensitive by default.
> When alias is generated, user is informed about the alias name and it consists of both lower and upper case characters, however, then when requested list of aliases from the credential store, it displays aliases in lower case. This could be confusing for users.
> Consider to use only lower case letters to be used for generating aliases.
> It should be only matter of changing https://github.com/wildfly/wildfly-core/pull/3925/files#diff-955e48598ef9...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-295) Credential reference alias is generated from lower and upper case letter
by Tomas Terem (Jira)
Tomas Terem created WFWIP-295:
---------------------------------
Summary: Credential reference alias is generated from lower and upper case letter
Key: WFWIP-295
URL: https://issues.redhat.com/browse/WFWIP-295
Project: WildFly WIP
Issue Type: Bug
Components: CLI, Security
Reporter: Tomas Terem
Assignee: Farah Juma
Credential store alias is generated from both lower and upper case letters which is unnecessary because aliases are case insensitive by default.
When alias is generated, user is informed about the alias name and it consists of both lower and upper case characters, however, then when requested list of aliases from the credential store, it displays aliases in lower case. This could be confusing for users.
Consider to use only lower case letters to be used for generating aliases.
It should be only matter of changing https://github.com/wildfly/wildfly-core/pull/3925/files#diff-955e48598ef9...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-295) Credential store alias is generated from lower and upper case letter
by Tomas Terem (Jira)
[ https://issues.redhat.com/browse/WFWIP-295?page=com.atlassian.jira.plugin... ]
Tomas Terem updated WFWIP-295:
------------------------------
Summary: Credential store alias is generated from lower and upper case letter (was: Credential reference alias is generated from lower and upper case letter)
> Credential store alias is generated from lower and upper case letter
> --------------------------------------------------------------------
>
> Key: WFWIP-295
> URL: https://issues.redhat.com/browse/WFWIP-295
> Project: WildFly WIP
> Issue Type: Bug
> Components: CLI, Security
> Reporter: Tomas Terem
> Assignee: Farah Juma
> Priority: Blocker
> Labels: cli, credential-reference, credential-store, management
>
> Credential store alias is generated from both lower and upper case letters which is unnecessary because aliases are case insensitive by default.
> When alias is generated, user is informed about the alias name and it consists of both lower and upper case characters, however, then when requested list of aliases from the credential store, it displays aliases in lower case. This could be confusing for users.
> Consider to use only lower case letters to be used for generating aliases.
> It should be only matter of changing https://github.com/wildfly/wildfly-core/pull/3925/files#diff-955e48598ef9...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (SWSQE-1039) Fix publish_jenkins_console.py
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1039?page=com.atlassian.jira.plugi... ]
Filip Brychta resolved SWSQE-1039.
----------------------------------
Resolution: Done
> Fix publish_jenkins_console.py
> ------------------------------
>
> Key: SWSQE-1039
> URL: https://issues.redhat.com/browse/SWSQE-1039
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Job Filter pattern: "[\w-]+ #\d+"
> Output Filter pattern: ""
> Jenkins Version: 2.190.2
> OrderedDict([('python-ui-test-pr', set([472])), ('upstream-pipeline', set([544])), ('build-kiali', set([871])), ('install-maistra', set([1377])), ('clean-environment', set([3240, 3241, 3242, 3239])), ('istio-kiali-mesh-checker', set([1864, 1865, 1866])), ('install-bookinfo', set([1619, 1620])), ('install-kiali-test-mesh-operator', set([881])), ('run-kiali-ui-tests-parallel', set([454])), ('run-kiali-ui-tests', set([7630, 7631, 7632, 7633, 7634, 7635, 7636, 7637, 7638, 7639, 7640, 7641, 7642, 7643, 7644, 7645, 7646]))])
> {'run-kiali-ui-tests-parallel': 'UNSTABLE', 'python-ui-test-pr': 'UNSTABLE', 'build-kiali': 'SUCCESS', 'istio-kiali-mesh-checker': 'SUCCESS', 'upstream-pipeline': 'UNSTABLE', 'clean-environment': 'SUCCESS', 'run-kiali-ui-tests': 'UNSTABLE', 'install-bookinfo': 'SUCCESS', 'install-maistra': 'SUCCESS', 'install-kiali-test-mesh-operator': 'SUCCESS'}
> Traceback (most recent call last):
> File "publish_jenkins_console.py", line 150, in <module>
> _url = _upload_console_log(_name, _ids_list)
> File "publish_jenkins_console.py", line 126, in _upload_console_log
> _url = _response.json()['url']
> File "/usr/lib/python2.7/site-packages/requests/models.py", line 897, in json
> return complexjson.loads(self.text, **kwargs)
> File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
> return _default_decoder.decode(s)
> File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> cat: /home/jenkins/agent/workspace/python-ui-test-pr/build_comment_log.md: No such file or directory
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-3879:
-------------------------------------
Description:
Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor.
>From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`.
Access to it has been "hided" behind a wrapper interface with three actual implementations:
* `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment
* `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment
* `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode).
As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place.
Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach.
Kogito-testing module is a standalone showcase that provides some minimum interaction to:
* load DMN files
* create DMN-related scesim assets, selecting one of the imported DMN.
Currently - RULE/data object model scesim is disabled.
Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset.
Some minimal tests may be done in the following way:
# full compilation (i.e. included GWT compilation) of the runtime module
# open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome
# inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid.
Some tricks: to avoid CORS and other policy-related issues:
# set chrome://flags/#allow-insecure-localhost for invalid certificates error
# start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file.
/----/
The "run scenario" functionality won't be implemented by this PR.
All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode
was:
Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor.
>From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`.
Access to it has been "hided" behind a wrapper interface with three actual implementations:
* `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment
* `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment
* `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode).
As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place.
Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach.
Kogito-testing module is a standalone showcase that provides some minimum interaction to:
* load DMN files
* create DMN-related scesim assets, selecting one of the imported DMN.
Currently - RULE/data object model scesim is disabled.
Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset.
Some minimal tests may be done in the following way:
# full compilation (i.e. included GWT compilation) of the runtime module
# open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome
# inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will create a new - empty - scesim file.
Some tricks: to avoid CORS and other policy-related issues:
# set chrome://flags/#allow-insecure-localhost for invalid certificates error
# start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file.
/----/
The "run scenario" functionality won't be implemented by this PR.
All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode
> Create Kogito version of Test Scenarios designer
> ------------------------------------------------
>
> Key: DROOLS-3879
> URL: https://issues.redhat.com/browse/DROOLS-3879
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor.
> From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`.
> Access to it has been "hided" behind a wrapper interface with three actual implementations:
> * `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment
> * `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment
> * `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode).
> As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place.
> Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach.
> Kogito-testing module is a standalone showcase that provides some minimum interaction to:
> * load DMN files
> * create DMN-related scesim assets, selecting one of the imported DMN.
> Currently - RULE/data object model scesim is disabled.
> Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset.
> Some minimal tests may be done in the following way:
> # full compilation (i.e. included GWT compilation) of the runtime module
> # open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome
> # inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid.
> Some tricks: to avoid CORS and other policy-related issues:
> # set chrome://flags/#allow-insecure-localhost for invalid certificates error
> # start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file.
> /----/
> The "run scenario" functionality won't be implemented by this PR.
> All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months