Smart Config fails on Gosund SP111: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC]

I'm unable to flash the Gosund SP111 (Version 2500 Watt) device.
The AP starts up, smartphone connects, SP111 is set into discovery mode (blue light blinks fast).
As soon as I start the flashing routine, the blinking stops, and the scripts tries to "Resend the SmartConfig Packets" until it times out.
Please find here my logs:
smarthack-psk.log
new client on port 443 from <IP_ADDRESS>:16557
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:48814
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:22643
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:39305
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:62224
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:23590
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:52637
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:36503
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:9530
ID: 02423f3f3f3f3f3f3f3f3f3f3f3f3f3f3f4cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
Prefix: b'B???????????????'
PSK: 1ba5826b9580b2c9bee1313c823a472a5afffc7725c94c2866017bd0f4b043b3
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:18564
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:18287
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:64759
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:16724
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:1363
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:18601
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:44869
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:24653
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:27214
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:17249
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:3004
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:28100
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:18425
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:8544
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:24596
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:8221
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:23001
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:9012
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:30844
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
new client on port 443 from <IP_ADDRESS>:10119
ID: 0242416f68626d643661473931494652314cc149fe6c7b373dacb48bc22278e3ddac47fa546639024d25a81a4c1f893174
PSK: f95ee0df92cd84cedce6c307d95bb7be81b523a91a84db72d4087277852944c4
could not establish sslpsk socket: [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:1056)
^CTraceback (most recent call last):
  File "./psk-frontend.py", line 113, in <module>
    main()
  File "./psk-frontend.py", line 106, in main
    r,_,_ =  select.select(readables, [], [])
KeyboardInterrupt

smarthack-udp.log
Listening for Tuya broadcast on UDP 6666
Listening for encrypted Tuya broadcast on UDP 6667
^C

smarthack-mqtt.log
1603202361: mosquitto version 1.5.7 starting
1603202361: Using default config.
1603202361: Opening ipv4 listen socket on port 1883.
1603202361: Opening ipv6 listen socket on port 1883.
^C1603202678: mosquitto version 1.5.7 terminating
1603202799: mosquitto version 1.5.7 starting
1603202799: Using default config.
1603202799: Opening ipv4 listen socket on port 1883.
1603202799: Opening ipv6 listen socket on port 1883.
^C1603203099: mosquitto version 1.5.7 terminating
1603203343: mosquitto version 1.5.7 starting
1603203343: Using default config.
1603203343: Opening ipv4 listen socket on port 1883.
1603203343: Opening ipv6 listen socket on port 1883.
^C1603205524: mosquitto version 1.5.7 terminating
1603205537: mosquitto version 1.5.7 starting
1603205537: Using default config.
1603205537: Opening ipv4 listen socket on port 1883.
1603205537: Opening ipv6 listen socket on port 1883.
^C1603207395: mosquitto version 1.5.7 terminating
1603207526: mosquitto version 1.5.7 starting
1603207526: Using default config.
1603207526: Opening ipv4 listen socket on port 1883.
1603207526: Opening ipv6 listen socket on port 1883.
^C1603207622: mosquitto version 1.5.7 terminating
1603207655: mosquitto version 1.5.7 starting
1603207655: Using default config.
1603207655: Opening ipv4 listen socket on port 1883.
1603207655: Opening ipv6 listen socket on port 1883.
^C1603208192: mosquitto version 1.5.7 terminating
1603208218: mosquitto version 1.5.7 starting
1603208218: Using default config.
1603208218: Opening ipv4 listen socket on port 1883.
1603208218: Opening ipv6 listen socket on port 1883.
^C1603213656: mosquitto version 1.5.7 terminating
1603213849: mosquitto version 1.5.7 starting
1603213849: Using default config.
1603213849: Opening ipv4 listen socket on port 1883.
1603213849: Opening ipv6 listen socket on port 1883.
^C1603214194: mosquitto version 1.5.7 terminating
1603214267: mosquitto version 1.5.7 starting
1603214267: Using default config.
1603214267: Opening ipv4 listen socket on port 1883.
1603214267: Opening ipv6 listen socket on port 1883.
^C1603214432: mosquitto version 1.5.7 terminating
1603216215: mosquitto version 1.5.7 starting
1603216215: Using default config.
1603216215: Opening ipv4 listen socket on port 1883.
1603216215: Opening ipv6 listen socket on port 1883.
^C1603216342: mosquitto version 1.5.7 terminating
1603216373: mosquitto version 1.5.7 starting
1603216373: Using default config.
1603216373: Opening ipv4 listen socket on port 1883.
1603216373: Opening ipv6 listen socket on port 1883.
^C1603216508: mosquitto version 1.5.7 terminating
1603216640: mosquitto version 1.5.7 starting
1603216640: Using default config.
1603216640: Opening ipv4 listen socket on port 1883.
1603216640: Opening ipv6 listen socket on port 1883.
^C1603216798: mosquitto version 1.5.7 terminating

smarthack-web.log
Listening on <IP_ADDRESS>:80
[I 201020 18:57:50 web:2250] 200 GET / (<IP_ADDRESS>) 5.29ms
^CReceived SIGINT, exiting...

smarthack-wifi.log
System info
===========
94acc3b
Linux octopi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
OpenSSL 1.1.1d  10 Sep 2019
Dnsmasq version 2.80  Copyright (c) 2000-2018 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
hostapd v2.8-devel
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2019, Jouni Malinen<EMAIL_ADDRESS>and contributors
Python 3.7.3
===========
Configuring AP interface...
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Starting DNSMASQ server...
Starting AP on wlan0...
Configuration file: /dev/stdin
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:39:59:5f and ssid "vtrust-flash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
wlan0: AP-STA-CONNECTED 50:02:91:10:10:6f
wlan0: AP-STA-DISCONNECTED 50:02:91:10:10:6f
wlan0: AP-STA-CONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-DISCONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-CONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-DISCONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-CONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-DISCONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-CONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-STA-CONNECTED 50:02:91:10:10:6f
wlan0: interface state ENABLED->DISABLED
wlan0: AP-STA-DISCONNECTED 50:02:91:10:10:6f
wlan0: AP-STA-DISCONNECTED 6c:c7:ec:7b:ee:54
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
AP closed
Stopping DNSMASQ server...

Duplicate #483, unsupported firmware


btrfs-progs: 6.5.3 -> 6.6

Changes: https://github.com/kdave/btrfs-progs/releases/tag/v6.6
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg build udiskie


Storage BoltDB

Current dependencies on/for this PR:

feature/proof-of-stake

PR #578

PR #599

PR #600

PR #601

PR #618

PR #619   👈

PR #617
PR #602

PR #603

This comment was auto-generated by Graphite.

Current dependencies on/for this PR:

feature/proof-of-stake

PR #578

PR #599

PR #600

PR #601

PR #618

PR #619   👈

PR #617
PR #602

PR #603

This comment was auto-generated by Graphite.

Current dependencies on/for this PR:

feature/proof-of-stake

PR #578

PR #599

PR #600

PR #601

PR #618

PR #619   👈

PR #617
PR #602

PR #603

This comment was auto-generated by Graphite.


Enhanced terminal mode keyboard (VDP protocol) support

Currently the command to turn on the terminal mode is binary - you can turn on terminal mode.  From that point on, the VDP assumes that the program running on the eZ80 is an application expecting the VDP to work as a pure terminal device and thus essentially stops all normal VDP operation.  From that point on, keyboard info is no longer sent back to the eZ80 using the VDP protocol but instead is captured on the VDP and ASCII bytes sent over to the eZ80.
It would be useful to allow for a different mode of operation for the terminal where the VDP protocol is allowed to continue, and for keyboard input (and other information, such as mouse data packets) to be sent.
It is suggested that the "enable terminal mode" command, which currently works as a "binary" on/off could accept different "enable" values to allow for the VDP protocol to continue operating.  This would allow for instance a BASIC program to use terminal mode for its output, but still allow its INPUT and GET$ keywords to operate.

upon investigation this idea has several problems associated with it
the terminal emulator inside vdp-gl has its own keyboard handling - some of this may need some de-coupling.  further investigation would be needed to work out exactly how the terminal emulator's keyboard handling may interact with the rest of the system.
as for allowing BASIC's INPUT keyword to work, it makes use of the MOS line editor, and that not only relies on the MOS VDP protocol's keyboard information packets to be sent, it will also perform other VDU commands to facilitate its operation.  as the VDU command processing isn't enabled, this doesn't work.  using INPUT from BASIC results in a spurious character being made visible on-screen, and the input will not work as expected
testing shows that GET$ also does not work
experimenting shows that the interaction for keyboard handling and the terminal mode is complex.  the existing support for suspending the terminal is done such that it just stops forwarding bytes from the eZ80 to the terminal emulator, and instead allow the VDP to process commands - VDP protocol keyboard handling is explicitly not properly resumed.  attempting to do so does not work - a BASIC program that enables terminal mode, prints some things out, and then suspends the terminal and attempts to perform an INPUT does not get all the key-presses.
the manner in which agon-vdp uses the Terminal is slightly odd - it connects the serial port to the terminal, but then also does its own out-of-bounds serial comms, including its own keyboard handling, which presumably replicates at least some of the internal behaviour of the terminal.  when the serial channel is not connected to the terminal, suspending the terminal from a BASIC program does allow the INPUT statement to work correctly


