iso custom types example doesn't compile

Copied from the example for custom types in the README:
Welcome to Scala 2.12.3 (OpenJDK 64-Bit Server VM, Java 1.8.0_131).
Type in expressions for evaluation. Or try :help.

scala> import sjsonnew._, LList.:*:
import sjsonnew._
import LList.$colon$times$colon

scala> import BasicJsonProtocol._
import BasicJsonProtocol._

scala> case class Person(name: String, value: Int)
defined class Person

scala> implicit val personIso = LList.iso(
     |          { p: Person => ("name", p.name) :*: ("value", p.value) :*: LNil },
     |          { case (_, name) :*: (_, value) :*: LNil => Person(name, value) })
<console>:22: error: missing parameter type for expanded function
The argument types of an anonymous function must be fully known. (SLS 8.5)
Expected type was: ? => ?
                { case (_, name) :*: (_, value) :*: LNil => Person(name, value) })
                ^

I'm also wary of whether this is even useful at all - doesn't the builder in this case require the order of the JSON properties to be the order that appears in the LList? If that's so, it's not a compliant JSON converter, since compliant JSON converters should allow properties to appear in any order.

In 2.12.10, even simple examples don't compile:
case class Test(x: String)
implicit val testIso = LList.iso(
    { t: Test => ("x", t.x) :*: LNil },
    { case (_, x) :*: LNil => Test(x) }
)
// error: missing parameter type for expanded function
// The argument types of an anonymous function must be fully known. (SLS 8.5)
// ...

The low-level API still works as expected, though, so that's what I used as a workaround for now.

I've found that you can actually make the high-level API work if you help out Scala's type inference:
LList.iso[Test, Int :*: LNil](
    { test: Test => ("test", test.x) :*: LNil },
    { case (_, x) :*: LNil => Test(x) }
)


Boostrap 4 .modal-dialog-scrollable does not work when EasyMDE is enabled

Describe the bug
I want to enable Bootstrap's modal-dialog-scrollable class so that I can have a scrollable modal body (dialog). But when I enable EasyMDE on that textbook, it stops working. Can you please help?
Screenshots

Version information

OS: [e.g. Zorin OS]
EasyMDE version: v2.9.0
Bootstrap version: 4.3.1

Did you try ?
.on('shown.bs.modal', function (e) {});

Did you try ?
.on('shown.bs.modal', function (e) {});


Add data source - confluent_schemas

Usage :
provider "confluent" {
  schema_registry_id            = var.schema_registry_id
  schema_registry_api_key       = var.schema_registry_api_key
  schema_registry_api_secret    = var.schema_registry_api_secret
  schema_registry_rest_endpoint = var.schema_registry_rest_endpoint
}

data "confluent_schemas" "schemas" {
  filter {
    subject_name = "examples.record-value"
    latest_only = false
    deleted = false
  }
}

Outputs :
Changes to Outputs:
  + confluent_schemas = [
      + {
          + format            = "PROTOBUF"
          + schema            = <<-EOT
                syntax = "proto3";
                package examples;

                message SomeRecord {
                  string value1 = 1;
                }
            EOT
          + schema_identifier = 100007
          + subject_name      = "examples.record-value"
          + version           = 1
        },
      + {
          + format            = "PROTOBUF"
          + schema            = <<-EOT
                syntax = "proto3";
                package examples;

                message SomeRecord {
                  string value1 = 1;
                  string value2 = 2;
                }
            EOT
          + schema_identifier = 100008
          + subject_name      = "examples.record-value"
          + version           = 2
        },
    ]

Closes: https://github.com/confluentinc/terraform-provider-confluent/issues/211

Thanks for creating a great PR @FabioBatSilva!
Unfortunately our CI doesn't allow community PRs yet but we'll merge this fix or a slightly updated version of it internally (and include to our next release) and will work on fixing our CI to allow community PRs in the future!
I've got a quick question: after reading this doc:

Boolean attributes like monitoring are usually written also as nouns describing what is being enabled. However, they can sometimes be named as verbs if the attribute is specifying whether to take some action, as with the delete_on_termination flag within the root_block_device block.

Boolean attributes are ideally oriented so that true means to do something and false means not to do it; it can be confusing to have "negative" flags that prevent something from happening, since they require the user to follow a double-negative in order to reason about what value should be provided.

Do you think we might want to update naming of

latest_only, deleted

The last quick thing is we might want to use hard_deleted or soft_deleted instead of just deleted, wdyt?

@FabioBatSilva right but there're 2 types of deletions for schemas: soft and hard delete.

@FabioBatSilva right but there're 2 types of deletions for schemas: soft and hard delete.

hard_deleted we will never be able to list right ?
might be why the GetSchemas api only support one of then (deleted).. :thinking:

That's a great catch!

@FabioBatSilva another qq: wdyt about subject_name vs subject_prefix:

I think subject_prefix makes sense assuming we can query all schemas starting with that value..
something like subject_prefix = "examples.*"

Thanks! For the context, I'm making a few edits this PR so we could include it in our next release early next week, thanks for the great work!

Update: we

Added new confluent_schemas data source in a Preview lifecycle stage.

in our latest 1.36.0 version of TF Provider.
cc @FabioBatSilva @navroopbath


How to get the osmos address given mnemonic?

Something like
import { Secp256k1HdWallet } from '@cosmjs/amino';

const offlineSigner = await Secp256k1HdWallet.fromMnemonic(
  'element fiber pioneer artefact harbor wear lawsuit trouble damage dance live fetch',
  { prefix: 'osmo' }
);
const address = (await offlineSigner.getAccounts())[0].address;
console.log('New account generated:', offlineSigner.mnemonic);
console.log('Address:', address);


Patch 3

Hi AdilKhn, im making a pull request to update the library so the user can change the color of the loader or spinner.
Added the "spinnerColor" property with a defaultProp of white "#fff" as it was defined.
That is in case the user needs to erase the background of the spinner and still can see the spinner if your app has a white background.
Thanks!

Sorry im new to this, but please let me know if i have to do anything else so this changed can be merged.
Thanks and have a nice day!


n-gram model

Try a n-gram model.

Type of crime tagging has a model that is "good enough" for now. If there's a concerted push to get better performance then I will create a new issue to track that progress.


Update Composer dependencies (2022-02-04-00-06)

