Run Audit Log tests against real cloud environment

Currently, our Audit Log tests are only ran on the Mock cloud (http-test-helper). That is because the endpoint used to fetch logs currently is supposed to return ALL logs (which is far too much data), and in practice it just seems to return []. So we rely on this endpoint in the mock instead.
This however poses the risk that changes in the cloud may cause regressions in the audit log implementation that can go unnoticed, because we do not have relevant tests.
This was inspired by my work on #10918 - I accidentally switched to real cloud and only then realized that I understand the endpoint definition wrong and was sending messages in wrong format. Because the Mock was implemented also by me, based on the understanding of the format - it was consistently wrong and so the tests were passing.
I also remember the actual cloud returning lists of events on the log_events endpoint, but now I see only empty list. This also seems like a regression that could have been caught if we had such tests.
Of course such testing will make most sense after we start running the Cloud tests on the CI (#9523).

Waiting until https://github.com/enso-org/cloud-v2/pull/1545 is merged and deployed.


Specify daemon host

Let users target the docker daemon via URL, defaulting to the local configuration if no host is set.
g:dockertools_docker_host can be set in the deploy.yaml to automatically set the daemon url
:DockerToolsSetHost tcp://host-url:host-port or :DockerToolsSetHost unix:///var/run/docker.sock can be used to set the host.
All docker cli calls are prefixed with the value of g:dockertools_docker_cmd.
On start if the docker host has been set the variable g:dockertools_docker_cmd is set to docker -H g:dockertools_docker_host where g:dockertools_docker_host is substituted with the value of the variable , if no value has been set for g:dockertools_docker_host g:dockertools_docker_cmd is set to docker.
If the DockerToolsSetHost command is used, the g:dockertools_docker_cmd is then set to the value docker -H a:1 where a:1 is substituted with the value of the host URL argument.
This does not support specifying the authentication mode / certificates used by the client due to the complexities of handling all the different client authentication modes but secure sessions will still work if the users environment is configured correctly for them. Handling of authentication and the certificates for the client would make for a good feature addition in the future though.
Tested on my local machine, targeting the locally running docker daemon using both a unix and tcp socket, as well as remote hosts using their tcp sockets. For each socket tested (local unix, local tcp, remote tcp), setting the socket was tested via setting from a variable in my .vimrc, and by using the :DockerToolsSetHost command.

I've fixed the merge conflicts, preferring your changes over mind, and fixed the empty string checking ("" and '' now resolve as empty)


Normalise errors to return Exception.t() from the backend

The idea is to return something like {:error, Exception.t()} instead of {:error, String.t()} that we have today.

We will simply call RuntimeError.message(...) to convert them. :)

I don't know if I understood correctly, but the idea is to change this:
https://github.com/elixir-explorer/explorer/blob/e29d77e0b2a3b27b9dfd5375ea5ef64f0b0320b5/lib/explorer/polars_backend/shared.ex#L152
for this?:
defp error_message(error) when is_binary(error), do: RuntimeError.message(%{message: error})

Yes, more precisely, you can do:
defp error_message(error) when is_binary(error), do: RuntimeError.message(error)

Using RuntimeError.message(error) returns this error:
iex(1)> RuntimeError.message("test")
** (KeyError) key :message not found in: "test"

If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map
    (elixir 1.15.0) lib/exception.ex:801: RuntimeError.message/1
    iex:1: (file)

That's why I did it like this RuntimeError.message(%{message: error})

I am very sorry, I meant this: RuntimeError.exception(error). The goal is to make it so it returns an Exception struct. We would also need to update the typespecs. :)


metrics(like kube.namespace.memory.limit ) does not get proper value while the pod in the namespace use different unit

What happened:
metrics(like kube.namespace.memory.limit ) does not get proper value while the pod in the namespace use different unit(for example, some pod use Gi, while some other use Mi)
What you expected to happen:
Expects the memory limit of namespace equal sum of the pods' memory limit in the namespace
How to reproduce it (as minimally and precisely as possible):
comparing the value in splunk search can see great difference for namespace have pod use different unit for memory limit
|mstats avg(kube.namespace.memory.limit) WHERE index="xxx" by name
|mstats avg(kube.pod.memory.limit) WHERE index="xxx" by name

Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): v1.18.13-gke.400
Ruby version (use ruby --version): n/a
OS (e.g: cat /etc/os-release): Ubuntu 18.04.5 LTS
Splunk version: 7.3.5/8.1.3
Splunk Connect for Kubernetes helm chart version: 1.4.7
Others:

can you share the numbers you are seeing with great difference?
btw, here is info on metrics. https://github.com/splunk/fluent-plugin-kubernetes-metrics/blob/develop/metrics-information.md

Hi @rockb1017
One of the metrics(kube.pod.memory.limit) that we get number from splunk is 1289090.189.
While we get the memory limit by kubectl is as below
resources:
limits:
cpu: "1"
memory:<PHONE_NUMBER>800m
By comparing the real memory limit and the limit we get in splunk, we noticed that the unit for splunk is KB instead of MB in this case.
And this is only one of the metrics got problem, kube.namespace.memory.limit will also have issue whenever the pods use unaligned memory limit unit defined in its yams.

Hi @rockb1017
One of the metrics(kube.pod.memory.limit) that we get number from splunk is 1289090.189.
While we get the memory limit by kubectl is as below
resources:
limits:
cpu: "1"
memory:<PHONE_NUMBER>800m
By comparing the real memory limit and the limit we get in splunk, we noticed that the unit for splunk is KB instead of MB in this case.
And this is only one of the metrics got problem, kube.namespace.memory.limit will also have issue whenever the pods use unaligned memory limit unit defined in its yams.

hey @vbasic123
I have updated metric-aggr plugin.
Closing the issue. Feel free to reopen the issue or create a new one if needed


Can't use style on all elements

Let me first start of saying that I love React Konva!
One thing that's not really clear to me is when I can use regular CSS on Konva elements. I styled my 'Stage' with pure CSS and this work perfectly, but when I'm trying to style my Group it doesn't effect the styling at all. It's not really clear to me on what Elements I can use regular CSS and for which one I have to add the styling as props to the component.

You can use CSS only for Stage component.
Stage has root <div> DOM element. We can apply styles here.
All other elements are not DOM elements. They are virtual Konva nodes. We can't apply CSS to Konva nodes.


Long file name -> broken UI

If you select a file name which is very long, the file name is wrapped into a next line, however, the control is not resized accordingly which looks bad:

Here is a JSFiddle demonstrating the problem: https://jsfiddle.net/p0ck9hba/2/