Something wrong with debugging and inspecting, generally interacting with elements

Description
https://github.com/user-attachments/assets/ec0cf844-cb67-4196-96f9-d3df0e4e4113
In video I just try to interact with search bar, and something don't allow me fully make text, and this is with ALL elements to interact with every page
Full steps to reproduce the issue
It's just default setting of puppeteer with last version
  "dependencies": {     "@2captcha/captcha-solver": "^1.3.0",     "axios": "^1.7.9",     "date-fns": "^4.1.0",     "dotenv": "^16.4.7",     "js-levenshtein": "^1.1.6",     "openai": "^4.76.1",     "playwright": "^1.48.2",     "playwright-extra": "^4.3.6",     "puppeteer": "^23.8.0",     "puppeteer-extra": "^3.3.6",     "puppeteer-extra-plugin-click-and-wait": "^2.3.3",     "puppeteer-extra-plugin-stealth": "^2.11.2",     "puppeteer-real-browser": "^1.3.17",     "puppeteer-screen-recorder": "^3.0.6"   },   "devDependencies": {     "@cloudflare/puppeteer": "^0.0.14"   }
It's not the full code, but the main part
`
const { connect } = require('puppeteer-real-browser');
const { page, browser } = await connect({
    headless: false,
    turnstile: true,
    fingerprint: true,
    customConfig: {
        devtools: true
    },
    args: [
        '--no-sandbox',
        `--proxy-server=${randomProxy.ip}:${randomProxy.port}`
    ],
    proxy: {
        server: `${randomProxy.ip}:${randomProxy.port}`,
        username: randomProxy.username,
        password: randomProxy.password
    }
})
await page.setRequestInterception(true);

page.on('request', (request) => {
    if (request.url().includes('screeb.app')) {
        request.abort();
    } else {
        request.continue();
    }
});

await page.setViewport(screenSize);

await page.authenticate({
    username: randomProxy.username,
    password: randomProxy.password
});`

Issue Type
Bug
Operating System
Mac OS
Do you use Docker?
I don't use Docker

it's because the turnstile, try set it to false.

turnstile

that's right, but I need turnstile also, is there any way to use it and avoid such beheviour?

turnstile

that's right, but I need turnstile also, is there any way to use it and avoid such beheviour?

why you really need turnstile set to true, is that appear on every page or what?

turnstile

that's right, but I need turnstile also, is there any way to use it and avoid such beheviour?

why you really need turnstile set to true, is that appear on every page or what?

not on every page, just I want to except such case

i think it's better to set it to false, and make the turnstile click "manually" based on some condition


Error: Unnotarized Developer ID (but everything works fine)

When running electron-forge make, I get the following errors:

Code sign failed; please retry manually.
Unnotarized Developer ID

But everything seems to be working. I get an email from Apple saying that the app was successfully notarized, and I'm able to open the the .app file without having to mess around with security settings. Any ideas what might be causing this?
Here's all the output:
✔ Checking your system
✔ Resolving Forge Config
We need to package your application before we can make it
✔ Compiling Main Process Code
✔ Compiling Renderer Template
✔ Preparing to Package Application for arch: x64
✔ Preparing native dependencies
⠇ Packaging ApplicationWARNING: Code sign failed; please retry manually. Error: Command failed: spctl --assess --type execute --verbose --ignore-cache --no-cache /var/folders/b2/39r20yb11fbd_ymjrmvtf5y80000gn/T/electron-packager/darwin-x64/Plumb-darwin-x64/Plumb.app
/var/folders/b2/39r20yb11fbd_ymjrmvtf5y80000gn/T/electron-packager/darwin-x64/Plumb-darwin-x64/Plumb.app: rejected
source=Unnotarized Developer ID
✔ Packaging Application
Making for the following targets: zip
✔ Making for target: zip - On platform: darwin - For arch: x64

Duplicate of #54

@malept Sorry—GitHub returned a 404 when I submitted the first time...I had assumed it didn't go through.


Only Build For amd64 Platforms

i386 and arm64 are currently included (default of goreleaser). We should update it to only build for arm64.

https://github.com/magneticstain/ip2cr/commit/9e644994e232b20212381cac5fdcde6c59ac220d


[BUG]: Introspection of Postgres tables with columns with LOCALTIMESTAMP default generates broken schema file

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.35.1
What version of drizzle-kit are you using?
0.26.2
Other packages
No response
Describe the Bug
Start with a table that has LOCALTIMESTAMP as default (this is part of the SQL standard):
create table test (test timestamp without time zone default LOCALTIMESTAMP);

Run npx drizzle-kit introspect and check the output schema.ts. You'll see:
export const test = pgTable("test", {
	test: timestamp({ mode: 'string' }).default(LOCALTIMESTAMP),
});

If you try to push this schema with npm drizzle-kit push, you'll get:
ReferenceError: LOCALTIMESTAMP is not defined

The work-around is to modify the schema and do the usual sql string interpolation that is needed for PG functions as default:
test: timestamp({ mode: 'string' }).default(sql`LOCALTIMESTAMP`),

Drizzle's introspect does this correctly in most cases, but not in this one, it seems.

Oops. Looks like this was fixed here:  https://github.com/drizzle-team/drizzle-orm/pull/2959
I pulled the latest (ORM 0.37 and kit 0.29) and I no longer see this problem. Closing.


Propositions of improvements in 'posts' tab

These are some propositions of improvements for Tamiat according to Wordpress features:

add posts categories in order to improve silo structure (for SEO)

add filtering (published, saved, all) and bulk actions (especially bulk delete)

searching post by title

sorting

edit categories and tags inside menu (under post tab)

confusing button values (add new && add)

maybe instead 'add' we can choose 'publish' and 'save draft'

maybe better would be 'featured image' instead

Does this search by title and sorting look okay?

Do we have some ideas on what categories should we have, do we let users input it as a new property in post?
For filtering we can maybe add a new property 'state' which can be published or saved?
Any suggestions on what to define as bulking actions? Maybe add a select box before post so the actions can be - select all, delete selected, etc?

Hello,

User should input it, usually we should be shiopping the hello world post with an example category.
Yes, publishing state is a good idea.
We can have the bulk action with delete only for now. and the method of markign as you said, select all, deselect all or manually check each post.

Generally speaking if in doubt, it would be a good idea to check how it is implemented in worpdress or ghost cms.

https://github.com/tamiat/tamiat/pull/125
https://github.com/tamiat/tamiat/pull/123
https://github.com/tamiat/tamiat/pull/120


Wrong auto-correct with block by method name replacement

Wrong replacement of a block with 2 actual arguments by SymbolProc causes an error with wrong number of arguments
slice_when{ |x| x.nil? } => slice_when(&:nil?)
=> nil? ArgumentError (wrong number of arguments (given 1, expected 0))

Expected behavior
slice_when{ |x| x.nil? } is incorrectly used because of two block variable should be specified here instead of one. Good behavior is to give recommendation that other method like slice_after should be used.
Actual behavior
C: Style/SymbolProc: Pass &:nil? as an argument to slice_when instead of a block.
[1, nil, 2, 3, nil, 4, 5, 6].slice_when{|x| x.nil?}.map(&:compact)
                                       ^^^^^^^^^^^^

Auto-correct produces unworkable code:
[1, nil, 2, 3, nil, 4, 5, 6].slice_when(&:nil?).map(&:compact)
#…
#>> ArgumentError (wrong number of arguments (given 1, expected 0))

Steps to reproduce the problem
[1, nil, 2, 3, nil, 4, 5, 6].slice_when{ |x| x.nil? }.map(&:compact)

RuboCop version
rubocop -V
0.61.1 (using Parser <IP_ADDRESS>, running on ruby 2.6.0 x86_64-darwin17)

Thank you for the report! 🙇
The root cause of this problem is that the original code does not properly reveal the yielded arguments, e.g.:
slice_when { |x, _| x.nil? }

Because the second argument is implicitly discarded, RuboCop gets the signature wrong. Unfortunately it's not realistic to keep a lookup table of the block arity of all standard library methods. Even if we did, the above would still be a false positive for user implemented methods.
What we can do is mark the auto-correct of Style/SymbolProc as unsafe, which will make it disabled by default.


Fix safer-destructive-actions on comments

Re-implements the suggestion from #410 which recently broke since GitHub seems to have changed their markup/CSS a bit.
Test
Test in any of your own issues, so I can't link any specific one here. 🙂

Oh, sure — didn't have that in mind at all. 😅

Thank you! :)

My pleasure. 🙂