Visual regression test passed!
View the visual regression test report


API

this is way in the future probably but would be cool to expose an API for people to hit

this has been requested a couple of times. should consider exposing an API and documenting it in the README or on the site itself

This sort of came up in an issue here https://github.com/avelino/awesome-go/issues/683
Would be nice to at least document the /checks endpoint so people don't need to find it themselves.

Big :+1: to an API. For 18F's micro-purchase project, we use various automated tests to help ensure the quality of code submitted for tiny government contracts. If we ever required a vendor to create a golang project/repo, this would be a wonderful tool to use. We could set a minimum threshold grade as part of the acceptance criteria.


GitHub Enterprise support

This PR is to add support for GitHub Enterprise by letting the github.com URL to be configurable and remove hardcoded URLs from the code base.
Testcases have been added for this, too.
Also some minor issue where fixed along the way, each in its own commit:

Properly generate the key on OSX 10.14
Fix #14 as per the issue
Discover the stage name in a Lambda deployment
Update dependencies to solve known issues (npm audit)

Thanks very much for this!
Could you comment a bit on the key generation issue? I developed this on OSX 10.14, and didn't have any problems.

On small comment - In the commit message, you link the Auth0 documentation to show the default location for jwks is at /.well-known/. I believe that's the documentation for the Auth0 product, and not the OpenID spec. Although much of the information is the same, the Auth0 docs shouldn't be a source for implementers.
As far as I am aware, this isn't defined by any relevant standard or RFC, and so I think it's a Cogntio bug not to use the URL returned by the discovery endpoint.
However, since we know what the issue is (and most implementations put the jwks uri under /.well-known/ anyway) we should still fix it - and the PR is very much appreciated.

so I think it's a Cogntio bug not to use the URL returned by the discovery endpoint.
Yes I think you are right - the Auth0 was just the only resource I could find 'as reference'.
But yes, everything you said :-)

