Retrain model from a spectral library tsv file containing custom modifications

Hi
I am trying to retrain the MS2 model using a spectral library file (tsv format) which contains a custom modification on cysteine.
Here is the output I got, it looks like most of spectra were skipped because the unknown modification. Could you help me to figure out which part I did wrong? Here I attached the ymal file and the trimmed version of the library tsv file.
Thank you very much in advance.
peptdeep_transfer_2024-01-05--11-10-14.400893.yaml.txt
NCIH_KRAS_GPF_Library_1_plus_2.report-lib_trimmed.tsv.txt
C:\>peptdeep transfer C:\Users\Chih-ChiangTsou\peptdeep\peptdeep_transfer_2024-01-05--11-10-14.400893.yaml

     ____             __  ____
    / __ \___  ____  / /_/ __ \___  ___  ____
   / /_/ / _ \/ __ \/ __/ / / / _ \/ _ \/ __ \
  / ____/  __/ /_/ / /_/ /_/ /  __/  __/ /_/ /
 /_/    \___/ .___/\__/_____/\___/\___/ .___/
           /_/                       /_/
....................................................
.                      1.1.1                       .
.       https://github.com/MannLabs/peptdeep       .
.                    Apache 2.0                    .
....................................................

2024-01-05 11:25:58> [PeptDeep] Running train task ...
2024-01-05 11:25:58> Platform information:
2024-01-05 11:25:58> system        - Windows
2024-01-05 11:25:58> release       - 10
2024-01-05 11:25:58> version       - 10.0.22631
2024-01-05 11:25:58> machine       - AMD64
2024-01-05 11:25:58> processor     - Intel64 Family 6 Model 141 Stepping 1, GenuineIntel
2024-01-05 11:25:58> cpu count     - 16
2024-01-05 11:25:58> ram           - 56.0/79.7 Gb (available/total)
2024-01-05 11:25:58>
2024-01-05 11:25:58> Python information:
2024-01-05 11:25:58> alphabase        - 1.2.0
2024-01-05 11:25:58> alpharaw         - 0.4.0
2024-01-05 11:25:58> biopython        - 1.82
2024-01-05 11:25:58> click            - 8.1.7
2024-01-05 11:25:58> lxml             - 5.0.0
2024-01-05 11:25:58> numba            - 0.58.1
2024-01-05 11:25:58> numpy            - 1.22.3
2024-01-05 11:25:58> pandas           - 1.4.2
2024-01-05 11:25:58> peptdeep         - 1.1.1
2024-01-05 11:25:58> psutil           - 5.9.7
2024-01-05 11:25:58> pyteomics        - 4.6.3
2024-01-05 11:25:58> python           - 3.10.4
2024-01-05 11:25:58> scikit-learn     - 1.3.2
2024-01-05 11:25:58> streamlit        - 1.29.0
2024-01-05 11:25:58> streamlit-aggrid - 0.3.4.post3
2024-01-05 11:25:58> torch            - 2.1.2
2024-01-05 11:25:58> tqdm             - 4.66.1
2024-01-05 11:25:58> transformers     - 4.36.2
2024-01-05 11:25:58>
2024-01-05 11:26:00> Loading PSMs and extracting fragments ...
794604 Entries with unknown modifications are removed
100%|████████████████████████████████████████████████████████████████████████████| 4052/4052 [00:01<00:00, 3027.46it/s]
2024-01-05 11:26:21> Loaded 4052 PSMs for training and testing
2024-01-05 11:26:21> Training RT model ...
2024-01-05 11:26:21> 3862 PSMs for RT model training/transfer learning
2024-01-05 11:26:21> Training with fixed sequence length: 0
[Training] Epoch=1, lr=1e-05, loss=0.13977318226049343

Hi @cctsou , in the yaml settings:
psm_modification_mapping:
      IADTB@C:
      - (IADTB)
      Oxidation@M:
      - (UniMod:35)
      Acetyl@Protein_N-term:
      - (UniMod:1)

must be changed to
psm_modification_mapping:
      IADTB@C:
      - C(IADTB)
      Oxidation@M:
      - M(UniMod:35)
      Acetyl@Protein_N-term:
      - _(UniMod:1)

Let me know if this addresses your issue:)

Hi @jalew188 , thanks, I did try that first but still, those entries were considered unknown modifications. Any suggestions?

@cctsou This is indeed a bug, I have fixed it in v1.1.3.

It's working, thanks a lot!!