[stable/rabbitmq] Existing secret values switches for password / erlang cookie

Signed-off-by: Louise Champ<EMAIL_ADDRESS>What this PR does / why we need it:
This PR allows predefined Rabbitmq passwords (and by extension erland cookies, as these values together in the same secret) to be managed external of the Rabbitmq Helm chart.
Special notes for your reviewer:
The chart creates its own secret, by default, so some additional logic has been added to this secret to ensure it is not generated if values have been defined for existingPasswordSecret and existingErlSecret.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

It seems there are conflicts with master files...can you resolve them?


CoreLightningRestWallet: Error in paid_invoices_stream

i'm running an lnbits instance with CoreLightningRestWallet on the backend
(separate node) and i'm getting "| ERROR | Error in paid_invoices_stream:"

Originally posted by @hdlslm in https://github.com/lnbits/lnbits/issues/2045#issuecomment-1791541156

thanks for editing. also not sure if it matters but my wallet has not been funded and i don't have any channels open.

hey can you try on latest? it might just be cln rest returning an error we don't catch if there are no channels open.
also can you share the logs what when it is initializing the fundingsource?

I believe this is still an issue.  I have a funded Core Lightning node running v24.02.2 with the c-lightning-rest plugin version v0.10.7 which is depreciated.  I am seeing these errors constantly
reconnecting... 2024-05-02 03:09:50.42 | ERROR | lnbits.wallets.corelightningrest:paid_invoices_stream:266 | Error in paid_invoices_stream: 2024-05-02 03:09:50.42 | DEBUG | lnbits.wallets.corelightningrest:paid_invoices_stream:296 | lost connection to corelightning-rest invoices stream: 'Timed out while waiting for invoice to be paid', reconnecting...
I'm noticing that my Bluewallet using LNDHUB is not updating the transactions so maybe this is related.  The transactions aren't consistently showing up in the web wallet either.
There is a new native clnrest interface in Core Lightning.  I believe the LNbits team is planning on supporting it.  Perhaps this issue will not occur with the new interface.


The order is not preserved, when fetching rows from SNMP.table

Hi. Thank you for great library.
When using SNMP.table method, order of fetched rows is not preserved.
(Because, type of Table._rows is dictionary.)
How about using collections.OrderedDict type for Table._rows ?

oh.. Already exist.#7 sorry.


'getImageData' on 'CanvasRenderingContext2D': The canvas has been tainted by cross-origin data

https://stackoverflow.com/questions/22097747/how-to-fix-getimagedata-error-the-canvas-has-been-tainted-by-cross-origin-data

Hasn't happened again. Closing for now.


Is eslint@5 officially supported?

Hey there, I noticed that eslint@5 was finally released. Does eslint-loader support this version or do we need to wait for an update?

it seems to work

It works but it displays warnings upon installing using npm / yarn.
<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><5.0.0"
Since in the package.json of eslint-loader (2.0.0) stated:
"peerDependencies": {
    "eslint": ">=1.6.0 <5.0.0",
    "webpack": ">=2.0.0 <5.0.0"
}

same here. seems to work but getting the warnings. please clarify the status. thx

#231

PR #231 is about this, but it seems to have failed on Travis-CI checks

eslint 5.1.0 is out now, seeing the same as others:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><5.0.0".

It looks like this has been fixed with 2.1.0. Thanks everyone.


add .gitignore for pycache

Can you please add a .gitignore with an entry to ignore the pycache subdirectory?
I cloned this repo into my homeassistant custom_components as recommended in the README. When I run homeassistant python is creating pycache, which causes the smartthingq checkout to appear as having unstaged files.

Hello! It is generally a really good idea to add things like this to your global .gitignore.
No objections to adding it to this repo too, of course—please open a PR if you like!


Consider to replace TileMatrixSetLink with TileSet metadata and change the name of the standard

See this issue to know more about the actual change.
https://github.com/opengeospatial/OGC-API-Tiles/issues/43
consider this too:
https://github.com/opengeospatial/2D-Tile-Matrix-Set/issues/10

An example of the Json encoding will be prepared.

Close https://github.com/opengeospatial/OGC-API-Tiles/issues/47 when this is closed

We checked this and is done in the Members meeting 2020-12-09


added fxserver log persistence

reference #295

Closed by 50730f97c68d9d5eb4e4d3b6a7762f9e529a97bb
Also, I think that PR meant the server log and not the fxserver log.


Fixes for Deployer 5

Simple changes in db.php and uploads.php to enable recipes to work on Deployer 5.x

👍

Closing due to lack of response.


Tolerant null in LG context

close: #3326
Original issue:
# hello
- @{user.name}

Today if user.name is null, it will result an exception, we should change this to "null" (we can optimize the result later) so that user won't be interrupted by exceptions.
Expected result:
>if a == null or a.b == null, result would be string "null"
# template1
- @{a.b}

> if a== null or a.b == null, result would be "result is 'null'"
# template2
- switch: @{a.b}
- CASE: @{'null'}
- result is 'null'

> if a template ref is return null, the result would be
>{ "lgType":"MyStruct", "key1":"null"}
# template3
[MyStruct
    key1 = @{template4()}
]

> return null
# template4
- IF:@{false}
- hello

Pull Request Test Coverage Report for Build 103307

0 of 0   changed or added relevant lines in 0 files are covered.
17 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-1.8%) to 79.575%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs
1
86.46%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/OAuthPrompt.cs
1
56.4%

/libraries/Microsoft.Bot.Builder/Inspection/InspectionMiddleware.cs
1
78.89%

/libraries/Microsoft.Bot.Builder.LanguageGeneration/LGErrors.cs
1
55.56%

/libraries/Microsoft.Bot.Expressions/BuiltInFunctions.cs
1
93.21%

/libraries/Microsoft.Bot.Expressions/LRUCache.cs
1
82.93%

/libraries/Microsoft.Bot.Expressions/TriggerTrees/Trigger.cs
1
85.09%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
2
75.0%

/libraries/Microsoft.Bot.Builder/MemoryTranscriptStore.cs
2
86.09%

/libraries/Microsoft.Bot.Builder.LanguageGeneration/Evaluator.cs
6
92.78%

Totals

Change from base Build 103299:
-1.8%

Covered Lines:
10870

Relevant Lines:
13660

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

will this be a public option instead of a private one?

will this be a public option instead of a private one?
For example, when developing, report null with error and when in production, replace null with custom warning like: [Not Set] and also trace it in telemetry for further investigation.

This PR's intention is to make not throw exception by default. We will explore whether make it configurable with something like "strict=true", which is out of scope of this one, and will be taken into considerations with other possible configurable behavior together.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


Testing the Armins solution for V3 package in remote

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

/package

/package

/package

/package

/package

/package


Could you authors please open the codes related to physical consistency in the paper?

The physical consistency part in neuralGCM paper is really great, especially better than other models.
For example, the power spectra and geostrophic wind balance figures are great for weather forecasters.
These codes are not so essential or important compared to neuralGCM itself.
So, if it's ok, could you please open these codes within neuralGCM too?
Thank you!

Most of the calculating these quantities is open sourced as part of the WeatherBench2 project: https://github.com/google-research/weatherbench2

Yes,however,it’s not easy to use.
I’m using local neuralGCM output netcdf data to compute derived variables,such as vertical velocity. After converting nc data to zarr file format, but running command line still gets error: inconsistent dimensions of time.

I'll learn weatherbench2 more to better understand neuralGCM and other models.
Thank you!


Added easy release script for windows

If the DistributionTool.exe is in the root directory, this script automatically builds the plugin, installing in Stream Deck and restarts the Stream Deck.

Hey @sohneg, thanks for your interest in the Stream Deck SDK. With the release of the new Maker CLI on the horizon, specifically the streamdeck create command, we aren’t accepting new pull requests to the template at this time as it will soon be archived. We do however encourage people to try the CLI, and Node.js SDK, and provide feedback and suggestions based on their experiences.
Thanks again, Richard

I just tried to start with the cli. but i got an error
[image: image.png]
Am So., 26. Nov. 2023 um 19:05 Uhr schrieb Richard Herman <
@.***>:

Closed #12
https://github.com/elgatosf/streamdeck-plugin-template/pull/12.
—
Reply to this email directly, view it on GitHub
https://github.com/elgatosf/streamdeck-plugin-template/pull/12#event-11063602087,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATVSXZV3SYBCPWAPTXQJMILYGOAEZAVCNFSM6AAAAAA7243GVGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGA3DGNRQGIYDQNY
.
You are receiving this because you were mentioned.Message ID:
<elgatosf/streamdeck-plugin-template/pull/12/issue_event/11063602087@
github.com>


Fix link.

Fix markdown syntax for #BKMK_CmdRef.

@KexyBiscuit,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks for your contribution! You'll see the changes live this morning.


Please provide README.md/LICENSE and spec/ in gem

Please provide README.md/LICENSE and spec/ in gem, it will simplify life for distribution maintainers aiming to package your gem.

