Windows Support

I attempted to enable NextLS via the VSCode Extension, however the client was not created.
The first question is, in a general sense, is NextLS viable in windows?
If NextLS supports windows, but the initialization script is unsupported in windows, then there is an issue packaging and initializing it for windows users of VSCode.

Trying to use NextLS in WSL:
[Error - 9:56:36 PM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 9:56:36 PM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:96701)
	at _.stop (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:96282)
	at _.stop (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/cmo/.vscode-server/extensions/elixir-tools.elixir-tools-0.3.0/dist/extension.js:2:102789)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)

Trying to use NextLS on Windows:
[Error - 9:58:50 PM] NextLS client: couldn't create connection to server.
Launching server using command c:\Users\simon\scoop\apps\vscode\1.80.1\data\extensions\elixir-tools.elixir-tools-0.3.0\bin\nextls failed. Error: spawn c:\Users\simon\scoop\apps\vscode\1.80.1\data\extensions\elixir-tools.elixir-tools-0.3.0\bin\nextls ENOENT

windows is very weird, when dealing with dev tools.

I now have windows binaries uploaded to the releases, but I still use a bash script so I'll need to convert that to a bat script or might not need it at all.
Should be good to test on windows after that

https://github.com/elixir-tools/next-ls/pull/144 - now that binaries are getting downloaded - will it work in WSL?

I can confirm that on WSL2, with Ubuntu 22.04, it is working. It downloaded the executable.
Thanks a lot. BTW, I am a big fan of your Temple library.
One question: what is the correct place for the code completion of definitions? I mean - when you type defmodule or def end automatically appearing. In this extension or code snippets?

Completions are not implemented yet, but are coming up soon on the roadmap.

BTW, I am a big fan of your Temple library.

That's awesome to hear! The https://www.elixir-tools.dev is built with Temple.
marking this comment as off topic tho, to keep the issue focused. You can open a github discussion on the Org for general questions or join the discord invite link

Hey friends, tried installing it on windows and getting:
2023-11-01 12:45:45.869 [error] Error: Download failed (https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64, status=404)
    at c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:432487
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at l.force (c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:432228)
    at c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:431445
    at e.activate (c:\Users\serafeim\.vscode\extensions\elixir-tools.elixir-tools-0.11.0\dist\extension.js:2:430807)
    at v.n (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:6205)
    at v.m (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:6168)
    at v.l (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:125:5625)
2023-11-01 12:49:48.601 [info] ExtensionService#_doActivateExtension vscode.simple-browser, startup: false, activationEvent: 'onOpenExternalUri:https'

Plase notice that the correct filename is next_ls_windows_amd64.exe !

Yes, like @spapas mentioned
2024-01-19 09:20:06.744 [info] ExtensionService#_doActivateExtension elixir-tools.elixir-tools, startup: false, activationEvent: 'onLanguage:elixir'
2024-01-19 09:20:10.850 [error] Activating extension elixir-tools.elixir-tools failed due to an error:
2024-01-19 09:20:10.850 [error] Error: Download failed (https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64, status=404)
    at c:\Users\chgeuer\.vscode\extensions\elixir-tools.elixir-tools-0.12.1\dist\extension.js:2:432487
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Tool tries to fetch https://github.com/elixir-tools/next-ls/releases/latest/download/next_ls_windows_amd64
Correct (I guess) would be https://github.com/elixir-tools/next-ls/releases/download/latest/next_ls_windows_amd64.exe

I'll try and get windows installed today and try it out.
Sorry about that!

My frustration in the question is more about - It was working earlier - not working now - what did I miss?
I installed lexical-vscode package and it shows a message that it is downloading lexical executable. I am not getting the same message with elixir-tools.vscode package. Problem might be mostly there. Unable to overwrite older version?
Thinking aloud... if it helps.

It was working earlier - not working now - what did I miss?

There is a bug in the auto updater that I fixed yesterday, but if you delete Next LS and reopen VSCode, it should prompt you to install it.
I just tested on my Mac and it worked, so I'm not really sure what is different about running VSCode on Windows using WSL2, which will require me to install and debug.

You are doing amazing work. We should be thankful - you should not be sorry!

🙇

That updater is in 0.19.1 and that is not yet released?
I tried reinstalling.

Removed elixir-tools.vscode from vscode
rm -rf ~/.cache/elixir-tools
Restart vscode
Install elixir-tols.vscode
Even on restart, it is not prompting to download. Socket Closed is the message in Output window.

Windows 11. WSL2 - Ubuntu 22.04

Thanks, downloading as ISO now

Okay, sort of bad-ish news...
Works on my machine 😅.
Link to a video recording of me installing the extension for the first time: https://f005.backblazeb2.com/file/elixir-tools/elixir-tools-wsl-test.mp4
Timeline is basically

install extension
it doesn't work because i hadn't restarted vscode since installing elixir, so it wasn't in the path
restart, it fails because i had never run mix local.hex --force on this elixir install
i run that and restart
it boots and prompts me to install deps, i click yes (this is a new feature in 0.19.1)
it installs them and then continues on and works as expected

Thanks. You took a lot of effort. One difference I could spot is - you are using nix for everything - and - I am using asdf for elixir. Not sure if it makes any difference.
Another thing to ponder is the burrito file is not there in the local/.hex folder.
I guess some caching somewhere in my system with the old version and is not getting deleted.
I will come back to you when I find something. Till then, please ignore this and move on.
Again, thanks a lot for the prompt response and huge time you put in.

it did actually crash after i let it sit there for a minute, investigating that now, but seems orthogonal to your issue.
I don't think asdf vs nix will make a difference for yours not even prompting you to install it

Another thing to ponder is the burrito file is not there in the local/.hex folder.

i'm not sure what you mean here

I guess some caching somewhere in my system with the old version and is not getting deleted.

you can uninstall from the command palette (search elixir tools and it will be there), then restart to see if it prompts you to download

Till then, please ignore this and move on.

no 😎

Interestingly, when I try to uninstall from the command palette, it gives an error message that Failed to uninstall NextLS from nextls

However, when I uninstall from Extensions tab, it is getting removed without any warnings/notices.

Does that trigger anything?

