overflow-bugfix

Short description of what this resolves:
Changes proposed in this pull request:

Ionic Version: 1.2.4
Fixes: #
if use js-scroll,  native-scrollbar and js-scrollbar both exist。

Thanks for opening this pull request with us! We really appreciate it! Would you mind posting a little more information about the changes you made and what they do? Also is there a bug that was related to this pull request?

@jgw96
My english not good, so there no information about this merge request.I'm very sorry.
I will try my best to explain what i do in this post.
When i use js-scrollbar,  the scroll container still contain class .scroll-view and scroll-y|scroll-x|scroll-xy, this class make the overflow visible。In PC, use mousewheel, you can see this problem.
try http://ionicframework.com/docs/api/directive/ionScroll/
I know ionic is not for PC, but i think this is a problem, so i try to fix it. just remove css selector .scroll-view.scroll-y|.scroll-view.scroll-x|.scroll-view.scroll-xy.
Ionic save me a lot of time, thank you!

No problem, you explained perfectly! Im glad ionic is working good for you!


@Valid on object parameter implementing Principal without @Auth

I'm using Dropwizard 0.9.0-rc3 and I'm running into some trouble with the new auth system.
I have a User model that implements Principal and a POST resource method for signing up new users. The signup method has a validated User parameter but it's not authenticated. When I try access that resource, I get an IllegalStateException with the message: Cannot inject a custom principal into unauthenticated request. Is there an easy way to handle this scenario?
EDIT: I should note that it works just fine if I don't use @Valid.
My signup method looks like this:
@POST
@Path("signup")
@Timed
@UnitOfWork
public Response signup(@Valid final User user, @Context final HttpServletRequest request) throws JOSEException {
	dao.setFilteredByTenantId(false);
	user.setInterceptorBypassed(true);
	user.setRole("Admin");
	final Optional<User> newUser = dao.create(user);
	dao.resetFilters();

	if (newUser.isPresent()) {
		final Token token = AuthUtils.createToken(request.getRemoteHost(), newUser.get().getId());
		return Response.status(Status.CREATED).entity(token).build();
	} else {
		return JSONErrorResponse.build(Status.CONFLICT, "Failed to create new user.");
	}
}

For some reason Jersey is trying to use AuthValueFactoryProvider for injecting of the User instance into the method even when no authentication is used. Looks like a bug.  Do you use @Auth annotation on another method or on class level for this resource class?

No @Auth annotations in that class.

I've located the bug and will provide fix for this.

Closed by #1241


feat(mm): remove MALLOC_MMAP_THRESHOLD_ env var

Summary

Remove MALLOC_MMAP_THRESHOLD_ env var. Per testing in #6007 this can cause performance issues, and the benefit of it is marginal for most users.
Update documentation for this change.
Fix incorrect troubleshooting documentation links

Related Issues / Discussions
Supersedes #6047
Closes #6007
QA Instructions
Use @RyanJDick 's troubleshooting methodology to test the impact of the change.
Merge Plan
N/A
Checklist

[x] The PR has a short but descriptive title, suitable for a changelog
[ ] Tests added / updated (if applicable) N/A
[x] Documentation added / updated (if applicable)

Was this not protecting against a memory creep issue?


Use of FactoryDeps when tx reverts with "The code hash is not known"

🐛 Bug Report for hardaht-zksync plugins
💥 Plugin name
hardhat-zksync-upgradable
📝 Description
When trying to deploy an upgradable contract, the tx reverts with a "The code hash is not known" error.
🔄 Reproduction Steps

