"Failed to write complete file to USB device" when using custom hardware

Hi
in an effort to streamline the process of programming multiple CMs we designed a custom pcb following the official IO-Boards usb circuit.

When booting the CMs as a mass storage device it works as intended. Currently we are using 16x flash pcbs at once and some command line magic to make it all happen.
Now we tried to boot the CMs with the directory option
sudo ./rpiboot -d /outputdir
This fails with following output:

philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_Entwicklung/scriptexecutor/output
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50216 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 47885 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2855972 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6669 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 47885 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned -7
Failed to write complete file to USB device

If i switch the exact CM to the official IO-Board and execute the exact command it works as expected.
Tested on Ubuntu 17.10

Is that 67R choke differential or common mode impedence?  It should be 90R
differential on USB, although it also requires suitably good quality
cabling (we have found lots of cheap USB cables do not have anything like
this which can cause significant issues...)
If you've just picked up a random cable then try a nice quality one, at
least one with good twisted pairs and a continuous shield.
Gordon
On 28 March 2018 at 11:11, FiesoDuck<EMAIL_ADDRESS>wrote:

Hi
in an effort to streamline the process of programming multiple CMs we
designed a custom pcb following the official IO-Boards usb circuit.
[image: flash adapter]
https://user-images.githubusercontent.com/5773030/38021342-d4e9f71a-327c-11e8-9dc6-98aa97e972d1.PNG
[image: flasher3]
https://user-images.githubusercontent.com/5773030/38022826-e002f1e8-3280-11e8-9196-9acf13a50328.png
When booting the CMs as a mass storage device it works as intended.
Currently we are using 16x flash pcbs at once and some command line magic
to make it all happen.
Now we tried to boot the CMs with the directory option
sudo ./rpiboot -d /outputdir
This fails with following output:
philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_
Entwicklung/scriptexecutor/output
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50216 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 47885 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2855972 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6669 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 47885 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned -7
Failed to write complete file to USB device
If i switch the exact CM to the official IO-Board and execute the exact
command it works as expected.
Tested on Ubuntu 17.10
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/raspberrypi/usbboot/issues/30, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB9CHJM4p5R6Tw7aIl2GFRWJtzatT-T4ks5ti2HRgaJpZM4S-Xql
.

Is that 67R choke differential or common mode impedence?

Yes it is. Replacing with an 90R did not yield better results.

If you've just picked up a random cable then try a nice quality one, at least one with good twisted pairs and a continuous shield.

This helped but now i get this error:

Received message GetFileSize: dt-blob.bin
Cannot open file dt-blob.bin

While using the official IO-Board the dt-blob.bin is not needed to be present in the output folder. And even after compiling (sudo dtc -I dts -O dtb -o /boot/dt-blob.bin dt-blob.dts) the dt-blob.bin and copying it to the output folder the board still won't boot:

philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_Entwicklung/scriptexecutor/output
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50216 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2855972 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6669 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: dt-blob.bin
File size = 48418 bytes
Received message ReadFile: dt-blob.bin
File read: dt-blob.bin
libusb_bulk_transfer returned 0

The command never finishes after that.
The dt-blob.bin is compiled into the .elf files iirc, why is it necessary to supply the dt-blob.bin when using our custom design and not when using the official IO-Board? And why is the freshly compiled dt-blob.bin not accepted when copied to the output folder?

I think the absence of dt-blob.bin is a red herring. There is no way to check for the presence of a file other than trying open it. As you've seen, providing a dt-blob.bin doesn't solve the problem, so attempting to load the dt-blob is just the last thing that the loader manages to do.

Here is the output for the official IO-Board:

philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_Entwicklung/scriptexecutor/output
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50216 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2855972 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6669 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: dt-blob.bin
Cannot open file dt-blob.bin
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: bootcfg.txt
Cannot open file bootcfg.txt
Received message GetFileSize: cmdline.txt
File size = 111 bytes
Received message ReadFile: cmdline.txt
File read: cmdline.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery8.img
Cannot open file recovery8.img
Received message GetFileSize: recovery8-32.img
Cannot open file recovery8-32.img
Received message GetFileSize: recovery7.img
Cannot open file recovery7.img
Received message GetFileSize: recovery.img
Cannot open file recovery.img
Received message GetFileSize: kernel8.img
Cannot open file kernel8.img
Received message GetFileSize: kernel8-32.img
Cannot open file kernel8-32.img
Received message GetFileSize: kernel7.img
Cannot open file kernel7.img
Received message GetFileSize: kernel.img
File size = 2900824 bytes
Received message GetFileSize: armstub8.bin
Cannot open file armstub8.bin
Received message GetFileSize: armstub8-32.bin
Cannot open file armstub8-32.bin
Received message GetFileSize: armstub7.bin
Cannot open file armstub7.bin
Received message GetFileSize: armstub.bin
Cannot open file armstub.bin
Received message GetFileSize: kernel.img
File size = 2900824 bytes
Received message ReadFile: kernel.img
File read: kernel.img
libusb_bulk_transfer returned 0
Received message GetFileSize: scriptexecute.img
File size = 669729 bytes
Received message ReadFile: scriptexecute.img
File read: scriptexecute.img
libusb_bulk_transfer returned 0
Received message GetFileSize: bcm2710-rpi-cm3.dtb
File size = 15346 bytes
Received message ReadFile: bcm2710-rpi-cm3.dtb
File read: bcm2710-rpi-cm3.dtb
libusb_bulk_transfer returned 0
Received message GetFileSize: config.txt
File size = 28 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message Done: config.txt
Second stage boot server done

Especially this part:

Received message GetFileSize: dt-blob.bin
Cannot open file dt-blob.bin

As you can see the error is the same but the official board just continues to boot while our custom board hangs.

If you are you able to get a shell prompt to  the CM3 while it's in the CMIO board (either via serial port or ssh over ethernet), use sudo vcdbg log msg to view the activity log. You should be able to correlate the file accesses from rpi-boot with positions in the log:
$ sudo vcdbg log msg |& grep File

You may find it easier to send the output to a file and use an editor to read it:
$ sudo vcdbg log msg >& vcdbg.txt

On a 3B+ I see two reads of config.txt, followed by a read of cmdline.txt, etc. Linking that to your rpiboot log suggests that your booting is failing between those two config.txt reads. All I see in that gap are HDMI messages, but you might see something different.

If you are you able to get a shell prompt to the CM3 while it's in the CMIO board (either via serial port or ssh over ethernet), use sudo vcdbg log msg to view the activity log.

I tried that and got
-sh: vcdbg: not found
I am following this btw.: https://github.com/raspberrypi/scriptexecutor/wiki/Building-and-customizing

You can copy the binary (the source isn't published for licensing reasons) from here: https://github.com/raspberrypi/firmware/blob/master/opt/vc/bin/vcdbg

I downloaded the file, put it on a usb stick and mounted the drive. When i try to ./vcdbg i still get  -sh: vcdbg: not found. I also tried chmod +x vcdbg with no success. I also tried to copy the file to the root home dir first and then execute it but to no avail.

You must also be missing some of the dependencies:
pi@raspberrypi:~ $ ldd /opt/vc/bin/vcdbg
	linux-vdso.so.1 (0x7ee95000)
	/usr/lib/arm-linux-gnueabihf/libarmmem.so (0x76f3f000)
	libdebug_sym.so => /opt/vc/lib/libdebug_sym.so (0x76f17000)
	libelftoolchain.so => /opt/vc/lib/libelftoolchain.so (0x76ec2000)
	libvcos.so => /opt/vc/lib/libvcos.so (0x76ea8000)
	libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x76e7f000)
	libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x76e6c000)
	librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x76e55000)
	libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x76d0d000)
	libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76c8e000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76c61000)
	libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76b22000)
	/lib/ld-linux-armhf.so.3 (0x76f55000)

I would start with the three from /opt/vc/lib.

https://github.com/raspberrypi/firmware/tree/master/opt/vc/lib

I replicated the directory structure and moved the corresponding files. (libdebug_sym.so, libelftoolchain.so, libvcos.so)
Same result as before: -sh: vcdbg: not found
Is it worth to mention, that /opt was empty before copying the files?

Your installation isn't putting /opt/vc/lib in the LD path. Put the libraries in /lib/arm-gnueabihf or /usr/local/lib instead.

Same result as before.
If libraries were missing,  shouldn't the error be more like
vcdbg: error while loading shared libraries: libelftoolchain.so: cannot open shared object file: No such file or directory

sudo ./vcdbg log msg?

-sh: sudo: not found

I am logged in as root

./vcdbg log msg then.

As i stated above, same result as before.
-sh: vcdbg: not found

ls -l vcdbg
file vcdbg

ls -l vcdbg
-rwxr-xr-x 1 root root 253273 Jan 1 01:05 vcdbg

file vcdbg
-sh: file: not found

How about debugging your hardware issue with a known Raspbian Lite image?

I am trying this as we speak.

I copied the contents of the FAT partition from 2017-07-05-raspbian-jessie-lite.img to my output directory.
When using the official IO-Board i get:

philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_Entwicklung/t
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50248 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2868132 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6688 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: dt-blob.bin
Cannot open file dt-blob.bin
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: bootcfg.txt
Cannot open file bootcfg.txt
Received message GetFileSize: cmdline.txt
File size = 190 bytes
Received message ReadFile: cmdline.txt
File read: cmdline.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery8.img
Cannot open file recovery8.img
Received message GetFileSize: recovery8-32.img
Cannot open file recovery8-32.img
Received message GetFileSize: recovery7.img
Cannot open file recovery7.img
Received message GetFileSize: recovery.img
Cannot open file recovery.img
Received message GetFileSize: kernel8.img
Cannot open file kernel8.img
Received message GetFileSize: kernel8-32.img
Cannot open file kernel8-32.img
Received message GetFileSize: kernel7.img
File size = 4581064 bytes
Received message GetFileSize: armstub8.bin
Cannot open file armstub8.bin
Received message GetFileSize: armstub8-32.bin
Cannot open file armstub8-32.bin
Received message GetFileSize: armstub7.bin
Cannot open file armstub7.bin
Received message GetFileSize: armstub.bin
Cannot open file armstub.bin
Received message GetFileSize: kernel7.img
File size = 4581064 bytes
Received message ReadFile: kernel7.img
File read: kernel7.img
libusb_bulk_transfer returned 0
Received message GetFileSize: bcm2710-rpi-cm3.dtb
File size = 16380 bytes
Received message ReadFile: bcm2710-rpi-cm3.dtb
File read: bcm2710-rpi-cm3.dtb
libusb_bulk_transfer returned 0
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message Done: config.txt
Second stage boot server done