looks like this got done at some point


Rename component.loaded & .mounted

I would probably have expected a bool from a field named loaded, but since we have the same with mounted we should follow that.

Originally posted by @spydon in https://github.com/flame-engine/flame/pull/1466#pullrequestreview-914639988
Given that the names .loaded and .mounted sound like they would return boolean flags, I suggest renaming those methods into .whenLoaded and .whenMounted. So, they could be called as
await component.whenLoaded;
await component.whenMounted;

I disagree with this, component.whenLoaded.when(...) would sound very weird. mounted and loaded makes a perfect reading when put before an await keyword.

component.whenLoaded.then(() {
  ...
});

sounds quite ok though, at least better than component.loaded.then.

This seems to be just based on personal opinion, component.loaded.then sounds good to me, not as good as component.loaded.whenComplete but it is fine for me.
I vote for not renaming those getters.

The original premise of this issue was the concern, raised by @spydon, that the name .loaded sounds ambiguous: as if it means a boolean flag, not a future.
Do you believe that that concern is invalid, or do you think it's valid but the names that I suggested are not adequate?

It is the same with Images.ready, I would also have expected a boolean from the adjective there.
Are there any futures like this in Flutter which we can take the naming convention from?

It is the same with Images.ready in #1441, I would also have expected a boolean from the adjective there.

Good point, there is a possibility of ready being confusing as well.
I guess one reason that it didn't look ambiguous to me, is that .ready() is a method, and I normally wouldn't expect a boolean indicator flag to be a method. So to me, images.ready() looks more like a future than images.ready.
Perhaps the same reasoning can be applied here as well? component.loaded() looks much less like a boolean than component.loaded.

I'll just repeat what I said on the other thread here too. Since effective dart expects you to have is, has, are etc on fields that are boolean, then we could assume that these fields are not booleans.

Perhaps the same reasoning can be applied here as well? component.loaded() looks much less like a boolean than component.loaded.

I think that might be clearer, I think the most important is that we follow the same structure on all of these kind of methods/fields.

Since they aren't actually doing much we decided it makes more sense to have them as getters, if you can make ready() a getter too we'll merge that too so that we get consistency over those methods. :)

@spydon I've double-checked with the Dart style guide, and here's what it has to say on the topic of choosing between a getter or a method:

Even so, choosing a getter over a method sends an important signal to the caller. The signal, roughly, is that the operation is “field-like”. The operation, at least in principle, could be implemented using a field, as far as the caller knows. That implies:

The operation does not take any arguments and returns a result.
The caller cares mostly about the result.
The operation does not have user-visible side effects.
The operation is idempotent.
The resulting object doesn’t expose all of the original object’s state.

If all of the above describe your operation, it should be a getter.

So, in this case .ready() is used primarily in order to create a side-effect, whereas its result is essentially void, and the user doesn't care about it all.

So, in this case .ready() is used primarily in order to create a side-effect, whereas its result is essentially void, and the user doesn't care about it all.

The side effect is kind of already running in the background though? So I think that you could argue that this is only a getter for the state of the already running side effects caused by load.

I realized now that we also have the FlameGame.ready() method, that one feels more natural as a method though.

But we are keeping mounted and loaded as they are right? So maybe we should close this?

But we are keeping mounted and loaded as they are right? So maybe we should close this?

This issue is about images.ready() too, since it falls into the same category, and @st-pasha haven't changed that one to a getter yet.

We're being stuck in a Fredkin's paradox here :)
I think one aspect here is what part of speech the name of the method/getter is. Say, if it's an imperative verb, then there should probably be parentheses, otherwise it just feels weird. If it's an adjective, then it could be either a getter or a method.
So, the question then is of the semantics of the name: do we intend ready to be a verb (as in "make this ready!"), or to be an adjective ("is this ready?"). For a verb, a method is more natural: game.ready(), meaning "make this game ready"; similarly images.ready() would mean "make all images ready". On the other hand, if we want to lean towards the adjective side of the word, then it could be a getter, but in that there should probably be some helper word to help disambiguate, like maybe await images.whenReady.

We're being stuck in a Fredkin's paradox here :)
I think one aspect here is what part of speech the name of the method/getter is. Say, if it's an imperative verb, then there should probably be parentheses, otherwise it just feels weird. If it's an adjective, then it could be either a getter or a method.
So, the question then is of the semantics of the name: do we intend ready to be a verb (as in "make this ready!"), or to be an adjective ("is this ready?"). For a verb, a method is more natural: game.ready(), meaning "make this game ready"; similarly images.ready() would mean "make all images ready". On the other hand, if we want to lean towards the adjective side of the word, then it could be a getter, but in that there should probably be some helper word to help disambiguate, like maybe await images.whenReady.

Let's keep the readys as verbs and the others as adjectives then and we can merge your PR, I think that can make sense from what they do too.


chore: increment dependencies. rm lint-failing aria-haspopup

please review

The pr lint doesn't tell me how to make a passing pr title

@lwhiteley please review :)

I'll review a bit later today. Still quite early for me 🤠

it seems the aria role should be changed to button and haspopup should be used  https://www.w3.org/TR/2016/WD-wai-aria-practices-1.1-20161214/examples/menu-button/menu-button-1/menu-button-1.html#rps1_label
however, changing the control in that way, the linter then requires the control be updated so that it can take focus. A separate MR should probably be made for the haspopup aria label and so the attribute is removed altogether to pass the lint here.


Access Private videos in You tube

Hi,
I would like to access private videos along with the public videos.
Could anyone please help me to achieve it.
Thanks in advance.

Provide username and password with -u and -p or use .netrc -n.


Copyright Notice

Include this copyright notice in the game files https://www.blizzard.com/en-gb/legal/5515ca11-1c96-42a0-b853-e7876a0d19bf/copyright-notices#977300007
Both the URL and the notice itself should be added e.g. in the TOC file:
# ©2004 Blizzard Entertainment, Inc. All rights reserved.
# World of Warcraft, Warcraft and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.
# source: https://www.blizzard.com/en-gb/legal/5515ca11-1c96-42a0-b853-e7876a0d19bf/copyright-notices#977300007

Fixed in https://github.com/ennvina/spellactivationoverlay/commit/715a8e4e27fe8f229ae476f37c9f07052f2e8e44
Please read the commit's extended message for more information about what has been selected and why.


How to save the tracking results on a custom video ?

Hi!
I'm extremely thankful to your work first of all!
However, I had a query with regards to saving the bounding box estimates on a test video.
I have used the following python call
Python call:
python .\tools\demo.py --config .\experiments\siamban_r50_l234\config.yaml --snapshot .\experiments\siamban_r50_l234\model.pth --video .\demo\Copex_002_Block-02_Trial-02_0000047.avi --save
And I get the corresponding error:
Traceback (most recent call last):
File ".\tools\demo.py", line 137, in
main()
File ".\tools\demo.py", line 101, in main
save_video_path = args.video_name.split(video_name)[0] + video_name + '_tracking.mp4'
ValueError: empty separator
But in any case this seems to be saving the whole visualization itself as a video itself and I'm not interested in that. Is there a way to be able to save just the bounding box estimates ?
Thanks in advance!

Hello, I don't know your needs well, you can modify the demo.py or test.py as needed.


Lint dartpad snippets against lints/core instead of recommended or flutter lints

lint dartpad snippets against lints/core instead of recommended or flutter lints
close https://github.com/dart-lang/dart-pad/issues/2815

package:lints/core.yaml was chosen mostly based on the comment in the above issue (...someone doing exploratory coding or writing a quick test...); it's aligned w/ dartpads use case - as a lightweight way to try out dart and flutter. Many of the lints in recommended and flutter_lints are more appropriate for large-scale development.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

Do consider pulling out the generation of the analysis option file's contents to a separate method so we only have to update one place if we make further changes.

👍 - done


Investigate why files became invalid after file metadata update

Affected dataset: Lung_Fibroblasts
https://contribute.data.humancellatlas.org/submissions/detail?uuid=d8bcfa5a-d8a7-4dd0-8953-3c3bafdbf87e&project=b4a7d12f-6c2f-40a3-9e35-9756997857e3
Check if it also happens with other older submissions.

The file metadata entities should have the following information. However, the files in this submission don't have this info and the validator is trying to request file validation again. The file validation request is failing and even if it succeeds the file validation will fail because we have deleted the file in Ingest already.
{
	"validationJob": {
		"validationId": "cdf63726-ef15-4e1c-a66d-a407608f4fb0",
		"checksums": {
			"sha1": "a8567c145833a8d67d4c497d9d93af14c852801a",
			"sha256": "8653dcd5c3a32fade0b1a741fa9e5cae9d3936ccac2093cea75e0315d6121317",
			"crc32c": "d91fd99c",
			"s3_etag": "c849c6642fb9e361b57ad33d4b04d50d-27"
		},
		"jobCompleted": true,
		"validationReport": {
			"validationState": "Valid",
			"validationErrors": []
		}
	}
}