Step 1: get the implementation contract to deploy is [here](here https://github.com/unlock-protocol/unlock/blob/48526611b37108db49ddaa27b386a1e605320d5c/packages/contracts/src/contracts/Unlock/UnlockV13.sol)
Step 2: use the hardhat-zksync-upgradable lib to deploy a proxied version with the following params

  deployArgs: [ '<address of the deployer>' ],
  deployOptions: { initializer: 'initialize(address)' }

the actual function can be seen here
https://github.com/unlock-protocol/unlock/blob/f2941fc2cd21a85ddddc6c3a6579a146484a2e5c/packages/hardhat-helpers/src/zkSync.js#L30-L55
You can also clone the zksync-support of the Unlock monorepo, then

git clone https://github.com/unlock-protocol/unlock.git && git checkout zksync-support
yarn & yarn build at root
cd governance
yarn hardhat deploy --unlock-version 13  --public-lock-version 14 --network zksyncSepolia

🤔 Expected Behavior
Deploy the implementation, the proxyAdmin and a proxy contract correctly set
😯 Current Behavior
The proxyAdmin and implementation get deployed. The proxy deployment step fails
📎 Log Output
yarn hardhat deploy --unlock-version 13  --public-lock-version 14 --network zksyncSepolia
Starting deployments on zkSync Era - Sepolia...
UNLOCK DEPLOYMENT > Deploying contracts on zkSync Era - Sepolia with the account: 0x246A13358Fb27523642D86367a51C2aEB137Ac6C
UNLOCK DEPLOYMENT > isLocalNet : false
Setting up version 13 from package
Implementation contract was deployed to 0xdab03e5E7f51065F4c41945a0718Bed21Ef9A9EF
Admin was deployed to 0xb52E38541e709622D86142DC2D50e2eE94017a06
An unexpected error occurred:

Error: execution reverted: "The code hash is not known" (action="estimateGas", data="0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001a54686520636f64652068617368206973206e6f74206b6e6f776e000000000000", reason="The code hash is not known", transaction={ "data": "0x9c4d535b00000000000000000000000000000000000000000000000000000000000000000100015f69aa55883cc3a9d732e813ef169a53ea385c3510e16035e8c10c3cac000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000dab03e5e7f51065f4c41945a0718bed21ef9a9ef000000000000000000000000b52e38541e709622d86142dc2d50e2ee94017a0600000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000024c4d66de8000000000000000000000000246a13358fb27523642d86367a51c2aeb137ac6c00000000000000000000000000000000000000000000000000000000", "from": "0x246A13358Fb27523642D86367a51C2aEB137Ac6C", "to": "0x0000000000000000000000000000000000008006" }, invocation=null, revert={ "args": [ "The code hash is not known" ], "name": "Error", "signature": "Error(string)" }, code=CALL_EXCEPTION, version=6.10.0)
    at makeError (/Users/clement/Dev/unlock/unlock/packages/hardhat-helpers/node_modules/ethers/src.ts/utils/errors.ts:694:21)
    at getBuiltinCallException (/Users/clement/Dev/unlock/unlock/packages/hardhat-helpers/node_modules/ethers/src.ts/abi/abi-coder.ts:118:21)
    at Function.getBuiltinCallException (/Users/clement/Dev/unlock/unlock/packages/hardhat-helpers/node_modules/ethers/src.ts/abi/abi-coder.ts:235:16)
    at Provider.getRpcError (/Users/clement/Dev/unlock/unlock/packages/hardhat-helpers/node_modules/ethers/src.ts/providers/provider-jsonrpc.ts:979:32)
    at /Users/clement/Dev/unlock/unlock/packages/hardhat-helpers/node_modules/ethers/src.ts/providers/provider-jsonrpc.ts:563:45
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'CALL_EXCEPTION',
  action: 'estimateGas',
  data: '0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001a54686520636f64652068617368206973206e6f74206b6e6f776e000000000000',
  reason: 'The code hash is not known',
  transaction: {
    to: '0x0000000000000000000000000000000000008006',
    data: '0x9c4d535b00000000000000000000000000000000000000000000000000000000000000000100015f69aa55883cc3a9d732e813ef169a53ea385c3510e16035e8c10c3cac000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000dab03e5e7f51065f4c41945a0718bed21ef9a9ef000000000000000000000000b52e38541e709622d86142dc2d50e2ee94017a0600000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000024c4d66de8000000000000000000000000246a13358fb27523642d86367a51c2aeb137ac6c00000000000000000000000000000000000000000000000000000000',
    from: '0x246A13358Fb27523642D86367a51C2aEB137Ac6C'
  },
  invocation: null,
  revert: {
    signature: 'Error(string)',
    name: 'Error',
    args: [ 'The code hash is not known' ]
  },
  shortMessage: 'execution reverted: "The code hash is not known"',
  info: {
    error: {
      code: 3,
      message: 'execution reverted: The code hash is not known',
      data: '0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001a54686520636f64652068617368206973206e6f74206b6e6f776e000000000000'
    },
    payload: {
      method: 'eth_estimateGas',
      params: [Array],
      id: 56,
      jsonrpc: '2.0'
    }
  }
}

Reading the docs and similar issue #304, it seems the reverts happen because of a missing / wrong settings of the factory_deps. In the present case, logging the built artifact gives
factoryDeps: {
      '0x010000edb51a9d1ee481114084d43cbe383212a0d19794ad33e80c87ce4b21a7': 'contracts/past-versions/UnlockV13.sol:ProxyAdmin',
      '0x0100015f00035b6caba21865ee421a517a22cba3044e486bdf2c0724d01375f7': 'contracts/past-versions/UnlockV13.sol:TransparentUpgradeableProxy'
    }

Not sure what I am doing wrong here ?

Hello @clemsos :wave: Usually, Hardhat plugins related to proxies and upgradable contracts are responsible for deploying proxies and admins for you, meaning that you don't need to deploy them from your code like you are doing here (check the log, you can see this: Admin was deployed to 0xb52E38541e709622D86142DC2D50e2eE94017a06).
But nonetheless, we should add support for deploying contracts from the implementation (not only ProxyAdmin in your case). Thus, we released a new version of the plugin, so you can try with it.
P.S. If you got an error like this TypeError: Cannot destructure property 'hash' of '(intermediate value)' as it is null. in line, you can try with another extension on the contract like this:
const { hash } = contract.deployTransaction;

@kiriyaga-txfusion thank you very much. I just tested with the new version and it worked just fine :)
Note that the Admin was deployed to 0xb52E38541e709622D86142DC2D50e2eE94017a06 is added by the deployProxy of zksync upgradable plugin itself.
Also thank you for the hash fix. It all works ~


Support channel options on BlazeServerBuilder

Reuses the derived methods from BlazeClientBuilder by extracting into blaze-core.
Fixes #1659.

OOPs, I did it again.  Briefly holding for same reason as #2240.


Add support for missing Payment Networks to Apple Pay

Based on https://developer.apple.com/documentation/passkit/pkpaymentnetwork

Hey @dmengelt, please take a look at this when you have time


