feat: BadUrlError

Description of the change
This pr adds BadUrlError, just like in Elm
https://github.com/elm/http/blob/34a9a27411c2492d3e247ac75cd48e22b473bef5/src/Http.elm#L539
which is thrown during xhr.open https://github.com/elm/http/blob/34a9a27411c2492d3e247ac75cd48e22b473bef5/src/Elm/Kernel/Http.js#L33
thought I wasn't been able to reproduce this, instead for me on spago test it was thrown on xhr.send
the error we are handling is (check first commit https://github.com/srghma/purescript-affjax/commit/0d30f28502eeb410074abe0f421757535ef59af6)
TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
    at new NodeError (node:internal/errors:363:5)
    at new ClientRequest (node:_http_client:154:13)
    at Object.request (node:http:96:10)
    at XMLHttpRequest._sendHxxpRequest (/home/srghma/projects/purescript-affjax/node_modules/xhr2/lib/xhr2.js:480:24)
    at XMLHttpRequest._sendHttp (/home/srghma/projects/purescript-affjax/node_modules/xhr2/lib/xhr2.js:460:14)
    at XMLHttpRequest.send (/home/srghma/projects/purescript-affjax/node_modules/xhr2/lib/xhr2.js:278:18)
    at /home/srghma/projects/purescript-affjax/output/Affjax/foreign.js:89:13
    at __do (/home/srghma/projects/purescript-affjax/output/Effect.Aff.Compat/index.js:15:22)
    at runAsync (/home/srghma/projects/purescript-affjax/output/Effect.Aff/foreign.js:98:20)
    at run (/home/srghma/projects/purescript-affjax/output/Effect.Aff/foreign.js:333:22) {
  code: 'ERR_UNESCAPED_CHARACTERS'
}

i'm not sure about this change

Checklist:

[ ] Added the change to the changelog's "Unreleased" section with a link to this PR and your username
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation in the README and/or documentation directory
[ ] Added a test for the contribution (if applicable)

TODO: add test to node and web
or maybe check my error code? ERR_UNESCAPED_CHARACTERS
    A.log "Testing invalid url"
    AX.get ResponseFormat.string "/фыва" >>= assertLeft >>= case _ of
       AX.BadUrlError url → assertEq "/фыва" url
       other → logAny' other *> assertFail "Expected a BadUrlError"

let errorRef = null
function simulateBadUrlError() {
  const XMLHttpRequest = require('xhr2');
  const xhr = new XMLHttpRequest();
  const badUrl = 'http://example.com/фіва';
  xhr.open('GET', badUrl, true);
  xhr.onerror = function (e) { console.error('Request failed', e); errorRef = e; };
  try {
    xhr.send();
  } catch (e) {
    console.error('Caught Error in send():', e); errorRef = e;
  }
}
simulateBadUrlError();

Caught Error in send(): TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
    at new ClientRequest (node:_http_client:184:13)
    at Object.request (node:http:102:10)

> errorRef.code
'ERR_UNESCAPED_CHARACTERS'

but returns success in browser

even this doesnt throw our error in browser
let errorRef = null
function simulateBadUrlError() {
  // const XMLHttpRequest = require('xhr2');
  const xhr = new XMLHttpRequest();
  const badUrl = 'http://  фівафіва/фіва';
  xhr.open('GET', badUrl, true);
  xhr.onerror = function (e) { console.error('Request failed', e); errorRef = e; };
  try {
    xhr.send();
  } catch (e) {
    console.error('Caught Error in send():', e); errorRef = e;
  }
}
simulateBadUrlError();

couldnt reproduce with try around open
https://github.com/elm/http/blob/34a9a27411c2492d3e247ac75cd48e22b473bef5/src/Elm/Kernel/Http.js#L30C1-L35C1
but it still makes sence to implement this error


Improve speed for printing floats with %a.

Inspired by an article from @andralex I found some speed optimizations for printing floating point numbers with %a. The idea is, to replace branches inside of a loop with arithmetics doing the same.
Some speed messurements (times in ns):

Compiler
fp type
old version with snprintf
current version
proposed version

dmd
float
414
422
408

dmd -O ...
float
421
344
306

ldc
float
520
517
465

ldc2 -O3 ...
float
292
105
105

ldc2 with DPO
float
207
103
104

dmd
double
420
504
414

dmd -O ...
double
410
406
314

ldc
double
509
593
513

ldc2 -O3 ...
double
242
106
106

ldc2 with DPO
double
216
106
105

Compilerflags for optimization with dmd where -O -release -boundscheck=off and with ldc2 they where -O3 -release -boundscheck=off -flto=full -defaultlib=phobos2-ldc-lto,druntime-ldc-lto -mcpu=native.
Seems like ldc with aggressive optimization is able to figure this out itself, while DPO only improves the use of snprintf.
(I did not manage to install a working version of gdc, so I had to skip it - maybe @ibuclaw might like to help me doing so? If yes, I'll supply times later.)
Thanks to @kinke and @Geod24 for help on ldc2 compilerflags.

@kinke Do you think, the whole PR is also pessimizing code legibility? It doesn't help ldc with optimization turned on, and the former version is better readable IMHO. I'm quite unsure, if we should add such speedups or if we should leave them for the compiler to do...

@kinke Do you think, the whole PR is also pessimizing code legibility? It doesn't help ldc with optimization turned on, and the former version is better readable IMHO. I'm quite unsure, if we should add such speedups or if we should leave them for the compiler to do...

I think it's okay.


read property 'exclude' of undefined     at applyDefaults (C:\ProjectFiles\docshala\node_modules\awesome-typescript-l oader\src\instance.ts:266:72)

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-beta.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

I am having the same issue. I have tried it with node version 7.2.1 ,6.9 and 6.3.1.

Same issue . node version 6.9.1 , npm version 4.0.3

double of #1249

Closing - Duplicate of #1249 for which the workaround has already been merged into master.


App Shell prevents Safari bottom address bar from collapsing on iOS

Current Behavior
When scrolling down a page that makes use of the App Shell with Safari on iOS with the address bar set to the bottom, the address bar doesn't collapse as it should normally. That behavior can be observed on the skeleton.dev website right now.
Expected Behavior
Address bar should collapse
Steps To Reproduce

Implement the default AppShell from https://www.skeleton.dev/components/app-shell
Add enough content for the page to be able to scroll

Link to Reproduction / Stackblitz
No response
More Information
https://github.com/skeletonlabs/skeleton/assets/18720666/1cf52959-9a16-4367-844c-b75f8f676606

@Keagel unfortunately this is one of several known issues with using the App Shell. Basically the App Shell abstracts scroll to a sub-panel within the shell, rather than allowing the entire <body> element to scroll. I've created a diagram to help visualize this:

Mobile Safari is setup to hide the bottom panel only when it detects the <body> is being scrolled, which of course never happens in the App Shell. This of course introduces the issue with Mobile Safari's bottom floating interface.
You can see some discussion around the topic here:
https://stackoverflow.com/a/75648985

Sadly I don't think there's anyway to get the behavior you're asking while using the App Shell. Even setting different height values doesn't help here, because the <body> never scrolls. For example, you can try something like:
<AppShell class="!h-[100sh]">
	<!-- ... -->
</AppShell>

If you prefer the bottom panel to auto-hide on scroll, then I recommend you move away from the App Shell and create your own custom layout which leans into the body scroll. While a bit more effort, it will help avoid some other common App Shell related issues:

Pull down to refresh not working on mobile (may be Android only)
Print styles not working as expected
Plus a few niche a11y issues

Furthermore, given these issues, we're actually taking a pretty hard stance on not bringing the App Shell forward to Skeleton v3. We're going to make the recommendation that folks construct their own custom layouts. That way they can fulfill any requirements they might have.
Hope this helps, and sorry we can't do more!

For now I'm not bothered by the bottom panel staying visible but I'll make the necessary changes since the App Shell won't be coming to v3. Thanks for the thorough answer!


steam _find_info fails when the keys are in lowercase

hi @BuongiornoTexas ,
looks like the keys in config/loginusers.vdf are not guaranteed to be in camel case
eg:
{
	<# removed in case it's sensitive>
	{
		"accountname"		"#"
		"PersonaName"		"JustinAiken"
		"RememberPassword"		"1"
		"Timestamp"		"1556751550"
		"WantsOfflineMode"		"0"
		"SkipOfflineModeWarning"		"0"
		"mostrecent"		"1"
	}
}

stack trace
Traceback (most recent call last):
  File "/usr/local/bin/importrsm", line 6, in <module>
    from rsrtools.importrsm import main
  File "/usr/local/lib/python3.7/site-packages/rsrtools/importrsm.py", line 21, in <module>
    from rsrtools.songlists.database import ArrangementDB
  File "/usr/local/lib/python3.7/site-packages/rsrtools/songlists/database.py", line 40, in <module>
    from rsrtools.files.profilemanager import RSProfileManager, JSON_path_type
  File "/usr/local/lib/python3.7/site-packages/rsrtools/files/profilemanager.py", line 1016, in <module>
    class RSProfileManager:
  File "/usr/local/lib/python3.7/site-packages/rsrtools/files/profilemanager.py", line 1100, in RSProfileManager
    _steam_accounts: SteamAccounts = SteamAccounts()
  File "/usr/local/lib/python3.7/site-packages/rsrtools/files/steam.py", line 191, in __init__
    self._account_info = self._find_info()
  File "/usr/local/lib/python3.7/site-packages/rsrtools/files/steam.py", line 263, in _find_info
    name = login_info["AccountName"]
KeyError: 'AccountName'

cc @JustinAiken, more info in https://github.com/sandiz/rs-manager/issues/58#issuecomment-489213328

Closed in 0.2.1.


uv run displays an incorrect list of commands

When executing uv run, a list of available commands is shown. python and python3 work fine, but other commands list do not. I don't think uv should be shipping with pip, etc so the provided command list seems wrong.
I tried using different Python version (e.g. -p 3.12) but the results were the same.
Listing commands
⋊> ~> uv -v run
DEBUG uv 0.5.4 (c62c83c37 2024-11-20)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for default Python interpreter in virtual environments or managed installations
DEBUG Searching for managed installations at `Library/Application Support/uv/python`
DEBUG Found managed installation `cpython-3.13.0-macos-aarch64-none`
DEBUG Found `cpython-3.13.0-macos-aarch64-none` at `/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13` (managed installations)
DEBUG Using Python 3.13.0 interpreter at: /Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
Provide a command or script to invoke with `uv run <command>` or `uv run <script>.py`.

The following commands are available in the environment:

- idle3
- idle3.13
- pip
- pip3
- pip3.13
- pydoc3
- pydoc3.13
- python
- python3
- python3-config
- python3.13
- python3.13-config

See `uv run --help` for more information.

Running python - OK
python3 works as well.
⋊> ~> uv -v run python
DEBUG uv 0.5.4 (c62c83c37 2024-11-20)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for default Python interpreter in virtual environments or managed installations
DEBUG Searching for managed installations at `Library/Application Support/uv/python`
DEBUG Found managed installation `cpython-3.13.0-macos-aarch64-none`
DEBUG Found `cpython-3.13.0-macos-aarch64-none` at `/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13` (managed installations)
DEBUG Using Python 3.13.0 interpreter at: /Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
DEBUG Running `python`
Python 3.13.0 (main, Oct  7 2024, 23:47:22) [Clang 18.1.8 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

Running pydoc3 - FAIL
pip, pip3, idle3, etc fail as well.
⋊> ~> uv -v run pydoc3
DEBUG uv 0.5.4 (c62c83c37 2024-11-20)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for default Python interpreter in virtual environments or managed installations
DEBUG Searching for managed installations at `Library/Application Support/uv/python`
DEBUG Found managed installation `cpython-3.13.0-macos-aarch64-none`
DEBUG Found `cpython-3.13.0-macos-aarch64-none` at `/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13` (managed installations)
DEBUG Using Python 3.13.0 interpreter at: /Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
DEBUG Running `pydoc3`
/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/pydoc3: line 2: /Users/gustavo/Library
Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13: No such file or directory
/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/pydoc3: line 2: exec: /Users/gustavo/Library
Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13: cannot execute: No such file or directory
DEBUG Command exited with code: 126

Hm I can't reproduce this
❯ uv run -v
DEBUG uv 0.5.3 (56d362208 2024-11-19)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for default Python interpreter in virtual environments, managed installations, or search path
DEBUG Searching for managed installations at `/Users/zb/.local/share/uv/python`
DEBUG Found managed installation `cpython-3.13.0-macos-aarch64-none`
DEBUG Found `cpython-3.13.0-macos-aarch64-none` at `/Users/zb/.local/share/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13` (managed installations)
DEBUG Using Python 3.13.0 interpreter at: /Users/zb/.local/share/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
Provide a command or script to invoke with `uv run <command>` or `uv run <script>.py`.

The following commands are available in the environment:

- idle3
- idle3.13
- pip
- pip3
- pip3.13
- pydoc3
- pydoc3.13
- python
- python3
- python3-config
- python3.13
- python3.13-config

See `uv run --help` for more information.
❯ uv run python3.13
Python 3.13.0 (main, Oct 16 2024, 08:05:40) [Clang 18.1.8 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
KeyboardInterrupt
>>>
❯ uv run pydoc3
pydoc - the Python documentation tool

pydoc3 <name> ...
    Show text documentation on something.  <name> may be the name of a
    Python keyword, topic, function, module, or package, or a dotted
    reference to a class or function within a module or module in a
    package.  If <name> contains a '/', it is used as the path to a
    Python source file to document. If name is 'keywords', 'topics',
    or 'modules', a listing of these things is displayed.

pydoc3 -k <keyword>
    Search for a keyword in the synopsis lines of all available modules.

pydoc3 -n <hostname>
    Start an HTTP server with the given hostname (default: localhost).

pydoc3 -p <port>
    Start an HTTP server on the given port on the local machine.  Port
    number 0 can be used to get an arbitrary unused port.

pydoc3 -b
    Start an HTTP server on an arbitrary unused port and open a web browser
    to interactively browse documentation.  This option can be used in
    combination with -n and/or -p.

pydoc3 -w <name> ...
    Write out the HTML documentation for a module to a file in the current
    directory.  If <name> contains a '/', it is treated as a filename; if
    it names a directory, documentation is written for all the contents.

 /
❯ uv run pip3 --version
pip 24.1.2 from /Users/zb/.local/share/uv/python/cpython-3.13.0-macos-aarch64-none/lib/python3.13/site-packages/pip (python 3.13)

The binaries (pydoc3, etc) were present in the installation directory (~/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/) but uv failed to find them. I updated the issue description to clarify that.
I believe this is somewhat related to #5806 and perhaps with the whitespace in Application Support not being properly escaped somehow.
I can reproduce this consistently on macOS using this:
> rm -rf ~/.local/share/uv
> rm -rf ~/Library/Application\ Support/uv/
> mkdir -p ~/Library/Application\ Support/uv
> uv -v --python-preference only-managed run --python 3.13.0 pydoc3

Output:
DEBUG uv 0.5.4 (c62c83c37 2024-11-20)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for Python 3.13.0 in virtual environments or managed installations
DEBUG Searching for managed installations at `Library/Application Support/uv/python`
DEBUG Requested Python not found, checking for available download...
DEBUG Acquired lock for `Library/Application Support/uv/python`
DEBUG Using request timeout of 30s
INFO Fetching requested Python...
DEBUG Downloading https://github.com/indygreg/python-build-standalone/releases/download/20241016/cpython-3.13.0%2B20241016-aarch64-apple-darwin-install_only_stripped.tar.gz to temporary location: /Users/gustavo/Library/Application Support/uv/python/.cache/.tmptaZksd
DEBUG Extracting cpython-3.13.0%2B20241016-aarch64-apple-darwin-install_only_stripped.tar.gz
DEBUG Moving /Users/gustavo/Library/Application Support/uv/python/.cache/.tmptaZksd/python to Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none
DEBUG Released lock at `/Users/gustavo/Library/Application Support/uv/python/.lock`
DEBUG Using Python 3.13.0 interpreter at: /Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
DEBUG Running `pydoc3`
/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/pydoc3: line 2: /Users/gustavo/Library
Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13: No such file or directory
/Users/gustavo/Library/Application Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/pydoc3: line 2: exec: /Users/gustavo/Library
Support/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13: cannot execute: No such file or directory
DEBUG Command exited with code: 126

Note that if ~/Library/Application\ Support/uv/ doesn't exist, the issue goes away:
> rm -rf ~/Library/Application\ Support/uv/
> uv -v --python-preference only-managed run --python 3.13.0 pydoc3

DEBUG uv 0.5.4 (c62c83c37 2024-11-20)
DEBUG No project found; searching for Python interpreter
DEBUG Searching for Python 3.13.0 in virtual environments or managed installations
DEBUG Searching for managed installations at `.local/share/uv/python`
DEBUG Requested Python not found, checking for available download...
DEBUG Acquired lock for `.local/share/uv/python`
DEBUG Using request timeout of 30s
INFO Fetching requested Python...
DEBUG Downloading https://github.com/indygreg/python-build-standalone/releases/download/20241016/cpython-3.13.0%2B20241016-aarch64-apple-darwin-install_only_stripped.tar.gz to temporary location: /Users/gustavo/.local/share/uv/python/.cache/.tmp2Z3nJ4
DEBUG Extracting cpython-3.13.0%2B20241016-aarch64-apple-darwin-install_only_stripped.tar.gz
DEBUG Moving /Users/gustavo/.local/share/uv/python/.cache/.tmp2Z3nJ4/python to .local/share/uv/python/cpython-3.13.0-macos-aarch64-none
DEBUG Released lock at `/Users/gustavo/.local/share/uv/python/.lock`
DEBUG Using Python 3.13.0 interpreter at: /Users/gustavo/.local/share/uv/python/cpython-3.13.0-macos-aarch64-none/bin/python3.13
DEBUG Running `pydoc3`
pydoc - the Python documentation tool

pydoc3 <name> ...
    Show text documentation on something.  <name> may be the name of a
    Python keyword, topic, function, module, or package, or a dotted
    reference to a class or function within a module or module in a
    package.  If <name> contains a '/', it is used as the path to a
    Python source file to document. If name is 'keywords', 'topics',
    or 'modules', a listing of these things is displayed.

pydoc3 -k <keyword>
    Search for a keyword in the synopsis lines of all available modules.

pydoc3 -n <hostname>
    Start an HTTP server with the given hostname (default: localhost).

pydoc3 -p <port>
    Start an HTTP server on the given port on the local machine.  Port
    number 0 can be used to get an arbitrary unused port.

pydoc3 -b
    Start an HTTP server on an arbitrary unused port and open a web browser
    to interactively browse documentation.  This option can be used in
    combination with -n and/or -p.

pydoc3 -w <name> ...
    Write out the HTML documentation for a module to a file in the current
    directory.  If <name> contains a '/', it is treated as a filename; if
    it names a directory, documentation is written for all the contents.

DEBUG Command exited with code: 0

Interesting, thanks. (We no longer write there by default IIRC but it's preserved for backwards compatibility.)

I think it must be an issue with the shebang that's being used in python-build-standalone (upstream)?

Filed: https://github.com/indygreg/python-build-standalone/issues/394. Should be an easy fix.

And now a PR here: https://github.com/indygreg/python-build-standalone/pull/395. I think that's right?

Thanks!
If anyone else hits this until it's fixed upstream, the quick fix is to simply delete your ~/Library/Application Support and reinstall any necessary Python versions in the new default location (~/.local/share/uv).

This is fixed upstream, but we need to release it there and here still.


bash: hash mismatch?

Describe the bug
I tried to nix build .#xapian --offline --rebuild because of #298828 and got a hash mismatch for the bash derivation:
error: hash mismatch in fixed-output derivation '/nix/store/5jrd75v747s76s16zxk59384xfcjqn58-bash-5.2.tar.gz.drv':
         specified: sha256-oTnBZt9/9EccXgczBRZC7lVWwcyKSnjxRVg8XIGrMvs=
            got:    sha256-0ofL38Lr0XXVdJAbqpJb2oCQelqqUmG2z6JLdIRjUkE=
error: 1 dependencies of derivation '/nix/store/1fvk81nk6b0zvcrn14whs2c3zn9pbq0q-bash-5.2p26.drv' failed to build
error: 1 dependencies of derivation '/nix/store/nhjzpkf3mp8cana2769sapgkyviyrb1w-bash-5.2p26.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rx8nvf07w150qpnj2b33fvrvli61xk6j-bash-5.2p26.drv' failed to build
error: 1 dependencies of derivation '/nix/store/vkz515grgl3dakz3n8qc7zz2ww3yaljk-bash-5.2p26.drv' failed to build
error (ignored): error: cannot unlink '/tmp/nix-build-perl-5.38.2.drv-0/perl-5.38.2': Directory not empty
error: 1 dependencies of derivation '/nix/store/6g8pm5l0g8y05sqia9d0j1xdvdif2avk-autoconf-2.72.tar.xz.drv' failed to build
error: 1 dependencies of derivation '/nix/store/p5y13bnrsb3vjl66m7dq8mvdlwikfmgm-automake-1.16.5.tar.xz.drv' failed to build
error: 1 dependencies of derivation '/nix/store/pb22q0s864syfqrzv22clvkvv933mfma-gnum4-1.4.19.drv' failed to build
error: 1 dependencies of derivation '/nix/store/q6s4pv3ck6qrhzilcwll41jpvsl14dbk-install-shell-files.drv' failed to build
error: 1 dependencies of derivation '/nix/store/rkxzihjaskwm8b598575awyq388v9b8h-libtool-2.4.7.drv' failed to build
error: 1 dependencies of derivation '/nix/store/ix0fw97g0qrlsdalpvwxvybbnmnciwpf-linux-pam-1.6.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/jvx31y3f5pal2clcvh0lwym3d7iy8nr5-autoreconf-hook.drv' failed to build
error: 1 dependencies of derivation '/nix/store/p86l093gmrzhci3h4ac13j1b04xb2zl1-xapian-1.4.25.drv' failed to build

Steps To Reproduce
Steps to reproduce the behavior:

git fetch https://github.com/nixos/nixpkgs master
git checkout ea37b82acd5737fa9f250f1452afafc3903ba4f7
nix build .#xapian --offline --rebuild

Notify maintainers
@dtzWill
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.77, NixOS, 23.11 (Tapir), 23.11.git.878ef7d9721b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/var/src/nixpkgs`

Add a :+1: reaction to issues you find important.

It seems like the gnu ftpmirror site is down? The hash does match if I try another local mirror.

ftpmirror is back up, and the bash hash matches as expected.


sqlsmith: ignoring failing queries in snapshot

Background
Previously suggested by @fuyufjh https://github.com/risingwavelabs/risingwave/pull/7967#discussion_r1116474526
When writing new features, some new bugs may be discovered. Then, either we have to disable these new features, or disable other related features which trigger the bug.
For example, when adding #3844, we have to disable query, replace it with simple_query, and perhaps also disable FULL OUTER JOIN. Alternatively, we have to disable the newly added feature.
Sometimes it is not clear which features should be disabled (or if any can even be reasonably disabled), so have no choice but to disable new feature.
Our workflow can be instead: Enable features, leave out failing queries from the test set, but still track them.
Design
CI workflow

PR workflow: Use pre-generated + execute.
Main workflow: Use pre-generated + execute.
Cron workflow: Use pre-generated + execute.

Use a larger snapshot for cron.
We can always generate more queries for main-cron.
New sqlsmith logic
Generate as per normal, if some query fails, terminate generation there, comment the failing query out.
Skip the rest.
@fuyufjh: Use new runs to make up the rest of it.
Disabling priority

Easy to disable in sqlsmith, doesn't affect much -> disable in sqlsmith.
Hard to disable in sqlsmith / could affect query gen significantly AND does not skip too many queries -> disable in snapshot.
Otherwise, block on it, should probably fix the bug first.

Future Optimizations
Sqlsmith can recover when it encounters query which cause crash:

Record failing query
Restart cluster
Re-run DDL + DML again.
Continue generation.

For execution of pre-generated queries, logic remains the same, no queries should fail, since the failing ones are already commented out.
If too many queries to recover, it can take a long time to generate a proper query set. In which case we should fail and disable the new feature.
Discussions

This approach adds operational overhead sqlsmith. Need to maintain snapshot + schedule it.
Seems easier to just disable/enable some feature in sqlsmith, than track multiple queries. Asking developers to manually uncomment queries won't scale, if we choose to increase snapshot size. We can expose weights of generating various expressions to make it easy for developers to disable / enable.

Maintain snapshot is actually easy, can just do via buildkite. Schedule it is not needed. Just run manually.

Increasing throughput of bugs found won't really be of much help when bottlenecked by bug fixing rate.

Yes, but sqlsmith development is affected by these bugs.

This also requires significant refactoring to be of use (see future optimizations). There's more important sqlsmith features to support, prefer to go with simpler approach: Disable other features which are not well supported.

There's already alternative ways suggested, we don't necessarily have to restart cluster.

The underlying issue is that it may be hard to find what is root cause, so we know the smallest thing to disable. I think pretty print + shrink will go a long way in helping to discover that.

Sure, but don't even have to find root cause if we use snapshot.

If we disable in sqlsmith instead, then we don't even have to maintain a snapshot. I think in most cases it is possible to do so. In the case of gen inserts we can easily disable FULL OUTER JOIN.

Still takes time to find root cause.

Perhaps adding a separate job for sqlsmith in buildkite, which can fail as suggested by @lmatz previously, so it doesn't block main-cron as well.

Ignore, main-cron can just use pre-generated queries.
Q&A
Q: Where to store snapshot queries?
A: Do not version control, leads to large diffs. Just store on s3 / buildkite.
Q: Why not decouple generation and execution?
A: Less to refactor. We can do that later.
Q: Why main-cron must use snapshot approach too?
A: There are some errors which are avoided by excluding from snapshot. To replicate this, main-cron should use snapshot approach too. Additionally, we can stabilize main-cron too, and still have good coverage by generating larger query set.
Q: Can't we just follow the original approach suggested? Just generate first, execute and ignore failing queries later?
A: Not really. When a query fails, if it is just due to unexpected error, we can continue execution. However, sometimes it can cause cluster to crash. When that happens sqlsmith will need to restart cluster, rerun ddl + dml. This is currently not supported in sqlsmith. We can leave it as a future optimization first.

Track by https://github.com/risingwavelabs/risingwave/issues/8284.


371 pjg update setup demos

@doutriaux1 with the master and edits to .travis.yml in this branch it's now got conflicts - if I keep going it's just going to get even more tangled so handing it over to you..

no problem.

@doutriaux1 PG to prepare demos.   Once that is done CD to ensure they map properly into conda

@doutriaux1 @durack1  In order for PG to follow through with demo we need to get this PR corrected/merged so the rest of the demos can follow from it...

@doutriaux1 closing this PR because it is partially redundant with https://github.com/PCMDI/pcmdi_metrics/pull/376


Supports guarantees around immutability/identity of clusters in list

/sig multicluster
The cluster registry should provide a way to guarantee that a cluster that has been added has not been changed out for another cluster at the same IP address. This could be via a certificate stored in the cluster that a controller validates against the registry, and that can be provided to the user to validate against the cluster in a defined way.
From https://github.com/kubernetes/community/blob/master/contributors/design-proposals/multicluster/cluster-registry/project-design-and-plan.md#later

/remove-lifecycle stale


Add support for MIPS Assembler

Could you add support for MCB32 mips assembler?
(MIPS is a popular teaching variant of assembler)

Does it have a dedicated atom grammar?

@nixel2007  like this one?

@Olian04 yeah, it's good.
Could you provide some command to run current file through MCB32? Lets say, that the executable is in the PATH already.

@nixel2007
(I'm still rather new to MCB32)
But this project works.
And this is the way I've been using it is:
0. Install MCB32

Call . /opt/mcb32tools/environment
Cd to file path
Call make

@nixel2007
Better aswere this time:
You can interpret MIPS wither using Mars -> java -jar mars.jar nc <input-file>, or SPIM -> spim, xspim, pcspim.


Possible issue in ownership script

Hi
Since the update overnight, my firefox app had stopped working.
It looks like it's this script running causing the issue:

This keeps erroring:

Believe it might be down to something in the script. The files it was trying to change already were set to GUID of 1000.
Firefox was working fine yesterday with same config.

Taking the volume out fixes it. I will say though it is a great update so far with the scaling. Keep it up! :)
Cheers
Chris

Thanks foe reporting.  What kind of folder is TrueNAS-Downloads?  Is it an SMB share?

It's an NFS share, it was working fine pre-update.

Fixed in latest image.


Exception when running twice 'No current assignment for partition xxx-0'

Hi there!
Was trying to use sink-pg-json, and noticed something.
When i run the connect in standalone mode, with the pretty much the default options:
name=prueba-connector-postgresql-standalone_v3
connector.class=com.justone.kafka.sink.pg.json.PostgreSQLSinkConnector
tasks.max=1
topics=hola
db.host=localhost
db.database=kafka
db.username=postgres
db.schema=web
db.table=event
db.columns=hola
db.json.parse=/@hola
db.buffer.size=1
db.delivery=synchronized

It works well the first time:
INFO Created connector prueba-connector-postgresql-standalone_v3 (org.apache.kafka.connect.cli.ConnectStandalone:91)
INFO Sink task WorkerSinkTask{id=prueba-connector-postgresql-standalone_v3-0} finished initialization and start (org.apache.kafka.connect.runtime.WorkerSinkTask:208)

INFO Discovered coordinator localhost:9092 (id:<PHONE_NUMBER> rack: null) for group connect-prueba-connector-postgresql-standalone_v3. (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:505)
INFO Revoking previously assigned partitions [] for group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:280)
INFO (Re-)joining group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:326)
INFO Successfully joined group connect-prueba-connector-postgresql-standalone_v3 with generation 1 (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:434)
INFO Setting newly assigned partitions [hola-0] for group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:219)

But then, when Ctrl+C and run exactly the same again, i see the following message:
INFO Created connector prueba-connector-postgresql-standalone_v3 (org.apache.kafka.connect.cli.ConnectStandalone:91)
INFO Sink task WorkerSinkTask{id=prueba-connector-postgresql-standalone_v3-0} finished initialization and start (org.apache.kafka.connect.runtime.WorkerSinkTask:208)
ERROR Task prueba-connector-postgresql-standalone_v3-0 threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:142)
java.lang.IllegalStateException: No current assignment for partition hola-0
    at org.apache.kafka.clients.consumer.internals.SubscriptionState.assignedState(SubscriptionState.java:231)
    at org.apache.kafka.clients.consumer.internals.SubscriptionState.seek(SubscriptionState.java:256)
    at org.apache.kafka.clients.consumer.KafkaConsumer.seek(KafkaConsumer.java:1134)
    at org.apache.kafka.connect.runtime.WorkerSinkTask.rewind(WorkerSinkTask.java:405)
    at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:214)
    at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:170)
    at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:142)
    at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:140)
    at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:175)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
ERROR Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask:143)

The Exception comes from here
So, when i delete the state in the database like this:
DELETE from "$justone$kafka$connect$sink"."web.event";

Then, it runs smoothly again.
Im pretty new to kafka and kafka-connect, there is a high probability im doing something wrong.
Is it something im missing or is this an expected behaviour?
Thanks!!

Hi Philip,
Thanks for the note. It's probably a bug. I will take a look when I am back
at work (next week).
Thanks
Duncan
On 11 Aug 2016 1:05 a.m., "Phillip Neumann"<EMAIL_ADDRESS>wrote:

Hi there!
Was trying to use sink-pg-json, and noticed something.
When i run the connect in standalone mode, with the pretty much the
default options:
name=prueba-connector-postgresql-standalone_v3
connector.class=com.justone.kafka.sink.pg.json.PostgreSQLSinkConnector
tasks.max=1
topics=hola
db.host=localhost
db.database=kafka
db.username=postgres
db.schema=web
db.table=event
db.columns=hola
db.json.parse=/@hola
db.buffer.size=1
db.delivery=synchronized
It works well the first time:
INFO Created connector prueba-connector-postgresql-standalone_v3 (org.apache.kafka.connect.cli.ConnectStandalone:91)
INFO Sink task WorkerSinkTask{id=prueba-connector-postgresql-standalone_v3-0} finished initialization and start (org.apache.kafka.connect.runtime.WorkerSinkTask:208)
INFO Discovered coordinator localhost:9092 (id:<PHONE_NUMBER> rack: null) for group connect-prueba-connector-postgresql-standalone_v3. (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:505)
INFO Revoking previously assigned partitions [] for group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:280)
INFO (Re-)joining group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:326)
INFO Successfully joined group connect-prueba-connector-postgresql-standalone_v3 with generation 1 (org.apache.kafka.clients.consumer.internals.AbstractCoordinator:434)
INFO Setting newly assigned partitions [hola-0] for group connect-prueba-connector-postgresql-standalone_v3 (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:219)
But then, when Ctrl+C and run exactly the same again, i see the following
message:
INFO Created connector prueba-connector-postgresql-standalone_v3 (org.apache.kafka.connect.cli.ConnectStandalone:91)
INFO Sink task WorkerSinkTask{id=prueba-connector-postgresql-standalone_v3-0} finished initialization and start (org.apache.kafka.connect.runtime.WorkerSinkTask:208)
ERROR Task prueba-connector-postgresql-standalone_v3-0 threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:142)
java.lang.IllegalStateException: No current assignment for partition hola-0
at org.apache.kafka.clients.consumer.internals.SubscriptionState.assignedState(SubscriptionState.java:231)
at org.apache.kafka.clients.consumer.internals.SubscriptionState.seek(SubscriptionState.java:256)
at org.apache.kafka.clients.consumer.KafkaConsumer.seek(KafkaConsumer.java:1134)
at org.apache.kafka.connect.runtime.WorkerSinkTask.rewind(WorkerSinkTask.java:405)
at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:214)
at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:170)
at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:142)
at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:140)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:175)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
ERROR Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask:143)
The Exception comes from here
https://www.codatlas.com/github.com/apache/kafka/0.10.0/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/WorkerTask.java?line=142
So, when i delete the state in the database like this:
DELETE from "$justone$kafka$connect$sink"."web.event";
Then, it runs smoothly again.
Im pretty new to kafka and kafka-connect, there is a high probability im
doing something wrong.
Is it something im missing or is this an expected behaviour?
Thanks!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/justonedb/kafka-sink-pg-json/issues/2, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA-W475-skZaXgdgYAegELL_RQ2gzeGVks5qemdOgaJpZM4JhsgZ
.

#5 up for this

Hi,
I have the same issue, but i dont have this table
"$justone$kafka$connect$sink"."web.event";
I only one temp table in this schema (the copy from myschema.mytable).
What other workaround can i do?
Thanks
Shannon

Hi Shannon,
The state table "$justone$kafka$connect$sink"."web.event" is only created
if db.delivery is set to "synchronized" in the connector properties file.
Is it set to "synchronized"?
If you can send me your property files and table schema I can take a look
and see if I can re-create the problem.
Thanks
Duncan
On Wed, Oct 26, 2016 at 10:48 PM, Shannon Ma<EMAIL_ADDRESS>wrote:

Hi,
I have the same issue, but i dont have this table
"$justone$kafka$connect$sink"."web.event";
I only one temp table in this schema (the copy from myschema.mytable).
What other workaround can i do?
Thanks
Shannon
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/justonedb/kafka-sink-pg-json/issues/2#issuecomment-256487417,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-W4zO_dfXxCVFzI73G2cD9f8dBEC7Sks5q38qngaJpZM4JhsgZ
.

Sometimes after rebalance I found the same exception:
[2017-03-23 14:43:04,313] ERROR Task ${task-name}-1 threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:142)
java.lang.IllegalStateException: No current assignment for partition ml-logs-0
        at org.apache.kafka.clients.consumer.internals.SubscriptionState.assignedState(SubscriptionState.java:251)
        at org.apache.kafka.clients.consumer.internals.SubscriptionState.seek(SubscriptionState.java:276)
        at org.apache.kafka.clients.consumer.KafkaConsumer.seek(KafkaConsumer.java:1132)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.rewind(WorkerSinkTask.java:416)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:214)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:170)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:142)
        at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:140)
        at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:175)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
[2017-03-23 14:43:04,313] ERROR Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask:143)

Can you advice something? (I use HDFS Connector)
P.S. I saw how task for this partition moved to another Worker, but Status (by REST call) shows that task in state FAILED.


Potential fix for the 2.2km

@crangelsmith does this work with your set up?

Fix this for different variables!

i'll merge this to the data loader branch.


Dynload

Unify tensorflow and tensorflow_gpu into single package
See #22562 and #16184
As a person who started all that (original patch here) I will take it to the finish line, hopefully.

Nagging Reviewer @Artem-B, @yifeif, @timshen91: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Is this patch still relevant?

@yifeif Do we still need this patch, or should we close the PR?

All the explicit dependency of cuda has been removed from core. @pkit I'll close this PR. If you are looking into removing the rest, let's open discuss in a new thread/PR. @gunan is also looking into dynamically load the kernels, so we might not need to wrap kernel's cuda usage.

@yifeif originally I needed only the libcuda out. Any additional things were just "nice to have", to make the deploy easier. So I'm good for now.


Add Schema for non empty collections

fixes #717
/claim #717

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Batch AI .Net SDKs related to swagger typo fix

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@lliimsft please update the branch
also please confirm you wish to bump the major version for this package

I confirmed that we wish to bump the major version for this package

@lliimsft LGTM please merge all commits into a single commit and update the PR, will merge once done

@lliimsft Please address comments soon. WIll close the PR by end of week if there is no activity

@lliimsft please open a new PR with all the comments addressed. Especially have your commit history clean.
We have lots of issues with merge commits and so we discourage not to have them.
This PR has been open for a while and will be closed.


Fix INA transport URL - RabbitMqClusterName

Ironic Neutron Agent was broken because the transport URL was created without setting the RabbitMqClusterName - causing the transport secret to never reconcile successfully.
Add RabbitMqClusterName back to IronicNeutronAgentSpec and set it in ironic controller the same way it is done for inspector.

Current architecture supports using different rabbitmq cluster for neutron and ironic, thus we should not always rely on the one used in ironic. That's because I kept the independent spec in INA.

Current architecture supports using different rabbitmq cluster for neutron and ironic, thus we should not always rely on the one used in ironic. That's because I kept the independent spec in INA.

I belive that would be true for ironic and ironic-inspector as well, they can use separate rabbitmq clusters as well.
The issue I am seeing without  this patch is basically that the transport for INA is never created, because the spec has empty string for Rabbitmq Cluster Name. I notice now this is not the case for kuttle tests on other PR's.
Converting this to Draft, it might be some mistake in my config.
$ oc describe transporturls.rabbitmq.openstack.org ironic-ironic-neutron-agent-transport
Name:         ironic-ironic-neutron-agent-transport
Namespace:    openstack
Labels:       <none>
Annotations:  <none>
API Version:  rabbitmq.openstack.org/v1beta1
Kind:         TransportURL
Metadata:
  Creation Timestamp:  2023-08-02T12:41:11Z
  Generation:          1
  Managed Fields:
    API Version:  rabbitmq.openstack.org/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:ownerReferences:
          .:
          k:{"uid":"02969e35-77d1-4329-9d19-cca1fdcf7331"}:
      f:spec:
        .:
        f:rabbitmqClusterName:
    Manager:      manager
    Operation:    Update
    Time:         2023-08-02T12:41:11Z
    API Version:  rabbitmq.openstack.org/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
    Manager:      manager
    Operation:    Update
    Subresource:  status
    Time:         2023-08-02T12:41:12Z
  Owner References:
    API Version:           ironic.openstack.org/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  IronicNeutronAgent
    Name:                  ironic-ironic-neutron-agent
    UID:                   02969e35-77d1-4329-9d19-cca1fdcf7331
  Resource Version:        900634
  UID:                     9a4b9fdf-089c-4507-bcf0-6246d9e4bb4c
Spec:
  Rabbitmq Cluster Name:
Status:
  Conditions:
    Last Transition Time:  2023-08-02T12:41:12Z
    Message:               Setup started
    Reason:                Init
    Status:                Unknown
    Type:                  Ready
    Last Transition Time:  2023-08-02T12:41:11Z
    Message:               TransportURL not configured
    Reason:                Init
    Status:                Unknown
    Type:                  TransportURLReady
Events:                    <none>

I have to check how CRs are defined when the issue is reproduced by very rough guess is that webhook is defaulting the spec to "" and that is bypassing the Required check.
If that is true then we probably have to convert String to String*, but I'd rather suggest we seriously consider allowing omitempty with required values considering the several problems caused by "additional" rule we are forcing ...

I have to check how CRs are defined when the issue is reproduced by very rough guess is that webhook is defaulting the spec to "" and that is bypassing the Required check.
If that is true then we probably have to convert String to String*, but I'd rather suggest we seriously consider allowing omitempty with required values considering the several problems caused by "additional" rule we are forcing ...

I belive your theory here is correct. The difference between samples and the config I used is that samples define ironicNeutronAgent: {} - I did not have ironicNeutronAgent at all expecting it do default correctly. When I add ironicNeutronAgent: {} to my config I don't have the issue.
Closing this PR.


Adding AiKit quickstart

Signed-off-by: Abolfazl Shahbazi<EMAIL_ADDRESS>This PR adds 'ConsoleQuickStart' kind for `oneAPI AiKit'.

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message
[x] JIRA link(s): https://issues.redhat.com/browse/RHODS-1820
[ ] The Jira story is acked
[ ] An entry has been added to the latest build document in Build Announcements Folder.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious)

@jeff-phillips-18 and @cfchase would you please review and let me know?
Thanks.

Thanks @jeff-phillips-18 and @Jooho
I'm updating this now.

All comments are addressed now.

@jeff-phillips-18 and @Jooho please let me know if you have any other changes in mind otherwise feel free to merge.

LGTM. If @Jooho agrees, we can merge.


Pasted code into DartPad needs manual formatting

If I copy correctly formatted code and paste it into DartPad, I have to manually re-format the code.

We have access to the formatter on the back-end, but haven't exposed it in the UI.
I'd like a subtle way to do this, so that it's not necessarily always available. Or perhaps the dart tab should always have a format button visible, next to the run button?

A format button is fine, but why not make it automatic, similar to Dart
Editor?
On Tue, May 19, 2015 at 7:09 PM, Devon Carew<EMAIL_ADDRESS>wrote:

We have access to the formatter on the back-end, but haven't exposed it in
the UI.
I'd like a subtle way to do this, so that it's not necessarily always
available. Or perhaps the dart tab should always have a format button
visible, next to the run button?
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/dart-pad/issues/430#issuecomment-103724086.

This almost isn't the a case of the formatter, it's more 'when you paste stuff into it, normalise the whitespace etc'
In terms of UX for formatting what I'd like to do is to anytime there is an analysis run the formatter and see if the result is different from the code currently in the pad. If it is then push a quick fix for 'format code'. That way we get the UI only when it's relevant and without adding any more chrome.
We might also add a a 'format before sharing' checkbox into the share workflow.

I'd love to see the formatter automatically run on the code when you paste it in. But anything's better than losing all your spacing.

As we now have a format button I'm going to close this. I agree there are other better options for integrating into the sharing workflow, but they're not planned for now.


Explore migrating UX wrappers to tiledbsoma / SOMA

Related to #78
We need to explore if UX wrappers can be incorporated in tiledbsoma or SOMA, if we succeed on this they should be removed from cell-census if not they are to be kept

UX wrappers include:
get_anndata()
get_experiment()

get_anndata() is to be kept as it provides a UX improvement for computations biologists. get_experiment can be removed or marked for internal use (if needed) since it's functionality simpler than get_anndata()
Final list of requirements
https://docs.google.com/document/d/1sdyIFVPxXjie2r6SSKxALEABWod8rGmdDJkyyk_A8r0/edit#


Patch v3.0.1 with the changes from 2 PRs that have been already merged

Hello!
We are looking to try latest changes from master, specifically: https://github.com/DataDog/dogstatsd-ruby/pull/51 and https://github.com/DataDog/dogstatsd-ruby/pull/53, both of them are part of next milestone: https://github.com/DataDog/dogstatsd-ruby/milestone/10?closed=1
It would be awesome if you can release changes sooner, for instance, patch v3.0.1 with the changes from that PR #51 and #53!
Anatoly

cc @zippolyte as you merged them

@mikhailov We have a few more PRs we need to merge before we release. We expect to have something out in December most likely.

v3.1.0 has been released https://github.com/DataDog/dogstatsd-ruby/blob/master/CHANGELOG.md#310--20171123


fix: add undici dependency and update http headers handling

#185  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @babayacotono and the rest of your teammates on  Graphite


SQL Comment Syntax Highlighting Not Working Properly

Problem: A space is required after the SQL comment code "--" in order for the line to become a comment.
-- This Comment Works
 --This Comment does not work
Expected Outcome: anything in a line after 2 dashes ("--") should be a comment.
Current Behavior: Here is a screenshot of behavior in Brackets, all lines should be commented after the first "--"

Possible Solution: I noticed in the languages.json that sql does not have a "lineComment" specified.
Inserting the following line at line 222 of the file languates.json may fix the issue.
"lineComment": ["--"]
Version Info: I am running Windows 7 x64, Brackets Release 1.6 build 1.6.0-16680, Extensions Disabled

Hi @benzen217, I looked a bit at this issue.
Brackets at the moment is mapping sql to the mysql dialect and here it states you need a space after the two dash for mysql.
So what you see it is somewhat correct.
I tried changing languates.json but I guess the syntax highlighting come completely from codemirror.
Here you can try several sql dialects.
Finally I tried to modify languates.json to something like the following to differentiate from sql and mysql:
    "sql": {
        "name": "SQL",
        "mode": ["sql", "text/x-sql"],
        "fileExtensions": ["sql"]
    },

    "mysql": {
        "name": "MySQL",
        "mode": ["sql", "text/x-mysql"],
    },

I will not open a PR so feel free to steal the code. I'm not sure it is exact but seems to work.

Interesting, never realized that it's supposed to have a space afterwards. Oracle says the same thing
It's odd because both Oracle SQL Developer and MS SQL Server Management Studio both consider a comment to start with "--" not "-- ".  Weird.  Oh well.
Thanks for looking into it ficristo!

Why did you close this @benzen217? I'm still unable to have comments properly highlighted, even with a .languages.json file in the repo.

@benzen217, please reopen, it's quite untenable that in 1--foo the bit that reads --foo is not shown as a comment. I don't know how this can be resolved but the issue remains.


Clarification of satisfaction/engagement tradeoff in choc-kale example

When running the chocolate/kale example, I select a slate following a deterministic kaleness-first selection policy - i.e. I order document observations descendingly by their kaleness and then define the action as the first slate_size items:
action = tuple(np.argsort([do[0] for do in document_observations]))[:slate_size]

document_observations is observation["doc"], so e.g. (array([0.57019677]), array([0.43860151]), ..., array([0.46631077]).
For comparison I run the environment with the reverse policy, which is to select the action by picking the documents with the lowest kaleness:
action = tuple(np.argsort([do[0] for do in document_observations]))[::-1][:slate_size]

If I compare both policies after running them for a couple hundred steps, the kaleness-first policy yields higher engagement and lower user satisfaction than the chocolateness-first policy. I would expect exactly the opposite, since kaleness is supposed to boost user satisfaction at the cost of lower engagement.
Why does selecting items with the highest kaleness yield a lower user satisfaction and higher engagement than selecting items with the lowest kaleness?

Thank you for using RecSim and sorry for the bug in the chocolate/kale example. The following is the correct version of generate_response(). As you can see we mess up kale_mean and choc_mean here but the code in https://github.com/google-research/recsim/blob/master/recsim/environments/long_term_satisfaction.py is correct.
def generate_response(self, doc, response):
response.clicked = True
linear interpolation between choc and kale.
engagement_loc = (doc.kaleness * self._user_state.kale_mean
+ (1 - doc.kaleness) * self._user_state.choc_mean)
engagement_loc *= self._user_state.satisfaction
engagement_scale = (doc.kaleness * self._user_state.kale_stddev
+ ((1 - doc.kaleness)
* self._user_state.choc_stddev))
log_engagement = np.random.normal(loc=engagement_loc,
scale=engagement_scale)
response.engagement = np.exp(log_engagement)
We will update the repository shortly. Let me know if you still have questions.

No, that's it. Thanks for your response!


next branch: fitWidth with xScaleProvider, props for EventHandler

I pushed to next by mistake, it is not stable code. This is part of the scale rewrite,

all examples fixed to use a slightly modified scale, there is no change needed if you use a d3.time.scale but if you use the existing financeEODDiscontinuousScale or financeIntradayDiscontinuousScale there will be a breaking change. I am yet to add more details in the change log.
in short, it is a 2 line change,
-var { financeEODDiscontinuousScale } = ReStock.scale;
+var { discontinuousTimeScaleProvider } = ReStock.scale;

and
<ChartCanvas ...
  xAccessor={d => d.date}
- discontinuous xScale={financeEODDiscontinuousScale()}
+ xScaleProvider={discontinuousTimeScaleProvider}
 ...

i have used financeIntradayDiscontinuousScale
but, after last commit only one Type Error

fixed it, can you try again,
financeIntradayDiscontinuousScale or financeEODDiscontinuousScale can no longer be used in next branch
<ChartCanvas ...
  xAccessor={d => d.date}
- discontinuous xScale={financeIntradayDiscontinuousScale()}
+ xScaleProvider={discontinuousTimeScaleProvider}
 ...

still have some trubles with fitWidth from next branch (

couldnt prepare planker, but when window resized, fitWidth doesn't  work

I am not able to recreate that issue, are you sure you dont have 2 versions of ReactDOM in your bundle?


KeyError: 'raincoat.match'

This error appeared on our builds with no apparent change:
https://app.circleci.com/pipelines/github/openfun/fun-richie-site-factory/98/workflows/4d0b471c-1761-4b78-889c-d2cbd88fe795/jobs/2619
>>> [ep.name for ep in importlib_metadata.entry_points() if "raincoat" in ep.name]
['raincoat']

Do you see any reason for the "raincoat.match" entrypoint declaration to be ignored in setup.cfg? :thinking:

Hey :)
I haven't been... very seriously maintaining this lib through the years... 😅
Seems like you're using it, would you be interested in taking a part in the maintenance ? I'm sure that if there's some activity, it will be much easier for me to spend time polishing it :)
No idea where that might come from. New release of importlib-metadata ?

I'll be delighted. I'll try to spend some time working on it in the next few days :)

Keeping it open until I manage to issue a release but that should happen quicky

https://pypi.org/project/raincoat/1.2.4/ 🎉


Snekbox deployment

Mr. Hemlock does not have the time for this right now, because it's the middle of Texas season.
Mark might be interested in doing this.

Hi @MarkKoz, do you want to sit together with us and work on this?

Yes, but I will likely be learning more than doing due to lack of experience. We'll just need to figure out a good time to work on it.


VSCode extension

I don't use VSCode, but if you do - please add an extension?
Let me know :)

Closing as this should be it's own repo - if you find this issue having written a code extension please contact me and we can nhost the repo here if you want - and I can add you to the org as admin of that repo 👍🏻


all docs updated to May26

Worked the full pull-request cycle and updated the document set to be more complete and useful.

looks good!


SELF_SIGNED_CERT_IN_CHAIN when using private hosted npm registry

/usr/local/lib/node_modules/npmd/index.js:95
    if(err) throw err
                  ^
Error: SELF_SIGNED_CERT_IN_CHAIN
    at SecurePair.<anonymous> (tls.js:1367:32)
    at SecurePair.emit (events.js:92:17)
    at SecurePair.maybeInitFinished (tls.js:979:10)
    at CleartextStream.read [as _read] (tls.js:471:13)
    at CleartextStream.Readable.read (_stream_readable.js:340:10)
    at EncryptedStream.write [as _write] (tls.js:368:25)
    at doWrite (_stream_writable.js:225:10)
    at writeOrBuffer (_stream_writable.js:215:5)
    at EncryptedStream.Writable.write (_stream_writable.js:182:11)
    at write (_stream_readable.js:601:24)

Our registry is behind a firewall so I don't have a way to provide a test case but I'm happy to try out a work in progress branch.  We install some dependencies directly over HTTPS. The only solution that works with npm for us is npm install --strict-ssl=false.
I wanted to give npmd a try. And here’s what I get:
.../npmd/index.js:95
    if(err) throw err
                  ^
Error: DEPTH_ZERO_SELF_SIGNED_CERT
    at SecurePair.<anonymous> (tls.js:1381:32)
    at SecurePair.emit (events.js:92:17)
    at SecurePair.maybeInitFinished (tls.js:980:10)
    at CleartextStream.read [as _read] (tls.js:472:13)
    at CleartextStream.Readable.read (_stream_readable.js:341:10)
    at EncryptedStream.write [as _write] (tls.js:369:25)
    at doWrite (_stream_writable.js:226:10)
    at writeOrBuffer (_stream_writable.js:216:5)
    at EncryptedStream.Writable.write (_stream_writable.js:183:11)
    at write (_stream_readable.js:602:24)

Oh hmm... okay so the ideal solution would be to be able to configure a cert to use for a particular domain, right?
I would be happy to merge a PR that allowed you to set certs, and to answer any questions necessary.

to be able to configure a cert to use for a particular domain

Yeah, so we’ve tried with npm – and after a several hours’ fight we gave up – and decided to pull our HTTPS modules with the option --strict-ssl=false.
@dylang was that why you migrated off HTTPS?
How about forwarding any options to npm? So you could just do npmd install --strict-ssl=false.

well the strict-ssl option is actually a thing that is being passed to request. npmd doesn't depend on npm.

@tomekwi We migrated to http because of (from what we can remember) couch issues with our cert and trust store and we didn't care to spend time trying to resolve because our registry is inside our firewall.


Is it a recommended way to validate argument with  _ = arg ?? throw new ArgumentNullException?

Under the A standalone discard section, there is a piece of sample code using _ and null coalescing operator to throw an ArgumentNullException when the argument is null:
public static void Method(string arg)
{
    _ = arg ?? throw new ArgumentNullException(paramName: nameof(arg), message: "arg can't be null");

    // Do work with arg.
}

I am wondering if this is the recommended way to validate an argument. Some of my teammates have started using this pattern in our codebase. It's more concise for sure, but I think it hurts the readability. I personally feel this really doesn't read as naturally as:
if (arg == null)
{
    throw new ArgumentNullException(paramName: nameof(arg), message: "arg can't be null");
}

Thoughts?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7ace3d2c-a7f7-c667-5f50-b8d8f1dfc87a
Version Independent ID: 6edd2f85-a04b-e9ad-2fc9-fc23dbfc5bba
Content: Discards - unassigned discardable variables
Content Source: docs/csharp/fundamentals/functional/discards.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

I doubt you're going to get any kind of "official" answer about this, since it's about a subjective element of code style.
That being said, there are other new and coming options for parameter null validation.
In .Net 6, you can use this:
public static void Method(string arg)
{
    ArgumentNullException.ThrowIfNull(arg); // paramName is automatically inferred

    // Do work with arg.
}

And in .Net 7, you'll be able to make the code even shorter:
public static void Method(string arg!!)
{
    // Do work with arg.
}

@svick - thanks for your response! I think that makes sense.
It's great to know those new options. I really like the .NET 6 one ArgumentNullException.ThrowIfNull(arg). It's concise enough but at the same time also shows the intention very clearly.


missing

nothing else

@Zwilla Mayyyyyybe you should just tell me whatever tool you are using for this so i get it set up on mine and we don't have to do this anymore? How hard is it to set up?


Mention that 1.x is feature-complete

It'll help would-be contributors (such as myself, see #2058) avoid creating PRs that won't be accepted - I didn't realize 1.x was feature-complete until I saw mention of that status in an unrelated issue which I happened to look at for an unrelated reason.

@aaron-em thanks. we should have done this sooner.


treat plugins as code dependencies

PR Summary
This simplifies the plugin spack situation by just treating plugins like any other code dependencies.
Each plugin just has to install its source code into the spack prefix and the singularity-eos plugin needs to be registered using its name, spack package name, and the relative path to the plugins source code.
PR Checklist

[ ] Adds a test for any bugs fixed. Adds tests for new features.
[ ] Format your changes by using the make format command after configuring with cmake.
[ ] Document any new features, update documentation for changes made.
[ ] Make sure the copyright notice on any files you modified is up to date.
[ ] After creating a pull request, note it in the CHANGELOG.md file.
[ ] LANL employees: make sure tests pass both on the github CI and on the Darwin CI

If preparing for a new release, in addition please check the following:

[ ] Update the version in cmake.
[ ] Move the changes in the CHANGELOG.md file under a new header for the new release, and reset the categories.

@Yurlungur what are you thoughts? I think this will simplify things, but I admit I'll need to see a full release process of a plugin to really understand the details. But based off of our other conversations, I think this is a good route to go in.

I think I'm supportive of this design. @rbberger when resolving a spack spec, how does this work? Does the ordering get swapped so the plugin is a dependency of singularity?

@Yurlungur found one more issue due to the variant, which was a directory into the source tree. Since it now no longer needs to be in one folder, it'll convert plugin/some/path to {plugin.prefix}/some/path

Right. Plugin spackages need to be made build dependencies and registered as plugins.

Does that mean we need to specify all available plugins in the spackage? Or can this happen "on the fly"? I.e., does this make the plugin infrastructure only useful for us? Or can others leverage it still?

It means that plugins can be added by manipulating the singularity-eos package since they need to become a build dependencies. Either directly or via inheritance.

So if there are other plugins out there, in order to use it'll have to be registered in our spackage.

Ok I think this is fine. But it is a downside since it means using a plugin with spack requires more "manual" intervention. But maybe that's unavoidable.


Change named export to default export

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Fixes #5639

By correcting the export this should resolve this issue here:
https://github.com/prisma/prisma/issues/5639


[FEATURE REQUEST] Speeding up the process in lots of times

Issue type: feature request
Severity: medium
Describe the feature
So, it seems that you are using pytorch library for this project (based on a single viewed file, i am sorry if i am just dumb and didnt read something), which is fine. But, I have a question, why it doesnt use cuda? CPU is slow for such computation kind (lots of same easy computations), but a GPU is designed in my mind for such use cases.
Switching the device to cuda, can make a big (or significant) perfomance uplift. I was doing some stuff with pytorch (my projects were dumb tho) and trasnfering the model to another device is very easy, one method and one check:
DEVICE = "cuda" if torch.cuda.is_available() else "cpu"
model = torch.load("model name").to(DEVICE)

(google it or search in pytorch docs, i am not sure about the method name for transfering models in another device)
btw, it would be better if used libs (such as pytorch) was installed on a pc in a created venv (you can create venvs via scripts, i guess). this will allow to bring quick pop up on a start, with a question "Do you have an NVidia GPU?", if yes it will install pytorch with cuda support, else pytorch without cuda. (yes, i am aware pytorch is about 2 gigs, at least with cuda support)
PC:

OS: Windows
Browser: Chrome
.exe file name: Spaceship.Generator.v1.0.3.exe

Additional context
how i came to such consern? my cuda is not used, when use stable diffusion or my own projects, they use cuda device
...also it would be useful to provide quick guide to know what gpu does user use, cuz sometimes i see people didnt knowing what gpu they are using.

also, venv folder can be made in %temp% or some cache folder

Hi @Spaceginner, the PyTorch library is supported but not used as default, as otherwise the executable would be a ~800MB file and would take even longer to start the application--this was implemented in https://github.com/arayabrain/space-engineers-ai-spaceship-generator/issues/35.
The PyTorch dependency is left for now for results reproducibility, as it was used in the earlier versions of the applications (before the user study release) in tests.
There is already some parallelisation going (using joblib.Parallel and joblib.delayed), but not all operations can be parallelised (or, at least, quite a bit of code refactorisation may be needed). I will leave this feature request open and add the 'help wanted' tag, as for now I don't think I'll manage to tackle it.

So, I understood, CUDA or any GPU computational power is not being used, right?

Correct, no parallelisation, just multithreading.
As for your question, yeah, you can. If you want to play around with this program, you can edit the configs.ini file and set the use_torch flag to True. PyInstaller will pick up automatically the libraries used in the project when you build, so that should not be a problem.
PS: consider forking this repository if you want to play around with it, you can still create a PR later on if you're happy with the changes you make 😃

One more question, will it pick up torch libraries with cuda support or regular ones?

If it's set up to use CUDA, it will use CUDA. If you're unsure, try and making a simple script such as
import torch

print(torch.cuda.is_available)

and creating an executable from it with
import PyInstaller.__main__ as pyinst

pyi_args = ['my_torch_script.py',
            '--clean',
            '--onefile',
            '--noconfirm',
            '--name', "my_torrch_executable"]

pyinst.run(pyi_args)

This will give you a very barebones test to see if you can make a Python executable with PyTorch and CUDA. You can then edit the first script to test tensor operations on a GPU device.

OK, thx


Update build guide

The readme mention to copy the plugin source into paraview sources, and then build all once.
This is not the recommended way. Please do so:

build ParaView alone
build the plugin in its own directory. At configuration time, pass -DParaView_DIR=/path/to/pv/build
That way, paraview sources stay clean, and it is easier to update either pv and the plugin.

At runtime, you will need to load new plugin, and look for NodeEditor.so under in paraview-node-editor/build/lib/paraview-5.8/plugins/NodeEditor

Hi Nicolas,
thanks! This is much better. I adjusted the ReadMe. If you think it is clear enough we can close this issue.
Best


feat(test): semantic release와 action 추가

:tada: This PR is included in version 1.0.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update api path in main after service account removal

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Checks will fail until: https://github.com/opensearch-project/opensearch-dashboards-functional-test/pull/1444#:~:text=Remove service accounts from Main opensearch-project/security-dashboards-plugin%232041 is merged

Approved.

Checks will fail until: https://github.com/opensearch-project/security-dashboards-plugin/pull/2041 is merged

I just re-ran the check since associated PR has merged.

Hi @derek-ho , the security release tests workflow still failed after re-run. Is that related to this PR? Just find the plugins/security/internalusers_spec.js was passed in this job. Can we merge it to the main branch? Do we need  backport to 2.x branch?

Checking on the other failures now

All checks passed. Merging.

@derek-ho Can you please update the description and link to the companion security-dashboards-plugin PR?


bug: /var/run/swiftwave folder get deleted on server restart

for this reason, the proxies are failing to start automatically

Moved the directory from /var/run/swiftwave to /etc/swiftwave


[Old PR libui#513] Add new API functions for table header clicks and sort indicators.

Old PR  libui#513
Proposal for introducing an enum sort type uiSort:
uiSortNone
uiSortAscending
uiSortDescending

Two functions for setting table header sort indicators (only visual, no sorting is performed):
uiSort uiTableHeaderSortIndicator(uiTable *t, int column);
void uiTableHeaderSetSortIndicator(uiTable *t, int column, uiSort order);

And a setter for a header on clicked callback function:
void uiTableHeaderOnClicked(uiTable *t, void (*f)(uiTable *table, int column, void *data), void *data);

Implementations are provided for darwin, unix, and windows.
Notes: The column is the index of the column when it was added to the table. It might be nice to be able to set a numeric identifier, similar to how table columns are handled on darwin. Or possibly even introducing a uiTableColumn type and cleaning up the uiTableAppendColumn API. This would however break the existing API, so I left it out for the time being.

Just updated the branch renaming the type and members to uiSortIndicator* and reverted back to using the SendMessageW function instead of macros.


Fixed dasboard docker pom.xml version to 2.1.0-SNAPSHOT

Motivation
CI build on master branch is failing because of discrepancy between the versions in the pom.xml file
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.pulsar:dashboard-docker-image:[unknown-version]: Could not find artifact org.apache.pulsar:docker-images:pom:2.0.0-incubating-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 23, column 11

retest this please


Running non-Cromwell tasks results in log pollution

Logs contain the following report for many non-Cromwell tasks:
CategoryName: TesApi.Web.Storage.DefaultStorageAccessProvider
AspNetCoreEnvironment: Production
OriginalFormat: Could not parse path '//rc'.
That file is only really expected for Cromwell tasks, and it should be ignored silently in non-Cromwell tasks.

Duplicate of #161


The EC2 instance was unable to find the mount IP OR mount EFS

I made a cloudformation template for the prerequisites, and here is the template:
AWSTemplateFormatVersion: '2010-09-09'
Description: Build Apache server, AutoScaling group, ELB and handle two different domain names
Resources:
  VPC:
    Type: AWS::EC2::VPC
    Properties:
      CidrBlock: <IP_ADDRESS>/16
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Name
        Value: FWagehPublicVPC
  InternetGateway:
    Type: AWS::EC2::InternetGateway
    Properties:
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Network
        Value: Public
  GatewayToInternet:
    Type: AWS::EC2::VPCGatewayAttachment
    Properties:
      VpcId:
        Ref: VPC
      InternetGatewayId:
        Ref: InternetGateway
  PublicSubnet:
    Type: AWS::EC2::Subnet
    Properties:
      VpcId:
        Ref: VPC
      CidrBlock: <IP_ADDRESS>/24
      AvailabilityZone: !Select
        - 1
        - Fn::GetAZs: !Ref 'AWS::Region'
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Name
        Value: fwageh_PublicSubnet
    PublicRouteTable:
    Type: AWS::EC2::RouteTable
    Properties:
      VpcId:
        Ref: VPC
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Name
        Value: PublicRouteTable
  PublicSubnetRouteTableAssociation:
    Type: AWS::EC2::SubnetRouteTableAssociation
    Properties:
      SubnetId:
        Ref: PublicSubnet
      RouteTableId:
        Ref: PublicRouteTable
  PublicRoute:
    Type: AWS::EC2::Route
    DependsOn: GatewayToInternet
    Properties:
      RouteTableId:
        Ref: PublicRouteTable
      DestinationCidrBlock: <IP_ADDRESS>/0
      GatewayId:
        Ref: InternetGateway
  PrivateSubnetMountOne:
    Type: AWS::EC2::Subnet
    Properties:
      VpcId:
        Ref: VPC
      CidrBlock: <IP_ADDRESS>/24
      AvailabilityZone: !Select
        - 0
        - Fn::GetAZs: !Ref 'AWS::Region'
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Name
        Value: fwageh_PrivateSubnetMountOne
  PrivateSubnetMountTwo:
    Type: AWS::EC2::Subnet
    Properties:
      VpcId:
        Ref: VPC
      CidrBlock: <IP_ADDRESS>/24
      AvailabilityZone: !Select
        - 1
        - Fn::GetAZs: !Ref 'AWS::Region'
      Tags:
      - Key: Application
        Value:
          Ref: AWS::StackId
      - Key: Name
        Value: fwageh_PrivateSubnetMountTwo
  NATGateway:
    DependsOn: GatewayToInternet
    Type: AWS::EC2::NatGateway
    Properties:
      AllocationId:
        Fn::GetAtt:
        - ElasticIP
        - AllocationId
      SubnetId:
        Ref: PublicSubnet
  ElasticIP:
    Type: AWS::EC2::EIP
    DependsOn: GatewayToInternet
    Properties:
      Domain: vpc
  PrivateRouteTable:
    Type: AWS::EC2::RouteTable
    Properties:
      VpcId:
        Ref: VPC
  PrivateRouteToInternet:
    Type: AWS::EC2::Route
    Properties:
      RouteTableId:
        Ref: PrivateRouteTable
      DestinationCidrBlock: <IP_ADDRESS>/0
      NatGatewayId:
        Ref: NATGateway
  PrivateSubnetOneRouteTableAssociation:
    Type: AWS::EC2::SubnetRouteTableAssociation
    Properties:
      SubnetId:
        Ref: PrivateSubnetMountOne
      RouteTableId:
        Ref: PrivateRouteTable
  PrivateSubnetTwoRouteTableAssociation:
    Type: AWS::EC2::SubnetRouteTableAssociation
    Properties:
      SubnetId:
        Ref: PrivateSubnetMountTwo
      RouteTableId:
        Ref: PrivateRouteTable
  FileSystem:
    Type: 'AWS::EFS::FileSystem'
    Properties:
      Encrypted: true
      KmsKeyId: !GetAtt
        - key
        - Arn
  key:
    Type: 'AWS::KMS::Key'
    Properties:
      KeyPolicy:
        Version: 2012-10-17
        Id: key-default-1
        Statement:
          - Sid: Allow administration of the key
            Effect: Allow
            Principal:
              AWS: !Join
                - ''
                - - 'arn:aws:iam::'
                  - !Ref 'AWS::AccountId'
                  - ':root'
            Action:
              - 'kms:*'
            Resource: '*'

And the SNS email Keeps telling me "The EFS backup was unsuccessful. The EC2 instance was unable to find the mount IP OR mount EFS"
And here is the ec2-log in my bucket:

Cloud-init v. 0.7.6 running 'init-local' at Mon, 30 Jul 2018 17:03:21 +0000. Up 6.78 seconds.
Cloud-init v. 0.7.6 running 'init' at Mon, 30 Jul 2018 17:03:21 +0000. Up 6.94 seconds.
ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++
ci-info:  Device   Up     Address         Mask          Hw-Address
ci-info:    lo    True   <IP_ADDRESS>     <IP_ADDRESS>            .
ci-info:   eth0   True  <IP_ADDRESS>  <IP_ADDRESS>  12:02:1a:0d:9b:d2
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info:  Route    Destination     Gateway       Genmask      Interface  Flags
ci-info:    0        <IP_ADDRESS>      <IP_ADDRESS>      <IP_ADDRESS>         eth0      UG
ci-info:    1       <IP_ADDRESS>      <IP_ADDRESS>    <IP_ADDRESS>      eth0      U
ci-info:    2    <IP_ADDRESS>   <IP_ADDRESS>   <IP_ADDRESS>     eth0      UH
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:vhv8fVQpM7DBmFLIXVDl/iaXTKB9uIzQK9xAWpvbJxQ root@ip-10-40-4-166
The key's randomart image is:
+---[RSA 2048]----+
|      . +oBo..   |
|       + + +.    |
|        .o E+o  .|
|        + +.=+o..|
|       .S= + +++ |
|       o. B + B .|
|        ++ * * * |
|         +..o =  |
|        o.. ..   |
+----[SHA256]-----+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:izZkrNY292nTQxNM/XUdOPRArX2TdpwxjquvWG/R9qs root@ip-10-40-4-166
The key's randomart image is:
+---[DSA 1024]----+
|            o=o.o|
|            .o+++|
|           o  +B|
|     .      oo B=|
|      + S    .+ +|
|     = . .  oo o |
|    o B o  +..o .|
|   . o + .=o+.  .|
|         ooo+E...|
+----[SHA256]-----+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:9JT5t0+TVY3nfs/irvWGs28V4frzuWmVzmKxismTQ8k root@ip-10-40-4-166
The key's randomart image is:
+---[ECDSA 256]---+
|                 |
|           o   o.|
|        . +   o =|
|       . o .   =.|
|        S o . o =|
|         E   + +=|
|        . .   O+|
|        .+o  =+@O|
|         +o.++*@@|
+----[SHA256]-----+
Cloud-init v. 0.7.6 running 'modules:config' at Mon, 30 Jul 2018 17:03:22 +0000. Up 7.60 seconds.
Loaded plugins: priorities, update-motd, upgrade-helper
1 package(s) needed (+0 related) for security, out of 3 available
Resolving Dependencies
--> Running transaction check
---> Package gnupg2.x86_64 0:2.0.28-2.31.amzn1 will be updated
---> Package gnupg2.x86_64 0:2.0.28-2.32.amzn1 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package       Arch          Version                  Repository           Size
Updating:
gnupg2        x86_64        2.0.28-2.32.amzn1        amzn-updates        2.6 M
Transaction Summary
Upgrade  1 Package
Total download size: 2.6 M
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating   : gnupg2-2.0.28-2.32.amzn1.x86_64                              1/2
Cleanup    : gnupg2-2.0.28-2.31.amzn1.x86_64                              2/2
Verifying  : gnupg2-2.0.28-2.32.amzn1.x86_64                              1/2
Verifying  : gnupg2-2.0.28-2.31.amzn1.x86_64                              2/2
Updated:
gnupg2.x86_64 0:2.0.28-2.32.amzn1
Complete!
Cloud-init v. 0.7.6 running 'modules:final' at Mon, 30 Jul 2018 17:03:27 +0000. Up 13.28 seconds.
Loaded plugins: priorities, update-motd, upgrade-helper
Existing lock /var/run/yum.pid: another copy is running as pid 2061.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory :  87 M RSS (334 MB VSZ)
Started: Mon Jul 30 17:03:26 2018 - 00:02 ago
State  : Running, pid: 2061
Examining /var/tmp/yum-root-uoTNk3/amazon-ssm-agent.rpm: amazon-ssm-agent-2.2.800.0-1.x86_64
Marking /var/tmp/yum-root-uoTNk3/amazon-ssm-agent.rpm as an update to amazon-ssm-agent-<IP_ADDRESS>-1.amzn1.x86_64
Resolving Dependencies
--> Running transaction check
---> Package amazon-ssm-agent.x86_64 0:<IP_ADDRESS>-1.amzn1 will be updated
---> Package amazon-ssm-agent.x86_64 0:2.2.800.0-1 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package              Arch       Version            Repository             Size
Updating:
amazon-ssm-agent     x86_64     2.2.800.0-1        /amazon-ssm-agent      40 M
Transaction Summary
Upgrade  1 Package
Total size: 40 M
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
amazon-ssm-agent stop/waiting
Updating   : amazon-ssm-agent-2.2.800.0-1.x86_64                          1/2
Cleanup    : amazon-ssm-agent-<IP_ADDRESS>-1.amzn1.x86_64                    2/2
amazon-ssm-agent start/running, process 2183
Verifying  : amazon-ssm-agent-2.2.800.0-1.x86_64                          1/2
Verifying  : amazon-ssm-agent-<IP_ADDRESS>-1.amzn1.x86_64                    2/2
Updated:
amazon-ssm-agent.x86_64 0:2.2.800.0-1
Complete!
start: Job is already running: amazon-ssm-agent
--2018-07-30 17:03:36--  https://s3.amazonaws.com/solutions-reference/efs-backup/latest/efs-ec2-backup.sh
Resolving s3.amazonaws.com (s3.amazonaws.com)... <IP_ADDRESS>
Connecting to s3.amazonaws.com (s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3268 (3.2K) [binary/octet-stream]
Saving to: ‘/home/ec2-user/efs-ec2-backup.sh’
 0K ...                                                   100% 10.5M=0s

2018-07-30 17:03:36 (10.5 MB/s) - ‘/home/ec2-user/efs-ec2-backup.sh’ saved [3268/3268]
--2018-07-30 17:03:36--  https://s3.amazonaws.com/solutions-reference/efs-backup/latest/efs-backup-fpsync.sh
Resolving s3.amazonaws.com (s3.amazonaws.com)... <IP_ADDRESS>
Connecting to s3.amazonaws.com (s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5903 (5.8K) [binary/octet-stream]
Saving to: ‘/home/ec2-user/efs-backup-fpsync.sh’
 0K .....                                                 100% 11.2M=0.001s

2018-07-30 17:03:36 (11.2 MB/s) - ‘/home/ec2-user/efs-backup-fpsync.sh’ saved [5903/5903]
This is the master script to perform efs backup
input from user
_source_efs: fs-d0464798
_destination_efs: fs-5b7f7e13
_interval: daily
_retain: 7
_folder_label: fwageh-efs-backup
_backup_prefix: /
region is us-east-1
instance-id is i-0582c39e3a29996e5
-- 2018-07-30T17:03:38 -- resolving source efs address fs-d0464798.efs.us-east-1.amazonaws.com
<IP_ADDRESS>
-- 2018-07-30T17:03:38 -- src mount ip: <IP_ADDRESS>
-- 2018-07-30T17:03:38 -- resolving backup efs address fs-5b7f7e13.efs.us-east-1.amazonaws.com
<IP_ADDRESS>
-- 2018-07-30T17:03:38 -- dst mount ip: <IP_ADDRESS>
-- 2018-07-30T17:03:38 -- running EFS backup script
input from user
source: <IP_ADDRESS>:/
destination: <IP_ADDRESS>:/
interval: daily
retain: 7
efsid: fwageh-efs-backup
-- 2018-07-30T17:03:38 -- sudo yum -y update
Loaded plugins: priorities, update-motd, upgrade-helper
Resolving Dependencies
--> Running transaction check
---> Package amazon-ssm-agent.x86_64 0:2.2.800.0-1 will be updated
---> Package amazon-ssm-agent.x86_64 0:2.2.800.0-1.amzn1 will be an update
---> Package kernel.x86_64 0:4.14.55-62.37.amzn1 will be installed
---> Package kernel-tools.x86_64 0:4.14.47-56.37.amzn1 will be updated
---> Package kernel-tools.x86_64 0:4.14.55-62.37.amzn1 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package              Arch       Version                 Repository        Size
Installing:
kernel               x86_64     4.14.55-62.37.amzn1     amzn-updates      21 M
Updating:
amazon-ssm-agent     x86_64     2.2.800.0-1.amzn1       amzn-updates      12 M
kernel-tools         x86_64     4.14.55-62.37.amzn1     amzn-updates     124 k
Transaction Summary
Install  1 Package
Upgrade  2 Packages
Total download size: 33 M
Downloading packages:
Total                                               16 MB/s |  33 MB  00:02
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : kernel-4.14.55-62.37.amzn1.x86_64                            1/5
Updating   : kernel-tools-4.14.55-62.37.amzn1.x86_64                      2/5
Updating   : amazon-ssm-agent-2.2.800.0-1.amzn1.x86_64                    3/5
Cleanup    : kernel-tools-4.14.47-56.37.amzn1.x86_64                      4/5
Cleanup    : amazon-ssm-agent-2.2.800.0-1.x86_64                          5/5
Verifying  : amazon-ssm-agent-2.2.800.0-1.amzn1.x86_64                    1/5
Verifying  : kernel-tools-4.14.55-62.37.amzn1.x86_64                      2/5
Verifying  : kernel-4.14.55-62.37.amzn1.x86_64                            3/5
Verifying  : kernel-tools-4.14.47-56.37.amzn1.x86_64                      4/5
Verifying  : amazon-ssm-agent-2.2.800.0-1.x86_64                          5/5
Installed:
kernel.x86_64 0:4.14.55-62.37.amzn1
Updated:
amazon-ssm-agent.x86_64 0:2.2.800.0-1.amzn1
kernel-tools.x86_64 0:4.14.55-62.37.amzn1
Complete!
-- 2018-07-30T17:04:08 -- sudo yum -y install nfs-utils
Loaded plugins: priorities, update-motd, upgrade-helper
Existing lock /var/run/yum.pid: another copy is running as pid 7603.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory :  35 M RSS (282 MB VSZ)
Started: Mon Jul 30 17:04:08 2018 - 00:00 ago
State  : Running, pid: 7603
Package 1:nfs-utils-1.3.0-0.21.amzn1.x86_64 already installed and latest version
Nothing to do
-- 2018-07-30T17:04:10 -- sudo mkdir /backup
-- 2018-07-30T17:04:10 -- sudo mkdir /mnt/backups
-- 2018-07-30T17:04:10 -- sudo mount -t nfs -o nfsvers=4.1 -o rsize=1048576 -o wsize=1048576 -o timeo=600 -o retrans=2 -o hard <IP_ADDRESS>:/ /backup
mount.nfs: Connection timed out
mount status for source efs: 32
-- 2018-07-30T17:08:33 -- sudo mount -t nfs -o nfsvers=4.1 -o rsize=1048576 -o wsize=1048576 -o timeo=600 -o retrans=2 -o hard <IP_ADDRESS>:/ /mnt/backups
mount status for backup efs: 0
-- 2018-07-30T17:08:36 -- ERROR:efs_not_mounted
-- 2018-07-30T17:08:36 -- Backup script finished before the backup window, stopping the ec2 instance.
ci-info: no authorized ssh keys fingerprints found for user ec2-user.
Cloud-init v. 0.7.6 finished at Mon, 30 Jul 2018 17:08:37 +0000. Datasource DataSourceEc2.  Up 322.79 seconds

I don't know where is the issue

mount.nfs: Connection timed out
mount status for source efs: 32
-- 2018-07-30T17:08:33 -- sudo mount -t nfs -o nfsvers=4.1 -o rsize=1048576 -o wsize=1048576 -o timeo=600 -o retrans=2 -o hard <IP_ADDRESS>:/ /mnt/backups
mount status for backup efs: 0
-- 2018-07-30T17:08:36 -- ERROR:efs_not_mounted

we can see the EFS was not mounted. please refer to this link to understand how to allow access to EFS mount targets. you must allow NFS port in your inbound rules so EC2 can mount the EFS volume.


make EKS tests possible to run from local arm machine

Will be fixed by https://github.com/kumahq/kuma/pull/7377


Quality-of-life additions to CplStringList.

[X] I agree to follow the project's code of conduct.
[X] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

New methods:

len
is_empty

New traits:

Debug
Iterator

New tests:

has_length
can_be_empty
invalid_keys
basic_list
debug_fmt
has_iterator

Also tested under:
ASAN_OPTIONS=detect_stack_use_after_return=1,sanitize-address-use-after-return=always RUSTFLAGS=-Zsanitizer=address cargo +nightly test cpl --target aarch64-apple-darwin

bors r=lnicola


What is uap6:AllowExecution used for?

Title really says it all. Why would you want to use this element in your AppX manifest, if it renders that AppX seemingly useless? Some context would be helpful here.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f19e5a49-35c4-a65a-7145-d195a7eb1fbc
Version Independent ID: f5a2d6c8-faae-eeae-13c0-8d6e8093196f
Content: uap6:AllowExecution - UWP app developer
Content Source: winrt-related-src/schemas/appxpackage/uapmanifestschema/element-uap6-allowexecution.md
Service: unspecified
GitHub Login: @laurenhughes
Microsoft Alias: lahugh

@wjk This is used for more complex packaging scenarios. For example, asset packages typically don't contain any executable files, so by designating an asset package's "uap6:AllowExecution" element to "false" you can save a bit of time when publishing an app in the Store. See Introduction to asset packages for more details. I'll add the link to the page and provide more context.
Thanks for your feedback!


Simplifying base templates

What type of PR is this? (check all applicable)

[X] Refactor
[X] Feature
[ ] Bug Fix
[X] Optimization
[X] Documentation Update

Description
Checklist before requesting a review

[X] I have performed a self-review of my code
[ ] I have added/updated tests.

@seanmcn It seems that everything is fine here, before the release of the 2.x version it is better to apply these changes.. But it’s better to check it first, can you please do this? :)

One thing that's a bit strange to me, and this is probably more to do with the 2.x.x branch than this PR is now if I run:
php demo/demo1/demoScript.php

I get:
Generation completed with errors
├───────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ERROR │ Configuration parameter `language_handlers.php.settings.composer_config_file` must contain exists file path │
│       │ This error occurs during the document rendering process                                                     │
│       │ /src/Core/Plugin/PluginEventDispatcher.php#32                                                               │
│       │ /sectionWithSubsections/pageLinkingExample/index.md.twig                                                    │

Do I need to pass this in manually now or?

@seanmcn For some reason I can't reply to the thread. The error in php demo/demo1/demoScript.php occurs because the demo config has not been corrected, it just needs to be corrected and the necessary option added


.NET core 2.1 support

Is support for .NET core 2.1 planned?
I just wonder whether I have to rewrite my integration tests using Microsoft.AspNetCore.Mvc.Testing.
PS
I took a crack at debugging but it exceeded my skills. I fear that changes in .net core 2,1 are too great to easily migrate Alba.

@esterad Sorry for the slow response, you caught me on vacation. I don't think this is gonna be all that big of a deal to address. I already his some of this with Jasper when I moved that up to 2.1. I'll try to get this fixed by Tuesday.

@jeremydmiller  Looking forward  to this fix :) Hope it would go smoothly. Thank you for creating and supporting Alba - great piece of software

Meh, by this coming Monday. Haven't forgotten you, just backed up

@esterad Would you try out Alba.AspNetCore2 v1.4.1 and see if it addressed your issues? I was able to verify it worked against what I was doing in an ASP.Net Core app using 2.1. If it does manage to fix things, it was just a 1 line code fix.

It works! Thank you 👍