We need to check if this also happens with older submissions. If not, I think we can just fix the files in this submission to have the validationJob which is valid so that their validationState can be set to valid.


which version of k8s should be used?

hi  guys
i  try to deploy tinkerbell in k8s  v1.22.3
but it raise :
no matches for kind "MutatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"
[root@k8s-master kubernetes]# kk api-resources  |grep admissionregistration
mutatingwebhookconfigurations                  admissionregistration.k8s.io/v1        false        MutatingWebhookConfiguration
validatingwebhookconfigurations                admissionregistration.k8s.io/v1        false        ValidatingWebhookConfiguration
what version should i used?   thanks .

Relating to #13 - though I believe that Kubernetes v1.21 should work.

The general answer is: we support the latest stable release of Kubernetes. It so happens that due to #13 that we recommend v1.21.x today.


Add a sub-page under the Resources page to outline the RS retry mechanism.

DevEx/OpEx
Add a sub-page under the Resources page to outline the RS retry mechanism.
Tasks

[ ] Look into RS retry mechanism for the ETOR use-case.
[ ] Add document this page in notion.

Additional Context
Add any other context or screenshots about the work here.

Got a thumbs up review from @jherrflexion


CAMEL-17075 Moved initialisation from evaluate() to init()

I run all core tests and SimpleBuilderTest fails, but I would say that's because they don't call init() before calling evaluate().
If I look at the interfaces Predicate and Expression they both says that all initialization should be done in init() and should be thread safe:
"A predicate should be thread-safe and be able to evaluate concurrently by different threads with different exchanges. Any initialization logic should be done by the init(CamelContext) method which allows to prepare the predicate such as wiring in resources, pre-parsing and what else."


Mirror status

When updating the status of the selected mirrors is a worthwhile data point to have for troubleshooting.
pacman-mirrors --status reports the mirrors and status in this format:
Local mirror status for unstable branch
Mirror #1   --  06:57   Netherlands  http://ftp.snt.utwente.nl/pub/linux/manjaro/
Mirror #2   --  05:21   Netherlands  https://mirror.koddos.net/manjaro/
Mirror #3   OK  00:21   Netherlands  https://manjaro.mirrors.lavatech.top/
Mirror #4   OK  01:06   Global       https://mirrors.fossho.st/manjaro/

In this example only mirrors 3 & 4  are up to date but this should not be an issue with the update since pamac should use only up-to-date mirrors.  The goal should be to report a failure if there are no up-to-date mirrors, informing the user about the status of the selected mirrors.

Implemented debug info in generated forum post.


resolve failed for "pagenodes-nodes": Error: Cannot find module 'pagenodes-nodes' node_modules\nan

Hi,
I am trying to setup in my windows 10 and getting below errors when i execute "npm run build" command.
resolve failed for "pagenodes-nodes": Error: Cannot find module 'pagenodes-nodes'
node_modules\nan
resolve failed for "grunt-simple-mocha": Error: Cannot find module 'grunt-simple-mocha'
resolve failed for "grunt-sass": Error: Cannot find module 'grunt-sass'
resolve failed for "grunt-nodemon": Error: Cannot find module 'grunt-nodemon'
resolve failed for "grunt-contrib-watch": Error: Cannot find module 'grunt-contrib-watch'
resolve failed for "grunt-contrib-uglify": Error: Cannot find module 'grunt-contrib-uglify'
resolve failed for "grunt-contrib-jshint": Error: Cannot find module 'grunt-contrib-jshint'
resolve failed for "grunt-contrib-copy": Error: Cannot find module 'grunt-contrib-copy'
resolve failed for "grunt-contrib-concat": Error: Cannot find module 'grunt-contrib-concat'
resolve failed for "grunt-contrib-compress": Error: Cannot find module 'grunt-contrib-compress'
resolve failed for "grunt-contrib-clean": Error: Cannot find module 'grunt-contrib-clean'
resolve failed for "grunt-concurrent": Error: Cannot find module 'grunt-concurrent'
resolve failed for "grunt-cli": Error: Cannot find module 'grunt-cli'
resolve failed for "babel-runtime": Error: Cannot find module 'babel-runtime'
resolve failed for "webpack-core": Error: Cannot find module 'webpack-core'
Hash:<PHONE_NUMBER>d02f34fa48
Version: webpack 1.14.0
Time: 116412ms
Asset     Size  Chunks             Chunk Names
function-worker.bundle.js   638 kB       0  [emitted]  function-worker
j5-worker.bundle.js  1.95 MB       1  [emitted]  j5-worker
service-worker.bundle.js   494 kB       2  [emitted]  service-worker
ui.bundle.js  5.58 MB       3  [emitted]  ui
+ 1011 hidden modules
WARNING in ./~/localforage/dist/localforage.js
Critical dependencies:
32:88-96 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
@ ./~/localforage/dist/localforage.js 32:88-96
ERROR in ./build/backend/plugin.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./log in D:\MyGitRepos\pagenodes\build\backend
@ ./build/backend/plugin.js 3:10-26

Works fine with latest update. Thanks.


Sort Unused Lints alphabetically

Sorts the "Unused Lints" section alphabetically to match the order in analysis_options.yaml

Thanks :)


𝐇𝐃𝐃 𝐝𝐢𝐝 𝐧𝐨𝐭 𝐢𝐧𝐢𝐭𝐢𝐚𝐥𝐢𝐳𝐞 & 𝐝𝐢𝐝𝐧'𝐭 𝐝𝐞𝐭𝐞𝐜𝐭 𝐢𝐧 𝐭𝐡𝐞 𝐧𝐞𝐰 𝐭𝐡𝐞  𝐏𝐂 .

What will be the process to fix it?
[Enter feedback here]

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

ID: f91258c0-7929-4d60-3f88-e67c957584c6
Version Independent ID: d952a74b-1f86-de68-df1e-1956ac045fc7
Content: Shrink a basic volume
Content Source: WindowsServerDocs/storage/disk-management/shrink-a-basic-volume.md
Service: windows-server
Sub-service: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

issue is not related to this repo, make a post on microsoft forums.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


use shared phobos library by default on linux

I'm not sure this is a good idea.

Please don't.
It'll make it impossible (in practice) to have 2 executables depending on a different version of the compiler. There's not a lot of packages currently that are built in D, and with this change, there won't be any.
With this change, if you install a binary that depends on a shared library, you'll need to have the same version of libphobos the program was compiled with. Which in turns forces package maintainers to patch our crazy versioning scheme. You're supposed to be able to start a library compiled with X.YY with a shared library which version is > X.YY. I'm not aware of any released version where that was the case.

Fine with me, @Dicebot can you undo this for ArchLinux as well.

Developers shipping binaries may not be sophisticated enough to get the .so installed correctly on their customers' machines.

Developers shipping binaries should always use static.
I don't see why you are telling package maintainers to not ship shared libraries.  @Dicebot might have something different in mind but I see shared libraries as their own package, which D programs depend upon.  Then static libraries are bundle with the development packages along with sources and a compiler.

And I'd pretty much call it standard procedure to trigger a rebuild if any source dependencies have changed in a OS distribution.  Eg: new compiler, new vibe.d library, etc...


Problems with the amount of columns in the table and the return of ajax

I want to add 2 columns with buttons so i can make some actions and here is my problem:
My ajax response give me 5 results and i want to have 7 columns but always when i try to search with this 2 extra columns i get the error "Integrity constraint violation: 1052 Column 'id' in where clause is ambiguous".
Can I set the data of a column as null? I tried it in different ways but nothing worked. It only works if my ajax response have also 7 results;

Hi - apologies if the "create new issue" template, or the contributing document were not clear enough, but please post support requests in the DataTables forum. This is so there is a single searchable source of DataTables support issues.
Please ensure that you also link to a test case showing the issue.


cmd/compile: generic function appears to use incorrect type descriptor

What version of Go are you using (go version)?

$ go version
go version go1.18 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="arm64"
GOBIN=""
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOOS="darwin"
GOPROXY="https://goproxy.io,https://mirrors.aliyun.com/goproxy/"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/yv/fd8s2yw54cldnj29jx3qxrh80000gn/T/go-build4280234465=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Go 2 Playground Link
What did you expect to see?
Type assertion to None returns true.
Type Switch prints s is a None.
What did you see instead?
Type assertion to None returned false.
Type Switch prints oops.

CC @randall77 @mdempsky

Since you are returning a generic type from your returnOption function, go would expect None to be generic as well. If you do change it to None[T], it seems to work for me :) At least that is a possible solution to the problem.

It is really a bug.
It looks the problem is gone if the line s = returnOption[int](0) is changed to s = returnOption[string](0).

