API Gateway Stage tags support

Added

support for /tags/**/stage/ rest apis

Terraform test

TestAccAWSAPIGatewayStage_basic passed
TestAccAWSAPIGatewayStage_accessLogSettings_kinesis passed
TestAccAWSAPIGatewayStage_accessLogSettings passed

@monty16597 It doesn't look like our CI is kicking off for this PR. Would you mind pushing an empty commit to this branch? Just put a space somewhere, hopefully that that's enough to get our CI back in work

Codecov Report

Merging #4160 (f2a1a01) into master (6d9abe1) will decrease coverage by 0.03%.
The diff coverage is 11.11%.

@@            Coverage Diff             @@
##           master    #4160      +/-   ##
==========================================
- Coverage   95.07%   95.03%   -0.04%
==========================================
  Files         485      485
  Lines       54365    54449      +84
==========================================
+ Hits        51687    51746      +59
- Misses       2678     2703      +25

Flag
Coverage Δ

servertests
54.85% <11.11%> (+0.01%)
:arrow_up:

test_responses
32.82% <11.11%> (-0.03%)
:arrow_down:

unittests
94.94% <11.11%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/apigateway/urls.py
100.00% <ø> (ø)

moto/apigateway/responses.py
93.49% <11.11%> (-3.35%)
:arrow_down:

moto/ec2/responses/security_groups.py
88.02% <0.00%> (-1.03%)
:arrow_down:

moto/ec2/models.py
95.92% <0.00%> (-0.12%)
:arrow_down:

moto/emr/utils.py
100.00% <0.00%> (ø)

moto/ec2/responses/spot_instances.py
96.15% <0.00%> (+0.50%)
:arrow_up:

Continue to review full report at Codecov.

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


dart2js crashes in strong mode.

With CL https://dart-review.googlesource.com/c/45501/, dart2js crashes on map_update_test.dart when run in strong mode. See: https://ci.chromium.org/p/dart/builders/luci.dart.try/dart2js-linux-d8-kernel-minified-try/35

Thanks Lasse, I'll just close this issue since we'll use the status file as the source of truth while we get strong mode in shape.


Adding hover colors for background and text

This PR add hover classes to change both the background color and text color. It works with all base and shade colors.  The documentation has been updated also.

If it would help, I can make a demo of this pull request.

This would be adding lot of page weight for classes that will be used very rarely. I don't think this is would be used enough to warrant adding this many lines.


Add Postal Code Capability

Add postal code storing capability and display them on GUI.

Merged pull request https://github.com/CS2103AUG2017-T16-B3/addressbook-level4/commit/c4d77b79f1f37fdeddfb7c3adda6e02114ac9918


filter noUncheckedIndexedAccess with own property check

Search Terms
ownProperty
hasOwnProperty
noUncheckedIndexedAccess
type check
Suggestion

noUncheckedIndexedAccess is a great feature. However, ts reports that object can be undefined even with hasOwnProperty check.
I suggest that a hasOwnProperty check makes unchecked indexed accesses checked, and return the checked value.
Use Cases
const obj: {[key: string]: string} = {};
// do something with obj
const key = "someKey";
if (Object.prototype.hasOwnProperty.call(obj, key)) {
  console.log(obj[key].length); // TS2532: Object is possibly 'undefined'.
}

Since only string values are allowed in obj, the only case such value is undefined is when the key does not exist on obj. The value of obj[key] can only be string. However, typescript still reports type of obj[key] being string | undefined.
Examples
const obj: {[key: string]: string} = {};
// do something with obj
const key = "someKey";
if (Object.prototype.hasOwnProperty.call(obj, key)) {
  console.log(obj[key].length); // no problem, since obj[key] has correct type string
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Related: #10530

Actually I consider the current behaviour to be a bug.
This playground reports two errors where I believe there should be none, as both cases are checked:
https://tsplay.dev/WG85Kw


Speeding up network play

What kind of work would be required to make network play less laggy? And is this project still actively maintained?

Network play is currently via a websocket proxy that passes all traffic through a single server. The next step up would be to write a networking back-end using WebRTC data channels, which can be direct from clients to servers, or at least distributed geographically like a CDN to minimal lag.
This is a considerable amount of work, and so I'm unlikely to do this soon. This project is on hold while I work on some others.

thank you for the response. great work.


Kuberentees installation issue

I have done the installation kubeadm. Aftrer initializing the cluster node takes forever to join the cluster.

Any help would be highly appreciated

solved

solved


xgboost training continuation convergence problem

Hello :)
I was using xgboost to train in a large dataset (using dmatrix external memory feature) and using the AWS Sagemaker with spot training enabled, so my training job can be interrupted at any moment. So, I needed to save xgboost.train() checkpoints. I was saving it at each round, but the model was giving a much worse score than the full trained one with just a subset of the data. So I decided to make some small tests on the iris dataset and I got to the following results:
1 - Full train:
xgb_full = xgb.train(hyperparameters,
                     dtrain,
                     num_boost_round=100,
                     evals=[(dtrain, 'train')],
                     feval=f1_score_dmatrix,
                     maximize=True,
                     verbose_eval=True)

This one converges to train-error:0.00833	train-f1:0.98667
2 - Checkpoint at each round:
xgb_partial = None
for _ in range(100):
    xgb_partial = xgb.train(hyperparameters,
                            dtrain,
                            num_boost_round=1,
                            evals=[(dtrain, 'train')],
                            feval=f1_score_dmatrix,
                            maximize=True,
                            verbose_eval=True,
                            xgb_model=xgb_partial)

This one converges to train-error:0.04167	train-f1:0.93671
3 - Checkpoint at each 10 rounds:
xgb_partial = None
for _ in range(10):
    xgb_partial = xgb.train(hyperparameters,
                            dtrain,
                            num_boost_round=10,
                            evals=[(dtrain, 'train')],
                            feval=f1_score_dmatrix,
                            maximize=True,
                            verbose_eval=True,
                            xgb_model=xgb_partial)

This one converges to train-error:0.01667	train-f1:0.97368
In that way, is this a known issue for training continuation feature and/or expected behavior?
The full test script code can be found in this gist

Hi, could you share which xgboost version are you using?

We have some strict tests for doing training continuation.  If you are using latest XGBoost (1.1 as of writing), I will try to reproduce it.

Hi, could you share which xgboost version are you using?

xgboost 1.1.0 version.

Just reproduced the issue.  It works fine when without specifying subsample though.

Just reproduced the issue. It works fine when without specifying subsample though.

Just confirmed this as well. It works as expected when removing the subsample hyperparameter. Maybe the subsampling is not the same when loading the model (e.g. different seeds)?

@ronaldpereira Try setting the seed manually and see if you can make subsampling deterministic. I'm afraid that subsamping may vary between multiple invocations of xgb.train(), even with a seed parameter. The reason is that setting the seed multiple times during the training results in a different random number sequence than setting the seed only once.
My suggestion is to remove the subsampling to achieve determinism with preemptible spot workers.


Vulnerability roundup 84: http-client-0.6.4: 2 advisories

search, files

[ ] CVE-2016-6287 CVSSv3=7.5 (nixos-20.03)
[ ] CVE-2020-11021 CVSSv3=7.5 (nixos-19.09, nixos-20.03)

Scanned versions: nixos-19.09: 31dcaa5eb67; nixos-20.03: 82b5f87fcc7. May contain false positives.

20.03 is frozen and EOL.
(as is 19.09) ;-)
Closing.


Adding users with upper case letters make them lower cased

I'm trying to add existing users from my GitHub organization to the terraform state.
module "admins" {
  source  = "mineiros-io/team/github"
  version = "0.3.0"

  name = "Admins"
  privacy = "closed"

  maintainers = [
    "PavelSusloparov"
  ]
}

terraform plan gives me
  # module.admins.github_team_membership.team_membership["pavelsusloparov"] will be created
  + resource "github_team_membership" "team_membership" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "maintainer"
      + team_id  = "79035"
      + username = "pavelsusloparov"
    }

I expect the username to be camelcase, as I specified in the maintainers section.
pavelsusloparov is not my GitHub name, PavelSusloparov is.
Please advise.

Hi @PavelSusloparov.. thanks for taking the time reporting this issue and thanks for giving our modules a try ;)
This should not make a difference as GitHub user names are case-insensitive. The only question is if it will create an idempotent state. but no matter what for the sake of not having a confusing plan, we should fix it.
I will add a test case for this to validate state will settle no matter what the case is.

Added a test to validate my assumption. the case does not matter. So this is just a cosmetic issue in the plan and an apply will work as expected adding the user to the team no matter the case.
I still added a fix but this will still not reflect the actual GitHub user name but will preserve the case in the plan that is used in the configuration. Will be released with a later release.
See also: #34 and test output.

Hey @PavelSusloparov , please let us know if there are any other concerns or if we may close this issue. Thank You!

closed due to merging the fix to default branch.... pls reopen if you feel it was not fixed.. will be included in the next release.


Error using PolymerElements with angular-cli-webpack

Following the steps in the angular-cli-webpack.adoc guide for using the PolymerElements results in an error: Uncaught Unexpected value 'class0' declared by the module 'AppModule'
It seems to stem from putting any of the PolymerElement() in the declarations tag of NgModule as such:
@NgModule({     ...     declarations: [ AppComponent,         PolymerElement('paper-input')     ],     ... })
Any help would be greatly appreciated, thanks!
angular-cli-version: 1.0.0-beta.11-webpack.8
vaadin version: "@vaadin/angular2-polymer": "^1.0.0-beta4",
bower dependencies:
{     "polymer": "^1.6.1",     "app-layout": "^0.10.4",     "iron-collapse": "^1.2.1",     "iron-icons": "^1.1.3",     "paper-card": "PolymerElements/paper-card#^1.1.2",     "paper-checkbox": "PolymerElements/paper-checkbox#^1.4.0",     "paper-dropdown-menu": "^1.4.0",     "paper-fab": "^1.2.0",     "paper-icon-button": "^1.1.2",     "paper-input": "^1.1.19",     "paper-item": "^1.2.1",     "paper-material": "^1.0.6",     "paper-toggle-button": "^1.2.0",     "paper-tooltip": "^1.1.3",     "iron-list": "^1.3.9",     "iron-flex-layout": "^1.3.1",     "paper-styles": "^1.1.4"   }

Try with 1.0.0-beta.11-webpack.9, it works with angular2-rc6.
1.0.0-beta4 works with angular2-rc6
1.0.0-beta.11-webpack.8 works with angular2-rc5

Thanks for the quick response.
I updated angular-cli to 1.0.0-beta.11-webpack.9 which updated angular to rc7, and left the vaadin script at 1.0.0-beta.4.  I'm still seeing the same error.
I don't have my project laid out the default way the cli set's it up, but if I don't attempt to use the polymerelements anywhere, the angular application works correctly, so I don't think that should matter... though I've been wrong before.

I just went through the angular-cli upgrade process again, and now it's working.  I guess I'll chalk this one up to a bad upgrade the first time.

What about just using vanilla webpack? I'm trying to just get a basic setup working without angular-cli, and I'm running into this same error when I add something like PolymerElement("paper-button") to my app module:

Uncaught Error: Unexpected value 'class0' declared by the module 'AppModule'

As others have reported, once I remove the declaration from the app module the app loads just fine.


Animate Top Nav Menu height to "unfurl"

When clicking on the Top Nav in mobile and desktop, add a quick/simple "unfurl" animation like this example: http://kylegoslan.co.uk/bootstrap-4-hamburger-menu-animation/ . Note: not wanting to copy the design, just the animation of the nav height contracting and expanding.

try animating css height from 0 to 100% at the bottom of src/Menu.scss


Support observers

In #476 I proposed to warn in some edge cases. Truth is - I hate when libraries are polluting STDERR/STDOUT without the way to control their verbosity level. So my first idea was - let's provide logging API, but in fact logger is simply a very specific use case of observer:
class MyHttpLogger < HTTP::Observer
  def initialize(logger)
    @logger = logger
  end

  def request_sent(request:)
    @logger.debug("#{request.verb} #{request.uri}")
  end
end

HTTP.observe(MyHttpLogger.new(Rails.logger)).get(url)

One thing that really bothers me in most Russian doll middleware architecture is pointless overhead of Array#each. With single observer object it will be possible to simply call:
observer&.request_sent(:request => request)

Providing HTTP::Observer base class will allow third parties to inject needed functionality on it using plain old Ruby:
HTTP::Observer.extend HotPotatoExtensions

There's been a ton of discussion about this (and even some merged code). You even have an issue open for it already I think: #209
See also #177 and #240, as well as #346
I am definitely a fan of avoiding the "middleware" pattern, especially as it pollutes the stack and makes backtraces that much more annoying to read (not to mention the performance implications).
One thing I'd suggest is avoiding the "null object pattern" for this (i.e. defining a class of observers that does nothing), in lieu of gating the invocations on a branch. Ruby method dispatch is rather slow, and the null object pattern would greatly increase the number of method invocations this library performs.

I feel myself so dumb now. Indeed we already had this conversation before! o_O Well the idea I had is pretty same to Spy in fact. with exception that there's a default implementation of observer and one will be able to just implement only needed handler to avoid if x.respond_to? guards which will impact performance. But in general API should accept an object that simply responds to all needed methods. Pretty much as Spy in fact. Just with ability to pass in any Spy-compliant implementation :D

Duplicate of my own issue indeed. :D


Input issue in modal

Hi,
This is khadeer,
When i am adding input in modal, Ex: if is there content more then window height, then add input content bottom after issue is there. when i am opening modal directly focus on input place if any type of input.
I am using semantic-ui 1.12.2 framework

Looks more like an usage question.
If that's right, please repost your issue on the projecttalk forum and read the contributing guide.
http://www.projecttalk.io/boards/Semantic-Org%2FSemantic-UI

You should use the latest version of SUI and provide a test case.

Hi avalanche1,
In latest version also this problem is there.

Settings to the rescue. This weeks edition autofocus
http://jsfiddle.net/zrk3cfm8/


Route Database (Feature Request)

As you all may know, the routes between cities are not fixed to flights in rw aviation and a route may be used for multiple flights between two cities by multiple airlines/types. In our current system, we need to have a route defined for every flight we insert to our schedule which in theory is too different from how real flight ops work.
So if you are trying to simulate a full schedule of a rw airline, then you will have to insert its flight schedule to your system with multiple flights between city pairs, with changed times and days etc if you seek full schedule realism. Or you may have multiple airlines flying the same city pair maybe with different types of aircrafts and you will insert them to your database too.
This means that you have to use the same route over and over again for multiple flights, in our current logic we need to enter the same route for every flight which is not realistic and time consuming, also hardens the maintanence if something changes (like airac update / airway change , intersection change etc)
To overcome this situation we need a separate route table in our databases, where you can insert at minimum only dep - arr - flight route details and then when inserting (or editing) a flight we should be able to select this route (like we select the expenses, subfleets, expenses etc). If you do not want to restrict a route to only an airline or a subfleet then you should be able to select that route for multiple airlines/flights etc as you wish.
If we have a seperate route database this also provides us to have multiple routing options between city pairs too, for example you may have 2 different routes between EDDL and LGIR one from north via Austria - Hungary another from going south via Switzerland - Italy etc.
When available, our pilots may choose the preffered route according to their wishes (upper air weather situations/distance etc) before generating their flight plan packages via simbrief.

Great idea, would love to be able to create a series of flights such as a world tour or tour of a Country or area.

Moving this to one of my modules 😃  No need to have deep realism in core at the moment. It is already complicated for most of the users, having a route database like real world will make lives harder.
Peacefully closing this request


c11_atomics - change arg type to unsigned int from signed int

Fixes #1030

Out of interest have you looked to see if there are any additional mismatches between A and M?

Hi Jeremy, sorry I do not understand your question.

Sorry it was badly written!
I was checking that there were no more signed/unsigned mismatches but I've had a look and can't see any.

Ok I have not noticed any more issues.


Update sbt-mdoc to 2.2.21

Updates org.scalameta:sbt-mdoc from 2.2.19 to 2.2.21.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

labels: sbt-plugin-update, semver-patch

This one is merging forward.


Include all files in sdist archives

Description
Remove the restriction on files inclduded in sdist archives in order to include documentation sources and tests there.  This is the default hatchling behavior and it is helpful to packagers (such as Linux distributions or Conda) as it permits using sdist archives to do packaging (instead of GitHub archives that are not guaranteed to be reproducible).  Most of the ordinary users will not be affected since starlette is a pure Python package and therefore pip will prefer wheels to install it everywhere.
Checklist:

[ ] I have added the relevant tests for this change.
[ ] I have added an item to the Pending section of docs/changes.rst.

I haven't added it to changelog since it is primarily packager-facing change rather than developer/user-facing. If you'd like me to add it there nevertheless, please let me know.

Doesn't this mean that a tests package is installed into users virtualenvs? I'm not sure this is what we want?

No, it's not. The tool.hatch.build.targets.sdist affects only sdist archives, tool.hatch.build.targets.wheel control what goes into wheels and therefore what is installed.

Thanks!


Update Generic Pages “about-counselling”

Automatically generated by Netlify CMS

👷 Deploy Preview for shimmering-marigold-4f5b4a processing.

Name
Link

🔨 Latest commit
8f31174243064c100a93aa6fc939627b1b4f410b

🔍 Latest deploy log
https://app.netlify.com/sites/shimmering-marigold-4f5b4a/deploys/633d9524c61acb00093e97f2


[FEATURE] Add label to the input in Profile section #8703

Fixes Issue
Closes #8703

Changes proposed
The label should be called Profile Layout.

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Before Change

After Change

Note to reviewers

Issue link https://github.com/EddieHubCommunity/BioDrop/issues/8703

Removing it makes the content visible for normal readers and it doesn't change the visibility for screen readers as the content will still be visible to screen readers too. On Tuesday, August 29, 2023 at 12:45:22 PM GMT+1, Sital Adhikari @.> wrote: @sital002 commented on this pull request. In components/form/Select.js:
@@ -10,7 +10,7 @@ export default function Select({
return ( <> {label && ( - <label htmlFor={name} className={sr-only ${className} hidden md:block}> + <label htmlFor={name} className={${className} hidden md:block}> ⬇ Suggested change- <label htmlFor={name} className={${className} hidden md:block}> + <label htmlFor={name} className={sr-only ${className} hidden md:block}> sr-only is used for accessibility purposes I think this shouldnot be removed. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Ooh I didn't new that my bad.

Great discussion 👍  sr-only is if we don't want it to be displayed but available for screen readers only, but without it, it will now be available to both


fix: add flag parse

:heavy_check_mark: Checklist:

[ ] Have only one commit (if not, squash them into one commit)
[ ] Tests for the changes have been added (for features / bug fixes / refactoring)

Codecov Report

Merging #286 (a9b5f23) into main (de73ba7) will not change coverage.
The diff coverage is 57.19%.

@@           Coverage Diff           @@
##             main     #286   +/-   ##
=======================================
  Coverage   61.25%   61.25%
=======================================
  Files           7        7
  Lines         382      382
=======================================
  Hits          234      234
  Misses        146      146
  Partials        2        2

Impacted Files
Coverage Δ

internal/api/api.go
100.00% <ø> (ø)

internal/api/find.go
28.57% <33.33%> (ø)

internal/api/build.go
44.50% <44.50%> (ø)

internal/parse/parse.go
89.70% <89.70%> (ø)

internal/read/read.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Adds a test case for decoding UTF-8 strings and fixes this bug

Multibyte strings were not being encoded back into UTF-8, so I wrote a test case (and fixed the bug)

I'll need to look into this a bit more but this looks like a great change.

@jqr @Freaky Used an module variable to set encoding. You think this should be documented somewhere?

Well, the point would be to make it easy to override if necessary, a constant would throw a warning if you redefined it.  I was thinking more along the lines of:
module PHP
  class << self
    attr_accessor :encoding
  end
end

PHP.encoding ='UTF-8'

Then users can set it to whatever weirdness they're using in PHP.  Might be mostly theoretical?

Today, I tried to merge #10 and #11 onto commit e23fcfd.
I noticed that these two patches are incompatible with each other.
#11 resolves the issue using a different approach, as keichan34 mentioned.
Thus, I think this #10 can be closed in favor of #11.

Yeah that force encoding seems problematic, closing in favor of #11.


Add minimum working Elixir/Erlang version in Travis CI.

This PR ensures Travis CI also includes the minimum module requirements of Elixir 1.9.x and Erlang/OTP 22.x.
All these commands works without issues.
$ asdf install
$ mix deps.get
$ mix compile
$ mix test

@lirossarvet Indeed make sense. Travis CI is the proper place to change it.

@kianmeng do you mind updating your branch with the latest main?

@kianmeng do you mind updating your branch with the latest main?

@lirossarvet
It's already rebased to the latest main branch from upstream.

Merged via https://github.com/lirossarvet/honeylixir/commit/c7ec6bc798d4f8dfe0d67fef33750e723a090b4f via apparently a weird workflow, sorry. I am...very new at maintaining something. however! your author email is correct this time.

Merged via c7ec6bc via apparently a weird workflow, sorry. I am...very new at maintaining something. however! your author email is correct this time.

@lirossarvet LGTM!


Fixing serve tests for working with latest cordova.

take a look at this @surajpindoria

not sure why the code coverage took such a huge fall


[WFCORE-3454] Ensure the dist archives contain the correct content. R…

…enamed the wildfly-vault-test-feature-pack maven module to wildfly-core-vault-test-feature-pack.
https://issues.jboss.org/browse/WFCORE-3454
One thing to note here is I did rename the wildfly-vault-test-feature-pack maven module to wildfly-core-vault-test-feature-pack. This was due to the fact that the default server.output.dir.prefix property was set to wildfly and for core should likely be wildfly-core. This feature pack seems to only be used in WildFly Core. If we feel this shouldn't change I can remove that change. I didn't see any usage in WildFly.

The rename of wildfly-vault-test-feature-pack is fine. That FP is just there to make picketbox available so we can test vault. WildFly has picketbox the normal way.

That's what it looked like which is why I thought renaming it wasn't a big deal. To be honest this fix really could be a one line fix in the assembly.xml, but I figured we may as well make it match what we do in full as close as we can.

Full integration - Windows Build 4712 outcome was FAILURE using a merge of 1ccd7364838ca6106b5c33f670e7c3fbe055c733
Summary: Tests failed: 2 (2 new), passed: 4198, ignored: 98 Build time: 02:27:44
Failed tests
org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase(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.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:286)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:179)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulSimpleFailover(AbstractWebFailoverTestCase.java:91)
------- Stdout: -------
19:59:28,090 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\77\9a3fcdf860d878de68ae96cf348a9b50d91e80\content
19:59:28,093 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "negotiationAuthenticator.war" (runtime-name: "negotiationAuthenticator.war")
19:59:28,118 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
19:59:28,167 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
19:59:28,174 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment negotiationAuthenticator.war
19:59:28,185 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "negotiationAuthenticator.war"' are as follows:

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

19:59:28,269 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 7) WFLYCLINF0002: Started default-server cache from web container
19:59:28,277 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started negotiationAuthenticator.war cache from web container
19:59:28,334 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1!
19:59:28,336 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1!
19:59:28,338 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1!
19:59:28,339 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1!
19:59:28,340 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1!
19:59:28,344 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1!
19:59:28,345 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
19:59:28,346 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
19:59:28,349 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.RequestedJMSContext is deprecated from CDI 1.1!
19:59:28,349 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.TransactedJMSContext is deprecated from CDI 1.1!
19:59:28,350 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.InjectedJMSContext is deprecated from CDI 1.1!
19:59:28,351 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
19:59:28,583 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0021: Registered web context: '/negotiationAuthenticator' for server 'default-server'
19:59:28,625 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "negotiationAuthenticator.war" (runtime-name : "negotiationAuthenticator.war")
19:59:28,664 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\77\9a3fcdf860d878de68ae96cf348a9b50d91e80\content
19:59:28,668 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "negotiationAuthenticator.war" (runtime-name: "negotiationAuthenticator.war")
19:59:28,702 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
19:59:28,768 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
19:59:28,768 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
19:59:28,768 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
19:59:28,768 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.negotiationAuthenticator.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.

org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase(tcp).test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase.test(SharedSessionFailoverTestCase.java:126)
------- Stdout: -------
20:00:02,473 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\41\966e752b2fc9f4089d43c32cb4fbc4a740e4fa\content
20:00:02,479 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "shared.ear" (runtime-name: "shared.ear")
20:00:02,512 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "war1.war")
20:00:02,512 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "war2.war")
20:00:02,777 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default-server cache from web container
20:00:02,792 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 12) WFLYCLINF0002: Started shared.ear cache from web container
20:00:02,825 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0021: Registered web context: '/war2' for server 'default-server'
20:00:02,825 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 12) WFLYUT0021: Registered web context: '/war1' for server 'default-server'
20:00:02,869 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "shared.ear" (runtime-name : "shared.ear")
20:00:03,087 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\41\966e752b2fc9f4089d43c32cb4fbc4a740e4fa\content
20:00:03,091 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "shared.ear" (runtime-name: "shared.ear")
20:00:03,130 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "war2.war")
20:00:03,130 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "war1.war")
20:00:03,400 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 90) WFLYCLINF0002: Started default-server cache from web container
20:00:03,414 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 26) WFLYCLINF0002: Started shared.ear cache from web container
20:00:03,440 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0021: Registered web context: '/war2' for server 'default-server'
20:00:03,447 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0021: Registered web context: '/war1' for server 'default-server'
20:00:03,468 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "shared.ear" (runtime-name : "shared.ear")
20:00:03,556 INFO  [io.undertow.servlet] (default task-1) /war1/simple, value = 1
20:00:03,586 INFO  [io.undertow.servlet] (default task-2) /war2/simple, value = 2
20:00:03,601 INFO  [io.undertow.servlet] (default task-12) /war1/simple, value = 1
20:00:03,616 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0022: Unregistered web context: '/war1' from server 'default-server'
20:00:03,616 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 12) WFLYUT0022: Unregistered web context: '/war2' from server 'default-server'
20:00:03,649 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 12) WFLYCLINF0003: Stopped default-server cache from web container
20:00:03,658 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 14) ISPN000029: Passivating all entries to disk
20:00:03,707 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 14) ISPN000030: Passivated 3 entries in 49 milliseconds
20:00:03,712 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 14) WFLYCLINF0003: Stopped shared.ear cache from web container
20:00:03,732 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: war1.war) in 122ms
20:00:03,733 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: war2.war) in 124ms
20:00:03,739 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment shared.ear (runtime-name: shared.ear) in 129ms
20:00:03,791 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\41\966e752b2fc9f4089d43c32cb4fbc4a740e4fa\content
20:00:03,792 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "shared.ear" (runtime-name: "shared.ear")
20:00:03,809 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 91) WFLYUT0022: Unregistered web context: '/war1' from server 'default-server'
20:00:03,810 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 26) WFLYUT0022: Unregistered web context: '/war2' from server 'default-server'
20:00:03,834 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 87) ISPN000029: Passivating all entries to disk
20:00:03,840 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 87) ISPN000030: Passivated 3 entries in 5 milliseconds
20:00:03,844 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped default-server cache from web container
20:00:03,846 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 87) WFLYCLINF0003: Stopped shared.ear cache from web container
20:00:03,870 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0208: Stopped subdeployment (runtime-name: war1.war) in 70ms
20:00:03,871 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0208: Stopped subdeployment (runtime-name: war2.war) in 71ms
20:00:03,878 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment shared.ear (runtime-name: shared.ear) in 78ms
20:00:03,905 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\41\966e752b2fc9f4089d43c32cb4fbc4a740e4fa\content
20:00:03,905 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "shared.ear" (runtime-name: "shared.ear")

Full integration - Windows Build 4720 outcome was FAILURE using a merge of 1ccd7364838ca6106b5c33f670e7c3fbe055c733
Summary: Tests failed: 5 (5 new), passed: 4195, ignored: 98 Build time: 02:02:57
Failed tests
org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(tcp).test: java.lang.AssertionError
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
22:27:10,772 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\5c\0bc07ec0136662b4f18276a9e267772a77ddaa\content
22:27:10,796 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
22:27:10,956 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started expiration.war cache from web container
22:27:10,964 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0002: Started default-server cache from web container
22:27:11,018 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 3) WFLYUT0021: Registered web context: '/expiration' for server 'default-server'
22:27:11,047 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
22:27:11,154 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\5c\0bc07ec0136662b4f18276a9e267772a77ddaa\content
22:27:11,157 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
22:27:11,273 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 85) WFLYCLINF0002: Started default-server cache from web container
22:27:11,284 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0002: Started expiration.war cache from web container
22:27:11,302 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0021: Registered web context: '/expiration' for server 'default-server'
22:27:11,331 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
22:27:11,436 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: '/expiration' from server 'default-server'
22:27:11,449 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 31) ISPN000029: Passivating all entries to disk
22:27:11,482 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 31) ISPN000030: Passivated 3 entries in 33 milliseconds
22:27:11,485 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0003: Stopped expiration.war cache from web container
22:27:11,496 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0003: Stopped default-server cache from web container
22:27:11,503 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 67ms
22:27:11,535 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\5c\0bc07ec0136662b4f18276a9e267772a77ddaa\content
22:27:11,536 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
22:27:11,549 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0022: Unregistered web context: '/expiration' from server 'default-server'
22:27:11,562 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000029: Passivating all entries to disk
22:27:11,563 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000030: Passivated 3 entries in 1 milliseconds
22:27:11,565 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped expiration.war cache from web container
22:27:11,585 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 37ms
22:27:11,590 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped default-server cache from web container
22:27:11,622 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\5c\0bc07ec0136662b4f18276a9e267772a77ddaa\content
22:27:11,622 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")

org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(tcp).test: java.lang.AssertionError
	at org.jboss.as.test.clustering.cluster.web.expiration.SessionExpirationTestCase.test(SessionExpirationTestCase.java:101)
------- Stdout: -------
22:27:11,678 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\2d\1514d77c2b516ec37de08d09c43cc5dc306c37\content
22:27:11,681 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
22:27:11,872 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started default-server cache from web container
22:27:11,876 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started expiration.war cache from web container
22:27:11,896 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0021: Registered web context: '/expiration' for server 'default-server'
22:27:11,912 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
22:27:11,930 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\2d\1514d77c2b516ec37de08d09c43cc5dc306c37\content
22:27:11,933 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "expiration.war" (runtime-name: "expiration.war")
22:27:12,056 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started expiration.war cache from web container
22:27:12,070 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0002: Started default-server cache from web container
22:27:12,087 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0021: Registered web context: '/expiration' for server 'default-server'
22:27:12,162 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "expiration.war" (runtime-name : "expiration.war")
22:27:12,228 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) WFLYUT0022: Unregistered web context: '/expiration' from server 'default-server'
22:27:12,235 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 37) ISPN000029: Passivating all entries to disk
22:27:12,238 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 37) ISPN000030: Passivated 4 entries in 3 milliseconds
22:27:12,240 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) WFLYCLINF0003: Stopped expiration.war cache from web container
22:27:12,251 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 25ms
22:27:12,252 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0003: Stopped default-server cache from web container
22:27:12,270 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\2d\1514d77c2b516ec37de08d09c43cc5dc306c37\content
22:27:12,270 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")
22:27:12,275 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0022: Unregistered web context: '/expiration' from server 'default-server'
22:27:12,285 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000029: Passivating all entries to disk
22:27:12,286 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000030: Passivated 3 entries in 1 milliseconds
22:27:12,287 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped expiration.war cache from web container
22:27:12,299 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped default-server cache from web container
22:27:12,299 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment expiration.war (runtime-name: expiration.war) in 25ms
22:27:12,315 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\2d\1514d77c2b516ec37de08d09c43cc5dc306c37\content
22:27:12,315 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "expiration.war" (runtime-name: "expiration.war")

org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(tcp).test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.assertValue(ExternalizerTestCase.java:108)
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test(ExternalizerTestCase.java:96)
------- Stdout: -------
22:27:12,343 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\b2\e585f1e2b937125e41d3ed54edab9cd1b7daf7\content
22:27:12,346 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
22:27:12,464 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) WFLYCLINF0002: Started externalizer.war cache from web container
22:27:12,467 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started default-server cache from web container
22:27:12,495 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 3) WFLYUT0021: Registered web context: '/externalizer' for server 'default-server'
22:27:12,513 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "externalizer.war" (runtime-name : "externalizer.war")
22:27:12,530 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\b2\e585f1e2b937125e41d3ed54edab9cd1b7daf7\content
22:27:12,532 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "externalizer.war" (runtime-name: "externalizer.war")
22:27:12,664 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default-server cache from web container
22:27:12,679 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0002: Started externalizer.war cache from web container
22:27:12,699 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 89) WFLYUT0021: Registered web context: '/externalizer' for server 'default-server'
22:27:12,713 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "externalizer.war" (runtime-name : "externalizer.war")
22:27:12,746 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 29) WFLYUT0022: Unregistered web context: '/externalizer' from server 'default-server'
22:27:12,754 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 30) ISPN000029: Passivating all entries to disk
22:27:12,756 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 30) ISPN000030: Passivated 3 entries in 1 milliseconds
22:27:12,758 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0003: Stopped externalizer.war cache from web container
22:27:12,765 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0003: Stopped default-server cache from web container
22:27:12,771 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment externalizer.war (runtime-name: externalizer.war) in 26ms
22:27:12,787 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\b2\e585f1e2b937125e41d3ed54edab9cd1b7daf7\content
22:27:12,788 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "externalizer.war" (runtime-name: "externalizer.war")
22:27:12,793 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0022: Unregistered web context: '/externalizer' from server 'default-server'
22:27:12,803 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 11) ISPN000029: Passivating all entries to disk
22:27:12,806 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 11) ISPN000030: Passivated 3 entries in 1 milliseconds
22:27:12,807 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0003: Stopped externalizer.war cache from web container
22:27:12,815 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0003: Stopped default-server cache from web container
22:27:12,821 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment externalizer.war (runtime-name: externalizer.war) in 28ms
22:27:12,838 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\b2\e585f1e2b937125e41d3ed54edab9cd1b7daf7\content
22:27:12,838 INFO  [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "externalizer.war" (runtime-name: "externalizer.war")

org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase(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.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:286)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:117)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:108)
------- Stdout: -------
22:27:12,885 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\74\977734340d744a13cdc386a0cfff3bcba70c76\content
22:27:12,888 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "fine-distributable.war" (runtime-name: "fine-distributable.war")
22:27:12,973 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
22:27:12,973 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
22:27:12,974 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
22:27:12,974 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
22:27:12,974 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
22:27:13,008 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment fine-distributable.war
22:27:13,060 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.3.5.Final
22:27:13,171 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-distributable.war"' are as follows:

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

22:27:13,312 INFO  [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 3.0.2 (Final)
22:27:13,349 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0002: Started default-server cache from web container
22:27:13,471 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0002: Started fine-distributable.war cache from web container
22:27:13,680 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
22:27:13,694 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.RequestedJMSContext is deprecated from CDI 1.1!
22:27:13,697 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.TransactedJMSContext is deprecated from CDI 1.1!
22:27:13,702 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.InjectedJMSContext is deprecated from CDI 1.1!
22:27:13,719 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
22:27:13,734 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
22:27:13,739 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1!
22:27:13,744 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1!
22:27:13,746 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1!
22:27:13,747 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1!
22:27:13,749 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1!
22:27:13,750 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1!
22:27:14,170 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) WFLYUT0021: Registered web context: '/fine-distributable' for server 'default-server'
22:27:14,190 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "fine-distributable.war" (runtime-name : "fine-distributable.war")
22:27:14,228 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\8b\63fbf2bd10386f21dc6441c564218cb275978a\content
22:27:14,232 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "fine-distributable.war" (runtime-name: "fine-distributable.war")
22:27:14,291 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
22:27:14,291 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
22:27:14,291 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
22:27:14,291 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
22:27:14,291 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.

org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase(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.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:286)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:117)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulSimpleFailover(AbstractWebFailoverTestCase.java:91)
------- Stdout: -------
22:27:29,903 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-0\standalone\data\content\ef\102a659e15d25e5a2942a139b8c7fd46e9c79c\content
22:27:29,905 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "fine-distributable.war" (runtime-name: "fine-distributable.war")
22:27:29,966 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
22:27:29,966 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
22:27:29,966 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
22:27:29,966 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
22:27:29,966 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
22:27:29,972 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment fine-distributable.war
22:27:29,982 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-distributable.war"' are as follows:

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

22:27:30,044 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0002: Started default-server cache from web container
22:27:30,059 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) WFLYCLINF0002: Started fine-distributable.war cache from web container
22:27:30,071 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
22:27:30,072 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.RequestedJMSContext is deprecated from CDI 1.1!
22:27:30,073 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.TransactedJMSContext is deprecated from CDI 1.1!
22:27:30,074 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.wildfly.extension.messaging.activemq.deployment.injection.InjectedJMSContext is deprecated from CDI 1.1!
22:27:30,076 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
22:27:30,079 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
22:27:30,080 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1!
22:27:30,081 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1!
22:27:30,081 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1!
22:27:30,082 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1!
22:27:30,083 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1!
22:27:30,083 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1!
22:27:30,274 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 3) WFLYUT0021: Registered web context: '/fine-distributable' for server 'default-server'
22:27:30,289 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "fine-distributable.war" (runtime-name : "fine-distributable.war")
22:27:30,307 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location C:\BuildAgent\work\5768cf3a0bee5b47\full\testsuite\integration\clustering\target\wildfly-tcp-1\standalone\data\content\20\751b6e2a53e7467e27feb0b5009b1522460207\content
22:27:30,309 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "fine-distributable.war" (runtime-name: "fine-distributable.war")
22:27:30,364 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
22:27:30,365 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
22:27:30,365 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
22:27:30,365 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
22:27:30,365 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.fine-distributable.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
22:27:30,371 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment fine-distributable.war
22:27:30,379 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "fine-distributable.war"' are as follows:


Handle Read-Only Mode After Cluster Failover

A AWS Aurora MySQL Cluster Failover might leave connections open to the old writer instance which is now a reader instance. (This scenario also applies to other databases and cluster solutions.)
The problem is that these connections are not closed / evicted from the pool.
While it is possible to configure a connectionTestQuery like select 1 from xxx where 1=2 for update as suggested in https://github.com/brettwooldridge/HikariCP/issues/1802#issuecomment-876064227, this is not enough.
A heavily used connection might not even get checked for quite some time without setting the system property com.zaxxer.hikari.aliveBypassWindowMs to 0.
Anyway, these workarounds are not optimal as they create some overhead and might have an impact on performance.
It would be much better if there was a way to handle the Exceptions when they occur and close and evict the connection right away.
For the AWS Aurora MySQL Cluster the exceptions look like this:
class: java.sql.SQLException
message: "The MySQL server is running with the --read-only option so it cannot execute this statement"
errorCode: 1290
SQLState: "HY000"
See https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_option_prevents_statement
Some possible approaches might be:

In ProxyConnection#checkException(SQLException), include this errorCode and SQLState or maybe the combination of both in the check. If there are any scenarios where this behavior is not wanted, maybe guard this with an extra configuration flag like mysqlClusterMode?
Create an extension point to mark connections throwing such a SQLException as to be evicted. This could probably be an extension of the existing SQLExceptionOverride feature. I created a separate issue for that, as I think it is a reasonable feature on its own that might also be useful in other situations: https://github.com/brettwooldridge/HikariCP/issues/2184

There already are some related issues, but I found them to be lacking some detail:
https://github.com/brettwooldridge/HikariCP/issues/1971
https://github.com/brettwooldridge/HikariCP/issues/1802

+1
I need weird crutches to achieve this now
class MysqlReadOnlyInterceptor implements ExceptionInterceptor {
    @Override
    public Exception interceptException(Exception ex) {
        if (ex instanceof SQLException sqlEx) {
            if (sqlEx.getErrorCode() == MysqlErrorNumbers.ER_OPTION_PREVENTS_STATEMENT
                    && sqlEx.getMessage().contains("read-only")) {

                dataSources.stream()
                        .map(HikariDataSource::getHikariPoolMXBean)
                        .filter(Objects::nonNull)
                        .forEach(pool -> {
                            log.warn("Evict connections due to read only {}", pool);
                            pool.softEvictConnections();
                        });
            }
        }
        return ex;
    }
}


are any multi-subdomain servers actually using this in production?

are any multi-subdomain servers actually using this in production? seems unlikely

Yes, we are!
~60 nodes + redis storage
No problems at all

Yup, we're also using this in production for various domains and subdomains. I'm going to close this, but feel free to open a new issue if you have a specific question.


Build error with resource routes

Hi, it seems the build process breaks when a project contains a resource route (A route that does not export a component).
To reproduce:

Create a fresh RePay project.
Add a resource route that does not export a component:

// myroute.tsx

import { redirect } from "@remix-run/node";

export function loader() {
    return redirect('/');
}

When you now try to run yarn build, you get:
server.ts:71:7 - error TS2769: No overload matches this call.
  Overload 1 of 2, '({ build, getLoadContext, mode, }: { build: ServerBuild | (() => Promise<ServerBuild>); getLoadContext?: GetLoadContextFunction | undefined; mode?: string | undefined; }): RequestHandler', gave the following error.
    Type '(() => Promise<ServerBuild>) | { default: typeof import("/home/kwabe007/test/repay/build/server/index"); assets: { entry: { module: string; imports: string[]; css: never[]; }; routes: { ...; }; url: string; version: string; }; ... 7 more ...; routes: { ...; }; }' is not assignable to type 'ServerBuild | (() => Promise<ServerBuild>)'.
      Type '{ default: typeof import("/home/kwabe007/test/repay/build/server/index"); assets: { entry: { module: string; imports: string[]; css: never[]; }; routes: { root: { id: string; parentId: undefined; path: string; ... 9 more ...; css: string[]; }; "routes/myroute": { ...; }; "routes/_index": { ...; }; }; url: string; ver...' is not assignable to type 'ServerBuild | (() => Promise<ServerBuild>)'.
        Type '{ default: typeof import("/home/kwabe007/test/repay/build/server/index"); assets: { entry: { module: string; imports: string[]; css: never[]; }; routes: { root: { id: string; parentId: undefined; path: string; ... 9 more ...; css: string[]; }; "routes/myroute": { ...; }; "routes/_index": { ...; }; }; url: string; ver...' is not assignable to type 'ServerBuild'.
          Types of property 'routes' are incompatible.
            Type '{ root: { id: string; parentId: undefined; path: string; index: undefined; caseSensitive: undefined; module: Readonly<{ __proto__: null; default: () => any; meta: () => ({ title: string; charSet?: undefined; name?: undefined; content?: undefined; } | { ...; } | { ...; })[]; }>; }; "routes/myroute": { ...; }; "routes...' is not assignable to type 'ServerRouteManifest'.
              Property '"routes/myroute"' is incompatible with index signature.
                Type '{ id: string; parentId: string; path: string; index: undefined; caseSensitive: undefined; module: Readonly<{ __proto__: null; loader: () => TypedResponse<never>; }>; }' is not assignable to type 'Omit<ServerRoute, "children">'.
                  Types of property 'module' are incompatible.
                    Property 'default' is missing in type 'Readonly<{ __proto__: null; loader: () => TypedResponse<never>; }>' but required in type 'ServerRouteModule'.

71       build: vite
         ~~~~~

  node_modules/@remix-run/server-runtime/dist/routeModules.d.ts:199:5
    199     default: any;
            ~~~~~~~
    'default' is declared here.
  env.d.ts:43:5
    43     build: ServerBuild | (() => Promise<ServerBuild>);
           ~~~~~
    The expected type comes from property 'build' which is declared here on type '{ build: ServerBuild | (() => Promise<ServerBuild>); getLoadContext?: GetLoadContextFunction | undefined; mode?: string | undefined; }'

Found 1 error in server.ts:71

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build:server" exited with 2.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

If you do however add an empty export:
export default function MyRoute() {
    return <></>;
}

The build process works fine. Resource routes are valid routes in Remix so RePay should support it as well. For now I'll just remember to add an empty component export to my routes but hope to see this fixed :)

Looking into this. Can you share a bit more about your dev environment (OS, node, yarn ver), so I can try to replicate this?

It still does not work after updating the package versions.
Environment:
Ubuntu 22.04.4 LTS (jammy)
Node v20.11.1
yarn v1.22.21
Got the same problem while trying to build a docker image from the project. In the docker image I use pnpm instead of yarn.
Docker Environment:
node:20.11.1-alpine
pnpm v8.15.4

Looks like this is a type issue with Remix. We can skip it for now by adding // @ts-expect-error in server.ts:
createRequestHandler({
      // @ts-expect-error
      build: vite
        ? () => vite.ssrLoadModule("virtual:remix/server-build")
        : await import("./build/server/index.js"),
      getLoadContext(req, res) {

https://github.com/manawiki/repay/commit/08b5e4f7f5072a679d75077795a7235ac7f7c3fe
I'll dig a bit further in this, we might need a PR into Remix core to completely resolve this.

Now that you mention it, I don't think I've checked if the bug exists on the Remix Vite template. I can check it a bit later.

Looking at the Remix Vite template I see that the code for handling SSR requests is different:
// handle SSR requests
app.all("*", remixHandler);

And it works fine building with a resource route.


[BREAKING- REFACTOR] argilla-server: remove metadata filter query param

Description

This PR removes support for filtering using metadata as a query param:

This filter is not available anymore for list endpoints
The metadata filter can be defined as part of the request body for search filters.

Type of change

Breaking change (fix or feature that would cause existing functionality to not work as expected)
Refactor (change restructuring the codebase without changing functionality)

How Has This Been Tested

Checklist

I added relevant documentation
follows the style guidelines of this project
I did a self-review of my code
I made corresponding changes to the documentation
I confirm My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

Looks ok to me (not sure if a line on CHANGELOG.md could be useful).


Add confirmed_flush_lsn to pg_stat_replication

Fixes: panic: inconsistent label cardinality using postgres_exporter with Postgresql 9.6 and replication slots.

Could you rebase this to comply with the new version-managed internals?

Done

Coverage remained the same at 51.815% when pulling eaf80db7ad3807dd08e1aa69cd77c555e937a2b5 on hhulkko:master into 1fa394d4888ed8893e275b1686507fe4c3ff1172 on wrouesnel:master.


HSEARCH-3674 + HSEARCH-3675 Document analysis and core concepts

HSEARCH-3674: Document analysis
HSEARCH-3675: Document core concepts

Merged, thanks!


docs: update (.online)

🚀 The feature
This is a running issue to update the doc and make it easy for everyone to learn and understand the framework.

add details about .online

Motivation, pitch
Make it easy for everyone to read and understand the capabilities of the framework.
Alternatives
No response
Additional context
No response

From #263
i think this should be doable using config now. just that we need to update documentation where we can mention "gpt-4" as the model.

Update docs about:
InitConfig: Server and Port
QueryConfig: Number of documents
From: #299

Update docs about:
App Types: PersonOpenSourceApp
From #299

Closing this issue as documentation changes are done.


Allocate enough space for new socket fd

At line 142 of main.c,
new_sock = malloc(1);
should be
new_sock = malloc(sizeof *new_sock);
in order to allocate enough memory for the new socket fd.

Noted and smashed. Thanks!


[Chore]: Backfill tests for the /v3/jobs endpoint

Background
We do not have any api e2e test for this endpoint
Action to take
Write api e2e tests for:

GET /v3/jobs/{guid]

Impact
We are confident that the jobs endpoint works as expected
Dev Notes
No response

Currently we have tests for GET /v3/jobs/{guid} which exercises org.delete, space.delete & space.applymanifest operations. The remaining work here is to add tests for app.delete and route.delete operations.


SWS-67 Handling errors (404,500) for Service Details endpoint

This PR adds error handling to Service Details endpoint. In particular, it adds the 404 error instead of only responding with 500 errors.

This is connected to SWS-67

@xeviknal can you add in model pod Name string returned with lowercase like labels?
type Pod struct {
	Name   string
	Labels map[string]string `json:"labels"`
}

@aljesusg I prefer to do it in a separate branch, for sanity. I'll publish it right after you are giving me an approval for this PR ;)

#73 is merged.

Yes, it worked. That is useful, let’s see how it evolves :)
El dc, 28 febr 2018 a les 19:18 Joel Takvorian<EMAIL_ADDRESS>va escriure:

@jotak approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/swift-sunshine/swscore/pull/72#pullrequestreview-100171636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAldti4QfEoWzyfek7vHxpkN3CwThELmks5tZZg5gaJpZM4SWhCo
.


P

System Info
when using PlanAndExecutor with guidance prompt of using tools, it does remember previously steps, which will make the pipeline fail as it doesn't know what's previously steps' ouput...

Who can help?
@hwchase17 @agola11
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[X] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
1: define guidence tools prompt:
combo_template = """
First understand the problem and devise a plan to solve the problem.
Please output the plan starting with the header 'Plan:' and then followed by a numbered list of steps. Do not use past conversation history when you are planning the steps.
Please make the plan the minimum number of steps required to accurately complete the task.
These are guidance on when to use a tool to solve a task, follow them strictly:
first use "reverse index search" tool to get table name
if previously step not find anyting，then use "embedding knn search" tool to get table name
if previously step still can't find the answer, say "I can't find the answer for this question."
otherwise use "db Querying Tool" tool to search table info using table name which previously step return
DO NOT CREATE STEPS THAT ARE NOT NEEDED TO SOLVE A TASK.
Once you have answers for the question, stop and provide the final answers. The final answers should be a combination of the answers to all the questions, not just the last one.
Please make sure you have a plan to answer all the questions in the input, not just the last one.
Please use these to construct an answer to the question , as though you were answering the question directly. Ensure that your answer is accurate and doesn’t contain any information not directly supported by the summary and quotes.
If there are no data or information in this document that seem relevant to this question, please just say "I can’t find any relevant quotes".
"""
2: load chat planner with llm(llama2 13b):
planner = load_chat_planner(sm_llm)
system_message_prompt = SystemMessagePromptTemplate.from_template(combo_template)
human_message_prompt = planner.llm_chain.prompt.messages[1]
planner.llm_chain.prompt = ChatPromptTemplate.from_messages([system_message_prompt, human_message_prompt])
executor = load_agent_executor(sm_llm, custom_tool_list, verbose=False)
agent = PlanAndExecute(planner=planner, executor=executor, verbose=False, max_iterations=1)
3: run agent
output = agent({"input":"最近一个月温度合格的派车单数量"})
Expected behavior
base on each steps to get into next step with previously steps' output

Thanks for quick response(not sure whether you are RAG bot or human :) )
but I use the function tool rather than subclassing the BaseTool :
Tool.from_function(
func=customReverseIndexSearch,
name="reverse index search",
description="用于向量检索找到具体的数据库和表名"
),
how can I modify the inner logic of the PlanAndExectutor execution chain ?
is there any other simply way to quickly solve the problem in this scenario？  or it's a bug of PlanAndExectutor with function run Tools?
Thanks again


Suggestion: Reserved diagnostic code for user's custom errors.

TypeScript Version:  2.3.1
We're checking for some error prone patterns in compile-time and making those patterns compiler errors. This involves assigning new error code to these patterns.
We could look at the existing error code from diagnosticMessages and pick some code that are unused. But they can be used in future still.
Expected behavior:
A range of error code is reserved for custom errors.
Actual behavior:
A random currently unassigned error code is used.

How are you adding these errors?

Similar to a Language Service plugin, we wrap the ts.Program in a proxy and decorate getSemanticDiagnostics().
An dummy example would be https://github.com/alexeagle/ts_plugin_prototype/blob/master/tscPlugin.ts

Diagnostics now should have a source property. This should be the name of your plugin. the host (VSCode for instance) would use that to indicate where the error comes from. see https://github.com/Microsoft/TypeScript/issues/15224 for more details.

Thanks mhegazy.source property should be good for us.


feat(service/header): update Store.Append to return amount of applied/valid headers

Currently, Store allows passing via Append partially valid header ranges, but it doesn't report back how many headers were applied, so the caller can react accordingly. This PR provides this by changing the Append method.
Based on #431
Review commit by commit

Yes and it is very minor, but you can review the PR anyway. I am going to resolve the conflict here and in other PRs altogether with any other rebase conflicts that might appear after applying review feedback.


Version 1.58 freezes while running python files

Issue Type: Bug
Taking up to 5 minutes  to run a python file (code as simple as hello world), VS code freezes for seconds .
OS : pop OS 21.04
Version 1.58

/extPython


lint: Add linter for go-kit/logger

It would be awesome to detect those kinds of issues automatically on CI:

Let's research on go-kit/log project first if anything like this exists, if not we can write out own.

I can work on this @bwplotka assign me!

I can work on this @bwplotka assign me!

👍🏽 thanks!

👍🏽 thanks!


Consider supporting and encouraging usage of heroku pipelines

You're probably aware of them, but pipelines may be able to improve or supplant some of the workflows parity provides.

Hey @djcp that's certainly been on my mind.
My next priority (after getting 2.0.0 on Homebrew) is to remove Traveling Ruby and stabilize distribution to non-macOS OSes for the longer-term.

I'm going to close this out until we have a PR. Thanks for the idea!


Export creds to envvars by default

Currently, the default operation (no arguments) displays the commands needed to export the obtained credentials to environment variables.
This creates an unnecessary step of copying and pasting them, as well as being insecure, as those secrets now persist in the shell's history.
The default action should export the credentials automatically and move the display functionality to a command line option, --show.

Fixed in #25


Copy new line

When adding new trip patterns, there are often two or three possibilities with just one or two stops different. For this it would be usefull to have a way to copy the new line and then make adjustments in stead of recreating the whole line.

We should just add a generic "duplicate modification" button.

This has been implemented!


Survey styling refinements

per google doc https://docs.google.com/document/d/1rH6166Uk1Er1TpP2-JdIECr2Yg0_QxGAMV06EtSKS5w/edit
and address issue #45

add "clear" button to allow user to remove answer (see screenshot)

fix UI presentation when user hovers over a radio option (see screenshot)

fix survey formatting on larger screen (see screenshot)

other change

Now that we have enabled clear button, add change to remove answer item from questionnaire responses when its value is cleared by user clicking the Clear button

we don't assemble the QR until the user has pressed the 'Submit' button at the end of the questionnaire...

@mcjustin  my understanding is that the QR is assembled (but not submitted to the FHIR host server) on the onValueChanging event of each question (see here,) so that if there is any CQL expression that needs to be evaluated, it is done based on the latest assembled responses (see here for latest patient bundle sent to CQL worker).  This is relevant, for instance, when a CQL expression being evaluated is to score an instrument.  We don't want to include a response that has since been cleared by the user using the clear button as that would result in a wrong score.  The final QR won't be submitted to the FHIR host server until the Submit button is hit.


Upgrade jackson dependencies

jackson-dataformat-xml is vulnerable to CVE-2016-3720.
Please update the jackson versions included in swagger to at least 2.7.4

Reference to the bug:
https://github.com/FasterXML/jackson-dataformat-xml/issues/199

https://mvnrepository.com/artifact/io.swagger/swagger-jaxrs/1.5.10 has the problematic dependency. This is a duplicate of https://github.com/swagger-api/swagger-core/issues/1937

It is, thanks.