Hmm, could you audit your settings to see what the value of elixir-tools.nextLS.installationDirectory is?

Can you confirm is that directory exists at all?

No. The directory does not exist.

As an experiment, can you manually create that directory and then restart VScode to see if it tries to install it?

No. nothing happened. This is the full error log.
[Error - 1:27:21 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:21 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:21 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:21 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Info  - 1:27:21 AM] Connection to server got closed. Server will restart.
true
[Error - 1:27:21 AM] Server initialization failed.
  Message: Socket closed before the connection was established
  Code: -32099
[Error - 1:27:21 AM] NextLS client: couldn't create connection to server.
  Message: Socket closed before the connection was established
  Code: -32099
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: startFailed
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: startFailed
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] NextLS client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] Restarting server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Info  - 1:27:22 AM] Connection to server got closed. Server will restart.
true
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] NextLS client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] Restarting server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Info  - 1:27:22 AM] Connection to server got closed. Server will restart.
true
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] NextLS client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] Restarting server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Info  - 1:27:22 AM] Connection to server got closed. Server will restart.
true
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Client NextLS: connection to server is erroring. Shutting down server.
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
	at _.shutdown (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96701)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:96282)
	at _.stop (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:258296)
	at _.handleConnectionError (/home/krishna/.vscode-server/extensions/elixir-tools.elixir-tools-0.13.0/dist/extension.js:2:102789)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 1:27:22 AM] Server initialization failed.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] NextLS client: couldn't create connection to server.
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] Restarting server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099
[Error - 1:27:22 AM] The NextLS server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

can you check the permissions on that directory?

and there is nothing in there in any of the dirs?

yes, the directories are empty.

Can you confirm your adapter is set to stdio and not tcp? In elixir tools settings

Yes. I confirm. It is stdio.

Not sure what happened. Today I uninstalled the vscode extension restarted WSL and installed nextls vscode extension. It downloaded the latest version and is working. Same process was not working earlier. Maybe your new release solved the issue?
Anyway, thanks a lot for the effort.

Nice!
I added more logging so if it happens again we'll have more to go on


[WIP] Add dependency bumping doc

What
Documents which type of dependencies are used and how to bump them.

Can anyone spot if something is missing?


Doesn't work as a reliable TimePicker only

My requirement is to show a start of day i.e. 12:00 AM as the default time selected in the time-picker text field and just display the time-picker.
I was able to use just the time-picker using the format option but my core requirement of setting the default time to start of day was not fulfilled. Below given are the versions of jQuery
bootstrap-datetimepicker v4.17.37
jQuery v1.12.0
Bootstrap v3.3.6
Browsers:

Mozilla Firefox 47.0 (on Ubuntu 14.04 LTS)
Google Chrome Version 49.0.2623.87 (64-bit) (on Ubuntu 14.04 LTS)

JS
  enableTimePicker = function() {
    var timeInputFieldObjects = $("input.time-picker");

    if (timeInputFieldObjects.length > 0) {
      timeInputFieldObjects.each(function() {
        $(this).datetimepicker({
          format: 'h:mm A',
          useCurrent: false,
          //defaultDate: moment().startOf('day')
          minDate: moment().startOf('day')
        });
      })
    }
  };

Options used and steps performed and the outcome:
passing no options except format OR passing format and useCurrent: false OR passing format and useCurrent: false and minDate: moment().startOf('day')

when the datetimepicker is applied the target text-field is empty
when focusing into the datetimepicker using the mouse and selecting a time, say 12:00 AM, 12:00 AM is shown in the text-field
when focusing out using mouse and focusing into again into the datetimepicker using the mouse but not selecting any time, 2:30 PM is shown
when focusing out using mouse and focusing into again into the datetimepicker using the mouse but not selecting any time, 3:00 PM is shown
when focusing out using mouse and focusing into again into the datetimepicker using the mouse but not selecting any time, 2:30 PM is shown

and subsequent focusing in and out keeps on switching the time between 2:30 PM and 3:00 PM. Don't know why 2:30 PM is displayed. I am in IST (UTC +05:30) timezone and at time of testing it the time was around 1:00 PM.
passing format and useCurrent: false and defaultDate: moment().startOf('day')

when the datetimepicker is applied the target text-field shows 2:30 PM as the default time. I was expecting it to be set to 12:00 AM
when focusing into the datetimepicker using the mouse, 2:30 PM gets replaced with 3:00 PM is shown in the text-field
when focusing out using mouse and focusing into again into the datetimepicker using the mouse but not selecting any time, 2:30 PM is shown

and subsequent focusing in and out keeps on switching the time between 2:30 PM and 3:00 PM.

If anybody ends-up having the same requirement as I have and facing problem using this component as time-picker only I have successfully implemented my requirement using this alternative component. And it works smoothly without any issues.
Hope it benefits someone urgently looking for solution until the issues in this library I have reported gets fixed.
Thanks.

Is any solution in the works for this? I have the same issue. Or perhaps the alternative component is the way to go?
Thanks


Upgrade DynamicUI to 0.0.8

Upgrade DynamicUI to 0.0.8

Thanks for submitting a pull request!
We will review it as soon as possible.

Hey @0xWDG,
Thanks for your contribution.
Your PR has been merged!
Your name will appear on https://auroraeditor.com/#contributors in a few moments, if you have contributed to the editor.
Thanks again for your contribution!
Kind Regards,
Aurora Editor Team.


brave: 1.63.162 -> 1.63.165

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for brave is: Privacy-oriented browser for Desktop and Laptop computers
meta.homepage for brave is: https://brave.com/
meta.changelog for brave is: https://github.com/brave/brave-browser/blob/master/CHANGELOG_DESKTOP.md#163165
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.63.165 with grep in /nix/store/banav2f5hk6db1189606iic391ildw92-brave-1.63.165
found 1.63.165 in filename of file in /nix/store/banav2f5hk6db1189606iic391ildw92-brave-1.63.165

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
brave

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/banav2f5hk6db1189606iic391ildw92-brave-1.63.165 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A brave https://github.com/r-ryantm/nixpkgs/archive/002c579a4ae0890309b64294e969e659ba18513b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/002c579a4ae0890309b64294e969e659ba18513b#brave

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/banav2f5hk6db1189606iic391ildw92-brave-1.63.165
ls -la /nix/store/banav2f5hk6db1189606iic391ildw92-brave-1.63.165/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