You'll find a solution to that here: https://bs-custom-file-input.netlify.com/
bsCustomFileInput accept one child in the label which will allow you to fix that 😉
See the example: Example with label containing a child

  <input id="inputGroupFile04" type="file" class="custom-file-input" multiple="">

    Choose several files

Hm, is there a way to cut the text dynamically according to the current input fields width? We have a responsive page (thanks to Bootstrap) and don't really know the number of characters beforehand...

Yep you can detect the width of your image (with getBoundingClientRect) and set a fixed with for the custom input file label

I'm not following you, would you be so kind and adjust my jsFiddle accordingly?

Like that it can work, but I don't think it's your use case: https://jsfiddle.net/gvfmo3rz/
Can you create a jsfiddle with your use case (with the image) ?

There is no image, I don't know where you get the idea from :-) Your jsFiddle has w-75 which is limited to a fixed number of characters. We're looking for a solution which "just fits" regardless of the actual width of the file input control / label, as we don't know its width beforehand.

Don't think it's doable because you fixed a width at 500px, that's why I added .text-truncate to truncate the file name when it's to long

I just added the 500px for demonstration purposes. In our real page there is no given width, the input box is resized with the page size (it's a responsive page, smaller on small displays, bigger on big displays). So the content's width should be dynamically adjusted as well.

So you can use my JSFiddle, and it'll works because w-75 is equal to width: 75% so it'll be responsive

It only works if the page is not too small. If the "Browse" button takes more than 25% of the space it doesn't work anymore.

You mean like that:

I think with some media query, you can override w-75 to fit your needs.

In my opinion all this stuff should be part of the bs-custom-file-input out-of-the-box-experience. I can't imagine anyone who wants to have long text overflowing the control. Every user of this extension needs to rework this so it doesn't wrap accidentally.

That's not the purpose of this plugin, this plugin dynamize bootstrap custom file input that's all.
If you have issues with Bootstrap custom file input responsiveness or the HTML Markup, you should try to find an open issue on Bootstrap repo or creating a new one.

Ah, now I understand. That's already a problem of the underlying Bootstrap file input control. Didn't realize that parts of that are already part of Bootstrap itself! Will report it at Bootstrap, thank you for your patience.

Bug created @ https://github.com/twbs/bootstrap/issues/28897


Resource snowflake_integration_grant does not correctly set terraform state for privilege USAGE

When using the USAGE role with a snowflake_integration_grant, Terraform state is not correctly updated. The result is that every run of terraform apply will perform this grant because it believes that terraform state and the resource state don't match.
If I create a terraform project with a single resource as:
resource "snowflake_integration_grant" "my_integration_grant" {
  integration_name = "MY_STORAGE_INTEGRATION"
  privilege        = "USAGE"
  roles            = ["MY_ROLE"]
}

If I then apply that and inspect terraform state, I can see that the role is not reflected.
% tf state show snowflake_integration_grant.my_integration_grant
# snowflake_integration_grant.my_integration_grant:
resource "snowflake_integration_grant" "my_integration_grant" {
    id               = "MY_STORAGE_INTEGRATION|||USAGE"
    integration_name = "MY_STORAGE_INTEGRATION"
    privilege        = "USAGE"
    roles            = []
}

The resource snowflake_integration_grant has it's roles set using readGenericGrant in pkg/resources/grant_helpers.go. As stated in that function, "We re-aggregate grants that would be equivalent to the "ALL" grant". The problem is that for a Snowflake storage integration, USAGE is the only type of grant. So any USAGE grant in this code is rolled up into ALL, which is then later filtered out in the call to ALLPrivsPresent.
As a workaround I can specify the ALL grant instead of USAGE. This is not desirable as my intent is to just grant USAGE, not all future privileges that Snowflake might add.

@teej I haven't had a chance to dig into this, but I have observed that snowflake will do some annoying things when you grant a privilege which is already covered by a broader grant. Is it possible that USAGE is already granted in another way?

I have also observed almost the same behavior, and I can confirm it's not caused by overlapping grants in Snowflake - at the moment I was checking, there was only a single USAGE grant on the integration (the one added via Terraform).
I'm saying "almost" because in my case the roles get stored in state just fine, but Terraform still insists to recreate the grant resource every time.
Workaround with "ALL" is working for me too, so it indeed looks like there is a problem with handling ALL when there is only one possible privilege. It's tricky, though, because as far as I know there is no way to tell from looking at grants in Snowflake whether one was granted explicitly or via ALL. So in case of resource grants in Terraform with only one type of grant possible, either ALL would work, or the explicit grant would work, but never both, at least not as it's currently implemented.
Note, if this is indeed the cause, then it should be possible to recreate the issue on any grant resource by explicitly granting every possible privilege to the same object by separate grant resources. Then provider will start thinking actual privileges on object were granted by ALL, and behave in the same way as with this issue.

Going to close this as we are going to be removing support for ALL grants.
If still occurring after that, feel free to re-open.


Plugin use_sim_time has no effect

on ros2 galactic I have set "use_sim_time" to true on my custom panel for rviz but the clock is still machine clock and not simulated time
I have tried setting the flag on runtime as well, and in callback loop I always see machine clock
see snippet below
ControlPanel::ControlPanel(QWidget* parent) : Panel(parent)
{
    // Setup ROS2 functionality
    node_ = rclcpp::Node::make_shared("control_panel");
    node_->set_parameter(rclcpp::Parameter("use_sim_time", true));

    auto now = node_->get_clock()->now();
    RCLCPP_INFO(node_->get_logger(), std::to_string(now.nanoseconds()).c_str());

}

`[rviz2-1] [INFO] [1636397904.147354086] [control_panel]:<PHONE_NUMBER>147343391`

I have the same problem.  I tried setting use_sim_time with the command line:
ros2 param set /rviz use_sim_time true
but rviz still does not use the time in the rosbag being played

you're setting the parameter after creating the node, so you'll have to spin a couple of times before the node reads the clock topic properly. Preferably add the parameters to rclcpp::NodeOptions and start the node with those options.


Dselans/common aliases

Hey folks,
We had a unique requirement that the top-level common section be called 'default' instead. This required a very minor code change to allow the COMMON_SECTION to turn into COMMON_SECTIONS.
Test updated (copy/paste from another test).

Woops, looks like this includes some previous changes.


Fix processing and redirection of acquireTokenRedirect

This PR fixes #1755, #1713 and #1763
loginStartPage is only being cached for login calls. This means that when navigateToLoginRequestUrl: true and calling acquireTokenRedirect the user will be redirected back to the root of their application and the response hash will not be processed.
Diff largely due to new Sample + E2E tests. Relevant code changes are just in UserAgentApplication

Coverage increased (+0.01%) to 76.875% when pulling 65d00b5e56f5f73eeae1c310b3716ec3a240c4a6 on Fix-acquireTokenRedirect into 4468dd0fbaacd6358cd203cc0fcf7967b2a80afd on dev.

Hi, i am still facing the same error can anyone help me out.
core.js:1449 ERROR Error: Uncaught (in promise): ClientAuthError: User login is required. For silent calls, request must contain either sid or login_hint
ClientAuthError: User login is required. For silent calls, request must contain either sid or login_hint.


docs: add some examples based on maven

I don't understand this report.
The reference documentation already shows both Maven and Gradle code snippets. Please add a description to your issue that explains the type of content that's currently missing.

OP might be talking about schema code generation as it's always different between tools.

@jvalkeal what schema code generation?

For example webmvc-http sample creates:
samples/webmvc-http/build/generated/sources/annotationProcessor/java/main/io/spring/sample/graphql/repository/QArtifactRepository.java

Thought I only now noticed it's from querydsl and not from schema classes generation(which is pretty common when working with domain classes).

Tx lot

Reopening to document the querydsl build setup.

I've added a rule to .gitignore related to Querydsl generated classes.

This does not cover a reactive query dsl and r2db connection, does it? It would be Greta if you can give an example here as well, as i can not  find any in this direction on the web


execute_process fails

im building qwindowkit in github actions on ubuntu-latest with gcc and ninja (cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++)
however this part keeps erroring
https://github.com/stdware/qmsetup/blob/1c82f2e09dd922b84a7807f4a360e07f141fcb10/cmake/modules/InstallPackage.cmake#L92-L100
CMake Error at DummyProject/ThirdParty/qwindowkit/qmsetup/cmake/modules/InstallPackage.cmake:108 (message):
  Configure failed, check
  "/home/runner/work/DummyProject/DummyProject/build/_build/qmsetup_configure.log"

qmsetup_configure.log:
Run cat /home/runner/work/DummyProject/DummyProject/build/_build/qmsetup_configure.log
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

so i went back and added some logging just before
execute_process(COMMAND ninja --version)
message("${CMAKE_COMMAND} -S ${_src_dir} -B ${_build_dir} ${_generator} ${_build_type}")

which yields
1.11.1
/usr/local/bin/cmake -S /home/runner/work/DummyProject/DummyProject/ThirdParty/qwindowkit/qmsetup -B /home/runner/work/DummyProject/DummyProject/build/_build/qmsetup -G Ninja -DCMAKE_BUILD_TYPE=Release

the full command cmake runs is:
execute_process(COMMAND /usr/local/bin/cmake -S /home/runner/work/DummyProject/DummyProject/ThirdParty/qwindowkit/qmsetup -B /home/runner/work/DummyProject/DummyProject/build/_build/qmsetup -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/home/runner/work/DummyProject/DummyProject/build/_install  OUTPUT_FILE /home/runner/work/DummyProject/DummyProject/build/_build/qmsetup_configure.log ERROR_FILE /home/runner/work/DummyProject/DummyProject/build/_build/qmsetup_configure.log RESULT_VARIABLE _code WORKING_DIRECTORY /home/runner/work/DummyProject/DummyProject/ThirdParty/qwindowkit )

so both ninja is found in PATH, and the command run is perfectly fine. how is this possible?
like i said, this happens only in CI, not locally

Update:
It seems that switching from https://github.com/ashutoshvarma/setup-ninja to just installing ninja with apt fixes it. I have no idea how that is possible since both put ninja is path but whatever

I don't know how this happened as well. https://github.com/ashutoshvarma/setup-ninja just downloads Ninja and adds it to PATH.


adding rudimentary debian package building support

With a liberal dose of FPM-magic, this allows a 'make packages-deb' command to build a valid Debian package which installs great on Debian 8.0 (Jessie) and Ubuntu 14.04 LTS (Wheezy)

LGTM


Tag crawl attempts

Engine now support and optional crawl_id argument. If crawl_id
is not provided it will be generated automatically.

I think we should wait until the list_spiders PR is settled, as it would change how the crawl_id is stored and passed around.
Ok, we could have some sort of agreement here, as I need this change in order to initiate jobs from Crawly UI properly. Otherwise, I have to guess which items I am getting.

I don't think passing the crawl_id everywhere as parameters is a good idea.
Yes, I think it should stay in the engine. Anyone who wants to get a tag will query the engine. That's the intention I have atm.

I also think that the handle_call for :start_spider should be the one generating the id.
I am not sure. Could you explain why it might be needed? E.g. we can still control if we want to store the UUID (e.g. if the spider was not started etc). So I can't see races or anything like that, which will make handle_call a better place for ID generation. Please advise.

I think that keeping it simple with a :crawl_id on the stored spider info would be good. I think the get_crawl_id should be changed to get_spider_info

As for generating the uuid in the handle_call, it's more about  keep the code localised, as the module would be getting quite big soon

will review again once #104 is done


caskl return error 1

Description
caskl tries to run new way to list casks, but an error code is returned.
Expected behavior
Listing of installed casks
Actual behavior
Error: Calling brew cask list is deprecated! Use brew list --cask instead.
-> [1]

Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Versions

Prezto commit: 0a405494cae54e208ff550c1ba83380ed115410a
ZSH version: zsh 5.7.1
OS information: macOS 10.15.6

I was able to get a repro with latest brew. That being said, it's a 'Warning' and only on the latest version of brew. Considering that a lot of people will be using older versions of brew. I do not believe it will be prudent to change the existing alias. A possible upgrade path can be providing an alternate alias for brew list --cask.

Closed in #1905.


[Swift4] Updated syntax and changed two property modifiers

• Updated syntaxes and method signatures to latest Swift 4.2
• Changed isPrepared and isRecording properties access modifiers to public. This changes are needed if user wants to update UI based on current recording status.

Can you please make this repo workable under swift 4.2 ?

Check  #51, contains a new branch with Swift 4.2 support.


Update for 1.9

Provides fallback for the new url module (extendModule(urlExtend))
Fixes issue where cached stories would be pulled on publish
Simplify theme routing setup

Fixes #48 #8

@zimme hacked

Cherry picked 712e845, into master and rebased this on master. I'll rebase #50 on master now and merge that, once that's done I'll rebase this against master again and remove the
a7697ea as that will have already been addressed in #50.

No need to remove commits that just do the same thing. Can't we just merge this?

Once I merge #50, which does more than your commit, this PR will have conflicts so I'll just rebase and merge after that.

@zimme I see, sorry 😅 thanks!


Feature: TextBox.SelectedText

What does the pull request do?
Adds a SelectedText getter/setter to TextBox based on the description from WPF here.
What is the current behavior?
TextBox does not currently have such a property.
What is the updated/expected behavior with this PR?
You can now do things like:
var textBox = new TextBox();
var text = textBox.SelectedText;
textBox.SelectedText = "Hello all!";

How was the solution implemented (if it's not obvious)?
Fairly straight forward -- calls already-existing code for this functionality.
Checklist

[x] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes
No breaking changes.
Fixed issues
None.

Thanks @Deadpikle !


Crasher in BraceStyleListener

Tailor will crash when parsing this valid Swift:
var foo: Bool {
    willSet { self.bar(newValue) }
}

With a java trace:
$ tailor tailor-crasher.swift
Exception in thread "main" java.lang.NullPointerException
at com.sleekbyte.tailor.listeners.BraceStyleListener.verifyWillSetClauseBraceStyle(BraceStyleListener.java:312)
at com.sleekbyte.tailor.listeners.BraceStyleListener.enterWillSetClause(BraceStyleListener.java:134)
at com.sleekbyte.tailor.antlr.SwiftParser$WillSetClauseContext.enterRule(SwiftParser.java:5768)
at org.antlr.v4.runtime.tree.ParseTreeWalker.enterRule(ParseTreeWalker.java:66)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:49)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at com.sleekbyte.tailor.Tailor.analyzeFiles(Tailor.java:285)
at com.sleekbyte.tailor.Tailor.main(Tailor.java:344)

Thanks for reporting @alexkent! I believe this issue was already fixed in #249, but you may be running v0.2.2 or earlier so please update to v0.3.0 and see if you can still reproduce.

You're right I am using 0.2.2.
brew upgrade tailor tells me that 0.2.2 is current. What needs to happen for Homebrew to acknowledge 0.30 exists?

brew update && brew upgrade tailor should do the trick :)