Without -m PEM it would fail in crypto.js with
crypto.js:331
  var ret = this._handle.sign(toBuf(key), passphrase, rsaPadding,
                         ^

Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
    at Sign.sign (crypto.js:331:26)
    at Object.sign (~/development/oss/github-cognito-openid-wrapper/node_modules/jwa/index.js:76:45)
    at Object.jwsSign [as sign] (~/development/oss/github-cognito-openid-wrapper/node_modules/jws/lib/sign-stream.js:32:24)
    at Object.module.exports [as sign] (~/development/oss/github-cognito-openid-wrapper/node_modules/jsonwebtoken/sign.js:188:16)
    at Object.makeIdToken (~/development/oss/github-cognito-openid-wrapper/src/crypto.js:26:16)
...

(Note: The lines might be a little bit off as I added a ton of debug logging not included in the PR)
The offending key:
$ file jwtRS256.key
jwtRS256.key: OpenSSH private key

The working key (with -m PEM as per 9d857c3):
$ file jwtRS256.key
jwtRS256.key: PEM RSA private key

My software versions:
$ ssh -v localhost
OpenSSH_7.9p1, LibreSSL 2.7.3

$ openssl version
LibreSSL 2.6.5

$ node --version
v8.16.0

Thanks again for this!


Name prop bug in Input component

Description
Added unused name prop to Input component.

Hi @imshubhamsingh. Please re-open this PR without forking.


Use native Math functions in the custom log2 function

It is quite confusing that the custom function is called log2 while it actually returns the ceiling value and handles zero and negative values differently than the native function.
To resolve this, we add a comment that explains these differences and make the function use the native Math functions internally instead of using our own custom logic. To verify that the function does what we expect, we add unit tests.
All browsers except for IE support Math.log2 for quite a long time already (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/log2). For IE, we use the core-js polyfill.
According to the microbenchmark at https://jsperf.com/log2-pdfjs/1, using the native functions should also be faster, in my testing almost six times as fast.

/botio-linux preview

/botio test

/botio-linux preview

Unfortunately Math.ceil(Math.log2(x)) still isn't entirely compatible with the old helper function, compare e.g. the result of x = 0 for the old/new code :-(

I have updated the patch to make sure that there are no difference in the implementations anymore.

/botio-linux preview

/botio test

I have updated the commit to adjust the comment above log2. No functional changes have been made.

/botio unittest


Rust tests with mod names other that default 'mod tests' filtered out and not run.

Hi there, thanks for this super plugin.
I have encountered an issue with using the plugin to test Rust projects.
It appears that the code is trying to perform an --exact flagged cargo test with the incorrect mod name, ie:
cargo test tests::my_test_function -- --exact`

This causes the test case to be filtered out, instead of being run, which shows up as a always passing test.
I don't use a default 'tests' mod, but one named after the area I am testing, eg
mod widget_tests

This means that the correct command should be:
cargo test my_specific_tests::my_test_function -- --exact

Multiple of these named modules can and do exist in the file being tested, as shown together with correct and current incorrect calls in the  terminal alongside(after doing a Nearest Test) :

An example of the correct terminal command running shown here:

One with the current incorrect invocation, using the hardcoded module tests and the result getting filtered out, over here:

I have uploaded the minimal test case repo here:
Link
Hope this explains the issue clearly enough, let me know if I can give any more details, thanks.

If I run the command:
''
cargo test -- -Z unstable-options --format json
''
I get the results:

''
{
"type": "suite",
"event": "started",
"test_count": 3
}
{
"type": "test",
"event": "started",
"name": "my_other_specific_tests::it_works"
}
{
"type": "test",
"event": "started",
"name": "my_second_specific_tests::it_works"
}
{
"type": "test",
"event": "started",
"name": "my_specific_tests::it_works"
}
{
"type": "test",
"name": "my_second_specific_tests::it_works",
"event": "ok"
}
{
"type": "test",
"name": "my_other_specific_tests::it_works",
"event": "failed",
"stdout": "thread 'my_other_specific_tests::it_works' panicked at 'assertion failed: (left == right)\n  left: 2,\n right: 4', src/lib.rs:25:9\nnote: run with RUST_BACKTRACE=1 environment variable to display a backtrace\n"
}
{
"type": "test",
"name": "my_specific_tests::it_works",
"event": "failed",
"stdout": "thread 'my_specific_tests::it_works' panicked at 'assertion failed: (left == right)\n  left: 2,\n right: 4', src/lib.rs:6:9\n"
}
{
"type": "suite",
"event": "failed",
"passed": 1,
"failed": 2,
"ignored": 0,
"measured": 0,
"filtered_out": 0,
"exec_time": 0.000321702
}
''

I put this here wondering if you think it's simpler making another test runner based on this command?

I believe this is a vim-test issue. You just need to update the regex used to match the namespace in the cargo file here https://github.com/vim-test/vim-test/blob/master/autoload/test/rust/cargotest.vim#L8. They'll be happy to take a PR, just make sure to add a test to handle the new case :smile:


How to test my images without label?

I want to run "Interactive-User-Interface.ipynb" ,but I cannot see any output images, can you show the simple user guider?

Hi, can you expand on the problem you're having?
Do you see any output image at all? Right now it's programmed to output the mask overlaying the original image.

What are you supposed to click on in the photo? Instructions would be nice.

I think I figured it out. Left click to indicate something should be added to the foreground, right click to indicate it should be removed.


Some tiles are missing

I use a command
$ gdal2tiles-multiprocess.py --leaflet --processes=6  raster -z 0-4 -w none karta.jpg /tiles
and tiles 0-0-0 and 1-1-0 are missing
but
$ gdal2tiles-multiprocess.py --leaflet --processes=2  raster -z 0-4 -w none karta.jpg /tiles
gives me a full set of tiles

$ gdal2tiles-multiprocess.py --leaflet --processes=6 -p raster -z 0-4 -w none karta.jpg /tiles
$ gdal2tiles-multiprocess.py --leaflet --processes=2 -p aster -z 0-4 -w none karta.jpg /tiles

Is there any update on this issue?

When using 2 cores,  this bug does not occur

Even with 2 cores, it takes a long time to tile a PNG image that's 2GB and more in size.

i had the same issue. the fix was from moving from multi processing to single processing. quite annoying, but still works.


Feature and checkpoint review

Changes Unknown when pulling 475ea05a5de59718198510a88a69cdac2ec76545 on feature-review into ** on develop**.

Changes Unknown when pulling 475ea05a5de59718198510a88a69cdac2ec76545 on feature-review into ** on develop**.

Changes Unknown when pulling 475ea05a5de59718198510a88a69cdac2ec76545 on feature-review into ** on develop**.

Changes Unknown when pulling 53b452b8a4fe9c58488c9be61b6d26bc83c02e80 on feature-review into ** on develop**.

Changes Unknown when pulling 64ba110249c9c6aeaaff10ba3c4c49e773b3e621 on feature-review into ** on develop**.

Changes Unknown when pulling 3b0698ffc7aa9baa0410a298cf0372457605f62b on feature-review into ** on develop**.

Changes Unknown when pulling 2ca277861ac18d94db4c71ea2c19328dd4925283 on feature-review into ** on develop**.

Changes Unknown when pulling 8fadd09dac16689cb535898892c76625b6848e62 on feature-review into ** on develop**.

Changes Unknown when pulling e2f5155f62b20220b983c5dc00daf50ab96ef462 on feature-review into ** on develop**.

Changes Unknown when pulling 4991307e8dcc991fe71e12afcd2e45ed5e4bfb64 on feature-review into ** on develop**.

Changes Unknown when pulling e70b033681088088bc831e3ceaa41b48135052f1 on feature-review into ** on develop**.

Changes Unknown when pulling e69b0726c90d99f1906cb7fd276cdb7231eebb16 on feature-review into ** on develop**.

Changes Unknown when pulling 01a80c65e7b73a7f92e6c441fd4f1149389c98ec on feature-review into ** on develop**.

Changes Unknown when pulling 9df0023409058433663d4da1448fb6ff0a371c31 on feature-review into ** on develop**.

Changes Unknown when pulling 64e3045199dd89022ec68730504e18b0277b01b4 on feature-review into ** on develop**.

Changes Unknown when pulling bfadf7a98fd0c73378cfb6d2c217edb0663523a8 on feature-review into ** on develop**.

Changes Unknown when pulling 183a56ae35c024e64a9b1c7a9a9deabaf4f5bdaa on feature-review into ** on develop**.

Changes Unknown when pulling 183a56ae35c024e64a9b1c7a9a9deabaf4f5bdaa on feature-review into ** on develop**.

Adds comments to code on all the actions.py module.
Adds test coverage.
Uses pep8 style imports on the modules that import several functions from other modules.
Spaces out system imports with blank lines from local imports.

Configures the project to work with coveralls.io.

Changes Unknown when pulling 739db8b6d61acd1ed494e38eb8a9c981f9ce6ca5 on feature-review into ** on develop**.

@njirap Changes as recommended by @andela-aabdulwahab made and tests rerun.

Changes Unknown when pulling 70cb64fbf549ed6d361eb7a71c2f420f7c1b08b1 on feature-review into ** on develop**.

Changes Unknown when pulling 00e7d0fb313a2832de29414c2c783a792e720cff on feature-review into ** on develop**.

Hi @njirap, Kindly see the latest commit with changes as suggested by Erika if you dont mind.

Changes Unknown when pulling 3d683e5e915bc9c7a7d3cb8e483561bc296f641b on feature-review into ** on develop**.


allow optional parameters to upgrade_to

@abezzub Can you please review?
This allows passing optional argument (i.e. webhook) to the upgrade_to resource.

lgtm


Annotations necessary for Animal (rodent) research

Discovering missing from https://www.hedtags.org/display_hed.html as we try to potentially annotate a dataset

"lick" as event
"running wheel"

there would need annotation of attributes such as "angular position"

attn @mvdm @manimoh @kleaman

Lick should be an Action.  The corresponding event tag is: Agent-action.  In the current schema, this might be tagged as:
(Agent-action, Perform/Lick).  Here I arbitrarily indicated that Lick was in the Perform subtree.
If a library schema had a 'Licktag, then we could tag as(Agent-action, Lick)`.  You could modify by what was being licked or the direction of the lick.

This is an interesting question. We have had a long debate about the items under Perceive (Hear, See, Sense-by-touch, Smell, Taste) which imply that the agent is perceiving through senses.
There are also analogous Perform  (Listen, Look, Touch, Sniff, Lick) that are not currently in the schema and are the analogous actions to try to sense.  We probably need to revisit.  We now also have the mechanisms to add connecting properties to the schema connecting tags such as Lick and Taste, but we haven't done much about them yet.
There are also actions such as "whisk" which are unique to animals that have whiskers.  These would probably go into a library schema for animal annotation.
Note a related discussion about animal annotation in bids-standard/bids-specification/#1839. HED can also be used to annotate participants.tsv.


As a dev, I want to fix the AttributeError in the analyze function

Description
Context
The unit test test_analyze fails due to an AttributeError.
Problem Statement
Error in test:
AttributeError: 'Prediction' object has no attribute 'rationale'

Additional information
Possibly due to new version of dspy. Working version: 2.4.13.
And some warnings:
WARNING:root:   *** In DSPy 2.5, all LM clients except `dspy.LM` are deprecated. ***
                You are using the client AzureOpenAI, which will be removed in DSPy 2.6.
                Changing the client is straightforward and will let you use new features (Adapters) that improve the consistency of LM outputs, especially when using chat LMs.

                Learn more about the changes and how to migrate at
                https://github.com/stanfordnlp/dspy/blob/main/examples/migration.ipynb

Will be fixed in https://github.com/ai-cfia/fertiscan-pipeline/pull/51


Instructions for Undocking unclear

I want to "Undock into separate window" using "Change placement from the main menu". Yet, the screenshots and the descriptions do not help me to find "Click Customize and control DevTools". If this tutorial is only vaild for some beta/insiders build, this info is missing (found the page via Google).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a0dff9d4-34da-5563-4b34-ca5ef03ade06
Version Independent ID: 55519333-e802-ec65-1b49-8fe64fe04825
Content: Change DevTools placement (Undock, Dock to bottom, Dock to left) - Microsoft Edge Development
Content Source: microsoft-edge/devtools-guide-chromium/customize/placement.md
Product: microsoft-edge
Technology: devtools
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thank you for your feedback. I agree that the screenshot is not helpful. We usually draw red rectangles around the areas that need to be clicked to match with the text instructions. But this one doesn't have anything.
I'll create a task on our backlog to improve this and we'll close this issue once the change has been made.

@captainbrosset - Already fixed, as part of the pending, open PR 1665.
https://review.docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/customize/placement?branch=pr-en-us-1665 - shows entire window as context, with red box around Customize and control DevTools (...) and red box around the list of layouts.


Rubber band

Hi,
What is code to implement a rubber band in napari and get the corners?
Or where can we find the documentation?
Thank you,

Hi @JosephBendahan, after a quick search I presume you mean the path extension/rubber band mode that you can find in Photoshop/Illustrator? If so, then that doesn't exist in napari, nor do we have immediate plans to support it. The closest thing we have is cubic interpolation as demonstrated in #5334. (You need to be on the main branch to use that, it has not yet been released.)


The put method should update existing folder contents

Problem:
When the cli put method receives a folder that already exists on the target board it completely skips that folder.
This makes updating projects with multiple sub-folders a pain.
Proposed solution
In this pull request when a folder is passed to the put method the files.DirectoryExistsError does not prevent the copy/overwrite action of the child files. Thus the folder contents are updated. Also:

The update action is implied in the original method description.
When the same method is used with single files it already does an update action

Thank you for your contribution.


Can't associate *.org with org4idea

I'm in a new Rubymine and I can't seem to associate a .org file with the plugin anymore :/

Is there any relevant intry in the Event Log?

No, nothing in the log. An existing x.org file just opens as a text file, and if I create a new y.org it asks me what to associate it with but I don't have any option for a .org management.

I just downloaded RubyMine and I could reproduce your exact behavior. Were you able to properly work with the previous version of org4idea?

Yes - that's how I discovered org4idea and came to this repo in the first
place :)
On Wed Feb 25 2015 at 1:34:57 PM Carlo Sciolla<EMAIL_ADDRESS>wrote:

I just downloaded RubyMine and I could reproduce your exact behavior. Were
you able to properly work with the previous version of org4idea?
—
Reply to this email directly or view it on GitHub
https://github.com/skuro/org4idea/issues/2#issuecomment-76025739.

Funny thing is that the same is happening to me. (while it was working with the jar I made).
I didn't tried yet to rebuild with the exact same commit and see if it's occur too.
(I had supposed it was due because I had the homemade jar before since I hadn't seen people upsetting about)

I also have the same problem. Installing manually with downloaded jar file(v0.1) solve the problem. Updating v0.2 and the problem happens again

Did you try by hand installing the 0.2? (getting more clues before the hunting)
I have to admit, I didn't have that much time to dig into it lately.
(I had look at the diff, but nothing hit me. Was working locally when I made the 0.2 publication, wouldn't have published otherwise)
I'll see what I can do but I promise anything in the short term. sorry about that :/

I did the following (on OSX):

Installed org4idea
Restarted Rubymine
Tried to create .org file => No .org extension handler available.
Found file in ~/Library/Application Support/Rubymine70 and copied it to ~/Downloads
Uninstalled org4idea
Restarted Rubymine
Installed from disk the jar I copied
Restarted Rubymine
Tried to create .org file => No .org extension handler available.

I can email you that jar file if you want.
Can I download a jar for 0.2 other than the way I did it?

@Trevoke not really, I think the issue is really there, but so far I couldn't find anything wrong in the code.
@dephiros what IDE are you using, you also on RubiMine or IDEA?

I am using PHPStorm
On Tue, Jul 28, 2015 at 12:25 AM Carlo Sciolla<EMAIL_ADDRESS>wrote:

@Trevoke https://github.com/Trevoke not really, I think the issue is
really there, but so far I couldn't find anything wrong in the code.
@dephiros https://github.com/dephiros what IDE are you using, you also
on RubiMine or IDEA?
—
Reply to this email directly or view it on GitHub
https://github.com/skuro/org4idea/issues/2#issuecomment-125481776.

Hey @all!
Sorry for that last answer, didn't have much opportunity to dug on this.
I don't know if it's jetbrain teams that had rebuild the package, but when I installed the plugin today for new version of Rubymine and Webstorm, upgrading/or installing the org4Idea module.
It was working right away.
What about you?

Has problem solve itself?
Otherwise try to reinstall, and tell me how it goes.
If it's okey for everyone, I will mark the issue as (mysteriously) resolved.

I will try again, but there's little to no chance that the package was rebuilt I think (no pushes / code changes since long time now). I will try again (need to experiment with IDEA 15 anyway) and comment here with my findings.

Hey @skuro, did you had the opportunity to try?
I made sevral fresh install on different os with new versions of  Rubymine, Intellij and Webstorm,
and was working each time.

I tried with IntelliJ IDEA v14 and v15, and I couldn't reproduce the issue. I'm currently downloading RubyMine v8 and WebStorm v11 to see whether it's any different there.

Okey, I close the issue. Reopen it if you find anything :)

Gave it a shot with fresh installs of RubyMine and WebStorm, no issues were found

that will remain a mistery :)


