Stopped working suddenly

Something has changed recently as I get this error now :

2020-04-19T06:43:37.0865452Z ##[section]Starting: Azure Web App
2020-04-19T06:43:37.1015155Z ==============================================================================
2020-04-19T06:43:37.1015609Z Task         : Azure Web App
2020-04-19T06:43:37.1015931Z Description  : Deploy an Azure Web App for Linux or Windows
2020-04-19T06:43:37.1016208Z Version      : 1.163.5
2020-04-19T06:43:37.1016457Z Author       : Microsoft Corporation
2020-04-19T06:43:37.1016793Z Help         : https://aka.ms/azurewebapptroubleshooting
2020-04-19T06:43:37.1017172Z ==============================================================================
2020-04-19T06:43:37.8682501Z Got service connection details for Azure App Service:'popayint'
2020-04-19T06:43:40.5090511Z Trying to update App Service Application settings. Data: {"WEBSITE_RUN_FROM_PACKAGE":"1"}
2020-04-19T06:43:40.5093215Z Deleting App Service Application settings. Data: ["WEBSITE_RUN_FROM_ZIP"]
2020-04-19T06:43:40.9467558Z App Service Application settings are already present.
2020-04-19T06:43:41.5305131Z Package deployment using ZIP Deploy initiated.
2020-04-19T06:44:42.2468404Z ##[error]Failed to deploy web package to App Service.
2020-04-19T06:44:42.2480169Z ##[error]To debug further please check Kudu stack trace URL<EMAIL_ADDRESS>2020-04-19T06:44:42.2481990Z ##[error]Error: Error: Failed to deploy web package to App Service. Internal Server Error (CODE: 500)
2020-04-19T06:44:42.4861453Z App Service Application URL: https://******.azurewebsites.net
2020-04-19T06:44:42.5174306Z ##[section]Finishing: Azure Web App

Before it was working well with these logs :

2020-04-15T17:46:06.9726894Z ##[section]Starting: Azure Web App
2020-04-15T17:46:06.9966372Z ==============================================================================
2020-04-15T17:46:06.9967029Z Task         : Azure Web App
2020-04-15T17:46:06.9967548Z Description  : Deploy an Azure Web App for Linux or Windows
2020-04-15T17:46:06.9968001Z Version      : 1.163.3
2020-04-15T17:46:06.9968437Z Author       : Microsoft Corporation
2020-04-15T17:46:06.9968937Z Help         : https://aka.ms/azurewebapptroubleshooting
2020-04-15T17:46:06.9969596Z ==============================================================================
2020-04-15T17:46:07.7429016Z Got service connection details for Azure App Service:'popayint'
2020-04-15T17:46:11.8637821Z Updating App Service Application settings. Data: {"WEBSITE_RUN_FROM_PACKAGE":"1"}
2020-04-15T17:46:11.8638750Z Deleting App Service Application settings. Data: ["WEBSITE_RUN_FROM_ZIP"]
2020-04-15T17:46:12.7653296Z Updated App Service Application settings and Kudu Application settings.
2020-04-15T17:46:22.5017745Z Package deployment using ZIP Deploy initiated.
2020-04-15T17:46:32.7451337Z Successfully deployed web package to App Service.
2020-04-15T17:46:32.7452090Z NOTE: Run From Package makes wwwroot read-only, so you will receive an error when writing files to this directory.
2020-04-15T17:46:34.7141037Z App Service Application URL: https://*******.azurewebsites.net
2020-04-15T17:46:34.7477598Z ##[section]Finishing: Azure Web App

The only thing that changed is the Azure Web App version from 1.163.3 to 1.163.5.
Is there anything I can do to help you resolve this ?
We can't deploy anymore

can you please check the status of your azure service? https://status.azure.com/status

The free Azure App service plan includes only 1Gb of disk space, and it was full, there was no warning anywhere, as I started to get error when I wanted to turn on logs, I knew something was wrong.
The error came from the disk space running out.
It there any option to clean up old zip in SitePackages directory ?

Please take a look at this link - https://stackoverflow.com/questions/58766693/azure-app-service-website-run-from-package-does-old-zip-files-gets-deleted

Can't find any way to delete old zip packages as the zip files are not in the wwwroot folder, there is no way to access the right folder using the proposed link.

Hi @Alexplose  Sorry for the delay in reply.
Please browse to ***.scm.azurewebsites.net
There you can see the option of using a debug console. Using the debug console you can navigate to home/data/SitePackages and manage your zip files.
Please let me know if this helps.

Yes that's what I'm doing right now, but I'd like to have this in my release pipeline, I'm in a continuous integration, and release are deployed often.

@Alexplose  Can you please confirm if you're using web deploy or zip deploy?
For web deploy we provide an option of cleaning additional files at the destination in the task itself.

I'm using zip deploy and I get zip files in my Site Packages folder along with a txt file pointing to the latest zip deployed, previous zip packages are still there using space.

Hi @Alexplose  The issue is there because you're using run from package. I can see that from the logs:

2020-04-15T17:46:07.7429016Z Got service connection details for Azure App Service:'popayint'
2020-04-15T17:46:11.8637821Z Updating App Service Application settings. Data: {"WEBSITE_RUN_FROM_PACKAGE":"1"}
2020-04-15T17:46:11.8638750Z Deleting App Service Application settings. Data: ["WEBSITE_RUN_FROM_ZIP"]

In this case yes we do not delete the zip packages from the sitePackages.

Ok but what can I add to my release pipeline to get them deleted? Any tasks, scripts? Seems I can't access this folder using kudo file system task.

@Alexplose  If you're deploying different packages every time and you want the previous packages to clean up you can deploy them to a slot. And delete that slot at the start of your pipeline during the next deployment.
You can use the Azure App Service Manage task to create/delete slots.
Please let me know if this helps.

Read more about slots here: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots
And more about the task here: https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureAppServiceManageV0/README.md

This seems to be a good solution, but I'm in a development process with a free F1 App service plan.
That's why my disk space is so limited.
Slots are not available in these plan.

@Alexplose  Nothing to worry about. Please try out the following steps and let me know if they work:

Clean your sitePackages folder before the deployment.
In the task please goto Additional Deployment Options and select Zip Deploy. You will see your folder will be mounted on wwwroot instead of sitePackages now.
For every further deployment it will replace the current folder in wwwroot and you won't have to clean the disk space every time you deploy.

This is working, as you described, the sitePackages folder is not used anymore, my package is now unzipped in the wwwroot folder.
Thanks for you help


Imgix 403 -> DOMException: Failed to execute 'toDataURL' on 'HTMLCanvasElement': Tainted canvases may not be exported.

Hello!
I have seen 403s start to pop up all over the admin side of the site, as imgix (when using nocache), is returning 403s. Nothing has changed in terms of my configuration, and the error that I am getting is DOMException: Failed to execute 'toDataURL' on 'HTMLCanvasElement': Tainted canvases may not be exported.
Does anyone have any experience with this error or any thoughts on how it could be fixed?

Hi @raymondtri!
We encountered this issue during the implementation of that component and resolved it using the crossOrigin attribute on the img tag but I know this can be picky. Maybe the cors setting on Imgix would help? https://support.imgix.com/hc/en-us/articles/360000537526-Cross-Domain-Policy


iwd: 0.8 -> 0.9