great! thanks, my crashing file now passes :+1:

Awesome!


The "Fire Exits Amount Overwrite" setting does not seem to consistently work

The "Fire Exits Amount Overwrite" setting does not seem to consistently work.
Since I just started with the template, I have just added new doors and increased the Entrance ID then set the overwrite.
What actually happens after loading the custom moon is the new doors do not work (entrance is blocked) except the main entrance and the first fire exit.

does it happen in both dungeons ? or especially one ?

does it happen in both dungeons ? or especially one ?

Always happens.
I even removed the mansion dungeon so its only the first one and it still happens.
It was working before the latest update (I had 6 fire exits as a test, I did not change this setting)


UPSTREAM: 1706: Update golang.org/x/crypto for CVE-2022-27191 (#1706)

This is cherry pick of https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/1706.
golang.org/x/crypto/ssh server can crash in certain conditions. This CSI
driver most probably does not run any ssh server, but update the package to
a safe version to be 100% sure. Using today's master, they don't use tags.
Updated using:
go get -u golang.org/x/crypto
go mod tidy

cc @openshift/storage


Feature: Deploy WebServices and process web.config using SettingsFileGenerator.xml

The BizTalk team is often the first to advise also on how to deploy web services.  I'm referring to ones written in .NET and called by orchestrations.  (I know you handle the orchestrations published as web services).

I'm currently using this technique: http://biztalk-training.com/articles.php?article_id=58.

But often, the same SQL Server and/or config parms have already been defined in the SettingsFileGenerator.xml.  It would be great to be able to use the ${variable} definitions in a regular WCF web.config, and have them preprocessed based on the SettingsFileGenerator.xml.
This work item was migrated from CodePlex
CodePlex work item ID: '5675'
Vote count: '1'

[tfabraham@12/31/2009]
Actually, you can already do that.  Just add  to your .btdfproj file and fill in a comma-separated list of files to be pre-processed (merging environment settings).  Does that match what you are hoping to do?

[NealWalters@1/4/2010]
I bought a book on MSBuild and got the big picture over the long weekend.
I could see how  could handle a web.config, but need to install in IIS, hook up to app pool, and ideally set-up the proper web.config file.
Even though  is aimed at Orchestrations published as web services, I guess it could also be used for pure web services as well?
("Pure", meaning a web service that might be called by BizTalk, but not created by BizTalk).
Last week, I created an MSI for my "pure" web service.  Then I was trying to deal with customizing the web configs.
I first tried it as mentioned above, then when someone suggested XMLPreprocess, I thought that was perfect because I could use the same SettingsFileGenerator.xml already in use by BizTalk.
I created two threads on XMLPreprocess:
http://xmlpreprocess.codeplex.com/Thread/View.aspx?ThreadId=79454
http://xmlpreprocess.codeplex.com/Thread/View.aspx?ThreadId=79698

[tfabraham@1/5/2010]
Correct.  I sometimes include regular WCF or ASMX web service projects in my BizTalk solution file.  If you do that, you can package the files into the same MSI with the BizTalk solution, use  to update the web.config and the  to configure the web service in IIS.

[NealWalters@1/5/2010]
I think that will work for this client, where the only IIS servers are on the BizTalk machines.  At other clients, we ran the "pure" web services on a machine reserved for IIS services.  As you know, the BizTalk orchs that are published as WebServices must be installed on the BizTalk machines.

[tfabraham@1/6/2010]
Is it OK to close out this issue?  I don't think there is anything to change at this point.

[NealWalters@1/7/2010]
Yea, I guess as far as closing it.  I'm going to try including the IIS in the next few days.  BUT what about the companies that need to install what I was calling the "pure" web services for IIS on a non-BizTalk server?   I would still love to preprocess these with the exact same settings file.  These people would need two MSI's, one for the BT machine, and an entirely different one for the IIS servers.  I've been fighting issues with using XmlPreprocess as part of an MSI Setup for several days - about to abandon that in favor of your idea here, but would like to solve it just for the satisfaction.   I'm not getting any answers from Loren over at the XmlPreprocess CodePlex discussion.  Debugging the CustomAction is what is killing me.
http://stackoverflow.com/questions/2007635/making-sense-out-on-msi-verbose-trace-running-a-customaction

[NealWalters@1/11/2010]
Regarding the files listed in the , is that filename on the source machine or on the target?  For this example regarding a web.config, would I put C:\inetpub\wwwroot\targetservicename\web.config?  Or would I put the local filename, and then have to add some copy step to copy it to C:\inetpub\wwwroot\targetservicename\web.config after it running it through the XmlPreprocessor?
Thanks!

[NealWalters@1/11/2010]
Another question.  My VS solution for the webservices is TFBIC.RCT.WebServices, but it's not physically in the existing TFBIC.RCT.BizTalk solution.  Would it be best to move it there to follow this approach (i.e. so that all the paths could be relative...)?   I could also see this as a political issue for some clients - i.e. mixing the BizTalk code and the C# web service code into the same TFS path.

[tfabraham@1/12/2010]
Usually the filenames in  would be relative to your .Deployment folder, like ..\Test.xml if that file is next to the .sln file.  If you want to put an explicit full path in there instead, go right ahead.

[UnknownUser@10/20/2011]

[UnknownUser@11/8/2011]

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]