A follow-up question: I was able to get the refined model and I am trying to use it to predict a new library given a FASTA file, but I encountered the following error message, it looks like it has something to do with the user-defined mod. Any clue?
`[PeptDeep] Starting a new job 'C:\Users\Chih-ChiangTsou/peptdeep/tasks/queue\peptdeep_library_2024-01-06--12-47-56.749038.yaml'...
[PeptDeep] Predicting library ...
2024-01-06 12:47:59> [PeptDeep] Running library task ...
2024-01-06 12:47:59> Input files (fasta): ['D:/fasta/test.fasta']
2024-01-06 12:47:59> Platform information:
2024-01-06 12:47:59> system        - Windows
2024-01-06 12:47:59> release       - 10
2024-01-06 12:47:59> version       - 10.0.22631
2024-01-06 12:47:59> machine       - AMD64
2024-01-06 12:47:59> processor     - Intel64 Family 6 Model 141 Stepping 1, GenuineIntel
2024-01-06 12:47:59> cpu count     - 16
2024-01-06 12:47:59> ram           - 56.2/79.7 Gb (available/total)
2024-01-06 12:47:59>
2024-01-06 12:47:59> Python information:
2024-01-06 12:47:59> alphabase        - 1.2.0
2024-01-06 12:47:59> alpharaw         - 0.4.0
2024-01-06 12:47:59> biopython        -
2024-01-06 12:47:59> click            - 8.1.7
2024-01-06 12:47:59> lxml             - 4.9.4
2024-01-06 12:47:59> numba            - 0.58.1
2024-01-06 12:47:59> numpy            - 1.26.2
2024-01-06 12:47:59> pandas           - 2.1.4
2024-01-06 12:47:59> peptdeep         - 1.1.3
2024-01-06 12:47:59> psutil           - 5.9.7
2024-01-06 12:47:59> pyteomics        - 4.6.3
2024-01-06 12:47:59> python           - 3.9.18
2024-01-06 12:47:59> scikit-learn     - 1.3.2
2024-01-06 12:47:59> streamlit        - 1.29.0
2024-01-06 12:47:59> streamlit-aggrid -
2024-01-06 12:47:59> torch            - 2.1.2
2024-01-06 12:47:59> tqdm             - 4.66.1
2024-01-06 12:47:59> transformers     - 4.36.2
2024-01-06 12:47:59>
2024-01-06 12:48:01> Using external ms2 model: 'C:/Users/Chih-ChiangTsou/peptdeep/refined_models/ms2.pth'
2024-01-06 12:48:01> Using external rt model: 'C:/Users/Chih-ChiangTsou/peptdeep/refined_models/rt.pth'
2024-01-06 12:48:01> Using external ccs model: 'C:/Users/Chih-ChiangTsou/peptdeep/refined_models/ccs.pth'
2024-01-06 12:48:01> xxx/library.tsv does not exist, use default IRT_PEPTIDE_DF to translate irt
2024-01-06 12:48:01> Generating the spectral library ...
2024-01-06 12:48:01> Loaded 17865 precursors.
2024-01-06 12:48:01> Predicting RT/IM/MS2 for 16892 precursors ...
2024-01-06 12:48:01> Using multiprocessing with 16 processes ...
2024-01-06 12:48:01> Predicting rt,mobility,ms2 ...
0%|                                                                                | 0/31 [00:15<?, ?it/s]
2024-01-06 12:48:18> multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "multiprocessing\pool.py", line 125, in worker
File "peptdeep\pretrained_models.py", line 914, in _predict_func_for_mp
return self.predict_all(
File "peptdeep\pretrained_models.py", line 1084, in predict_all
self.predict_rt(precursor_df,
File "peptdeep\pretrained_models.py", line 877, in predict_rt
df = self.rt_model.predict(precursor_df,
File "peptdeep\model\model_interface.py", line 388, in predict
features = self._get_features_from_batch_df(
File "peptdeep\model\rt.py", line 161, in _get_features_from_batch_df
self._get_mod_features(batch_df)
File "peptdeep\model\model_interface.py", line 812, in _get_mod_features
get_batch_mod_feature(batch_df)
File "peptdeep\model\featurize.py", line 86, in get_batch_mod_feature
mod_features_list = batch_df.mods.str.split(';').apply(
File "pandas\core\series.py", line 4757, in apply
return SeriesApply(
File "pandas\core\apply.py", line 1209, in apply
return self.apply_standard()
File "pandas\core\apply.py", line 1289, in apply_standard
mapped = obj._map_values(
File "pandas\core\base.py", line 921, in _map_values
return algorithms.map_array(arr, mapper, na_action=na_action, convert=convert)
File "pandas\core\algorithms.py", line 1814, in map_array
return lib.map_infer(values, mapper, convert=convert)
File "lib.pyx", line 2926, in pandas._libs.lib.map_infer
File "peptdeep\model\featurize.py", line 87, in
lambda mod_names: [
File "peptdeep\model\featurize.py", line 88, in
MOD_TO_FEATURE[mod] for mod in mod_names
KeyError: 'IADTB@C'
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "peptdeep\pipeline_api.py", line 416, in generate_library
lib_maker.make_library(lib_settings['infiles'])
File "peptdeep\spec_lib\library_factory.py", line 105, in make_library
self._predict()
File "peptdeep\spec_lib\library_factory.py", line 68, in _predict
self.spec_lib.predict_all()
File "peptdeep\spec_lib\predict_lib.py", line 121, in predict_all
res = self.model_manager.predict_all(
File "peptdeep\pretrained_models.py", line 1127, in predict_all
return self.predict_all_mp(
File "peptdeep\pretrained_models.py", line 964, in predict_all_mp
for ret_dict in process_bar(
File "peptdeep\utils.py", line 27, in process_bar
for i,iter in enumerate(iterator):
File "multiprocessing\pool.py", line 870, in next
KeyError: 'IADTB@C'
'IADTB@C'`


Not providing view options makes cursor reset after every input

Describe the bug
If you don't provide view options, the editor only lets you input once at a time before it resets and puts your cursor back to the start of the line you're on.
To Reproduce
Steps to reproduce the behavior:

In the sandbox, remove the view property from the options object.
Put your cursor somewhere that isn't at the start of a line
Press any input key (character, backspace, etc)
Cursor resets to the start of the line

Expected Behavior
Either fill in the default options if they are not provided in a way that doesn't cause the editor to fully reload with every change (my personal preference and what I would expect to happen as "options" are usually providing things that differ from default), or make the view property mandatory (and please provide an example of how to provide the default settings in the TSDoc so we aren't guessing).
Thanks!
Tested on platform editor.

