cups-filters: fix the build with poppler-0.67.0

Motivation for this change
Apply the patch from https://github.com/OpenPrinting/cups-filters/pull/51 to fix the build of cups-filter originally broken by 7d016502d88a89bebb2fd8728a5bb40702a7feba.
Things done

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

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

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

closes #44282

@GrahamcOfBorg build cups-filters system-config-printer

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: cups-filters, system-config-printer
Partial log (click to expand)

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

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

Failure on x86_64-linux (full log)
Attempted: cups-filters, system-config-printer
Partial log (click to expand)
trying https://github.com/OpenPrinting/cups-filters/commit/219de01c61f3b1ec146abf142d0dfc8c560cc58e.patch
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   814    0   814    0     0   2071      0 --:--:-- --:--:-- --:--:--  2071
fixed-output derivation produced path '/nix/store/8lsqp42m40sc1sdvhicqkmpngxvk2bg6-219de01c61f3b1ec146abf142d0dfc8c560cc58e.patch' with sha256 hash '0f0lql3rbm2g8mxrpigfyi8fb4i2g4av20g417jzdilp60jq0ny8' instead of the expected hash '0i503z6qa4m07qiaxfy81fpj9ybnswp7dkja2amv6m2n9pk45qqj'
cannot build derivation '/nix/store/1ghmmbdzfsw152qzx7b0q1v9hzaj44gj-cups-filters-1.20.4.drv': 1 dependencies couldn't be built
copying path '/nix/store/7xinm3hzili33mnq8609qrirv3g261ag-samba-4.7.6' from 'https://cache.nixos.org'...
copying path '/nix/store/ifbg4dawi1jwq0r3siqlmlgbif8r2y8h-python3.6-pysmbc-<IP_ADDRESS>' from 'https://cache.nixos.org'...
cannot build derivation '/nix/store/bwiixqijkxldwkpfqbg5qdx35nfs8737-system-config-printer-1.5.11.drv': 1 dependencies couldn't be built
error: build of '/nix/store/1ghmmbdzfsw152qzx7b0q1v9hzaj44gj-cups-filters-1.20.4.drv', '/nix/store/bwiixqijkxldwkpfqbg5qdx35nfs8737-system-config-printer-1.5.11.drv' failed

Failure on aarch64-linux (full log)
Attempted: cups-filters, system-config-printer
Partial log (click to expand)
  File "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/lib/python3.6/wsgiref/simple_server.py", line 133, in handle
    handler.run(self.server.get_app())
  File "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/lib/python3.6/wsgiref/handlers.py", line 144, in run
    self.close()
  File "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/lib/python3.6/wsgiref/simple_server.py", line 35, in close
    self.status.split(' ',1)[0], self.bytes_sent
AttributeError: 'NoneType' object has no attribute 'split'
part1part2
cannot build derivation '/nix/store/ayb0v4z5jydm39src0h6vcnxiwn6hgmk-system-config-printer-1.5.11.drv': 1 dependencies couldn't be built
error: build of '/nix/store/4jyl94k7l5k9s4152axk8jj9fzck4az0-cups-filters-1.20.4.drv', '/nix/store/ayb0v4z5jydm39src0h6vcnxiwn6hgmk-system-config-printer-1.5.11.drv' failed

hash mismatch of the patch.

@xeji I fixed the hash, please rebuild.

That was fast :smiley:
@GrahamcOfBorg build cups-filters system-config-printer

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: cups-filters, system-config-printer
Partial log (click to expand)

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

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

Success on aarch64-linux (full log)
Attempted: cups-filters, system-config-printer
Partial log (click to expand)
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/check-device-ids.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/pysmb.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/scp-dbus-service.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/system-config-printer.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/install-printerdriver.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/applet.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11/share/system-config-printer/troubleshoot/__init__.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/grlcs2s6hzmra5r6sdb2l612q3002ssn-python3-3.6.6/bin/python3"
checking for references to /build in /nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11...
/nix/store/6v26pqp2xr4hj1pxa7wwj8w4hyzyqhif-cups-filters-1.20.4
/nix/store/9qcf8a4wdvhayv2dywwpak01b593x7a4-system-config-printer-1.5.11

Success on x86_64-linux (full log)
Attempted: cups-filters, system-config-printer
Partial log (click to expand)
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/share/system-config-printer/troubleshoot/__init__.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/8wfgl06xbcsxs6pmwr3n04kyhnvsh31d-python3-3.6.6/bin/python3"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/share/system-config-printer/pysmb.py: interpreter directive changed from "/usr/bin/python3" to "/nix/store/8wfgl06xbcsxs6pmwr3n04kyhnvsh31d-python3-3.6.6/bin/python3"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/bin/.install-printerdriver-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/bin/.system-config-printer-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/bin/.system-config-printer-applet-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/bin/.scp-dbus-service-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11/etc/udev/udev-add-printer: interpreter directive changed from "/usr/bin/python3 -sB" to "/nix/store/8wfgl06xbcsxs6pmwr3n04kyhnvsh31d-python3-3.6.6/bin/python3 -sB"
checking for references to /build in /nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11...
/nix/store/fbl03vnkcdvkq4ad216mq3amvh51lyz6-cups-filters-1.20.4
/nix/store/lsmhnj70420bksvnqj5k9hpq21ihljfc-system-config-printer-1.5.11


update availability doesn't work

Describe the bug:
mov-cli > utils > version.py
as far as i know this should show a notification when the mov-cli run at the terminal indicating that there's a new update is available if there's any new version.
but it hasn't been worked with v4 since it's been released to pypi.
@THEGOLDENPRO please have a look at this.

It's been working perfectly for me. When a new version is available it will notify you when you run the mov-cli command. This has worked for me in multiple versions since v4 without fail.
Could you downgrade to an older version and try and reproduce it?

could anyone else also try and reproduce this issue

Could you downgrade to an older version and try and reproduce it?

i just downgraded to 4.2.0 and tried, it's showing now.
it's really weird for me, since it never showed for me before.
i'll close it now, maybe if similar thing happens, i'll try to open it again with a log & terminal output.


Problem profiling 2.4 GHz client TPS980P

problem profiling a TPS980P on 0.0.1.dev1 with following WLAN NICs: CF-912AC, EDUP EP-AC1615, NETGEAR A6210.
client is a 1SS, 2.4 GHz only client running Android 7.1.2.
ran profiler like: sudo python3.7 -m profiler2 -c 1 --logging debug
i tried running with --no11ax, --no11r params with no success.
i validated profiler was working by testing a Samsung S10 and iPhone 6s+.

I will soon no longer have access to this client.


Fix map nullable flag in ParquetTypeConverter

Which issue does this PR close?

Closes #1587.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Codecov Report

Merging #1592 (bc0cb98) into master (db4cb8f) will increase coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head bc0cb98 differs from pull request most recent head 380ba0a. Consider uploading reports for the commit 380ba0a to get more accurate results

@@            Coverage Diff             @@
##           master    #1592      +/-   ##
==========================================
+ Coverage   82.93%   82.95%   +0.01%
==========================================
  Files         193      193
  Lines       55350    55376      +26
==========================================
+ Hits        45907    45939      +32
+ Misses       9443     9437       -6

Impacted Files
Coverage Δ

arrow/src/compute/kernels/substring.rs
100.00% <100.00%> (+1.68%)
:arrow_up:

parquet/src/arrow/schema.rs
86.08% <100.00%> (+0.24%)
:arrow_up:

arrow/src/array/transform/mod.rs
86.57% <0.00%> (+0.22%)
:arrow_up:

parquet_derive/src/parquet_field.rs
66.43% <0.00%> (+0.22%)
:arrow_up:

Continue to review full report at Codecov.

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

Thank you @tustvold for confirming it.


Adding support for dynamic update methods.

This adds the possibility to use the "updates" field as a method for dynamically returning fields to update instead of just allowing a static list. It makes the whole package much for interesting when used in combination with final-form-arrays.
I also added a new test case to cover the new functionality.
Other tests and linting are looking good as well.
Fixed #5

Adjusted for using typeof.

Can you update both types.js and the README?

I updated the readme. Unfortunately, I don't have enough experience with Flowtype to make the adjustment. Can you handle this?

Hi Erik, I'm unsure - I don't want to put you under any pressure. It would be great, though, you could take over and release a new release. Thank you :)

I can do it. Just gotta get around to it. 😄

Hi all ! how can i get this feature ?

Published fix in v1.1.0.


Please help with the config

Hello,
I need some help with my cofig.
Setup: 2BMS on a Smartshunt
BMS1: com.victronenergy.battery.ttyUSB0
BMS2: com.victronenergy.battery.ttyUSB1
Smartshunt: com.victronenergy.battery.ttyS7 n

what I want:
current from "Smartshunt" ;
voltages and SOC from BMS1;
I don't need BMS2
My config:
{
"excludedServices": [
"com.victronenergy.battery.ttyUSB1"
],
"primaryServices": {
"com.victronenergy.battery.ttyUSB0": [
"/Soc"
],
"com.victronenergy.battery.ttyS7": [
"/DC/0/Current"
]
},
"capacity": 584
}

This looks fine on the face of it. What actually happens?

Hello, thanks for the quick answer.
If I restart the cerbogx with this config, the battery aggregator does not start.
If I just exclude the smartshunt then it works
{
"excludedServices": [
"com.victronenergy.battery.ttyS7"
],
"capacity": 584
}

Please check the log.