Documentation Translation (we first need committed translators)

Hi 👋
we're already a large community with different languages. 🚀  Hopefully we should have a several translated versions of our README or other dosc. 💥
It's my personal suggestions. and obviously I'd love to start contributing 🖐
Thanks 🙏

I'd love this but the docs regularly change (so it's a moving target)... currently I'd wager our English README is WAY, WAY newer than our Russian one. I try and keep the URLs and version numbers updated, but not much else - since I can't read any of it.  It also seems we'd optimally need at least TWO people for each foreign language... one to translate then another to review the work for issues (who can also read the language)...  I'd rather have one accurate document in English than 10 old translations that aren't being maintained.  So my biggest concern in the long-term maintenance of the translations...
I wonder if some type of auto-translate might be a better solution?
@allejo @egor-rogov Any thoughts?

I think it'd be great if we could start translating our documentation into other languages. However, I agree with Josh where we would need several dedicated users to help us translate this; at least two per language.  But I hope I'm wrong and if we start asking users if they'd be interested in helping with translations, then we'd get plenty of volunteers.
Realistically and short-term, we could encourage users to try using Google Translate on our docs and then giving us feedback on things we could try rewriting so that Google Translate can handle it better?

try using Google Translate on our docs and then giving us feedback on things we could try rewriting so that Google Translate can handle it better?

I'd wonder to see what such changes might be though. I'm not sure we should reduce the English readability of the docs just to improve the readability of a translation.
Especially since I presume and hope Google translate isn't a static target. IE I assume it gets better over time so changes docs to deal with point in time quirks in the translation seems problematic.

You're completely right @allejo  🔥
Steps we can do:

we can handle this situation using Google Translator at first step.
Make a list of contributors who are highly interested to translate our docs into their native language.
we'll only start translating using google translate our docs according to our contributors.
Once we get our auto translated docs, our contributors will now help making changes on our genarated files . Still there's some issues with google translator. 😭

Oh I agree, we should not reduce English readability. I'm just thinking that if someone finds something that is translated very poorly and they're able to rewrite it to be translated better and still make sense in English, then we could be looking for that type of feedback in the meanwhile.

The problem with that is that anytime anyone is updating the readme they're not thinking about what changes have been made in the past to improve the translation they're only reading the current English and then perhaps finding a better way to phrase it. ￼
So today's tweak to improve the translation is just destroyed by tomorrow's edit. ￼￼
￼

Honestly I'm not even sure google translate is a brilliant idea unless we actually have some native speakers of whichever languages were considering actually read the Google translate results and see if it's usable.
Plus isn't google translate something that you can use easily inside the browser?  Ie, someone should be able to run it on our read me easily without us actually doing anything. Or am I thinking of something else?￼￼

Oh, err, allow me to clarify a bit; I wasn't super clear :sweat_smile: I didn't mean to use Google Translate to translate the README or RTD and then dump that off to a new website. I meant, more so just encourage users to use Google Translate in their browsers (like Chrome does natively or some browser extension) for the time being and seeing how well that does.
i.e. I think we should gather user feedback on "can we tell users to use Google Translate because it's good enough?" or "do we need to gather a team of translators and make a plan for maintenance of multi-language docs?"

So, what's the final decision then?  🤔

I think someone plays with Google Translate (is there some way we can link to versions of the docs auto-translated?) until we have multiple people who volunteer to be ongoing translators...

@joshgoebel I can translate to Polish if you want

@joshgoebel I can translate to Polish if you want

Awesome ❤
Stay connected mate. 😘😘

@joshgoebel I can translate to Polish if you want

Awesome ❤
Stay connected mate. 😘😘

I already started translating README.md from master will push my PR this month

I really worry about not having any automated way to keep all these translations up-to-date - that they are going to age as poorly as our Russian copy has... and whether having 10 old out-of-date READMEs in native languages is better than having a single up-to-date canonical English version...

I really worry about not having any automated way to keep all these translations up-to-date - that they are going to age as poorly as our Russian copy has... and whether having 10 old out-of-date READMEs in native languages is better than having a single up-to-date canonical English version...

@joshgoebel You can ping me every time the docs changes. I know a bunch of polish people who can help :-)

@joshgoebel @shaonkabir8  I opened PR. Will find some polish people to double-check it. In the meantime could somebody put label hacktoberfest-accepted on my PR ?

So I've been thinking about this a bit more. Originally my suggestion for using Google Translate was to use Google's widget that you could embed in your website and it'll translate your page; i.e. I intended this to be used for RTD since that was the more... text-heavy documentation compared to the README. But Google killed it in favor of native browser support for translation.
The README itself has a lot of text, but the essential information in the README is the code snippets, and they're already split up into sections with names or titles that I would think non-English speakers can recognize or Google fairly easily; e.g., CDN, ES6, Node.js. For this reason, I'd suggest the README itself remain only in English.
The content on RTD is a lot more text-heavy and harder for non-English speakers to understand or translate. IF we were to start translating these docs, I think we should create teams in this organization, e.g. @highlightjs/translators-polish. This way, we'd be able to ping them as a group and anyone on that team would be able to help us out.
All of this being said, translating RTD is not going to be an easy feat. We would need to gather a team of dedicated translators for each language and I don't know about Josh's availability, but mine is limited. There would need to be a volunteer that could gather available translators for different languages.