Fixed in PR #143.


[enhancement]: AnimateDiff support

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Ability to create animation with AnimateDiff or with same technology
Alternatives
AnimateDiff extension for Automatic1111
Additional Content
No response

Agreed, would be awesome!
Closing this as it's a duplicate of #4477


code in document 11.2 has not update

Code in document use HttpClient, but project code has turn to WebClient.

Here is a related mail I've received:

I would like to notify you about your tutorial on Vert.x here http://escoffier.me/vertx-hol/#_task_coordinating_async_methods_and_consuming_http_endpoints_portfolio_value_evaluation
that maybe there is a slight error.
In this code snippet:
HttpEndpoint.getClient(discovery, new JsonObject().put("name", "quotes"), (1)
client -> {
if (client.failed()) {                                                     (2)
// It failed...
resultHandler.handle(Future.failedFuture(client.cause()));
} else {
// We have the client
HttpClient httpClient = client.result();                                 (3)
computeEvaluation(httpClient, resultHandler);
}
});
The compiler complains that the discovery field is not the type it supposed to be and offers me to cast it to like this:
HttpEndpoint.getClient((io.vertx.rxjava.servicediscovery.ServiceDiscovery) discovery, new JsonObject().put("name", "quotes"),
...
});
or in other words, from type io.vertx.servicediscovery.ServiceDiscovery to type io.vertx.rxjava.servicediscovery.ServiceDiscovery.
So far, I am following the tutorial as described. Can you please look at it when you have time? To see if I am doing something wrong, or the tutorial at this point should be redacted.


Gutter visualization displaying statement values

Populate the code editor gutter with the value of the corresponding line provided by the Trace.

I believe this is implemented given the state of the current gutter


Cannot create a model anymore

Describe the bug
I just downloaded the newest Modeler release (5.4.1) as dmg. I opened up the application and tried to create a new Camunda 8 BPMN file. This led to an exception being thrown. I have tried to repeat creating an new BPMN file without success.
This image contains further information