Config:
{
"excludedServices": [
"com.victronenergy.battery.ttyUSB1"
],
"primaryServices": {
"com.victronenergy.battery.ttyUSB0": [
"/soc"
],
"com.victronenergy.battery.ttyS7": [
"/DC/0/Current"
]
},
"capacity": 584,
"logLevel": "DEBUG"
}
Log:
root@Cerbo-GX-Lan:~# cat /var/log/BatteryAggregator/current
@40000000676c598a0742546c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 3.0
@40000000676c598a0bc4524c INFO:main:Waiting for batteries (attempt 28 of 30)...
@40000000676c598a30cc64bc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.2
@40000000676c598a322f09cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -10.66
@40000000676c598b0bcc800c INFO:main:Waiting for batteries (attempt 29 of 30)...
@40000000676c598b31eba7cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.18
@40000000676c598b32c89664 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -9.6
@40000000676c598c06767cd4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>3164062
@40000000676c598c06d77124 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.9000000953674316
@40000000676c598c0bca41d4 INFO:main:Waiting for batteries (attempt 30 of 30)...
@40000000676c598c0bda2824 WARNING:main:No batteries discovered!
@40000000676c598c0bed69d4 INFO:main:Exit
@40000000676c599207c94364 INFO:main:Starting...
@40000000676c59920b116d6c INFO:dbusmonitor:===== Search on dbus for services that we will monitor starting... =====
@40000000676c59920b881854 INFO:dbusmonitor:Found: com.victronenergy.settings, scanning and storing items
@40000000676c599315e8c99c INFO:dbusmonitor:       com.victronenergy.settings has device instance 0
@40000000676c59931764078c INFO:dbusmonitor:Found: com.victronenergy.system, scanning and storing items
@40000000676c599329073644 INFO:dbusmonitor:       com.victronenergy.system has device instance 0
@40000000676c59932b833e7c INFO:dbusmonitor:Found: com.victronenergy.battery.ttyS7, scanning and storing items
@40000000676c59932ea5101c INFO:dbusmonitor:       com.victronenergy.battery.ttyS7 has device instance 279
@40000000676c59933079bc94 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyUSB0, scanning and storing items
@40000000676c59940008a4e4 INFO:dbusmonitor:       com.victronenergy.battery.ttyUSB0 has device instance 2
@40000000676c599401026a4c INFO:dbusmonitor:===== Search on dbus for services that we will monitor finished =====
@40000000676c5994086e979c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.09
@40000000676c599408802b9c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -4.59
@40000000676c599408902d44 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.08
@40000000676c599408b23434 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -4.13
@40000000676c599430a0ff5c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.07
@40000000676c59943179a064 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -3.72
@40000000676c5995068b2db4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>8554688
@40000000676c599506e140dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.5999999046325684
@40000000676c59950bca45bc INFO:main:Waiting for batteries (attempt 1 of 30)...
@40000000676c599530cedd8c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.06
@40000000676c599531683f2c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -3.35
@40000000676c59960bc7c904 INFO:main:Waiting for batteries (attempt 2 of 30)...
@40000000676c5996309ebd3c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -3.01
@40000000676c59970bcd1864 INFO:main:Waiting for batteries (attempt 3 of 30)...
@40000000676c5997327029ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.05
@40000000676c5997338d45f4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -2.71
@40000000676c59980bcd147c INFO:main:Waiting for batteries (attempt 4 of 30)...
@40000000676c599830d8f77c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -2.44
@40000000676c59990bc442ac INFO:main:Waiting for batteries (attempt 5 of 30)...
@40000000676c599930cee944 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.04
@40000000676c599931774abc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -2.2
@40000000676c599a06f7bac4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>0351562
@40000000676c599a070b46ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.5
@40000000676c599a0bc918f4 INFO:main:Waiting for batteries (attempt 6 of 30)...
@40000000676c599a30a56c2c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.98
@40000000676c599b0bc311fc INFO:main:Waiting for batteries (attempt 7 of 30)...
@40000000676c599b2ff7617c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.03
@40000000676c599b319d39ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.78
@40000000676c599c0bc64a34 INFO:main:Waiting for batteries (attempt 8 of 30)...
@40000000676c599c300b81d4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.6
@40000000676c599d0bc98e24 INFO:main:Waiting for batteries (attempt 9 of 30)...
@40000000676c599d31bde8dc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.44
@40000000676c599e06e63a4c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>9208984
@40000000676c599e06fdc1bc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.4000000953674316
@40000000676c599e0bccca44 INFO:main:Waiting for batteries (attempt 10 of 30)...
@40000000676c599e308205ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.02
@40000000676c599e3133dd04 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.3
@40000000676c599f0bc24ac4 INFO:main:Waiting for batteries (attempt 11 of 30)...
@40000000676c599f2fb19a34 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.17
@40000000676c59a00bc86d14 INFO:main:Waiting for batteries (attempt 12 of 30)...
@40000000676c59a030f62824 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -1.05
@40000000676c59a10bc96714 INFO:main:Waiting for batteries (attempt 13 of 30)...
@40000000676c59a1308d09fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.95
@40000000676c59a206dedf7c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>8066406
@40000000676c59a2073cc2a4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.299999952316284
@40000000676c59a20bc0bc54 INFO:main:Waiting for batteries (attempt 14 of 30)...
@40000000676c59a2319df144 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.85
@40000000676c59a30bd486bc INFO:main:Waiting for batteries (attempt 15 of 30)...
@40000000676c59a3310a199c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.01
@40000000676c59a3320682cc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.77
@40000000676c59a40bd5cedc INFO:main:Waiting for batteries (attempt 16 of 30)...
@40000000676c59a430a73d04 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.69
@40000000676c59a50bc8d68c INFO:main:Waiting for batteries (attempt 17 of 30)...
@40000000676c59a530894cf4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.62
@40000000676c59a60bd4389c INFO:main:Waiting for batteries (attempt 18 of 30)...
@40000000676c59a630f26734 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.56
@40000000676c59a70bc9a97c INFO:main:Waiting for batteries (attempt 19 of 30)...
@40000000676c59a731a9b4fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.5
@40000000676c59a806f4d494 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>9863281
@40000000676c59a8070fc31c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.200000047683716
@40000000676c59a80bc8e62c INFO:main:Waiting for batteries (attempt 20 of 30)...
@40000000676c59a8308fb594 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.45
@40000000676c59a90bc5447c INFO:main:Waiting for batteries (attempt 21 of 30)...
@40000000676c59a9311a8c8c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.41
@40000000676c59aa0bd24884 INFO:main:Waiting for batteries (attempt 22 of 30)...
@40000000676c59aa31021abc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.37
@40000000676c59ab0bcf46fc INFO:main:Waiting for batteries (attempt 23 of 30)...
@40000000676c59ab3077768c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.33
@40000000676c59ac06d7fdc4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>8720703
@40000000676c59ac07b9592c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.0999999046325684
@40000000676c59ac0bdcf6e4 INFO:main:Waiting for batteries (attempt 24 of 30)...
@40000000676c59ac32fc15fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.3
@40000000676c59ad0bc776fc INFO:main:Waiting for batteries (attempt 25 of 30)...
@40000000676c59ad31c5a16c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.27
@40000000676c59ae0bca6ccc INFO:main:Waiting for batteries (attempt 26 of 30)...
@40000000676c59ae309c57f4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Current -0.0
@40000000676c59ae31446f34 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.24
@40000000676c59af06a4300c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /ConsumedAmphours -433.79998779296875
@40000000676c59af0bc4db04 INFO:main:Waiting for batteries (attempt 27 of 30)...
@40000000676c59af30dd4124 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.22
@40000000676c59b00bc7d4bc INFO:main:Waiting for batteries (attempt 28 of 30)...
@40000000676c59b031c7fee4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.19
@40000000676c59b10bcaca8c INFO:main:Waiting for batteries (attempt 29 of 30)...
@40000000676c59b12f671be4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.18
@40000000676c59b206a8b44c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>0517578
@40000000676c59b206bd6144 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 2.0
@40000000676c59b20bd06fdc INFO:main:Waiting for batteries (attempt 30 of 30)...
@40000000676c59b20bea0a8c WARNING:main:No batteries discovered!
@40000000676c59b20c03300c INFO:main:Exit
@40000000676c59b43ab9bac4 INFO:main:Starting...
@40000000676c59b501abba0c INFO:dbusmonitor:===== Search on dbus for services that we will monitor starting... =====
@40000000676c59b50204fd9c INFO:dbusmonitor:Found: com.victronenergy.settings, scanning and storing items
@40000000676c59b523177794 INFO:dbusmonitor:       com.victronenergy.settings hasdevice instance 0
@40000000676c59b525417f9c INFO:dbusmonitor:Found: com.victronenergy.system, scanning and storing items
@40000000676c59b531b2501c INFO:dbusmonitor:       com.victronenergy.system has device instance 0
@40000000676c59b532848c6c INFO:dbusmonitor:Found: com.victronenergy.battery.ttyS7, scanning and storing items
@40000000676c59b535e514bc INFO:dbusmonitor:       com.victronenergy.battery.ttyS7 has device instance 279
@40000000676c59b536787734 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyUSB0, scanning and storing items
@40000000676c59b53b74fc44 INFO:dbusmonitor:       com.victronenergy.battery.ttyUSB0 has device instance 2
@40000000676c59b600887b74 INFO:dbusmonitor:===== Search on dbus for services that we will monitor finished =====
@40000000676c59b632fce8ec DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.1
@40000000676c59b70bd2b9cc INFO:main:Waiting for batteries (attempt 1 of 30)...
@40000000676c59b73201df4c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.09
@40000000676c59b80bd63c3c INFO:main:Waiting for batteries (attempt 2 of 30)...
@40000000676c59b834242ec4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.08
@40000000676c59b906d584f4 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power<PHONE_NUMBER>2314453
@40000000676c59b906efb7fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 1.899999976158142
@40000000676c59b90bc16834 INFO:main:Waiting for batteries (attempt 3 of 30)...
@40000000676c59ba0bd6fba4 INFO:main:Waiting for batteries (attempt 4 of 30)...
@40000000676c59ba344a3524 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.07
@40000000676c59bb0bd0e124 INFO:main:Waiting for batteries (attempt 5 of 30)...
@40000000676c59bb346c9204 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.06
@40000000676c59bc0bc64e1c INFO:main:Waiting for batteries (attempt 6 of 30)...
@40000000676c59bc32f56edc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.05
@40000000676c59bd0bcd2bec INFO:main:Waiting for batteries (attempt 7 of 30)...
@40000000676c59be0bcb3404 INFO:main:Waiting for batteries (attempt 8 of 30)...
@40000000676c59be344c7f14 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.04
@40000000676c59bf0bd0c1e4 INFO:main:Waiting for batteries (attempt 9 of 30)...
@40000000676c59c00bc586e4 INFO:main:Waiting for batteries (attempt 10 of 30)...
@40000000676c59c036a47104 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /TimeToGo None
@40000000676c59c10bd895cc INFO:main:Waiting for batteries (attempt 11 of 30)...
@40000000676c59c1344e1554 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.03
@40000000676c59c206e5675c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power 95.11199951171875
@40000000676c59c206fa8d6c DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 1.7999999523162842
@40000000676c59c20bc1d97c INFO:main:Waiting for batteries (attempt 12 of 30)...
@40000000676c59c30bcbd814 INFO:main:Waiting for batteries (attempt 13 of 30)...
@40000000676c59c40bc7387c INFO:main:Waiting for batteries (attempt 14 of 30)...
@40000000676c59c433fe62fc DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.02
@40000000676c59c50bc90954 INFO:main:Waiting for batteries (attempt 15 of 30)...
@40000000676c59c60bc9d474 INFO:main:Waiting for batteries (attempt 16 of 30)...
@40000000676c59c70bcb89f4 INFO:main:Waiting for batteries (attempt 17 of 30)...
@40000000676c59c80bd716fc INFO:main:Waiting for batteries (attempt 18 of 30)...
@40000000676c59c90bca5174 INFO:main:Waiting for batteries (attempt 19 of 30)...
@40000000676c59c9343b3164 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.01
@40000000676c59ca0bcc5ce4 INFO:main:Waiting for batteries (attempt 20 of 30)...
@40000000676c59cb0bd0c9b4 INFO:main:Waiting for batteries (attempt 21 of 30)...
@40000000676c59cc06b20704 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Power 89.8280029296875
@40000000676c59cc06c479ac DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyS7 /Dc/0/Current 1.7000000476837158
@40000000676c59cc0bcf0c64 INFO:main:Waiting for batteries (attempt 22 of 30)...
@40000000676c59cd0bd968bc INFO:main:Waiting for batteries (attempt 23 of 30)...
@40000000676c59ce0bc924ac INFO:main:Waiting for batteries (attempt 24 of 30)...
@40000000676c59cf0bcc2a1c INFO:main:Waiting for batteries (attempt 25 of 30)...
@40000000676c59d00bd97474 INFO:main:Waiting for batteries (attempt 26 of 30)...
@40000000676c59d10bcf0494 INFO:main:Waiting for batteries (attempt 27 of 30)...
@40000000676c59d20bd44c24 INFO:main:Waiting for batteries (attempt 28 of 30)...
@40000000676c59d30bcebe44 INFO:main:Waiting for batteries (attempt 29 of 30)...
@40000000676c59d3342b3b74 DEBUG:com.victronenergy.battery.aggregator:Battery value changed: com.victronenergy.battery.ttyUSB0 /Dc/0/Power -0.0
@40000000676c59d40bf57854 INFO:main:Waiting for batteries (attempt 30 of 30)...
@40000000676c59d40bf5a34c WARNING:main:No batteries discovered!
@40000000676c59d40bf5af04 INFO:main:Exit