IF we were to start translating these docs, I think we should create teams in this organization, e.g. @highlightjs/translators-polish. This way, we'd be able to ping them as a group and anyone on that team would be able to help us out.

Wait, you can ping groups? That's kind of awesome.

...the essential information in the README is the code snippets, and they're already split up into sections with names or titles that I would think non-English speakers can recognize ... I'd suggest the README itself remain only in English.

We would need to gather a team of dedicated translators for each language...

Good points...  I'm thinking perhaps we don't draw a hard line like this (README vs RTD, etc), but FIRST it's clear we need people... so to accept translated docs I'd say we need a team of at least 3 translators per language...

1 to translate
1 to review
1 extra person for backup

This whole endeavor doesn't work at all if we get 2 people but one of them turns out to be busy,  unavailable, gets hit by a bus, etc... IE, it is not helpful if it's done by a single motived person who then moves on leaving documentation behind that will never be updated again - like our very poorly aged Russian README.

Hey I am new here, looking to contribute through code as well as documentation. Can translate the MD files to Hindi(Indian) language until I go through the code.

Which "documentation" are you referring to?   Translating the whole docs site would be quite an achievement... and we'd need to figure out how to host multiple translations... most people in the past have been interested in translating the readme, etc...  but as always we really need to get 2 or 3 people interested before a translation even begins to make sense because we don't want to have out-of-date translations if a single translator does the work then gets busy with other things, etc...
@WishAllVA Are any of the major translation tools (Google, etc) any good for English -> Hindi these days?
If you're just interested in pitching in in general you could look at the "help wanted" and "good first issue" tags...

as always we really need to get 2 or 3 people interested before a translation even begins to make sense

I can get one more person with me for the translation.

we don't want to have out-of-date translations if a single translator does the work then gets busy with other things

Agreed. So an automation tool is needed to translate, but I don't think there is any tool which does as good a job as manual.

Are any of the major translation tools (Google, etc) any good for English -> Hindi these days?

There are some that do the translation enough so that the end user will understand the meaning, but in no way they'll be perfect in the Hindi Grammar.

If you're just interested in pitching in in general you could look at the "help wanted" and "good first issue" tags

sure, have not worked much on Regex, but hopefully will learn along the way.


Fixes #79: Bearer token support

@simon3z please review
@jimmidyson , please add details and usage example to the readme file as part of the PR - how can a bearer token be created and passed to the client.

@abonas Rebased. Will update docs now.

@abonas @simon3z Updated README

@abonas @simon3z Updated README. I hope you don't mind but I also updated it to do nicer highlighting & add in links via headers to examples to make it easier to share.

@jimmidyson the readme rework is a nice touch - thanks for that, but in the future please do such things as a separate PR.
It's retouching the entire file, is unrelated to bearer token support and should not require to be reviewed together.

@abonas Let me do it in separate PR now - got carried away ;)

@abonas As requested, rolled back README updates - will submit separate PR.

@abonas And finally updated the README here :)

@simon3z please review
@oschreib -fyi

:+1: but can you add the tests? Thanks!

@simon3z Thanks for the review. Have added some tests.

@simon3z Added headers to test - that's much better thanks!

@abonas any chance of a release with these changes? Really need it for openshift 3/kubernetes stuff

@abonas any chance of a release with these changes? Really need it for openshift 3/kubernetes stuff

sure. 0.1.15 is released

Thanks @abonas!
On Thu, 14 May 2015 at 09:26 abonas<EMAIL_ADDRESS>wrote:

@abonas https://github.com/abonas any chance of a release with these
changes? Really need it for openshift 3/kubernetes stuff
sure. 0.1.15 is released
—
Reply to this email directly or view it on GitHub
https://github.com/abonas/kubeclient/pull/80#issuecomment-101969397.


Adds protection against user-given pollingInterval values

Currently a client can provide any value for its pollingInterval, and when it happens to be a number, it can be arbitrary. This exposes both the DirectLineJS client library and the DirectLine API. One could specify a pollingInterval of 1ms and absolutely hammer the DirectLine API. We should prevent that.

Please note that there are some comments from related PR #127 need to be addressed.

We need auto generating CHANGELOG's, this is silly.

@compulim I'll go ahead and make the stylistic nit changes from the #127 but I'd prefer like to run the entire file with prettier while will change pretty much everything.

Feel free to go prettier after this PR. Maybe a different PR will make it easier to consume.
Commit message cannot easily replace changelog entry because:

We are heavy on Markdown in CHANGELOG.md, we want people love to read our changelog, and understand our design decisions and history
Sometimes we have multiple changelog entries for a single PR, or vice versa
Commit message cannot be easily classified as Added, Changed, Fixed, Removed, and Deprecated

I am happy to add changelog update for you. And I also help external contributors to write the changelog entry if they missed.

I think we should hold off on this PR until we can define a better polling strategy moving forward. A static polling strategy for http is at odds with the documentation on polling. I think we should correctly implement polling based on the recommendations in the doc (or model them as closely as we can) since it seems like the correct way to move forward.

The documentation on polling suggests that this client is totally out of spec! How long have people been using this and referencing that documentation?

For as long as I can remember.


WFLY-5929: Upgrade HAL to 2.8.17.Final

https://issues.jboss.org/browse/WFLY-5929