brave

Maintainer pings
cc @uskudnik @rht @JeffLabonte @nasirhm @buckley310 for testing.

Adding the backport label in case that works. Stable is one PR behind currently so probably requires manual backport :shrug:


Manifest issue with polus-notebook-plugin/plugin_csv_to_csv.json

The plugin polus-notebook-plugin/plugin_csv_to_csv.json is missing fields: ('author',)

There is now an author field in the manifest


Too many open files

I have a hm.. library of markdown files. 36000 total. I can't use this CMS because of error:

Is it fixable on your side or this is astro problem too? Can you give me an advice, how to handle this amount with your cms?

+1

Regarding Astro, see https://github.com/withastro/astro/issues/11683.


It is Using Jekyll server for the theme

Need to customize the site so it will not go to the Jekyll server for the theme. We can have customize Theme

this issue was closed with the pull request  "overwrite minima theme #2"


(PUP-9076) Puppet should fail when it cannot find a functional server

When server_list is set, rather than fall back to the default server
setting, puppet should just fail.
This commit updates the acceptance tests, which were missed when this
change was originally made.

jenkins please test this with servertests

CLA signed by all contributors.


Support the using keyword for functions

Describe the feature
The following check for the using keyword currently only allows it for objects. These lines will prevent the using keyword from being used on functions which is allowed in tsc.
https://github.com/swc-project/swc/blob/d6cd2146faed9155ae6f2c625daa173ddc7c0064/packages/helpers/esm/_using.js#L5-L7
A function can have the Symbol.dispose or Symbol.asyncDispose added to them to make them disposable just like how an object can. Here is the implementation in TypeScript, showing that it should allow the using keyword for functions.
https://github.com/microsoft/TypeScript/blob/36f9e9e037a8bf715d96c8270732d5830719d7c8/tests/baselines/reference/usingDeclarations.11.js#L57
if (typeof value !== "object" && typeof value !== "function") throw new TypeError("Object expected.");

Babel plugin or link to the feature description
No response
Additional context
This is based on a discussion about making spies and stubs disposable so that the originals will automatically be restored after they are no longer needed. This is needed to implement the feature.
https://github.com/denoland/deno_std/issues/3966

babel/babel#16150


ci(apple): CI/CD check for forbidden syscalls like fstat

https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api
https://github.com/Wooder/ios_17_required_reason_api_scanner/tree/main

I managed to prune out all of our dependencies on fstat, but rustc still links against libSystem at the end of the day, which pulls in fstat and stat, so this CI check won't be that useful.
#4400 should eliminate the need for this CI check.


Change DataShuttle public 'shower' functions to getters. [6]

This PR changes at lot of the 'showers' functions in the API to getters, which makes more sense from an API-focused perspective. Now the CLI functions print the output in the command_line_interface.py script.
Also, all CLI functions are now tested (mostly these showers were not tested previously).
In some cases, showing configs and local-file-tree are still exposed as these perform some __repr__ like functionality. Otherwise everything is a getter.
Currently, the CLI is a bit weird (e.g. I'm not sure if these should be called 'getters' in the CLI as they can't return anything) and not all underlying arguments are explosed. As descripted in #267, if we proceed with CLI then CLI can be properly designed to break the link between CLI and API. For now though the CLI should be fairly well fixed (in a sub-optimal state) and we can decide what to do with it later.
Slight change to docs to reflect new function name, but for most part these are build automatically from the API / CLI.

Cheers! Fixed here


Block references break after the note is refactored

The block references created within the main note no longer work after the note is refactored. Is there a way to retain them?

@lynchjames Hi, I also encountered this problem (which has been reported for the core note composer as well).
It would be great if I had the time to send a PR to your repository, but unfortunately I've been busy so I couldn't find time to look around the codebase.
So I've just created another plugin that can extract selections without breaking links:
https://github.com/RyotaUshio/obsidian-better-note-composer
If you're interested, feel free to merge the code to this plugin with my credit.


Bloodhound: Replace getIntersection method.

Fixes functional error when matches array only has one key, and that key value is less than the first key value in the ids array, which results in an empty intersection array. Uses the same logic as the _.intersection(array) method from underscore.js to safely find the intersection of the two arrays.

Refs #105


Client gets kicked from server if a macaw is within tracking range, until it doesn't

To join a server with a macaw present, you have to keep joining and joining, getting kicked, until it just works. Then it works for the rest of the client session.

It's a race condition, and it's probably totally not fixed and I'm just lucky, but we can hope


"The specified MaxQuant msms.txt file does not exist"