ver 0.9:
Fix issue with handling EAP-WSC passwords.
Add support for TTLS-CHAP and TTLS-PAP.
Add support for handling FT over SAE.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @Mic92

Hopefully they add matching subdomains of the radius server in WPA-EAP so I can use it someday in my university wifi.

@GrahamcOfBorg build iwd

Success on aarch64-linux (full log)
Attempted: iwd
Partial log (click to expand)
wrapping `/nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/bin/connect-network'...
shrinking RPATHs of ELF executables and libraries in /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9
shrinking /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/libexec/iwd
shrinking /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/bin/iwmon
shrinking /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/bin/iwctl
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/lib  /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/libexec  /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9/bin
patching script interpreter paths in /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9
checking for references to /build in /nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9...
/nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: iwd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: iwd
Partial log (click to expand)
wrapping `/nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/connect-network'...
shrinking RPATHs of ELF executables and libraries in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/libexec/iwd
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/iwctl
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/iwmon
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/lib  /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/libexec  /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin
patching script interpreter paths in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9
checking for references to /build in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9...
/nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9

Success on aarch64-linux (full log)
Attempted: iwd
Partial log (click to expand)
/nix/store/5ajlhpqmyxxkpvxnv6rhdac38hlf4bzl-iwd-0.9

Success on x86_64-linux (full log)
Attempted: iwd
Partial log (click to expand)
wrapping `/nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/monitor-ead'...
shrinking RPATHs of ELF executables and libraries in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/libexec/iwd
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/iwctl
shrinking /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin/iwmon
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/lib  /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/libexec  /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9/bin
patching script interpreter paths in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9
checking for references to /build in /nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9...
/nix/store/3ynm34azimrbrp7jp34kb0yjbnwgkyph-iwd-0.9


[Issue #87] - Make logging fully configurable via log4net

Addresses #87 and several other feature requests regarding logging subsystem (#182, #39, #61). Now everybody will be able to configure whatever he wants using the log4net logging mode.
Current implementation supports two modes:

Redirect STDERR/STDOUT to log4net (Info and Error logging levels)
Redirect STDERR/STDOUT to log4net AND configure all loggers (CLI, Wrapper log, Event log, STDOUT/STDERR) over a standard log4net configuration file

Mode 1: Redirect STDERR/STDOUT
  <log mode="log4net"/>

Mode 2: Full configuration via config file
  <log mode="log4net">
	<configPath>%BASE%\log4net.xml</configPath>
  </log>

TODOs:

[x] - First prototype
[ ] - rework PoC to have two separate logging mode names
[ ] - Get feedback from users and requesters
[ ] - Polish/refactor the implementation
[ ] - Documentation
[ ] - Functional tests

Test build will be available from AppVeyor. CC @aminjam , @roederja2 , @maurokade, @Randy1967, @pvandervelde

@oleg-nenashev I'm working with @aminjam and were not seeing the STDOUT/STDERR of the child process ran by winsw in the log4net logs - winsw's internal logs are present.  We are using log4net with the below configuration:
<?xml version="1.0"?>
<configuration>
  <log4net debug="true">
    <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender">
      <file value="log.log" />
      <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
      <appendToFile value="true" />
      <rollingStyle value="Size" />
      <maxSizeRollBackups value="5" />
      <maximumFileSize value="100KB" />
      <staticLogFileName value="true" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date %level - %message%newline" />
      </layout>
    </appender>
    <root>
      <level value="ALL" />
      <appender-ref ref="LogFileAppender" />
    </root>
  </log4net>
</configuration>

The process we are running simply prints to STDOUT and STDERR at roughly 1kb a second, so I don't think this is a buffering issue.  Any thoughts?

@charlievieth Maybe I just messed up something. It used to work with my infinite ping test app, but I will re-check just in case

@oleg-nenashev If you have a test log4net configuration that you would like us to test, we'd be happy to verify that. Is there anything else we should verify?

Can anybody update me on the status of this? I just tried logging="log4net" in my xml file but didn't have any luck. Is it working for anyone else? Is the commit ready to be merged just under need of review? I can try to do that if necessary. Please let me know your thoughts. Thanks.

@wayofthefuture generally it needs more testing feedback and more time from me to get it over the fence. I am pretty overloaded in other projects, but I hope to do it in the middle of September after Jenkins World and ORCONF. Any testing will be appreciated. If you want to make any changes, please feel free to create pull requests against the development branch

Good question.
This page in Jenkins pretty much reflects my current status (even missed this PR). It's usually my "next task to work on the weekend" and it slips down. Let me see if I can finally do something on this weekend. If not, I will try to decouple the task and describe the action items left


client is not blocking now, waits for polling config to set up the file.

After syncing offline, we've decided not to continue pursuing an async initialization method for now as the amount of effort and complexity might not be worth the effort. @pawels-optimizely I am gonna close this PR.


Also build on stable Rust 1.1.0

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks!


datum cli import coco and voc dataset error

My actions before raising this issue
I have installed CVAT on ubuntu 20.04 using the installation instructions.
(i did have a previous version of CVAT, but didnt get any errors while re-running installations instructions)
everything seems to work fine when starting a new dataset and playing around with the UI.
when trying the dataset import feature using cli datum I get an import error both with official pascal voc and official coco dataset.
Current Behaviour
i used the following commands
datum project import --format coco --input-path ~/Documents/datasets/coco/

output:
020-05-14 16:00:58,476 INFO: Importing project from '/home/kevin/Documents/datasets/coco/'
2020-05-14 16:00:58,476 INFO: Importing project as 'coco'
2020-05-14 16:00:58,790 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/captions_train2017.json'
2020-05-14 16:00:58,790 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/person_keypoints_train2017.json'
2020-05-14 16:00:58,790 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/instances_train2017.json'
2020-05-14 16:00:58,791 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/instances_val2017.json'
2020-05-14 16:00:58,791 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/captions_val2017.json'
2020-05-14 16:00:58,791 INFO: Found a dataset at '/home/kevin/Documents/datasets/coco/annotations/person_keypoints_val2017.json'
2020-05-14 16:00:58,791 INFO: Checking the dataset...
creating index...
index created!
creating index...
index created!
2020-05-14 16:01:13,823 ERROR: unhashable type: 'list'
Traceback (most recent call last):
  File "/home/kevin/.local/bin/datum", line 8, in <module>
    sys.exit(main())
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/cli/__main__.py", line 156, in main
    return args.command(args)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/cli/contexts/project/__init__.py", line 220, in import_command
    dataset = project.make_dataset()
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/project.py", line 765, in make_dataset
    return ProjectDataset(self)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/project.py", line 479, in __init__
    sources[s_name] = env.make_extractor(s_format,
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/project.py", line 274, in make_extractor
    return self.extractors.get(name)(*args, **kwargs)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/coco_format/extractor.py", line 244, in __init__
    super().__init__(path, **kwargs)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/coco_format/extractor.py", line 44, in __init__
    self._load_categories(loader)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/coco_format/extractor.py", line 79, in _load_categories
    person_kp_categories = self._load_person_kp_categories(loader)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/coco_format/extractor.py", line 103, in _load_person_kp_categories
    categories.add(label_id=label_id,
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/extractor.py", line 498, in add
    self.items[label_id] = self.Category(labels, set(adjacent))
TypeError: unhashable type: 'list'

datum project import --format voc --input-path ~/Documents/datasets/VOCdevkit/VOC2012/

output:
2020-05-14 16:00:02,955 INFO: Importing project from '/home/kevin/Documents/datasets/VOCdevkit/VOC2012/'
2020-05-14 16:00:02,955 INFO: Importing project as 'voc'
2020-05-14 16:00:02,956 INFO: Checking the dataset...
2020-05-14 16:00:09,686 ERROR: list index out of range
Traceback (most recent call last):
  File "/home/kevin/.local/bin/datum", line 8, in <module>
    sys.exit(main())
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/cli/__main__.py", line 156, in main
    return args.command(args)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/cli/contexts/project/__init__.py", line 220, in import_command
    dataset = project.make_dataset()
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/project.py", line 765, in make_dataset
    return ProjectDataset(self)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/components/project.py", line 509, in __init__
    for item in source:
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/voc_format/extractor.py", line 224, in __iter__
    anns = self._load_annotations(item_id)
  File "/home/kevin/.local/lib/python3.8/site-packages/datumaro/plugins/voc_format/extractor.py", line 266, in _load_annotations
    for a in label_cat.items[label_id].attributes
IndexError: list index out of range

Hi, thanks for the report. Could you specify which version of python you are using?

I am using python3.8, will make a venv of python3.6
To see if error changes when I am on pc

The same error occurs on python 3.5, 3.7 and 3.8.
btw i am using this from local install not the cvat docker container, not sure if that is required or not.

These problems should be fixed now.


docs: add governance and socials information

This PR adds a GOVERNANCE.md which is generated from the script files inside
of the governance/ folder.
A socials/ folder has also been added to list all of the places where
Catppuccin is available on various social media platforms.
This will allow programmatic retrieval of governance information and socials
information, ideally for the Catppuccin website.
A reminder what the GOVERNANCE.md file should be for:

A GOVERNANCE file lets people know about how your project is governed. For example, it might discuss project roles and how decisions are made.
- Supported file types - GitHub

Closes #8

make me core and then merge it


I am interested in using your game on my website. Could you add a license file like the MIT one in this pull request so I know how you want your software used?

MIT license was added.


Known issue with BLE for newcomers

Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

[X] I am running the latest version
[X] I checked the documentation and found no answer
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow or on our Gitter channel.

Question
Could we please pin somewhere on this repository issues/ the readme the known issues with ble, even not specific to this lib? This one for example concerns a lot of peoples imo but is hard to find, especially if you only test with a samsung: https://forum.developer.samsung.com/t/samsung-android-10-ble-connectivity-regression/509/75 When testing the library i was stuck because of that and thought it was the libraries' fault...

Also, don't use react-native 0.63.0...

Also, is not working for IOS. Just for Android

@nriccar Im using it on production on IOS. If you have any troubles just fill another issue please, the point of this question is not to list all difficulties you can have on installation but to ask for a list of KNOWN bugs to be accessible.

@CarbonC Its not actually a "difficulty", its an error. Polidea confirmed themselves. You do have a production IOS working code that is retrieving services and characteristics from an iPhone?
This is strange, since Polidea confirmed me that characteristics for IOS were not working. If you could share your package.json it would be really useful

@CarbonC Its not actually a "difficulty", its an error. Polidea confirmed themselves. You do have a production IOS working code that is retrieving services and characteristics from an iPhone?
This is strange, since Polidea confirmed me that characteristics for IOS were not working. If you could share your package.json it would be really useful

@nriccar Im using react native ble plx 2.0.0... But i dont think im actually retrieving characteristics or service from the remote device since I connect only to a hardware that is under my control and i know what is exposed. If characteristics scan is a known bug on IOS it clearly deserves to be on a list accessible without pm to Polidea...

@nriccar Where did they confirm this at? I was able to scan, discover and read from a characteristic on iOS with
...
"react-native": "~0.62.2",
"react-native-ble-plx": "^2.0.1"
...

They confirmed it via email and on a private call. I´ll check again, maybe its from my device, although the main engineer behind the libraries confirmed that he was aware of this issues..

i'm not getting updates for my monitorCharacteristicForService callback on iOS - should I try an older version of thelibrary? I'm on the most recent version.


flutter-win-2 is being quarantined with >1024 temp files

For the last few days, flutter-win-2 get quarantined each day with:

1024 files in TEMP (C:\Users\swarming\AppData\Local\Temp)

Rebooting the machine does not clear up temp files.
There seems to be a lot of empty temp dirs in that location.

Removed all dirs and files from the temp folder. Bot is back up.


Add a keybinding option in mobile

I play gd with your mod in ChromeOs but I can't customize the keys. it thinks its mobile so I need you to add it pls. this is a message for the developer.

add it pls


Rebaseline all performance tests

As a follow up to https://github.com/gradle/gradle/pull/17640

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


added ascii banner

added ASCII banner , an added a confirmation message when a new command is added.

can you specify where

console.log(
  chalk.blue(
    figlet.textSync("RUNN", {
      font: 'Cyberlarge'
    })
  )
);

like this

In all places actually. I  think we used single quotes initially. in yours changes I can see all are changed to double quotes. Could you match our existing coding style ?

changed to single quotes


Fix link in README.md

Fix broken link to the lexicon docs

same thing was merged here, but thank you! https://github.com/bluesky-social/feed-generator/pull/108


linking heatmap plot to other plots

description
ScottPlot Version: 4.1.15 (trunk)
Operating System: Win10
Application Type: WinForms
Question: I can't find the way how to link the heatmap to a plot of other type... if I understand correctly - currently it's not possible to change the Xaxis of the heatmap, is this true? My main aim is to be able to link the heatmap to other plot.. is this possible somehow? Maybe in beta?
code sample
In WinForms app I have 3 plots: candlesticks, bars, and heatmap.
I have followed the linking example:
        FormsPlots = new FormsPlot[] { formsPlot1, formsPlot2, formsPlot3 };
        foreach (var fp in FormsPlots)
            fp.AxesChanged += OnAxesChanged;

and slightly adjusted the code, so that only X-Axis would be in-sync:
    private void OnAxesChanged(object sender, EventArgs e)
    {
        FormsPlot changedPlot = (FormsPlot)sender;
        var newAxisLimits = changedPlot.Plot.GetAxisLimits();

        foreach (var fp in FormsPlots)
        {
            if (fp == changedPlot)
                continue;

            // disable events briefly to avoid an infinite loop
            fp.Configuration.AxesChangedEventEnabled = false;
            //fp.Plot.SetAxisLimits(newAxisLimits);
            fp.Plot.SetAxisLimitsX(newAxisLimits.XMin, newAxisLimits.XMax);
            fp.Render();
            fp.Configuration.AxesChangedEventEnabled = true;
        }
    }

without X-axis linking - result looks like this:

With linking - heatmap plot disappears to somewhere:

I think it's because heatmap has no physical x-axis that other plots could link to.. Any advices on how to solve the issue are highly appreciated.

Strangely, if I remove the "bar plot" from linking, then sync starts to work...

So 1 issue solved but then I have bar ploy sync issue.. Any advices?
For the sake of clarity attaching full reproducible code:
    public Form1()
    {
        InitializeComponent();

        int totalPoints = 60;

        var formsPlot = this.formsPlot1;
        var plt = formsPlot.Plot;
        OHLC[] prices = DataGen.RandomStockPrices(null, totalPoints);
        var candlePlot = plt.AddCandlesticks(prices);
        candlePlot.YAxisIndex = 0;

        var formsPlot2 = this.formsPlot2;
        var plt2 = formsPlot2.Plot;

        double[] values = DataGen.RandomNormal(0, totalPoints, 5, 10);
        double[] offsets = Enumerable.Range(0, values.Length)
            .Select(x =>
            {
                var val = values[x];
                if (val < 0)
                    return Math.Abs(val);
                return 0;
            })
            .ToArray();

        var bar = plt2.AddBar(values);
        bar.ValueOffsets = offsets;
        bar.FillColorNegative = Color.Red;
        bar.FillColor = Color.Green;
        bar.YAxisIndex = 1;

        // order books
        var formsPlot3 = this.formsPlot3;
        var plt3 = formsPlot3.Plot;

        int orderBookPointsTotal = 26;
        int orderBookPoints = orderBookPointsTotal / 2;
        var sellBooks = new double[orderBookPoints, totalPoints];
        var buyBooks = new double[orderBookPoints, totalPoints];
        var gapGeneratorRand = new Random(0);
        for (int i = 0; i < totalPoints; i++)
        {
            var singleBookVolumes = DataGen.Random(new Random(), orderBookPointsTotal);
            if (gapGeneratorRand.Next(2) == 1)
            {
                singleBookVolumes[10] = 0;
                singleBookVolumes[11] = 0;
                singleBookVolumes[12] = 0;
                singleBookVolumes[13] = 0;
                singleBookVolumes[14] = 0;
                singleBookVolumes[15] = 0;
            }

            for (int j = 0; j < orderBookPoints; j++)
                sellBooks[j, i] = singleBookVolumes[j];

            int idx = 0;
            for (int j = orderBookPoints; j < orderBookPointsTotal; j++)
                buyBooks[idx++, i] = singleBookVolumes[j];
        }

        double[,] data2D = { { 1, 2, 3 },
            { 4, 5, 6 } };

        var sellsHeatPlot = plt3.AddHeatmap(sellBooks, Colormap.Amp);
        //var sellsHeatPlotCb = plt3.AddColorbar(sellsHeatPlot);

        double[] buyOffsets = Enumerable.Range(0, values.Length)
            .Select(x => (double)-orderBookPoints)
            .ToArray();

        //var buysHeatPlot = plt3.AddHeatmap(buyBooks, Colormap.Algae);
        //buysHeatPlot.AxisOffsets = buyOffsets;

        FormsPlots = new FormsPlot[] { formsPlot1, formsPlot2, formsPlot3 }; // no heatmap
        //FormsPlots = new FormsPlot[] { formsPlot1, formsPlot3 }; // no bar chart
        foreach (var fp in FormsPlots)
            fp.AxesChanged += OnAxesChanged;
    }

    private FormsPlot[] FormsPlots;

    private void OnAxesChanged(object sender, EventArgs e)
    {
        FormsPlot changedPlot = (FormsPlot)sender;
        var newAxisLimits = changedPlot.Plot.GetAxisLimits();

        foreach (var fp in FormsPlots)
        {
            if (fp == changedPlot)
                continue;

            // disable events briefly to avoid an infinite loop
            fp.Configuration.AxesChangedEventEnabled = false;
            //fp.Plot.SetAxisLimits(newAxisLimits);
            fp.Plot.SetAxisLimitsX(newAxisLimits.XMin, newAxisLimits.XMax);
            fp.Render();
            fp.Configuration.AxesChangedEventEnabled = true;
        }
    }

A bonus question/feature request would be to add a configuration option for moving the "heatmap bar" outside of plot area. When you add a "bar" - essentially some of the plotting area is resized, so the synchronization ends up looing like this:

This is the latest experiment. Semi-successful. Seems like heatmap plot is living it's own life.. The axis are scaled differently. See gif.
    private void OnAxesChanged(object sender, EventArgs e)
    {
        FormsPlot changedPlot = (FormsPlot)sender;
        var newAxisLimits = changedPlot.Plot.GetAxisLimits();

        for (int i = 0; i < FormsCount; i++)
        {
            if (FormsPlots[i] == changedPlot)
                continue;
            FormsPlots[i].Configuration.AxesChangedEventEnabled = false;
        }

        for (int i = 0; i < FormsCount; i++)
        {
            if (FormsPlots[i] == changedPlot)
                continue;

            FormsPlots[i].Plot.SetAxisLimitsX(newAxisLimits.XMin, newAxisLimits.XMax);
            FormsPlots[i].Render();
        }

        foreach (var fp in FormsPlots)
        {
            if (fp == changedPlot)
                continue;
            fp.Configuration.AxesChangedEventEnabled = true;
        }
    }

The problem is that AddHeatmap() automatically calls AxisScaleLock(true) which automatically stretches the horizontal axis to force heatmap squares to always be square (not rectangular). You can disable this behavior with an optional argument when adding this plot type.
The idea that just adding a plottable to the plot changes axis behavior is a bit surprising... maybe this behavior should be disabled by default. @bclehmann may want to weigh-in here. Even though many people may want to constrain axes to maintain square tiles, the idea that adding a plot has other side effects may be unexpected and hard to troubleshoot.
Example
public Form1()
{
    InitializeComponent();
    formsPlot1.AxesChanged += FormsPlot1_AxesChanged;

    var prices = ScottPlot.DataGen.RandomStockPrices(new Random(0), 50);
    formsPlot1.Plot.AddCandlesticks(prices);

    double[,] data = ScottPlot.DataGen.Random2D(new Random(0), 10, 50);
    formsPlot2.Plot.AddHeatmap(data, lockScales: false); // <-- disable this behavior
}

private void FormsPlot1_AxesChanged(object sender, EventArgs e)
{
    var limits = formsPlot1.Plot.GetAxisLimits();
    formsPlot2.Plot.SetAxisLimitsX(limits.XMin, limits.XMax);
    formsPlot2.Render();
}


[WFLY-5458] Do not allow expressions for jgroup-stack and groups-channel attributes

These attributes may referenceother management resources (cf. WFLY-5189) and must not
allow expressions.
JIRA: https://issues.jboss.org/browse/WFLY-5458

Linux with security manager Build 3209 outcome was FAILURE using a merge of 191f500ddbfaf8c0a18b319c540c188ca23880e4
Summary: Tests failed: 2 (2 new), passed: 938, ignored: 297 Build time: 00:10:32
Failed tests
org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries(MigrateTestCase.java:134)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0085: Could not create a legacy-connection-factory based on connection-factory [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"connection-factory\" => \"InVmConnectionFactory\")
]. It used a HornetQ in-vm connector that is not compatible with Artemis in-vm connector ",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries(MigrateTestCase.java:129)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

Windows Build 3413 outcome was FAILURE using a merge of 191f500ddbfaf8c0a18b319c540c188ca23880e4
Summary: Tests failed: 2 (2 new), passed: 3188, ignored: 374 Build time: 00:57:11
Failed tests
org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries(MigrateTestCase.java:134)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0085: Could not create a legacy-connection-factory based on connection-factory [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"connection-factory\" => \"InVmConnectionFactory\")
]. It used a HornetQ in-vm connector that is not compatible with Artemis in-vm connector ",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries(MigrateTestCase.java:129)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

Linux Build 8376 outcome was FAILURE using a merge of 191f500ddbfaf8c0a18b319c540c188ca23880e4
Summary: Tests failed: 2 (2 new), passed: 3188, ignored: 374 Build time: 01:00:19
Failed tests
org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithLegacyEntries(MigrateTestCase.java:134)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0085: Could not create a legacy-connection-factory based on connection-factory [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"connection-factory\" => \"InVmConnectionFactory\")
]. It used a HornetQ in-vm connector that is not compatible with Artemis in-vm connector ",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries: java.lang.AssertionError: WFLYMSG0081: Migration failed, see results for more details.
	at org.jboss.as.model.test.ModelTestUtils.checkOutcome(ModelTestUtils.java:121)
	at org.jboss.as.subsystem.test.AbstractSubsystemTest.checkOutcome(AbstractSubsystemTest.java:206)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperation(MigrateTestCase.java:155)
	at org.jboss.as.messaging.test.MigrateTestCase.testMigrateOperationWithoutLegacyEntries(MigrateTestCase.java:129)
------- Stdout: -------
response = {
    "outcome" => "failed",
    "result" => {
        "migration-warnings" => [
            "WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0082: Classes providing the remoting-outgoing-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.",
            "WFLYMSG0083: Could not migrate the HA configuration of [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\")
]. Its shared-store and backup attributes holds expressions and it is not possible to determine unambiguously how to create the corresponding ha-policy for the messaging-activemq's server.",
            "WFLYMSG0084: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupC\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0084: Could not migrate attribute group-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"discovery-group\" => \"groupD\")
]. Use instead the socket-attribute to configure this discovery-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-address from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",
            "WFLYMSG0080: Could not migrate attribute local-bind-port from resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"broadcast-group\" => \"groupA\")
]. Use instead the socket-attribute to configure this broadcast-group.",

retest this please

Linux with security manager Build 3217 outcome was FAILURE using a merge of e69ba0a978593db39a3eb692ec4ef0f047f3c16b
Summary: Tests failed: 1, passed: 939, ignored: 297 Build time: 00:07:41
Failed tests
org.jboss.as.test.smoke.deployment.rar.tests.earmultirar.EarPackagedMultiRarDeploymentTestCase: 	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.ra.deployer.\"ear_packaged.ear#ear_packaged2.rar\".jboss.ironjacamar.resource" => "org.jboss.msc.service.StartException in service jboss.ra.deployer.\"ear_packaged.ear#ear_packaged2.rar\".jboss.ironjacamar.resource: Failed to start service
    Caused by: java.lang.NullPointerException"}}
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
	at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
	at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
	at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)
	at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144)
------- Stdout: -------
 [0m18:02:13,533 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0011: Unbound JCA AdminObject [java:jboss/Name3]
 [0m [0m18:02:13,540 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) WFLYUT0022: Unregistered web context: /servlet
 [0m [0m18:02:13,533 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:jboss/name1]
 [0m [0m18:02:13,640 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: complex_ij.rar) in 116ms
 [0m [0m18:02:13,640 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: servlet.war) in 116ms
 [0m [0m18:02:13,643 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment new.ear (runtime-name: new.ear) in 119ms
 [0m [0m18:02:13,650 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/smoke/target/jbossas/standalone/data/content/77/6fc78ecb474fc2f01fce7a961645169fba6b90/content
 [0m [0m18:02:13,651 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "new.ear" (runtime-name: "new.ear")
 [0m [0m18:02:13,772 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/smoke/target/jbossas/standalone/data/content/b2/fc25e1d9747b7e77f9facc852132de9f650ef4/content
 [0m [0m18:02:13,776 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "ear_packaged.ear" (runtime-name: "ear_packaged.ear")
 [0m [0m18:02:13,795 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ear_packaged.rar")
 [0m [0m18:02:13,796 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "ear_packaged2.rar")
 [0m [33m18:02:13,822 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ear_packaged.ear" is using a private module ("org.jboss.as.cli:main") which may be changed or removed in future versions without notice.
 [0m [33m18:02:13,822 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ear_packaged.ear" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [33m18:02:13,831 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ear_packaged.ear.ear_packaged2.rar" is using a private module ("org.jboss.as.cli:main") which may be changed or removed in future versions without notice.
 [0m [33m18:02:13,832 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ear_packaged.ear.ear_packaged.rar" is using a private module ("org.jboss.as.cli:main") which may be changed or removed in future versions without notice.
 [0m [33m18:02:13,832 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ear_packaged.ear.ear_packaged2.rar" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [33m18:02:13,832 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ear_packaged.ear.ear_packaged.rar" is using a private module ("org.wildfly.security.manager:main") which may be changed or removed in future versions without notice.
 [0m [0m18:02:13,839 INFO  [org.jboss.as.arquillian] (MSC service thread 1-1) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."ear_packaged.ear",unit=ear_packaged.ear,tests=[org.jboss.as.test.smoke.deployment.rar.tests.earmultirar.EarPackagedMultiRarDeploymentTestCase]]
 [0m [0m18:02:13,871 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:jboss/name3
 [0m [0m18:02:13,872 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0006: Registered admin object at java:jboss/Name5
 [0m [0m18:02:13,875 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:jboss/name2
 [0m [0m18:02:13,876 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0006: Registered admin object at java:jboss/Name4
 [0m [0m18:02:13,872 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020002: Deployed: file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/smoke/target/jbossas/standalone/tmp/vfs/deployment/deployment52ab398d91091262/ear_packaged.rar-57704de087483229/contents/
 [0m [0m18:02:13,877 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-4) IJ020002: Deployed: file:/opt/buildAgent/work/a31d203e70e89f90/testsuite/integration/smoke/target/jbossas/standalone/tmp/vfs/deployment/deployment52ab398d91091262/ear_packaged2.rar-f1b0d5600efbaced/contents/
 [0m [31m18:02:13,883 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.ra.deployer."ear_packaged.ear#ear_packaged2.rar".jboss.ironjacamar.resource: org.jboss.msc.service.StartException in service jboss.ra.deployer."ear_packaged.ear#ear_packaged2.rar".jboss.ironjacamar.resource: Failed to start service
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
	at org.jboss.as.connector.services.resourceadapters.IronJacamarActivationResourceService.start(IronJacamarActivationResourceService.java:196)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	... 3 more

:+1: Looks good to me.

Should the migrate op warn about this? The legacy subsystem allowed expressions on these.

The migrate op will fail if the legacy subsystem has expressions in it as the add operations for the new subsystem will not allow the expressions.
The user will then be able to "fix" the legacy subsystems by removing the expressions from there.

retest this please

Windows Build 3608 outcome was FAILURE using a merge of e69ba0a978593db39a3eb692ec4ef0f047f3c16b
Summary: Tests failed: 2 (2 new), passed: 3179, ignored: 370 Build time: 01:10:09
Failed tests
org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite: org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainDeployment630TestCase: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.awaitServers(DomainLifecycleUtil.java:442)
	at org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil.start(DomainLifecycleUtil.java:244)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startAndAdjust(MixedDomainTestSupport.java:105)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:76)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:78)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:57)
	at org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite.initializeDomain(MixedDomain630TestSuite.java:44)
	at org.jboss.as.test.integration.domain.mixed.eap630.MixedDomainDeployment630TestCase.beforeClass(MixedDomainDeployment630TestCase.java:38)
------- Stdout: -------
05:25:30,793 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
05:25:31,134 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 05:25:31,771 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
[Host Controller] 05:25:32,076 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
[Host Controller] 05:25:32,147 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.CR4-SNAPSHOT (WildFly Core 2.0.0.CR7) starting
[Host Controller] 05:25:33,020 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.3.2.Final
[Host Controller] 05:25:33,020 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 05:25:33,029 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.2.Final
[Host Controller] 05:25:33,085 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.14.Final
[Host Controller] 05:25:33,120 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 05:25:34,940 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9990/management
[Host Controller] 05:25:34,940 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
[Host Controller] 05:25:34,940 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR4-SNAPSHOT (WildFly Core 2.0.0.CR7) (Host Controller) started in 3662ms - Started 43 of 46 services (13 services are lazy, passive or on-demand)
INFO  [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] HostController started in 4756 ms
[Host Controller] 05:25:37,144 WARN  [org.jboss.as.messaging] (management-handler-thread - 3) WFLYMSG0071: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!
[Host Controller] 05:25:37,145 WARN  [org.jboss.as.messaging] (management-handler-thread - 3) WFLYMSG0072: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!
[Host Controller] 05:25:38,668 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 3) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 05:25:39,305 INFO  [org.jboss.as.controller.management-deprecated] (management-handler-thread - 4) WFLYCTL0028: Attribute 'stack' in the resource at address '/' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 05:25:39,431 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: WildFly Full 10.0.0.CR4-SNAPSHOT (WildFly Core 2.0.0.CR7) stopped in 27ms
[Host Controller] 05:25:39,434 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 10.0.0.CR4-SNAPSHOT (WildFly Core 2.0.0.CR7) starting
[Host Controller] 05:25:39,459 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0003: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 05:25:39,503 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on [::1]:9999
[Host Controller] 05:25:39,622 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/profile=full-ha/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
[Host Controller] 05:25:39,759 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server server-one
05:25:39,774 INFO  [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:server-one'
[Server:server-one] 05:25:40,440 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
[Server:server-one] 05:25:40,713 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
[Server:server-one] 05:25:40,919 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.CR4-SNAPSHOT (WildFly Core 2.0.0.CR7) starting
[Server:server-one] 05:25:41,029 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.3.2.Final
[Server:server-one] 05:25:41,040 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.2.Final
[Server:server-one] 05:25:41,091 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.14.Final
[Host Controller] 05:25:42,018 INFO  [org.jboss.as.host.controller] (Remoting "master:MANAGEMENT" task-14) WFLYHC0021: Server [Server:server-one] connected using connection [Channel ID 36c27178 (inbound) of Remoting connection 019ac7f0 to /0:0:0:0:0:0:0:1:65435]
[Host Controller] 05:25:42,045 ERROR [org.jboss.as.controller.management-operation] (server-registration-threads - 1) WFLYCTL0013: Operation ("describe") failed - address: ([
[Host Controller]     ("profile" => "full-ha"),
[Host Controller]     ("subsystem" => "web")
[Host Controller] ]) - failure description: "WFLYCTL0309: Legacy extension 'org.jboss.as.web' is not supported on servers running this version. The extension is only supported for use by hosts running a previous release in a mixed-version managed domain"
[Host Controller] 05:25:42,047 ERROR [org.jboss.as.controller.management-operation] (server-registration-threads - 1) WFLYCTL0013: Operation ("register-server") failed - address: ([]): java.lang.RuntimeException: WFLYHC0056: Failed to retrieve profile operations from domain controller
[Host Controller] 	at org.jboss.as.host.controller.DomainModelControllerService.getProfileOperations(DomainModelControllerService.java:448)
[Host Controller] 	at org.jboss.as.host.controller.ManagedServerOperationsFactory.addSubsystems(ManagedServerOperationsFactory.java:729)
[Host Controller] 	at org.jboss.as.host.controller.ManagedServerOperationsFactory.getBootUpdates(ManagedServerOperationsFactory.java:244)
[Host Controller] 	at org.jboss.as.host.controller.ManagedServerOperationsFactory.createBootUpdates(ManagedServerOperationsFactory.java:175)

org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite: java.lang.AssertionError: expected:<EAP_6_3_0> but was:<EAP_6_4_0>
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getVersion(MixedDomainTestSuite.java:43)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:65)
	at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:57)
	at org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite.initializeDomain(MixedDomain640TestSuite.java:44)

retest this please


Move mozjs from buildbot to travis.

Running in production

@bors-servo r+

Reviewed 1 of 1 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

:pushpin: Commit 657b253 has been approved by metajack

:hourglass: Testing commit 657b253 with merge ff698f1...

:sunny: Test successful - travis


Samples/ExplorerUI bugs

Reported by @neoxeo
controls not change when Windows size change
color of background is not good after expand/reduce if windows size have changed

I improved ExplorerUI sample, so we can close this issue


Can't get it to start in a Phoenix project

From the examples it's not clear to me how to start Honeydew in a phoenix project, in any point where I try to add the start up code I get this error:
no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started

I tried placing it in the existing Application.start/2 method, in a GenServer module inside of the supervision tree of the existing Application, I always get that error, could you point me in the right direction please?

Hey there,
Could you show me the following?

Your project's deps
How you're starting the queue
How you're starting the workers
How you're enqueuing jobs

closing due to inactivity, please let me know if you still need help!


Calico pods in newly launched HA microk8s cluster stuck in CrashLoopBackoff

Ubuntu 20.04 LTS (ARM64)
Microk8s 1.19 (1669)
Kernel 5.6.0-1137-ayufan-ge57f05e7bf8f
When launching a new microk8s cluster on the 1.19 stable channel of microk8s, Calico does not enter a ready state when adding three HA nodes. Testing previously on the latest/edge/ha-preview channel did not show this same behaviour on the same systems. I have removed microk8s and reinstalled it freshly, bootstrapping a new 3 node cluster each time, and have been able to reproduce this behaviour.
node1,2 & 3: sudo snap install microk8s --channel 1.19/stable --classic
node1,2,3: -
microk8s status
microk8s is running
high-availability: no
  datastore master nodes: <IP_ADDRESS>:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    ingress              # Ingress controller for external access
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    storage              # Storage class; allocates storage from host directory

node1: microk8s add-node
node2: microk8s join <IP_ADDRESS>:25000/<x>
node1: microk8s add-node (before, or after node2 is finished adding shows the same behaviour)
node3: microk8s join <IP_ADDRESS>:25000/<y> (again, before, or after node2 is finished adding shows the same behaviour)
node1, node2, node3: -
microk8s status
microk8s is running
high-availability: yes
  datastore master nodes: <IP_ADDRESS>:19001 <IP_ADDRESS>:19001 <IP_ADDRESS>:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    ingress              # Ingress controller for external access
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    storage              # Storage class; allocates storage from host directory

No calico nodes enter healthy state, stuck in CrashLoopBackoff -
microk8s kubectl get all -A
NAMESPACE     NAME                                          READY   STATUS              RESTARTS   AGE
kube-system   pod/calico-kube-controllers-847c8c99d-nv86p   0/1     ContainerCreating   0          14m
kube-system   pod/calico-node-pn6wj                         0/1     CrashLoopBackOff    6          11m
kube-system   pod/calico-node-9sfmr                         0/1     CrashLoopBackOff    6          10m
kube-system   pod/calico-node-2l7pv                         0/1     Running             0          19s

NAMESPACE   NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
default     service/kubernetes   ClusterIP   <IP_ADDRESS>   <none>        443/TCP   14m

NAMESPACE     NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/calico-node   3         3         0       3            0           kubernetes.io/os=linux   14m

NAMESPACE     NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/calico-kube-controllers   0/1     1            0           14m

NAMESPACE     NAME                                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/calico-kube-controllers-847c8c99d   1         1         0       14m

microk8s kubectl logs -f pod/calico-node-2l7pv -n kube-system
2020-09-08 12:17:16.514 [INFO][9] startup.go 290: Early log level set to info
2020-09-08 12:17:16.514 [INFO][9] startup.go 306: Using NODENAME environment for node name
2020-09-08 12:17:16.514 [INFO][9] startup.go 318: Determined node name: melchior.gaia
2020-09-08 12:17:16.518 [INFO][9] startup.go 350: Checking datastore connection
2020-09-08 12:17:16.566 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:17.620 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:18.667 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:19.705 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:20.756 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:21.806 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:22.858 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host
2020-09-08 12:17:23.958 [INFO][9] startup.go 365: Hit error connecting to datastore - retry error=Get https://<IP_ADDRESS>:443/api/v1/nodes/foo: dial tcp <IP_ADDRESS>:443: connect: no route to host

Name:                 calico-node-9sfmr
Namespace:            kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-node-critical
Node:                 balthasar.gaia/<IP_ADDRESS>
Start Time:           Tue, 08 Sep 2020 12:05:55 +0000
Labels:               controller-revision-hash=679986bc67
                      k8s-app=calico-node
                      pod-template-generation=2
Annotations:          scheduler.alpha.kubernetes.io/critical-pod:
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/calico-node
Init Containers:
  upgrade-ipam:
    Container ID:  containerd://f552f728a11b2841aa6b2db28d26eed10c61808a1da5a8e85e748a7b831ea346
    Image:         calico/cni:v3.13.2
    Image ID:      docker.io/calico/cni@sha256:bbf7e3ac3f80d0a356a6c27b095bd313d1106f8ed84f85850816ed79295843c1
    Port:          <none>
    Host Port:     <none>
    Command:
      /opt/cni/bin/calico-ipam
      -upgrade
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 08 Sep 2020 12:05:56 +0000
      Finished:     Tue, 08 Sep 2020 12:05:56 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      KUBERNETES_NODE_NAME:        (v1:spec.nodeName)
      CALICO_NETWORKING_BACKEND:  <set to the key 'calico_backend' of config map 'calico-config'>  Optional: false
    Mounts:
      /host/opt/cni/bin from cni-bin-dir (rw)
      /var/lib/cni/networks from host-local-net-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from calico-node-token-l6vc2 (ro)
  install-cni:
    Container ID:  containerd://65e3e9bf7133b22ef8c4c116ff00cdf5056337c76426accdab9ed0b48612dce2
    Image:         calico/cni:v3.13.2
    Image ID:      docker.io/calico/cni@sha256:bbf7e3ac3f80d0a356a6c27b095bd313d1106f8ed84f85850816ed79295843c1
    Port:          <none>
    Host Port:     <none>
    Command:
      /install-cni.sh
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 08 Sep 2020 12:05:57 +0000
      Finished:     Tue, 08 Sep 2020 12:05:58 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      CNI_CONF_NAME:         10-calico.conflist
      CNI_NETWORK_CONFIG:    <set to the key 'cni_network_config' of config map 'calico-config'>  Optional: false
      KUBERNETES_NODE_NAME:   (v1:spec.nodeName)
      CNI_MTU:               <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      SLEEP:                 false
      CNI_NET_DIR:           /var/snap/microk8s/current/args/cni-network
    Mounts:
      /host/etc/cni/net.d from cni-net-dir (rw)
      /host/opt/cni/bin from cni-bin-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from calico-node-token-l6vc2 (ro)
Containers:
  calico-node:
    Container ID:   containerd://4461881bfcf4698c394e2f5996836d4eebfea1bf66fdc9427e679e3e51e6ebe5
    Image:          calico/node:v3.13.2
    Image ID:       docker.io/calico/node@sha256:cb9dea7b86471c71925ae318f7c60af72d9ddf1dab0fe2029832a671b83bba6a
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Tue, 08 Sep 2020 12:18:19 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Tue, 08 Sep 2020 12:14:18 +0000
      Finished:     Tue, 08 Sep 2020 12:15:27 +0000
    Ready:          False
    Restart Count:  7
    Requests:
      cpu:      250m
    Liveness:   exec [/bin/calico-node -felix-live] delay=10s timeout=1s period=10s #success=1 #failure=6
    Readiness:  exec [/bin/calico-node -felix-ready] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      DATASTORE_TYPE:                     kubernetes
      WAIT_FOR_DATASTORE:                 true
      NODENAME:                            (v1:spec.nodeName)
      CALICO_NETWORKING_BACKEND:          <set to the key 'calico_backend' of config map 'calico-config'>  Optional: false
      CLUSTER_TYPE:                       k8s,bgp
      IP:                                 autodetect
      IP_AUTODETECTION_METHOD:            can-reach=<IP_ADDRESS>
      CALICO_IPV4POOL_VXLAN:              Always
      FELIX_IPINIPMTU:                    <set to the key 'veth_mtu' of config map 'calico-config'>  Optional: false
      CALICO_IPV4POOL_CIDR:               <IP_ADDRESS>/16
      CALICO_DISABLE_FILE_LOGGING:        true
      FELIX_DEFAULTENDPOINTTOHOSTACTION:  ACCEPT
      FELIX_IPV6SUPPORT:                  false
      FELIX_LOGSEVERITYSCREEN:            error
      FELIX_HEALTHENABLED:                true
    Mounts:
      /lib/modules from lib-modules (ro)
      /run/xtables.lock from xtables-lock (rw)
      /var/lib/calico from var-lib-calico (rw)
      /var/run/calico from var-run-calico (rw)
      /var/run/nodeagent from policysync (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from calico-node-token-l6vc2 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  lib-modules:
    Type:          HostPath (bare host directory volume)
    Path:          /lib/modules
    HostPathType:
  var-run-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/var/run/calico
    HostPathType:
  var-lib-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/var/lib/calico
    HostPathType:
  xtables-lock:
    Type:          HostPath (bare host directory volume)
    Path:          /run/xtables.lock
    HostPathType:  FileOrCreate
  cni-bin-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/opt/cni/bin
    HostPathType:
  cni-net-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/args/cni-network
    HostPathType:
  host-local-net-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/var/lib/cni/networks
    HostPathType:
  policysync:
    Type:          HostPath (bare host directory volume)
    Path:          /var/snap/microk8s/current/var/run/nodeagent
    HostPathType:  DirectoryOrCreate
  flexvol-driver-host:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds
    HostPathType:  DirectoryOrCreate
  calico-node-token-l6vc2:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  calico-node-token-l6vc2
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  kubernetes.io/os=linux
Tolerations:     :NoScheduleop=Exists
                 :NoExecuteop=Exists
                 CriticalAddonsOnly op=Exists
                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                 node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists
                 node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                 node.kubernetes.io/unreachable:NoExecute op=Exists
                 node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                     From                     Message
  ----     ------     ----                    ----                     -------
  Normal   Scheduled  12m                                              Successfully assigned kube-system/calico-node-9sfmr to balthasar.gaia
  Normal   Pulled     12m                     kubelet, balthasar.gaia  Container image "calico/cni:v3.13.2" already present on machine
  Normal   Created    12m                     kubelet, balthasar.gaia  Created container upgrade-ipam
  Normal   Started    12m                     kubelet, balthasar.gaia  Started container upgrade-ipam
  Normal   Pulled     12m                     kubelet, balthasar.gaia  Container image "calico/cni:v3.13.2" already present on machine
  Normal   Created    12m                     kubelet, balthasar.gaia  Created container install-cni
  Normal   Started    12m                     kubelet, balthasar.gaia  Started container install-cni
  Normal   Pulled     12m                     kubelet, balthasar.gaia  Container image "calico/pod2daemon-flexvol:v3.13.2" already present on machine
  Normal   Created    12m                     kubelet, balthasar.gaia  Created container flexvol-driver
  Normal   Started    12m                     kubelet, balthasar.gaia  Started container flexvol-driver
  Normal   Pulled     12m                     kubelet, balthasar.gaia  Container image "calico/node:v3.13.2" already present on machine
  Normal   Created    12m                     kubelet, balthasar.gaia  Created container calico-node
  Normal   Started    12m                     kubelet, balthasar.gaia  Started container calico-node
  Warning  Unhealthy  11m (x6 over 12m)       kubelet, balthasar.gaia  Liveness probe failed: calico/node is not ready: Felix is not live: Get http://localhost:9099/liveness: dial tcp [::1]:9099: connect: connection refused
  Normal   Killing    11m                     kubelet, balthasar.gaia  Container calico-node failed liveness probe, will be restarted
  Warning  Unhealthy  7m51s (x30 over 12m)    kubelet, balthasar.gaia  Readiness probe failed: calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: dial tcp [::1]:9099: connect: connection refused
  Warning  BackOff    2m43s (x12 over 5m54s)  kubelet, balthasar.gaia  Back-off restarting failed container

inspection-report-20200908_122206.tar.gz

It can be related to this issue https://github.com/ubuntu/microk8s/issues/1511
Care to try latest/edge channel, there was a fix to address the that issue.

Hi @devec0  this maybe something introduced in 1.19.
I can see that it seems to be trying to use ipv6.
See this issue #1549 and how it was resolved. Is it something that you can try?

Hi @devec0,
What can you tell me about the kernel you use? I see that kube-proxy cannot load a module:
Sep 08 12:05:28 balthasar.gaia microk8s.daemon-proxy[1129352]: + modprobe br_netfilter
Sep 08 12:05:28 balthasar.gaia microk8s.daemon-proxy[1129594]: modprobe: FATAL: Module br_netfilter not found in directory /lib/modules/5.6.0-1137-ayufan-ge57f05e7bf8f

Could you make sure this module is loaded?

I did end up trying the latest edge channel, and got the same result.
I indeed suspect this could be kernel related. I'd not noticed the br_netfilter message, and the more I read, the more that module seems to be required by several components in K8S. I'm in the process of rebuilding the kernel for this device (RockPro64) to include the standard Ubuntu modules and will report back once tested.

OK, so, I think this can be closed out. I do think there is some opportunity to add something to the documentation around required kernel modules and configuration, as I've tried several permutations of different kernel versions and kernel builds using the standard Ubuntu kernel configuration file for ARM64, and have finally found a version and configuration that works. Unsurprisingly, the default Ubuntu kernel configuration file produces an ARM64 kernel on the 5.4.x focal kernels which works with microk8s ha-cluster, on the 1.19 version. Stepping outside of these constraints, and thar be dragons.
In summary, I observed that the issue was resolved by using the 1.19/stable channel, the standard Ubuntu focal 5.4 kernel from kernel.ubuntu.com git, compiled with the default Ubuntu kernel configuration for ARM64. I can confirm that this configuration does include br_netfilter, including all of the kernel modules listed in the Calico requirements documentation.
As an interesting aside, the HWE-5.8 kernel was tested, but exhibited some strange failure modes on bringing up microk8s ha-clustering, so I decided to go back to the the 5.4 branch and recompile. This is probably worth being aware of for future HWE testing, once that kernel is released, as I noted issues in bringing up the apiserver, which inevitably caused microk8s to fail during ha-cluster bootstrap. This could either be related to the standard HWE-5.8 kernel config or some breaking change in 5.8 - If I see that again, I'll open a separate issue.
As an additional note, but also noting that latest/edge is under active development, the current latest/edge does seem to also have an issue during ha-cluster bringup, even on the working kernel configuration I mentioned (5.4 + standard ARM64 Ubuntu kernel configuration) but it was not related to this issue as far as I can tell. In my testing on latest/edge, I found I had to go back to 1.19 on each kernel I tested, and was only able to get working ha-cluster once I switched back to 1.19/stable. The apiserver would simply fail whilst applying CNI configuration, nothing stood out in the logs. Also, if I hit this again during future upgrades, I'll be sure to file another issue.
For the sake of completeness:
microk8s kubectl get all -A
NAMESPACE     NAME                                          READY   STATUS    RESTARTS   AGE
kube-system   pod/calico-node-ztxlv                         1/1     Running   0          14m
kube-system   pod/calico-kube-controllers-847c8c99d-chpkf   1/1     Running   1          16m
kube-system   pod/calico-node-m6rw2                         1/1     Running   0          13m
kube-system   pod/calico-node-jvz9r                         1/1     Running   0          13m

NAMESPACE   NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE
default     service/kubernetes   ClusterIP   <IP_ADDRESS>   <none>        443/TCP   16m

NAMESPACE     NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/calico-node   3         3         3       3            3           kubernetes.io/os=linux   16m

NAMESPACE     NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/calico-kube-controllers   1/1     1            1           16m

NAMESPACE     NAME                                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/calico-kube-controllers-847c8c99d   1         1         1       16m

microk8s status
microk8s is running
high-availability: yes
  datastore master nodes: <IP_ADDRESS>:19001 <IP_ADDRESS>:19001 <IP_ADDRESS>:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    ingress              # Ingress controller for external access
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    storage              # Storage class; allocates storage from host directory


CMake: use _WINDLL rather than _USRDLL

_USRDLL is used to indicate that you are building a MFC DLL while
_WINDLL is specified for ALL DLL builds.  Use the correct macro.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test and merge

@swift-ci please smoke test Linux platform

@swift-ci please smoke test Linux platform


27 create a initial community using gitter

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.62%. Comparing base (965b4ed) to head (2fa9dc8).
Report is 2 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
+ Coverage   33.33%   39.62%   +6.28%
==========================================
  Files           3        3
  Lines         159      159
==========================================
+ Hits           53       63      +10
+ Misses        106       96      -10

Flag
Coverage Δ

unittests
39.62% <ø> (+6.28%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.