Windows Build 4062 outcome was FAILURE using a merge of 1a34a94a7852474d202d3fc0f9a97714902ba41e
Summary: Tests failed: 8 (8 new), passed: 3302, ignored: 191 Build time: 00:57:27
Failed tests
org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase(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: -------
03:50:02,024 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:02,025 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:02,025 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:02,046 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\2f\47b32ef706c18b94e789994214174f8ca678a1\content
03:50:02,050 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
03:50:02,101 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) 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.
03:50:02,101 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) 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.
03:50:02,102 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) 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.
03:50:02,158 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment coarse-distributable.war
03:50:02,212 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.2.2.Final
03:50:02,281 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) 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

03:50:02,418 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,419 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,422 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,423 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,428 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Starting Services for CDI deployment: coarse-distributable.war
03:50:02,471 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.3.2 (Final)
03:50:02,515 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,516 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,517 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,517 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:02,536 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment coarse-distributable.war
03:50:02,564 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.
03:50:02,564 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.
03:50:02,689 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started client-mappings cache from ejb container
03:50:02,690 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0002: Started routing cache from web container
03:50:02,722 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) WFLYCLINF0002: Started coarse-distributable.war cache from web container
03:50:02,725 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started dist cache from ejb container
03:50:03,441 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0021: Registered web context: /coarse-distributable
03:50:03,464 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "coarse-distributable.war" (runtime-name : "coarse-distributable.war")
03:50:03,464 INFO  [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
WFLYCTL0185:    Newly corrected services:
      service jboss.module.service."deployment.distributable.war".main (no longer required)
      service jboss.module.spec.service."deployment.arquillian-service".main (no longer required)

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:112)
	at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)
------- Stdout: -------
03:50:20,535 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:20,535 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:20,535 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:20,548 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\33\e23436d8b061d85502f78a01bb01e9d4ddc512\content
03:50:20,550 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
03:50:20,582 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) 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.
03:50:20,582 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) 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.
03:50:20,582 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) 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.
03:50:20,589 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment coarse-distributable.war
03:50:20,596 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

03:50:20,629 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0006: Starting Services for CDI deployment: coarse-distributable.war
03:50:20,632 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,633 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,635 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,636 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,636 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment coarse-distributable.war
03:50:20,636 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,637 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,643 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started client-mappings cache from ejb container
03:50:20,644 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,644 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,648 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,650 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:20,655 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started dist cache from ejb container
03:50:20,658 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started routing cache from web container
03:50:20,668 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started coarse-distributable.war cache from web container
03:50:20,870 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 24) WFLYUT0021: Registered web context: /coarse-distributable
03:50:20,884 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "coarse-distributable.war" (runtime-name : "coarse-distributable.war")
03:50:20,892 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
03:50:20,901 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\33\e23436d8b061d85502f78a01bb01e9d4ddc512\content
03:50:20,904 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "coarse-distributable.war" (runtime-name: "coarse-distributable.war")
03:50:20,928 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) 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.
03:50:20,928 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) 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.
03:50:20,928 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) 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.

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: -------
03:50:36,437 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:36,437 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:36,437 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:36,437 INFO  [org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer] (main) Deploy arquillian service: arquillian-service: 981 assets
03:50:37,032 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\17\ff4c267a2a7ca14ec5caab35a81557d1f16f25\content
03:50:37,036 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "arquillian-service" (runtime-name: "arquillian-service")
03:50:37,188 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
03:50:37,189 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
03:50:37,189 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
03:50:37,189 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) 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.
03:50:37,195 WARN  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0013: Deployment deployment "arquillian-service" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
03:50:37,215 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "arquillian-service" (runtime-name : "arquillian-service")
03:50:37,228 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\0f\91f2852384059d6f72348d0530a180517ab5d1\content
03:50:37,232 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "conversation.war" (runtime-name: "conversation.war")
03:50:37,263 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) 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.
03:50:37,263 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) 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.
03:50:37,263 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.conversation.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.
03:50:37,263 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) 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.
03:50:37,270 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment conversation.war
03:50:37,276 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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

03:50:37,302 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 76) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,303 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 76) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,301 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Starting Services for CDI deployment: conversation.war
03:50:37,304 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,304 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,311 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started dist cache from ejb container
03:50:37,314 INFO  [org.jboss.as.arquillian] (MSC service thread 1-5) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."conversation.war",unit=conversation.war,tests=[org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase]]
03:50:37,315 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Starting weld service for deployment conversation.war
03:50:37,320 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,320 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,322 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,322 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,330 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,330 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:37,341 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started client-mappings cache from ejb container

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: -------
03:50:53,055 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:53,055 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:53,055 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:53,070 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\8f\2ed9bd8d9ce1981d06bffcb6e744127a2918a3\content
03:50:53,073 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
03:50:53,139 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,140 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,140 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,141 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,142 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,143 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,147 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0002: Started expiration.war cache from web container
03:50:53,150 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started routing cache from web container
03:50:53,166 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: /expiration
03:50:53,178 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
03:50:53,183 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
03:50:53,193 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\8f\2ed9bd8d9ce1981d06bffcb6e744127a2918a3\content
03:50:53,195 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
03:50:53,239 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.
03:50:53,240 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.
03:50:53,259 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.
03:50:53,260 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.
03:50:53,264 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 83) WFLYCLINF0002: Started routing cache from web container
03:50:53,285 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.
03:50:53,285 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.
03:50:53,316 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77) WFLYCLINF0002: Started expiration.war cache from web container
03:50:53,372 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 16) WFLYUT0021: Registered web context: /expiration
03:50:53,382 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
03:50:53,411 INFO  [stdout] (default task-6) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=QY8h8Pu7JVCVnu99U7-RECmhX3lopZNKSEN2vfPn