Hello! I want to try to process the MaxQuant test file from the resources page using the synthedia package from the command line. However the msm.txt file is not detected. The package works fine with the example prosit file. Could you help me figure out how to solve this? thank you
Operating System: Ubuntu 20.04.5 LTS
Kernel: Linux 5.15.0-58-generic
(Synthedia) usr@sysbc-lx-507:$ synthedia --mq_txt_dir '~/230125_synthedia_test/example_MaxQuant_msms/example_msms.txt' --centroid_ms1 --centroid_ms2
2023-01-25 14:49:14,578 - INFO - Started Synthedia 2023-01-25 14:49:14.578185
2023-01-25 14:49:14,578 - INFO - Config args:
2023-01-25 14:49:14,578 - INFO - 	mq_txt_dir: ~/230125_synthedia_test/example_MaxQuant_msms/example_msms.txt
2023-01-25 14:49:14,578 - INFO - 	prosit: None
2023-01-25 14:49:14,578 - INFO - 	prosit_peptide_abundance_model: exponentially_modified_gaussian
2023-01-25 14:49:14,578 - INFO - 	prosit_peptide_abundance_mean: 22
2023-01-25 14:49:14,578 - INFO - 	prosit_peptide_abundance_stdev: 1.4
2023-01-25 14:49:14,578 - INFO - 	prosit_peptide_abundance_emg_k: 1
2023-01-25 14:49:14,578 - INFO - 	acquisition_schema: None
2023-01-25 14:49:14,578 - INFO - 	use_existing_peptide_file: None
2023-01-25 14:49:14,578 - INFO - 	out_dir: /local/home/usr/output
2023-01-25 14:49:14,578 - INFO - 	output_label: output
2023-01-25 14:49:14,578 - INFO - 	config: None
2023-01-25 14:49:14,578 - INFO - 	silent: False
2023-01-25 14:49:14,578 - INFO - 	write_params: False
2023-01-25 14:49:14,578 - INFO - 	mq_pep_threshold: 0.001
2023-01-25 14:49:14,578 - INFO - 	filterTerm: ['CON_', 'REV']
2023-01-25 14:49:14,578 - INFO - 	num_processors: 8
2023-01-25 14:49:14,578 - INFO - 	ms1_min_mz: 350
2023-01-25 14:49:14,578 - INFO - 	ms1_max_mz: 1600
2023-01-25 14:49:14,578 - INFO - 	ms2_min_mz: 100
2023-01-25 14:49:14,578 - INFO - 	ms2_max_mz: 2000
2023-01-25 14:49:14,578 - INFO - 	ms1_resolution: 120000
2023-01-25 14:49:14,579 - INFO - 	ms2_resolution: 15000
2023-01-25 14:49:14,579 - INFO - 	ms1_scan_duration: 0.37
2023-01-25 14:49:14,579 - INFO - 	ms2_scan_duration: 0.037
2023-01-25 14:49:14,579 - INFO - 	isolation_window: 30
2023-01-25 14:49:14,579 - INFO - 	resolution_at: 200
2023-01-25 14:49:14,579 - INFO - 	n_points_gt_fwhm: 3
2023-01-25 14:49:14,579 - INFO - 	esi_instability: 20
2023-01-25 14:49:14,579 - INFO - 	ms1_ppm_error_mean: 0
2023-01-25 14:49:14,579 - INFO - 	ms1_ppm_error_stdev: 0
2023-01-25 14:49:14,579 - INFO - 	ms2_ppm_error_mean: 0
2023-01-25 14:49:14,579 - INFO - 	ms2_ppm_error_stdev: 0
2023-01-25 14:49:14,579 - INFO - 	rt_peak_fwhm_distribution_model: exponentially_modified_gaussian
2023-01-25 14:49:14,579 - INFO - 	rt_peak_fwhm_distribution_mean: 4
2023-01-25 14:49:14,579 - INFO - 	rt_peak_fwhm_distribution_stdev: 1
2023-01-25 14:49:14,579 - INFO - 	rt_peak_fwhm_distribution_emg_k: 1
2023-01-25 14:49:14,579 - INFO - 	min_rt_peak_fwhm: 1
2023-01-25 14:49:14,579 - INFO - 	original_run_length: 0
2023-01-25 14:49:14,579 - INFO - 	new_run_length: 0
2023-01-25 14:49:14,579 - INFO - 	rt_buffer: 5
2023-01-25 14:49:14,579 - INFO - 	rt_instability: 15
2023-01-25 14:49:14,579 - INFO - 	ms1_min_peak_intensity: 100
2023-01-25 14:49:14,579 - INFO - 	ms2_min_peak_intensity: 10
2023-01-25 14:49:14,579 - INFO - 	centroid_ms1: True
2023-01-25 14:49:14,579 - INFO - 	centroid_ms2: True
2023-01-25 14:49:14,579 - INFO - 	write_empty_spectra: False
2023-01-25 14:49:14,579 - INFO - 	mz_peak_model: gaussian
2023-01-25 14:49:14,579 - INFO - 	rt_peak_model: exponentially_modified_gaussian
2023-01-25 14:49:14,579 - INFO - 	mz_emg_k: 2
2023-01-25 14:49:14,579 - INFO - 	rt_emg_k: 1
2023-01-25 14:49:14,579 - INFO - 	prob_missing_in_sample: 0
2023-01-25 14:49:14,579 - INFO - 	prob_missing_in_group: 0
2023-01-25 14:49:14,579 - INFO - 	no_isotopes: False
2023-01-25 14:49:14,579 - INFO - 	tic: False
2023-01-25 14:49:14,579 - INFO - 	schema: False
2023-01-25 14:49:14,579 - INFO - 	all: False
2023-01-25 14:49:14,579 - INFO - 	n_groups: 1
2023-01-25 14:49:14,579 - INFO - 	samples_per_group: 1
2023-01-25 14:49:14,579 - INFO - 	between_group_stdev: 1.0
2023-01-25 14:49:14,580 - INFO - 	within_group_stdev: 0.2
2023-01-25 14:49:14,580 - INFO - 	decoy_msp_file: None
2023-01-25 14:49:14,580 - INFO - 	num_decoys: 500
2023-01-25 14:49:14,580 - INFO - 	simulate_top_n_decoy_fragments: 15
2023-01-25 14:49:14,580 - INFO - 	decoy_abundance_mean: 22
2023-01-25 14:49:14,580 - INFO - 	decoy_abundance_stdev: 3
2023-01-25 14:49:14,580 - INFO - 	preview: False
2023-01-25 14:49:14,580 - INFO - 	preview_sequence: SAMPLER
2023-01-25 14:49:14,580 - INFO - 	preview_charge: 2
2023-01-25 14:49:14,580 - INFO - 	preview_abundance: 1000000
2023-01-25 14:49:14,580 - INFO - Calculating peak parameters
2023-01-25 14:49:14,580 - INFO - The specified MaxQuant msms.txt file does not exist
2023-01-25 14:49:14,580 - INFO - Exiting
Traceback (most recent call last):
File "/local/home/usr/.local/bin/synthedia", line 8, in
sys.exit(main())
File "/local/home/usr/.local/lib/python3.8/site-packages/synthedia/main.py", line 200, in main
assembly.assemble(options)
File "/local/home/usr/.local/lib/python3.8/site-packages/synthedia/assembly.py", line 398, in assemble
options = get_extra_parameters(options)
File "/local/home/usr/.local/lib/python3.8/site-packages/synthedia/assembly.py", line 329, in get_extra_parameters
options.original_run_length = get_rt_range_from_input_data(options)
File "/local/home/usr/.local/lib/python3.8/site-packages/synthedia/assembly.py", line 270, in get_rt_range_from_input_data
raise IncorrectInputError(msg)
synthedia.assembly.IncorrectInputError: The specified MaxQuant msms.txt file does not exist