and then tries to boot. It gets stuck but that besides the point.
When using my custom board i get:

philip@Dell:~/usbboot$ sudo ./rpiboot -v -d /media/philip/ext4_Entwicklung/t
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer returned 0
Writing 50248 bytes
libusb_bulk_transfer returned 0
Successful read 4 bytes
Waiting for BCM2835/6/7
Device located successfully
Initialised device correctly
Found serial number 1
Second stage boot server
Received message GetFileSize: autoboot.txt
Cannot open file autoboot.txt
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: start.elf
File size = 2868132 bytes
Received message ReadFile: start.elf
File read: start.elf
libusb_bulk_transfer returned 0
Received message GetFileSize: fixup.dat
File size = 6688 bytes
Received message ReadFile: fixup.dat
File read: fixup.dat
libusb_bulk_transfer returned 0
Received message GetFileSize: recovery.elf
Cannot open file recovery.elf
Received message GetFileSize: config.txt
File size = 1590 bytes
Received message ReadFile: config.txt
File read: config.txt
libusb_bulk_transfer returned 0
Received message GetFileSize: dt-blob.bin
Cannot open file dt-blob.bin

And i just halts from here. Same thing as before with the custom image build with https://github.com/raspberrypi/scriptexecutor

I am also curious as to why using sudo ./rpiboot works as intended but  sudo ./rpiboot -d [directory] fails the way it does.
I can "flash" the CMs and use them just fine in our application. We followed the original schematics closely when designing our board. If the hardware is faulty, how does the device boot in mass storage at all? How can this issue be hardware related?