https://gotipplay.golang.org/p/p-xVGVKSW10
switch (any)(s).(type) {

@gopherbot please open a backport issue for 1.18.


Error using adapter: "waterline-sqlite3", in SailsJS v0.11

Trying to add Sqlite3 adaptor to SailsJS project, on 'sails lift' I get:
error: There was an error attempting to require("waterline-sqlite3") error: Is this a valid Sails/Waterline adapter?  The following error was encountered :: error: Error: Cannot find module '/var/www/project/node_modules/waterline-sqlite3/node_modules/sqlite3/lib/binding/node-v47-linux-x64/node_sqlite3.node'
My connections.js is
`
sqlitedb: {
	adapter: "waterline-sqlite3",
	/**
	 * Database instance type. Specify whether to store the database on disk
	 * or in memory.
	 */
	type: 'disk', // or 'memory'

	/**
	 * Location of file if type='disk'
	 */
	filename: './tmp/db.sqlite',

	/**
	 * Set to true to output SQL queries
	 */
	debug: false
}

`
Looking in
/var/www/project/node_modules/waterline-sqlite3/node_modules/sqlite3/lib/binding/
I see a
node-v14-linux-x64/
dir ,whereas it seems its looking for
node-v47-linux-x64/
npm version is 3.3.6 , node version is 5.0.0

As an update to this, in:
/var/www/project/node_modules/sqlite3/lib/binding/
I have a
node-v47-linux-x64
directory. Manually copying that to:
/var/www/project/node_modules/waterline-sqlite3/node_modules/sqlite3/lib/binding/
Removes the error.

That's really strange. What version of node are you running?

your sails app folder and package.json for install waterline-sqlite3 file path is not a same file

I was getting a similar error. Looking at the npm install log, I solved my problem with this SO post.
Hope it helps.

@ducky427 Deleting my node_modules and then running :
 npm install --unsafe-perm
Removes the error. I guess this is some permissions issue, I'm running everything as root right now, including
sails lift


determine process for sharing project config after or as part of project invite flow

Closing since we are syncing project config now


The HTTP request was forbidden with client authentication scheme 'Anonymous'

Hello,
the CdsServiceClient throws an exception when trying to use the ClientSecret authentication and you have not registered the application in the dynamics instance yet. The stack trace is the following:
Microsoft.Powerplatform.Cds.Client.Utils.CdsConnectionException
  HResult=0x80131500
  Message=Failed to connect to Common Data Service
  Source=Microsoft.Powerplatform.Cds.Client
  StackTrace:
   at Microsoft.Powerplatform.Cds.Client.CdsServiceClient.CreateCdsServiceConnection(Object externalOrgServiceProxy, AuthenticationType requestedAuthType, String hostName, String port, String orgName, NetworkCredential credential, String userId, SecureString password, String domain, String Geo, String claimsHomeRealm, Boolean useSsl, Boolean useUniqueInstance, OrganizationDetail orgDetail, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, OrganizationWebProxyClient externalOrgWebProxyClient, String certificateThumbPrint, StoreName certificateStoreName, X509Certificate2 certificate, Uri instanceUrl, Boolean isCloned, Boolean useDefaultCreds)
   at Microsoft.Powerplatform.Cds.Client.CdsServiceClient..ctor(Uri instanceUrl, String clientId, String clientSecret, Boolean useUniqueInstance, String tokenCachePath)
   at CDS.Core_Test.Program.Main(String[] args) in C:\Demo\CDS.Core Test\CDS.Core Test\Program.cs:line 17

  This exception was originally thrown at this call stack:
    Microsoft.Powerplatform.Cds.Client.CdsConnectionService.InitCdsService()
    Microsoft.Powerplatform.Cds.Client.CdsConnectionService.GetCachedCDSService(out Microsoft.Powerplatform.Cds.Client.CdsConnectionService)
    Microsoft.Powerplatform.Cds.Client.CdsConnectionService.IntilizeService(out Microsoft.Powerplatform.Cds.Client.CdsConnectionService)
    Microsoft.Powerplatform.Cds.Client.CdsConnectionService.DoLogin(out Microsoft.Powerplatform.Cds.Client.CdsConnectionService)
    Microsoft.Powerplatform.Cds.Client.CdsServiceClient.CreateCdsServiceConnection(object, Microsoft.Powerplatform.Cds.Client.AuthenticationType, string, string, string, System.Net.NetworkCredential, string, System.Security.SecureString, string, string, string, bool, bool, Microsoft.Xrm.Sdk.Discovery.OrganizationDetail, Microsoft.IdentityModel.Clients.ActiveDirectory.UserIdentifier, string, System.Uri, Microsoft.IdentityModel.Clients.ActiveDirectory.PromptBehavior, string, Microsoft.Xrm.Sdk.WebServiceClient.OrganizationWebProxyClient, string, System.Security.Cryptography.X509Certificates.StoreName, System.Security.Cryptography.X509Certificates.X509Certificate2, System.Uri, bool, bool)

Inner Exception 1:
MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Anonymous'.

You can use the following code to replicate the problem:
using Microsoft.Extensions.Configuration;
using Microsoft.Powerplatform.Cds.Client;
using System;
using System.IO;

namespace CDS.Core_Test
{
    class Program
    {
        static void Main(string[] args)
        {
            IConfiguration config = new ConfigurationBuilder().SetBasePath(Directory.GetCurrentDirectory())
                                            .AddJsonFile("appsettings.json", true, true)
                                            .Build();
            var cdsClientConfig = config.GetSection("CdsClient");

            var cdsClient = new CdsServiceClient(new Uri(cdsClientConfig["Uri"]), cdsClientConfig["ClientId"], cdsClientConfig["ClientSecret"], true, cdsClientConfig["TokenCache"]);
            if (cdsClient.IsReady)
            {
                Console.WriteLine("Hello, connected to CDS using .NET Core");
            }
            else
            {
                // Never reaches this line of code because the constructor throws an exception
                Console.WriteLine("Failed to connect to CDS using .NET Core :(");
            }

            Console.ReadKey();
        }
    }
}

I replicated the same situation using CrmServiceConnection from Microsoft.Xrm.Tooling.Connector and it does not throw an exception, instead, it handles the exception and stores it in the CrmServiceClient.LastCrmException property. You can use the following code to replicate it using .Net Framewrork
using Microsoft.Xrm.Tooling.Connector;
using System;
using System.Configuration;

namespace CrmServiceClient_Test
{
    class Program
    {
        static void Main(string[] args)
        {
            var appSettings = ConfigurationManager.AppSettings;
            var crmClient = new CrmServiceClient(new Uri(appSettings["Uri"]), appSettings["ClientId"], appSettings["ClientSecret"], true, appSettings["TokenCache"]);
            if (crmClient.IsReady)
            {
                Console.WriteLine("Hello, connected to Dynamics using .NET Framework");
            }
            else
            {
                Console.WriteLine("Failed to connect to Dynamics using .NET Framework :(");
                //this works without an exception
            }

            Console.ReadKey();
        }
    }
}

Actually CrmServiceClient.LastCrmException does not have an InnerException and contains no Trace information and the most meaningfull information I got from this (by configuring Visual Studio to break on thrown exceptions) is the following:
Microsoft.IdentityModel.Clients.ActiveDirectory.Internal.HttpRequestWrapperException
  HResult=0x80131500
  Message=
  Source=Microsoft.IdentityModel.Clients.ActiveDirectory
  StackTrace:
   at Microsoft.IdentityModel.Clients.ActiveDirectory.Internal.Http.HttpClientWrapper.<GetResponseAsync>d__31.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

Inner Exception 1:
HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).

Inner Exception 2:
AdalException: : Unknown error