[diagram_1.bpmn] this.getModeler(...).get(...).setErrors is not a function     at setErrors (webpack://camunda-modeler-client/src/app/tabs/cloud-bpmn/BpmnEditor.js:181:39)     at componentDidUpdate (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:216:295)     at Vh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:220:181)     at file:///Applications/Camunda%20Modeler.app/Contents/Resources/app.asar/public/bundle.js:2:1616732     at b (webpack://camunda-modeler-client/node_modules/scheduler/cjs/scheduler.production.min.js:18:162)     at unstable_runWithPriority (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:250:202)     at Fi (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:249:382)     at Di (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:248:143)     at Yh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:245:331)     at Xh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:243:85)     at qf (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:130:227)     at enqueueSetState (webpack://camunda-modeler-client/node_modules/react/cjs/react.production.min.js:13:223)     at setState (webpack://camunda-modeler-client/src/app/App.js:900:9)     at setLintingState (webpack://camunda-modeler-client/src/app/App.js:877:9)     at async file:///Applications/Camunda%20Modeler.app/Contents/Resources/app.asar/public/bundle.js:2:2820929 [ error ] This error may be the result of a plug-in compatibility issue. [ info ]
I have got three plugins installed:

Though I have no possibility to disable them through the Desktop Modeler.
Steps to reproduce

Install the Plugins for a future version of the Desktop Modeler
Update the Desktop Modeler to version (5.4.1)
Try creating a new BPMN diagram

Expected behavior
Of course I would expect the Modeler to create a new bpmn file. In case this is due to a plugin my expectation is to see which one is responsible for this error.
Environment

OS: MacOS 12.6
Camunda Modeler Version: 5.4.1
Execution Platform: Both are not working
Installed plug-ins: Token Simulation, Linting, Migration

Additional context
No response

Update: It seems to be caused by the linting plugin

The linter plugin which you linked was replaced in Camunda Modeler 5.3+ with a built-in linter. You need to remove it if you want to use v5.4.1 of the app. If you want to use custom lint rules, check out this repo https://github.com/camunda/camunda-modeler-custom-linter-rules-plugin


Reset Finder appearance in Admin playbook

Someone switched one of our admin accounts to grey. Switch it back to defaults.

Might have been an app called "DockMod" kill that too.


[Feat] Enable external serving of Vizro assets

Description

Change our weird (but remarkably effective) flask blueprint scheme for serving Vizro assets into a more conventional Dash library scheme for handling resources
This makes it possible to serve all our resources through the CDN when serve_locally=False (previously this was possible only for the library CSS, which was just figures.css)
Fix serving of fonts, which previously was putting extraneous <link rel="stylesheet"> in our HTML source
Update JS so that it works in-browser without being a module - this is needed due to the new way assets are served

To do:

[ ] @antonymilne: maybe write unit tests
[ ] @antonymilne: check https://vizro--775.org.readthedocs.build/en/775/pages/user-guides/run/
[ ] @huong-li-nguyen: manual test + make sure you understand how everything works with the following - I've already done the first two but good to have a second pair of eyes on it. Please check the 404 page on these and also that the order of CSS is ok since I didn't check that.

[ ] serve_locally=True Vizro app (try it disconnected from Internet)
[ ] serve_locally=False Vizro app
[ ] serve_locally=True Dash app using Vizro library
[ ] serve_locally=False Dash app using Vizro library (less important to test, because it's an edge case and also if the above work then I'm confident this does too)

Notes (will go in updated developer docs)
When serve_locally=True (the default), Dash serves component library resources (generally CSS and JS) through the Flask server using the _dash-component-suites route.

For Vizro library components (currently just KPI cards), this should happen when Vizro is imported.
For Vizro framework components (everything else), this should happen only when Vizro() is instantiated.

This makes our footprint as small as possible and ensures there's reduced risk of CSS name clash when someone wants to use Vizro just as a library but doesn't instantiate Vizro() (not common at all now, but maybe will be in the future).
When serve_locally=True, Dash switches to serving resources through external_url, where it's specified. For Vizro components we use jsDeliver as a CDN for this.
A few complications:

files that aren't CSS/JS (e.g. fonts, maps) can still be served through the same routes but should not have a


[WFCORE-5147] Adjusting git integration logging and stability of RemoteSshGitRepositoryTestCase

https://issues.redhat.com/browse/WFCORE-5147
The RemoteSshGitRepositoryTestCase test case was quite unstable on a resource constrained environment, the test was dependent on monitoring the server.log for an error message but it appears the git integration may log the error in a separate thread so I believe the process can be terminated before the message is logged.
Attempting to debug the issue I realised the test case was not properly restoring the default server configuration between test as attempts to add additional logging categories were being overridden.
Finally we were not logging useful information ourselves, although log and throw can be a bad practice at the moment the uncaught exception only made it's way to System.err - the problem with this was if you are reliant on the server.log the messages would be missing.

I think we need to think about how far we want to go with these kinds of review, the majority of this change is related to some opportunities I have seen to improve the logging situation of something that is difficult to debug which could also be a problem if we need to debug this remotely.
The issue here is it is not an are of code I am not likely to directly support myself.  Two weeks after submitting my PR to clean something up where I have seen some opportunities to improve logging I suddenly receive a lot of comments which are largely cosmetic.
Just as I did whilst working on the changes the module definition for the classes with the changed visibility could have been opened to see we already declare all these classes as private API:
<module xmlns="urn:jboss:module:1.8" name="org.jboss.as.server">
    <properties>
        <property name="jboss.api" value="private"/>
        <property name="jboss.require-java-version" value="1.8"/>
    </properties>

Regarding the name of an existing variable in the test suite that should have been static all along, sure it is correct it should be in upper case but it is also a private test variable.
The discussion about test clean up is worthwhile but it is quick to confirm that the clean up already happens after each test.
One point not picked up was the Temp commit that had crept in so I am quickly addressing that now.
But overall with PRs such as this I think we really need to ask if the code changes have improved the codebase or introduced a problem, ideally all engineers should be able to quickly submit PRs to clean things up especially around missing logging - but if these come back to you two weeks later so you have to context switch back to them it risks the individual engineer asking the question "Is it worth MY time to clean this up?".
Note:  This is not the first PR like this, this is just the most recent one where I have stopped my planned work to come back to.

Core - Full Integration Build 10113 outcome was FAILURE using a merge of e9acb6962cf0782310df8c197502a7186a130d50
Summary: Tests failed: 13 (13 new), passed: 7060, ignored: 109 Build time: 02:37:14
Failed tests
org.jboss.as.test.manualmode.messaging.ha.ReplicatedNettyFailoverTestCase.testBackupFailoverAfterFailback: javax.naming.NameNotFoundException: jms/RemoteConnectionFactory -- service jboss.naming.context.java.jboss.exported.jms.RemoteConnectionFactory
	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
	at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
	at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1280)
	at java.lang.Thread.run(Thread.java:748)