Issue closed by tfabraham with comment
Closing since the question is directed at using BTDF tools for deploying web services that are not specifically related to BizTalk.  The tools will certainly work for other scenarios, but this project is intended to support only BizTalk deployments.


Set DebuggerSupport to true in the ClangImporterOptions.

Swift's ClangImporter is more lenient when this option is set, but
LLDB wasn't passing it correctly to the ClangImporter, only to the
LanguageOptions.
rdar://problem/37922760

@swift-ci test

@swift-ci test

The linux bot was stuck checking out swift.


Fix to use only needed columns from tables to get repository git paths

Fixes #3864

Codecov Report

Merging #3870 into master will increase coverage by 0.04%.
The diff coverage is 61.29%.

@@            Coverage Diff             @@
##           master    #3870      +/-   ##
==========================================
+ Coverage   20.22%   20.26%   +0.04%
==========================================
  Files         145      145
  Lines       28997    29024      +27
==========================================
+ Hits         5864     5883      +19
- Misses      22242    22248       +6
- Partials      891      893       +2

Impacted Files
Coverage Δ

models/wiki.go
62.5% <100%> (ø)
:arrow_up:

models/repo.go
18% <60%> (+0.67%)
:arrow_up:

modules/avatar/avatar.go
100% <0%> (+18.75%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fff022e...efba083. Read the comment docs.


[WFCORE-2491] Add support for graceless startup

Squashed commit of the following:
commit 874016e30ed412a184b251773b9050edd726f4d9
Author: Brian Stansberry<EMAIL_ADDRESS>Date:   Mon Jul 29 13:50:48 2019 -0500
[WFCORE-4291] Basic implementation of disabling initial boot-time suspension of a server.

Behavior for a standalone server is enabled via a new 'graceless' value for the --start-mode command line parameter.
Configuration for domain mode is not implemented.

Add support for "graceless" startup
Modify schema to add attribute to server-group for domain mode support
Add support for '--graceless' command line param for server startup
Fix startGraceless log message
Exposed isStartGraceless and isStartSuspended
Remove changes that are no longer needed

Hello, jasondlee. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

Hello, jasondlee. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

/ok-to-test

/ok-to-test

Core - Full Integration Build 10275 outcome was FAILURE using a merge of ef313d3039231404c7f8872d6ff795657bfff171
Summary: Execution timeout (new); tests failed: 3 (3 new), passed: 7002, ignored: 112 Build time: 05:01:07
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationFailedTestCase.testPassivationFailure: java.lang.AssertionError
	at org.jboss.as.test.integration.ejb.stateful.passivation.PassivationFailedTestCase.testPassivationFailure(PassivationFailedTestCase.java:85)
	at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:200)
	at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:176)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1494)
	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727)
	at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
	at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258)
	at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66)
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: javax.ejb.NoSuchEJBException: WFLYEJB0168: Could not find EJB with id UUIDSessionID [0bc930f8-4ab8-488e-a141-d22e9ac76bb8]
		at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:55)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:388)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:158)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
		at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72)
		at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