03:50:53,439 INFO  [stdout] (default task-7) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=QY8h8Pu7JVCVnu99U7-RECmhX3lopZNKSEN2vfPn

03:50:53,454 INFO  [stdout] (default task-12) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=DWumiZjJxpLjlPmRQybNDl3C5o62g-1lxL6-wKK5

03:50:53,459 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:53,459 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:53,459 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
03:50:53,470 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0022: Unregistered web context: /expiration
03:50:53,476 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 24) ISPN000029: Passivating all entries to disk
03:50:53,506 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 24) ISPN000030: Passivated 3 entries in 29 milliseconds
03:50:53,511 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0003: Stopped expiration.war cache from web container
03:50:53,518 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0003: Stopped routing cache from web container
03:50:53,524 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 55ms
03:50:53,539 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\8f\2ed9bd8d9ce1981d06bffcb6e744127a2918a3\content
03:50:53,539 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
03:50:53,541 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
03:50:53,545 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 16) WFLYUT0022: Unregistered web context: /expiration
03:50:53,549 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 20) ISPN000029: Passivating all entries to disk

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: -------
03:50:53,585 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:53,585 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:53,585 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:53,599 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\4e\a2f91397acb4e95d44e981a0f097e5f0ffcde9\content
03:50:53,601 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
03:50:53,662 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,663 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,663 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,664 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,670 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started routing cache from web container
03:50:53,672 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,674 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,706 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started expiration.war cache from web container
03:50:53,730 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0021: Registered web context: /expiration
03:50:53,745 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
03:50:53,753 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
03:50:53,767 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\4e\a2f91397acb4e95d44e981a0f097e5f0ffcde9\content
03:50:53,771 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
03:50:53,859 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 77) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,860 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 77) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,860 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 20) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,860 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 20) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,865 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) WFLYCLINF0002: Started expiration.war cache from web container
03:50:53,873 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,874 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:53,878 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started routing cache from web container
03:50:53,901 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: /expiration
03:50:53,912 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
03:50:53,933 INFO  [stdout] (default task-8) http://[::1]:8080/expiration/listener?operation=set&name=a;jsessionid=Jsh7OCUJ1oohnnnyHHycmMMkUjcetWmmuct_DGA2

03:50:53,941 INFO  [stdout] (default task-9) http://[::1]:8080/expiration/listener?operation=set&name=a&value=1;jsessionid=Jsh7OCUJ1oohnnnyHHycmMMkUjcetWmmuct_DGA2

03:50:53,950 INFO  [stdout] (default task-13) http://[::1]:8180/expiration/listener?operation=get&name=a;jsessionid=leE1cjbPGVRe5xu4c17ZfG-yLAFJb_jFByexAr2x

03:50:53,955 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:53,955 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:53,955 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
03:50:53,965 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0022: Unregistered web context: /expiration
03:50:53,971 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 80) ISPN000029: Passivating all entries to disk
03:50:53,974 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 80) ISPN000030: Passivated 3 entries in 3 milliseconds
03:50:53,977 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0003: Stopped expiration.war cache from web container
03:50:53,994 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 80) WFLYCLINF0003: Stopped routing cache from web container
03:50:54,001 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 36ms
03:50:54,013 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\clustering\target\wildfly-SYNC-tcp-0\standalone\data\content\4e\a2f91397acb4e95d44e981a0f097e5f0ffcde9\content
03:50:54,013 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
03:50:54,015 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-1
03:50:54,019 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0022: Unregistered web context: /expiration
03:50:54,026 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 80) ISPN000029: Passivating all entries to disk

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: -------
03:50:54,054 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
03:50:54,055 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
03:50:54,057 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:54,057 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:54,057 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:54,064 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\04\0b611c1b62ba789a29a7c4dd7db5ad531a616f\content
03:50:54,067 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
03:50:54,113 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,114 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,115 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,116 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,117 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,117 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

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: -------
03:50:54,422 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:50:54,422 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:50:54,422 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:50:54,435 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\a7\1cc01b77dcce612be77e949fa76b7e712ef2fb\content
03:50:54,438 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
03:50:54,462 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.
03:50:54,462 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.
03:50:54,462 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.
03:50:54,467 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment granular-distributable.war
03:50:54,472 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) 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

03:50:54,495 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
03:50:54,497 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,497 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,506 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
03:50:54,506 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started dist cache from ejb container
03:50:54,507 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,507 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,509 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,509 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 78) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,510 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,511 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 80) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,514 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started routing cache from web container
03:50:54,520 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started client-mappings cache from ejb container
03:50:54,560 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,561 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:50:54,571 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started granular-distributable.war cache from web container
03:50:54,688 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0021: Registered web context: /granular-distributable
03:50:54,699 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
03:50:54,706 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
03:50:54,721 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\a7\1cc01b77dcce612be77e949fa76b7e712ef2fb\content
03:50:54,723 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
03:50:54,747 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.
03:50:54,748 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.
03:50:54,748 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.

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: -------
03:51:10,035 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
03:51:10,036 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
03:51:10,036 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
03:51:10,046 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\d1\aec8271b3d549a831a20bb9e79c6995090d5d6\content
03:51:10,052 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
03:51:10,076 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.
03:51:10,077 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.
03:51:10,077 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.
03:51:10,081 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment granular-distributable.war
03:51:10,085 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) 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