------- Stdout: -------
 [0m12:58:47,516 INFO  [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final
 [0m [0m12:58:47,750 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
 [0m [0m12:58:47,759 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m12:58:47,857 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 22.0.0.Beta1-SNAPSHOT (WildFly Core 14.0.0.Beta2-SNAPSHOT) starting
 [0m [0m12:58:48,745 INFO  [org.wildfly.security] (ServerService Thread Pool -- 29) ELY00001: WildFly Elytron version 1.13.1.Final
 [0m [0m12:58:49,579 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m12:58:49,639 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 13) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m12:58:49,764 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m12:58:49,779 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.8.2.Final
 [0m [0m12:58:49,784 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.8.2.Final
 [0m [0m12:58:49,823 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 58) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m12:58:49,835 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 64) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.2.5
 [0m [33m12:58:49,843 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 86) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m12:58:49,847 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 73) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
 [0m [0m12:58:49,858 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 50) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m12:58:49,871 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 83) WFLYSEC0002: Activating Security Subsystem
 [0m [0m12:58:49,874 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 71) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m12:58:49,867 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 75) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m12:58:49,869 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 77) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m12:58:49,878 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m12:58:49,883 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.19.Final
 [0m [0m12:58:49,885 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 88) WFLYWS0002: Activating WebServices Extension
 [0m [0m12:58:49,903 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
 [0m [0m12:58:49,912 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 74) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
 [0m [0m12:58:49,915 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
 [0m [0m12:58:49,919 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 60) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m12:58:49,939 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 61) WFLYRS0016: RESTEasy version 3.13.2.Final
 [0m [0m12:58:49,942 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 67) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m12:58:49,951 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m12:58:49,953 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 2.2.2.Final starting
 [0m [0m12:58:50,004 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 72) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
 [0m [0m12:58:50,062 INFO  [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service
 [0m [0m12:58:50,084 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m12:58:50,215 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/manualmode/target/jbossas-messaging-ha-server1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m12:58:50,221 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testJsfWorks: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".CdiValidatorFactoryService",
            "jboss.deployment.unit.\"test.war\".WeldStartService",
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".CdiValidatorFactoryService",
            "jboss.deployment.unit.\"test.war\".WeldStartService",
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".WeldInstantiator",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedArchiveDeployment: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedArchiveDeployment(MixedDomainDeploymentTest.java:202)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testDeploymentViaStream: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:404)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:190)
------- Stdout: -------
[Host Controller]  [0m [0m13:41:41,158 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/mixed-domain/target/domains/MixedDomain700TestSuite/master/data/content/4d/5dbf47d483dbf01b1ea3906c626040a3d90b5c/content [0m
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testRedeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:404)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:190)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testRedeploy(MixedDomainDeploymentTest.java:306)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedRedeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:214)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedRedeploy(MixedDomainDeploymentTest.java:322)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUndeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:404)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:190)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUndeploy(MixedDomainDeploymentTest.java:282)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedUndeploy: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:214)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedUndeploy(MixedDomainDeploymentTest.java:298)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testReplace: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:404)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaStream(MixedDomainDeploymentTest.java:190)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testReplace(MixedDomainDeploymentTest.java:330)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testDeploymentViaUrl: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testDeploymentViaUrl(MixedDomainDeploymentTest.java:177)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true

org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite: org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainDeployment700TestCase.testUnmanagedExplodedDeployment: java.lang.AssertionError: {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
java.lang.AssertionError:
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"other-server-group" => {"host" => {"slave" => {"server-one" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.test.test.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"],
    "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.deployment.unit.\"test.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.faces.webapp.FacetTag\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
            "jboss.deployment.unit.\"test.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
            "jboss.deployment.unit.\"test.war\".deploymentCompleteService",
            "jboss.deployment.unit.\"test.war\".jndiDependencyService",
            "jboss.undertow.deployment.default-server.default-host./test",
            "jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService"
        ],
        "Services that may be the cause:" => [
            "jboss.clustering.singleton.server.default",
            "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
        ]
    }
}}}}}}}}}
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:266)
	at org.jboss.as.test.integration.domain.management.util.DomainTestSupport.validateResponse(DomainTestSupport.java:258)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.executeOnMaster(MixedDomainDeploymentTest.java:400)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.testUnmanagedExplodedDeployment(MixedDomainDeploymentTest.java:214)
------- Stdout: -------
Failed response:
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "rolled-back" => true

##### there are 3 more failed tests, see build details

Retest this please


ipc_service: Automatically include source files for backends

The purpose of this change is to allow to enable more than one
backend at once.
The outcoming changes include:

removal of choice option for IPC backends Kconfig
removal of ZTEST backend
removal necessity of explicitly specifying backend
move IPC_SERVICE_NUM_ENDPOINTS_PER_INSTANCE option
to Kconfig.rpmsg (+rename)
dependency to rpmsg backend specific options (this allows to
hide those options when backend is not configured in DT)
automatical source file inclusion for chosen backend (now depends
on DT configuration)
clean up of samples and Kconfig files that were explicitly chosing
STATIC_VRINGS as backend

Signed-off-by: Emil Obalski<EMAIL_ADDRESS>

Hi @kapi-no. I would like to kindly ask you to have a look here. I'm changing some things you've recently added. I think we don't need to explicitly select backends and this could be done as presented.
@e-rk if possible, could you verify if this suits you as well and if it affect your work in any significant way?
@carlocaione Those are the changes we discussed offline some time ago, please fell free to speak out.

can you please split the BT changes from the general IPC ones in two separate commits?

IPC service won't work on 1st commit then. Are you sure about that? This change is pretty simple. I can do it but is there much need for that?

Force pushed with changes + rebase due to conflicts.

Removed depends on mentioned by @carlocaione and @nordic-krch  - see reviews above.
Split removal of configuration options from samples to separate commit as it doesn't break anything.

Rebased due to conflicts.


python 2 support

I'm wondering if it's time to stop supporting superset on python 2. I created by mistake a virtualenv with python2 instead of python3 and sqllab does not work at all when non ascii encodable data is used. It breaks in the loggers, it breaks when poking with dataframes.
So given that airbnb is on python3 and tests does not catch any encoding issue is it time to stop supporting it?

Python 2.7 is there to stay. In many environments people might now have the luxury to choose.
We use it in production at Airbnb. We  could run 3.4 or 3.5 if we wanted but we'll probably make the switch when our standard images use distros that ship py3 by default.
So even though it reduce the surface for bugs, we're not dropping py2.7 support, I don't think there's a lot of projects that are doing that at the moment.
I'm not sure what your exact issues were, but most likely something that's easy to fix across the board with some environment (or perhaps database connection) setting.

An easy reproducer for sqllab breaking with python2.7 is something like over a table from the examples:
select 'ኴ' from anexampletable;

Closing then.

Another fact that should be kept in mind:
python-ldap is not available for python3.
LDAP-auth is the sole reason why we run superset in a python2.7 venv.

@rumbin except you can upgrade :) https://github.com/pyldap/pyldap.

@xrmx thanks for pointing me to pyldap, it seems to work well!


Development documentation

Description
This pull request update the documentation.
Fixes #1316
Type of change
Please check all relevant options.

[x] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Codecov Report

Merging #1319 (d54576e) into dev_1.8.0 (31f7931) will decrease coverage by 58.40%.
The diff coverage is 80.00%.

:exclamation: Current head d54576e differs from pull request most recent head 72313ec.


Wrong number of pods for job with coefficient parallelism.

My 4 worker nodes have 8 vcpus each. I want to spread my data so that each CPU takes charge of a worker (pod) , so I set a coefficient of 8. However, the job only created 16 pods in kubernetes ( i expected 32) Any ideas about why is this?

This was reported for 1.3.16 but it seems like it should apply to 1.4 as well since the code hasn't changed much.

More info from the user:

I asked @jdoliner yesterday. He said: I’d try again with the constant field set to 32 and see if maybe that gets you a sane result, we’re going to have to run some tests and see if we can reproduce what you’re seeing here.
In that case, the same thing happened. 16 pods

+1

Tested it with 1.4 stable release. Now it seems to work better. However, instead of creating 32 (8vcpus*4worker nodes), i see that it created 48 pods (presumably 8 vcpus * 6 nodes including the 2 edge nodes ). Any ideas about this? I think it is desirable that they would only be scheduled in the worker nodes.

Dupe of #1547 afaict


piano keys edited wrt issue #3781

I have resolved issue #3781. @kunjgit kindly review it and accept the pr.

Thank you @bhumika-1127 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @bhumika-1127 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀

/assign


Code storage by hash

PR description
Storing code by hash instead of by address. This is needed so that Besu can serve snapsync as we need to be able to retrieve the code by hash.

Added two new column families. The CODE_STORAGE_BY_HASH stores code by code hash. The CODE_HASH_COUNT stores a count of how many times code is stored for self-destruct. Once the count reaches zero we can actually delete the code.
Added compatibility for existing code storage and new code storage mode. The existing code storage mode will be used if there are already values in the CODE_STORAGE column family. This compatibility is handled by having a CodeStorageStrategy with implementations for both modes used by the FlatDbStrategy
Add rockdb get to transactions so that any pending updates for storing code changes in the same transaction are updated correctly
Changed WorldStateStorage.getCode to take the codeHash using Hash type to be consistent with usage elsewhere. This added a few more changes to files than I expected. So could take this out of the PR if it makes it easier to review.

After syncing with this change it's not possible to downgrade to an older version of Besu. If we think this is needed I could add a subcommand to do the conversion.
Testing

Checkpoint sync on Sepolia, Goerli and Mainnet
Confirmed the same code bytes were stored for both column families by running a comparison tool on the stored code bytes https://github.com/hyperledger/besu/pull/6019/files#diff-9c4d660b9f0b067bbaf230c40ff79f2a53fef78e88c0c5e368b43e3891d0f68bR227
Compatibility testing to ensure that existing databases continue to work
Compared storage of code size on mainnet. Before: 9 GiB After: 2GiB. Column family to store code counts i.e. CODE_HASH_COUNT is using 38 MiB.
Compared FCU and new payload times on mainnet with and without code changes showing no significant difference in times

Fixed Issue(s)

fixed #5388

Looks pretty good so far. Mostly just some questions and naming...
What regression testing has been done for FOREST mode?
Will the new column families only be created for BONSAI mode - i.e. there should be no impact when downgrading a FOREST database?

The new columns should only exist for BONSAI mode. There is no impact on FOREST as the existing column CODE_STORAGE also only applies to BONSAI.

Reminder to revisit count

@matkt @garyschulte Ready for another review when you get a chance. I've changed the PR to reuse the existing CODE_STORAGE column family instead of introducing two new column families and have added a --Xsnapsync-server-enabled to toggle the functionality.

It looks like we are going to be deleting code by hash in this impl rather than leaving it as we discussed on discord?
A few minor requested changes, generally LGTM

It looks like we are going to be deleting code by hash in this impl rather than leaving it as we discussed on discord?
A few minor requested changes, generally LGTM

Where I thought we got to was that by default we would delete code as that would be the best option for most users. But have a config option to not delete as the only case we wouldn't want to delete would be if we needed it for a future optimised tracing call. Didn't add that to this PR as it was getting quite messy with adding all the config options I thought I could do that in another PR once I had the mess sorted out. But at this point maybe yet another param isn't such an issue.

It looks like we are going to be deleting code by hash in this impl rather than leaving it as we discussed on discord?
A few minor requested changes, generally LGTM

It looks like we are going to be deleting code by hash in this impl rather than leaving it as we discussed on discord?
A few minor requested changes, generally LGTM

Where I thought we got to was that by default we would delete code as that would be the best option for most users. But have a config option to not delete as the only case we wouldn't want to delete would be if we needed it for a future optimised tracing call. Didn't add that to this PR as it was getting quite messy with adding all the config options I thought I could do that in another PR once I had the mess sorted out. But at this point maybe yet another param isn't such an issue.

Changed agreed on from DM,

On deleting code. Add that extra flag to disable deleting code. Will be enabled by default as is best for the majority of users
Removing the --Xsnap-sync-server-enabled flag and adding a feature flag for this feature instead so it's not confusing with snap server needing to be enabled

Not a fan of leaking bonsai config into storage interfaces, but in the interest of expedience and to limit the PR scope, 🚢 and we can fast-follow with a storage option config encapsulation pr

Don't like it either. But I think the alternative is to do some refactoring around how the BonsaiWorldStateKeyValueStorage gets initialised. Would like to clean that up. But prefer to do that in another PR so this PR doesn't get any bigger.

💯 🚀


PERF102 - False Positive with Poorly Named Variables

-                    for (i, j), _ in smat.items():
+                    for (i, j) in smat.keys():
                         diag_entries[(i + rmax, j + cmax)] = _

This code snippit is from sympy/matrices/common.py, this uses the latest stable ruff version and just has PERF102 manually selected using the command ruff --select PERF --fix .
I know that the _ prefix is often used to look for variables that should be unused in a loop, but ruff should check if the variable is actually unused before autofixing it to prevent bugprone autofixes. It should at least handle this trivial case.

Yeah we can support this.

Wow that's madness :) We should add a rule that checks for usage of _ outside of unpacking!

Yeah, I've seen this kind of usage in the wild especially in comprehensions for one off variables.

crates/ruff/src/rules/flake8_bugbear/rules/unused_loop_control_variable.rs is a similar rule (it detects unused loop control variables more generally) that we can use as a reference.


Format PHP according to PHP Style Guide

https://gist.github.com/ryansechrest/8138375

Remember to update variable names for consistency

Completed updating variable names: https://gist.github.com/ryansechrest/8138375#7-variables


Predictor with StyleTransferTranslator multiple Inputs not working

Hello, I have exported a style transfer model with torch script and I am trying to get it to run in java.
The Model expects 2 inputs, a content image and a style image.
Trying to run with 2 inputs:

As you can see 2 inputs are expected.

So how can I run the predictor with both necessary inputs?

I suspect that the signature for StyleTransferTranslator is not right for your model then. That Translator expects that the model accepts only a single image.
If you need two images as inputs, you may need to make your own Translator implementation. Then, it could have a type which is something like a Translator<MyStyleTransferInputClass, Image> or Translator<Pair<Image, Image>, Image>.

Yeah it worked that way, thanks.
But I am confused why the StyleTransferTranslator does not support multiple inputs since every style transfer needs content and style Image.

I believe it was that one version of style transfer would train one model for each style. Then, you just need to pass the content image into the Monet model and it would return the Monet styled image


Support for mikel/mail 2.8.1?

I take it this patch of mikel/mail is still required to support iso-2022-jp? If so, may we have permission to open PRs to help move support along for mikel/mail 2.8.1?

@alduethadyn
Yes, please.


Add tests for new GRPC disconnect handling logic

Motivation
Follow up to #5469. This adds unit tests to assert that in the event of a connection drop or error the correct events and logs are emitted.
Changes
Added tests for various scenarios:

proof -> complete
proof -> fail
proof -> disconnect & reconnect -> complete
proof -> disconnect -> fail to reconnect

Test Plan
new tests
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge


Fix sync issue on atsign reset

- What I did

Sync the local changes to server when server is reset.
Refactor the sync_service_impl.dart file to write unit test
Write unit test for server reset scenario.

NOTE: **sync_service_impl supersedes the sync_manager.dart. The changes to sync_manager are made only to avoid compile time issue. sync_manager.dart is not in use.
- How I did it
If localCommitId is greater than serverCommitId indicates server is reset (In other conditions localCommitId is either equal or less than serverCommitId). then set localSeqNumber to serverCommitId to get all the changes to sync to server.
- How to verify it
Pair the atsign in mobile app and reset the server. Upon activation the data should be sync'ed back to server.
- Description for the changelog

@gkc : Can you please let me know if we can close this PR?

@kalluriramkumar : Please close whenever you wish. @VJag has started a document to talk about desired behaviour in all of the different possible reset / data loss scenarios. That document should include a reference to this PR.

Sure Gary, Thank you.


[spirv-headers] Update to latest version and properly installing the target

Describe the pull request

What does your PR fix?
Actually configures, builds and installs the spirv-headers target

Which triplets are supported/not supported? Have you updated the CI baseline?
All

Does your PR follow the maintainer guide?

Yes

Thanks!


Background music in The Question is playing as mono

When I play res://game/illurock.ogg in editor is playing as stereo, but in game is playing as a mono.
When I open it in Audacity I saw that it was mono so I change it to stereo as res://game/illurock-stereo.ogg and set to it as stream of $BGMusic in res://game/scenes/Start/start.tscn.
But it still plays as mono in game :disappointed:
Realted files:

https://github.com/rakugoteam/Rakugo/blob/the-question-1.2/game/scenes/Start/start.tscn
https://github.com/rakugoteam/Rakugo/blob/the-question-1.2/game/illurock-stereo.ogg
https://github.com/rakugoteam/Rakugo/blob/the-question-1.2/game/illurock-stereo.ogg.import
https://github.com/rakugoteam/Rakugo/blob/the-question-1.2/default_bus_layout.tres

I will try different backgournd music

I fix it by chaning type of BGMPlayer to RakugoAudioPlayer
And change pause_mode to process.


Closure Editor - Issue with "OUTDENT" functionality

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=154

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Gesture events not working.

Ionic version:  (check one with "x")
[ ] 1.x
[X] 2.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Gesture events mentioned in the docu (https://ionicframework.com/docs/v2/components/#gestures) do not work for me. Rotate and pinch events don't seem to get triggered. Tap, press, swipe and pan work fine. This problem occurs on Android and Web, other platforms not tested. I'd expect this simple example to work - is it not supposed to?
Related code:
html
<ion-content padding
    (tap)="tapHandler($event)"
    (press)="pressHandler($event)"
    (swipe)="swipeHandler($event)"
    (rotate)="rotateHandler($event)"
    (pinch)="pinchHandler($event)">
</ion-content>

controller
    tapHandler(args) {
        alert('tap');
    }
    pressHandler(args) {
        alert('press');
    }
    swipeHandler(args) {
        alert('swipe');
    }
    rotateHandler(args) {
        alert('rotate');
    }
    pinchHandler(args) {
        alert('pinch');
    }

gesture event "pinch"  do not work also using import { Gesture } ....

Ok, same for the rotate event I assume? Maybe this should be mentioned in the docu, the way it is listed right now seems misleading to me.

I use Gesture directly and got pinch event.
But most event triggered at the wrong time.
Some events delay and then all delayed event will trigger when next touch.

@iron9light I met the same question these daya,  did u have any solutions?

@iron9light  @iron9light  Hey, I met the same question these days, did u have any solutions?

@JasonZzs No. I just gave up

@iron9light  ok....it's really a pitty;


Update with management code sample

@simonaco,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/relay.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

needs review before #sign-off

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/relay.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/relay.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/relay.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/relay.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

LGTM
#sign-off


Update Get-SafeLinksAggregateReport.md

@chrisda

Docs Build status updates of commit 75be8e8:
:clock10: Full build: the average full build time is 17 min(s) 34 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 75be8e8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 42d4282:
:clock10: Full build: the average full build time is 17 min(s) 34 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 42d4282:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Use tts from pyhelper-utils - 592

[Auto generated]
Number: [#592]

openshift-cli-installer(gtPiG)[PR 592]: Closing issue for PR: Use tts from pyhelper-utils.
PR was closed.


Dynamic route vars silently shadow all other vars

Thanks for fixing. Here is my broken almost minimal example:
import reflex as rx

app = rx.App()

class State1(rx.State):
    redirect_to: str | None = None
    redirect_me: str | None = None

    def on_load(self):
        self.redirect_to = self.router.page.params.get("redirect_me")
        self.redirect_me = self.router.page.params.get("redirect_me")
        print(self)
        return rx.redirect(f"/{self.redirect_me}")

@rx.page(route="/goto/[redirect_me]", on_load=State1.on_load)
def goto() -> rx.Component:
    return rx.box(
        rx.text("Redirecting..."),
    )

@rx.page(route="/page2")
def page2() -> rx.Component:
    return rx.box(
        rx.heading("Page 2"),
        rx.text("This is page 2"),
        rx.el.pre(
        rx.text(f"Different name from route param  >>{State1.redirect_to}<<"),
        rx.text(f"Same name as route param is gone >>{State1.redirect_me}<<"),
        )
    )

def index() -> rx.Component:
    return rx.box(
        rx.heading("Hello, Reflex!"),
        rx.text("This is a test of Reflex."),
        rx.button("Go to /goto/page2", on_click=rx.redirect("/goto/page2")),
    )

app.add_page(index)

There was one minor issue with multiple pages using the same dynamic argument name. It is fixed and tested now

I would like to deprecate those automatically generated computed vars for dynamic routes.

They are untyped because the attribute is added dynamically
They can be easily created manually
There should be one good way to do things
They either shadow other vars or block var names (this PR)
They are uncached computed vars, and without usage tracking they are computed and transmitted to the frontend all the time, even if you don't need them

What's your opinion @picklelo?

Thanks, @masenf, for the great ideas.
I would merge this PR as-is to prevent unwanted shadowing and create issues for further dynamic arg var decisions and substate field overwrites.

Something like rx.Query.redirect_me
I am unsure about this because it stores and transmits the same variable multiple times. All query params still live in rx.State.router. Maybe we should focus on #3681 first and later add a RouterState.params hybrid_property (#3806) to add an ergonomic alias without overhead.

The other big problem I see in state.py is that substates cannot redefine or override fields from a parent state
I totally agree :100:  I think we should change this

Instead of adding a field to ImmutableComputedVar, can we subclass it as DynamicRouteVar and use that as the determinant?

Great idea, done


Attempt 3 to fix LDAP login issues when git pushing after password change

This fixes the issue for #898 (and I've actually tested it and got it running production this time).

Thanks a lot! Appreciate your work!


Want to add rounting to the project

I want to add routing between the pages so that different pages can be navigated through url

I want to add routing between the pages so that different pages can be navigated through url

Go for it @ArtiGaund
All the Best

I also want to add routing between the pages . Can you please assign it to me also ?

Routing done


Question about resource usage

I have created a very simple node.js express application.
It loads about 1 gig of JSON data into a memoryonly nedb database.
So I'm wondering what happens when I try to run this in production?
I don't know how express is deployed but presumably using some sort of web server that executes multiple express processes?
I am wondering if this means that each process will have its own one gigabyte nedb database in memory?
Is there a way to configure such that the one nedb database is shared amongst all the node.js express processes?

On x64 1GB is close to the limit. Depending on your app you may be able to load 1.2GB not much more. For these kinds of datasets you'll be better off using MongoDB.


Screenshots?

Can we add some screenshots either to the wiki or to the readme?

I'll pick this up and PR when ready.

See #48


Fix focusFollowMouse

Because this looks like it's entirely broken in main, and possibly in 1.17(?)
 As to be expected, that explodes.
Closes #15412

I don't understand totally - what state is this change in? I would love to merge in a very surgical fix for 1.17.

(I am also cool with this fix if it isn't exactly surgical and just pulls things out into member functions. As long as it can be backported cleanly.)


Fix deprecated warnings

@pierrealixt let me know if I need to merge for you

It won't be necessary, I can merge it myself. Thank you @fluffels.