org.jboss.as.test.integration.mgmt.access.PermissionsCoverageTestCase.testTheEntireDomainTreeHasPermissionsDefined: java.lang.AssertionError: {"outcome" => "failed","failure-description" => "WFLYCTL0158: Operation handler failed: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key server.env.start-suspended","rolled-back" => true}
	at org.jboss.as.test.integration.management.rbac.RbacUtil.checkOperationResult(RbacUtil.java:115)
	at org.jboss.as.test.integration.management.rbac.RbacUtil.executeOperation(RbacUtil.java:100)
	at org.jboss.as.test.integration.management.rbac.PermissionsCoverageTestUtil.assertTheEntireDomainTreeHasPermissionsDefined(PermissionsCoverageTestUtil.java:37)
	at org.jboss.as.test.integration.mgmt.access.PermissionsCoverageTestCase.testTheEntireDomainTreeHasPermissionsDefined(PermissionsCoverageTestCase.java:70)
------- Stdout: -------
 [0m16:58:20,227 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m16:58:20,964 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
 [0m [0m16:58:20,986 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m16:58:21,223 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting
 [0m [0m16:58:23,017 INFO  [org.wildfly.security] (ServerService Thread Pool -- 27) ELY00001: WildFly Elytron version 1.14.1.Final
 [0m [0m16:58:24,473 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 [0m16:58:24,624 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 3) 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 [0m16:58:24,808 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m16:58:24,855 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.8.4.Final
 [0m [0m16:58:24,879 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.8.4.Final
 [0m [0m16:58:24,985 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.20.Final
 [0m [0m16:58:25,052 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 70) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
 [0m [0m16:58:25,089 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 71) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m16:58:25,098 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 57) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m16:58:25,102 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 56) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m16:58:25,115 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 55) WFLYHEALTH0001: Activating Base Health Subsystem
 [0m [0m16:58:25,119 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 59) WFLYRS0016: RESTEasy version 3.14.0.Final
 [0m [0m16:58:25,127 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 82) WFLYWS0002: Activating WebServices Extension
 [0m [33m16:58:25,141 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 80) 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 [0m16:58:25,143 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 69) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m16:58:25,161 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 64) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m16:58:25,181 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 72) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m16:58:25,201 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 78) WFLYSEC0002: Activating Security Subsystem
 [0m [0m16:58:25,267 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 58) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m16:58:25,308 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 68) WFLYMETRICS0001: Activating Base Metrics Subsystem
 [0m [0m16:58:25,385 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 47) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m16:58:25,377 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
 [0m [0m16:58:25,431 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
 [0m [0m16:58:25,454 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m16:58:25,455 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 2.2.3.Final starting
 [0m [0m16:58:25,827 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
 [0m [0m16:58:25,889 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m16:58:26,115 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m16:58:26,117 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
 [0m [33m16:58:26,251 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-4) WFLYELY00023: KeyStore file '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore' does not exist. Used blank.
 [0m [33m16:58:26,303 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-1) WFLYELY01084: KeyStore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
 [0m [0m16:58:26,323 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m16:58:26,423 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
 [0m [0m16:58:26,486 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
 [0m [0m16:58:26,819 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m16:58:26,933 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m16:58:27,275 INFO  [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [33m16:58:27,327 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m16:58:27,407 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 [0m [0m16:58:27,422 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/deployments

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: java.lang.AssertionError: [("server-group" => "main-server-group")] attribute graceless value false is an unconverted expression expected:<expression "${exp.test:false}"> but was:<false>
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateAttributeValue(ExpressionSupportSmokeTestCase.java:710)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateExpectedValues(ExpressionSupportSmokeTestCase.java:684)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateExpectedValues(ExpressionSupportSmokeTestCase.java:701)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test(ExpressionSupportSmokeTestCase.java:153)
------- Stdout: -------
 [0m19:51:00,167 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m19:51:00,663 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m19:51:00,702 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:51:01,931 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final [0m
[Host Controller]  [0m [0m19:51:02,604 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final [0m
[Host Controller]  [0m [0m19:51:02,624 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final [0m
[Host Controller]  [0m [0m19:51:02,770 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting [0m
[Host Controller]  [0m [0m19:51:03,849 INFO  [org.wildfly.security] (Host Controller Service Threads - 4) ELY00001: WildFly Elytron version 1.14.1.Final [0m
[Host Controller]  [0m [0m19:51:04,797 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/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
[Host Controller]  [0m [0m19:51:04,990 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [0m
[Host Controller]  [0m [0m19:51:05,083 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.8.4.Final [0m
[Host Controller]  [0m [0m19:51:05,100 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.8.4.Final [0m
[Host Controller]  [0m [0m19:51:05,293 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.20.Final [0m
[Host Controller]  [0m [0m19:51:05,355 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none [0m
[Host Controller]  [0m [33m19:51:05,423 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/domain/target/domains/ExpressionSupportSmokeTestCase/master/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost [0m
[Host Controller]  [33m [0m [0m19:51:09,615 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/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
[Host Controller]  [0m [0m19:51:09,760 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/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
[Host Controller]  [0m [0m19:51:09,840 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/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
[Host Controller]  [0m [0m19:51:09,933 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/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
[Host Controller]  [0m [0m19:51:11,134 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) (Host Controller) started in 10220ms - Started 74 of 82 services (26 services are lazy, passive or on-demand) [0m
[Host Controller]  [0m [0m19:51:11,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://[::1]:9990/management and https://[::1]:-1/management [0m
[Host Controller]  [0m [0m19:51:11,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled [0m
Failed operation:
{
    "operation" => "read-resource",
    "address" => [
        ("host" => "master"),
        ("core-service" => "management"),
        ("service" => "management-operations"),
        ("active-operation" => "-305572225")
    ],
    "include-defaults" => true
}
Response:
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0216: Management resource '[
    (\"host\" => \"master\"),
    (\"core-service\" => \"management\"),
    (\"service\" => \"management-operations\"),
    (\"active-operation\" => \"-305572225\")
]' not found",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

Core - Full Integration Build 10275 outcome was FAILURE using a merge of ef313d3039231404c7f8872d6ff795657bfff171
Summary: Execution timeout (new); tests failed: 3 (3 new), passed: 7002, ignored: 112 Build time: 05:01:07
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationFailedTestCase.testPassivationFailure: java.lang.AssertionError
	at org.jboss.as.test.integration.ejb.stateful.passivation.PassivationFailedTestCase.testPassivationFailure(PassivationFailedTestCase.java:85)
	at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:200)
	at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:176)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
	at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1494)
	at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727)
	at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
	at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258)
	at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
	at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66)
	at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: javax.ejb.NoSuchEJBException: WFLYEJB0168: Could not find EJB with id UUIDSessionID [0bc930f8-4ab8-488e-a141-d22e9ac76bb8]
		at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:55)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:388)
		at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:158)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
		at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72)
		at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
		at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
		at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

org.jboss.as.test.integration.mgmt.access.PermissionsCoverageTestCase.testTheEntireDomainTreeHasPermissionsDefined: java.lang.AssertionError: {"outcome" => "failed","failure-description" => "WFLYCTL0158: Operation handler failed: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key server.env.start-suspended","rolled-back" => true}
	at org.jboss.as.test.integration.management.rbac.RbacUtil.checkOperationResult(RbacUtil.java:115)
	at org.jboss.as.test.integration.management.rbac.RbacUtil.executeOperation(RbacUtil.java:100)
	at org.jboss.as.test.integration.management.rbac.PermissionsCoverageTestUtil.assertTheEntireDomainTreeHasPermissionsDefined(PermissionsCoverageTestUtil.java:37)
	at org.jboss.as.test.integration.mgmt.access.PermissionsCoverageTestCase.testTheEntireDomainTreeHasPermissionsDefined(PermissionsCoverageTestCase.java:70)
------- Stdout: -------
 [0m16:58:20,227 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m16:58:20,964 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
 [0m [0m16:58:20,986 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m16:58:21,223 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting
 [0m [0m16:58:23,017 INFO  [org.wildfly.security] (ServerService Thread Pool -- 27) ELY00001: WildFly Elytron version 1.14.1.Final
 [0m [0m16:58:24,473 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 [0m16:58:24,624 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 3) 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 [0m16:58:24,808 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m16:58:24,855 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.8.4.Final
 [0m [0m16:58:24,879 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.8.4.Final
 [0m [0m16:58:24,985 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.20.Final
 [0m [0m16:58:25,052 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 70) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
 [0m [0m16:58:25,089 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 71) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m16:58:25,098 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 57) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m16:58:25,102 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 56) WFLYIIOP0001: Activating IIOP Subsystem
 [0m [0m16:58:25,115 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 55) WFLYHEALTH0001: Activating Base Health Subsystem
 [0m [0m16:58:25,119 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 59) WFLYRS0016: RESTEasy version 3.14.0.Final
 [0m [0m16:58:25,127 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 82) WFLYWS0002: Activating WebServices Extension
 [0m [33m16:58:25,141 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 80) 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 [0m16:58:25,143 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 69) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m16:58:25,161 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 64) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m16:58:25,181 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 72) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m16:58:25,201 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 78) WFLYSEC0002: Activating Security Subsystem
 [0m [0m16:58:25,267 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 58) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m16:58:25,308 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 68) WFLYMETRICS0001: Activating Base Metrics Subsystem
 [0m [0m16:58:25,385 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 47) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m16:58:25,377 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
 [0m [0m16:58:25,431 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
 [0m [0m16:58:25,454 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m16:58:25,455 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 2.2.3.Final starting
 [0m [0m16:58:25,827 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
 [0m [0m16:58:25,889 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m16:58:26,115 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m16:58:26,117 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
 [0m [33m16:58:26,251 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-4) WFLYELY00023: KeyStore file '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore' does not exist. Used blank.
 [0m [33m16:58:26,303 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-1) WFLYELY01084: KeyStore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
 [0m [0m16:58:26,323 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m16:58:26,423 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
 [0m [0m16:58:26,486 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
 [0m [0m16:58:26,819 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m16:58:26,933 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m16:58:27,275 INFO  [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [33m16:58:27,327 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m16:58:27,407 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 [0m [0m16:58:27,422 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/rbac/target/wildfly/standalone/deployments

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: java.lang.AssertionError: [("server-group" => "main-server-group")] attribute graceless value false is an unconverted expression expected:<expression "${exp.test:false}"> but was:<false>
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateAttributeValue(ExpressionSupportSmokeTestCase.java:710)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateExpectedValues(ExpressionSupportSmokeTestCase.java:684)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.validateExpectedValues(ExpressionSupportSmokeTestCase.java:701)
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test(ExpressionSupportSmokeTestCase.java:153)
------- Stdout: -------
 [0m19:51:00,167 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m19:51:00,663 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m19:51:00,702 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:51:01,931 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final [0m
[Host Controller]  [0m [0m19:51:02,604 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final [0m
[Host Controller]  [0m [0m19:51:02,624 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final [0m
[Host Controller]  [0m [0m19:51:02,770 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting [0m
[Host Controller]  [0m [0m19:51:03,849 INFO  [org.wildfly.security] (Host Controller Service Threads - 4) ELY00001: WildFly Elytron version 1.14.1.Final [0m
[Host Controller]  [0m [0m19:51:04,797 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/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
[Host Controller]  [0m [0m19:51:04,990 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1) [0m
[Host Controller]  [0m [0m19:51:05,083 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.8.4.Final [0m
[Host Controller]  [0m [0m19:51:05,100 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.8.4.Final [0m
[Host Controller]  [0m [0m19:51:05,293 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.20.Final [0m
[Host Controller]  [0m [0m19:51:05,355 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none [0m
[Host Controller]  [0m [33m19:51:05,423 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/domain/target/domains/ExpressionSupportSmokeTestCase/master/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost [0m
[Host Controller]  [33m [0m [0m19:51:09,615 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/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
[Host Controller]  [0m [0m19:51:09,760 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/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
[Host Controller]  [0m [0m19:51:09,840 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/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
[Host Controller]  [0m [0m19:51:09,933 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/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
[Host Controller]  [0m [0m19:51:11,134 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) (Host Controller) started in 10220ms - Started 74 of 82 services (26 services are lazy, passive or on-demand) [0m
[Host Controller]  [0m [0m19:51:11,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0062: Http management interface listening on http://[::1]:9990/management and https://[::1]:-1/management [0m
[Host Controller]  [0m [0m19:51:11,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled [0m
Failed operation:
{
    "operation" => "read-resource",
    "address" => [
        ("host" => "master"),
        ("core-service" => "management"),
        ("service" => "management-operations"),
        ("active-operation" => "-305572225")
    ],
    "include-defaults" => true
}
Response:
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0216: Management resource '[
    (\"host\" => \"master\"),
    (\"core-service\" => \"management\"),
    (\"service\" => \"management-operations\"),
    (\"active-operation\" => \"-305572225\")
]' not found",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

Core - Full Integration Build 10303 outcome was FAILURE using a merge of 15a9b4d9a2a3c9aada20c0a027270c03e557448f
Summary: Tests failed: 1 (1 new), passed: 7144, ignored: 114 Build time: 03:43:46
Failed tests
org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase.testEntityCacheReplication: java.lang.AssertionError
	at org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase.testEntityCacheReplication(ClusteredJPA2LCTestCase.java:115)
------- Stdout: -------
 [0m23:41:05,776 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m23:41:06,127 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
 [0m [0m23:41:06,140 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m23:41:06,283 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting
 [0m [0m23:41:07,537 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.14.1.Final
 [0m [0m23:41:08,656 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 [0m23:41:08,773 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 40) 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 [0m23:41:08,926 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m23:41:08,943 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.8.4.Final
 [0m [0m23:41:08,952 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.8.4.Final
 [0m [0m23:41:09,026 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 68) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
 [0m [0m23:41:09,034 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m23:41:09,058 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 67) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m23:41:09,075 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 55) WFLYHEALTH0001: Activating Base Health Subsystem
 [0m [0m23:41:09,079 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 77) WFLYSEC0002: Activating Security Subsystem
 [0m [0m23:41:09,081 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
 [0m [33m23:41:09,107 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 80) 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 [0m23:41:09,107 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 58) WFLYRS0016: RESTEasy version 3.14.0.Final
 [0m [0m23:41:09,110 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 71) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m23:41:09,114 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 69) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m23:41:09,133 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 57) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m23:41:09,136 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 66) WFLYMETRICS0001: Activating Base Metrics Subsystem
 [0m [0m23:41:09,139 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 82) WFLYWS0002: Activating WebServices Extension
 [0m [0m23:41:09,146 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 61) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.2.11
 [0m [0m23:41:09,156 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 64) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m23:41:09,181 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.20.Final
 [0m [0m23:41:09,281 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 47) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m23:41:09,284 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.2.3.Final starting
 [0m [0m23:41:09,291 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
 [0m [0m23:41:09,291 INFO  [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
 [0m [0m23:41:09,298 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m23:41:09,354 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m23:41:09,644 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m23:41:09,693 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
 [0m [0m23:41:09,701 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
 [0m [33m23:41:09,705 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY00023: KeyStore file '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore' does not exist. Used blank.
 [0m [33m23:41:09,746 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY01084: KeyStore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
 [0m [0m23:41:09,769 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
 [0m [0m23:41:09,769 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m23:41:09,978 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m23:41:09,979 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
 [0m [0m23:41:10,066 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 84) MODCLUSTER000001: Initializing mod_cluster version 1.4.1.Final
 [0m [0m23:41:10,087 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 84) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m23:41:10,199 INFO  [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [0m23:41:10,209 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m23:41:10,267 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/deployments
 [0m [33m23:41:10,255 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m23:41:10,316 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on [::1]:8443

Core - Full Integration Build 10303 outcome was FAILURE using a merge of 15a9b4d9a2a3c9aada20c0a027270c03e557448f
Summary: Tests failed: 1 (1 new), passed: 7144, ignored: 114 Build time: 03:43:46
Failed tests
org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase.testEntityCacheReplication: java.lang.AssertionError
	at org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase.testEntityCacheReplication(ClusteredJPA2LCTestCase.java:115)
------- Stdout: -------
 [0m23:41:05,776 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
 [0m [0m23:41:06,127 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
 [0m [0m23:41:06,140 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
 [0m [0m23:41:06,283 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 23.0.0.Beta1-SNAPSHOT (WildFly Core 15.0.0.Beta1-SNAPSHOT) starting
 [0m [0m23:41:07,537 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.14.1.Final
 [0m [0m23:41:08,656 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 [0m23:41:08,773 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 40) 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 [0m23:41:08,926 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m23:41:08,943 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.8.4.Final
 [0m [0m23:41:08,952 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.8.4.Final
 [0m [0m23:41:09,026 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 68) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
 [0m [0m23:41:09,034 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m23:41:09,058 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 67) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 [0m [0m23:41:09,075 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 55) WFLYHEALTH0001: Activating Base Health Subsystem
 [0m [0m23:41:09,079 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 77) WFLYSEC0002: Activating Security Subsystem
 [0m [0m23:41:09,081 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00007
 [0m [33m23:41:09,107 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 80) 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 [0m23:41:09,107 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 58) WFLYRS0016: RESTEasy version 3.14.0.Final
 [0m [0m23:41:09,110 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 71) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m23:41:09,114 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 69) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 [0m [0m23:41:09,133 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 57) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
 [0m [0m23:41:09,136 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 66) WFLYMETRICS0001: Activating Base Metrics Subsystem
 [0m [0m23:41:09,139 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 82) WFLYWS0002: Activating WebServices Extension
 [0m [0m23:41:09,146 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 61) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.2.11
 [0m [0m23:41:09,156 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 64) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m23:41:09,181 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.20.Final
 [0m [0m23:41:09,281 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 47) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m23:41:09,284 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.2.3.Final starting
 [0m [0m23:41:09,291 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar @VERSION@)
 [0m [0m23:41:09,291 INFO  [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
 [0m [0m23:41:09,298 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m23:41:09,354 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m23:41:09,644 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m23:41:09,693 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
 [0m [0m23:41:09,701 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
 [0m [33m23:41:09,705 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY00023: KeyStore file '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore' does not exist. Used blank.
 [0m [33m23:41:09,746 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY01084: KeyStore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
 [0m [0m23:41:09,769 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
 [0m [0m23:41:09,769 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m23:41:09,978 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m23:41:09,979 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
 [0m [0m23:41:10,066 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 84) MODCLUSTER000001: Initializing mod_cluster version 1.4.1.Final
 [0m [0m23:41:10,087 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 84) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m23:41:10,199 INFO  [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [0m23:41:10,209 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m23:41:10,267 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/deployments
 [0m [33m23:41:10,255 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-4) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m23:41:10,316 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on [::1]:8443

Core - Full Integration Build 10322 outcome was FAILURE using a merge of 15a9b4d9a2a3c9aada20c0a027270c03e557448f
Summary: Execution timeout (new); tests passed: 7045, ignored: 113 Build time: 05:01:14

@jasondlee Could you please check the issue related to this PR (and link it in the commit message)?
https://issues.redhat.com/browse/WFCORE-2491 does not seem to be the correct issue...

https://issues.redhat.com/browse/WFCORE-4291 is the right one! ;)

@jasondlee Could you please check the issue related to this PR (and link it in the commit message)?
https://issues.redhat.com/browse/WFCORE-2491 does not seem to be the correct issue...

Wow. That's been that way forever. Fat fingered that. Got it fixed. :)

Core - Full Integration Build 10333 outcome was FAILURE using a merge of c80d8c33d9f235f9f84982820a0feef6c768c5a3
Summary: Execution timeout (new); tests passed: 6926, ignored: 110 Build time: 05:01:14

Pre-check is done, I'm merging this PR.
@jasondlee Thanks!


633 | Sum of Square Numbers | C++

Sum of Square Numbers -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[] Improving Code
[] Improving Documentation
[] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[] Python
[x] C++
[] Java
[] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Assign this to me please

assign this to me ,Iam ready.

Please assign this issue to me

please assign this to me

Hello I'm Interested to work on this. Pls assign this to me

@SSKale1 check the pull request I have mentioned here the issue was raised 5 days ago still the pull request is not merged


fix: fix old consignments nav

The type of this PR is: fix
This PR resolves MOPLAT-132
Description
The old consignments upload flow used to be presented modally but was changed to be presented via push while we were building the new consignments upload flow, this means the old dismissModal nav methods no longer worked. Instead this uses popToRoot() method and shows a back button rather than an X button on the initial overview screen.
Screenshots
https://user-images.githubusercontent.com/49686530/155795129-3c282368-a57e-4f1f-9641-4fff78d1f701.mp4
https://user-images.githubusercontent.com/49686530/155795146-dbe0bcd8-e954-424d-a398-25e49fca0e11.mp4

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Fix consignments upload nav - brian

iOS user-facing changes

Android user-facing changes

Dev changes

This PR contains the following changes:

Cross-platform user-facing changes (Fix consignments upload nav - brian)

  Generated by :no_entry_sign: dangerJS against bc3600be914b902bde7255d70fe0b54d6f409f4e

hmm, the PR is failing because of something you didn't change, this is weird

aha, this is happening because of mocking popToRoot that we send here

OMG I merged the PR instead of squashing it :(


Enable/Disable Siren switch missing

I see an Siren switch in HA, which conrols the siren (on/off). But I don't see the switch for the siren alarm on/off.
Using the latest versions of the integration and HA with an Reolink RCL-823A. Is this a general problem, or has this something to do with the cam model?

I have the opposite actually - I have the Siren and Spotlight flags in my 822a and the camera doesn’t support those

Oh I also have the siren and spotlight flag and I can turn both on and off with it. But whats missing is the switch for the alarm, so the siren doesn't go on when I enter the garden.

My bad misread that - not sure why the 822 is reporting capability it doesn’t have


HHH-14356 Fix NPE

Introduced by HHH-14334
when use Envers with hibernate.xml_mapping_enabled=false
see https://github.com/hibernate/hibernate-orm/commit/34151a9660f92dfd5128c1336fa9d27b8ca7f6e7#r44735539

Many thanks @quaff , I've merged this and will backport it to 5.4 too.