Hi,
The --mq_txt_dir parameter needs to point to a directory that contains both the msms.txt and evidence.txt files. Above, it's pointing to the msms.txt file specifically. The corresponding evidence.txt file can be downloaded here.
Also note that it's important that the files are named msms.txt and evidence.txt exactly. So where you've named the file example_msms.txt, should be renamed to msms.txt. This is because we're assuming that synthedia is being directed to the txt directory produced by MaxQuant.
For example, with the directory structure:
.
└── example
    └── txt
        ├── evidence.txt
        └── msms.txt

we'd run:
synthedia --mq_txt_dir example/txt --centroid_ms1 --centroid_ms2

Hope that helps :)


Add optional hostNetwork for controller

Although not ideal, in some situations allowing this chart to set hostNetwork: true for the controller is the least invasive solution. This PR sets this field only if specified, otherwise it's a no-op.

Thank you very much, works perfectly.
Would be nice to have it in a release.

LGTM, cheers


fix(solid): client.subcribe is undefined when using multi clients

:tada: This PR is included in version 0.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Set up JKAN

@JackGilmore is this one about the test JKAN setup pre-CTC24, or is this the use of live data?

@KarenJewell This is the task just to get JKAN forked and set up with OAuth for log in. I might also try and get some organisations imported before CTC24 but we may need some sort of tool for bulk creation given that these are stored as individual markdown files that contain YAML. I've opened #21 to look into this

JKAN has been forked to https://github.com/OpenDataScotland/jkan
I've added some initial branding but hoping to see some movement on the current open PR for JKAN to get Bootstrap 4 added (https://github.com/timwis/jkan/pull/153) before we get down and dirty with some proper theming.
JKAN still needs OAuth configured and the custom domain applied.

OAuth is set up and I've added the ODS org admin group as maintainers on the JKAN repository. Reckon we can mark this as closed now? @KarenJewell

Custom domain name purchased and assigned to GitHub Pages repo under https://github.com/OpenDataScotland/jkan


Rudin's Dowker space is a P-space

Resolves https://topology.pi-base.org/spaces/S000138/properties/P000147
Note that there is no trait that could be added from which this one could be deduced, and that wouldn't be deducible from this and already existing properties of S138.

Ready for review.


Modified README Markdown Formatting

A bit of a spontaneous round of edits.
I'm open to discussion if anything seems off or is unwanted. Thank you!