Christy's request regarding # of pre-1900 digitised books

Email from Natalie after she talked to Christy

Re the question from Christy, she wants to know the number of copies (items, not bibs) of pre-1900 books we hold that are not yet digitised, and as a proportion of the total.
So is it possible to get:
Total number of items for the bib format book printed before 1900
Number of those that haven’t been digitised
These will all have to be unsuppressed, I think
And also have a bib level value of monograph (as opposed to e.g. chapt/article)

Christy's original email

I’m trying to compare how many books we’ve digitised against the entirety of the catalogued collection. This is proving quite tricky to do through the user interfaces.

Is it possible to use the API to find out how many books we have catalogued in Sierra that were published before 1900?
And following on from that, is it possible to tell which ones do not have a version that’s digitised/hosted by Wellcome (as opposed to third party subscription sites)? And then to export a list of those?
Happy to chat further if anyone has time to look into this – it’s not super urgent.

Query
// works that are books
// that were produced before 1900
// that are not available online
get works-indexed-2024-08-15/_count
{
  "query": {
    "bool": {
      "must": [
        {
          "match": {
            "filterableValues.format.id": "a"
          }
        },
        {
          "range": {
            "query.production.label": {
              "lt": 1900
            }
          }
        }
      ],
      "must_not": [
        {
          "match": {
            "filterableValues.availabilities.id": "online"
          }
        }
      ]
    }
  }
}

Aggs to add up the items for the found works
"aggs": {
    "total_items_id": {
      "sum": {
        "script": {
          "source": "doc['query.items.id'].length"
        }
      }
    }
  }

I have a local script to query the index and parse the hits into a csv, with identifier (bNumber), title and workId (potentially looking to format these into works url)

Blocked: Christy is on leave right now and we need some clarifications on a few points

210632 books published before 1900
51719 of which are not available online
Sent Christy a CSV list of the 1st 10000 hits

you can pause on this if you like, I'm checking whether locations would helpful or not to add in determining sets that are suitable for digitisation (there's a lot of stuff on the list of 10k that you sent that we have already looked through, journals catalogued as books, etc. but location might help to narrow down the collections we're interested in.

Closing this. Will open new issue if she wants the location added


[WFLY-5564] Unable to set use-journal-store if use-jdbc-store was set…

… to true before
https://issues.jboss.org/browse/JBEAP-1354
https://issues.jboss.org/browse/WFLY-5564
Modifications:

Removed USE_JDBC_STORE.setAlternatives(USE_JOURNAL_STORE) and inverse because it prevented to set the first even if the other was set to false. Implemented special write handler to validate this correctly.
Removed JDBC_STORE_DATASOURCE.setRequires(USE_JDBC_STORE) and instead implemented special write handler checking that JDBC_STORE_DATASOURCE is set if USE_JDBC_STORE is true.

TransactionSubsystemAdd should do these validations as well.

Ah sorry, forgot about that during weekend.

Thanks for reminding me!

@n1hility You asked about the compatibility impacts of this. I believe the only impacts are:
In WildFly < 10 this would work:
{code}
/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true)
/subsystem=transactions:write-attribute(name=jdbc-store-datasource,value=java:datasources/blah)
{code}
Now it won't. The user would have to encapsulate those two calls in a batch.
The old behavior was incorrect as the first operation by itself puts the config in an invalid state. This PR corrects that by adding appropriate validation.
The business with .setAlternatives() on USE_JOURNAL_STORE and USE_JDBC_STORE won't affect compatibility since prior to WF 10 there was no checking of those constraints. Also, the "alternatives" support in the kernel isn't really appropriate for these attributes, as the constraint is really that both can't be defined with a value of 'true' while the kernel rejects any case where they are both defined, regardless of value. I'd like to enhance the kernel to somehow account for this distinction, but in the meantime it's not correct to say the two attributes are alternatives given the present meaning of the metadata.

Updated

test ObjectStoreTypeTest renamed to ObjectStoreTypeTestCase so it's part of normal surefire execution.
test for hornetq store remains
added validations to TransactionSubsystemAdd

Windows Build 3691 outcome was FAILURE using a merge of 0eb316f437b472f6b2cab2ad6f4666ab20507ce5
Summary: Tests failed: 7 (7 new), passed: 3281, ignored: 363 Build time: 00:54:46
Failed tests
org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.establishTopology(ClusteredWebFailoverAbstractCase.java:256)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:171)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)
------- Stdout: -------
13:52:59,134 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:52:59,135 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:52:59,135 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:52:59,145 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\e1\5e1207cc49223487d9954a1253470bfd9a894d\content
13:52:59,147 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
13:52:59,171 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:52:59,172 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:52:59,172 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:52:59,177 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment coarse-distributable.war
13:52:59,183 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "coarse-distributable.war"' are as follows:

	java:global/coarse-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/coarse-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/coarse-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/coarse-distributable/TopologyChangeListenerBean
	java:app/coarse-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

13:52:59,206 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,207 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 29) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,208 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: coarse-distributable.war
13:52:59,213 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,214 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,213 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Starting weld service for deployment coarse-distributable.war
13:52:59,215 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,215 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:52:59,235 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0002: Started coarse-distributable.war cache from web container
13:52:59,236 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) WFLYCLINF0002: Started dist cache from ejb container
13:52:59,236 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started dist cache from web container
13:52:59,358 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 3) WFLYUT0021: Registered web context: /coarse-distributable
13:52:59,372 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "coarse-distributable.war" (runtime-name : "coarse-distributable.war")
13:52:59,378 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
13:52:59,388 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\e1\5e1207cc49223487d9954a1253470bfd9a894d\content
13:52:59,390 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
13:52:59,412 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:52:59,413 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:52:59,413 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.coarse-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:52:59,418 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment coarse-distributable.war
13:52:59,424 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "coarse-distributable.war"' are as follows:

	java:global/coarse-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/coarse-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase(SYNC-tcp).testInvalidate: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase.establishTopology(InvalidateConversationTestCase.java:129)
	at org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase.testInvalidate(InvalidateConversationTestCase.java:93)