03:51:10,108 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: granular-distributable.war
03:51:10,109 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 79) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,109 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 79) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,113 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,115 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 14) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,116 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Starting weld service for deployment granular-distributable.war
03:51:10,117 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,118 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,120 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,121 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,125 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,125 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 26) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
03:51:10,132 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0002: Started client-mappings cache from ejb container
03:51:10,133 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started granular-distributable.war cache from web container
03:51:10,138 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started routing cache from web container
03:51:10,141 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 79) WFLYCLINF0002: Started dist cache from ejb container
03:51:10,248 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0021: Registered web context: /granular-distributable
03:51:10,260 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "granular-distributable.war" (runtime-name : "granular-distributable.war")
03:51:10,267 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
03:51:10,276 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\d1\aec8271b3d549a831a20bb9e79c6995090d5d6\content
03:51:10,277 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "granular-distributable.war" (runtime-name: "granular-distributable.war")
03:51:10,301 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.
03:51:10,301 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.
03:51:10,302 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.

Retest this please


Fix #30

Did what @jdanyow suggested here: https://github.com/aurelia/ux/pull/31#issuecomment-289225303
I did not fix ALL the lint issues, so many of them, but I fixed the errors that would have broken "npm build"

we can get the lint errors fixed in a separate PR.

After pulling down this repository fresh, I ran npm install and tried to run build and doc
npm run build works as expected
npm run doc failed with the following output
><EMAIL_ADDRESS>predoc E:\Development\Aurelia\_review\ux
> cross-env rimraf doc/api.json && rimraf dist/doc-temp && tsc --project tsconfig.build.json --outFile dist/doc-temp/aurelia-ux.js && node doc/shape-defs && copyfiles tsconfig.json dist/doc-temp

Shaped the dist/doc-temp/aurelia-ux.d.ts file.

><EMAIL_ADDRESS>doc E:\Development\Aurelia\_review\ux
> cross-env typedoc --json doc/api.json --excludeExternals --includeDeclarations --mode modules --target ES6 --name aurelia-ux-docs dist/doc-temp/

Using TypeScript 2.2.1 from E:\Development\Aurelia\_review\ux\node_modules\typescript\lib
Error: File 'E:/lib.dom.d.ts' not found.
Error: File 'E:/lib.es2017.d.ts' not found.

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "doc"
npm ERR! node v7.7.4
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>doc: `cross-env typedoc --json doc/api.json --excludeExternals --includeDeclarations --mode modules --target ES6 --name aurelia-ux-docs dist/doc-temp/`
npm ERR! Exit status 4
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>doc script 'cross-env typedoc --json doc/api.json --excludeExternals --includeDeclarations --mode modules --target ES6 --name aurelia-ux-docs dist/doc-temp/'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the aurelia-ux package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env typedoc --json doc/api.json --excludeExternals --includeDeclarations --mode modules --target ES6 --name aurelia-ux-docs dist/doc-temp/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs aurelia-ux
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls aurelia-ux
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\Development\Aurelia\_review\ux\npm-debug.log

@ZHollingshead unfortunately this is an issue with typedoc on windows. I hit the same issue on my windows machine with their latest release and had to switch over to my unbuntu installation.

@jdanyow Ah, that is very unfortunate indeed.
Other than this everything looks alright. I can fix the lint issues as soon as this is pulled in. The main issue of the build being broken is resolved.

Ok, all merged in :)


Can't add reminders using the Chrome extension

Hi - the extension defaults to 'Event' and does not allow me to add Reminders to my calendar.

Please note that adding Reminders is supported on both Google Calendar web and mobile apps.
Web >

Mobile >

without reminders ( viewing & adding them ), the extension is useless for me.

without reminders the extension is useless.  I do not understand why google does not like reminders.  In calendar and mail(followup)

highly in demand!


Engine crashes when i load a non-moving character in a song in chart editor

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version.
When i tried to do this on the normal Psych engine, it worked pretty well but idk what is happening on JS engine but it crashes whenever i choose a non moving character in chart editor. A moderator here said to update the egine and instantly closed the thing. It didn't work at all.
Command Prompt/Terminal logs (if existing)
https://cdn.discordapp.com/attachments/979114840037683200/1209744447491805235/2024-02-21_07-05-23.png?ex=65e80950&is=65d59450&hm=1343d9a57ce07cd426af7364a2e62f99331e0565b2ac38a520ed742af39b8386&)

Copy and paste it on the url

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
It's pretty easy, use a on moving character like Conbis for example and change characters in chart editor.

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
i added a marathon song with characters and events, that's all
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here.
Yes

im pretty sure this is an icon issue.
does your icon actually exist? if so, does it have 2 frames or 1?

Oh my god wait it actually worked. I used other characters icon and worked! Thanks dude :    )