You need to either add "/DC/0/Voltage" or everything with []. Currently the minimum requirement for a battery is that it has a voltage. My suggested config would be:
{
"excludedServices": [
"com.victronenergy.battery.ttyUSB1"
],
"primaryServices": {
"com.victronenergy.battery.ttyS7": [
"/DC/0/Current"
],
"com.victronenergy.battery.ttyUSB0": []
},
"capacity": 584
}

That is, you want everything from the BMS, but you want the current from the shunt to override that of the BMS.


Vivature - CSV Uploader Onboarding

Sender Info:

Sender/Company Name: Vivature
Type of Sender: EMR offering COVID solutions to schools, universities and sport teams.
Referred By:  CA-DPH
Location: Addison, TX

Standard Tasks / Onboarding Steps:
Initial Interest & Follow Up:
Sender Setup:
- Create OKTA group & OKTA account
- Create Sender Settings for Staging & PROD
Testing
- Prod/Test Internal
- Prod/Test External (if required by the STLT)

Closed this EPIC and all related Issues.  Moved to EPIC/Issue #:4119


DOCU-2415: updates Services and Routes getting started section

Summary
Brings the Services and Routes section of the getting started guide up to date w/ the Get Kong page.
This is PR 2 in a series that will bring the entire Getting Started section together as a tutorial like unit.
Reason
Improve the getting started experience for docs users.
Testing
Built docs locally

Document is still WIP

I believe this PR will require some rebasing after https://github.com/Kong/docs.konghq.com/pull/4284 and potentially resolving conflicts in TOC and moved urls documents.

rebased on release/gateway-3.0 and force pushed


Is it possible to recover overwritten marimo notebooks (.py files)?

Describe the bug
Is it possible to recover overwritten marimo notebooks (.py files)? I launched two different scripts in the same port and one overwrote the other, it seems.
Longer version/more details:
I was working in VS code (version 1.84.2) with a remote ssh connection. In the terminal of the ssh machine, I typed marimo edit remote_script.py which launched localhost:2718 (the default) in my local browser. I edited and saved there, with the "Notebook saved" notification on the bottom right corner popping up often.
I have, at the same time, another VS code window open that is local. When I typed marimo edit different_script.py in the terminal (of this local window) where different_script.py is a blank script, it launched to localhost:2718 in my local browser again by default, because I meant to but forgot to specify a port. Unfortunately, this action seemed to have overwritten the remote_scripty.py in my remote session.
I have tried a few different ways to recover the saving history, including looking at VS code Timeline/local history. The most recent save is my latest commit, ~2 days ago. I am able to see the edit history of my other scripts in the past two days though.
Thank you!
Version
0.1.43
Code to reproduce
No response

Hi @akshayka, thanks for the quick and compassionate response. The loss is not huge and I am almost done rebuilding the progress.
Your understanding is correct. I meant to reproduce the error too and will do that as soon as I can.
From what I recall, launching the tutorials in the same port did not lead to this overwriting issue. Instead, it displayed some error message on the browser page which I don't exactly recall. So it could be the case that this happens only when starting a blank new script. But mostly speculation now; more on that when I can.

Hi @tdiao. We've implemented a fix (in #367) and released it as part of version 0.1.53. Thanks so much once again for the thorough report!
I'll close this issue for now. But please write back and re-open if you're still running into issues.


[+] THC & COPC

[+] Added THC
[+] Added COPC

@tobezdev Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


WIP: add analysis run engine

This is still a work in progress

Closing to reopen and restart travis

Current coverage is 81.69% (diff: 81.69%)

No coverage report found for master at a671358.

Powered by Codecov. Last update a671358...f9a2bc6

@chiahaoliu @sbanerjee23 @sbillinge This is ready for review.

@tacaswell @danielballan if you get a second can you take a look at this?

Hard-coding the inserts into mds/fs I think is a bit of an anti-pattern as is assuming that the source databroker and the destination databroker are the same.   Probably better to start with taking in the event streams.
I suggest embracing dicts over 'happen to be aligned' lists.
Instead of doing a frame-work thing first, I strongly suggest just manually writing out the analysis store integration, it will probably be less work than manually marking up every function you want to use with a sufficient amount of metadata.  Once this has been done at a couple of beamlines, we might know enough to start generalizing.
Also suggest embracing python3 with annotation + signature.
Have a look at https://github.com/qiime2/qiime2 which is much farther along at automatically marking up analysis functions (but from their scipy talk seem very tied to their version of data artifacts).
The core of what you have here (wrapping functions in objects, using a higher-layer executor to run the wrapped functions, optionally serialize the results) is the core of what vistrails does.
There does not seem to be a way to chain multiple steps together?
See https://github.com/BrookhavenNationalLaboratory/pyRafters for my abandoned attempt at something like this.
[ran out of time on the train]

@tacaswell Thank you very much for your through review (I shudder to think what would have happened if you didn't run out of time).
I think I will try to address your comments piecemeal since each one deserves quite a bit of thought.
Under the current code one could simply hand the output header from one analysis run engine to another to chain the two together. In the long run I personally would like to use dask, see #2. I have very little interest in performing the scheduling/task graph assembling/optimization myself. Ideally I would like this system to just act as a passive observer, tracking what went in and what went out with enough metadata to recreate things (if possible). The similar logic applies to vistrails, I would hope that this could just observe what is going on without getting into the problem of how users assemble their workflows.

I guess I am a bit uncertain about "I suggest embracing dicts over 'happen to be aligned' lists." what do you mean?

I will definitely start using annotations for the functions, is it ok to use them as info for the documents?


[BUG] DataFactoryResource.GetDataFactoryLinkedServices() JSON deserialization error

Library name and version
Azure.ResourceManager.DataFactory 1.0.0-beta.4
Describe the bug
Trying to get all the linked serivices from a DataFactoryResource. The foreach enumeration of the result (kind of) works for the first n-items, then a deserialization exception comes.
Expected behavior
All the linked data-sources must be reachable in the foreach loop
Actual behavior
At some index, the loop breaks, as the behind-the-scenes deserializer can't cast the result into a type-safe class (my guess).
ex.Message
"Unable to cast object of type 'System.Boolean' to type 'System.String'."
ex.StackTrace
"   at Azure.Core.Expressions.DataFactory.DataFactoryElementJsonConverter.Deserialize[T](JsonElement json)\r\n   at Azure.Core.Expressions.DataFactory.DataFactoryElementJsonConverter.Read(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options)\r\n   at System.Text.Json.Serialization.Converters.CastingConverter`2.Read(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options)\r\n   at System.Text.Json.Serialization.JsonConverter`1.TryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)\r\n   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)\r\n   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 utf8Json, JsonTypeInfo jsonTypeInfo, Nullable`1 actualByteCount)\r\n   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo jsonTypeInfo)\r\n   at System.Text.Json.JsonSerializer.Deserialize[TV
alue](String json, JsonSerializerOptions options)\r\n   at Azure.ResourceManager.DataFactory.Models.GoogleBigQueryLinkedService.DeserializeGoogleBigQueryLinkedService(JsonElement element)\r\n   at Azure.ResourceManager.DataFactory.Models.DataFactoryLinkedServiceProperties.DeserializeDataFactoryLinkedServiceProperties(JsonElement element)\r\n   at Azure.ResourceManager.DataFactory.DataFactoryLinkedServiceData.DeserializeDataFactoryLinkedServiceData(JsonElement element)\r\n   at Azure.ResourceManager.DataFactory.DataFactoryLinkedServiceCollection.<GetAllAsync>b__9_2(JsonElement e)\r\n   at Azure.Core.PageableHelpers.PageableImplementation`1.GetAsyncEnumerator(CancellationToken cancellationToken)+MoveNext()\r\n   at Azure.Core.PageableHelpers.PageableImplementation`1.GetAsyncEnumerator(CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()\r\n   at AzureReflector.AzureParsing.AzureEnumerator.EnumResourcesAsync(String resourceGroupName) in C:\\Projects\\swi
zzbits.sk\\dotnet\\AzureReflector\\AzureParsing\\AzureEnumerator.cs:line 70\r\n   at AzureReflector.AzureParsing.AzureEnumerator.EnumResourcesAsync(String resourceGroupName) in C:\\Projects\\swizzbits.sk\\dotnet\\AzureReflector\\AzureParsing\\AzureEnumerator.cs:line 70\r\n   at AzureReflector.AzureParsing.AzureEnumerator.EnumResourcesAsync(String resourceGroupName) in C:\\Projects\\swizzbits.sk\\dotnet\\AzureReflector\\AzureParsing\\AzureEnumerator.cs:line 52"

Reproduction Steps
Try to get all the linked resources in a DataFactoryResource: there is somewhere a deserialization bug while iterating through the JSON internally - I can't tell where from your log message, as the actual JSON is not logged.
// here, the loop breaks at some index, trying interally to cast a Bool to String
await foreach (var resource in resourceGroup.GetGenericResourcesAsync())
{
  if (resource.Id.ResourceType.ToString() == "Microsoft.DataFactory/factories"
  {
    var dfRsrc = _armClient.GetDataFactoryResource(resource.Id);
    var r2 = await dfRsrc.GetAsync();
    var lsR = r2.Value.GetDataFactoryLinkedServices().GetAllAsync();

    // while looping, at some index the exception breaks the execution
    await foreach (var ls in lsR)
    {

Environment
C:\Users\andy>dotnet --info
.NET SDK:
 Version:   7.0.402
 Commit:    791db8e2d8

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.402\

Host:
  Version:      7.0.12
  Architecture: x64
  Commit:       4a824ef37c

.NET SDKs installed:
  7.0.402 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.23 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

This seems to indicate an issue with the definition of one of the properties in GoogleBigQueryLinkedService, or potentially with what the service is sending back for one of the properties. In particular, RequestGoogleDriveScope is defined as DataFactoryElement<string> but perhaps a bool is coming back. Does the error not occur for the first element? If it did that would indicate the type in the library is wrong. If it doesn't, it seems the service is sending back inconsistent results.
/cc @ArthurMa1978

It's happening not on the 1st element, but on the 8th or something like that => it seems like a problem of casting a bool into string. I didn't look into the sources nor decompiled them, but you should call a .ToString() on the deserialized result just to be on the safe-side ;-). TY

This points to the API definition potentially being inaccurate for the property mentioned. @ArthurMa1978, are you able to confirm with the service team whether RequestGoogleDriveScope can contain both a bool or a string? If so, we may need to modify the swagger to represent this as DataFactoryElement<BinaryData>.

@visingla-ms, @Frey-Wang any idea here on whether RequestGoogleDriveScope is defined correctly?

@SuperNose could you please https://www.nuget.org/packages/Azure.ResourceManager.DataFactory/ 1.0.0 version. It should resolve that issue.

Fixed in https://github.com/Azure/azure-rest-api-specs/pull/26507


Foreach children in template - this.children unexpected behaviour

Hello there,
I have recently asked this question on SO.
But afther doing a bit more investigation I found some strange behaviour with th this,children property in Chrome and FF.
I have created a simple repo that demonstrates the behaviour.
With FF the behaviour happens because one of the children contains a custom element, if I remove the custom element then it behaves as expected,

Inside firstUpdated the property this.children is returning 0 in Chrome when I expect it to be 4.

Even more bizarrely, FireFox output 3 children, but when I expand the console log I can see lenght: 4.
(<span> contains a custom element)

You can see on the console log that children.length: 3 but when I expand then length: 4

Does anyone have any idea what is happening have?

I have just found this SO question.
If I add a setTimeout in my ComponentOne then all is fine:
    firstUpdated() {
        setTimeout(() => {
        console.log("In FF, this.children == 3, in Chrome it == 0 - Why?")
        console.log("Children length " + this.children.length);
        console.log(this.children);
        console.log("Now in FF when we expand we have 4 children - Why?")
        }. 100);
    }

But the problem is that the children are just ordinary HTML elements, I cannot await updateCompleted

The best way to handle children is to assume that they change at any time (they can) and dynamically handle children changing via a slot and the slotchage event.

hmmm, I wonder would it be possible to use asyncReplace to render the children within the template?
Now I understand more about the event loop and slots I will do some more investegation.

I guess I will close this as it is expected browser behaviour...


Add LegacyEmitter that will by default use legacy or high compatibility modes

Based on #25.  Add a new emitter, so for non-current EPSON printer users, or 3rd party printers, they could use a LegacyEmitter that will use the legacy image print technique by default.

This is not necessary as the only command that has shown incompatibilities with legacy models is the PrintImage command, and it has a flag isLegacy that will force the legacy print option.


InterlockedIncrement/Decrement fix

Ran across this over here:  https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b3e6bc26-2879-4a2a-a82c-2e97f811cafa/interlockedincrement-not-found-when-using-clr-and-windows-81-sdk-in-mfc-dll-vs-2012-project?forum=vcgeneral
I was looking at this, which might be a more "correct" solution:  https://inu-games.com/2018/10/15/sapi-in-ue4/

Moving code to a plugin structurally impacts the unreal VPinball game project - to get this to work, and to fix that project, follow these steps:
Requirements:  Git Bash

in your Source directory, delete or remove com.h, VPmame.h, & VPmame.cpp (these are all in the plugin now)
If it doesn't already exist, create a 'Plugins' folder in your unreal project directory (VPinball)
Using file explorer, right click on that Plugins folder, and select "Git Bash Here"
In git bash, do a 'git clone https://github.com/datasung/Unreal-Visual-Pinball' into Plugins folder (use git bash) - you can test this using my fork if you'd like to test it before merging the pull request.
back in file explorer, right click on the VPinball.uproject file and select Generate Visual Studio project files
Open the VS project file (VPinball.sln) and rebuild your VPinball visual studio project
Yay!  Now you can open your unreal project (VPinball.uproject) and keep playing :-)
The plugin will be enabled by default and can be found under Project/Gameplay/UE4_VPinMAME


[CursorInfo] Implement a few expression references as solver-based

This implements cursor info resolving for a few expression types using the constraint system. This allows us to detect ambiguous results – we cannot deliver them yet but that will be done in a follow-up PR.

@swift-ci Please SourceKit stress test

@swift-ci Please SourceKit stress test

Stress tester failure at SceneDelegate.swift:unmodified:1981 is an improvement. A reduced reproducer is
protocol MyProto {
    static func makeInstance() -> Self
}

class Base: MyProto {
    static func makeInstance() -> Self {
        fatalError()
    }
}

class Inherited: Base {
    var member: Int
}

// RUN: %sourcekitd-test -req=cursor -pos=%(line + 2):30 %s -- %s
func foo() {
    Inherited.makeInstance().member = 2
}

The AST-based implementation reported Base as the receiver type, the solver-based implementation reports Inherited, which is correct.

Stress tester failure at SceneDelegate.swift:concurrent-708:703 is an improvement.
The AST-based implementation reported shared as a class variable, but it’s spelled as a static variable in source.

Stress tester failure at APIService.swift:unmodified:3766 is an improvement.
In the AST-based implementation on async in DispatchQueue.main.async no receiver was reported, the solver-based implementation reports OS_dispatch_queue.

@swift-ci Please SourceKit stress test

The AST-based implementation reported Base as the receiver type, the solver-based implementation reports Inherited, which is correct.

I wouldn't expect any receiver type here, it's statically resolvable. If the old implementation is returning dynamic here I'd say that's a bug.

In the AST-based implementation on async in DispatchQueue.main.async no receiver was reported, the solver-based implementation reports OS_dispatch_queue.

Is DispatchQueue.async @objc? If it isn't then as it's defined in an extension, it isn't overridable, and thus shouldn't be dynamic or have a receiver. As far as I can tell, it isn't, though maybe we're just missing the annotation in the generated interface.

@swift-ci Please SourceKit stress test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

@swift-ci Please SourceKit stress test

@swift-ci Please SourceKit stress test

@swift-ci Please SourceKit stress test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

Note to self: The stress tester only found failures in refactoring where previously we didn’t report any cursor, so all of those are improvements.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

@swift-ci Please smoke test Windows


Password-based auth will fail for installations upgraded from early 11.x EC and 1.4

The final portion of this change which invoked chef-mover to upgrade users to bcrypt-sha1 encryption  was never merged in:
https://github.com/opscode/opscode-omnibus/pull/212/files#diff-065818c635e5d9c58ec887ed71a64cbdR22
Note that the underlying schema change exists in the current 'migration 13', but the migration does not include the execution of chef-mover to update the data: https://github.com/opscode/opscode-omnibus/blob/master/files/private-chef-upgrades/001/013_bcrypt_users.rb
Because the conversion is never done, data is not migrated from the legacy password (sha1) to the new password form (sha1-bcrypt intermediate stage, or bcrypt).
Secondarily,   oc_erchef no longer looks in users.serialized_object field to validate a user's password, instead expecting them to  exist in the password-related columns of the user table.
Impacts

If an installation of chef server originated at 11.1.x  or earlier,  password data for users created prior to 11.2.x  is kept in the older sha1 hash format until they log in successfully via web ui.
if a certain upgrade path is followed, users will not be able to log into manage under 12.x (or directly authenticate against the /authenticate_user endpoint) until a password reset is performed for that user account.

Who Impacted

Installations of chef server that have upgraded from 11.1 or 1.4 -> 11.2
Installations of chef server that have upgraded from 11.x -> 12.x

Not impacted

Users created after installation 11.2 or higher
New installations that started after 11.2 or higher
users imported via upgrade from OSC 11.

Exceptions

if a user logged in while 11.2.x was installed, their password would have have been updated to the new format in the process of logging in.

Closing since this is no longer relevant. Sorry for the inconvenience caused.


Wrong gem name when requiring it

require 'google-translate' doesn't work.
require 'google_translate' does.

This isn't a bug. This is intentional. It's convention to not have filenames with hyphens in ruby, but gems are allowed to have hyphens in their names..


Allow to download just the simulation

[x] Download simulation
[x] Run only simulation
[x] Upload simulation
[x] Run only evaluation

Implemented in 6fddd12


Allow v1.3.x harvester cluster link to v1.3 doc

Summary
This PR updates the doc version from serverVersion().
PR Checklists

Do we need to backport this PR change to the Harvester Dashboard?

[ ] Yes, the relevant PR is at:

Are backend engineers aware of UI changes?

[ ] Yes, the backend owner is:

Related Issue
https://github.com/harvester/harvester/issues/6935
Test screenshot/video

Extra technical notes summary

Done rebase.


add a minimal cdelivery core that just includes the console, gogs, nexus, jenkins, sonaqube

add a minimal cdelivery core that just includes the console, gogs, nexus, jenkins, sonaqube

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/422/
Test PASSed.


Error: Unknown Dialect ~malformed~ when redefining a source already defined in an imported file

I defined a source airports in one file, imported this file into a second file, and accidentally defined a source in this file also named airports. Error was unhelpful and did not show the area causing the problem.

Every time this happens, what has happened is that the compiler has generated an error, but as it continues to parse the rest of the file, it does something which generates an exception, which means the error which is in the error log is never reported. I'll fix this one. Thanks.

I can't repro this, I get "Cannot redefine 'airports'" and then a warning about airports using : and not ? and then an unformatted dump of the error array in the preview window

I need a reproducible case, my attempt to repro from the screen shot has failed.

I have fixed some of these types of errors, it is possible that this will go away if you run something newer.

I'm also now unable to reproduce since updating to the brand new pre-release. Sorry about that--marking resolved!


Pluggable Services (with High Availability Strategies)

Currently services have the following attributes

name
binding
egressRouter
endpointAddress

To be able to support failover and HA capable services, we need to be able to support services with multiple endpoints. To support all of the use cases, we could split out the endpoint information into a separate structure.
Service would just retain

name

There would be a new structure, name TBD (endpoint, terminator, egressPoint), which would have the following attributes

id and/or name?
priority
binding
egressRouter
endpointAddress

When a new session is established the controller would pick an endpoint from all endpoints which had the highest priority.
For SDK applications which are binding, these entries would get created/removed dynamically. The binding would allow setting the priority. The priority could also be specified as -1, which would set the priority to one lower than the currently lowest priority.
So to model different scenarios -
HA - many endpoints with the same priority
Main/backups - N endpoints with priority 0, 1, etc...
Rolling failover - N endpoints, each one grabs the next lowest priority as they bind, so that we don't fail back when servers come back up
We could also store these entries associated to router and then dynamically add/remove them to/from the services as the router goes online/offline

Note: this will likely resolve #38

Prompted by discussions with @michaelquigley, going to examine this from the other perspective. The above looks at a solution and examines which use cases we could solve with it. Let's explicitly list which use cases we want to support and see what we need to support them.
Proposed Requirements

Ability to support multiple strategies, including pluggable strategies. This implies that we have an
API for strategies and a way to register them.
Bundled strategies should include:

some form of horizontal scale, where multiple endpoints can bind and the controller will load balance sessions across those endpoints using some algorithm
some form of active/passive, where multiple endpoints can bind, but the controller will use a single endpoint for all sessions until that endpoint fails, at which point the controller will failover to another endpoint.

Some way to provide per endpoint context, which can feed into endpoint selection strategies. Some examples of the kinds of context an endpoint might want to provide are:

Priority - This would allow a strategy to rank endpoints and select a subset of endpoints to load balance sessions across.
Weight - This would allow a strategy to better to decide how to load balance across endpoints. Endpoints with a lower weight would receive a lower percentage of sessions

Strategies could also use things like bind time and drive traffic to the endpoint which has been around the longest.
Proposal

Add EndpointStrategy API to fabric and allow registration of endpoint strategies
Add endpointStrategy field to service, so endpoint strategies can be configured per-service
Add endpoint entity to fabric model with the following fields

id - string
binding - string
egressRouter - string (must be existing router id)
endpointAddress - string
createdAt - datetime
strategyOptions - map[string]interface{}

The strategyOptions field could be a map of strategy name -> single value or map of values.
API
type TerminatingEndpoint struct {
    id string
    binding string
    egressRouter string
    endpointAddress string
    createAt time.Time
    strategyOptions map[string]
}

type EndpointStrategy interface {
    GetEndpoint(service *Service, clientId string, endpoints[]*TerminatingEndpoint) *TerminatingEndpoint
}

Example One
Let's suppose we have a webservice we want to provide horizontally scaled access, where endpoints are load balanced using random selection.

service

name: my-web-service
endpointStrategy: hs-random

binding 1

id:
binding: edge
egressRouter:
endpointAddress: hosted:
createdAt: Wed 19 Feb 2020 02:08:02 PM EST
strategyOptions: nil

binding 2

id:
binding: edge
egressRouter:
endpointAddress: hosted:
createdAt: Wed 19 Feb 2020 02:08:02 PM EST
strategyOptions: nil

Here the strategy doesn't require any contextual data. It would probably be implemented something like:
type HSRandomStrategy struct {}

func (HSRandomStrategy)  GetEndpoint(_ *Service, _ string, endpoints[]*TerminatingEndpoint) *TerminatingEndpoint {
   idx := rand.Intn(len(endpoints))
   return endpoints[idx]
}

Example Two
Let's suppose we have a database service where we have a primary and backup. We want to the primary if available, otherwise use the backup. We could represent this with priorities, where the primary gets priority 0 and the backup gets priority 1.

service

name: my-db
endpointStrategy: ha-priority

binding 1

id:
binding: edge
egressRouter:
endpointAddress: hosted:
createdAt: Wed 19 Feb 2020 02:08:02 PM EST
strategyOptions: map[string]interface{} { "ha-priority" : 0 }

binding 2

id:
binding: edge
egressRouter:
endpointAddress: hosted:
createdAt: Wed 19 Feb 2020 02:08:02 PM EST
strategyOptions: map[string]interface{} { "ha-priority" : 1 }

Here the strategy does require context.
// abbreviated type for example purposes
type TerminatingEndpoint struct {
	strategyOptions map[string]interface{}
}

func (e *TerminatingEndpoint) GetStrategyOptionsAsInt(strategyName string, defaultVal int) int {
	if e.strategyOptions == nil {
		return defaultVal
	}
	val, found := e.strategyOptions[strategyName]
	if !found {
		return defaultVal
	}
	iVal, ok := val.(int)
	if !ok {
		return defaultVal
	}
	return iVal
}

type PrioritySortedTerminatingEndpointList []*TerminatingEndpoint

func (p PrioritySortedTerminatingEndpointList) Len() int {
	return len(p)
}

func (p PrioritySortedTerminatingEndpointList) Less(i, j int) bool {
	p1 := p[i].GetStrategyOptionsAsInt("ha-priority", math.MaxInt32)
	p2 := p[i].GetStrategyOptionsAsInt("ha-priority", math.MaxInt32)
	return p1 < p2
}

func (p PrioritySortedTerminatingEndpointList) Swap(i, j int) {
	tmp := p[i]
	p[i] = p[j]
	p[j] = tmp
}

type HAPriorityStrategy struct {}

func (HAPriorityStrategy) GetEndpoint(_ *Service, _ string, endpoints[]*TerminatingEndpoint) *TerminatingEndpoint {
	sortable := PrioritySortedTerminatingEndpointList(endpoints)
	sort.Sort(sortable)
	return sortable[0]
}

Questions
Is map[string]interface{} overkill here? On the plus side it allows a binding to have separate options per strategy and allows any kind of data. On the downside it makes the data harder to work with (and crucially, less efficient) and we don't currently have any use cases that aren't covered by a simple number.

I think this looks pretty solid. A few things that we might consider:

Let's use interface{} instead of map[string]interface{}. That would flip the relationship around in the correct direction, letting the strategies define their own data model, and for cases where we're just using a simple "weight" or "priority" expressed as an int, we wouldn't have much cost in just asserting the interface{} to int.

We should make sure we standardize the terminology. Let's use terminatingRouter, or terminator instead of egressRouter.

I suspect we'll want to polish up the naming in general as this starts to flesh out. Some of the names are a little long, and feel a bit like Spring-style Java names (PrioritySortedTerminatingEndpointList for example).

But yes, this is looking good.

@r-caamano Brought up another use case which I hadn't considered. He wondered how this would enable a single SDK client using multiple terminating routers for redundancy.
I think from the fabric perspective, this should work fine as we can allow the SDK client to bind multiple times. The edge code and the SDK itself may need some facility to ensure that multiple binds reach multiple routers and that we don't bind more times than there are available routers.


Error creating machine after new CHEFDK release.

martinstev-ltm1:~ martin.stevens$ knife rackspace server create --server-name MSTEST -f 3 -I f2db6fd7-1e40-41f1-9ac0-ad8d1dfd7651
ERROR: Fog::Compute::RackspaceV2::InternalServerError: [HTTP 500 | req-5747fc8f-4a32-4724-9d5b-2ae2ef5df32d] The server has either erred or is incapable of performing the requested operation.

can you run this with debugging on?

knife rackspace server create -f 3 -I f2db6fd7-1e40-41f1-9ac0-ad8d1dfd7651 -VV
INFO: Using configuration from /Users/martin.stevens/.chef/knife.rb
DEBUG: version  (config)
DEBUG: version v2 (cli)
DEBUG: rackspace_api_key ***** (config)
DEBUG: rackspace_api_key ***** (cli)
DEBUG: rackspace_username  (config)
DEBUG: rackspace_username  (cli)
DEBUG: rackspace_api_username advertising1 (config)
DEBUG: rackspace_api_username  (cli)
DEBUG: rackspace_auth_url  (config)
DEBUG: rackspace_auth_url  (cli)
DEBUG: rackspace_auth_url https://identity.api.rackspacecloud.com/v2.0 (using)
DEBUG: rackspace_region LON (config)
DEBUG: rackspace_region LON (cli)
DEBUG: rackspace v2
DEBUG: https_proxy  (config)
DEBUG: http_proxy  (config)
DEBUG: using proxy  (config)
DEBUG: ssl_verify_peer  (config)
DEBUG: version  (config)
DEBUG: version v2 (cli)
DEBUG: rackspace_api_key ****** (config)
DEBUG: rackspace_api_key ***** (cli)
DEBUG: rackspace_username  (config)
DEBUG: rackspace_username  (cli)
DEBUG: rackspace_api_username advertising1 (config)
DEBUG: rackspace_api_username  (cli)
DEBUG: rackspace_auth_url  (config)
DEBUG: rackspace_auth_url  (cli)
DEBUG: rackspace_auth_url https://identity.api.rackspacecloud.com/v2.0 (using)
DEBUG: rackspace_region LON (config)
DEBUG: rackspace_region LON (cli)
DEBUG: rackspace v2
DEBUG: version  (config)
DEBUG: version v2 (cli)
DEBUG: rackspace_api_key ****** (config)
DEBUG: rackspace_api_key ****** (cli)
DEBUG: rackspace_username  (config)
DEBUG: rackspace_username  (cli)
DEBUG: rackspace_api_username advertising1 (config)
DEBUG: rackspace_api_username  (cli)
DEBUG: rackspace_auth_url  (config)
DEBUG: rackspace_auth_url  (cli)
DEBUG: rackspace_auth_url https://identity.api.rackspacecloud.com/v2.0 (using)
DEBUG: rackspace_region LON (config)
DEBUG: rackspace_region LON (cli)
DEBUG: rackspace v2
/opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/excon-0.54.0/lib/excon/middlewares/expects.rb:7:in response_call': [HTTP 500 | req-af703276-d6a3-4970-bec5-102e2c7cfa2a] The server has either erred or is incapable of performing the requested operation. (Fog::Compute::RackspaceV2::InternalServerError) 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/excon-0.54.0/lib/excon/middlewares/response_parser.rb:9:in response_call'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/excon-0.54.0/lib/excon/connection.rb:388:in response' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/excon-0.54.0/lib/excon/connection.rb:252:in request'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-core-1.43.0/lib/fog/core/connection.rb:81:in request' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-rackspace-0.1.4/lib/fog/rackspace/service.rb:42:in request'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-rackspace-0.1.4/lib/fog/rackspace/compute_v2.rb:166:in request' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-rackspace-0.1.4/lib/fog/rackspace/requests/compute_v2/create_server.rb:124:in create_server'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-rackspace-0.1.4/lib/fog/rackspace/models/compute_v2/server.rb:274:in create' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/fog-rackspace-0.1.4/lib/fog/rackspace/models/compute_v2/server.rb:232:in save'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/knife-rackspace-1.0.2/lib/chef/knife/rackspace_server_create.rb:439:in run' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/lib/chef/knife.rb:443:in block in run_with_pretty_exceptions'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/lib/chef/local_mode.rb:44:in with_server_connectivity' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/lib/chef/knife.rb:442:in run_with_pretty_exceptions'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/lib/chef/knife.rb:219:in run' 	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/lib/chef/application/knife.rb:156:in run'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.18.31/bin/knife:25:in <top (required)>' 	from /usr/local/bin/knife:57:in load'
from /usr/local/bin/knife:57:in `'

I noticed you've got knife-rackspace 1.0.2, but we haven't released a 1.0.2 version yet -- that seems a bit odd. It seems like I can reproduce the issue between 0.11.0 and 0.11.1 of knife-rackspace, so I've tracked it down to that. I won't have a ton of free cycles to debug this further but I'll assign the issue to me so I can chase it later unless someone else wants to pick it up before then.

I came across this thread because I encountered exactly this issue using fog directly.  I  have a working version on my laptop and a non-working version on a VM, so I'll work through the differences in versions and I'll post anything I find that I think will be of use here.

The problem appears to be a change between fog-rackspace 0.1.12 and 0.1.13.  I have raised a bug for it ( https://github.com/fog/fog-rackspace/issues/23 ).  In the meantime, as a workaround, simply downgrading the fog-rackspace gem to version 0.1.12 worked for me.
Good Luck.

The problem appears to be a change between fog-rackspace 0.1.12 and 0.1.13

@msommerville Should that be 0.1.2 and 0.1.3? I don't see the versions you mention on https://rubygems.org/gems/fog-rackspace/versions

Yes, it should - sorry.

This bug has been open for a rather long time - is a fix coming to ChefDK, or will the stable release (which doesn't work for us because of this bug) be yanked? This is an outright blocker for Rackspace Cloud users.

Also hitting this bug. Not sure what to do...

@trappar: I've had good luck downgrading fog-rackspace to 0.1.2 per @msommerville's suggestion.

/CC @mdarby too, since he was looking at fog-rackspace and the issue filed there.

Drying this up today

Seems this is the offender:
https://github.com/fog/fog-rackspace/commit/e41257fcb5aff3ef6fba72be70dec6614c4eafe8#diff-6c806c7bcc47991b339f88323d854897
I reverted that commit and pushed 0.1.5 here locally. Would someone care to test :master against their Chef/etc routines?

Thanks @mdarby! https://github.com/fog/fog-rackspace/issues/23 seems to have done the trick.
For anyone else following along, my method for testing was to manually install the gem before and after the fix:
$ cd fog-rackspace
$ git checkout 575a93c6e08379b23bad8e2155497b36d990c119
$ /opt/chefdk/embedded/bin/gem build fog-rackspace.gemspec
$ /opt/chefdk/embedded/bin/gem install fog-rackspace-0.1.3.gem
$ /opt/chefdk/embedded/bin/knife server create # ...
# failure

$ cd fog-rackspace
$ git checkout master
$ /opt/chefdk/embedded/bin/gem build fog-rackspace.gemspec
$ /opt/chefdk/embedded/bin/gem install fog-rackspace-0.1.5.gem
$ /opt/chefdk/embedded/bin/knife server create # ...
# success

I will push fog-rackspace 0.1.5 later today unless we see some fail cases.

Successfully registered gem: fog-rackspace (0.1.5)

Thanks @mdarby! All, I've released v1.0.4 of knife-rackspace, which has the fog-rackspace dependency pinned to be the new, fixed fog-rackspace release. Thanks for the help everyone!

Thanks @martinb3!


Add new Dice shuffle and win game in javascript projects

Added new game project in javascript section.

Good Contribution. Keep it up


Update Thailand holidays in 2025

Proposed change

Update Thailand holidays in 2025.

"Royal Ploughing Ceremony" date for 2025 is now confirmed as May 9, 2025.
SUN-MON-TUE format for "Songkran" holidays do indeed has in-lieu observance on WED as seen in 2014 and 2025, and has been fixed accordingly.

Type of change

[ ] New country/market holidays support (thank you!)
[x] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency update (version deprecation/pin/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] I've run make pre-commit, it didn't generate any changes
[x] I've run make test, all tests passed locally

In L614:
            Thailand(categories=GOVERNMENT, years=range(1960, 2024)),

everything works correctly (due to auto-expand), but for accuracy:
            Thailand(categories=GOVERNMENT, years=range(1960, 2026)),

@KJhellico I ended up refactoring all Thailand test cases to modern standards, so additional reviews will be needed here.


[highlighter] Add complex numbers pattern to our highlighter's number matching

Type of changes

[x] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[x] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
closes #2214
The fix in action:
In IPython:

In a Jupyter notebook:

In plain Python

No worries. We only really need to worry about what the repr for complex numbers can produce.
I'm afraid it does get more complex. If the imaginary part has an exponent, the regex fails.
e.g.  (-123123-2.1312342342423422e+25j)
I suspect that will occur almost never, but maybe we should try to support it.
I'm actually thinking that maybe the best approach would be to add a new regex for a new number type, which includes the parenthesis. So it matches (<NUMBER>(+/-)<NUMBER>j). What do you think?

I made some progress, but still not there for the moment... :sweat_smile:
Now my issue is that the "number" and "brace" patterns seem to take always precedence over the new "complex_number" one - which seem to make sense, at least for the brace, since (<NUMBER>(+/-)<NUMBER>j) does contain braces. Not sure what the best way to solve this could be? :thinking:

@willmcgugan I think I got there! It seems that I cannot prevent the "braces" to take precedence (even if I move the new complex_number matcher at the same level than it, outside of the _combine_regex() call), but apart from that it seems to work.
Here with a different visual style than "plain" numbers, just to illustrate that the matching is well and truly different:

What do you think? Good enough, or should we try harder to include the braces into this representation? :slightly_smiling_face:

Also, I just discovered that 3.4j is a valid imaginary number, and in that case (only an imaginary part) there are no braces in its repersentation!

Would you mind adding an entry in CHANGELOG.md with a link to the issue

Sure! Done in a02e5d6 :slightly_smiling_face:


Add logic to serialize/deserialize SetAccumulators

This is the second in a set of PRs to add support for spilling distinct aggregations (see full version in https://github.com/facebookincubator/velox/pull/7791).
The logic to serialize/deserialize SetAccumulators is used in the DistinctAggregations for spilling.

@mbasmanova : Have updated this code post rebase and addressing comments. PTAL.

@mbasmanova : Have updated the code to serialize to an ARRAY(VARBINARY) instead of a single String buffer. PTAL.

@xiaoxmeng : Meng, Would appreciate a round of review. Thanks !

@xiaoxmeng : Meng, ping for review. Thanks


Create confirmation box UI component

Fixes https://x-team-internal.atlassian.net/browse/XP-3374
Description
The purpose of this component is to serve as a generic confirmation box, to be rendered inside a modal.
ref: https://x-team-internal.atlassian.net/browse/XP-3374
Checklist

[x] set yourself as an assignee
[x] set appropriate labels for a PR (In Review or In Progress depending on its status)
[x] move respective JIRA issue to the IN REVIEW column
[x] make sure your code lints (npm run lint)
[x] Flow typechecks passed (npm run flow)
[x] Snapshots tests passed (npm run jest)
[x] manually tested the app by running it in several different browsers (Firefox, Chrome, Opera, Safari, MS IE/Edge, etc.) and checked nothing is broken and operates as expected!

Steps to Test or Reproduce
This component is not in use yet but it can be visualized on StoryBook.
Impacted Areas in Application
New core component created.
Screenshots

FYI: I shipped all the changes and now waiting for the build to pass on Netlify and Travis CI...

AND IT PASSED 🎉

I tested this PR with x-team/xp-registration#95 and works well. I had some feedback that need attention before approving this PR:

It's missing an updated bundle (make sure to run npm run build)
Move with Modal and random data to under Debug group http://localhost:9001/?path=/story/core-components-confirmationbox-use-cases--with-modal-and-random-data
The heading of the component should not have fixed height, this causes problems when it has more than 1 line of text
The class cx.ctaContainer probably don't need fixed height as well

Also make sure to check Nick's notes to change request.
Other than that this is very promising, great stuff @WagnerMoreira
Good call on these changes and thank you!

@WagnerMoreira Code looks good to me now, but found some UI related things to improve:

When Dismiss is rendered alone, its left-hand side (while hovering) isn't aligned with text box above. This can be fixed by using some pseudo selectors when the child is the only one so we remove left padding in that case

According to designs, we should use tuna color for the main content textL

Thank you so much for taking the time to review that! I pushed a commit addressing those 2 points

I'm leaving line-height there to match the designs, I don't think it can cause any issues but please let me know if anything comes to mind.

Yeah, line-height is valid to keep it, just need to remove height 👍

@bernardodiasc thank you so much for reviewing! I just pushed the changes addressing all the comments 👍


Mount point for volumes conflicts with Docker local volumes

/var/lib/docker/volumes/testa16
The volume mount point that is used should be outside of /var/lib/docker/volumes and likely associated to the volume manager.  Something like /var/lib/rexray/volumes would suffice.
https://github.com/docker/docker/issues/15880#issuecomment-135455678

Hi @clintonskitson,
I don't think I changed this code from the original, so it's likely what you had it. Are you asking me to change it because you want it relocated, or because you think I changed it from its original location? I only ask because I want to make sure that we have checks in place to ensure the suggested path exists.

I will make the change here and add a PR.

Hi Clint,
Let me as I want to move the path to the config area. Unless you want to create a config variable with default options.
--
-a
"I wonder if procrastinators realize that they're not putting off work, just putting it off onto other people?"

On Sep 15, 2015, at 10:51 AM, Clinton Kitson<EMAIL_ADDRESS>wrote:
I will make the change here and add a PR.
—
Reply to this email directly or view it on GitHub https://github.com/emccode/rexray/issues/27#issuecomment-140438811.

Nope, feel free.  If its a simple change to make it configurable, then I say go for it.  Otherwise, the only operational complexity I see with that is possibly having multiple RR instances running and the same volume trying to be mounted across the instances.  The first instance may allow it, but the second would atttempt it as well and likely fail.
I believe having a single path for both instances would be the best approach.  But I might differ from that if we said that all RR instances have the single path.

Let me clarify..

Allow each RR instance to have its own mount path
Allow configurable mount path for all instances
Don't allow configurable mount path

I would be in for #2 or #3 right now.

Hi @clintonskitson,
Don't get me wrong, I think it should absolutely be a single path for all instances. I do believe however that that path should be configurable.

Agree there

Yep, on same page.

Hi @clintonskitson,
We're going to have to do #3 for now as there's no good way to restrict a config value once set to be used for all instances. I know how I will do it, but it will involve too much work for this release.


Add deprecation warning

#68.

This uses python's warning system.
By default, only the first occurrence will be printed if it is used in __main__.
ref: https://docs.python.org/3/library/warnings.html#:~:text=category for warn().-,DeprecationWarning,-Base category for


fix inotify memory leak

What type of PR is this?
/kind bug
What this PR does / why we need it:
when delete file or dir , os will delete watch descriptor related to this path, file descriptor or watch descriptor not found, InotifyRmWatch syscall return EINVAL error, if return error, it may lead this path remain in watches and paths map, and no other event can trigger remove action.
Which issue(s) this PR fixes:

Fixes #100241
Special notes for your reviewer:
Release note:

/assign @thockin

Is there a way we can test this?  It SEEMS like a reasonably plausible change, but how do I know?

@thockin, i wrote a test function
package main

import (
	"flag"
	"fmt"
	"strings"
	"time"

	"k8s.io/utils/inotify"
)

func main() {
	var path string
	flag.StringVar(&path, "path", "", "path want to watch")
	flag.Parse()
	path = strings.TrimSpace(path)
	if len(path) == 0 {
		fmt.Println("error input path")
		return
	}
	watcher, err := inotify.NewWatcher()
	if err != nil {
		fmt.Println("create new watcher failed: ", err)
		return
	}
	err = watcher.Watch(path)
	if err != nil {
		fmt.Println("add watcher failed: ", err)
		return
	}
	for {
		select {
		case ev := <-watcher.Event:
			fmt.Println("event:", ev)
			eventType := ""
			switch {
			case ev.Mask&inotify.InDelete > 0:
				eventType = "delete"
			case ev.Mask&inotify.InDeleteSelf > 0:
				eventType = "delete"
			}
			if eventType == "delete" {
				time.Sleep(1 * time.Second)
                                err = watcher.RemoveWatch(path)
                                if err != nil {
                                        fmt.Println("remove watcher failed: ", err)
                                        return
                                }
			}
		case err := <-watcher.Error:
			fmt.Println("error:", err)
			return
		}
	}
}

watched input path, and i deleted this path,  test function watched InDelete or InDeleteSelf call RemoveWatch, you can see function return error

I really meant an automated test, but I'll approve for now.

/lgtm
/approve

Will you also update this in k/k ? I think we can make a case for this bugfix after code freeze, if we need to.

ok, i will submit a PR in k/k.

found that there are some projects may also needs update https://grep.app/search?q=k8s.io/utils/inotify


fix(typo): testPlugin -> testingPlugin

Summary
testPlugin -> testingPlugin

Related Links
closes #5046
Checklist

[x] I have added changeset via pnpm run change.
[x] I have updated the documentation.
[x] I have added tests to cover my changes.

nice catch！


Subscribing non persistent topic error if cluster disallow auto subscription creation

Describe the bug
I am trying to use non persistent topic on pulsar 2.7.2 non persistent topic. Pulsar cluster disallow auto subscription creation, allowAutoSubscriptionCreation=false.
I tried to create subscription using pulsar admin api but receiving error Create subscription on non-persistent topic can only be done through client
To Reproduce
Steps to reproduce the behavior:

Delopy a Pulsar cluster with allowAutoSubscriptionCreation=false
Create a non persistent topic non-persistent://test/test/topic1
Create a consumer to subscribe the topic
See error

Expected behavior
The consumer can subscribe the non persistent topic correctly.
Additional context
The pulsar admin disallow creating subscription on non persistent topic:
https://github.com/apache/pulsar/blob/016fb87039f44bdf3f8829797bb08a71e61483ab/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/v2/PersistentTopics.java#L1347-L1350
The broker reject the subscription:
https://github.com/apache/pulsar/blob/016fb87039f44bdf3f8829797bb08a71e61483ab/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/ServerCnx.java#L1013-L1022

Hi, Why create subscription on non persistent topic is not support by admin api? @hangc0276

Hi, Why create subscription on non persistent topic is not support by admin api? @hangc0276

Relative issue: #7397

@shibd For the non-persistent topic, the broker will not hold any messages. It looks like a message is forwarded between channels, from the producer channel to the consumer channel, so it does not make sense to create a subscription without a connected consumer


Thaumcraft does not load

I'm trying to get thaumcraft into my singleplayer game, but the mod doesn't load.
The game went through initialization finely without any crashes. I have optifine, TiC, forestry and other little mods like journey map, iron chest, etc that run without any issues.
Thaumcraft -1.12.2-6.1.BETA13.jar
Minecraft - 1.12.2
Forge - <IP_ADDRESS>55

No crashes, but what do the logs have to say about the mod, can you post a clean latest.log where allyou do is start the game? (Please use Gist for that.)

https://gist.github.com/baibai0909/c333862bb25bb61ef75145bebb1d6fe7 is this the right format.

Add the Baubles for correct operation the thaumcraft mod

I do have baubles. And it does run.

FML has found a non-mod file Thaumcraft-1.8.9-5.2.4.jar in your mods directory. It will now be injected into your classpath. This could severe stability issues, it should be removed if possible.

Okay. You either have a stray mod file in your folder, or you're somehow trying to get a version of TC5 for Minecraft 1.8.9 to run on Minecraft 1.12.2. :) Not going to happen.
Delete the old file and be sure you're using the newest TC beta for 1.12 from here.

https://minecraft.curseforge.com/projects/thaumcraft/files/2558648
I downloaded it from here. I now noticed the file say "1.8.9-5.2.4.jar"
The "Thaumcraft-1.12.2-6.1.BETA13.jar" and "Thaumcraft-1.12.2-6.1.BETA12.jar" are both 1.8.9.
I just redownloaded the Thaumcraft-1.12.2-6.1.BETA11.jar and it worked.
Thank you for rechecking the file.
And yes, there are some other mods I don't need anymore so I just left them.

Thaumcraft-1.12.2-6.1.BETA13.jar is 10,657,278 bytes long--that's a 1.12.2 mod, not 1.8.9. Not sure what you're downloading but the link provided works to get the Beta 13.
You'll be experiencing some bugs that have already been fixed if you use Beta 11, just be aware.


refactor query function

move code from the generated files to the query function itself
make it easier to know that is going to be executed

completed in https://github.com/agiletiger/ojotas/pull/34


Add modern Swift Concurrency support

Adds support for running commands that can be awaited on and deprecates previous non-async closure based methods.
Only one breaking change for Subprocess.init which no longer takes a QOS argument since the underlying implementation now uses Swift Concurrency instead of GCD. This version should be tagged as a major update: 3.0.0.
Subprocess methods return AsyncSequence which can use familiar Swift sequence operators (e.g. map, filter, etc).
Shell has been deprecated in favor of replacement static convenience methods added as extensions to Subprocess. One less class to remember.
Other miscellaneous changes and updates that feel more inline with Swift best practices since the last release of this package. Minimum version has been bumped to 10.15.4 in order to use non-objective-c exception throwing methods on FileHandle.

Yes, the functions still compile and work with the latest tools and OS. The deprecations were added in the case that a project needs to piecemeal adopt the new interface. The deprecations are also a hint that an updated usage of the package exists.

If that's the case, I'm not sure we want to mark the closure-based functions as deprecated unless we also plan on removing them at some future time.  Apple has provided async-await versions of URL loading functions but the classic functions still work and are not deprecated.  It's a choice of the consuming code to use async-await or not, and it seems like either choice should be acceptable from the point of view of this library as long as the functionality of both choices is essentially the same.
Forcing code that chooses to stick with classic GCD to also put up with deprecation warnings when using the most recent version of this library is not something I feel we need to do.

If that's the case, I'm not sure we want to mark the closure-based functions as deprecated unless we also plan on removing them at some future time. Apple has provided async-await versions of URL loading functions but the classic functions still work and are not deprecated. It's a choice of the consuming code to use async-await or not, and it seems like either choice should be acceptable from the point of view of this library as long as the functionality of both choices is essentially the same.
Forcing code that chooses to stick with classic GCD to also put up with deprecation warnings when using the most recent version of this library is not something I feel we need to do.

I see your point. I have restored the closure based launch methods.
I think the Shell class should still be deprecated and removed in some future version as the async replacements in Subprocess replace that class and have well defined concurrent execution points and Shell uses a synchronous wait that can't be canceled like its newer counterparts.


multi stream latency constrain wrong ?

https://github.com/mlperf/inference_policies/blob/master/inference_rules.adoc#41-benchmarks
mobilenet = 66ms
ssd-resnet34 = 50 ms
seems wrong. Need to swap this?

Looking at the "MLPerf Cloud/Edge Inference Matrix" spreadsheet, the rules document seems to have transposed the numbers. Sorry. It's probably my fault. @guschmue, would you like to write a PR to swap the latencies or should I?

sure can do.

done!


Ubi wsl

Adds a wsl image type based on the UBI package set.
The UBI package set isn't entirely identical to the current ubi images (2 or 3 packages differ), mostly because we don't include CRB.

Cleaning up.

wait @achilleas-k should I add the test case to osbuild/images rather than composer?

Tests / edge-ami-9 and Tests / edge-ami-cs9 needs a rebase because PR #3542 just got merged yesterday.

Sanne is out this week so I took care of the rebase.


Coverage complaining about lines outside the PR delta

First of all, I apologize if this is the wrong place to post this bug report. I do not have permissions to create a new topic in discuss.
My issue is that when we have a PR that touches a file with existing coverage issues, all of these issues are surfaced in a given PR rather than only the issues introduced or resolved by the pull request line delta. The analysis scope is set to "granular", yet existing coverage issues service anyway on lines not affected by a given pull request.

For a specific example, this pull request https://github.com/prysmaticlabs/prysm/pull/7488 was rather small in scope and only reduced a few redundant error checks. However, the coverage reporting says this pull request introduces two new coverage issues which are completely unrelated.

Please re-open. This issue was never addressed.


wpa_supplicant/hostapd: 2.10 -> 2.11

Description of changes
Please find the changelog per daemon below.
I kept privsep and epoll disabled, as they still do not work upstream.
Privsep does not support sending EAPOL frames over nl80211 control port, which would slow down network connection time significantly.
Changes for nixpkgs:

I dropped patches, that are upstream now.
I enabled 802.11be/Wi-Fi 7 in the configs. This is still not really settled, but we should try this, as the next release will probably take another 2-3 years.

Questions for discussion

Is #8332 still a thing or can we enable TLS 1.2 by default?
Should a release notes entry be added?

wpa_supplicant

Wi-Fi Easy Connect

add support for DPP release 3
allow Configurator parameters to be provided during config exchange

MACsec

add support for GCM-AES-256 cipher suite
remove incorrect EAP Session-Id length constraint
add hardware offload support for additional drivers

HE/IEEE 802.11ax/Wi-Fi 6

support BSS color updates
various fixes

EHT/IEEE 802.11be/Wi-Fi 7

add preliminary support

support OpenSSL 3.0 API changes
improve EAP-TLS support for TLSv1.3
EAP-SIM/AKA: support IMSI privacy
improve mitigation against DoS attacks when PMF is used
improve 4-way handshake operations

discard unencrypted EAPOL frames in additional cases
use Secure=1 in message 2 during PTK rekeying

OCV: do not check Frequency Segment 1 Channel Number for 160 MHz cases
to avoid interoperability issues
support new SAE AKM suites with variable length keys
support new AKM for 802.1X/EAP with SHA384
improve cross-AKM roaming with driver-based SME/BSS selection
PASN

extend support for secure ranging
allow PASN implementation to be used with external programs for
Wi-Fi Aware

FT: Use SHA256 to derive PMKID for AKM 00-0F-AC:3 (FT-EAP)

this is based on additional details being added in the IEEE 802.11
standard
the new implementation is not backwards compatible, but PMKSA
caching with FT-EAP was, and still is, disabled by default

support a pregenerated MAC (mac_addr=3) as an alternative mechanism
for using per-network random MAC addresses
EAP-PEAP: require Phase 2 authentication by default (phase2_auth=1)
to improve security for still unfortunately common invalid
configurations that do not set ca_cert
extend SCS support for QoS Characteristics
extend MSCS support
support unsynchronized service discovery (USD)
add support for explicit SSID protection in 4-way handshake
(a mitigation for CVE-2023-52424; disabled by default for now, can be
enabled with ssid_protection=1)

in addition, verify SSID after key setup when beacon protection is
used

fix SAE H2E rejected groups validation to avoid downgrade attacks
a large number of other fixes, cleanup, and extensions

http://w1.fi/cgit/hostap/tree/wpa_supplicant/ChangeLog?id=d945ddd368085f255e68328f2d3b020ceea359af
hostapd

Wi-Fi Easy Connect

add support for DPP release 3
allow Configurator parameters to be provided during config exchange

HE/IEEE 802.11ax/Wi-Fi 6

various fixes

EHT/IEEE 802.11be/Wi-Fi 7

add preliminary support

SAE: add support for fetching the password from a RADIUS server
support OpenSSL 3.0 API changes
support background radar detection and CAC with some additional
drivers
support RADIUS ACL/PSK check during 4-way handshake (wpa_psk_radius=3)
EAP-SIM/AKA: support IMSI privacy
improve 4-way handshake operations

use Secure=1 in message 3 during PTK rekeying

OCV: do not check Frequency Segment 1 Channel Number for 160 MHz cases
to avoid interoperability issues
support new SAE AKM suites with variable length keys
support new AKM for 802.1X/EAP with SHA384
extend PASN support for secure ranging
FT: Use SHA256 to derive PMKID for AKM 00-0F-AC:3 (FT-EAP)

this is based on additional details being added in the IEEE 802.11
standard
the new implementation is not backwards compatible

improved ACS to cover additional channel types/bandwidths
extended Multiple BSSID support
fix beacon protection with FT protocol (incorrect BIGTK was provided)
support unsynchronized service discovery (USD)
add preliminary support for RADIUS/TLS
add support for explicit SSID protection in 4-way handshake
(a mitigation for CVE-2023-52424; disabled by default for now, can be
enabled with ssid_protection=1)
fix SAE H2E rejected groups validation to avoid downgrade attacks
use stricter validation for some RADIUS messages
a large number of other fixes, cleanup, and extensions

http://w1.fi/cgit/hostap/tree/hostapd/ChangeLog?id=d945ddd368085f255e68328f2d3b020ceea359af
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 330386 run on x86_64-linux 1

7 packages built:

hostapd
hostapd.man
linux-router
linux-wifi-hotspot
wifish
wpa_supplicant
wpa_supplicant_gui

Can confirm What @LeSuisse Said - It seems to effect most if not all Broadcom chips so basically any Mac and lots of other computers besides.

We might want to revert upstream commit https://w1.fi/cgit/hostap/commit/?id=41638606054a09867fe3f9a2b5523aa4678cbfa5 until a proper fix land

That's what https://github.com/NixOS/nixpkgs/pull/333475 does.

This PR breaks wifi for Broadcom BCM43a0 802.11 Hybrid Wireless Controller <IP_ADDRESS>1 (r587334)
Just fails to activate interface and stays disconnected. nmtui doesn't event display it as an interface that's possible to activate.
please revert.


As a data provider/user I want to understand the definition of terms e.g. 'dataset' or 'survey' so I am clear on how to classify the data

Create a glossary in the data standard?

@kellymacleod agree this is part of data standard definition; not really a big deal/ticket

@kellymacleod agree this is part of data standard definition; not really a big deal/ticket

Steering Group Jan2020 agreed;
Will be included with the data standard, and relevant elements for development picked up through that route.