System.ServiceModel.Security.MessageSecurityException
  HResult=0x80131501
  Message=The HTTP request was forbidden with client authentication scheme 'Anonymous'.
  Source=System.ServiceModel
  StackTrace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory`1 factory)

  This exception was originally thrown at this call stack:
    System.Net.HttpWebRequest.GetResponse()
    System.ServiceModel.Channels.HttpChannelFactory<TChannel>.HttpRequestChannel.HttpChannelRequest.WaitForReply(System.TimeSpan)

Inner Exception 1:
WebException: The remote server returned an error: (403) Forbidden.

Thanks for the report,   This is actually the behavior of the API endpoint in CDS coming though.. as the identity your trying to access with does not exist, it does not know what the do with it and throws a 403,   We are looking at ways to make that message better from the API itself.  More similar to the "user does not exist in this instance" error we used to throw when trying to access an instance where your user identity was blocked by security or policy.

One thing I did not specify clearly is that the CdsServiceClient constructor throws exceptions and instead the CrmServiceClient constructor catches the exception and puts it in the CrmServiceClient.LastCrmError property.

Yes, this is intentional..   CrmServiceClient follows a C++ pattern for exception management from when it was originally designed many years ago.   We wanted to move over to the more common "throw breaking exception on connect fail" but could not without breaking a lot of existing clients.   Adding a Option to the constructor or a static setting didn't make sense either so we lived with it.
also: re the exception stack trimming things,  we did a fix for that recently that will now include the full stack though all levels,  if you patch to current nuget's you will get that behavior.
With CdsServiceClient we moved to using Exceptions on connect.  Its noted in the nuget release notes.   We have not yet decided if we are going to do away with the LastException pattern completely yet.. but for now it will always throw exceptions on connect, which is the more accepted pattern today.
Feedback is welcome on that.

I am so excited that finally there will be client library that we can use from .NET Core applications when interacting with Dynamics CRM. Thank You!!
Is there a resolution to this issue? I am getting the same error message when using Client ID and Client Secret connecting to Dynamic 365 CRM Online. Thanks again

Hello @twiga2013,
you have to register your application user in dynamics, the issue has been opened because the error message is misleading.
I have written a LinkedIn Article on how to build an MVP for this.
Best regards,
Betim.

Hi Betim,
I have created the App Registration under the same Azure Active Directory that CRM Dynamics is using but when I got to add Application user all the fields are locked and I am logged in Dynamics as System Administrator.

@twiga2013 , Change the user view from "user" to "Application User"

I did switch to Application User form everything is locked. I did try it out from a complete different tenant and Application User forms fields are not locked.
I will need to contact Microsoft support to find out why the application user form fields are all locked.

I am going to close this for now,  the API team has a repro of this working now and is working though providing a better error experience.
thanks all for your feedback here.


Document in Chinese

Enhancement proposal

Hi, I know about manim recently and I think that this is a pretty cool project especially you would like to share something with others.
I notice that there are different languages for documents. Hence, Could we add a Chinese version to the document?
I hope more people know about this project and use that!
I can work on this change and submit a pull request. If you think this is an enhancement.
Additional comments

Have a look at https://docs.manim.community/en/stable/contributing/internationalization.html


Text alignment options

Add (horizontal and vertical) alignment options for drawing text.
This is just a suggested API, comments welcome.

I don't know whether it's better to have generic Alignment values, or separate enums for horizontal and vertical alignment.
The names might be too clunky, leading to code that looks like: { textAlign = TextAlignment AlignCenter AlignCenter }. Or worse, with qualified imports: { textAlign = Text.TextAlignment Text.AlignCenter Text.AlignCenter }

I think the API looks good how it is :) Thanks!


Home page cards fonts

The cards in home page looks weird.
Why not fix it ?

I want titles like ( "What we do") to be a bit bolder.
I want sub titles like (" We conjugate ") to have a greater font size

I want to work on this issue under JWOC

I want to work on this issue under JWOC

Assigned to you  @whiteHatpro

@IAmTamal i have made the desired changes and attached the respective screenshot
should i create the pull request?

This looks awesome , can i get the heading text (what we do . ..) to be a bit bigger , so that it stands out.
And also change it's color to blue , preferebly  : #339a9c

sure!!

@IAmTamal i have done the changes as u asked
should i create pull request?

Go ahead.

Thanks @whiteHatpro for taking up on this issue.
See you soon !!


SHA1 functions in DownloadManager conflict with functions from OpenSSL on Linux

They have the same name, and as DownloadManager ends up being dynamically linked to libcrypto.so, the OpenSSL function will be called instead, resulting in a segfault due to differing function signatures.

Resolved in https://github.com/TypesettingTools/ffi-experiments/commit/76b1c55ea283e9e289741cef41e45d233fa65c5f


Reolink Video Doorbell - stream won't close after 2 way audio

Hi,
I am using the frigate hass card with 2 way audio which works great with the doorbell. The only issue is that after finishing 2 way talk the stream doesn't seem to close and the blue status ring on the doorbell stays blue indicating it still receiving audio.

Here is my config in case it has something to do with that:
api:
  ffmpeg:
    bin: /usr/local/bin/ffmpeg
  origin: '*'
ffmpeg:
  rtsp: -fflags nobuffer -flags low_delay -stimeout 5000000 -user_agent go2rtc/ffmpeg
    -rtsp_transport tcp -i {input}
hass:
  config: /config
log:
  format: text
rtsp:
  default_query: mp4
streams:
  reolink:
  - ffmpeg:http://<IP_ADDRESS>/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=smartcam#video=copy#audio=opus
  - rtsp://REDACTED@<IP_ADDRESS>:554/h264Preview_01_main
  reolink_rec:
  - rtsp://REDACTED@<IP_ADDRESS>:554/h264Preview_01_main#backchannel=0
  - ffmpeg:reolink_rec#audio=pcma
webrtc:
  candidates:
  - <IP_ADDRESS>:8555
  - stun:8555
  listen: :8555

Just to add more information, in my setup, with go2rtc version 1.7.1 it seems to be working fine, but with version 1.9 and up it does not.

Can you confirm that after 2-way audio is closed, that client isn't still an active consumer? If you list out the stream consumers, you should be able to see if there's anything still connected to your backchannel stream. If nothing is connected but the streams remain, that would indicate an issue. I am assuming though, that something is still connected as a consumer even though you believe it's closed.

@danluckner Since you're using Reolink with an audio stream, see #1254 for the fix I used for a similar problem.


besiclometer, enplanement

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,e]

/trunk merge


mplus-outline-fonts: add github release

Motivation for this change
The new, revamped (pre)release of the M+ font superfamily is highly deserving of inclusion, and is meant to replace the OSDN release for good. I've chosen to add a (sub)package instead of replacing the existing one so that we don't break existing user configurations (the fonts have been renamed and reshuffled across the two releases).
Things done

Built on platform(s)

[x] x86_64-linux, NixOS (with --option sandbox true)

Tested, as applicable (inapplicable)
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 (nothing depends on this package)
[x] Fits CONTRIBUTING.md.

cc @henrytill

Updated upstream and rebased on top of fresh nixpkgs; also added recurseIntoAttrs at the top-level.
@SuperSandro2000 Thank you for your lints. And to answer your question: the GitHub release of M+ actually contains a different set of font styles – under different names, too – which would make it a breaking change if we replaced the OSDN release with it. Many users depend on the old M+ font set to be available on their system and we wouldn’t want to force their hand in replacing the configuration files for their editors and whatnot. This way we at least get a “deprecation period” (though I don’t think I have the freedom to declare the OSDN release as deprecated here. A warning could be nice though).

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 151705 run on x86_64-linux 1

2 packages built:

mplus-outline-fonts.githubRelease
mplus-outline-fonts.osdnRelease


Unable to import Unchained Capital/Caravan wallet

When I import Caravan wallets into Sparrow, I am unable to click the "apply" button.  The wallets, xpubs, master fingerprint, and derivation path's are there. The script type is Legacy(P2SH) but I'm pretty sure caravan uses Nested Segwitt.
Is this a bug or am I doing something wrong?
I am using Ubuntu.

There is a problem on "GreenTape" keystore (can't see what it is). Are you using the Caravan file import?

No. I experimented with Unchained Capital. I downloaded the file from unchained capital, but I was able to recreate it in Caravan.

Ok. Can you identify the problem with the "GreenTape" keystore?

I'm not sure. Here are The other two keystores.

.

These are strange and non-standard derivation paths. If you are certain they are correct, try disabling the derivation path validation in the General Preferences. However, given your previous comments I think it's likely this setup does not represent the same Caravan wallet.

See response from https://twitter.com/MsHodl on this https://twitter.com/nakamotwani/status/1479977316793020416
Something seems amiss with Unchained derivation path.
Are derivation paths required to access all the funds associated with a given multi-sig?

They're not strictly necessary, although certain non-essential fields in the PSBT will be technically incomplete/incorrect. So long as you have the correct xpub for all the signers you can generate the spending scripts for the multisig wallet.


ocgrpc exports all traces

What happened:
ocgrpc, when registered as the StatsExporter for the gRPC client and server in the CRI, exports all traces into Stackdriver, whether or not specified.
What you expected to happen:
It was my understanding that I should have to be explicit and let ocgrpc know to export the traces. I'm not even sure where this trace exporer is registered.
How it could be fixed
Deep diving into the source code and documentation for ocgrpc and isolating where it is exporting these traces. Note: found the issue <=> trace exports all the time, wrapping the beginning and end of the RPC. Could add some turn-on-and-off hackage.
EDIT: found mitigation, but it messes up context propagation
How to reproduce it (as minimally and precisely as possible):
Run off latest branch with the ocgrpc changes.

This is still a firm issue in ocgrpc. Commenting out the span's end in the lib solved this while still transferring context downward, but there should be better configuration so that we can choose which gRPC methods to trace...


No longer possible to create a Job from a CronJob

Describe the bug
It is no longer possible to create a Job from a CronJob through the CronJob details panel.
To Reproduce
Steps to reproduce the behavior:

Open a CronJob details panel
The button for creating a Job from the CronJob is missing

Expected behavior
It was possible to create a Job from a CronJob by clicking a button of the CronJob details panel.
Screenshots

Environment (please complete the following information):

Lens Version: 2022.11.101953-latest
OS: Windows 11 Pro / 22H2 / 22623.891
Installation method: .exe

If you quit Lens (from the Tray menu) and then run it from powershell, do you see any logs relating to a failure to load "pod-menu-extension"?

Same thing for me on MacOS using brew, started several days ago with the latest Lens version. No mention of "pod-menu-extension" in the logs when running from terminal.

Same thing for me,
version 2022.11.101953-latest

same for me on MacOs
version: Lens: 2022.11.101953-latest

The trigger button has disappeared

Same on Windows 2022.11.101953-latest

Is there a workaround for this btw?

Seems to be followed up in https://github.com/lensapp/lens/issues/6572 with a fix in https://github.com/lensapp/lens/pull/6581

Thanks for pointing me to this issue too. Yes these two issues are duplicates and I will choose this over in favour of that one.


update of displaycal and argyllcms

Motivation for this change
Upgrade displaycal (color management and display profiling) and its underlying library argyllcms.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Argyllcm should be up to date: https://github.com/NixOS/nixpkgs/pull/36431 Not sure if it works

ah I hadn't noticed as there was no merge conflict, the displaycal upgrade is still worth having though. Thanks.

@GrahamcOfBorg build displaycal

Success on aarch64-linux (full log)
Attempted: displaycal
Partial log (click to expand)
warning: no previously-included files matching '*.bak' found anywhere in distribution
writing manifest file 'DisplayCAL.egg-info/SOURCES.txt'
running build_ext
copying build/lib.linux-aarch64-2.7/DisplayCAL/lib64/python27/RealDisplaySizeMM.so -> DisplayCAL/lib64/python27

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/xbhr7spjs44dds27hclwbiggcqs22qby-python2.7-displaycal-<IP_ADDRESS>

Success on x86_64-linux (full log)
Attempted: displaycal
Partial log (click to expand)
warning: no previously-included files matching '*.bak' found anywhere in distribution
writing manifest file 'DisplayCAL.egg-info/SOURCES.txt'
running build_ext
copying build/lib.linux-x86_64-2.7/DisplayCAL/lib64/python27/RealDisplaySizeMM.so -> DisplayCAL/lib64/python27

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/5v1b51cv5gjywiaia3ynpvg3gygm0scj-python2.7-displaycal-<IP_ADDRESS>


Preflight Response while making a POST request.

I am trying to use Yii2 Rest to develop an APP. after Trying a lot am into an unknown issue. If I send a CORS request for the first time. I get this response, and keep getting this unless i do a tweak like I return the post data just after the actionFunction. This is my initial code
class UserController extends Controller
 {
 	public function beforeAction($action) {
    	$this->enableCsrfValidation = false;
    	return parent::beforeAction($action);
	}

	public function actions()
    {
        $actions = parent::actions();
        unset($actions['create']);

        return [
        	'error' => [
        		'class' => 'yii\web\ErrorAction',
            ],
            'options' => [
            	'class' => 'app\components\OptionsAction',
            ],

        ];

        //return $actions;
    }

    public function behaviors() {
	 	$behaviors = parent::behaviors();

		$behaviors['authenticator'] = [
		    'class' => HttpBearerAuth::className(),
		    'only' => ['dashboard'],
		];

		$behaviors['contentNegotiator'] = [
		    'class' => ContentNegotiator::className(),
		    'formats' => [
		        'application/json' => Response::FORMAT_JSON,
		    ],
		];

		$behaviors['corsFilter'] = [
            'class' => \yii\filters\Cors::className(),
            'cors' => [
                // restrict access to
                'Origin' => ['http://<IP_ADDRESS>','http://localhost','*'],
                'Access-Control-Request-Method' => ['GET', 'POST', 'OPTIONS', '*'],
                // Allow only POST and PUT methods
                'Access-Control-Request-Headers' => ['*'],
                // Allow only headers 'X-Wsse'
                'Access-Control-Allow-Credentials' => null,
                // Allow OPTIONS caching
                'Access-Control-Max-Age' => 86400,
                // Allow the X-Pagination-Current-Page header to be exposed to the browser.
                'Access-Control-Expose-Headers' => ['X-Pagination-Current-Page'],
            ],
        ];

		return $behaviors ;
	}

	protected function verbs()
	{
	    return [
	    	'register' => ['POST','OPTIONS'],
	    	'seller-details' => ['POST','OPTIONS'],
	    	'address' => ['POST','OPTIONS'],
	    	'login' => ['POST','OPTIONS'],
	        'index' => ['GET', 'HEAD'],
	        'view' => ['GET', 'HEAD'],
	        'create' => ['POST'],
	        'update' => ['PUT', 'PATCH'],
	        'delete' => ['DELETE'],
	    ];
	}

and This is my actionFunction
public function actionAddress() {

		$data = Yii::$app->request->post();
		$seller = User::findIdentityByAccessToken($data['auth_key']);

		$seller_address = new Addresses() ;

		try {
			$seller_address->id = '0' ;
			$seller_address->user_id = $seller->id ;
			$seller_address->fullName = $data['fullName'];
			$seller_address->address1 = $data['address1'];
			$seller_address->address2 = $data['address2'];
			$seller_address->city = $data['city'];
			$seller_address->zip = $data['zip'];
			$seller_address->country = $data['country'];
			$seller_address->phoneNumber = $data['phoneNumber'];
			$seller_address->landmark = $data['landmark'];
			$seller_address->addressType = $data['addressType'];
			$seller_address->status = '0';

			if(!($seller_address->save())) {
					$response = $seller_address->getErrors('fullName');
					if(!empty($response)) {
						throw new ErrorException("Please fill the Name");
					}
					$response = $seller_address->getErrors('address1');
					if(!empty($response)) {
						throw new ErrorException("Please fill the address");
					}
					$response = $seller_address->getErrors('city');
					if(!empty($response)) {
						throw new ErrorException("Please fill the city");
					}
					$response = $seller_address->getErrors('zip');
					if(!empty($response)) {
						throw new ErrorException("Please fill the zip");
					}
					$response = $seller_address->getErrors('country');
					if(!empty($response)) {
						throw new ErrorException("Please fill the country");
					}
					$response = $seller_address->getErrors('phoneNumber');
					if(!empty($response)) {
						throw new ErrorException("Please fill the phone number");
					}
			}

				$response = [
					'data' => $data,
					'message' => 'Seller address updated successfully',
				];

				return $response;
		}

		catch(Exception $e) {
			throw new Exception($e);

		}

	}

Here is the screenshot of the error

I made this change into my actionFunction
public function actionAddress() {

		$data = Yii::$app->request->post();
                return $data ; // I returned the data here
		$seller = User::findIdentityByAccessToken($data['auth_key']);

		$seller_address = new Addresses() ;

		try {
			$seller_address->id = '0' ;
			$seller_address->user_id = $seller->id ;
			$seller_address->fullName = $data['fullName'];
			$seller_address->address1 = $data['address1'];
			$seller_address->address2 = $data['address2'];
			$seller_address->city = $data['city'];
			$seller_address->zip = $data['zip'];
			$seller_address->country = $data['country'];
			$seller_address->phoneNumber = $data['phoneNumber'];
			$seller_address->landmark = $data['landmark'];
			$seller_address->addressType = $data['addressType'];
			$seller_address->status = '0';

			if(!($seller_address->save())) {
					$response = $seller_address->getErrors('fullName');
					if(!empty($response)) {
						throw new ErrorException("Please fill the Name");
					}
					$response = $seller_address->getErrors('address1');
					if(!empty($response)) {
						throw new ErrorException("Please fill the address");
					}
					$response = $seller_address->getErrors('city');
					if(!empty($response)) {
						throw new ErrorException("Please fill the city");
					}
					$response = $seller_address->getErrors('zip');
					if(!empty($response)) {
						throw new ErrorException("Please fill the zip");
					}
					$response = $seller_address->getErrors('country');
					if(!empty($response)) {
						throw new ErrorException("Please fill the country");
					}
					$response = $seller_address->getErrors('phoneNumber');
					if(!empty($response)) {
						throw new ErrorException("Please fill the phone number");
					}
			}

				$response = [
					'data' => $data,
					'message' => 'Seller address updated successfully',
				];

				return $response;
		}

		catch(Exception $e) {
			throw new Exception($e);

		}

	}

After returning this data I reverted my actionFunction to the original state and It worked afterwards for every request
Here is the screenshot for the success

This happened to my every function, for some function it worked with the same configuration. I am not sure why this is happening I tried searching on google and issues up here on github but cant resolve this. Any suggestion is welcomed.

just replace $behaviors['authenticator'] by $behaviors[] or do it without defining array keys like it is done in here in docs.
it is a sort issue when merging with parent. the way you've done it replaces authenticator in parent behavior but pushes corsFilter at the bottom of the arrays as it is not defined (yet) by default in \yii\web\Controller which breaks the rule already mentioned in the doc I linked :

The Cors filter should be defined before Authentication / Authorization filters to make sure the CORS headers will always be sent.