Spelling: ontop >> on top
Spelling: virtualisation >> virtualization (since the latter appears most often in the MD)
Formatting: use bullets for reference links (so they don't mush into a single line)
Formatting: change case of PowerShell to be titlecase
Formatting: titlecase Markdown headers
Formatting: combine two adjacent MD code fences into one code fence (same syntax/language)

Note: I plan to give the MD another re-read or two to see if there are any other tweaks.

@mjbear Thanks!
When you're ready @FloSch62 or I can merge.


fix step-before and step-after with dedicated test (#2340)

Hi all
I request approval for this pull request for resolve the #2340 bug int he step chart with restore the "step-before" and "step-after" in the stop type graph.
I created a basic test for check if the graph works fine.
All test for my point of view are correctly ( I modify marginally the code of the graph).
For more usefull test I create two jsfiddle test
d3: v4.13.0 - https://jsfiddle.net/xjy7r25w/
d3: v5.4.0 - https://jsfiddle.net/p0qe247m/
Please accept this pull request.
Thanks
Lorenzo

Codecov Report

Merging #2385 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2385   +/-   ##
=======================================
  Coverage   77.23%   77.23%
=======================================
  Files          51       51
  Lines        4138     4138
=======================================
  Hits         3196     3196
  Misses        942      942

Impacted Files
Coverage Δ

src/shape.js
78.68% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@tanganellilore
Thanks for the contribution! Sorry for the delayed response...
The change seems good and I confirmed 'step-after' and 'step-before' work for line.step.type 👍
The source code seems including tab indentation. Can you replace these with 4-space indent? (If you use editorconfig compliant editor, it automatically formats them correctly.

Hi @kt3k  ,
sorry for my mistake, I fix it!
I hadn't install editorconfig in my Visual Studio Code.
Now all is ok!
Thanks
Lorenzo


[WFCORE-3867] trim read sys prop string

Core - Full Integration Build 7428 outcome was FAILURE using a merge of 9fc576ae1ace4742def574b10854660f1a3f7c4a
Summary: Tests failed: 5 (5 new), passed: 4336, ignored: 142 Build time: 01:43:38
Failed tests
org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m18:21:25,965 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/ed/9129a8918e4ac10a44371802b66d865d2990c9/content
 [0m [0m18:21:25,968 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m18:21:26,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:21:26,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:21:26,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:21:26,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:21:26,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:21:26,123 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m18:21:26,193 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m18:21:26,279 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

 [0m [0m18:21:26,441 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 3.0.4 (Final)
 [0m [0m18:21:26,529 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m18:21:26,595 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 2) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m18:21:26,818 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m18:21:26,835 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m18:21:27,283 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m18:21:27,302 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m18:21:27,454 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/ac/59c5b9467f2349d7006bac0afb69095dc0e332/content
 [0m [0m18:21:27,456 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m18:21:27,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:21:27,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:21:27,596 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:21:27,597 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:21:27,597 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:21:27,624 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m18:21:27,685 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m18:21:27,765 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

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

org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m18:22:17,665 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/d0/91611dad932caf862032b0a5250068179bd203/content
 [0m [0m18:22:17,669 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m18:22:17,793 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:22:17,794 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:22:17,794 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:22:17,794 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:22:17,794 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:22:17,834 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m18:22:17,922 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m18:22:18,023 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

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

 [0m [0m18:22:18,183 INFO  [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 3.0.4 (Final)
 [0m [0m18:22:18,281 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m18:22:18,317 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started CoarseWebFailoverTestCase.war cache from web container
 [0m [33m18:22:18,575 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [33m18:22:18,613 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [0m18:22:18,949 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Registered web context: '/CoarseWebFailoverTestCase' for server 'default-server'
 [0m [0m18:22:18,969 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "CoarseWebFailoverTestCase.war" (runtime-name : "CoarseWebFailoverTestCase.war")
 [0m [0m18:22:19,097 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/d7/a05e083128e2c58b520b9e3e558c88e4ac860f/content
 [0m [0m18:22:19,100 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m18:22:19,150 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:22:19,151 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:22:19,151 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:22:19,151 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:22:19,151 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:22:19,155 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m18:22:19,175 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

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

org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m18:22:48,883 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
 [0m [0m18:22:49,238 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
 [0m [0m18:22:49,253 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
 [0m [0m18:22:49,418 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Beta2-SNAPSHOT (WildFly Core 5.0.0.Beta5-SNAPSHOT) starting
 [0m [0m18:22:51,023 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m18:22:51,060 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 25) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m18:22:51,071 INFO  [org.wildfly.security] (ServerService Thread Pool -- 33) ELY00001: WildFly Elytron version 1.3.2.Final
 [0m [0m18:22:51,213 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m18:22:51,235 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 3.6.3.Final
 [0m [0m18:22:51,248 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.6.3.Final
 [0m [0m18:22:51,309 INFO  [org.jboss.as.ee] (ServerService Thread Pool -- 44) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
 [0m [0m18:22:51,317 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m18:22:51,324 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 59) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m18:22:51,331 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.5.1.Final
 [0m [0m18:22:51,335 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
 [0m [33m18:22:51,353 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 68) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 [0m [0m18:22:51,361 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 70) WFLYWS0002: Activating WebServices Extension
 [0m [0m18:22:51,405 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m18:22:51,411 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 65) WFLYSEC0002: Activating Security Subsystem
 [0m [0m18:22:51,411 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.0.11
 [0m [0m18:22:51,443 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.2.Final
 [0m [0m18:22:51,459 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 41) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m18:22:51,523 INFO  [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service
 [0m [0m18:22:51,531 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 2.0.7.Final starting
 [0m [0m18:22:51,576 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m18:22:51,659 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.7.Final
 [0m [0m18:22:51,667 INFO  [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
 [0m [0m18:22:51,704 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m18:22:51,714 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
 [0m [0m18:22:51,714 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
 [0m [0m18:22:51,915 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m18:22:51,954 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
 [0m [0m18:22:51,957 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
 [0m [0m18:22:52,005 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m18:22:52,015 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
 [0m [0m18:22:52,026 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000001: Initializing mod_cluster version 1.3.9.Final
 [0m [0m18:22:52,032 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m18:22:52,041 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m18:22:52,149 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 [0m [0m18:22:52,164 INFO  [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [0m18:22:52,177 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/deployments
 [0m [33m18:22:52,178 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost

org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.assertValue(ExternalizerTestCase.java:108)
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test(ExternalizerTestCase.java:96)
------- Stdout: -------
 [0m18:23:12,111 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/b4/4a00aa57eebd9acfde9afe8afe3c420388e8d9/content
 [0m [0m18:23:12,114 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m18:23:12,245 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 5) WFLYCLINF0002: Started ExternalizerTestCase.war cache from web container
 [0m [0m18:23:12,250 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m18:23:12,267 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) WFLYUT0021: Registered web context: '/ExternalizerTestCase' for server 'default-server'
 [0m [0m18:23:12,286 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ExternalizerTestCase.war" (runtime-name : "ExternalizerTestCase.war")
 [0m [0m18:23:12,303 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/b4/4a00aa57eebd9acfde9afe8afe3c420388e8d9/content
 [0m [0m18:23:12,305 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m18:23:12,405 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 82) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m18:23:12,405 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0002: Started ExternalizerTestCase.war cache from web container
 [0m [0m18:23:12,414 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 89) WFLYUT0021: Registered web context: '/ExternalizerTestCase' for server 'default-server'
 [0m [0m18:23:12,425 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ExternalizerTestCase.war" (runtime-name : "ExternalizerTestCase.war")
 [0m [0m18:23:12,538 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0022: Unregistered web context: '/ExternalizerTestCase' from server 'default-server'
 [0m [0m18:23:12,551 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 30) ISPN000029: Passivating all entries to disk
 [0m [0m18:23:12,554 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 30) ISPN000030: Passivated 3 entries in 2 milliseconds
 [0m [0m18:23:12,557 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0003: Stopped ExternalizerTestCase.war cache from web container
 [0m [0m18:23:12,572 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment ExternalizerTestCase.war (runtime-name: ExternalizerTestCase.war) in 35ms
 [0m [0m18:23:12,572 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m18:23:12,585 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/b4/4a00aa57eebd9acfde9afe8afe3c420388e8d9/content
 [0m [0m18:23:12,585 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m18:23:12,594 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0022: Unregistered web context: '/ExternalizerTestCase' from server 'default-server'
 [0m [0m18:23:12,604 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 89) ISPN000029: Passivating all entries to disk
 [0m [0m18:23:12,604 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 89) ISPN000030: Passivated 3 entries in 0 milliseconds
 [0m [0m18:23:12,607 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0003: Stopped ExternalizerTestCase.war cache from web container
 [0m [0m18:23:12,613 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment ExternalizerTestCase.war (runtime-name: ExternalizerTestCase.war) in 22ms
 [0m [0m18:23:12,614 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 89) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m18:23:12,623 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/b4/4a00aa57eebd9acfde9afe8afe3c420388e8d9/content
 [0m [0m18:23:12,623 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m

org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.testOneRequestSimpleFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<2> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.testOneRequestSimpleFailover(ReplicationForNegotiationAuthenticatorTestCase.java:114)
------- Stdout: -------
 [0m18:23:12,669 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/90/0866338ef4bfe64bb873e17b328dac65a0de0d/content
 [0m [0m18:23:12,672 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m18:23:12,690 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m18:23:12,758 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m18:23:12,759 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:23:12,759 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:23:12,759 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:23:12,759 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:23:12,759 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:23:12,764 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m18:23:12,776 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

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

 [0m [0m18:23:12,840 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started ReplicationForNegotiationAuthenticatorTestCase.war cache from web container
 [0m [0m18:23:12,845 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) WFLYCLINF0002: Started default-server cache from web container
 [0m [33m18:23:12,858 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m18:23:12,862 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m18:23:12,981 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0021: Registered web context: '/ReplicationForNegotiationAuthenticatorTestCase' for server 'default-server'
 [0m [0m18:23:12,996 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name : "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [0m18:23:13,021 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/90/0866338ef4bfe64bb873e17b328dac65a0de0d/content
 [0m [0m18:23:13,026 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m18:23:13,039 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m18:23:13,086 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m18:23:13,090 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m18:23:13,098 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

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

retest this please


Issues dataset CLEVRER loading annotations

Hello, first of all thank you for your very interesting work.
As I was doing some experiments with your repo, I found out some issues with annotations in the CLEVRER dataset for the slot training with masks (--load_mask == True). I instead added some script to evaluate some metrics during the learning of the vision model with mask quality, etc.
Two of the videos contains only 104 frames (the 9777 and 7648) and were failing in the _read_mask function. It seems that you already removed one "broken_video" in the _get_files function, was it related to the same kind of issue ?
Next to that, I also had some issue related to the bbox loading: two other videos (8182 and 18700) seemed to have 8 objects in at least one of their frames and thus the bbox padding function was also failing.
Did you encounter this during your process or not at all, if yes did how did you solve the issue ? (for now I just added a list of broken_videos, 5 in total)
Thank you in advance.

Hi, I don't really remember the details but IIRC, indeed there are some files corrupted and I handled one of them in the code (as you pointed out). Then, I realized there might be more such files, and it's impossible to go over all videos to find them out (because there might be different errors, e.g., number of frames, number of objects, or just file corruptions). Therefore, I decided to just skip all wrong data when encountered. That's what my _rand_another() function is doing -- every time when an error occurs in the reading function, I'll just read another data item at a random index.

Ok, thank you for your answer, on my side it seems that the function was not correctly called in certain case as the try catch was only caught for ValueError, with a simple modification it seems to be working gently.


Can we get a package so npm and yarn can import these contracts?

Without a package, I'm left trying to copy these in. Are these contracts at the point they can be packaged up an hosted at npm?

https://www.npmjs.com/package/operator-filter-registry

This is great, thank you. Is there a reason there aren't any releases listed in the repo here? That would have helped me locate it. I was looking for @ProjectOpenSea/operator-filter-registry.

The creator of that package has graciously transferred ownership to OpenSea, and we are hoping to publish the most recent versions and update the readme in the coming days.

Added to the repo and published the latest updates, thanks!


Add unit tests for SCR examples

We should add the scr examples as unit tests.
This will likely require adding some scr checkpoint files to the axom_data repository: https://github.com/LLNL/axom_data

@nselliott will touch base with Adam M. about his PR.

The example spio_IO_SCR_Checkpoint_ex example has unit test code added into it, in order to keep all SCR testing in one executable, as errors occur if two SCR-enabled executables get launched in parallel during a make test run.  I think this satisfies the request in this issue.  Any further SCR-based unit testing should be inserted into this example.


Major refactoring to use pydantic models for config files.

Description
This PR is related to issue #200, whereby .toml files (that hold parameters) are loaded into pydantic models, to streamline the code, enable validation, and make it easier for parameters to be documented than relying upon dictionaries internally.
While we only need a single model to handle all the datasets, each potential requires their own model, however, the basic structure is the same.
E.g. the CoreParameter section is more or less unique for each NNP, although  the post processing can use the same submodules (just with different defaults).
class ANI2xParameters(ParametersBase):
    class CoreParameter(ParametersBase):
        angle_sections: int = 4
        radial_max_distance: str = "5.1 angstrom"
        radial_min_distance: str = "0.8 angstrom"
        number_of_radial_basis_functions: int = 16
        angular_max_distance: str = "3.5 angstrom"
        angular_min_distance: str = "0.8 angstrom"
        angular_dist_divisions: int = 8

    class PostProcessingParameter(ParametersBase):
        per_atom_energy: PerAtomEnergy = PerAtomEnergy(
            normalize=True,
            from_atom_to_molecule_reduction=True,
            keep_per_atom_property=True,
        )
        general_post_processing_operation: GeneralPostProcessingOperation = (
            GeneralPostProcessingOperation(
                calculate_molecular_self_energy=False,
                calculate_atomic_self_energy=False,
            )
        )

    model_name: str = "ANI2x"
    core_parameter: CoreParameter
    postprocessing_parameter: PostProcessingParameter

After several iterations, I think it is clearest to give each NNP parameter model a unique name (but using the same scheme, e.g, ANI2xParameters, SchNetParameters), and have these all stored in the same python file (potentials/parameters.py).  I also decided to nest the CoreParameter class inside the main parameter class for each, allowing us to retain the same internal naming structure, regardless of the NNP (since they are general, the PerAtomEnergy sub model, and GeneralPostProcessingOperation models live outside of the class structure).
Todo

[x] Add in CI tests for the models themselves
[x] Add in CI tests for training using the new models
[x] Merge in main

Status

[x] Ready to go

Currently running into issues on the CI, as qcportal and qcelemental do not seem to import properly.  This only started once I explicitly put in pydantic 2 in the environment file. qcportal uses pydantic 1, but using the .v1 namespace so it should be compatible with pydantic 2, but doesn't seem to be working as expected.   This does not appear to occur locally for me on either Mac or linux, and all installed packages seem to be the same, but it is failing on Mac and linux CI.
I may just need to mark the tests to skip for now; the curation module is largely independent from the rest of the code (relies on some functions in utils), and the main training code does not depend upon it (also does not use pydantic directly).

Currently running into issues on the CI, as qcportal and qcelemental do not seem to import properly. This only started once I explicitly put in pydantic 2 in the environment file. qcportal uses pydantic 1, but using the .v1 namespace so it should be compatible with pydantic 2, but doesn't seem to be working as expected. This does not appear to occur locally for me on either Mac or linux, and all installed packages seem to be the same, but it is failing on Mac and linux CI.
I may just need to mark the tests to skip for now; the curation module is largely independent from the rest of the code (relies on some functions in utils), and the main training code does not depend upon it (also does not use pydantic directly).

The issue appears to have been a pin to an older version of qcelemental ( A version that apparently was using pydantic 1, not the .v1 namespace, so it was causing issues when pydantic 2 was installed).

It's taken a lot of time to resolve test failures (seems like main was failing already when merged in), but I think I have gotten everything resolved.

We have used NNP and potential throughout the first versions. Since we are trying to standardize naming conventions, I am wondering if we should move to model instead?

We have used NNP and potential throughout the first versions. Since we are trying to standardize naming conventions, I am wondering if we should move to model instead?

I think potential is fine, as we've changed a lot of that.  I'll also note model is a protected namespace in pydantic, so it gets unhappy to have variables that start with model_

We have used NNP and potential throughout the first versions. Since we are trying to standardize naming conventions, I am wondering if we should move to model instead?

I think potential is fine, as we've changed a lot of that. I'll also note model is a protected namespace in pydantic, so it gets unhappy to have variables that start with model_

That is a great point! Then let's use potential instead!

I think this is a great step towards input validation and read to merge in principle. I left a few comments that should be resolved first.
I saw that there are a few default parameters set tp False, do you think that there is a way to remove these?

I think I had put a note about this in the code.  This is only related to the post processing operations.
In order to define a model for the post processing operations, each possible operation variable needs to be defined in the model.   I chose to just mark all post processing operations to False; if you want to perform the post processing operations, you need to define it as True in the toml file. I think this fits with the general approach of no default parameters, because by default, if you do not define True, it does nothing.
While these could be marked as "Optional", the code to parse this would still require us to check their value (the first check would be to see if not None, then checking the actual bool value).  Marking by default False in the model avoids this extra layer of checking and it will ultimately behave exactly the same.

I have everything addressed now, reading for a second look over @wiederm .


Add linter for editorconfig

We actually have a linter / tests for the editorconfig already or do you mean adding it to the linter which checks a config before the pipeline executes it?

well i found a wrong intendation:
https://github.com/woodpecker-ci/woodpecker/blob/fe006d9656309cab84c6059f7648ba2c6ee1ca30/.woodpecker/docs.yml#L56-L57

  editor-config:
    image: mstruebing/editorconfig-checker

adding this step should do it

to exclude stuff create file .ecrc
{
  "Exclude": ["LICENSE", ".git*"]
}


Instructions to update Vale application

We need to document how a user updates their instance of Vale, for example to catch fixes in a Vale minor release.
Research how to upgrade Vale to the latest instance. You can see the latest release here: https://github.com/errata-ai/vale/releases
Run vale --version to check the version installed locally.
See what command works for Linux users to update Vale (the procedure for Mac users might have to be in another issue).
The command is probably either:
sudo dnf upgrade vale
Or the install command again for our VRH docs:
$ sudo dnf copr enable mczernek/vale && sudo dnf install vale
You can update the user guide here: https://github.com/redhat-documentation/vale-at-red-hat/tree/main/modules/user-guide

Does VS Code auto-update the Vale instance?

I wouldn't have thought so? VS Code just points to the local Vale binary and uses that to lint the file?

So whatever version you have installed locally I presumed is what VS Code would use.

https://docs.google.com/document/d/1S9jZc2EZ8vUm33t0rrTEr6FZH0WnOXEs7ajcbQIaqv0/edit#heading=h.ym2k03fipx1m - FYI


Dogecoin Docker on Photon OS for scaleabilty

This issue tracker is only for technical issues related to Dogecoin Core.
For general questions about Dogecoin or wallet recovery please use one of the various communities:

Dogeducation on reddit
Discord

Describe the issue
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

When I restart the docker the progress goes to 0. Are there plans to make it useable for docker containers because of scalabilty. I used photonOS for VMWARE

Expected behaviour
State should be saved
Actual behaviour
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of Dogecoin Core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
Machine specs:

OS:
CPU:
RAM:
Disk size:
Disk Type (HD/SDD):

Any extra information that might be useful in the debugging process.
This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

Thinking about running it in datacenters with scalabilty on docker swarms.
Much scaleabilty, lightweight OS and effeciency improvement.
Toughts on Kubernetes?

Docker containers aren't persistent, you should attach a volume to the container. I don't think isn't an issue with Dogecoin Core.

Okay thanks makes sense. So for my understanding It just would be a transaction node ?

We can't handle deployment queries, sorry. Please try https://www.reddit.com/r/dogeducation/


global or full longitude map central_lon at 180

This PR is to fix issue #325 . This issue is caused by central_lon =180 only set with global map, however for the the S60N90 region with full longitude, setting central longitude to180 is also needed.

Hi @forsyth2 I have tested this PR with lat-lon and RRM config files. Would you please review the codes and also test with relevant configurations? Thank you!

@chengzhuzhang I checked out this branch, ran pip install . and ./tests/test.sh. All 26 tests passed. They use the configuration at https://github.com/E3SM-Project/e3sm_diags/blob/master/tests/system/all_sets.cfg. Visual inspection of the lat_lon plots looks good to me. Is there another config file I should run/test on?

@chengzhuzhang I also ran the command from #325 (changing the results dir to my directory) on Cori and the plots look fine to me.

Thank you for testing, Ryan! I will go ahead and merge.


#6090 Document accessibility considerations

See #6090. This is a new documentation page, meant as a reference of all things to consider for the accessibility of Wagtail sites – essentially raising awareness of common issues we see in countless audits of real-world sites.

@Scotchester this should now be ready for review – I hope it all makes sense!

Should this guide also mention the obvious: Write valid HTML?

Thank you all for the feedback!


Error not rendering

I have this code inside a composer to render an error in my app. I'm successfully entering the if statement and printing the error to the console. But for some reason, the error is not rendering in place of the component. Instead, my app continually displays the loading component.
Any ideas?
  console.log('here');
  if (notPermitted) {
    const error = new Error(`You do not have the correct permissions`);
    console.log(error);
    onData(error);
  }

Could you try that with v2? (Check README)
Reopen with more info.