Update ndb instructions for require path.

Missed in https://github.com/webmixedreality/exokit/pull/459.


walkthrough/k8s201.html error in rendered text

The source has the following:
$ export SERVICE_IP=$(kubectl get service nginx-service -o=template -t={{.spec.clusterIP}})
$ export SERVICE_PORT=$(kubectl get service nginx-service -o=template '-t={{(index .spec.ports 0).port}}')
$ curl http://${SERVICE_IP}:${SERVICE_PORT}

but on the support kubernetes.io site at :
http://kubernetes.io/v1.0/docs/user-guide/walkthrough/k8s201.html
The template has been omitted.
$ export SERVICE_IP=$(kubectl get service nginx-service -o=template -t=)
$ export SERVICE_PORT=$(kubectl get service nginx-service -o=template '-t=')
$ curl http://${SERVICE_IP}:${SERVICE_PORT}

cc @lavalamp

@krousey @thockin Looks like a problem with the markdown renderer

My guess is that by using redcarpet to render and replacing fenced code blocks with {% highlight <lang> %} directives, the Go template directives need to be escaped as to not be gobbled by redcarpet.

looking at it.
On Wed, Jul 22, 2015 at 1:32 PM, krousey<EMAIL_ADDRESS>wrote:

My guess is that by using redcarpet to render and replacing fenced code
blocks with {% highlight  %} directives, the Go template directives
need to be escaped as to not be gobbled by redcarpet.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/11696#issuecomment-123853391
.

Uggh, ok I think adding {% raw %} to all code blocks will do the trick.
Will test a bit.
On Wed, Jul 22, 2015 at 3:00 PM, Tim Hockin<EMAIL_ADDRESS>wrote:

looking at it.
On Wed, Jul 22, 2015 at 1:32 PM, krousey<EMAIL_ADDRESS>wrote:

My guess is that by using redcarpet to render and replacing fenced code
blocks with {% highlight  %} directives, the Go template
directives need to be escaped as to not be gobbled by redcarpet.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/11696#issuecomment-123853391
.

Looks like solution is merged with #11720. Close issue?


Clear button on select is not working anymore

The clear button on select is not working anymore in version 4.3.10.
If I changed to a previous version (ex : 4.3.4), it works.
Code is the same in both version.

show your code on codepen.io

Hope it helps :
https://codepen.io/Merenia/pen/mdPmwyN

Thank you, fixed in 4.4.0


Docs: consullocker/etcd3locker - correct UnlockUpload method docs

The following statement in the docs is not accurate for consullocker and etcd3locker.

If no such lock exists, no error will be returned.

This PR removes that statement for both locker implementations.

You're right, thank you very much!


fix: exclude parquet files from checks

I am drafting a PR to update terraform samples in https://github.com/terraform-google-modules/terraform-docs-samples/pull/474
The lint stage of the CI is failing as we're attempting to check that parquet files end in new lines. You can't append new lines to parquet files wihtout invalidating them.
So we should not check that parquet files end in newlines.
Related PR: (https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/1725)

/gcbrun

moving to attempt 2 github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/1776


Does not honour the .. meta:: directive.

Steps To Reproduce
Create a file with the following at the top:
.. meta::
      :description: The reStructuredText plaintext markup language
      :keywords: plaintext, markup language

Result
No meta tags are generated.
Expected result
Produced HTML should have meta tags like:
<meta content="The reStructuredText plaintext markup language" name="description" />
<meta content="plaintext, markup language" name="keywords" />

Comments
The default theme handles this correctly.

I am not sure when this started working but this now works.


Wait for xenpcid before starting DomU

With the above nit considered:
Reviewed-by: Oleksandr Andrushchenko<EMAIL_ADDRESS>


feat: Implement some parts of the new UI

Review Requested @pepoospina

I've manually built this and puhsed already


fix testcaferc metadata filter

Fixes the broken metadata filters in the testcaferc.json.
Currently you can only use the metadata filter via the command line. The testcaferc passes an object to optionValueToKeyValue which it currently doesn't support. This adds support for objects.

Thank you for creating this PR! However, I've found that it's better to parse meta key-value strings directly in the command line argument parse plus this case needs to be covered by a test. So I will add some commits atop of your contribution. Thank you again  for using TestCafe ❤

PR looks valid now
@miherlosev

It's not finished, the case mentioned in this comment is not fixed, and it doesn't have a test for this case.

Unfortunately I can't push my fixes to this branch anymore, so I open https://github.com/DevExpress/testcafe/pull/3474 to continue working on it. Thank you again for your contribution.


Update hooks is missing for forked repository

I have installed 0.5.11 version. And encountered with bug in update logic on forked repos. The webhooks does not fire after git push to forked repo. This is broke drone CI integration in my case. Webhooks in not forker repo works ok.
Also activity stream (explore) does not show "Updated" label correctly.
My environment:
host Centos 6.6
go1.4.1 linux/amd64
mysql version 5.5.40 with innodb.
update.log is empty

Thanks for your report and patient, it's been backlog here: https://trello.com/c/0Csbq8BX/391-update-hooks-is-missing-for-forked-repository :eyes:

Hi @Dumbris , I've pushed fix on master, you can also test on https://try.gogs.io !

I'm closing it with the release, feel free to reopen it if you want to continue discussion. :smiley: