Feature: Add support for auto-pagination API calls

Most endpoints return all the data needed on the very first call, but a few are impacted by the pagination caps and require subsequent calls to get all the data necessary for the final schema generation.
Ideally, this should be made easier by modifying the voyagerFetch method (or associated methods) to accept a parameter to "auto-paginate" with an arbitrary limit, and then have the method run the requests (ideally in parallel if possible) and return the results together as a single combined entity.

I think this is going to be a blocker that needs to get addressed in order to implement a fix for #22.


qdiskinfo: init at 0.2

Description of changes

A native linux alternative to CrystalDiskInfo. Provides SMART information about ATA and NVMe drives.
https://github.com/edisionnano/QDiskInfo
Resubmit of #325304
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Add qtwayland to buildInputs for Wayland support

Added


ci: Added black PEP styleguide formatter and ruff linter.

ci: Added black PEP styleguide formatter and ruff linter.
Includes updated .vscode settings.json with various python related formatted and linting recommendations.
Includes updating .gitignore with .ruff_cache related ignores.

Resolves #10

That's great! Thanks a lot for these @michealroberts!


WIP: Airflow deferrable operator

Closes  #1992
Special notes for your reviewer:
┆Issue is synchronized with this Jira Task by Unito

rebased


Not set offset with null as default for _all_docs

Overview

Revert the change of setting offset with null for _all_docs when keys is set in request to avoid compatibility of returned response where offset with 0 is expected.
Background: there is PR #1085 (Return update_seq and offset when update_seq is true and keys is set) used to address issue https://github.com/apache/couchdb/issues/969 (GET /db/_all_docs?update_seq=true missing 'offset' and 'update_seq' when 'keys' also provided).
Recently, new issue #1648(Result contains "offset": null instead of "offset": 0) was reported to complain "offset": null instead of "offset": 0.
Testing recommendations

make check skip_deps+=couch_epi apps=chttpd tests=all_test_
======================== EUnit ========================
chttpd security tests
Application crypto was left running!
  chttpd_security_tests:147: should_allow_admin_db_compaction...[0.004 s] ok
  chttpd_security_tests:163: should_allow_valid_password_to_create_user...ok
  chttpd_security_tests:173: should_disallow_invalid_password_to_create_user...ok
  chttpd_security_tests:181: should_disallow_anonymous_db_compaction...ok
  chttpd_security_tests:189: should_disallow_db_member_db_compaction...ok
  chttpd_security_tests:192: should_allow_db_admin_db_compaction...[0.003 s] ok
  chttpd_security_tests:202: should_allow_admin_view_compaction...[0.017 s] ok
  chttpd_security_tests:217: should_disallow_anonymous_view_compaction...ok
  chttpd_security_tests:220: should_allow_admin_db_view_cleanup...[0.003 s] ok
  chttpd_security_tests:235: should_disallow_anonymous_db_view_cleanup...ok
  chttpd_security_tests:238: should_allow_admin_purge...[0.020 s] ok
  chttpd_security_tests:254: should_disallow_anonymous_purge...ok
  chttpd_security_tests:262: should_disallow_db_member_purge...ok
  chttpd_security_tests:265: should_allow_admin_purged_infos_limit...[0.003 s] ok
  chttpd_security_tests:280: should_disallow_anonymous_purged_infos_limit...ok
  chttpd_security_tests:288: should_disallow_db_member_purged_infos_limit...ok
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
  [done in 13.188 s]
chttpd db tests
  chttpd_db_test:91: should_return_ok_true_on_bulk_update...[0.063 s] ok
  chttpd_db_test:106: should_return_ok_true_on_ensure_full_commit...[0.005 s] ok
  chttpd_db_test:116: should_return_404_for_ensure_full_commit_on_no_db...[0.006 s] ok
  chttpd_db_test:138: should_accept_live_as_an_alias_for_continuous...[0.044 s] ok
  chttpd_db_test:153: should_return_404_for_delete_att_on_notadoc...[0.007 s] ok
  chttpd_db_test:175: should_return_409_for_del_att_without_rev...[0.107 s] ok
  chttpd_db_test:193: should_return_200_for_del_att_with_rev...[0.084 s] ok
  chttpd_db_test:214: should_return_409_for_put_att_nonexistent_rev...[0.031 s] ok
  chttpd_db_test:229: should_return_update_seq_when_set_on_all_docs...[0.132 s] ok
  chttpd_db_test:243: should_not_return_update_seq_when_unset_on_all_docs...[0.110 s] ok
  chttpd_db_test:257: should_return_correct_id_on_doc_copy...[0.117 s] ok
  chttpd_db_test:288: should_return_400_for_bad_engine...[0.006 s] ok
  chttpd_db_test:300: should_succeed_on_all_docs_with_queries_keys...[0.304 s] ok
  chttpd_db_test:314: should_succeed_on_all_docs_with_queries_limit_skip...[0.307 s] ok
  chttpd_db_test:329: should_succeed_on_all_docs_with_multiple_queries...[0.308 s] ok
  chttpd_db_test:347: should_succeed_on_design_docs_with_queries_keys...[0.307 s] ok
  chttpd_db_test:362: should_succeed_on_design_docs_with_queries_limit_skip...[0.321 s] ok
  chttpd_db_test:377: should_succeed_on_design_docs_with_multiple_queries...[0.315 s] ok
  chttpd_db_test:395: should_succeed_on_local_docs_with_queries_keys...[0.287 s] ok
  chttpd_db_test:410: should_succeed_on_local_docs_with_queries_limit_skip...[0.302 s] ok
  chttpd_db_test:424: should_succeed_on_local_docs_with_multiple_queries...[0.307 s] ok
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
  [done in 9.221 s]
chttpd db max_document_size tests
  chttpd_db_doc_size_tests:84: post_single_doc...ok
  chttpd_db_doc_size_tests:92: put_single_doc...ok
  chttpd_db_doc_size_tests:101: bulk_doc...ok
  chttpd_db_doc_size_tests:127: put_post_doc_attach_inline...ok
  chttpd_db_doc_size_tests:128: put_post_doc_attach_inline...ok
  chttpd_db_doc_size_tests:129: put_post_doc_attach_inline...ok
  chttpd_db_doc_size_tests:130: put_post_doc_attach_inline...ok
  chttpd_db_doc_size_tests:152: put_multi_part_related...ok
  chttpd_db_doc_size_tests:153: put_multi_part_related...ok
  chttpd_db_doc_size_tests:177: post_multi_part_form...ok
  chttpd_db_doc_size_tests:178: post_multi_part_form...ok
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
  [done in 1.897 s]
=======================================================
  All 48 tests passed.

Related Issues or Pull Requests

#1648
#1085
Checklist

[X] Code is written and works correctly;
[X] Changes are covered by tests;
[ ] Documentation reflects the changes;

offset was added because of issue https://github.com/apache/couchdb/issues/969.  Why are we reverting it?

and PR https://github.com/apache/couchdb/pull/1085 is related, see the discussion there.

offset was added because of issue #969. Why are we reverting it?

We are breaking Java libraries by changing the type of the value we return.
@rnewson : Please -1 if you think we shouldn't revert it. I am not sure what would be the right course of action in this case.

Also see @davisp opinion here https://github.com/apache/couchdb/issues/1648#issuecomment-442965049

imo it has been null since nov 2017 without significant issue. It is not "Java libraries" per se that don't like this, I think? Just one specific one that insists on adding strong typing.
The ultimate right place to be, in my view, is not to send offset at all, for any set of parameters. That will require a major version number bump so we shouldn't do that now.
The history here is one person filed a ticket requesting we send offset where previously we weren't, and we did, and now a second person (I'm inferring that happened in an IBM support ticket that did not get reported here?) requesting offset be 0?
I don't think it's right to change the API on either basis, and we're implicitly saying that this part of the API flip flops based on who complains most recently, which is no basis at all.
Saying offset: 0 for a view response that does not start with the earliest emitted key for the view is wrong and we should not do it. Whether omitting offset entirely or including offset:null is better, I'm less sure. I would stick with existing behaviour (i.e, do not merge this PR) and instead report the issue to the client library that has a problem with null.

sidebar: if this PR is initiated by an IBM support ticket, I think that should be declared at the start. The "overview" could have expanded on the problem and called it out as a backward compatibility issue, citing previous CouchDB releases' behaviours.

sidebar: if this PR is initiated by an IBM support ticket, I think that should be declared at the start.

I don't think it was opened by IBMer.

thanks @iilyak and @rnewson for comments. The background I got is from https://github.com/apache/couchdb/issues/1648. I am not aware of the ticket from IBM support yet.
But the following comments make sense, and I will add them

The "overview" could have expanded on the problem and called it out as a backward compatibility issue, citing previous CouchDB releases' behaviours.

@jiangphcn any plans to get this in? I am preparing to mass-close old PRs that never got merged.

Due different opinion about whether we need to "offset": null instead of "offset": 0, I suggest to close this PR and keep current behavior. If there is strong request to revert, we can re-open this PR and follow up.
Thanks @wohali for checking.


Enabling PDF Docs upload

Does anyone have any idea how this could be achieve?
The file model seems to be written in a way that it only allow images.

No, files are files. It has some handling for images to create thumbnails, but any file can be uploaded. Are you getting an error of some kind?

A mistake on our part.
Nginx/Apache configuration is disabling the users from uploading files larger than certain size.


generalized the ecephys metadata for spikeglx so it can be called outside the class

@bendichter When using the SIPickle interfaces to read in a processed (synchronized) recording extractor, the electrode metadata format has to be directly added to the metadata prior to conversion to avoid filling with default values.
Specific to the use in the Tank lab, this PR generalizes this as a static method so it can be called in the conversion scripts prior to run_conversion.
PR pointing to add_save_si_object_function branch for readability.

ToDo: work out and implement the better way of retrieving ecephys metadata from cross-interface or cross-repo methods instead of static usage with manual parameter passing. Possible solution, as Ben suggested, could be to just always instantiate a recording extractor local to the get_metadata method that can use its internal workings in the way an extractor would if it were intended to be converted.

This is now unnecessary. Closing


State in script not pulling correctly?

Alarmo Version
1.8.7
HA Version
2022.4.7
Bug description
I have a script that runs when the alarm is triggered. The script waits 30s, then checks the state condition. If it's still triggered, it will turn on a siren. The purpose is to give us time to disarm the alarm after it has been triggered without sounding the alarm.
When I run the script, the only state returned is armed_away, even when triggered, or armed_home. I have not been able to get a different state.
Executed: May 3, 2022, 6:10:14 PM
Result:
result: false
entity_id/0
Executed: May 3, 2022, 6:10:14 PM
Result:
result: false
state: armed_away
wanted_state: triggered
Steps to reproduce
No response
Relevant log output
No response

I'm really not sure if something is wrong on Alarmo's side which could cause this.
Is the script configured as an action in Alarmo?
Perhaps the triggering of the script and the state change of the alarm_control_panel entity coincide?
You can enable debug logging for alarmo by adding this to the configuration.yaml of HA and restarting HA:
logger:
  default: warning
  logs:
    custom_components.alarmo: debug

You could use it to see at which point your automation is triggered.
In the .storage/alarmo.storage file you could find back the ID's of the automations.

Thanks, I appreciate the reply! I'll dig in and see if I can track it down. I did have it running as an action in Alarmo. I've upgraded to HA 2022.5.1, so I may try the new If-Then action to see if it works that way.


Separate color variables and classes

Closes #3743

See https://github.com/Dogfalo/materialize/pull/4556/


Option to hide the top bar or make it thinner

The document font is too small, so if I zoom the page in, the top bar gets thicker, taking up limited vertical space of modern wide-screen monitors. I do not think the top bar serves any useful features for the most people. How about providing a feature to hide that top bar?

Hello @HubKing,
Thank you for reaching out to us and sharing your feedback. We'll keep it in mind for the future maintenance of  codelabs.


types of macro defined constants

Why are the types of ZSTD_CONTENTSIZE_UNKNOWN and  ZSTD_CONTENTSIZE_ERROR in rust is i32 but in the C header file are defined as unsigned long long int?
https://docs.rs/zstd-sys/2.0.1+zstd.1.5.2/src/zstd_sys/bindings_zstd_experimental.rs.html#49-50
https://github.com/facebook/zstd/blob/dev/lib/zstd.h#L180-L181

These bindings are auto-generated, so it seems to be what bindgen comes up with.
Note that zstd_safe re-exports this variable with the proper type: https://docs.rs/zstd-safe/latest/src/zstd_safe/constants.rs.html#6


fix(UserCollection): remove duplicate interval refresh

Thank you for your contribution! Unfortunately this PR is now stale so for house keeping purposes we're going to close it. Feel free to update the code and re-open the PR if the changes are still relevant.


Test subcommands sort

Codecov Report

Merging #12 (6877cd2) into main (3cfaf46) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   96.69%   96.69%
=======================================
  Files           4        4
  Lines         242      242
=======================================
  Hits          234      234
  Misses          6        6
  Partials        2        2

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 3cfaf46...6877cd2. Read the comment docs.


CRDT Operations

Add operations to support CRDTs.

Was an issue for the .Net client, not the java client.
[posted via JIRA by Alexander Moore]


ocr_predictor always use cpu not gpu

Bug description
the workload always on cpu, not gpu
Code snippet to reproduce the bug
from doctr.models import ocr_predictor
import os

os.environ["USE_TORCH"] = '1'

predictor = ocr_predictor(det_arch='db_resnet50', reco_arch='crnn_vgg16_bn', pretrained=True)

Error traceback
no error
Environment
DocTR version: 0.6.1a0
TensorFlow version: N/A
PyTorch version: 2.0.1 (torchvision 0.15.2)
OpenCV version: 4.7.0
OS: Ubuntu 22.04.2 LTS
Python version: 3.8.16
Is CUDA available (TensorFlow): N/A
Is CUDA available (PyTorch): Yes
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: Tesla P40
Nvidia driver version: 530.41.03
cuDNN version: Could not collect
Deep Learning backend
is_tf_available: False
is_torch_available: True

find out works code
device = torch.device("cuda:0")
predictor = ocr_predictor(det_arch='db_resnet50', reco_arch='crnn_vgg16_bn', pretrained=True).to(device)

find out works code
device = torch.device("cuda:0")
predictor = ocr_predictor(det_arch='db_resnet50', reco_arch='crnn_vgg16_bn', pretrained=True).to(device)

Doesn't work in google colab
AttributeError: 'OCRPredictor' object has no attribute 'to'

You need to set os.environ['USE_TORCH'] = 'YES' and os.environ['USE_TF'] = 'NO'. That solved the issue for me.


Build script not cross platform, fails on windows

in package.config
"build:clean": "rm -rf build/",  this will not work on windows and build fails.

@snios Thank you for reporting. I'll replace it with rimraf.

Fixed by 5e224fc3267639d4c1ed6829f29bb3dd4a3d970e


Dashboard product image not found

Dashboard product image popup, image not found.

Path of the images seems to repeate. (see screenshot)
settings.py
MEDIA_URL = '/media/'
MEDIA_ROOT = location('public/media')
STATIC_URL = '/static/'
STATIC_ROOT = location('public/static')
nginx.conf
location /static/ {
alias /app/sandbox/public/static/;
expires max;
}
location /media/ {
	alias /app/sandbox/public/media/;
	expires max;
}

This is the only place I have issues with images. Other views are using media/cache path. Any idea what is causing it? I have tried turning debug mode off and other things, but nothing seems to work.

Hi there. We use Github only for managing bugs and feature requests, and not for support. We recommend that you ask for help on Stack Overflow using the django-oscar tag, or joining our slack workspace and asking a question there. I'd suggest you post your full settings file and full project structure on Stack Overflow, as the information you've provided about isn't sufficient to know what might be going on. Thanks.


Linking error with LDC on Win64 due to strange subpackage libs-ldc

Testing dub (v1.1) and vibe.d (v0.7.30) with an early LDC 1.1 (https://github.com/ldc-developers/ldc/pull/1891), a project template cannot be linked on Win64 due to missing z.lib. This seems to come in via vibe.d's subpackages in %AppData%\dub\packages\vibe-d-0.7.30\vibe-d\dub.json, where there's a "libs-ldc": [ "z" ] item. Removing it gets the project to compile, link and run successfully, with both LDC2 and LDMD2.
I did a quick test on Ubuntu 16.04 (x86_64), removed the subpackage as well (and worked around #1611 with a manually added OpenSSL dependency), and it's also working. So this LDC-specific dependency (on zlib apparently) may not be required after all (isn't it part of druntime Phobos?) and only causes trouble on Windows.

I had to add the explicit dependency a while ago (9df23d49, same was done for GDC: #1607). Did the build succeed on Linux without removing it? If that's the case, I would suggest to change this to "libs-ldc-posix": ["z"], so that older versions of LDC also still work.

Did the build succeed on Linux without removing it?

It did. So your suggested fix makes sense, although zlib should be part of libphobos2-ldc for quite a while now.

Okay, I'll change it like that then. Based on the context of my commit, I guess that LDC 1.0.0 was still affected by this, which is still the latest stable release, so I'd like to keep the workaround for a while still.


config: define config_names [more]

These are the names of the config.py variables
that can be used to override the BibliogaphicResourceConfigs
and BibliographicServiceConfig.

closes https://github.com/inveniosoftware/invenio-records-resources/issues/67
(needs https://github.com/inveniosoftware/invenio-records-resources/pull/76 but not for tests to pass)

Coverage increased (+0.05%) to 90.204% when pulling 6b41e30e2ecbcc1bfa3688e34167e1ac3fc9a97b on fenekku:67_set_config_names into 4930e785bf9f21cf39615c4115f0b97c06a478cf on inveniosoftware:master.


feat: support image set for superset worker separately in helm chart

SUMMARY

To enable alerts and reports, i need to use dev image or custom built image for superset worker. This PR allows for users to use dev image only for worker.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@josedev-union it feels incomplete to add this optionality to supersetWorker, but not the other deployments, too. For consistency, do you think it would make sense to make this available to the other ones as well?

Also, just a note that you'll need to run the pre-commit hook for CI to pass.


Special characters: Umlaute not displayed properly

The app can't show Umlaute, instead a " � " is displayed.

I have the same problem. All my feeds use Cyrillic characters, so I can't use this app


Feature Requested: Navigation with Google Earth Style

Hi.
I want a navigation animation which works like Google Earth app. I mean you start in a zoom position and then the animation begin to zoom out and drag the map and then when your are near the desired target position the animation zoom in.
I have developed something similar but I'm not very happy with the result. I have my own MapControl with this functions
private void StartNavigationAnimationWithZoom(double begin, double middle, double end,
            double originX, double originY,
            double finalX, double finalY)
        {
            if (begin != double.NaN && middle != double.NaN && end != double.NaN)
            {
                if (begin > middle)
                {
                    middle = begin;
                }
                _firstZoomAnimation.From = begin;
                _firstZoomAnimation.To = middle;
                _firstZoomAnimation.Completed -= _firstZoomAnimation_Completed;
                _firstZoomAnimation.Completed += _firstZoomAnimation_Completed;

                _secondZoomAnimation.From = middle;
                _secondZoomAnimation.To = end;
                zoomViewportLocked = false;
                _secondZoomAnimation.Completed -= _secondZoomAnimation_Completed;
                _secondZoomAnimation.Completed += _secondZoomAnimation_Completed;

                _pointAnimation.From = new Point(originX, originY);
                _pointAnimation.To = new Point(finalX, finalY);

                _currentMousePosition = new Point(ActualWidth / 2, ActualHeight / 2);
                this.BeginAnimation(ResolutionProperty, _firstZoomAnimation);
                this.BeginAnimation(CenterProperty, _pointAnimation);
            }

        }

        private void _secondZoomAnimation_Completed(object sender, EventArgs e)
        {
            _secondZoomAnimation.Completed -= _secondZoomAnimation_Completed;
            zoomViewportLocked = true;
            OnNavigateWithZoomOperationFinished(EventArgs.Empty);
        }

        private void _firstZoomAnimation_Completed(object sender, EventArgs e)
        {
            _firstZoomAnimation.Completed -= _firstZoomAnimation_Completed;
            this.BeginAnimation(ResolutionProperty, _secondZoomAnimation);
        }

public void NavigateToPositionWithZoomAnimation(double finalLat, double finalLon, int finalZoomLevel)
        {
            Mapsui.Geometries.Point oldCenter = Map.Viewport.Center;
            Mapsui.Geometries.Point oldCenterLatLon = new Mapsui.Geometries.Point();
            Mapsui.Geometries.Point finalCenterLatLon = new Mapsui.Geometries.Point(finalLon, finalLat);
            Mapsui.Geometries.Point finalCenter = new Mapsui.Geometries.Point();

            if (Map.CRS == CRS_WEB_MERCATOR)
            {
                oldCenterLatLon =
                    Mapsui.Projection.SphericalMercator.ToLonLat(oldCenter.X, oldCenter.Y);

                finalCenter = Mapsui.Projection.SphericalMercator.FromLonLat(finalLon, finalLat);
            }
            else if (Map.CRS == CRS_LAT_LON)
            {
                oldCenterLatLon.X = oldCenter.X;
                oldCenterLatLon.Y = oldCenter.Y;
                finalCenter.X = finalLon;
                finalCenter.Y = finalLat;
            }

            //Obtain Middle Resolution based on distance
            double distanceBetweenCenters = DistFrom(oldCenterLatLon.Y, oldCenterLatLon.X, finalCenterLatLon.Y, finalCenterLatLon.X);
            double finalResolution = (Map.Resolutions.Count <= finalZoomLevel || finalZoomLevel < 0) ? Map.Resolutions.Last() : Map.Resolutions[finalZoomLevel];
            double middleResolution = ZoomHelper.DetermineResolution(distanceBetweenCenters, distanceBetweenCenters, Map.Viewport.Width, Map.Viewport.Height);

            if (middleResolution < finalResolution)
            {
                middleResolution = finalResolution;
            }

            OnMapAnimationStarted(EventArgs.Empty);

            StartNavigationAnimationWithZoom(Map.Viewport.Resolution, middleResolution, finalResolution,
                oldCenter.X, oldCenter.Y,
                finalCenter.X, finalCenter.Y);
        }

Tell me if you need more details about implementation.

It would be nice to hear, what the reason is, that you are not satisfied with your solution.

i want to get rid of my map control and use the  one from Mapsui. In order to improve compatibility with new versions of Mapsui.

In v4 something like exists in the Navigator.FlyTo animation.
The exact way this behaves might not be what you want but it is also possible to add your own animation. You could start with copying the FlyToAnimation.Create method (this is used in the FlyTo animation) and apply it like this:
Navigator.SetViewportAnimations(MyFlyToAnimation.Create( ... ));


[WFCORE-3872] Upgrade to WildFly Galleon plugins 1.0.0.CR7 and fork e…

…mbedded in the build
https://issues.jboss.org/browse/WFCORE-3872
This commit upgrades to the latest WF Galleon plugins which includes an option to execute embedded server operations in a separate process to avoid FD leaks.

retest this please

^^^ is to try and get CI to run.
@aloubyansky testing this on master-ignore the build fails:
[17:51:22][Step 3/5] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugins:1.0.0.CR7:generate-feature-specs (feature-spec-build) on project wildfly-core-galleon-pack: Feature spec generator failed
https://ci.wildfly.org/viewLog.html?buildId=106055&buildTypeId=WildFlyCore_MasterIgnorWindows&tab=buildLog&_focus=12053

Core - Full Integration Build 7431 outcome was FAILURE using a merge of d71293e5cbafe535eff43c9f5fd9b21248591398
Summary: Exit code 1 (new) Build time: 00:01:32

Core - Full Integration Build 7434 outcome was FAILURE using a merge of 144caf84e31d14decfd243d8f6e0401c62e62f77
Summary: Exit code 1 Build time: 00:01:36

@aloubyansky could you ping us when this PR is ready to be merged.

The error on the Linux JDK9 seems related to the PR:
[10:48:05]W:	 [Step 2/3] [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugins:1.0.0.CR10:generate-feature-specs (feature-spec-build) on project wildfly-core-galleon-pack: Feature spec generator failed: Failed to read feature spec file /store/work/temp/buildTmp/wfgp3374547397248029361standalone-specs: org.jboss.dmr.stream.ModelException: Unexpected EOF while reading DMR stream -> [Help 1]
[10:48:05] :	 [Step 2/3] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugins:1.0.0.CR10:generate-feature-specs (feature-spec-build) on project wildfly-core-galleon-pack: Feature spec generator failed

Core - Full Integration Build 7438 outcome was FAILURE using a merge of cf0c24afca3f400962946c374e9dc8d56e86f17a
Summary: Tests failed: 1 (1 new), passed: 4340, ignored: 142 Build time: 01:38:54
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m00:55:43,336 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/0e/06c42149933a6d501e8e6cb5e4d2dc563208aa/content
 [0m [0m00:55:43,339 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m00:55:43,410 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m00:55:43,410 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m00:55:43,410 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m00:55:43,411 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m00:55:43,411 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m00:55:43,435 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m00:55:43,491 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m00:55:43,559 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

 [0m [0m00:55:43,678 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.0.4 (Final)
 [0m [0m00:55:43,806 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m00:55:43,845 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m00:55:44,001 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!
 [0m [33m00:55:44,011 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!
 [0m [0m00:55:44,295 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m00:55:44,340 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m00:55:44,430 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/d0/40cf143cf6e8e73156c43de6bd7b4da23a0190/content
 [0m [0m00:55:44,433 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m00:55:44,527 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m00:55:44,527 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m00:55:44,527 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m00:55:44,527 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m00:55:44,527 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m00:55:44,554 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m00:55:44,602 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m00:55:44,665 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

Core - Full Integration Build 7441 outcome was FAILURE using a merge of 4259b31d9e218a63de443cd568372a9ec2a41776
Summary: Tests failed: 4 (3 new), passed: 4337, ignored: 142 Build time: 01:39:48
Failed tests
org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:45:50,256 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/53/75aa12d8a9517ad3f695bd8c52aa96bdfd691d/content
 [0m [0m03:45:50,261 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m03:45:50,370 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:45:50,370 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:45:50,371 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:45:50,371 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:45:50,371 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:45:50,406 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m03:45:50,476 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:45:50,573 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

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

 [0m [0m03:45:50,712 INFO  [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.0.4 (Final)
 [0m [0m03:45:50,798 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 7) WFLYCLINF0002: Started CoarseWebFailoverTestCase.war cache from web container
 [0m [0m03:45:50,803 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 9) WFLYCLINF0002: Started default-server cache from web container
 [0m [33m03:45:51,029 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [33m03:45:51,048 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [0m03:45:51,372 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0021: Registered web context: '/CoarseWebFailoverTestCase' for server 'default-server'
 [0m [0m03:45:51,391 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "CoarseWebFailoverTestCase.war" (runtime-name : "CoarseWebFailoverTestCase.war")
 [0m [0m03:45:51,514 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/53/75aa12d8a9517ad3f695bd8c52aa96bdfd691d/content
 [0m [0m03:45:51,517 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m03:45:51,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:45:51,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:45:51,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:45:51,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:45:51,557 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:45:51,561 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m03:45:51,574 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

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

org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:46:19,982 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
 [0m [0m03:46:20,314 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
 [0m [0m03:46:20,324 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
 [0m [0m03:46:20,499 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Beta2-SNAPSHOT (WildFly Core 5.0.0.Beta5-SNAPSHOT) starting
 [0m [0m03:46:22,144 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:46:22,180 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 23) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:46:22,188 INFO  [org.wildfly.security] (ServerService Thread Pool -- 2) ELY00001: WildFly Elytron version 1.3.2.Final
 [0m [0m03:46:22,327 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m03:46:22,348 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
 [0m [0m03:46:22,363 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
 [0m [0m03:46:22,399 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 41) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m03:46:22,428 INFO  [org.jboss.as.ee] (ServerService Thread Pool -- 44) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
 [0m [0m03:46:22,438 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m03:46:22,475 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.0.11
 [0m [0m03:46:22,534 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
 [0m [0m03:46:22,538 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 65) WFLYSEC0002: Activating Security Subsystem
 [0m [0m03:46:22,545 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m03:46:22,548 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.5.1.Final
 [0m [0m03:46:22,549 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m03:46:22,551 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
 [0m [0m03:46:22,551 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.2.Final
 [0m [33m03:46:22,555 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 68) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m03:46:22,577 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 59) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m03:46:22,642 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.7.Final
 [0m [0m03:46:22,648 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 70) WFLYWS0002: Activating WebServices Extension
 [0m [0m03:46:22,704 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 2.0.7.Final starting
 [0m [0m03:46:22,741 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
 [0m [0m03:46:22,742 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m03:46:22,854 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m03:46:22,854 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
 [0m [0m03:46:22,935 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m03:46:22,973 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
 [0m [0m03:46:22,975 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
 [0m [0m03:46:23,015 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
 [0m [0m03:46:23,017 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m03:46:23,022 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000001: Initializing mod_cluster version 1.3.9.Final
 [0m [0m03:46:23,031 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m03:46:23,092 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m03:46:23,143 INFO  [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [0m03:46:23,158 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 [0m [33m03:46:23,166 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m03:46:23,182 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/deployments

org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:46:45,074 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/43/09d1bc9ba417c2a20eeada490d969ccdb7d4ad/content
 [0m [0m03:46:45,079 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:46:45,088 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,143 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:46:45,149 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:46:45,162 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

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

 [0m [33m03:46:45,309 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m03:46:45,311 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-6) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m03:46:45,345 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) WFLYCLINF0002: Started ReplicationForNegotiationAuthenticatorTestCase.war cache from web container
 [0m [0m03:46:45,356 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 11) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:46:45,502 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0021: Registered web context: '/ReplicationForNegotiationAuthenticatorTestCase' for server 'default-server'
 [0m [0m03:46:45,517 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name : "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [0m03:46:45,534 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/43/09d1bc9ba417c2a20eeada490d969ccdb7d4ad/content
 [0m [0m03:46:45,536 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:46:45,546 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:46:45,581 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:46:45,585 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:46:45,591 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

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

org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:44:52,211 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/fd/cc1c88e31ab0d4b0aabda1b9012b126f1ea8f1/content
 [0m [0m03:44:52,213 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:44:52,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:44:52,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:44:52,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:44:52,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:44:52,310 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:44:52,339 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:44:52,407 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:44:52,478 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

 [0m [0m03:44:52,593 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.0.4 (Final)
 [0m [0m03:44:52,703 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:44:52,748 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m03:44:52,912 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!
 [0m [33m03:44:52,922 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!
 [0m [0m03:44:53,224 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 28) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m03:44:53,236 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m03:44:53,314 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/fd/cc1c88e31ab0d4b0aabda1b9012b126f1ea8f1/content
 [0m [0m03:44:53,317 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:44:53,399 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:44:53,399 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:44:53,399 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:44:53,399 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:44:53,399 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:44:53,423 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:44:53,470 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:44:53,530 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

Core - Full Integration Build 7443 outcome was UNKNOWN using a merge of 4259b31d9e218a63de443cd568372a9ec2a41776
Summary: Canceled (Error while applying patch; cannot find commit 2782191b00df2814a101ac85bfc8b400cc270aa7 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/3321/merge branch was updated and the commit selected for the ... Build time: 00:00:11

Core - Full Integration Build 7442 outcome was FAILURE using a merge of 4259b31d9e218a63de443cd568372a9ec2a41776
Summary: Tests failed: 1, passed: 4340, ignored: 142 Build time: 02:07:41
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: 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:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:44:39,481 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/06/138a3f87638e3587a42405eb15f1c80c9dac49/content
 [0m [0m03:44:39,484 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:44:39,630 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:44:39,630 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:44:39,630 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:44:39,630 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:44:39,630 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:44:39,664 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:44:39,731 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:44:39,815 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

 [0m [0m03:44:39,983 INFO  [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.0.4 (Final)
 [0m [0m03:44:40,171 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:44:40,172 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m03:44:40,456 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m03:44:40,471 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m03:44:41,022 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m03:44:41,069 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m03:44:41,213 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/a2/770a8848f8e9a7fe4a67a7b0462bb831b56a66/content
 [0m [0m03:44:41,219 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:44:41,414 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:44:41,414 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:44:41,414 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:44:41,414 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:44:41,414 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:44:41,452 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:44:41,544 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:44:41,644 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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


feat: report-problem base

Controls should be in line with the body of the component.

"Describe the problem" text is displayed in a wrong font


Feature request: New snapshot of Equity or Free Margin bassed off user set timer

A perfect feature to add to make this already great software even better :) Thank you in advance.
Eg. at local or server time 17:00 every day, take a new snapshot of the account equity.

Hello!
That's already possible. You just set up a second instance of AP with the timer and the Capture Snapshots action. You also need to set the Global Snapshots input for both instances.


upload fails for analyses with same name

append unique id to analysis name so that unique collection can be created on neurovault and images can be uploaded successfully

This is actually a main NS bug, a should be closed


Move models to their own separate model folder.

Currently the models in the yacs-web/src/app folder are not well organized; they are all in their own separate folders. We should create a new model folder where all models will be saved and use the convention:
name.model.ts
This should be placed in the folder:
yacs-web/src/app/models
This would mean that we also need to update all the file locations that use these models.
The current models are:

course-list/course/course.ts
course-list/section/period.ts
course-list/section/section.ts
schedule-view/schedule/schedule.ts
schedule-view/schedule-event/schedule-event.ts
school-list/department/department.ts
school-list/school/school.ts

Changes have been made. Double checking completion before pushing to fork

Multiple files overlap with a recent RP of mine. Will wait for resolution of said PR before pushing so as to avoid confusion

Fixed as of #47
Thanks again @marchdan !


⚠ Fetchers has degraded performance

In fa5187a, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 232 ms

Resolved: Fetchers performance has improved in e46d26b.


Verification service recognizes revocation and reports it correctly

I think that this one can be closed. What do you think @2byrds ?


Set alpha values for different parts of an Image

Is is possible to set the alpha values separately for each point of an Image? This would be useful for layering images on top with different blending modes.

Yes, if you have an NxMx4 image, then the last channel would be the alpha channel and it should participate in transparancy/blending as expected.


Statusbar with icons disapperad, terminal-plus not working

It just stopped working. I removed and reinstalled, but it still isn't working.

Please taka a look at https://github.com/jeremyramin/terminal-plus/issues/223 temporary.

What about #223?

What is the Atom version?

1.7.1

Do you have the same problems with https://atom.io/packages/platformio-ide-terminal ?

Hm, https://atom.io/packages/platformio-ide-terminal  seems to be working OK!


Updated readme with security paragraph

Sorry for the barrage of PRs, just trying to make it easier for you to pick changes a la carte.

AFAICT you'll need to override node['consul']['service_user'] to change the owner of the file, not node['consul']['config']['owner'], and this will only work on Linux (might want to mention that too).
https://github.com/johnbellone/consul-cookbook/blob/master/libraries/consul_config.rb#L125


Define GOPATH and GOBIN when undefined within module

Fixes https://github.com/edgexfoundry-holding/edgex-cli/issues/118

lgtm


Ignore auto generated tags

If you use this plugin as a submodule with pathogen or whatever this file is generated and then shows up as an unstaged commit

@lespea Thanks for your help.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210718213712538 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210718213712538 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.566%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26721

Relevant Lines:
56896

💛  - Coveralls


Bard doesn't remember on rerun

bard doesn't remember on rerun whats the conversation id used for im passing it to bardcookies but it still wont remember past conversation

This issue cannot be supported at the bardapi package level.
Officially, chatgpt has recently fixed the seed and retains the conversation, but Bard still appears to have different IDs for multi-choice. In other words, there are no options to fix the stream option and seed like chatgpt, and the only way is to keep appending previous conversation in a certain format.
Since this requires modifications at Google's official model server level, we have to close this issue as something that cannot be supported at the package level. We appreciate you checking for any duplicate issues. (We will update if it is supported in the future.)
Thank you.
#99 opened on Jul 12 by ranjan-sumit
#59 opened on Jun 10 by BabaYaga1221
#30 by MohitSM18 was closed on May 23
#19 by CatAnonymous was closed on May 19
#15 by debayangg was closed on May 18


ROX-17956: Fix error in roxctl authorize mode

Description
Currently, when executing roxctl central login and the central instance doesn't have any auth provider configured besides the default basic auth provider, the authorize roxctl page will contain an error.
This is due to the current login page code assuming that there will be at least one auth provider within the list of available auth providers. However, since we filter out the basic auth provider in roxctl authorize mode, since its not compatible with the flow, this assumption doesn't hold true anymore.
This PR fixes this by a) ensuring that the current code in LoadingOrForm respects potential empty auth provider list within the initial values and b) returning an error in roxctl authorize mode in case of an empty auth provider list after filtering out the basic auth provider.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #6584   👈

This comment was auto-generated by Graphite.

@dhaus67 if this is ready on your end please merge it asap so I can cut what's looking like the final RC


Front-proxy Example: Didn't find a registered implementation for name: 'envoy.filters.network.http_connection_manager'

Title: Front-proxy Example: Didn't find a registered implementation for name: 'envoy.filters.network.http_connection_manager'
Description:
I'm facing the issue when I run front-proxy example: https://www.envoyproxy.io/learn/on-your-laptop. Envoy doesn't start due to Didn't find a registered implementation for name: 'envoy.filters.network.http_connection_manager' error.
Switching to envoyproxy/envoy-dev:latest doesn't help in this case. I'm facing the same issue with v1.13.0, v1.12.2, v1.11.0 etc. Please advise how to run front-proxy example or make fixes to make sure it's working properly as this is a blocker for potential users. Thanks!
Repro steps:
Just follow https://www.envoyproxy.io/learn/on-your-laptop to run front-proxy
ALMOSTSEEDRADIO:front-proxy ma$ docker-compose ps
front-proxy_front-envoy_1   /docker-entrypoint.sh /bin ...   Exit 1
front-proxy_service1_1      /bin/sh -c /usr/local/bin/ ...   Up       10000/tcp, 80/tcp
front-proxy_service2_1      /bin/sh -c /usr/local/bin/ ...   Up       10000/tcp, 80/tcp
Logs:
[2020-02-19 18:29:15.230][7][info][main] [source/server/server.cc:251] initializing epoch 0 (hot restart version=11.104) [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:253] statically linked extensions: [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.filters.http: envoy.buffer, envoy.cors, envoy.csrf, envoy.ext_authz, envoy.fault, envoy.filters.http.adaptive_concurrency, envoy.filters.http.dynamic_forward_proxy, envoy.filters.http.grpc_http1_reverse_bridge, envoy.filters.http.grpc_stats, envoy.filters.http.header_to_metadata, envoy.filters.http.jwt_authn, envoy.filters.http.on_demand, envoy.filters.http.original_src, envoy.filters.http.rbac, envoy.filters.http.tap, envoy.grpc_http1_bridge, envoy.grpc_json_transcoder, envoy.grpc_web, envoy.gzip, envoy.health_check, envoy.http_dynamo_filter, envoy.ip_tagging, envoy.lua, envoy.rate_limit, envoy.router, envoy.squash [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.tracers: envoy.dynamic.ot, envoy.lightstep, envoy.tracers.datadog, envoy.tracers.opencensus, envoy.tracers.xray, envoy.zipkin [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.thrift_proxy.filters: envoy.filters.thrift.rate_limit, envoy.filters.thrift.router [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.access_loggers: envoy.file_access_log, envoy.http_grpc_access_log, envoy.tcp_grpc_access_log [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.dubbo_proxy.protocols: dubbo [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.udp_listeners: raw_udp_listener [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.dubbo_proxy.serializers: dubbo.hessian2 [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.filters.network: envoy.client_ssl_auth, envoy.echo, envoy.ext_authz, envoy.filters.network.dubbo_proxy, envoy.filters.network.kafka_broker, envoy.filters.network.local_ratelimit, envoy.filters.network.mysql_proxy, envoy.filters.network.rbac, envoy.filters.network.sni_cluster, envoy.filters.network.thrift_proxy, envoy.filters.network.zookeeper_proxy, envoy.http_connection_manager, envoy.mongo_proxy, envoy.ratelimit, envoy.redis_proxy, envoy.tcp_proxy [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.resolvers: envoy.ip [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.resource_monitors: envoy.resource_monitors.fixed_heap, envoy.resource_monitors.injected_resource [2020-02-19 18:29:15.232][7][info][main] [source/server/server.cc:255]   envoy.stats_sinks: envoy.dog_statsd, envoy.metrics_service, envoy.stat_sinks.hystrix, envoy.statsd [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.retry_priorities: envoy.retry_priorities.previous_priorities [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.clusters: envoy.cluster.eds, envoy.cluster.logical_dns, envoy.cluster.original_dst, envoy.cluster.static, envoy.cluster.strict_dns, envoy.clusters.aggregate, envoy.clusters.dynamic_forward_proxy, envoy.clusters.redis [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.retry_host_predicates: envoy.retry_host_predicates.omit_canary_hosts, envoy.retry_host_predicates.previous_hosts [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.filters.udp_listener: envoy.filters.udp_listener.udp_proxy [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.dubbo_proxy.filters: envoy.filters.dubbo.router [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.transport_sockets.upstream: envoy.transport_sockets.alts, envoy.transport_sockets.raw_buffer, envoy.transport_sockets.tap, envoy.transport_sockets.tls, raw_buffer, tls [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.transport_sockets.downstream: envoy.transport_sockets.alts, envoy.transport_sockets.raw_buffer, envoy.transport_sockets.tap, envoy.transport_sockets.tls, raw_buffer, tls [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.health_checkers: envoy.health_checkers.redis [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.dubbo_proxy.route_matchers: default [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.thrift_proxy.transports: auto, framed, header, unframed [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.thrift_proxy.protocols: auto, binary, binary/non-strict, compact, twitter [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.grpc_credentials: envoy.grpc_credentials.aws_iam, envoy.grpc_credentials.default, envoy.grpc_credentials.file_based_metadata [2020-02-19 18:29:15.233][7][info][main] [source/server/server.cc:255]   envoy.filters.listener: envoy.listener.http_inspector, envoy.listener.original_dst, envoy.listener.original_src, envoy.listener.proxy_protocol, envoy.listener.tls_inspector [2020-02-19 18:29:15.255][7][info][main] [source/server/server.cc:336] admin address: <IP_ADDRESS>:9901 [2020-02-19 18:29:15.261][7][info][main] [source/server/server.cc:455] runtime: layers:   name: base     static_layer:       {}  name: admin     admin_layer:       {} [2020-02-19 18:29:15.262][7][info][config] [source/server/configuration_impl.cc:62] loading 0 static secret(s) [2020-02-19 18:29:15.262][7][info][config] [source/server/configuration_impl.cc:68] loading 1 cluster(s) [2020-02-19 18:29:15.290][7][info][upstream] [source/common/upstream/cluster_manager_impl.cc:171] cm init: all clusters initialized [2020-02-19 18:29:15.290][7][info][config] [source/server/configuration_impl.cc:72] loading 1 listener(s) [2020-02-19 18:29:15.299][7][critical][main] [source/server/server.cc:94] error initializing configuration '/etc/front-envoy.yaml': Didn't find a registered implementation for name: 'envoy.filters.network.http_connection_manager' [2020-02-19 18:29:15.301][7][info][main] [source/server/server.cc:595] exiting Didn't find a registered implementation for name: 'envoy.filters.network.http_connection_manager'
[optional Relevant Links:]
https://www.envoyproxy.io/learn/on-your-laptop

I've found a way how to fix the issue. All *.yaml files in front-proxy should be updated:
envoy.filters.network.http_connection_manager replace with envoy.http_connection_manager
Same updated is needed at Dynamic Forward Proxy configuration page because the configuration listed will be failing due to the same issue: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/dynamic_forward_proxy_filter#config-http-filters-dynamic-forward-proxy
@mattklein123 Please make sure suggested fixes are pushed to your upcoming release / dev branches as these are blockers for people who want to start using Envoy.

@mattklein123 Please make sure suggested fixes are pushed to your upcoming release / dev branches as these are blockers for people who want to start using Envoy.

PRs appreciated. Unfortunately the learn documents are not really owned/updated right now as they are not covered by our sphinx doc build. cc @zuercher who has been working in this area.

envoy.filters.network.http_connection_manager is the new name and envoy.http_connection_manager is deprecated. It seems you're using an older version (though perhaps not by much) of Envoy that doesn't accept the new name. If you use the examples from the version you're building they should work.

@zuercher The issue is still in the most recent envoy image, but not in envoy-dev.

I'm kinda new to Envoy but I believe the issue is that those have to match:

https://github.com/envoyproxy/envoy/blob/v1.13.0/source/extensions/filters/network/well_known_names.h#L22
https://github.com/envoyproxy/envoy/blob/v1.13.0/api/envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#L29
and they don't.

Oh, and by the way, HTTP Connection Manager doesn't seems to be the only one affected, here's another random example:

https://github.com/envoyproxy/envoy/blob/v1.13.0/source/extensions/filters/http/well_known_names.h#L42
https://github.com/envoyproxy/envoy/blob/v1.13.0/api/envoy/extensions/filters/http/router/v3/router.proto#L19

Each extension has a name used in the build system. For example, envoy.filters.network.http_connection_manager.
Each extension has a separate defined name used in configuration. For many older filters, this configuration "well-known name" did not match the extension name. For example, the http connection manager's well-known-name was envoy.http_connection_manager. Newer filters were required to use the same extension name as their well-known name.
In a series of PRs I have modified all the canonical names for access loggers, http filters, network filters, listener filters, stats sinks and tracers so that their official well-known names match their extension names. The old names continue to work. Using the old names on the current master builds (and eventually in the 1.14.0 release) will generate log messages and increment the deprecated feature stat.
However, if you use the files in the examples from current master and use them with a version of Envoy that predates the changes I've described, you will get errors. The standardized well-known names are not used by the older releases of Envoy.
My recommendation is that you use the examples from the release of Envoy you're using. That means either:

Build envoy from master and use the examples from master, or
Use a release version of Envoy and the examples from the github tag for that release.

@zuercher that's exactly what I was doing, except that I was referring to the doc, not examples:

I see. That's turns out to be the reason I undertook the change -- so that we could correctly generate that line in the documentation.

.