------- Stdout: -------
13:53:25,093 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:25,093 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:25,094 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:25,094 INFO  [org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer] (main) Deploy arquillian service: arquillian-service: 977 assets
13:53:25,823 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\0d\2811fbd061a5ec5ae7f91083511a760fe1f816\content
13:53:25,827 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "arquillian-service" (runtime-name: "arquillian-service")
13:53:25,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
13:53:25,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:25,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.jboss.jandex:main") which may be changed or removed in future versions without notice.
13:53:25,982 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.arquillian-service" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
13:53:25,990 WARN  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0013: Deployment deployment "arquillian-service" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
13:53:26,022 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "arquillian-service" (runtime-name : "arquillian-service")
13:53:26,118 WARN  [org.jboss.remotingjmx.Util] (main) The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
13:53:26,191 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\0d\0baa63bfab758c58ab308a004f5f4f7fdab329\content
13:53:26,197 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "conversation.war" (runtime-name: "conversation.war")
13:53:26,227 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:53:26,227 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:26,227 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:53:26,227 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
13:53:26,235 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment conversation.war
13:53:26,239 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "conversation.war"' are as follows:

	java:global/conversation/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/conversation/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/conversation/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/conversation/TopologyChangeListenerBean
	java:app/conversation/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

13:53:26,269 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,269 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Starting Services for CDI deployment: conversation.war
13:53:26,269 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,278 INFO  [org.jboss.as.arquillian] (MSC service thread 1-8) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."conversation.war",unit=conversation.war,tests=[org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase]]
13:53:26,279 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 6) WFLYCLINF0002: Started dist cache from ejb container
13:53:26,281 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment conversation.war
13:53:26,289 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,290 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,291 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,291 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:26,299 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0002: Started dist cache from web container
13:53:26,302 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 6) WFLYCLINF0002: Started conversation.war cache from web container
13:53:26,467 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0021: Registered web context: /conversation
13:53:26,482 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "conversation.war" (runtime-name : "conversation.war")

org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test: java.lang.AssertionError: null
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
13:53:42,044 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:42,044 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:42,045 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:42,054 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\af\24ea8ed8fa15edb672d520793e503de7ab3232\content
13:53:42,056 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
13:53:42,113 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,114 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,118 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,119 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 83) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,122 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started dist cache from web container
13:53:42,130 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started expiration.war cache from web container
13:53:42,142 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0021: Registered web context: /expiration
13:53:42,155 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
13:53:42,160 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
13:53:42,170 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\af\24ea8ed8fa15edb672d520793e503de7ab3232\content
13:53:42,173 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
13:53:42,221 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,222 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,242 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0002: Started dist cache from web container
13:53:42,243 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,243 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,509 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started expiration.war cache from web container
13:53:42,573 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0021: Registered web context: /expiration
13:53:42,583 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
13:53:42,611 INFO  [stdout] (default task-2) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=mzKIVy8U6tAxeM1x-e3Nree6wc5dA9-HaeEYZhpI

13:53:42,631 INFO  [stdout] (default task-3) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=mzKIVy8U6tAxeM1x-e3Nree6wc5dA9-HaeEYZhpI

13:53:42,642 INFO  [stdout] (default task-22) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=gPu7qjUHlpokyDhYnzycqmoF1s4-RE1N6TbDSNpl

13:53:42,646 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:42,647 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:42,647 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
13:53:42,652 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0022: Unregistered web context: /expiration
13:53:42,657 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 84) ISPN000029: Passivating all entries to disk
13:53:42,676 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 84) ISPN000030: Passivated 3 entries in 18 milliseconds
13:53:42,679 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0003: Stopped expiration.war cache from web container
13:53:42,683 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000029: Passivating all entries to disk
13:53:42,683 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000030: Passivated 0 entries in 0 milliseconds
13:53:42,688 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0003: Stopped dist cache from web container
13:53:42,692 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 42ms
13:53:42,706 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\af\24ea8ed8fa15edb672d520793e503de7ab3232\content
13:53:42,706 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
13:53:42,710 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
13:53:42,714 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0022: Unregistered web context: /expiration
13:53:42,717 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000029: Passivating all entries to disk
13:53:42,721 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000030: Passivated 3 entries in 3 milliseconds
13:53:42,723 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0003: Stopped expiration.war cache from web container

org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test: java.lang.AssertionError: null
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
13:53:42,759 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:42,760 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:42,760 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:42,772 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\89\d5d68d24e02d079100445871cdb854a0ad541f\content
13:53:42,776 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
13:53:42,824 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,825 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,826 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,826 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,834 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started expiration.war cache from web container
13:53:42,838 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0002: Started dist cache from web container
13:53:42,850 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0021: Registered web context: /expiration
13:53:42,862 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
13:53:42,867 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
13:53:42,877 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\89\d5d68d24e02d079100445871cdb854a0ad541f\content
13:53:42,879 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
13:53:42,941 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,941 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 87) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,944 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,944 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:42,948 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started expiration.war cache from web container
13:53:42,948 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0002: Started dist cache from web container
13:53:42,967 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0021: Registered web context: /expiration
13:53:42,979 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
13:53:43,003 INFO  [stdout] (default task-4) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=pwMADb7UkwWvk0hgULQ9KYhAcrM_vtb9gWU8az9K

13:53:43,009 INFO  [stdout] (default task-5) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=pwMADb7UkwWvk0hgULQ9KYhAcrM_vtb9gWU8az9K

13:53:43,016 INFO  [stdout] (default task-23) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=1aoDkIVqOUZ94EXbZPlrzfhqAhNnmmNZM_Re8l2i