Very little is done between those two reads of config.txt (at least in terms of functionality - there's a fair amount of code involved). The initial startup is complicated due to some chicken vs egg sequencing problems when processing the config settings.  As a result, an initial pass is performed to establish some facts about the platform. After this, just enough is done to determine which of the config,txt conditional sections to interpret and which to skip before it is parsed again, this time for real.
The additional steps are:

reading the EDID from any attached HDMI device,
reading the serial number from OTP, and
reading and acting upon dt-blob.bin (external or embedded).

Apart from reinitialising some internal state before the second pass, the next thing it does is attempt to find recovery.elf. To me this says that the problem is all in the setting of the GPIO states and their effects on the board.
Specifying a directory affects the way that rpiboot locates files to send. The only way that should make a difference to the target device is if the files being downloaded are different. Compare the contents of your user directory with /usr/share/rpiboot/msd/.
You can also get extra diagnostic output from rpiboot with -vv.

It's possible it's the way you've handled the HDMI hotplug connection...
If this is wrong it may be stuck trying to read the EDID from HDMI.
Gordon
On 3 April 2018 at 13:46, Phil Elwell<EMAIL_ADDRESS>wrote:

Very little is done between those two reads of config.txt (at least in
terms of functionality - there's a fair amount of code involved). The
initial startup is complicated due to some chicken vs egg sequencing
problems when processing the config settings. As a result, an initial pass
is performed to establish some facts about the platform. After this, just
enough is done to determine which of the config,txt conditional sections to
interpret and which to skip before it is parsed again, this time for real.
The additional steps are:

reading the EDID from any attached HDMI device,
reading the serial number from OTP, and
reading and acting upon dt-blob.bin (external or embedded).

Apart from reinitialising some internal state before the second pass, the
next thing it does is attempt to find recovery.elf. To me this says that
the problem is all in the setting of the GPIO states and their effects on
the board.
Specifying a directory affects the way that rpiboot locates files to send.
The only way that should make a difference to the target device is if the
files being downloaded are different. Compare the contents of your user
directory with /usr/share/rpiboot/msd/.
You can also get extra diagnostic output from rpiboot with -vv.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/raspberrypi/usbboot/issues/30#issuecomment-378237222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB9CHGu9jPXUZFJp5pV7o1XF1SpzTCRrks5tk28jgaJpZM4S-Xql
.

The fact that it goes on to look for dt-blob.bin suggests that can't be the case.

Specifying a directory affects the way that rpiboot locates files to send. The only way that should make a difference to the target device is if the files being downloaded are different. Compare the contents of your user directory with /usr/share/rpiboot/msd/.

ls /usr/share/rpiboot/msd/
bootcode.bin
start.elf

When i diff these files against the user files they are obviously different.
I proceeded with copying /usr/share/rpiboot/msd/bootcode.bin and start.elf to the user directory and
did  sudo ./rpiboot -d [directory] again.
Both boards (custom and official) then boot into MSD. Sorry but i am kinda lost here, what does that
imply?

To me this says that the problem is all in the setting of the GPIO states and their effects on the board.

As shown in the schematics above we haven't customized the GPIOs or the usage of them in our board. What problems with the GPIO states are you referring to?

Closed due to inactivity.


Github Action Deprecated

Describe the bug or the issue that you are facing

Steps/Code to Reproduce
run the tf-gha-deploy-infra.yml github action
Expected Output
use of deprecated github feature
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Versions
latest MLOps-V2 Accelerator
Which platform are you using for deploying your infrastrucutre?
GitHub Actions (GitHub)
If you mentioned Others, please mention which platformm are you using?
No response
What are you using for deploying your infrastrucutre?
Terraform
Are you using Azure ML CLI v2 or Azure ML Python SDK v2
Azure ML CLI v2
Describe the example that you are trying to run?
following latest deployment guide

@setuc  is reviewing

I investigated this. The deprecated set-output calls are not explicitly in the MLOps SA code. They are in the javascript toolkit library used by the read_yaml action. This deprecation warning was recently reported for the toolkit itself (https://github.com/actions/toolkit/issues/1336) though no update is available yet. Will monitor updates to the toolkit to mitigate the deprecation as well as investigate workarounds or new approach to read_yaml implementation in MLOps.

This is apparently fixed in @actions/core v1.10.0, updated the NPM packages to the latest versions and created a PR. Unfortunately it looks like the warning will still be there but there is a fix in the actual code.


Error handling: every func returning (err error)?

Related: https://github.com/Fantom-foundation/go-lachesis/pull/140
As for whether to return one or mutliple, that's a worthy debate. https://github.com/hashicorp/go-multierror is another option.
Would be good to remove all panics and Fatal calls, outside of the topmost entrypoint (i.e.: main and tests).

outdated


Sign-in Error "The SSL connection could not be established, see inner exception"

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.33.1 (98)
Regression From
1.32.1
Architecture
i86
Storage Explorer Build Number
20240410.2
Platform
Windows
OS Version
Windows 11
Bug Description
Suddenly, SE fails to log me in in to Azure account throwing the error:
{
  "message": "\"The SSL connection could not be established, see inner exception.\""
}

Steps to Reproduce

Launch SE
Click "Sign in with Azure"
In "Select Azure Environment" to "Azure"
Click "Next" to start the browser authentication flow.
Error "Unable to sign in: The SSL connection could not be established, see inner exception." appears.

Actual Experience

Expected Experience
After the browser authentication flow has completed, the SE lists the available Azure subscribtions.
Additional Context
Nothing unusual. It just stopped working.
I still can access the same Blob Storage from CLI (az storage blob ..) using the same user and the same machine.
It is related to https://github.com/microsoft/AzureStorageExplorer/issues/7593, but the latter does not provide the solution or provides an obscure recommendation by the author.

It is related to https://github.com/microsoft/AzureStorageExplorer/issues/7593, but the latter does not provide the solution or provides an obscure recommendation by the author.

Did you try the solution suggested in the final comment?

@0anton given that what the user user did worked, I would recommend that you try it as well.

I have exact same issue and as a MS internal I am not able to use many tools that requires to have SSL Secure tunnel connection to remote host. CaseBuddy, OofSponder, SA, Kusto, and some more have exact same issue.
Not even able to RDP to Azure machine, not sure if this is related to that.

@prafulbusa method (extending the list of allowed protocols didn't work for me.
Still getting:
{
  "message": "\"The SSL connection could not be established, see inner exception.\""
}

I've just restarted the app. Did you reboot the PC to apply new SSL configs?

@MRayermannMSFT is it possible you extend the error message to include the inner exception, so I have hints why the SSL connection originating from Azure Storage Explorer got dropped?

@0anton can you try following these steps to get a hold of your authentication logs?
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting?tabs=Windows#authentication-logs
Those logs may have the inner exception, if they don't then please share the logs here so I can share with the team responsible for surfacing the inner exception. Also, please follow the recommended step of clearing out the existing logs before gathering the fresh set. Thanks.

I faced the same issue today.
BTW, I'm behind the company VPN. It worked after disconnecting the VPN.
My logfiles are attached anyway.
ServiceHub.zip

@MRayermannMSFT Take a look at the logs and see what can be done.

Trying to open Azure Support request as direct on the home page. Still not working, tried disabling FW, enabling additional ssl ciphers... No avail

@0anton It has been suggested that you try Wireshark instead of Fiddler, as it is better at diagnosing SSL issues.
Here are some links that may also be helpful:

https://dev.azure.com/VS-Languages-Training-Path/Training/_wiki/wikis/Test.wiki/104/SSL-issues
https://dev.azure.com/VS-Languages-Training-Path/Training/_wiki/wikis/Test.wiki/14/TLS-1.2-TLS-1.3-detection-script-for-VS-Sign-in(by-Chris-Mann)

Thanks @craxal, @MRayermannMSFT for hints!
Somehow it started working.
I believe allowing again ciphers
RSAE-PSS/SHA256
RSAE-PSS/SHA384
RSAE-PSS/SHA512

by adding them at the top of the Functions in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Cryptography\Configuration\Local\SSL\00010003\  and rebooting the host did the trick.
That's the same what @prafulbusa suggested and also https://github.com/microsoft/AzureStorageExplorer/issues/7593
Will observer and closing for now.


Nothing happens when I connect devices

Prerequisites
If the following boxes are not ALL checked, your issue is likely to be closed.

[x ] Using yarn
[ x] Using node 10.x
[ x] Using an up-to-date master branch
[x ] Using latest version of devtools. See wiki for howto update
[x ] For issue in production release, devtools output of DEBUG_PROD=true yarn build && yarn start
[ x] Tried solutions mentioned in #400

Describe the bug
I couldn't see an option in the prerequisites for "Downloaded the latest binary via brew?"  That is my case, although I do also have yarn and node 10 installed...  Also I attempted to install from the .dmg before trying brew - issue is the same as outlined below.
I have been searching for an app like this forever!  :-) However it doesn't seem to recorgnise either devices that I connect.  Both of which I can mount find using the trial of MacDroid - which I mention only to indicate that MTP file transfer and USB debugging are enabled device-side.
Expected behaviour

OpenMTP displays my device filesystem in its UI?

Current Behavior
OpenMTP doesn't show the device filesystem.
Possible Solution
Unknown
Steps to Reproduce (for bugs)

Launch OpenMTP
Connect device via USB (both are Android 10.  One is a Pixel XL, one is a Redmi K20 Pro
OpenMTP doesn't show the device filesystem.
Quit OpenMTP & re-launch.  Same

Your Environment

macOS 10.15.6
Android 10

Attachments
OpenMTP-log.zip

I'm currently working on a new mtp kernel. hopefully soon we will have support for all these devices.

This should have been fixed by https://github.com/ganeshrvel/openmtp/pull/181
Keeping this open until stable release it out.

@steveharman
Could you download the latest community beta version of OpenMTP from https://drive.google.com/file/d/1wpSlkGWZKe4-nRYcdJaPVA3Y6kOBMTsO/view?usp=sharing and let me know whether your device is recognized?
Cheers


Investigate removing no-agenda.txt and no-agenda.csv

no-agenda.csv appears to be completely unused.
no-agenda.txt appears to be explicitly checked for use in a test, but no view appears to use it.
Perhaps I'm missing where they are invoked, so some investigation should be done before simply removing the templates.

They are being used from here: https://github.com/ietf-tools/datatracker/blob/cb2f4afc8b81212896016568bd99b98d3c62adf4/ietf/meeting/views.py#L1546-L1548
I wonder if simply returning 404 would be simpler.

Having the ics 404 will cause some calendaring programs to refuse to accept the url as a subscription - returning the empty calendar is better.
In any case, I think we should change the code above to not make the template use so hard to find. I'll make a PR.


Some Git and NodeJS stuff

Some fussiness

Yay! First pull request. Now i feel myself like a part of opensource community.

@pulviscriptor Sure you can!
But I have something bigger for you, just wait for it.


Warp sync with Aura: Incomplete block import pipeline.

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
I had some issues using warp sync with the chainflip public testnet. (See here)
Following @bkchr's advice in the above stackexchange question, I cherry-picked the commits from #13058 and #13074. This allowed the warp sync to progress further but I ran into a new issue:
2023-01-23 13:31:24.175  WARN tokio-runtime-worker sync: 💔 Error importing block 0xd826b720a99165998df41aaf67f9590b53a874611b150aad890a3d52397dc062: consensus error: Import failed: Import failed: Incomplete block import pipeline.

The error originates here.
As far as I can tell this is because, during a warp sync, the Aura verifier returns early, before the fork_choice is set:
https://github.com/paritytech/substrate/blob/419b840fa1f170a1c2027b63310549d1bf6d2ed0/client/consensus/aura/src/import_queue.rs#L185-L200
I tried moving this line to the start of the verify method and this allowed the warp sync to complete:
block.fork_choice = Some(ForkChoiceStrategy::LongestChain);

Not sure whether this is correct approach, but it at least demonstrates the source of the problem...
Steps to reproduce
No response

Ty for the report: https://github.com/paritytech/substrate/pull/13221


Block Bot

Can someone send me a pull request with this feature?

#739

where is it? :/

they deleted their repo, rip. there exists no blockbot currently, (you could make one).

But the blockbot is still in there accessuble


CNV-37813: upgrading to react router v6

📝 Description
Replacing react-router v5 in v6 version.
🎥 Demo
Internal changes only, no difference in view.

/lgtm

/retest

/retest

/retest

/retest

until this https://github.com/openshift/release/pull/48740 is merged it wont pass test, our ci is using 4.14 and we need 4.15

/retest

/retest

/retest

/lgtm


Double evaluation in ++ operator

The operand of all the pre- and post- increment/decrement operators gets evaluated twice.
If this operand has side effects, these cause faulty behavior. Contrary to C, in C# this situation is well specified.
https://deck.net/1163f28e0ee3fb9f69c6f9fd4103039f
https://dotnetfiddle.net/Z2H5rW
public class Test
{
    public static void Main()
    {
        int[] a = new int[] { 3, 8 };
        int i = 0;
        a[i++]++;
        System.Console.WriteLine(i);
        System.Console.WriteLine(a[0]);
        System.Console.WriteLine(a[1]);
    }
}

Output
2
9
8

Expected output
1
4
8

Interesting defect. Thanks again for pointing out these defects and for providing the excellent samples. We will investigate and fix before the next Bridge release.

I have come up with this whole bunch of reports because I have a battery of tests that I use for my java-to-C# converter. Throwing the generated C# now at the bridge.net converter gives some interesting results. But most of it is compiling extremely well, even on the super-weird way my converter has to facilitate goto to implement the java construct of labeled break and continue.

Thanks for taking the time to post these reports. We really appreciate the interest and pushing the compiler into these edge cases.
@c0pperdragon Is your Java-to-C# project on GitHub or any other details available? Sounds interesting.

We have created it for our own purpose, but I got the OK from my company to open-source it as well:
https://github.com/Greentube/Java-converter
It was intended as a light-weight alternative to GWT, but as it turns out, Google had just the same idea and they developed J2CL at the same time. So now my converter is quite overshadowed by the work of the big guys.  :-(

Fixed! The fix is going to make it to the following Bridge release (according to assigned milestone).


id: person's address, comes after second petitioner information and references same address

unable to say yes same address becuase we have not yet provided the "same" address and it won't let me move forward

Also add in google validation for addresses if the answer is no


Bug: The sign out button when clicked does not require confirmation of the action

Fixed by 9bcaf68 commit

Fixed by 9bcaf68 commit


Debian post-inst script fails to correctly create system service when multiple users are present

Latest debian build fails to correctly create the system service when multiple users are present in the result of who, this causes the service to reference an incorrect user alias and therefore the service is unable to start.
Issue seen on the latest build, using a fresh install of Raspbian Buster.

I have a fix for this, i'll submit a PR for review 👍


DEBUG Log only shows something when you restart HB

Prerequisite

[X] Yes, I've read the readme completely.

Cache

[X] Yes, I've cleaned accessory cache and the issue still exists.

Version
v1.7.0-beta.48
Device Infomation JSON File
No response
Device Control Mode
None
Logs
No response
Other Infomations
when enabling DEBUG Log in Plugin Settings, DEBUG messages will only loaded after you restart HB.

it takes up to 5 mins to get those messages.

sry, have to reopen. there was a message without restarting HB but only because access token was expired because i have added the same token to my home assistant instance. removed them now. it seems like he is not getting the messaged from the server pushed or is only getting the messages when the plugin is asking the tuya cloud IOT portal.

Yes, "token expired" actually not time expired, it's revoked by serverside, so only when requesting the api, then we can know if the token is working. there's no server pushing.

HB Log before restarting and initiated a self test 6 mins ago.
[7/12/2023, 11:42:49 AM] [Shelly] Excluding device SHPLG-S 3CE90ED7F63B at <IP_ADDRESS> [7/12/2023, 11:42:52 AM] [Shelly] Excluding device SHPLG-S DE9339 at <IP_ADDRESS> [7/12/2023, 11:42:55 AM] [Shelly] Excluding device SHSW-1 8CAAB56200C7 at <IP_ADDRESS> [7/12/2023, 11:42:56 AM] [Shelly] Excluding device SHPLG-S C8C9A3B8D4CA at <IP_ADDRESS> [7/12/2023, 11:43:37 AM] [Homebridge UI] [HapClient] Discovery :: Ended [7/12/2023, 11:43:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications [7/12/2023, 11:43:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered [7/12/2023, 11:43:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:43:46" (from "Wed Jul 12 2023 11:42:46") [7/12/2023, 11:43:46 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press [7/12/2023, 11:44:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications [7/12/2023, 11:44:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered [7/12/2023, 11:44:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:44:46" (from "Wed Jul 12 2023 11:43:46") [7/12/2023, 11:44:46 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press [7/12/2023, 11:45:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications [7/12/2023, 11:45:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered [7/12/2023, 11:45:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:45:46" (from "Wed Jul 12 2023 11:44:46") [7/12/2023, 11:45:46 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press [7/12/2023, 11:46:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications [7/12/2023, 11:46:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered [7/12/2023, 11:46:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:46:46" (from "Wed Jul 12 2023 11:45:46") [7/12/2023, 11:46:46 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press [7/12/2023, 11:47:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications [7/12/2023, 11:47:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered [7/12/2023, 11:47:46 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:47:46" (from "Wed Jul 12 2023 11:46:46") [7/12/2023, 11:47:46 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press [7/12/2023, 11:48:45 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications
LOG After Restart HB:
`[7/12/2023, 11:50:11 AM] [Tuya] Log in to Tuya Cloud.
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Login to: https://openapi.tuyaeu.com
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Request:
method = post
endpoint = https://openapi.tuyaeu.com
path = /v1.0/iot-01/associated-users/actions/authorized-login
query = null
headers = {
"t": "1689155411035",
"client_id": "XXXX",
"nonce": "700d9d6a-f9d1-4020-a18e-92296c45478e",
"Signature-Headers": "client_id",
"sign": "DDCB2C3F52E6D558FE79ECEC5DEC28B97F7F7F8DF06635B6FA36AD0198175628",
"sign_method": "HMAC-SHA256",
"access_token": "",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = {
"country_code": 49,
"username": "XXXX",
"password": "XXXX",
"schema": "smartlife"
}
Setup Payload:
X-HM://0023KK4P9N722
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 060-91-981 │
└────────────┘

[7/12/2023, 11:50:11 AM] Homebridge v1.6.1 (HAP v0.11.1) (padHomebridge) is running on port 51174.
[7/12/2023, 11:50:11 AM] [Shelly] Admin server is running on port 9999
[7/12/2023, 11:50:11 AM] [HomeConnect] Attempting authorisation
[7/12/2023, 11:50:11 AM] [Nuki] Launched child bridge with PID 340020
[7/12/2023, 11:50:11 AM] [HomeConnect] Using saved access token
[7/12/2023, 11:50:11 AM] [HomeConnect] Successfully authorised
[7/12/2023, 11:50:11 AM] The plugin "homebridge-nb" requires Node.js version of ^18.16.1 which does not satisfy the current Node.js version of v18.13.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[7/12/2023, 11:50:11 AM] [padHomePilot] Warning. Password has been configured but does not appear to be enabled on HomePilot.
[7/12/2023, 11:50:11 AM] Registering platform 'homebridge-nb.NB'
[7/12/2023, 11:50:11 AM] [Nuki] Loaded homebridge-nb v1.4.4 child bridge successfully
[7/12/2023, 11:50:11 AM] [Nuki] warning: recommended version: node v18.16.1 LTS
[7/12/2023, 11:50:11 AM] Loaded 3 cached accessories from cachedAccessories.0E7D08EB57B6.
[7/12/2023, 11:50:11 AM] [Nuki] homebridge-nb v1.4.4, node v18.13.0, homebridge v1.6.1, homebridge-lib v6.3.18
[7/12/2023, 11:50:11 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Nuki Bridge v2.15.0 7E7F1CE1 at <IP_ADDRESS>:8080
[7/12/2023, 11:50:11 AM] [Nuki] Haustür Summer: Nuki Opener v1.9.3 2A770322
[7/12/2023, 11:50:11 AM] [Nuki] Wohnungstür: Nuki Smart Lock 3.0 v3.4.10 2C5B4D6C
[7/12/2023, 11:50:11 AM] [BigShelly] Received MQTT: shelly/0/bigshelly/Relay0/Switch = true
[7/12/2023, 11:50:11 AM] [BigShelly] Received MQTT: shelly/0/bigshelly/Relay0/Power = 0
[7/12/2023, 11:50:11 AM] [BigShelly] Received MQTT: shelly/0/bigshelly/Relay0/Energy = 14.75921
[7/12/2023, 11:50:11 AM] [deCONZ] hardware: x64
[7/12/2023, 11:50:11 AM] [deCONZ] os: Ubuntu 20.04.5 LTS [64 bit]
[7/12/2023, 11:50:11 AM] [deCONZ] restored 15 accessories from cache
[7/12/2023, 11:50:11 AM] [deCONZ] ui server: listening on http://<IP_ADDRESS>:40747/
[7/12/2023, 11:50:11 AM] Homebridge v1.6.1 (HAP v0.11.1) (Nuki) is running on port 52257.
[7/12/2023, 11:50:11 AM] [Nuki] hardware: x64
[7/12/2023, 11:50:11 AM] [Nuki] os: Ubuntu 20.04.5 LTS [64 bit]
[7/12/2023, 11:50:11 AM] [Nuki] restored 3 accessories from cache
[7/12/2023, 11:50:11 AM] [padHomePilot] Unknown product: 16234511_S
[7/12/2023, 11:50:11 AM] [padHomePilot] {
description: 'großes Fenster ',
deviceGroup: 3,
did: 7,
automations: [ 30 ],
readings: { sun_detected: false },
timestamp: -1,
iconSetInverted: 0,
iconSet: { k: 'iconset25' },
name: 'Sonnensensor',
statusValid: true,
deviceNumber: '16234511_S',
uid: '619224_S_1',
visible: false
}
[7/12/2023, 11:50:11 AM] [HomeConnect] Starting events stream for all appliances
[7/12/2023, 11:50:11 AM] [HomeConnect] [Kaffeevollautomat] Siemens CoffeeMaker (E-Nr: TI9575X1DE/10)
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/iot-01/associated-users/actions/authorized-login
data = {
"result": {
"access_token": "XXXX",
"expire_time": 7200,
"platform_url": "https://openapi.tuyaeu.com",
"refresh_token": "XXXX",
"uid": "XXXX"
},
"success": true,
"t":<PHONE_NUMBER>350,
"tid": "7e19d68d209911ee8ac9ce4d0cb672c1"
}
[7/12/2023, 11:50:11 AM] [Tuya] Start MQTT connection.
[7/12/2023, 11:50:11 AM] [Tuya] Fetching home list.
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Request:
method = post
endpoint = https://openapi.tuyaeu.com
path = /v1.0/iot-03/open-hub/access-config
query = null
headers = {
"t": "1689155411591",
"client_id": "XXXX",
"nonce": "914fa681-72db-4976-b3f1-d19a918a66b5",
"Signature-Headers": "client_id",
"sign": "349E12E691F96CACD2A7E6B654E3A86025414C415A12D49B5A629AE9B5A4A7D3",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = {
"uid": "XXXX",
"link_id": "41488ecd-46aa-4d1f-8bfc-142ceb93a2fa",
"link_type": "mqtt",
"topics": "device",
"msg_encrypted_version": "1.0"
}
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Request:
method = get
endpoint = https://openapi.tuyaeu.com
path = /v1.0/users/XXXX/homes
query = undefined
headers = {
"t": "1689155411592",
"client_id": "XXXX",
"nonce": "d8df17a8-6eb1-467e-ace3-02ffe1cb2443",
"Signature-Headers": "client_id",
"sign": "EA5B50724124DB48A3BB5748B847D8CBC7F6EE24181334151C14BE1938CC1F0A",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = null
[7/12/2023, 11:50:11 AM] [padHomePilot] blinds are online: Rollladen [1]
[7/12/2023, 11:50:11 AM] [padHomePilot] blinds are online: Rollladen [3]
[7/12/2023, 11:50:11 AM] [padHomePilot] blinds are online: Ihre Gerätebeschreibung [4]
[7/12/2023, 11:50:11 AM] [padHomePilot] blinds are online: Fenster [5]
[7/12/2023, 11:50:11 AM] [padHomePilot] blinds are online: Rollladen [6]
[7/12/2023, 11:50:11 AM] [HomeConnect] [Kaffeevollautomat] Can be placed in standby
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/iot-03/open-hub/access-config
data = {
"result": {
"client_id": "cloud_b54d8c210da99b528c10ef02214bacd4",
"expire_time": 7200,
"password": "c0a44dfad38869b23de44d9c142afec0",
"sink_topic": {
"device": "cloud/token/out/{device_id}"
},
"source_topic": {
"device": "cloud/token/in/41faf2b2b9a8739d6aeea8e3c3d17d34"
},
"url": "ssl://m1.tuyaeu.com:8883",
"username": "cloud_41faf2b2b9a8739d6aeea8e3c3d17d34"
},
"success": true,
"t":<PHONE_NUMBER>693,
"tid": "7e56389d209911ee8ac9ce4d0cb672c1"
}
[7/12/2023, 11:50:11 AM] [pad Anwesent] 1 monitored device(s) found. Accessory is in mode "any" so triggering occupancy.
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/users/XXXX/homes
data = {
"result": [
{
"geo_name": "",
"home_id": 9691003,
"lat": 0,
"lon": 0,
"name": "Mein Zuhause ..",
"role": "OWNER"
}
],
"success": true,
"t":<PHONE_NUMBER>876,
"tid": "7e660c22209911ee871736843e81b476"
}
[7/12/2023, 11:50:11 AM] [Tuya] Got home_id=9691003, name=Mein Zuhause ..
[7/12/2023, 11:50:11 AM] [Tuya] Fetching device list.
[7/12/2023, 11:50:11 AM] [Tuya] [TuyaOpenAPI] Request:
method = get
endpoint = https://openapi.tuyaeu.com
path = /v1.0/homes/9691003/devices
query = undefined
headers = {
"t": "1689155411882",
"client_id": "XXXX",
"nonce": "b2bc243a-c7e2-4ce2-aef6-e293c566b6b3",
"Signature-Headers": "client_id",
"sign": "C74C0CEECAB695DEF3EFE4994F08DC2DB9C05A526F7D40996C790D181FBE768A",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = null
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/homes/9691003/devices
data = {
"result": [
{
"active_time":<PHONE_NUMBER>,
"biz_type": 18,
"category": "ywbj",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay1523863664200blDVo/b232063be7ca251466ed453ba702bd36.png",
"id": "bf04b531361dc2662bzkw7",
"ip": "<IP_ADDRESS>",
"lat": "51.3055",
"local_key": "c<x[[8oapaF%q2uI",
"lon": "9.4672",
"model": "WS2SA-TY(CBU)",
"name": "EG Flur",
"online": true,
"owner_id": "9691003",
"product_id": "swpzietsal8wdlzb",
"product_name": "WiFi Smart Smoke Alarm(CBU)",
"status": [
{
"code": "smoke_sensor_status",
"value": "normal"
},
{
"code": "checking_result",
"value": "check_success"
},
{
"code": "battery_state",
"value": "high"
},
{
"code": "battery_percentage",
"value": 100
},
{
"code": "muffling",
"value": false
}
],
"sub": false,
"time_zone": "+02:00",
"uid": "XXXX",
"update_time":<PHONE_NUMBER>,
"uuid": "110365059ac696f8"
},
{
"active_time":<PHONE_NUMBER>,
"biz_type": 18,
"category": "ywbj",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay1523863664200blDVo/b232063be7ca251466ed453ba702bd36.png",
"id": "bf9de1eb5ef0a335acn2di",
"ip": "<IP_ADDRESS>",
"lat": "",
"local_key": "I=sg665Ld*vQ;Mzi",
"lon": "",
"model": "WS2SA-TY(CBU)",
"name": "WiFi Smart Smoke Alarm(CBU) 2",
"online": true,
"owner_id": "9691003",
"product_id": "swpzietsal8wdlzb",
"product_name": "WiFi Smart Smoke Alarm(CBU)",
"status": [
{
"code": "smoke_sensor_status",
"value": "normal"
},
{
"code": "checking_result",
"value": "check_success"
},
{
"code": "battery_state",
"value": "high"
},
{
"code": "battery_percentage",
"value": 100
},
{
"code": "muffling",
"value": false
}
],
"sub": false,
"time_zone": "+02:00",
"uid": "XXXX",
"update_time":<PHONE_NUMBER>,
"uuid": "2470dfa2a094e4eb"
}
],
"success": true,
"t":<PHONE_NUMBER>006,
"tid": "7e7ec18b209911ee97740a4306e7517e"
}
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Request:
method = get
endpoint = https://openapi.tuyaeu.com
path = /v1.0/devices/bf04b531361dc2662bzkw7/specifications
query = undefined
headers = {
"t": "1689155412012",
"client_id": "XXXX",
"nonce": "a3324547-30cd-4f96-8838-3b2a67cbf946",
"Signature-Headers": "client_id",
"sign": "AC0FE7C79CBBC5F866F18BA77A6E0BB7DC5874838C5656FB761E634EB48C4F60",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = null
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Found HAP device with username 0E:7D:08:EB:57:B6
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Testing 0E:7D:08:EB:57:B6 via http://<IP_ADDRESS>:52257/accessories
[7/12/2023, 11:50:12 AM] [harmonyHUB] (Schlafzimmer harmony )INFO - Discovered Activity : Apple TV sehen
[7/12/2023, 11:50:12 AM] [harmonyHUB] (Schlafzimmer harmony )INFO - Discovered Activity : Fire TV Cube
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Success 0E:7D:08:EB:57:B6 via http://<IP_ADDRESS>:52257/accessories
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: [<IP_ADDRESS>:52257 (0E:7D:08:EB:57:B6)] Instance Registered
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Found HAP device with username CC:22:3D:E3:CE:31
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Testing CC:22:3D:E3:CE:31 via http://<IP_ADDRESS>:51174/accessories
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/devices/bf04b531361dc2662bzkw7/specifications
data = {
"result": {
"category": "ywbj",
"functions": [
{
"code": "muffling",
"type": "Boolean",
"values": "{}"
}
],
"status": [
{
"code": "smoke_sensor_status",
"type": "Enum",
"values": "{"range":["alarm","normal"]}"
},
{
"code": "checking_result",
"type": "Enum",
"values": "{"range":["checking","check_success","check_failure"]}"
},
{
"code": "battery_state",
"type": "Enum",
"values": "{"range":["low","middle","high"]}"
},
{
"code": "battery_percentage",
"type": "Integer",
"values": "{"unit":"%","min":0,"max":100,"scale":0,"step":1}"
},
{
"code": "muffling",
"type": "Boolean",
"values": "{}"
}
]
},
"success": true,
"t":<PHONE_NUMBER>107,
"tid": "7e96394d209911ee8ac9ce4d0cb672c1"
}
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Request:
method = get
endpoint = https://openapi.tuyaeu.com
path = /v1.0/devices/bf9de1eb5ef0a335acn2di/specifications
query = undefined
headers = {
"t": "1689155412144",
"client_id": "XXXX",
"nonce": "f72a1bee-db99-4bb4-abdc-22e449d16174",
"Signature-Headers": "client_id",
"sign": "1FA35F1830F48AFF13A6A137599C6C00C67F7EE53C321F8EA6E5C818395D5AC5",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = null
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: Success CC:22:3D:E3:CE:31 via http://<IP_ADDRESS>:51174/accessories
[7/12/2023, 11:50:12 AM] [Homebridge UI] [HapClient] Discovery :: [<IP_ADDRESS>:51174 (CC:22:3D:E3:CE:31)] Instance Registered
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.0/devices/bf9de1eb5ef0a335acn2di/specifications
data = {
"result": {
"category": "ywbj",
"functions": [
{
"code": "muffling",
"type": "Boolean",
"values": "{}"
}
],
"status": [
{
"code": "smoke_sensor_status",
"type": "Enum",
"values": "{"range":["alarm","normal"]}"
},
{
"code": "checking_result",
"type": "Enum",
"values": "{"range":["checking","check_success","check_failure"]}"
},
{
"code": "battery_state",
"type": "Enum",
"values": "{"range":["low","middle","high"]}"
},
{
"code": "battery_percentage",
"type": "Integer",
"values": "{"unit":"%","min":0,"max":100,"scale":0,"step":1}"
},
{
"code": "muffling",
"type": "Boolean",
"values": "{}"
}
]
},
"success": true,
"t":<PHONE_NUMBER>217,
"tid": "7ea7b4b0209911ee8ac9ce4d0cb672c1"
}
[7/12/2023, 11:50:12 AM] [Tuya] Fetching scene list.
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Request:
method = get
endpoint = https://openapi.tuyaeu.com
path = /v1.1/homes/9691003/scenes
query = undefined
headers = {
"t": "1689155412228",
"client_id": "XXXX",
"nonce": "b9f93a9c-dbcd-46ec-8dc5-2c02aa486a3b",
"Signature-Headers": "client_id",
"sign": "35B89346CBC8A21371F9895874DA63D4941FEB8978AAD424B27765E55307825A",
"sign_method": "HMAC-SHA256",
"access_token": "XXXX",
"lang": "en",
"dev_lang": "javascript",
"dev_channel": "homebridge",
"devVersion": "1.7.0-beta.48"
}
body = null
[7/12/2023, 11:50:12 AM] [deCONZ] padCONBEE: dresden elektronik deCONZ / ConBee II gateway v2.22.2
[7/12/2023, 11:50:12 AM] [deCONZ] padCONBEE: warning: recommended version: deCONZ v2.21.2
[7/12/2023, 11:50:12 AM] [deCONZ] padCONBEE: websocket connected to ws://<IP_ADDRESS>:443
[7/12/2023, 11:50:12 AM] [Tuya] [TuyaOpenAPI] Response:
path = /v1.1/homes/9691003/scenes
data = {
"result": [],
"success": true,
"t":<PHONE_NUMBER>307,
"tid": "7eb4a4d6209911ee8ac9ce4d0cb672c1"
}
[7/12/2023, 11:50:12 AM] [Tuya] Got 2 device(s) and scene(s).
[7/12/2023, 11:50:12 AM] [Tuya] Device list saved at /var/lib/homebridge/persist/TuyaDeviceList.XXXX.json
[7/12/2023, 11:50:12 AM] [Tuya] Restoring existing accessory from cache: EG Flur
[7/12/2023, 11:50:12 AM] [Tuya] Restoring existing accessory from cache: WiFi Smart Smoke Alarm(CBU) 2
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Adding Accessory : harmonyHUB-TV
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - configuring Main TV Service
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating TV Service
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating Input Service - Apple TV sehen in position 1
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating Input Service - TV in position 2
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating Input Service - Fire TV sehen in position 3
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating Input Service - Airplay in position 4
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating Input Service - Xbox One X in position 5
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)WARNING - No main Activity that match config file found, default to first one
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Configuring Main Activity Apple TV sehen
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Creating TV Speaker Service
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Discovered Activity : Apple TV sehen
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Discovered Activity : TV-Switch
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Discovered Activity : Fire TV sehen
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Discovered Activity : Airplay
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - Discovered Activity : Xbox One X
[7/12/2023, 11:50:12 AM] [harmonyHUB] (harmonyHUB)INFO - setupFoundAccessories - TV accessory added as external accessory
[7/12/2023, 11:50:12 AM] harmonyHUB-TV 60D0 is running on port 38925.
[7/12/2023, 11:50:12 AM] Please add [harmonyHUB-TV 60D0] manually in Home app. Setup Code: 060-91-981
[7/12/2023, 11:50:12 AM] [Nuki] listening on http://<IP_ADDRESS>:34965/notify
[7/12/2023, 11:50:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Door closed
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Inactive (Inactive)
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Remote operation enabled (remote start allowed)
[7/12/2023, 11:50:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Child lock disabled
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Off
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Connected
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Off
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Inactive (Inactive)
[7/12/2023, 11:50:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:50:12" (from "Wed Jul 12 2023 11:49:46")
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Finished reading available program options
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Adding services for 0 programs
[7/12/2023, 11:50:12 AM] [HomeConnect] [Kaffeevollautomat] Removing services for 0 programs
[7/12/2023, 11:50:13 AM] [Govee] [LAN] client enabled and found 1 device(s).
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Daylight: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Daylight: dresden elektronik Daylight v2.22.2 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Büro Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Büro Fenster: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Balkon Tür: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Balkon Tür: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Essbereich Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Essbereich Fenster: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Sofa Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Sofa Fenster: LUMI lumi.sensor_magnet.aq2 v20161128 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Bad Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Bad Fenster: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Küchen Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Küchen Fenster: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Haustür: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Haustür: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Brief: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Brief: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Schlafzimmer Fenster: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Schlafzimmer Fenster: LUMI lumi.sensor_magnet.aq2 v0.0.3 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Water 38: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Water 38: LUMI lumi.sensor_wleak.aq1 v0.0.4 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: Heizungsmelder: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] Heizungsmelder: IKEA of Sweden TRADFRI motion sensor v2.0.022 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: VPIR Heizungsraum: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] VPIR Heizungsraum: dresden elektronik CLIPPresence v2.22.2 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: FSM_STATE Heizungsraum: add accessory
[7/12/2023, 11:50:13 AM] [deCONZ] FSM_STATE Heizungsraum: dresden elektronik CLIPGenericStatus v2.22.2 (1 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: dresden elektronik deCONZ / ConBee II gateway v2.22.2 (14 accessories for 20 devices, 14 resources)
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: migration: /resourcelinks/2: 14 resources
[7/12/2023, 11:50:13 AM] [deCONZ] padCONBEE: warning: recommended version: deCONZ v2.21.2
[7/12/2023, 11:50:13 AM] [deCONZ] 1 gateways
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Found HAP device with username D3:4F:59:C4:24:44
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Testing D3:4F:59:C4:24:44 via http://<IP_ADDRESS>:38925/accessories
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Success D3:4F:59:C4:24:44 via http://<IP_ADDRESS>:38925/accessories
[7/12/2023, 11:50:13 AM] [deCONZ] created debug dump file /var/lib/homebridge/homebridge-deconz.json.gz
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: [<IP_ADDRESS>:38925 (D3:4F:59:C4:24:44)] Instance Registered
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Failed 78:e8:0a:b5:1d:41 via http://<IP_ADDRESS>:80/accessories
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Failed 78:e8:0a:b5:1d:41 with error: timeout of 10000ms exceeded
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Could not register to device with username 78:e8:0a:b5:1d:41
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Failed ce:76:ef:e7:72:2d via http://<IP_ADDRESS>:80/accessories
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Failed ce:76:ef:e7:72:2d with error: timeout of 10000ms exceeded
[7/12/2023, 11:50:13 AM] [Homebridge UI] [HapClient] Discovery :: Could not register to device with username ce:76:ef:e7:72:2d
[7/12/2023, 11:50:13 AM] [Govee] [HTTP] client enabled and found 3 device(s).
[7/12/2023, 11:50:13 AM] [Govee] [AWS] client enabled.
[7/12/2023, 11:50:13 AM] [Govee] [BLE] disabling client as ENODEV, No such device.
[7/12/2023, 11:50:13 AM] [Govee] [Fiona light] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[7/12/2023, 11:50:13 AM] [Govee] [Fiona light] initialised with id [3F:13:D4:AD:FC:3E:D9:79] [H619C].
[7/12/2023, 11:50:14 AM] [Govee] [Cloud] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[7/12/2023, 11:50:14 AM] [Govee] [Cloud] initialised with id [7A:E2:D4:AD:FC:61:82:AA] [H61A0].
[7/12/2023, 11:50:14 AM] [Govee] [PornoLicht] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"enabled"}.
[7/12/2023, 11:50:14 AM] [Govee] [PornoLicht] initialised with id [F1:CD:D4:AD:FC:11:D9:1A] [H61A0].
[7/12/2023, 11:50:14 AM] [Shelly] Excluding device SHPLG-S C8C9A3B8D4CA at <IP_ADDRESS>
[7/12/2023, 11:50:15 AM] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
[7/12/2023, 11:50:16 AM] [Shelly] Excluding device SHPLG-S 3CE90ED7F63B at <IP_ADDRESS>
[7/12/2023, 11:50:16 AM] [Homebridge UI] Starting terminal session
[7/12/2023, 11:50:17 AM] [Shelly] Excluding device SHPLG-S 3CE90ED7B20D at <IP_ADDRESS>
[7/12/2023, 11:50:20 AM] [Shelly] Excluding device SHPLG2-1 2B13C4 at <IP_ADDRESS>
[7/12/2023, 11:50:21 AM] [Shelly] Excluding device SHPLG-S DE9339 at <IP_ADDRESS>
[7/12/2023, 11:50:25 AM] [Shelly] Excluding device SHSW-1 8CAAB56200C7 at <IP_ADDRESS>
[7/12/2023, 11:51:03 AM] [Homebridge UI] [HapClient] Discovery :: Ended
[7/12/2023, 11:51:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: subscribe to event notifications
[7/12/2023, 11:51:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: error: too many callbacks registered
[7/12/2023, 11:51:12 AM] [Nuki] Nuki_Bridge_7E7F1CE1: Last Updated: set to "Wed Jul 12 2023 11:51:12" (from "Wed Jul 12 2023 11:50:12")
[7/12/2023, 11:51:13 AM] [deCONZ] padCONBEE Button: Programmable Switch Event: Single Press
`


How to do with 3d Rotation of Sprites

Hi,
Just curious to know if something like this is possible now in Phaser V3 ?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Using the Mesh game object, yes.
http://labs.phaser.io/index.html?dir=game objects/mesh/&q=
For all subsequent questions like this, please use either Slack, Discord or the forum. Issues are for reporting issues with the API.


Implement Search

Description
The website needs a search function.  Ideally that search function would also search an identified list of other conda-related sites as well.  See here for how Galaxy does this with Google Programmable Engine Search.
Tasks

[ ] Content Team: Identify list of sites / subsites / URLs to include
[ ] Implementation Team: Identify search technology to use
[ ] Implementation Team: Implement proof of concept
[ ] Implementation and Design Teams: iterate over presentation

See

Search Notes

Split this issue into 3 smaller ones: #19, #20, and #21.


Fix Hermes support for React Native 0.61.0

Fix Hermes support for React Native 0.61.0: change Hermes binary path from hermesvm to hermes-engine because hermesvm is now deprecated…
React Native 0.61.x start using hermes-engine instead of hermesvm. Introduced in: https://github.com/facebook/react-native/pull/25908/commits/70f1c87db120ad63fee7f86a8a10b3fde2df47d2
https://www.npmjs.com/package/hermesvm is now deprecated in favour of hermes-engine.

Hi @lpikora
Thanks a lot for your contribution, but we have another PR that was opened later to solve the same issue: #654. That one supports both engines so we'll prefer it for now.


Setup automated tests

Automated tests have been set up. Initial tests for Reconstruction class have been implemented.


removed flush() argument

I propose to remove the flush() prefix argument as I don't see any use case. I think it was there because the method is recursive, but that's leaking an implementation detail. Passing a prefix was not documented.

:+1:


add new bootnode to Kusama

Current dependencies on/for this PR:

main

PR #110   👈

This stack of pull requests is managed by Graphite.


kernel: Kconfig: Remove redundant 'default n' properties

Bool symbols implicitly default to 'n'.
A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you
want to override a 'default y' on the base definition of the symbol. It
isn't used like that on any of these symbols though.
Also simplify the definitions of COOP_ENABLED, PREEMPT_ENABLED, and
SYS_CLOCK_EXISTS. 'default' (and def_bool) can take any expression, not
just a fixed value.
(It would work without the parentheses around the comparisons too.)
Signed-off-by: Ulf Magnusson<EMAIL_ADDRESS>

Codecov Report

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

@@          Coverage Diff           @@
##           master   #8515   +/-   ##
======================================
  Coverage    63.8%   63.8%
======================================
  Files         426     426
  Lines       40890   40890
  Branches     6921    6921
======================================
  Hits        26089   26089
  Misses      11666   11666
  Partials     3135    3135

Continue to review full report at Codecov.

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


Check if a variable is of type component

In order to use the addComponent function, that function need to chack that the parameter passed is a valid component (not just a random type like string).
Someone figure out how to do this:
this.addComponent = function(componentInstance)
    {
        //Check that it is a valid componenet
        //e.g. renderer
        //--> How would I do this <--

        //Add to list
        this.components.push(componentInstance);
    }

The component system has been removed and is being rewritten - use the newest version.


Wiki root page has broken images

@arosien, could it be your endpoint protection is blocking the images somehow?  The images show up just fine for me.

Hmm, weird. Yeah it was me.


Deprecate GeoTransforms class

This is PR into #1179 so merge that first.
It also depends on CesiumGS/cesium-native#696 so merge that first, too.
Between Unreal itself having double-precision vector and matrix types, and new capabilities in cesium-native (like LocalHorizontalCoordinateSystem), the GeoTransforms class is no longer needed.
This PR marks it deprecated and switches all of our uses of it to an alternative. I was really happy to see that this ends up deleting more code than it adds.
I didn't switch UCesiumGlobeAnchorComponent to use cesium-native's GlobeAnchor yet, so there's a little duplication because of that at the moment. That will be a separate PR.

Thanks for the pull request @kring!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

Looks great @kring . Will merge once the checks finish.


Comparing option fields is not correct

Hi !
I have an issues with getting option value from text. (as bellow)

You see value of Field.Type is Option. So, the result of comparison expression should be No
But the system show result:

Please check this problem for me.

Hi!
Please check my case.

We will investigate it.

This is fixed in the latest update.
pageextension 50101 MyExtension extends "Customer Card"
{
    trigger OnOpenPage()
    var
        t: Codeunit TestingCodeUnit;
    begin
        Message('Before');
        GetOptionNo(Database::Customer, 80, '');
        Message('After');
    end;

    local procedure GetOptionNo(TableNum: Integer; FieldNumber: Integer; PValue: Text[250])
    var
        RecRef: RecordRef;
        FieldRef: FieldRef;
        TypeHelper: Codeunit 10;
        "Field": Record Field;
    begin
        RecRef.Open(TableNum);
        FieldRef := RecRef.Field(FieldNumber);
        Field.Get(RecRef.Number, FieldRef.Number);
        Message(Format(Field.Type<>Field.Type::Option));

    end;
}


fix(cli): Fix agent restart command

copilot:all

Current dependencies on/for this PR:

main

PR #3699   👈

This comment was auto-generated by Graphite.


chore: upgrade Aspect Workflows to 5.10.0-alpha.8

Sorting change in rosetta output?

Not sure. @mattem ?


Allow user in target address

This PR supports users in direct target address, i.e user@example.com:22
see #73

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 84.291%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
1819

Relevant Lines:
2158

💛  - Coveralls


fix the missing symbol issue in stencils with scalar arguments

Description
fix the bugs in the scalar function argument in stencils, this bug caused by the unreachable code trimming due to the non-overlapped loop region. This fix releases the unreachable code trimming and keep the same IR to dace which has the same function signatures as in the function call tree when orchestration option is used.
this fix requires to work with https://github.com/GridTools/gt4py/pull/1612.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note
any relevant details for your test configuration (e.g. compiler, OS).  Include
enough information so someone can reproduce your tests.
Checklist:

[ y ] My code follows the style guidelines of this project
[ y ] I have performed a self-review of my own code
[ y] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ y ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
[ ] New check tests, if applicable, are included
[ ] Targeted model if this changed was triggered by a model need/shortcoming

I have been able to test these changes, along with the changes in PR 1612 in GT4Py, in a c384 16x16 layout baroclinic configuration.


PLAT-94881: Add JSDoc to Agate

This PR adds or corrects the inline documentation.  There are some placeholders for text I wasn't sure about.  Also, there is a lot of inconsistency about what is exported from various components.  We may want to address this in a future PR.  I did not, in general, add jsdoc for props where they were missing.  This, too, will have to be addressed in a future PR.

For ease of testing, you can link agate into the enact/packages directory for parsing.


angular v17 features

Description
Please provide the following information:

What changes you made:

Why you made them, and:

Any other useful context:

Make sure to follow the PR preparation steps in CONTRIBUTING.md before submitting your PR:

[ ] format the codebase: from the root, run yarn fmt:prettier.
[ ] update all snapshots (in core & CLI): from the root, run yarn test:update
[ ] add Changeset entry: from the root, run yarn g:changeset and follow the CLI instructions. Alternatively, use the Changeset Github Bot to create the file.

Closing this for now, will re-open if we need any v17 features in the future


Semi-transparent border appears around dropdown menus in code-oss on Hyprland

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
No
System Info and Version
Hyprland, built from branch  at commit 0f594732b063a90d44df8c5d402d658f27471dfe  (props: bump version to 0.43.0).
Date: Sun Sep 8 16:48:21 2024
Tag: v0.43.0, commits: 5196
flags: (if any)
System Information:
System name: Linux
Node name: archlinux
Release: 6.11.2-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Fri, 04 Oct 2024 21:51:11 +0000
GPU information:
c1:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller])
os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
plugins:
======Config-Start======
Config File: /home/stolas/.config/hypr/hyprland.conf: Read Succeeded

AUTOGENERATED HYPR CONFIG.

This is an example Hyprland config file.
Refer to the wiki for more information.
https://wiki.hyprland.org/Configuring/Configuring-Hyprland/
Please note not all available settings / options are set here.
For a full list, see the wiki
You can split this configuration into multiple files
Create your files separately and then link them to this file like this:
source = ~/.config/hypr/myColors.conf
################
MONITORS
################
See https://wiki.hyprland.org/Configuring/Monitors/
monitor=eDP-1,preferred,auto,auto
#external monitor
monitor=DP-2,preferred,auto,auto, mirror, eDP-1
###################
MY PROGRAMS
###################

See https://wiki.hyprland.org/Configuring/Keywords/
Set programs that you use
$terminal = kitty
$fileManager = kitty -e /usr/bin/spf
$menu = wofi --show drun
#################
AUTOSTART
#################
Autostart necessary processes (like notifications daemons, status bars, etc.)
Or execute your favorite apps at launch like this:
exec-once = $terminal
exec-once = nm-applet &
exec-once = hyprpaper
#############################
ENVIRONMENT VARIABLES
#############################
See https://wiki.hyprland.org/Configuring/Environment-variables/
env = XCURSOR_SIZE,24
env = HYPRCURSOR_SIZE,24
#####################
LOOK AND FEEL
#####################
Refer to https://wiki.hyprland.org/Configuring/Variables/
https://wiki.hyprland.org/Configuring/Variables/#general
general {
gaps_in = 4
gaps_out = 5
border_size = 2

# https://wiki.hyprland.org/Configuring/Variables/#variable-types for info about colors
col.active_border = rgba(33ccffee) rgba(00ff99ee) 45deg
col.inactive_border = rgba(595959aa)

# Set to true enable resizing windows by clicking and dragging on borders and gaps
resize_on_border = false

# Please see https://wiki.hyprland.org/Configuring/Tearing/ before you turn this on
allow_tearing = false

layout = dwindle

}
https://wiki.hyprland.org/Configuring/Variables/#decoration
decoration {
rounding = 10
# Change transparency of focused and unfocused windows
active_opacity = 1.0
inactive_opacity = 1.0

drop_shadow = true
shadow_range = 4
shadow_render_power = 3
col.shadow = rgba(1a1a1aee)

# https://wiki.hyprland.org/Configuring/Variables/#blur
blur {
    enabled = true
    size = 1000
    passes = 1

    vibrancy = 0.1696
}

}
https://wiki.hyprland.org/Configuring/Variables/#animations
animations {
enabled = true
# Default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

bezier = myBezier, 0.05, 0.9, 0.1, 1.05

animation = windows, 1, 7, myBezier
animation = windowsOut, 1, 7, default, popin 80%
animation = border, 1, 10, default
animation = borderangle, 1, 8, default
animation = fade, 1, 7, default
animation = workspaces, 1, 6, default

}
See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
dwindle {
pseudotile = true # Master switch for pseudotiling. Enabling is bound to mainMod + P in the keybinds section below
preserve_split = true # You probably want this
no_gaps_when_only = 1
}
See https://wiki.hyprland.org/Configuring/Master-Layout/ for more
master {
new_status = master
}
https://wiki.hyprland.org/Configuring/Variables/#misc
misc {
force_default_wallpaper = -1 # Set to 0 or 1 to disable the anime mascot wallpapers
disable_hyprland_logo = false # If true disables the random hyprland logo / anime girl background. :(
}
#############
INPUT
#############
https://wiki.hyprland.org/Configuring/Variables/#input
input {
kb_layout = de
kb_variant = nodeadkeys
kb_model =
kb_options =
kb_rules =
follow_mouse = 1

sensitivity = 0 # -1.0 - 1.0, 0 means no modification.

touchpad {
    natural_scroll = false
    disable_while_typing = true
}

}
https://wiki.hyprland.org/Configuring/Variables/#gestures
gestures {
workspace_swipe = false
}
Example per-device config
See https://wiki.hyprland.org/Configuring/Keywords/#per-device-input-configs for more
device {
name = epic-mouse-v1
sensitivity = -0.5
}
###################
KEYBINDINGS
###################
See https://wiki.hyprland.org/Configuring/Keywords/
$mainMod = SUPER # Sets "Windows" key as main modifier
Example binds, see https://wiki.hyprland.org/Configuring/Binds/ for more
bind = $mainMod, Q, exec, $terminal
bind = $mainMod, C, killactive,
bind = $mainMod, M, exit,
bind = $mainMod, E, exec, $fileManager
bind = $mainMod, V, togglefloating,
bind = $mainMod, R, exec, $menu
bind = $mainMod, P, pseudo, # dwindle
bind = $mainMod, J, togglesplit, # dwindle
Move focus with mainMod + arrow keys
bind = $mainMod, left, movefocus, l
bind = $mainMod, right, movefocus, r
bind = $mainMod, up, movefocus, u
bind = $mainMod, down, movefocus, d
Switch workspaces with mainMod + [0-9]
bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10
Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = $mainMod SHIFT, 1, movetoworkspace, 1
bind = $mainMod SHIFT, 2, movetoworkspace, 2
bind = $mainMod SHIFT, 3, movetoworkspace, 3
bind = $mainMod SHIFT, 4, movetoworkspace, 4
bind = $mainMod SHIFT, 5, movetoworkspace, 5
bind = $mainMod SHIFT, 6, movetoworkspace, 6
bind = $mainMod SHIFT, 7, movetoworkspace, 7
bind = $mainMod SHIFT, 8, movetoworkspace, 8
bind = $mainMod SHIFT, 9, movetoworkspace, 9
bind = $mainMod SHIFT, 0, movetoworkspace, 10
Example special workspace (scratchpad)
bind = $mainMod, S, togglespecialworkspace, magic
bind = $mainMod SHIFT, S, movetoworkspace, special:magic
#Fullscreen
bind=SUPER,F,fullscreen
Move workspace windows around
bind = $mainMod SHIFT, left, swapwindow, l
bind = $mainMod SHIFT, right, swapwindow, r
bind = $mainMod SHIFT, up, swapwindow, u
bind = $mainMod SHIFT, down, swapwindow, d
Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, e+1
bind = $mainMod, mouse_up, workspace, e-1
Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow
Laptop multimedia keys for volume and LCD brightness
bindel = ,XF86AudioRaiseVolume, exec, wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+
bindel = ,XF86AudioLowerVolume, exec, wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%-
bindel = ,XF86AudioMute, exec, wpctl set-mute @DEFAULT_AUDIO_SINK@ toggle
bindel = ,XF86AudioMicMute, exec, wpctl set-mute @DEFAULT_AUDIO_SOURCE@ toggle
bindel = ,XF86MonBrightnessUp, exec, brightnessctl s 5%+
bindel = ,XF86MonBrightnessDown, exec, brightnessctl s 5%-
##############################
WINDOWS AND WORKSPACES
##############################
See https://wiki.hyprland.org/Configuring/Window-Rules/ for more
See https://wiki.hyprland.org/Configuring/Workspace-Rules/ for workspace rules
Example windowrule v1
windowrule = float, ^(kitty)$
Example windowrule v2
windowrulev2 = float,class:^(kitty)$,title:^(kitty)$
windowrulev2 = suppressevent maximize, class:.* # You'll probably like this.
windowrulev2 = opacity 0.8 0.7, class:(kitty)
======Config-End========
Description
I'm experiencing a visual issue when using code-oss on the Hyprland window manager. When I click on the options in the top menu bar (such as File, Edit, or Settings), a semi-transparent border appears around the dropdown menu that opens. This border is not present in other applications and seems to be specific to code-oss.
Expected Behavior:
The dropdown menu should open without any additional borders or visual artifacts.
Actual Behavior:
A semi-transparent border appears around the dropdown menu, which is visually distracting.
How to reproduce
Steps to Reproduce:
Open code-oss on Hyprland.
Click on any option in the top menu bar (e.g., File, Edit, Settings).
Observe the semi-transparent border around the dropdown menu.

Crash reports, logs, images, videos
hyprland.log

what? Can you provide a screenshot?

what? Can you provide a screenshot?

Oh my bad i completely forgot. I will do so asap

dont launch it in xwayland. That's an unfixable issue with xwl. Whats you are seeing is blur. Why is it bugged? IDK, maybe legacy_renderer.


Mapping to flip-flops with an enable in dfflibmap

Feature Description
dfflibmap is responsible for mapping to technology flip-flops as described in a Liberty file. This ticket is to add support for mapping to flip-flop types with an enable, which there's no support for as of yet.

I had a similar need. What I did is first use difflegalize to reduce all ffs into to a compatable subset of dffs, and use techmap to map them manually.
# script.ys
dfflegalize -cell $_DFF_P_ 0 -cell $_DFFE_PP_ 0
techmap -map techmap_dff.v

// techmap_dff.v
module \$_DFF_P_ (input D, C, output Q);
MY_DFF _TECHMAP_REPLACE_ (.C(C), .D(D), .Q(Q));
endmodule

module \$_DFFE_PP_ (input D, C, E, output Q);
MY_DFFE _TECHMAP_REPLACE_ (.C(C), .D(D), .E(E), .Q(Q));
endmodule

This requires a separate techmap_dff.v with all your flops. I guess you can create a techmap verilog file for your library, or find some way to extract and generate the techmap file.
I also took a look at the code of dfflibmap a while back. It looked quite hard-coded. Matching is done directly on Liberty AST. Matching flops with enable is too difficult for me to code up, but I think it can be done, since there's clearly a working Liberty frontend driven by read_liberty.

Yes, I have written a similar file for sky130hd to estimate the impact of inferring/not inferring the flip-flops. Let me share it on the off chance it's useful to someone.
(* techmap_celltype="$_DFFE_PP_" *)
module dffe_rule(D, C, E, Q);
	input D, C, E;
	output Q;
	sky130_fd_sc_hd__edfxtp_1 _TECHMAP_REPLACE_
		(.CLK(C), .DE(E), .D(D), .Q(Q));
endmodule

It might need a bit of code to write generic detection but the information in the Liberty file is there:
        ff ("IQ","IQ_N") {
            clocked_on : "CLK";
            next_state : "(D&DE) | (IQ&!DE)";
        }
        pin ("Q") {
            function : "IQ";
        }


ARM64v8-TSV110: dgemm sigfaults on large square matrices single thread

Description:
Crash in dgemm_oncopy(). This is because sb parameter points out of allocated buffer. And the pointer is calculated in driver/level3/level3.c:350 as (sb + min_l * (jjs - js) * COMPSIZE * l1stride), where jjs is close to 4000 and min_l is 512. jjs limited by GEMM_R and it is GEMM_R == DGEMM_DEFAULT_R == 4096.
To reproduce:
OS: CentOS Linux release 7.6.1810 (AltArch)
CPU: TSV110
Compiler: gcc 9.2.0
Commands:
make TARGET=TSV110 USE_OPENMP=yes
cd benchmarks; make
ulimit -s unlimited
OMP_NUM_THREADS=1 ./dgemm.goto 4000 10000 1000
Root cause:
BUFFER_SIZE is too small for P, Q and R.
Suggested fix
Add to common_arm64.h:
 #if defined(CORTEXA57)
 #define BUFFER_SIZE     (20 << 20)
+#elif defined(TSV110) || defined(EMAG8180)
+#define BUFFER_SIZE     (32 << 20)
 #else
 #define BUFFER_SIZE     (16 << 20)
 #endif

And in the beginning of memory.c add a buffer size guard like this:
/* Memory buffer must fit two matrix subblocks of maximal size */
#if BUFFER_SIZE < (SGEMM_DEFAULT_P * SGEMM_DEFAULT_Q * 4 * 2) || \
    BUFFER_SIZE < (SGEMM_DEFAULT_P * SGEMM_DEFAULT_R * 4 * 2) || \
    BUFFER_SIZE < (SGEMM_DEFAULT_R * SGEMM_DEFAULT_Q * 4 * 2)
#error BUFFER_SIZE is too small for P, Q, and R of SGEMM
#endif
#if BUFFER_SIZE < (DGEMM_DEFAULT_P * DGEMM_DEFAULT_Q * 8 * 2) || \
    BUFFER_SIZE < (DGEMM_DEFAULT_P * DGEMM_DEFAULT_R * 8 * 2) || \
    BUFFER_SIZE < (DGEMM_DEFAULT_R * DGEMM_DEFAULT_Q * 8 * 2)
#error BUFFER_SIZE is too small for P, Q, and R of DGEMM
#endif
#if BUFFER_SIZE < (CGEMM_DEFAULT_P * CGEMM_DEFAULT_Q * 8 * 2) || \
    BUFFER_SIZE < (CGEMM_DEFAULT_P * CGEMM_DEFAULT_R * 8 * 2) || \
    BUFFER_SIZE < (CGEMM_DEFAULT_R * CGEMM_DEFAULT_Q * 8 * 2)
#error BUFFER_SIZE is too small for P, Q, and R of CGEMM
#endif
#if BUFFER_SIZE < (ZGEMM_DEFAULT_P * ZGEMM_DEFAULT_Q * 16 * 2) || \
    BUFFER_SIZE < (ZGEMM_DEFAULT_P * ZGEMM_DEFAULT_R * 16 * 2) || \
    BUFFER_SIZE < (ZGEMM_DEFAULT_R * ZGEMM_DEFAULT_Q * 16 * 2)
#error BUFFER_SIZE is too small for P, Q, and R of ZGEMM
#endif

Note
This issue mostlikly also affect EMAG8180 target, possible others - the guard should notify about that.

Thanks - ultimately this is probably "just" another manifestation of the fundamental problem from #1698 (BUFFER_SIZE should be more easily configurable at compile time, if it cannot go away completely). The current values are mostly from the GotoBLAS of ten years ago, and must have been quite arbitrary even then.

Well that escalated quickly... seems same problem affects SkylakeX and ARMV7 targets at least.

Hmm. Either the formula is wrong or there is something fundamentally wrong with the buffer allocation on POWER8. I just do not see how BUFFER_SIZE can ever be large enough to accomodate the value derived in the absence of a predefined xGEMM_DEFAULT_R...

One thing that seems to be clear is that the calculation of the size requirement in the error message is going to overflow when xGEMM_DEFAULT:_R is itself a notrivial formula rather than a constant. (Which appears to have been the case specifically for POWERx platforms ever since GotoBLAS2, but I have no idea why)


Allow disabling enum generation

Generating java enums from schemas generates problems with backwards compatibility. If a new values is ever added to an enum, all clients must be upgraded first, otherwise they would break, which makes upgrades very slow and costly.
Please allow disabling enum generation using a configuration switch, in which case just Strings would be generated for the specific fields (since they mostly have type: String, in jsonschema).

Feel free to submit a pull request for this. It would be good to implement a new optional called useEnumForEnums.


Removed [anysex] to be handled by generic extractor

Please follow the guide below
Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[x] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Anysex webpages video urls are located in the html video sources which can be extracted by the generic extractor
closes #19279

Formats are not sorted.

Adjusted InfoExtractor to sort formats


Ability to customize output video/audio format per-channel

fixed in https://github.com/chrisbenincasa/tunarr/pull/1001


Free-form text box to self report purchases

https://github.com/artsy/collector-experience/issues/86#issuecomment-278797200
Text box to self report historical inquiries/purchases

Added in https://github.com/artsy/reaction-force/pull/40


Plugin error: OA-file-hider Error

When I want to activate the plugin I get the error message: Plugin failure: OA-file-hider Error.
In the console I see: Plugin failure: OA-file-hider Error: ENOENT: no such file or directory, open 'R:\Daten\obsidian\NAS-Frank.obsidian\plugins\file-hider-main\main. js'
What am I doing wrong.

Hi there,
This is most likely because the plugin is written in Typescript and I don't keep a compiled version of the code in the repo.
If you must install it manually, the compiled main.js can be found in releases. If you can though, I would recommend installing the plugin using Obsidian's plugin manager.

Hi and thanks for the quick answer.  Learned something again. Your plugin is perfect for me. I hide the png files because I don't want to see them in the obsidian tree. It would be even better if I could hide all png files automatically :-) Thanks again!!!
Best regards
Frank
Von: Oliver @.>
Gesendet: Samstag, 11. November 2023 21:10
An: Oliver-Akins/file-hider @.>
Cc: FS-Code-zz @.>; Author @.>
Betreff: Re: [Oliver-Akins/file-hider] Plugin error: OA-file-hider Error (Issue #38)
Hi there,
This is most likely because the plugin is written in Typescript and I don't keep a compiled version of the code in the repo.
If you must install it manually, the compiled main.js can be found in releases https://github.com/Oliver-Akins/file-hider/releases/tag/1.1.1 . If you can though, I would recommend installing the plugin using Obsidian's plugin manager.
—
Reply to this email directly, view it on GitHub https://github.com/Oliver-Akins/file-hider/issues/38#issuecomment-1806906656 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AOYTY2JPG4BC7GLFPCIUYLDYD7LTHAVCNFSM6AAAAAA7HNOPWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWHEYDMNRVGY .
You are receiving this because you authored the thread.Message ID: @.***>

No worries, glad I could help get it sorted out.
One thing I want to note: you're not stupid for not understanding/knowing the plugin is written in Typescript and what that requires, it's just something that not everyone may know, if I did make you feel stupid, sorry; that wasn't my intent (I was trying to explain why it wouldn't work with the code as it was).
On your note of having it hide files automatically, I've been looking into ways of doing this using RegEx patterns (hiding .*\.png would result in all files ending in .png to be hidden automatically), however I haven't gotten a solution up to my standards yet so it isn't something I've even released a beta version of yet.


[T4A4][W15-A2]Liu Ziyang

Ready for review

Some comments added. Feel free to add more comment if you have any questions. Once you are done, you may close the PR after reading comments.


Add an equivalent for Scalaz Task

An implementation is already in progress. Proposal is here: https://gist.github.com/alexandru/55a6038c2fe61025d555

I'm assigning it the 1.1 milestone, as I won't be breaking any API for adding it. The 2.0 milestone is reserved for moving stuff around and removing deprecated stuff, as in things breaking people's source compatibility.

Done, it's on master.

Done. It's on master.


Example for image classification using efficientnet with fine-tuning

FYI, @fchollet and @omalleyt12

Please rebase from master, there's a fix for the CI

This looks like something messed up in a merge commit. Can you push a clean version of the commit history or create a new pr, rebased on  master?

Sure. The merge after rebase seemed to mess it up


command to generate list of unresolved glottolog lookups

As I'm going through and sorting out glottolog lookup fails, it would be great to be able to generate the list @xrotwang made here again myself.

This list is spit out by the grambank cldf command - which you should be able to run now. Syntax is https://github.com/glottobank/grambank-cldf/blob/master/RELEASING.md#releasing-the-grambank-data-as-cldf-datset

I can't seem to run grambank cldf fully, trying to problem solve right now. Stuck at the stage right after langs to refs mapping. I think it may have something to do with the glottolog repos. I've got an updated clone of all the relevant reposes listed, but it seems the glottolog repos should contain a glottolog folder(?). I'm not really sure what's going on, I'll try a couple of ideas myself but if there is something that jumps at you Robert please let me know. I'm guessing it's to do with running some part of pyglottolog.
I'm running the following within a virtual python environment where pygrambank is installed:
grambank --repos /Users/skirgard/Dropbox/Git/Grambank cldf --wiki_repos /Users/skirgard/Dropbox/Git/grambank_grambank/Grambank.wiki/ --glottolog-version v4.1 --cldf_repos /Users/skirgard/Dropbox/Git/grambank-cldf/  /Users/skirgard/Dropbox/Git/glottolog
tail end of terminal output:

Selecting best sheet for zaye1235
195 dps: choosing sheet BHR_zaye1235
195 dps: skipping sheet SR_zaye1235
loading bibs
computing lang-to-refs mapping ...
... done
Traceback (most recent call last):
  File "/Users/skirgard/py_venvs/grambank/bin/grambank", line 8, in <module>
    sys.exit(main())
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/__main__.py", line 150, in main
    return args.main(args) or 0
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/commands/cldf.py", line 34, in run
    create(args.repos, glottolog.dir, args.wiki_repos, args.cldf_repos)
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/cldf.py", line 96, in create
    'https://github.com/glottobank/pygrambank', clone=Path(__file__).parent.parent.parent),
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pycldf/dataset.py", line 180, in add_provenance
    v = [to_json(vv) for vv in v]
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pycldf/dataset.py", line 180, in <listcomp>
    v = [to_json(vv) for vv in v]
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pycldf/dataset.py", line 173, in to_json
    return obj.json_ld()
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pycldf/dataset.py", line 120, in json_ld
    res['dc:created'] = git_describe(self.clone)
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/clldutils/path.py", line 192, in git_describe
    raise ValueError('cannot describe non-existent directory')
ValueError: cannot describe non-existent directory

Or wait, installing pyclf of course. Hold on

No.. that's not it.  Will stare at it for a while longer.

And all the paths you are passing in do exist?

Including /Users/skirgard/Dropbox/Git/grambank_grambank/Grambank.wiki/?

I had moved it because of something else, just noticed. Moved it back. Now:
loading bibs
computing lang-to-refs mapping ...
... done
Traceback (most recent call last):
  File "/Users/skirgard/py_venvs/grambank/bin/grambank", line 8, in <module>
    sys.exit(main())
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/__main__.py", line 150, in main
    return args.main(args) or 0
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/commands/cldf.py", line 34, in run
    create(args.repos, glottolog.dir, args.wiki_repos, args.cldf_repos)
  File "/Users/skirgard/py_venvs/grambank/lib/python3.7/site-packages/pygrambank/cldf.py", line 166, in create
    lang = glottolog.languoids_by_glottocode[sheet.glottocode]
KeyError: 'east2851'

That's a new glottocode, you'll have to run with --glottolog-version v4.2.1.

Aha okay.

Uh it looks like it worked! Hurray! Let me inspect these failed glottolog lookups just to see that things make sense :)

The output or warnings is divided into two parts, the first with the syntax of
('Maurer', '1968', 'tang1348') 1 and the second with the syntax oftang1348 [('Maurer', '1968'), ('Maurer', '1967')]. Earlier I got only the first part, but the second is actually more helpful. I take it no-one else is really going to run this command so it matters relatively little, but I was a bit surprised to get this output.