13:53:43,020 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:43,021 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:43,021 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
13:53:43,024 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0022: Unregistered web context: /expiration
13:53:43,027 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000029: Passivating all entries to disk
13:53:43,030 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000030: Passivated 3 entries in 2 milliseconds
13:53:43,032 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped expiration.war cache from web container
13:53:43,035 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
13:53:43,035 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 0 entries in 0 milliseconds
13:53:43,039 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped dist cache from web container
13:53:43,043 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 19ms
13:53:43,054 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\89\d5d68d24e02d079100445871cdb854a0ad541f\content
13:53:43,054 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
13:53:43,055 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
13:53:43,059 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0022: Unregistered web context: /expiration
13:53:43,065 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 85) ISPN000029: Passivating all entries to disk
13:53:43,066 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 85) ISPN000030: Passivated 2 entries in 1 milliseconds
13:53:43,068 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0003: Stopped expiration.war cache from web container

org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(SYNC-tcp).test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.assertValue(ExternalizerTestCase.java:109)
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test(ExternalizerTestCase.java:97)
------- Stdout: -------
13:53:43,097 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) externalizer.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/META-INF/
/WEB-INF/classes/META-INF/services/
/WEB-INF/classes/META-INF/services/org.wildfly.clustering.marshalling.Externalizer
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/Counter.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterExternalizer.class
/WEB-INF/web.xml
13:53:43,098 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) externalizer.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/META-INF/
/WEB-INF/classes/META-INF/services/
/WEB-INF/classes/META-INF/services/org.wildfly.clustering.marshalling.Externalizer
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/Counter.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/cluster/web/externalizer/CounterExternalizer.class
/WEB-INF/web.xml
13:53:43,101 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:43,101 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:43,102 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:43,120 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\e4\3fa195bbe921c0c703210b068ab6a7a6f9c6b9\content
13:53:43,122 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
13:53:43,174 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,175 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,183 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,183 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,200 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started externalizer.war cache from web container
13:53:43,200 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started dist cache from web container

org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.establishTopology(ClusteredWebFailoverAbstractCase.java:256)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulUndeployFailover(ClusteredWebFailoverAbstractCase.java:103)
------- Stdout: -------
13:53:43,500 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:43,501 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:43,501 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:43,520 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\fb\c4f093d04a14c4da2d63d5d65f68922cd95ac7\content
13:53:43,523 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
13:53:43,550 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:53:43,550 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:43,551 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:53:43,555 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment granular-distributable.war
13:53:43,560 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

	java:global/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/granular-distributable/TopologyChangeListenerBean
	java:app/granular-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

13:53:43,590 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
13:53:43,592 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,592 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 81) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,599 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
13:53:43,602 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0002: Started dist cache from ejb container
13:53:43,604 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,604 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,605 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,606 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:43,618 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started dist cache from web container
13:53:43,621 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started granular-distributable.war cache from web container
13:53:43,848 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0021: Registered web context: /granular-distributable
13:53:43,862 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
13:53:43,871 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
13:53:43,882 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\fb\c4f093d04a14c4da2d63d5d65f68922cd95ac7\content
13:53:43,885 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
13:53:43,910 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:53:43,910 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:43,910 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:53:43,914 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment granular-distributable.war
13:53:43,919 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

	java:global/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.establishTopology(ClusteredWebFailoverAbstractCase.java:256)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)
------- Stdout: -------
13:53:59,173 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
13:53:59,174 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
13:53:59,174 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
13:53:59,187 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\63\8dea8bc5ef9d9ea18e2f75079ec4bbf30a3b0c\content
13:53:59,188 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
13:53:59,211 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:53:59,212 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:59,212 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:53:59,216 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment granular-distributable.war
13:53:59,221 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

	java:global/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/granular-distributable/TopologyChangeListenerBean
	java:app/granular-distributable/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

13:53:59,244 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,244 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 82) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,245 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
13:53:59,250 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
13:53:59,255 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 22) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,255 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 22) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,260 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,260 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 84) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
13:53:59,270 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 84) WFLYCLINF0002: Started granular-distributable.war cache from web container
13:53:59,270 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started dist cache from ejb container
13:53:59,269 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 22) WFLYCLINF0002: Started dist cache from web container
13:53:59,373 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0021: Registered web context: /granular-distributable
13:53:59,383 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
13:53:59,389 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
13:53:59,401 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-1\standalone\data\content\63\8dea8bc5ef9d9ea18e2f75079ec4bbf30a3b0c\content
13:53:59,402 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
13:53:59,425 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.clustering.common:main") which may be changed or removed in future versions without notice.
13:53:59,425 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
13:53:59,425 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.granular-distributable.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
13:53:59,429 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment granular-distributable.war
13:53:59,434 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "granular-distributable.war"' are as follows:

	java:global/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/granular-distributable/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

Retest this please.

retest this please

Linux Build 8674 outcome was FAILURE using a merge of 0eb316f437b472f6b2cab2ad6f4666ab20507ce5
Summary: Tests failed: 1 (1 new), passed: 3283, ignored: 362 Build time: 01:00:35
Failed tests
org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs: java.lang.AssertionError: Reply message was null on reply queue: ActiveMQQueue[ejb2x/replyQueueB]
	at org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs(MDB20TopicTestCase.java:119)
------- Stdout: -------
 [0m22:01:37,046 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment mdb.jar (runtime-name: mdb.jar) in 35ms
 [0m [0m22:01:37,051 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/basic/target/jbossas/standalone/data/content/c7/e771e4ab072120319310a64a894c73a334a6e0/content
 [0m [0m22:01:37,051 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "mdb.jar" (runtime-name: "mdb.jar")
 [0m22:01:37,062 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "ejb2x/queue")
    ]
}
22:01:37,072 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "remove",
    "address" => [
        ("subsystem" => "messaging-activemq"),
        ("server" => "default"),
        ("jms-queue" => "ejb2x/replyQueue")
    ]
}
22:01:37,077 INFO  [org.jboss.as.test.integration.ejb.mdb.ejb2x.AbstractMDB2xTestCase] (main) MDB20TopicTestCase.jar:
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/integration/
/org/jboss/as/test/integration/ejb/
/org/jboss/as/test/integration/ejb/mdb/
/org/jboss/as/test/integration/ejb/mdb/ejb2x/
/org/jboss/as/test/integration/ejb/mdb/ejb2x/MDB20TopicTestCase$JmsQueueSetup.class
/org/jboss/as/test/integration/ejb/mdb/ejb2x/EJB2xMDB.class
/org/jboss/as/test/integration/ejb/mdb/ejb2x/AbstractMDB2xTestCase.class
/org/jboss/as/test/integration/common/
/org/jboss/as/test/integration/common/jms/
/org/jboss/as/test/integration/common/jms/JMSOperations.class
/org/jboss/as/test/integration/common/jms/JMSOperationsProvider.class
/org/jboss/as/test/integration/common/jms/ActiveMQProviderJMSOperations.class
/org/jboss/as/test/integration/common/jms/JMSOperationsException.class
/org/jboss/as/test/shared/
/org/jboss/as/test/shared/TimeoutUtil.class
/META-INF/
/META-INF/MANIFEST.MF
/META-INF/ejb-jar.xml
/META-INF/jboss-ejb3.xml
 [0m22:01:37,086 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 16) AMQ221003: trying to deploy queue jms.topic.ejb2x/topic
 [0m22:01:37,096 INFO  [org.jboss.as.test.integration.common.jms.JMSOperationsProvider] (main) Operation successful for update = {
    "operation" => "add",
    "address" => [
        ("subsystem" => "messaging-activemq"),

Looks good!


No connection to mqtt broker after setup

Description of the issue
I did following steps:

Install Mosquitto broker Current version: 6.4.0 (Änderungsprotokoll)
-> Start it.
Logs:

    s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
parse error: Expected string key before ':' at line 1, column 4
[19:19:08] ERROR: Unknown HTTP error occured
jq: error (at <stdin>:1): null (null) has no keys
[19:19:08] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[19:19:08] INFO: Starting NGINX for authentication handling...
[19:19:08] INFO: Starting mosquitto MQTT broker...
2024-04-16 19:19:08: Warning: Mosquitto should not be run as root/administrator.
2024-04-16 19:19:08: mosquitto version 2.0.18 starting
2024-04-16 19:19:08: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-04-16 19:19:08: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-04-16 19:19:08:  ├── Username/password checking enabled.
2024-04-16 19:19:08:  ├── TLS-PSK checking enabled.
2024-04-16 19:19:08:  └── Extended authentication not enabled.
2024-04-16 19:19:08: Opening ipv4 listen socket on port 1883.
2024-04-16 19:19:08: Opening ipv6 listen socket on port 1883.
2024-04-16 19:19:08: Opening websockets listen socket on port 1884.
2024-04-16 19:19:08: mosquitto version 2.0.18 running
s6-rc: info: service legacy-services successfully started
2024-04-16 19:19:08: New connection from <IP_ADDRESS>:46938 on port 1883.
2024-04-16 19:19:08: Client <unknown> disconnected due to protocol error.
parse error: Expected string key before ':' at line 1, column 4
[19:19:09] ERROR: Unknown HTTP error occured
[19:19:09] INFO: Successfully send discovery information to Home Assistant.
[19:19:09] INFO: Successfully send service information to the Supervisor.

then I installed zigbee2mqtt.

I set mqtt: server: mqtt://localhost:1883 and serial: port: /dev/ttyUSB0 then I started
Logs:

[19:21:23] INFO: Preparing to start...
[19:21:23] INFO: Socat not enabled
[19:21:24] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2024-04-16 19:21:26: Logging to console and directory: '/config/zigbee2mqtt/log/2024-04-16.19-21-26' filename: log.txt
Zigbee2MQTT:info  2024-04-16 19:21:26: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
Zigbee2MQTT:info  2024-04-16 19:21:26: Starting zigbee-herdsman (0.40.3)
Zigbee2MQTT:info  2024-04-16 19:21:26: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2024-04-16 19:21:26: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2024-04-16 19:21:26: Currently 0 devices are joined:
Zigbee2MQTT:info  2024-04-16 19:21:26: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2024-04-16 19:21:26: Connecting to MQTT server at mqtt://localhost:1883
Zigbee2MQTT:error 2024-04-16 19:21:26: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:26: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2024-04-16 19:21:26: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2024-04-16 19:21:27: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:28: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:29: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:30: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:31: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:32: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:33: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:error 2024-04-16 19:21:34: MQTT error: connect ECONNREFUSED <IP_ADDRESS>:1883
Zigbee2MQTT:info  2024-04-16 19:21:35: Stopped zigbee-herdsman

In the meanwhile Mosquitto shows:
2024-04-16 19:20:51: New connection from <IP_ADDRESS>:46786 on port 1883.
2024-04-16 19:20:51: Client <unknown> closed its connection.

Addon version
1.36.1-1
Platform
Home Assistant
Core
2024.4.3
Supervisor
2024.04.0
Operating System
12.2
Frontend
20240404.2
Logs of the issue (if applicable)
see above

After changing server to server: mqtt://core-mosquitto my logs shows:
19:32:42] INFO: Preparing to start...
[19:32:42] INFO: Socat not enabled
[19:32:43] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2024-04-16 19:32:44: Logging to console and directory: '/config/zigbee2mqtt/log/2024-04-16.19-32-44' filename: log.txt
Zigbee2MQTT:info  2024-04-16 19:32:44: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
Zigbee2MQTT:info  2024-04-16 19:32:44: Starting zigbee-herdsman (0.40.3)
Zigbee2MQTT:info  2024-04-16 19:32:45: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2024-04-16 19:32:45: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2024-04-16 19:32:45: Currently 0 devices are joined:
Zigbee2MQTT:info  2024-04-16 19:32:45: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2024-04-16 19:32:45: Connecting to MQTT server at mqtt://core-mosquitto
Zigbee2MQTT:error 2024-04-16 19:32:45: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:45: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2024-04-16 19:32:45: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2024-04-16 19:32:46: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:47: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:48: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:49: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:50: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:51: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:52: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2024-04-16 19:32:53: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:info  2024-04-16 19:32:53: Stopped zigbee-herdsman

After I did everything EXACTLY like in this video, it worked: https://www.youtube.com/watch?v=hGv8Jm574LE&t
I've no idea where the problem was. Maybe you need to add the mqtt json property in the textfield again (it looked wrong, but it worked).
I'm not so brave to kill my configuration to find the reason for my issue ...