MT6853 test was not successful

*.ofp has *. Auth file after unpacking. Is this step unnecessary?But sp_flash_tool_v5.2052 download error?

I can't find any info on MT6835, also please provide a log of the utility

I can't find any info on MT6835, also please provide a log of the utility

I'm sorry, the model is MT6853, which is used in Realme Q2 Pro.I can provide more information and support, such as TeamViewer.
[2021-02-09 19:41:20.028892] Device hw code: 0x996
[2021-02-09 19:41:20.029890] Device hw sub code: 0x8a00
[2021-02-09 19:41:20.029890] Device hw version: 0xca00
[2021-02-09 19:41:20.029890] Device sw version: 0x0
[2021-02-09 19:41:20.030890] Device secure boot: True
[2021-02-09 19:41:20.031889] Device serial link authorization: False
[2021-02-09 19:41:20.032889] Device download agent authorization: True
[2021-02-09 19:41:20.034889] Disabling watchdog timer
[2021-02-09 19:41:20.035888] Disabling protection
[2021-02-09 19:41:21.065907] Test mode, testing 0x1...
[2021-02-09 19:41:21.068908] Waiting for bootrom
[2021-02-09 19:41:27.790375] Found port = COM3
[2021-02-09 19:41:28.812503] Test mode, testing 0x2...

MT6853 / HW_CODE 0x996 is not (yet) supported.
You can try to dump brom using testmode.
Testmode will test all values for var_1 one after the other.
You can also first try manually testing the known values from other devices:
https://github.com/MTK-bypass/exploits_collection/blob/master/default_config.json5
main.py --testmode --var_1 = <value>

MT6853 / HW_CODE 0x996 is not (yet) supported.
You can try to dump brom using testmode.
Testmode will test all values for var_1 one after the other.
You can also first try manually testing the known values from other devices:
https://github.com/MTK-bypass/exploits_collection/blob/master/default_config.json5
main.py --testmode --var_1 = <value>

main.py -t -v 1
This instruction has been tested from 1 to ff with no success.That's why I'm here to issue whether there are other solutions.

If all values from 0x01 to 0xFF have been tested, there is also the possibility that it uses a different payload_address (-a | --payload_address, or that it isn't vulnerable (which is unlikely)
Unfortunately without having a bootrom-dump you'll just have to keep trying.

If all values from 0x01 to 0xFF have been tested, there is also the possibility that it uses a different payload_address (-a | --payload_address), or that it isn't vulnerable (which is unlikely)
Unfortunately without having a bootrom-dump you'll just have to keep trying.

So now I need to test payload_address and var_1.What is the most appropriate growth value for payload_address (+=16)?What is the maximum value of VAR_1 (0x30)?

There really is no way to tell, look at the values, that have been used so far by other devices.
Maximum value for var_1 is 0xB4 (so far).
Also make sure, libusb is set up correctly. Do you have another MTK-device that you could use to verify the setup is working correctly?

There really is no way to tell, look at the values, that have been used so far by other devices.
Maximum value for var_1 is 0xB4 (so far).
Also make sure, libusb is set up correctly. Do you have another MTK-device that you could use to verify the setup is working correctly?

Do you mean try this paragraph ([Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: \xc1\xac\xb5\xbd\xcf\xb5\xcd\xb3\xc9\xcf\xb5\xc4\xc9\xe8\xb1\xb8\xc3\xbb\xd3\xd0\xb7\xa2\xbb\xd3\xd7\xf7\xd3\xc3\xa1\xa3\r\n\n')?
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error:Devices connected to the system are not functioning.'
This error message also works on my friend's computer.It is X7 Pro, the CPU model is MT6889
[2021-02-08 00:20:51.290245] Device hw code: 0x816
[2021-02-08 00:20:51.292241] Device hw sub code: 0x8a00
[2021-02-08 00:20:51.293237] Device hw version: 0xca00
[2021-02-08 00:20:51.294235] Device sw version: 0x0
[2021-02-08 00:20:51.295232] Device secure boot: True
[2021-02-08 00:20:51.296229] Device serial link authorization: False
[2021-02-08 00:20:51.297226] Device download agent authorization: True

MT6889 / 0x816 is also unsupported.
Do you have access to any supported device, to confirm your setup is correct?

MT6889 / 0x816 is also unsupported.
Do you have access to any supported device, to confirm your setup is correct?

Found an MT6755 and passed the test!
python3 main.py
[2021-02-11 16:27:36.492550] Waiting for bootrom
[2021-02-11 16:27:53.721814] Found port = COM3
[2021-02-11 16:27:53.752263] Device hw code: 0x326
[2021-02-11 16:27:53.753264] Device hw sub code: 0x8a00
[2021-02-11 16:27:53.754760] Device hw version: 0xcb00
[2021-02-11 16:27:53.755757] Device sw version: 0x1
[2021-02-11 16:27:53.756257] Device secure boot: True
[2021-02-11 16:27:53.757756] Device serial link authorization: True
[2021-02-11 16:27:53.757756] Device download agent authorization: True
[2021-02-11 16:27:53.759751] Disabling watchdog timer
[2021-02-11 16:27:53.760749] Disabling protection
[2021-02-11 16:27:53.797191] Protection disabled
The 0x326 configuration item does not specify var_1, but using --test mode will also fail!0xa is the default var_1! In test mode.Also won't appear ([Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error:Devices connected to the system are not functioning.') this kind of situation!
"0x326": { // mt6755
    "payload": "mt6755_payload.bin"
},

python3 main.py -t -v 8
[2021-02-11 16:31:49.878808] Waiting for bootrom
[2021-02-11 16:32:00.623838] Found port = COM3
[2021-02-11 16:32:00.723366] Device hw code: 0x326
[2021-02-11 16:32:00.724863] Device hw sub code: 0x8a00
[2021-02-11 16:32:00.727858] Device hw version: 0xcb00
[2021-02-11 16:32:00.728358] Device sw version: 0x1
[2021-02-11 16:32:00.728869] Device secure boot: True
[2021-02-11 16:32:00.729855] Device serial link authorization: True
[2021-02-11 16:32:00.730354] Device download agent authorization: True
[2021-02-11 16:32:00.731356] Disabling watchdog timer
[2021-02-11 16:32:00.733362] Disabling protection
[2021-02-11 16:32:17.784525] Test mode, payload_address..0x100a10 watchdog..0x10007000 var1..0x9
[2021-02-11 16:32:17.786011] Waiting for bootrom
[2021-02-11 16:32:32.011467] Found port = COM3
[2021-02-11 16:32:34.034898] Test mode, payload_address..0x100a10 watchdog..0x10007000 var1..0xa
[2021-02-11 16:32:34.036387] Waiting for bootrom
[2021-02-11 16:33:13.457209] Found port = COM3
[2021-02-11 16:33:20.396929] Test mode, payload_address..0x100a10 watchdog..0x10007000 var1..0xb
[2021-02-11 16:33:20.399420] Waiting for bootrom
[2021-02-11 16:33:21.475050] Found port = COM3
[2021-02-11 16:33:38.500275] Test mode, payload_address..0x100a10 watchdog..0x10007000 var1..0xc
[2021-02-11 16:33:38.501747] Waiting for bootrom

It looks like you changed the payload_address, 0x100A00 should be the default for 0x326
If this one doesn't give the error, I am not sure what else to try.
You could try on Linux with kernel patch.

Sorry, I did change the payload_address and did not correct it back.Seems to be the case with every new model I have ([Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error:Devices connected to the system are not functioning.')!I'm trying Linux with kernel patch!

Just a little info, the libusb-error you're getting when decoded with GBK reads:
连到系统上的设备没有发挥作用。
Google translates that to:
The equipment connected to the system is not functioning.
Is your OS in chinese, or is this message possibly coming from the device?

Just a little info, the libusb-error you're getting when decoded with GBK reads:
连到系统上的设备没有发挥作用。
Google translates that to:
The equipment connected to the system is not functioning.
Is your OS in chinese, or is this message possibly coming from the device?

Yes, my operating system is in Chinese!The device is Oppo's Realme, and the manufacturer does put some weird restrictions on it!

I see, let me know if using linux behaves differently.
If you want to use debian, I have uploaded patched kernel-packages ready to install here:
http://www.mediafire.com/folder/4aasetrfedl4t/kamakiri-kernels

I see, let me know if using linux behaves differently.
If you want to use debian, I have uploaded patched kernel-packages ready to install here:
http://www.mediafire.com/folder/4aasetrfedl4t/kamakiri-kernels

Libusb worked fine on my computer, and I'll retest it in a Linux environment later!If not successful, use other brands (millet) MT6853 or MT6853 for testing!

E:\python\bypass_utility>python3 main.py -t -v 8
[2021-02-12 18:49:04.495265] Waiting for bootrom
[2021-02-12 18:49:13.035204] Found port = COM3
[2021-02-12 18:49:13.057189] Device hw code: 0x326
[2021-02-12 18:49:13.059187] Device hw sub code: 0x8a00
[2021-02-12 18:49:13.059187] Device hw version: 0xcb00
[2021-02-12 18:49:13.060190] Device sw version: 0x1
[2021-02-12 18:49:13.060190] Device secure boot: True
[2021-02-12 18:49:13.060190] Device serial link authorization: True
[2021-02-12 18:49:13.060190] Device download agent authorization: True
[2021-02-12 18:49:13.061185] Disabling watchdog timer
[2021-02-12 18:49:13.061185] Disabling protection
[2021-02-12 18:49:30.099115] Test mode, payload_address..0x100a00 watchdog..0x10007000 var1..0x9
[2021-02-12 18:49:30.100088] Waiting for bootrom
[2021-02-12 18:49:48.013136] Found port = COM3
[2021-02-12 18:49:50.037017] Test mode, payload_address..0x100a00 watchdog..0x10007000 var1..0xa
[2021-02-12 18:49:50.038028] Waiting for bootrom
[2021-02-12 18:50:12.004511] Found port = COM3
[2021-02-12 18:50:13.019547] Found send_dword, dumping bootrom to bootrom_326.bin

Libusb worked fine on my computer, and I'll retest it in a Linux environment later!If not successful, use other brands (millet) MT6853 or MT6853 for testing!

If you find other devices with MT6853 that have security disabled, that would be perfect, since it could be used to dump brom and figure aut var_1

Libusb worked fine on my computer, and I'll retest it in a Linux environment later!If not successful, use other brands (millet) MT6853 or MT6853 for testing!

If you find other devices with MT6853 that have security disabled, that would be perfect, since it could be used to dump brom and figure aut var_1

In the case of the Debian test, it looks like Oppo is limiting something!
python3.9 main.py -t -v 0
[2021-02-12 21:21:43.308852] Waiting for device
[2021-02-12 21:21:47.427605] Found port = /dev/ttyACM0
[2021-02-12 21:21:47.471907] Device hw code: 0x996
[2021-02-12 21:21:47.472079] Device hw sub code: 0x8a00
[2021-02-12 21:21:47.472167] Device hw version: 0xca00
[2021-02-12 21:21:47.472241] Device sw version: 0x0
[2021-02-12 21:21:47.472289] Device secure boot: True
[2021-02-12 21:21:47.472356] Device serial link authorization: False
[2021-02-12 21:21:47.472440] Device download agent authorization: True
[2021-02-12 21:21:47.472527] Disabling watchdog timer
[2021-02-12 21:21:47.474130] Disabling protection
[Errno 32] Pipe error
[2021-02-12 21:21:48.505814] Test mode, testing 0x1...
[2021-02-12 21:21:48.506048] Waiting for device
[2021-02-12 21:21:56.256513] Found port = /dev/ttyACM0
[Errno 32] Pipe error
[2021-02-12 21:21:57.286097] Test mode, testing 0x2...
[2021-02-12 21:21:57.286516] Waiting for device
[2021-02-12 21:22:05.879545] Found port = /dev/ttyACM0
[Errno 32] Pipe error
[2021-02-12 21:22:06.935502] Test mode, testing 0x3...
[2021-02-12 21:22:06.935692] Waiting for device

Pipe error or Operation timed out is expected when var_1 is incorrect.
Kernel is patched?

Pipe error or Operation timed out is expected when var_1 is incorrect.
Kernel is patched?

If this error is normal!I'll keep testing!The kernel is patched!

Pipe error or Operation timed out is expected when var_1 is incorrect.
Kernel is patched?

I have to find another brand of MT6853 to try it out!

Very unfortunate.
Let's hope you find a device with security disabled so we can get a bootrom-dump.

I also encountered the error of “sending control message failed” on Xiaomi MT6853

I also encountered the error of “sending control message failed” on Xiaomi MT6853

RedMi Note9 5G？

I also encountered the error of “sending control message failed” on Xiaomi MT6853

RedMi Note9 5G？

yes

I also encountered the error of “sending control message failed” on Xiaomi MT6853

RedMi Note9 5G？

yes

This is embarrassing! I was going to buy it and try it on!

I have a Samsung A32 5G, same chip, no idea how to test this but I'm willing!!! (Bootloader locked 5G)

Found this which might be helpful?
https://androidfilehost.com/?fid=17248734326145723274
Here's the scatter I found

I would be interesting in helping with this too. I'm now the proud owner of a bricked Redmi Note 9T (which is the global version of the Redmi Note 9 5G). I've had a go with the tool, here's my output from test mode, which is basically the same as other attempts:
python main.py -t -v 0
[2021-05-24 12:08:58.138556] Waiting for device
[2021-05-24 12:09:02.089725] Found port = COM3
[2021-05-24 12:09:02.152197] Device hw code: 0x996
[2021-05-24 12:09:02.167805] Device hw sub code: 0x8a00
[2021-05-24 12:09:02.167805] Device hw version: 0xca00
[2021-05-24 12:09:02.167805] Device sw version: 0x0
[2021-05-24 12:09:02.167805] Device secure boot: True
[2021-05-24 12:09:02.167805] Device serial link authorization: True
[2021-05-24 12:09:02.183429] Device download agent authorization: True
[2021-05-24 12:09:02.183429] Disabling watchdog timer
[2021-05-24 12:09:02.183429] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:03.277516] Test mode, testing 0x1...
[2021-05-24 12:09:03.277516] Waiting for device
[2021-05-24 12:09:16.048212] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:16.335811] Test mode, testing 0x2...
[2021-05-24 12:09:16.335811] Waiting for device
[2021-05-24 12:09:18.060070] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:19.143053] Test mode, testing 0x3...
[2021-05-24 12:09:19.143053] Waiting for device
[2021-05-24 12:09:26.317893] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:27.393683] Test mode, testing 0x4...
[2021-05-24 12:09:27.393683] Waiting for device
[2021-05-24 12:09:34.807363] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:35.932830] Test mode, testing 0x5...
[2021-05-24 12:09:35.932830] Waiting for device
Looks like the "[Errno None]" is the windows equivalent of the "[Errno 32] Pipe Error" which you get on Linux. I tried your kernel patched version of FireISO too @chaosmaster and it's basically the same output (but with Errno 32s instead). I'm pretty sure my libusb is set up properly.
I could run through the full set of 0x01 to 0xFF to try and find var_1 (which in test mode should then dump the brom?), but it looks like that's already been done by @sundaqiang and didn't work?
@GarnetSunset, I don't think the ROM and scatter files help as the brom is written into the firmware of the MT6853 chip itself. It looks like the only solution at the moment is to find someone with a phone that isn't already locked down. Which I think means when the tool is run we want to see "Device serial link authorization: False and Device download agent authorization: False", but can someone confirm please?

Yes, having a device with security disabled would be ideal to dump the bootrom.
At this point it's hard to say if the device is even vulnerable or not.

I would be interesting in helping with this too. I'm now the proud owner of a bricked Redmi Note 9T (which is the global version of the Redmi Note 9 5G). I've had a go with the tool, here's my output from test mode, which is basically the same as other attempts:
python main.py -t -v 0
[2021-05-24 12:08:58.138556] Waiting for device
[2021-05-24 12:09:02.089725] Found port = COM3
[2021-05-24 12:09:02.152197] Device hw code: 0x996
[2021-05-24 12:09:02.167805] Device hw sub code: 0x8a00
[2021-05-24 12:09:02.167805] Device hw version: 0xca00
[2021-05-24 12:09:02.167805] Device sw version: 0x0
[2021-05-24 12:09:02.167805] Device secure boot: True
[2021-05-24 12:09:02.167805] Device serial link authorization: True
[2021-05-24 12:09:02.183429] Device download agent authorization: True
[2021-05-24 12:09:02.183429] Disabling watchdog timer
[2021-05-24 12:09:02.183429] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:03.277516] Test mode, testing 0x1...
[2021-05-24 12:09:03.277516] Waiting for device
[2021-05-24 12:09:16.048212] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:16.335811] Test mode, testing 0x2...
[2021-05-24 12:09:16.335811] Waiting for device
[2021-05-24 12:09:18.060070] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:19.143053] Test mode, testing 0x3...
[2021-05-24 12:09:19.143053] Waiting for device
[2021-05-24 12:09:26.317893] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:27.393683] Test mode, testing 0x4...
[2021-05-24 12:09:27.393683] Waiting for device
[2021-05-24 12:09:34.807363] Found port = COM3
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.\r\n\n'
[2021-05-24 12:09:35.932830] Test mode, testing 0x5...
[2021-05-24 12:09:35.932830] Waiting for device
Looks like the "[Errno None]" is the windows equivalent of the "[Errno 32] Pipe Error" which you get on Linux. I tried your kernel patched version of FireISO too @chaosmaster and it's basically the same output (but with Errno 32s instead). I'm pretty sure my libusb is set up properly.
I could run through the full set of 0x01 to 0xFF to try and find var_1 (which in test mode should then dump the brom?), but it looks like that's already been done by @sundaqiang and didn't work?
@GarnetSunset, I don't think the ROM and scatter files help as the brom is written into the firmware of the MT6853 chip itself. It looks like the only solution at the moment is to find someone with a phone that isn't already locked down. Which I think means when the tool is run we want to see "Device serial link authorization: False and Device download agent authorization: False", but can someone confirm please?

Same situation，my device is realme Q2  mt6853.

Hey there! I have a rooted/bootloader unlocked A32 5G, anything I can do to help?

@GarnetSunset unfortunately that may not be enough as it won't get us the boot rom off the MT6853 chip. What would be of interest is to find out if Samsung locked down the chip or not.
Have a go at installing/running the tool, and paste the output here on the issue. What we're looking for is someone who has:
Device serial link authorization: False
Device download agent authorization: False
Instructions are on the front page: https://github.com/MTK-bypass/bypass_utility
There's also a write-up on the xda site: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/

I've attached the DA file for this chip here (it's for MT6853 and MT6873). Not sure it's of use for this specific exploit, but will verify us through Secure Boot.
MTK_AllInOne_DA.zip

I can't find any info on MT6835, also please provide a log of the utility

I have Realme X7 5G stuck in bootloop. Right bottom it says "RECOVERY MODE" and it continuously switches OFF and switches ON. Couldn't bypass BROM in any ways. SP tool says wrong Scatter everytime. Please please help anyone..

It is now confirmed, that the vulnerability was fixed in MT6853 unfortunately: chaosmaster/bypass_payloads/issues/7

I log in to the original download software and can use realme Q2 (MT6583),anything I can do to help?

I log in to the original download software and can use realme Q2 (MT6583),anything I can do to help?

download:
https://drive.google.com/file/d/1ksZBNZJVJDUOAsSv-aafeCbnAzVaXPVn/view?usp=sharing
Note: The account may expire or be cancelled soon, please try to detect usb data/dump the certificate as soon as possible.

@GarnetSunset unfortunately that may not be enough as it won't get us the boot rom off the MT6853 chip. What would be of interest is to find out if Samsung locked down the chip or not.
Have a go at installing/running the tool, and paste the output here on the issue. What we're looking for is someone who has:
Device serial link authorization: False
Device download agent authorization: False
Instructions are on the front page: https://github.com/MTK-bypass/bypass_utility
There's also a write-up on the xda site: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/

I log in to the original download software and can use realme Q2 (MT6583),anything I can do to help?
download:
https://drive.google.com/file/d/1ksZBNZJVJDUOAsSv-aafeCbnAzVaXPVn/view?usp=sharing
Note: The account may expire or be cancelled soon, please try to detect usb data/dump the certificate as soon as possible.

@GarnetSunset unfortunately that may not be enough as it won't get us the boot rom off the MT6853 chip. What would be of interest is to find out if Samsung locked down the chip or not.
Have a go at installing/running the tool, and paste the output here on the issue. What we're looking for is someone who has:
Device serial link authorization: False
Device download agent authorization: False
Instructions are on the front page: https://github.com/MTK-bypass/bypass_utility
There's also a write-up on the xda site: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/

I log in to the original download software and can use realme Q2 (MT6583),anything I can do to help?
download:
https://drive.google.com/file/d/1ksZBNZJVJDUOAsSv-aafeCbnAzVaXPVn/view?usp=sharing
Note: The account may expire or be cancelled soon, please try to detect usb data/dump the certificate as soon as possible.

This is a Wireshark usb flashing dump.
https://drive.google.com/file/d/1tJyypd0L6yGFTj1JCGPR6RKu6oe8KgsF/view?usp=sharing

MT6853 is now supported, please try.

MT6853  - SM-A32 5G
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
DAXFlash
DAXFlash - [LIB]: Error on sending parameter: Read parttbl failed (0xc0040007)
xflashext
xflashext - [LIB]: Error on writing seccfg config to flash.

@chaosmaster

Hi,
I'm getting "Status 7024" on "Device hw code: 0x996".
This is Vivo V21 5g on MT6853.
Attached the log. Are you able to help?
bypass_utility.log

I have a MT6833. I dunno if bootrom protection(sla and daa) is there at all. Can someone tell me how to verify the same . I was able to install patched magisk boot image does that means SLA and DAA are disabled ?

it's not going. can anybody help? thanks
[2024-11-24 17:54:25.201723] Found device in preloader mode, trying to crash...

[2024-11-24 17:54:25.206758] status is 7024

[2024-11-24 17:54:25.211780] Waiting for device
[2024-11-24 17:54:27.589873] Found port = COM4

[2024-11-24 17:54:27.873502] Device hw code: 0x717
[2024-11-24 17:54:27.873502] Device hw sub code: 0x8a00
[2024-11-24 17:54:27.873502] Device hw version: 0xca01
[2024-11-24 17:54:27.873502] Device sw version: 0x200
[2024-11-24 17:54:27.887019] Device secure boot: True
[2024-11-24 17:54:27.887019] Device serial link authorization: False
[2024-11-24 17:54:27.887019] Device download agent authorization: True

it's a mt6761 chip. any ideas what this could mean?


Doesn't save when using git account

After initial commit if u close or get to previous page, no changes are being saved. It is a very bad experience. Add some temporary file or smth else. Or just any alert message.

Not sure what you mean, can you please clarify: What are the exact steps to reproduce the problem? What is the expected and what is the actual output?

@alderg Just login only via GitHub account.  Problem occurs when you have done some actions and then you go to one page back. All changes are reset without ability to restore them. What I want is that this gonna be temporary saved without doing actual commit or alert message saying that all changes will be reset if you will accidentally close tab. This bug doesn't occur when you're logged in via Google account, cause it is saving all changes.

Thanks for the report, this will be fixed in the next release.


exception on incident-creation

I get an exception when i try to add an incident:

SQLSTATE[23000]: Integrity constraint violation: 19 components.status may not be NULL (SQL: update "components" set "status" = , "updated_at" = 2015-01-27 16:05:42 where "id" = 1)

Open: /var/www/status/vendor/laravel/framework/src/Illuminate/Database/Connection.php
		}

		// If an exception occurs when attempting to run a query, we'll format the error
		// message to include the bindings with SQL, which will make this exception a
		// lot more helpful to the developer instead of just the database's errors.
		catch (\Exception $e)
		{
			throw new QueryException(
				$query, $this->prepareBindings($bindings), $e
			);

POST data:
template
incident	Array ( [name] => foo [status] => 4 [component_id] => 1 [message] => bar [user_id] => 1 )

The incident is added nontheless...

Looks like you need to run gulp because you should be seeing a component status picker there too.

i might have to write a how-to-keep-up2date... :dancer:
thx


Fix issue #21

We try to fix the problem presented in #21

[x] Fix stripes on central-lateral sphere of the demo
[x] Fix checkered pattern in the central-lower sphere of the demo
[x] Solve bas superposition of spheres problem

A crude solution might be to simply clamp the value of the z component of the point between -1 and 1. The resulting output when mapping the v coordinate as in the previous example will be

This comment was first issued in issue #20

The demo animation command outputs the following video
https://user-images.githubusercontent.com/79973069/120009986-e627a400-bfdc-11eb-8264-b50cc161a760.mp4
from which we can see that the central-lateral sphere has now the intended stripes pattern on it, but this is still not the case fot the lower one and that there are still wrong superpositions, as seen in this frame

Interstingly enough the above mentioned issues of strange behaviour of chechered patterns on spheres and wrong superposition  happens more evidently for small spheres in the scene, and it involves an alteration of the u coordinate, as can be seen in these three videos
https://user-images.githubusercontent.com/79973069/120029591-981f9a00-bff6-11eb-977a-1f4cdfb6530b.mp4
https://user-images.githubusercontent.com/79973069/120029598-98b83080-bff6-11eb-9a30-7ebdb32ecb0d.mp4
https://user-images.githubusercontent.com/79973069/120029594-98b83080-bff6-11eb-8fd9-3a816a16cb7e.mp4
Notice how the "moon" in the last video hast the stripes representing the u coordinates far wider in angle than their counterparts in the "planet", even if some distortion in the planet is visible when the boundaries are near the front of the camera

We found mistake in our implementation for ray_intersect(::Ray, ::Sphere), once fixed it resulted in sensible visual output. To be noted a change in the UV mapping of spheres. We then close issue #21 since bugs have been solved.


bash_it.sh: Require interactive shell

Previously, a fix was added for bad behavior when bash-it printed text
to the console in conjunction with protocols like SCP, as commit
83c44fac "template/profile: Require interactive shell".
It did work for those users who replace their original ~/.bash_profile
file with the one provided by bash-it, but not for those who merely
append a bash-it call to their existing ~/.bash_profile file.
Fix the behavior for the latter case, too.
This serves as a preparation for #1501

Apparently, tests are run in non-interactive mode, so they will need to be adapted or the business logic for interactive mode moved to a separate script so it can be tested.

Thanks for providing this fix - can you please take a look at the broken test cases?

Greetings All,
Question: Is it possible that, even in non-interactive mode, the user may be trying to do something that requires (at least parts of) bash-it to initialize?
I'm thinking something along the lines of expecting an alias or plugin to be configured?  say, pyenv or somesuch?
Just wondering if this is something to be concerned about what with the user delegating so much of their startup routine to bash-it (per design).
NOTE: This PR seems to keep par with the current pattern introduced Here, but with the user no-longer having direct control over it, I thought it might be worth discussing.
Wondering if we might find something like this useful:
~/.bash_profile
# Hide bash-it output if shell is non-interactive
case $- in
	*i*) source "$BASH_IT"/bash_it.sh;;
	  *) source "$BASH_IT"/bash_it.sh 1>/dev/null 2>&1;;
esac

I tested this locally with a few shell scripts and it worked as expected.
Thoughts?
-DF

Re https://github.com/Bash-it/bash-it/pull/1533#issuecomment-606743441

Just wondering if this is something to be concerned about what with the user delegating so much of their startup routine to bash-it (per design).

IMHO, that's something people shouldn't do.

Wondering if we might find something like this useful:
# Hide bash-it output if shell is non-interactive

I tested this locally with a few shell scripts and it worked as expected.

I found that SCP transfers were slow to start in such a setting because of all the time it takes to run bash_it.sh. IIRC, tab completion for scp on the client side was slowed down, too.
I lean towards a different approach where there is an external bash_it.sh which skips in non-interactive mode and an internal bash_it.sh which runs regardless of whether the shell is interactive or not.
The matters seem a bit more complex than initially thought, we'll probably need additional automated tests for a swift discussion. Next time, I will look into testing with bats.

Thanks for discussing this - the SCP use case is pretty important, true. We should make sure that whatever we does not result in longer init times when doing things like SSH, SCP, etc.
I'm not sure I understand the external/internal approach - can you please provide some more details on that, @rico-chet?

With the current PR, we have the issues that:

Tests fail in CI due to non-interactive shell being used.
Users who call from a custom ~/.bash_profile → bash_it.sh in non-interactive shells and rely on e.g. plugins having effect will find their things broken.

The approach is to have:

public script (for external use, let's stick to bash_it.sh) preventing non-interactive shells from calling the:
private script (for internal use, let's call it bash_it_private.sh) which runs the business logic. It can be called directly to run tests from non-interactive CI and by users who want to use bash-it plugins in non-interactive mode.

Then, when printing is added to bash-it, users in 2.) would need to switch from sourcing bash_it.sh to bash_it_private.sh &>/dev/null, that'd be a breaking change for them. Common users would not be affected.
Alternatively, we could add an environment variable, e.g. BASH_IT_ENABLE_NON_INTERACTIVE (default to false) or BASH_IT_INTERACTIVE_ONLY (default to true) that would switch between the two modes.

I would lean toward keeping one access point for users, ie. bash-it.sh.
I think there's value in supporting a concept of "interactive-only components" and could see configuration going one of two ways:

Always-Initiated Components
Interactive-Only Components

or

Always-Initiated Components
Non-Interactive-Only Components
Interactive-Only Components

The 2nd option offers more flexibility, but the 1st option most-likely matches real-world usage.
Themes and Completions seem to clearly fit into the "Interactive-Only Components" category.
Plugins and Aliases may be a bit more nuanced.  These components could potentially tag themselves (using meta-data) as interactive or non by default.
I think the user should have the ability to override the default on a per-component basis.  Maybe something like
BASH_IT_INITIATE_PLUGINS_ALWAYS=plugin1,plugin2...

This could give the user the ability to orchestrate both their interactive and non-interactive sessions.
The user could get creative in their bash_profile and add ssh_detection code and then control exactly which components should be initiated for ssh/scp sessions.
NOTE: Components are still expected to be enabled via bash-it enable ... so the overrides would only apply to enabled components (silently ignored for others).
Additionally, I think my idea of routing all output to /dev/null in non-interactive mode still has merit. Although we may want to place such logic behind a configuration option.
-DF

I really like this idea of plugins having the option of being always on vs interactive only.
However, I kinda see this PR as a bug fix, since it sounds like this hasn't been thought out previously. I know I've had to wrap my bash-it includes with this clause and has annoyed other people I've gotten to adopt bash-it. In that vein, I think it'd be great if this PR could be merged (once travis is happy) and further discussion moved to an issue maybe? I hope I don't come off like a jerk, I'm just trying to keep things moving :-)

@rico-chet ping

To make Travis happy, we would need to figure out how to run the tests in CI pretending the shell is interactive, because otherwise they just fail. Shouldn't be hard but might have side effects.
A new test would be handy which proves that SCP scenarios work fine. I made some progress running SSH server in a docker container but failed to get the test red.
And the question of how we deal with existing expectations isn't really solved. Due to lack of knowledge of bash-it internals I cannot come up with a simple solution yet.

For now, I found that it's complicated on the bash side already: run_startup_files() is full of ifs, ifdefs and flags, so no wonder I cannot get the SCP scenario test red. FYI, SSH_SOURCE_BASHRC is set in Debian and Fedora.
A quick attempt to make existing tests green wasn't successful, so it will take a while for me to get it done, if at all.
If anybody's interested to pick it up, feel free to do so. Since personally, I'm not affected by the issue and am spending my spare time on other activities recently, it's not going to be done soon otherwise.

I'm in the same boat. If I find spare time or need a break from work, I might copy your work to a branch and see what I can pull off.

If I may add my $0.02, I think that Bash It isn't the right place for deciding if it should load itself whether interactive or not. This feels like something that should be handled in .bashrc by the user. I would be surprised to find anyone relying on something loaded by Bash It in non-interactive scripts, except possibly manipulating $PATH in their custom.bash. IMO, I don't think Bash It should be loaded in .bash_profile at all, but rather in .bashrc.


Some small style tweaks to make pandoc working

I was trying to generate pdf handbooks for kubernetes from official documents using pandoc. There were some errors preventing pandoc doing its work.
One of them is because some files are in the dos format with extra ^M. I fixed it with one commit.
In order to improve the quality of the result pdf files, I also make some small changes to tweak the header level and table width. It's in the other commit.
I could create another PR for the pandoc environment if someone finds it useful.

This change is

Can you verify that these changes don't have any negative effect on how the documentation renders?

For the first commit it just removed unnecessary ^M which would not change the document render at all.
For the second commit I make some small changes to the content like modifying header level and fixing a broken link for the image. I think they're good improvements.

Please rebase and resolve all merge conflicts and I'll check it via automatic staging.

rebased

I spot-checked most of the files. Looks okay. However, many of these files are going to be touched in 1.4, so this PR is going to cause a large number of merge conflicts at launch.

Post 1.4 launch, this has merge conflicts that need to be resolved.

I'll do a rebase soon.

rebased


Compatibility with JupyterLab >2.0

Just tried installing this extension with JupyterLab 2.1.4 and got the following conflicts:
ValueError: The extension "jupyterlab-bokeh-server" does not yet support the current version of JupyterLab.

Conflicting Dependencies:
JupyterLab              Extension      Package
>=2.1.2 <2.2.0          >=1.0.0-alpha.6 <2.0.0@jupyterlab/application
>=2.1.1 <2.2.0          >=1.0.0-alpha.6 <2.0.0@jupyterlab/apputils
>=4.1.0 <4.2.0          3.0.0-alpha.6  @jupyterlab/coreutils

I have the same problem with JupyterLab 2.1.5
Any recommendation to solve this issue?

Any recommendation to solve this issue?

I'm running into the same issue unfortunately with jupyter lab 3.1.11


[PROPOSAL] Clarify Issue Types and "Last Call for Comments"

What are you proposing?
We have Feature Requests and Feature Proposals documented in CONTRIBUTING.md, but we also have PROPOSALS, RFCs, FEATURE BRIEFs, BUGS.

Could we standardize on the types of issues?

BUG: an unexpected result from some operation in OpenSearch that SEEMS like a bug (meaning something broken)
Feature Request: I have an idea for new functionality, but don't have a solution. I'd like to collaborate on one or just put it out there for someone else to build.
Collapse these into "Feature Proposal" (clearest definition I see).

RFC: Request for Comments. - I have an idea for some implementation of a problem I have, but really want to hear from the community before doing too much.
PROPOSAL: is this different than RFC?
Feature Proposal: I have an idea for a feature and maybe a solution. I don't know necessarily how to build this and want to understand what others think (is this too subtle a difference from an RFC? Should this be rolled up?)
* Are there others?

The GH issue should be used for commenting/discussion of the initial design. The forum should be used for long lived discussions/questions of the feature.
For an RFC/Proposal/Feature Proposal, let's standardize on addressing how long the issue will stay open (could be a field in the issue template and could vary on a case by case basis) and post a reminder that the issue will be closed at least a week ahead?

What users have asked for this feature?
@mashah - "Yes, we’re not sure both on where and how to get involved. It would be great 1/ we could put the discussion and comments for RFCs in one place (right now it seems to be distributed between forums and GitHub). 2/ Have a protocol for agreeing on and closing RFCs. A simple “last call for comments” and aiming to “close on date XX” would be helpful. 3/ perhaps have a place where we know the experimental items are ? (Again, I might have missed it.)"
https://opensearch.slack.com/archives/C04UM4D6XN2/p1685306611855109

@macohen I think the issue types are pretty clear, what do you want to accomplish with standardizing them?  It might be easier to see this with a PR to modify the issue template(s) that you'd like to see changed.

@peternied what I think I realized here is that these issue templates are pretty good and they have been updated since one of the repos I work in was created; I may have missed something, but it might be great to create issues in every repo when any .github files that could apply everywhere are updated. It's always up to the admins if the change is required (like the recently completed maintainer cleanup). If it's not required the repo maintainers can decide whether to take the change or not and close the issue.

@macohen When you perform the 'sync', would you mind writing that process up and creating a PR in this repo?
There are two issues around automating these processes, one [1] created by @elfisher to synchronize the issue templates and another issue for sync'ing workflow files [2].

[1] https://github.com/opensearch-project/.github/issues/9
[2] https://github.com/opensearch-project/.github/issues/113

@macohen the original proposal seems relatively complete, how would you like to use this issue or would you rather close it out?

Closing it out. It seems the answer is to create a process to sync .github project changes across the org. I'll track the other issues regarding automation. Thanks.


Fix link from https://lea.verou.me/2012/10/easy-color-contrast-ratios/ ?

I noticed that on https://lea.verou.me/2012/10/easy-color-contrast-ratios/ there is still a broken link to http://leaverou.github.com/contrast-ratio/ (this results in 404). I think it should now point here to color.js, no?
Love this tool, wow!

Note: The broken link is "my own tool" (the pull requests link was already updated to point to https://github.com/LeaVerou/contrast-ratio)

Fixed, thanks!
Please note contrast-ratio doesn't use color.js yet (needs https://github.com/LeaVerou/color.js/issues/230 to be fixed first)


HOW TO GET LINKS

How to generate links like This  and this
@PurpShell  @pokearaujo @andresayac

How to generate links like This  and this
@PurpShell  @pokearaujo @andresayac

can you explain more

How to generate links like This  and this
@PurpShell  @pokearaujo @andresayac

can you explain more

How can I generate link like :- https://whiskeysockets.github.io/ and https://whiskeysockets.github.io/Baileys


chore: release 2.2.0

:robot: I have created a release beep boop
2.2.0 (2023-09-12)
Features

move to bun (9d9a95e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/infodusha/define-html/releases/tag/v2.2.0 :sunflower:


Add cylinder shape

Objective
Adds a cylinder shape. Fixes #2282.
Solution

I added a custom cylinder shape, taken from here with permission from @rparrett.
I also added the cylinder shape to the 3d_shapes example scene.

Changelog

Added cylinder shape

Co-Authored-By: Rob Parrett<EMAIL_ADDRESS>Co-Authored-By: davidhof<EMAIL_ADDRESS>

Lgtm!

Treating @JMS55's "LGTM" comment as an approval.

This also partially addresses #3456.

bors r+


Update README.md

Coverage remained the same at 81.887% when pulling 2ded1e6f10a2544ac93402c4124e2644e7d4d7f0 on rotembr-patch-6 into 62cdd1e9ead80d10f0fac5f1113670834bd1c4f9 on development.


Log when a message is updated (edited) or deleted.

Added logging for when a user updates or deletes a message. I feel like there could be a better way to write the actual event handler, rather than having to do something like:
client.on("messageDelete", (message) => {
    events.messageDelete.run(message);
});

every time you want to add a new event... Suggestions welcome.

There are other ways to setup the event handler but I think this way is the best because of how explicit it is. Other ways would not be so evident.


New feature: Wide Equations?

Hi,
first, thanks for the class, I really like it !
Do you think it would be possible / desirable to have wide environments for things like equations ?
It would behave like wide figures, tables, but with equations.
Thanks,
Rémy

See #52 :)

Oh, well, perfect. I'll see if I can add some doc about this in the .tex :)


Upgrade to Elm 0.17

This includes forking the new compiler and core.

Regarding elm 0.17, is it necessary to fork the compiler or core anymore?
Could it be enough to have a render port that yielded a Json.Encode.Value description of the render, along with an event port to receive the event stream from react?  If each event handler were replaced by a routing ID outbound and saved in a parallel data structure, then it seems that one might even be able to remove nativeEventHandler entirely and let a javascript shim do all non-elm work entirely on the other side of the port?

This is awesome work.
I'm new to elm and I have been playing with your 0.17 fork.  I'm curious if you have thought/found a way for equivalent functionality to Http.App.map for NativeUI since elm has moved away from signals.

Thanks for trying it out. I added NativeUi.map to my fork and updated the example.

Haha that was fast.  Thanks a lot!

Just so you know, I think it's fantastic that you are trying to solve some of these problems!
I myself am leaning a little towards maybe waiting for 0.18 at this point, since it should bring custom program types to the table. But I am definitely interested in seeing how you are dealing with this stuff. :)

Hey thanks for writing.  It's not really intended for widespread use or a
replacement for deeper work on elm.
Ultimately, I wanted to do an experiment to push ports as far as possible
without writing native code or modifying the compiler or generated code.
Clearly it'll be nicer to have program be more flexible.  Since elm
development is mostly driven by use cases, I was also hoping to contribute
a concrete example to the general ethos.
On Tue, Oct 4, 2016 at 12:49 PM, Ossi Hanhinen<EMAIL_ADDRESS>wrote:

Just so you know, I think it's fantastic that you are trying to solve some
of these problems!
I myself am leaning a little towards maybe waiting for 0.18 at this point,
since it should bring custom program types to the table. But I am
definitely interested in seeing how you are dealing with this stuff. :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elm-native-ui/elm-native-ui/issues/39#issuecomment-251493041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOEEDC6qibgpHYnrPRCd0ZU_4577AWAks5qwq2vgaJpZM4Id3pU
.

I started working on this, it totally works!

Woo, awesome @lukewestby! I need to try this out for myself. :)

This is now done, as of #41. :tada:


Enforce LF-only line endings in git

Having some files using CRLF makes things extremely messy when
using tarballs on Linux, as the git repository gets automatically
converted, but the tarball stores the original line ending,
so the two do not match anymore and importing new releases fails.
Enforce that LF-only line endings get committed to the repository,
and add instructions for Windows developers on how to configure
their local git client to checkout in CRLF, so that CRLF never
propagate to the repository but remain only in local checkouts.

Thank you for your contribution! We will review the pull request and get back to you soon.

I'm not a git guru, I checked the doc after you created this PR. So correct me if I'm wrong.
I guess you want to do this:

Every file ends with lf in Git index.
Windows users still get crlf when checkout.

But this PR does not achieve the above target?

The bat files end with crlf in https://api.github.com/repos/azure/azure-cli/tarball/dev

eof enforce line ending conversion when checkout, Windows user are affected.

This attribute marks a path to use a specific line-ending style in the working tree when it is checked out
Set to string value "crlf"
This setting converts the file’s line endings in the working directory to crlf when the file is checked out.
Set to string value "lf"
This setting uses the same line endings in the working directory as in the index when the file is checked out.
-- https://www.git-scm.com/docs/gitattributes#_eol

I'm using Windows and have core.autocrlf=true setting. Here is the test result.
Before:
git ls-files --eol src/azure-cli/az.bat
i/lf    w/crlf  attr/text=auto eol=crlf src/azure-cli/az.bat
git ls-files --eol .github/policies/resourceManagement.yml
i/crlf  w/crlf  attr/text=auto          .github/policies/resourceManagement.yml
git ls-files --eol .\src\azure-cli\setup.py
i/lf    w/crlf  attr/text=auto          src/azure-cli/setup.py

After checkout to this pr and run git rm -rf --cached . && git reset --hard HEAD
git ls-files --eol src/azure-cli/az.bat
i/lf    w/lf    attr/text=auto eol=lf   src/azure-cli/az.bat
git ls-files --eol .github/policies/resourceManagement.yml
i/lf    w/lf    attr/text=auto eol=lf   .github/policies/resourceManagement.yml
git ls-files --eol .\src\azure-cli\setup.py
i/lf    w/lf    attr/text=auto eol=lf   src/azure-cli/setup.py

The above files are converted to lf.
I prefer to keep the original settings. It makes sense to keep bat files ending with crlf.

I don’t know which tarball you’re using. The bat files end with crlf in https://api.github.com/repos/azure/azure-cli/tarball/dev

The ones from https://github.com/Azure/azure-cli/releases and yes having any files with crlf in release tarballs is just broken. That can be allowed to happen if and only if a project is to be used exclusively on Windows, which is not the case here.

eof enforce line ending conversion when checkout, Windows user are affected.

This attribute marks a path to use a specific line-ending style in the working tree when it is checked out
Set to string value "crlf"
This setting converts the file’s line endings in the working directory to crlf when the file is checked out.
Set to string value "lf"
This setting uses the same line endings in the working directory as in the index when the file is checked out.
-- https://www.git-scm.com/docs/gitattributes#_eol

I'm using Windows and have core.autocrlf=true setting. Here is the test result. Before:

Which version of git is that? Also can you try with a fresh clone after changing the global setting? Honestly I don't know why git doesn't make this the default on WIndows, anything else is just broken. I was sure that was the right combination to achieve crlf on checkout on Windows, but maybe there's some other knob to turn?

The above files are converted to lf. I’m open to change resourceManagement.yml to lf, but I prefer to keep the original eol settings. It makes sense to keep bat files ending with crlf.

No files can have crlf, otherwise things are just broken and we need to fork the repository and re-create the tarballs from scratch on Linux, which is a gigantic pain.

Maybe the issue is the gitattributes? Perhaps another approach would be to drop that bit, convert once all files, and then add a CI test that enforces no clrf anywhere?

Find similar statement from GitHub doc:

text eol=lf Git will always convert line endings to LF on checkout. You should use this for files that must keep LF endings, even on Windows.  -- https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings

eol=lf enforces lF on Windows, so this change breaks bat files on Windows.

Currently, only bat, sln and resourceManagement.yml contains CRLF.
If you want to make bat file end with LF, removing *.bat eol=crlf in .gitattributes meets your needs.
But bat is a Windows only file, I'd like to keep it using CRLF. May I know how bat files affect your workflow on Linux?
❯ find . -not -type d -exec file "{}" ";" | grep CRLF
./src/azure-cli/az.bat: DOS batch file, ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/autoscale/build_python.bat: ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/autoscale/grun.bat: DOS batch file, ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/autoscale/run_test.bat: ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/metric_alert/build_python.bat: ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/metric_alert/grun.bat: DOS batch file, ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/monitor/grammar/metric_alert/run_test.bat: ASCII text, with CRLF line terminators
./src/azure-cli/azure/cli/command_modules/batch/tests/latest/generate_full_cli_help.bat: ASCII text, with CRLF line terminators
./azure-cli2017.sln: Unicode text, UTF-8 (with BOM) text, with CRLF line terminators
./doc/sphinx/make.bat: DOS batch file, ASCII text, with CRLF line terminators
./doc/sphinx/sphinx.sln: Unicode text, UTF-8 (with BOM) text, with CRLF line terminators
./scripts/install_full.bat: ASCII text, with CRLF line terminators
./scripts/ci/dependency_check.bat: ASCII text, with CRLF line terminators
./.github/policies/resourceManagement.yml: Unicode text, UTF-8 text, with very long lines (352), with CRLF line terminators
./azure-cli.sln: Unicode text, UTF-8 (with BOM) text, with CRLF line terminators
./build_scripts/windows/azure-cli.sln: Unicode text, UTF-8 (with BOM) text, with CRLF line terminators

But bat is a Windows only file, I'd like to keep it using CRLF. May I know how bat files affect your workflow on Linux?

As mentioned in the PR description:

Having some files using CRLF makes things extremely messy when
using tarballs on Linux, as the git repository gets automatically
converted, but the tarball stores the original line ending,
so the two do not match anymore and importing new releases fails.

Having any file checked in with crlf in git, for projects that are not exclusively and only Windows-specific, is just broken.

Ok I've dropped the settings in .gitattributes, and instead I've added a CI job and converted all the files. This should allow core.autocrlf=true to do its job, and stop any crlf from being merged. Can anybody running on Windows check that it works as expected please?

The git checkout content on Linux is identical to tarball, I don't see your point.

The git checkout content on Linux is identical to tarball, I don't see your point.

No, it is not when exported and reimported, because the line endings are changed.

sln file is exclusive to visual studio, which is not available on Linux, keep CRLF looks good to me.

No, it does not, checking CRLF files in git is broken and breaks many workflows. They can be added automatically on checkouts as documented.


Can't run more than one instance of mochad_dispatch

When you try to start another instance of mochad_dipsatch it dies with the error "Unable to lock on the pidfile".  This is due to the hardcoded pidfile /tmp/mochad_dispatch.pid

Fixed in commit dd7445a1dfa6d706cfc5a76088a4292526560472


Feature request: drag items by handle

Feature requests
Overview
An option to add a handle to each row to start dragging. Instead of start dragging by clicking anywhere in the row add a new element and only start dragging by clicking that handle.
Purpose / Reason
In mobile devices sometimes scrolling over a tree (with the finger) is interpreted as a drag-and-drop action and the tree is messed.
Any implementation ideas?
It would be nice if in the render function the handle could be defined.
Reference information
I have read the project is using react-dnd for drag and drop functionality. Here is an example of react-dnd
https://codesandbox.io/s/github/react-dnd/react-dnd/tree/gh-pages/examples_hooks_js/05-customize/handles-and-previews (it would be the example with the green box)
Another project that supports this is: dnd-kit
https://5fc05e08a4a65d0021ae0bf2-bphcuqqqih.chromatic.com/?path=/docs/examples-tree-sortable--all-features
In this example the handle can is more evident.

is there any updates about this issue? i have the same problem

i solved it by the following
add new boolean variable
const [dragHandler,setDragHandler]=useState(false)
canDrag (node)=>{
if(dragHandler) return true
}
....
render(node,{.....})=>{
return(<CustomNode. ...... handleDrag={e=>setDragHandler(e) } )/>)
}
inside the customNode   i added IconButton
<IconButton
draggable='true'
onDragStart={()=>props.handleDrag(true)}
onDragEnd={()=>props.handleDrag(false)}
..../>

@minop1205 is this a feature you are considering to introduce in the future? If not, do you have a recommended workaround to get custom drag elements working? Would greatly appreciate your thoughts

@mattevans-dev I am considering implementing this feature in the future. I will be releasing v3 soon, after which I will consider how to implement it. This request will naturally be requested in the future, so it is a high priority among the new features.

An alpha version of v3.2 is available today.
We can install it with the following command
npm i @minoru/react-dnd-treeview@alpha

This version supports drag handle.
See below for samples and documentation.
Document
https://github.com/minop1205/react-dnd-treeview#drag-handle
Storybook
https://minop1205.github.io/react-dnd-treeview/?path=/docs/examples-tree-drag-handle--drag-handle-story

Merged: https://github.com/minop1205/react-dnd-treeview/pull/150


[WIP]HIVE-26071: JWT authentication mechanism for Thrift over HTTP in HiveMetastore

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

@dengzhhu653 @yongzhi @harishjp Could you please review this PR please? Thank you

@dengzhhu653 @yongzhi @harishjp Could you please review this PR please? Thank you

Thank you for informing me. Some minor comments, others look good to me!

Thanks @nrg4878 @dengzhhu653 @saihemanth-cloudera @hsnusonic for the review and @yongzhi for the merge.


WCAG 4.1.2: (devenv/tab item 'Microsoft.ML.ModelBuilder.ImageFolderModel') Focusable sibling elements must not have the same Name and LocalizedControlType.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:
#A11yMAS; #A11yTCS; #Win32; #DesktopApp; #Feature-ML.NETModelBuilder-Win32-Nov2020; #A11ySev2; #Benchmark; #Visual Studio; #A11yAuto; #WCAG4.1.2;
Environment Details:
Microsoft Visual Studio 2019 Preview Version 16.8.0 Preview 6.0
Repro Steps:
1.Open Visual Studio Enterprise 2019 Preview
2. Create a new .Net Core Console App (C#)
3. Tab to "Solution Explorer" and right click on the project (Shift + F10) and then from the expanded list Select "Add" and then from the list items select "Machine learning"
4. Tab till "Image Classification" scenario and select the scenario
5. Select any of the environment and tab till "Next Step" button and press enter
6.Tab till Browse button and press enter and upload the file
7. Run Accessibility Insights for the screen
The following accessibility issue needs investigation.
App:
devenv
Element path:
tab item 'Microsoft.ML.ModelBuilder.ImageFolderModel'
Issue Details:
Focusable sibling elements must not have the same Name and LocalizedControlType. WCAG 4.1.2
How To Fix:
Provide unique names for sibling controls that have the same ControlType property.
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.

Verified the bug in the latest build and the issue is fixed.
Hence closing the bug
Please find the attachment for reference
Microsoft Visual Studio Enterprise 2019 Preview
Version 16.9.0 Preview 4.0 [30917.4.main]

Github tag: #Closed;


[Bot] Auto update template

I am a bot, this PR cmi-dair to childmindreasearch. Beep boop.

Closing this since these were separately addressed in https://github.com/childmindresearch/niftyone/pull/4.


Uglifier doesn't load with Ruby 2.4.0 using The Ruby Racer JS runtime

I'm getting following error when launch Rails application with Ruby 2.4.0

TypeError: wrong argument type Class (expected Module)

Running irb and then requiring Uglifier into it throws the same error as well.

Same for me.
Backtrace first lines :

/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:in `include'
/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:in `block (2 levels) in <top (required)>'
/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:in `class_eval'
/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:in `block in <top (required)>'
/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in `each'
/home/fabien/.rvm/gems/ruby-2.4.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in `<top (required)>'

Thanks for the trace @Apokly. It seems that The Ruby Racer does not yet work with Ruby 2.4, but the fix is already merged: https://github.com/cowboyd/therubyracer/commit/f2ccbad7e9e3899e8743624d9b1436500100420a

Hello,
therubyracer 0.12.3 was released to rubygems with Ruby 2.4 support.


optimal rational approximate routine

I’d love a verified optimal rational approximate routine if you feel like writing it (via continued fractions).
See the best rational approximation section of https://en.m.wikipedia.org/wiki/Continued_fraction. Basically you start with the obvious rational equal to the Floating number, then expand its continued fraction as far as you can until the numerator or denominator get too large.
It would be something like Floating.rat : Floating -> (max : N) -> (up : Bool) -> Option Q that turns a floating into a rational in terms at most max.
Originally posted by @girving in https://github.com/girving/interval/issues/1#issuecomment-2267547757

I made a new issue to keep the topic separate.
I'm interested in looking into this. However, I'm still not sure what exactly you mean.
I'm assuming Floating.rat f N _ has denominator at most N. There is (if I understand wikipedia/Continued_fraction) a unique rational number with denominator at most N such that any better rational approximation of f has a larger denominator.
If that's so, why does one need the up : Bool argument? I guess it might be useful to know for sure if one has rounded up or down. How does one characterize the result in this case?
def Floating.rat : Floating -> (max : ℕ) -> (up : Bool) -> Option ℚ := sorry

section proofs_about_floating_rat

variable (f : Floating) (N : ℕ) (up : Bool) (frat : ℚ)
variable (h : f.rat N up = some frat)

lemma Floating.den_rat_le : frat.den ≤ N := sorry

lemma Floating.rat_up_ge (hup : up = true) : f.val ≤ frat := sorry
lemma Floating.rat_down_le (hup : up = false) : frat ≤ f.val := sorry

-- this theorem is false because the best approximation is unique, i.e., independent of `up`?
lemma Floating.rat_good_approx (frat' : ℚ) (hden : frat'.den ≤ N) :
    |f.val - (frat : ℝ)| ≤ |f.val - (frat' : ℝ)| := sorry

In order to round an interval you have to round lo down and hi up. I’m not sure how to get the best rational approximate rounded down offhand, so that would take some searching.

I guess this will have a unique solution? No idea at the moment how to compute it though. You wanted N to bound both numerator and denominator, right? The Wikipedia on continued fractions focuses on denominators.
/--
Best rational approximation with numerator and denominator smaller than `N`,
that is (depending on `up`) either smaller or larger than the input, if we manage to compute it.
-/
def Floating.rat : Floating -> (max : ℕ) -> (up : Bool) -> Option ℚ := sorry

/--
`f.rat N true` is the best rational approximation (with denominator at most `N`) that is no larger
than `f`.
-/
lemma Floating.rat_up_good_approx (f : Floating) (N : ℕ) (frat : ℚ)
    (h : f.rat N true = some frat)
    (frat' : ℚ) (h' :  f.val ≤ frat') (hden : frat'.den ≤ N) :
    |f.val - (frat : ℝ)| ≤ |f.val - (frat' : ℝ)| := sorry

lemma Floating.rat_down_good_approx (f : Floating) (N : ℕ) (frat : ℚ)
    (h : f.rat N false = some frat)
    (frat' : ℚ) (h' :  frat' ≤ f.val) (hden : frat'.den ≤ N) :
    |f.val - (frat : ℝ)| ≤ |f.val - (frat' : ℝ)| := sorry

You can prove that if you want, but it would require developing the theory of optimal rational approximation. I’d be fine if you don’t do that, and instead

Write what you think is the optimal rational approximation routine, or near-optimal
Don’t prove it correct
Once you compute the rational, check that it’s rounded in the right direction and produce none if not

I was looking at Mathlib's continued fractions materials for this and noticed that this project uses a pretty old version of Mathlib. Are you interested in updating it?
I updated the dependency and noticed a lot of errors, some of which I fixed already but many remain.
The main "interesting" question I found is that NatCast UInt64 is now a "local" instance. If you want to update at all, I'm not sure if you want to define it globally for your package or use some other function to cast explicitly rather than writing (n : UInt64) when originally (n : Nat).

I started that update, but likely won't get to finishing it for a week or two.

OK, if you're already doing it then I will stop. Just in case you haven't updated any of the files I looked at so far, I pushed my partial "error fixing" to the branch update_mathlib_dependency of my fork

The current Mathlib version has code to compute the n-th partial fraction convergent. It looks like this
import Mathlib

def r : ℚ := 432453245/9457645766745
def x := GenContFract.of r

-- 7th convergent
#eval (x.convs 7) - r -- (34136 : Rat)/60189386400379474359

However, it seems that the performance of this is not great, e.g., computing the 1000th convergent overflows the stack  (not sure if you care about that).
I'm also not sure how to adapt it to "stop once numerator/denominator get too big" or to "ensure it's rounding up or down"...
I realized that I actually forgot what application you had in mind for this. Just getting the "best Int64 / UInt64" for a Floating or Interval as a goal in itself? Or are you planing to use it to build something else?

I don't need at all: I just use Interval directly. I think you have some reason to want rationals, but I don't understand it.

I also don't actually need rationals... guess that was a misunderstanding then :D
A potentially nice addition to the library would be the option to print an Interval in scientific notation. Some ideas:

3.17E-4 ± 5E-10 (maybe also allowing base 2, taking the number roughly in the middle of the interval, with truncation adjustable and sensible defaults)
10^-13 * [1.1826410293874, 1.1826410293879] (with truncation where the numbers differ)

Yes, that kind of printing would be great. I don’t have great ideas for how to implement it, though, since I haven’t looked at what floating point printing machinery is available.

I'll  make a new issue if I get around to working on the pretty-printing... Thanks for the interesting discussion!


Design: syntax trees vs identity

In https://github.com/rust-analyzer/rust-analyzer/pull/3120#discussion_r378404842, I've once again noticed that working with syntax trees when you want to get semantic information is annoying. This issue is just a brain dump of the things we might do here.
The problem we have is that it's difficult to "index" semantic info by current syntax trees.
For example, here's how one gets a type of expression in Roslyn (with some details ommited):
            SyntaxTree tree = CSharpSyntaxTree.ParseText("some code");

            var model =  getSemanticModel(tree);

            var helloWorldString = root.DescendantNodes()
                                       .OfType<LiteralExpressionSyntax>()
                                       .First();

            var type = model.GetTypeInfo(helloWorldString).Type; // *

Note how at * we only pass the tree to the model to get the type.
In contrast, with the current API in Rust syntax trees are value types which don't remember the context they originated from. So, to get  a type of an expression syntax, you also need to specify the identity of the file this syntax originates from.
The current way to specify identity is mostly the InFile<T> type, which is a pair of T and a (real or macro) file id. There are two problems with this approach:

It does not actually yield a true global identity, because the same file can be included twice into a module tree of a crate (Note how this makes syntax<->semantics not a bijection, which is painful to deal with).
The API is awkward because, if you have s: InFile<ast::StructDef>, you can't get an Option<InFile<ast::Name>> by calling an s.name(), instead you need to s.map(|it| it.name()).transpose(),  which is a lot.

It also has it's benefits:

It is composable, you can have InFile<ast::SomeNod>, InFile<TextRange>, InFile<Token>.
It removes identity from the tree itself, making the boundaries between the components clearer.

What can we do here:

Maintain the status quo, requiring all the IDE code to explicitly mange, map and transpose InFile<T>'s.
Explicitely mirror AST API for InFile<T>. Ie, generate something like impl InFile<ast::StructDef> {  fn name(&self) -> Option<InFile<ast::StructDef>> }
Add FIleId(u32) field to each syntax node, such that nodes always come with a strong identity.

Zulip thread: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Design.20question.3A.20identity.20in.20syntax.20trees

Found a seemingly cute solution: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Design.20question.3A.20identity.20in.20syntax.20trees/near/188124603
We add an identity to the tree, but this identity doesn't have any semantics attached.

For the time being this is closed by https://github.com/rust-analyzer/rust-analyzer/pull/3222.


ES6 support

Just wondering where in the generator does it add the ES6 support or if it just comes natively in Electron?

The current limited ES6 usage comes natively, since Electron uses iojs. You can find supported ES6 features here: https://iojs.org/en/es6.html
Though I plan to integrate babel so we can use any ES6 feature.

:+1:

Electron now supports most of ES6, and will soon support all of it. I don't want to setup up Babel with so little gain. If you want it, you can use https://github.com/electronjs/electron-compile.


🌐 Add Japanese translation for docs/ja/docs/tutorial/metadata.md

This PR translates tutorial/metadata.md in Japanese.

📝 Docs preview for commit 991d09d8cefcc6cf9260b728d23227d8e71e376f at: https://649a13c1bc5da1114be66f3e--fastapi.netlify.app

Thank you @tokusumi! :rocket:
As you are one of the champions of Japanese translations I'm gonna go ahead and merge this. :tada:
If others see things that could be improved later, we can check them in new PRs. :nerd_face:


CLI is too noisy

Expected Behavior
The CLI should output exactly the relevant information, and hide extra debug/info logging behind a --verbose flag or something similar.
Observed Behavior

Currently, the CLI logs a ton of irrelevant information when running, burying the actual relevant information in the bottom (and often leading it to be truncated if the gui showing it has a limit.

Steps to Reproduce

N/A
Context

Explained above.
Your Environment

Version of detekt used: 1.8.0
Version of Gradle used (if applicable): N/A
Operating System and version: MacOS
Link to your project (if it's a public repository):

It seems like you used the --debug flag when calling detekt here. As of 1.6.0 - I think - detekt is quiet by default.

D'oh, I could have sworn I checked that


@swc/core threw an error when attempting to validate swc compiler options.

Describe the bug
Hi there,
I am using @swc/core to speedup the execution of my test suite with avajs/ava.
System info:
Ubuntu 20.04.1 (VM via parallels 18 on a Mac Mini Intel)
node 16.15.0
During npm run test I receive the following error, and I am not sure how to resolve the issue.
/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/transpilers/swc.ts:262
      throw new Error(
            ^
Error: @swc/core threw an error when attempting to validate swc compiler options.
You may be using an old version of swc which does not support the options used by ts-node.
Try upgrading to the latest version of swc.
Error message from swc:
Bindings not found
    at createVariant (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/transpilers/swc.ts:262:13)
    at createSwcOptions (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/transpilers/swc.ts:211:25)
    at create (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/transpilers/swc.ts:56:41)
    at createTranspiler (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/index.ts:784:16)
    at createTranspileOnlyGetOutputFunction (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/index.ts:1341:28)
    at createFromPreloadedConfig (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/index.ts:1404:34)
    at create (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/index.ts:624:10)
    at register (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/index.ts:591:15)
    at Object.registerAndCreateEsmHooks (/home/st/actions-runner/_work/snow/snow/node_modules/ts-node/src/esm.ts:116:34)
    at file:///home/st/actions-runner/_work/snow/snow/node_modules/ts-node/esm.mjs:8:7
  ✖ test/1.sys.test.ts exited with a non-zero exit code: 1

Input code
No response
Config
Snippet of tsconfig.json config:
  "ts-node": {
    "swc": true
  },

Playground link
No response
Expected behavior
Successful execution of npm run test.
Actual behavior
No response
Version
v1.2.241
Additional context
No response

Which os/cpu are you using?

Also, did you use something like --skip-optional or --ignore-scripts?

I added more information under System Info.  No --skip-optional nor --ignore-scripts is used.
Also for completeness, here is the definition of npm run test" in package.json`:
"test": "nyc --reporter=html --reporter=lcov --reporter=text ava"

Thanks for the quick reply! I added more information under System Info.  No --skip-optional nor --ignore-scripts is used.
Also for completeness, here is the definition of npm run test in package.json:
"test": "nyc --reporter=html --reporter=lcov --reporter=text ava"

Quick update, the same project successfully built on the same machine (also Parallels) under Windows. Updating to<EMAIL_ADDRESS>now also under Linux. Could the error come back or did the latest version fix something that could explain the issue on Linux?

Did you share the project directory? You should install on target platform unless you are overriding npm config

I was able to reproduce this issue with my Apollo Federation Gateway running in a Node docker container. I can provide the Dockerfile
FROM node:17.3
WORKDIR /app
ENV NODE_ENV=dev
ENV ZIPKIN=http://localhost:9411
EXPOSE 4000
COPY . .
CMD ["yarn", "run", "dev"]

encountered this error on docker run my-image:1.0
$ docker run graphql-federation-poc:0.2
yarn run v1.22.17
$ ts-node src/index.ts
/app/node_modules/ts-node/src/transpilers/swc.ts:262
      throw new Error(
            ^
Error: @swc/core threw an error when attempting to validate swc compiler options.
You may be using an old version of swc which does not support the options used by ts-node.
Try upgrading to the latest version of swc.
Error message from swc:
Bindings not found
    at createVariant (/app/node_modules/ts-node/src/transpilers/swc.ts:262:13)
    at createSwcOptions (/app/node_modules/ts-node/src/transpilers/swc.ts:211:25)
    at create (/app/node_modules/ts-node/src/transpilers/swc.ts:56:41)
    at createTranspiler (/app/node_modules/ts-node/src/index.ts:784:16)
    at createTranspileOnlyGetOutputFunction (/app/node_modules/ts-node/src/index.ts:1341:28)
    at createFromPreloadedConfig (/app/node_modules/ts-node/src/index.ts:1404:34)
    at phase4 (/app/node_modules/ts-node/src/bin.ts:543:44)
    at bootstrap (/app/node_modules/ts-node/src/bin.ts:95:10)
    at main (/app/node_modules/ts-node/src/bin.ts:55:10)
    at Object.<anonymous> (/app/node_modules/ts-node/src/bin.ts:800:3)
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.

I have the same problem, I can't start my project at all with Docker/TS-Node/SWC

Can you try to reinstall swc in your docker?

That's what I am doing
Dockerfile:
FROM node:16.16-alpine

WORKDIR /app

COPY package*.json ./
RUN npm install
COPY . .

CMD npm run start

.dockerignore:
node_modules

This issue is still valid

I'm also running into this issue after updating from node 14.17.1 to node 16.16.0 on a MBP 16 M1 Pro:
/Users/.../node_modules/@swc/core/index.js:250
        throw new Error("Bindings not found");
        ^

Error: Bindings not found
    at Compiler.transformSync (/Users/.../node_modules/@swc/core/index.js:250:15)
    at transformSync (/Users/.../node_modules/@swc/core/index.js:348:21)
    at transformSync (/Users/.../node_modules/@swc-node/core/index.ts:69:26)
    at compile (/Users/.../node_modules/@swc-node/register/register.ts:44:40)
    at exts (/Users/.../node_modules/@swc-node/register/register.ts:55:38)
    at Module._compile (/Users/.../node_modules/pirates/lib/index.js:130:29)
    at Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Object.newLoader [as .ts] (/Users/.../node_modules/pirates/lib/index.js:141:7)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)

The issue is still valid.

Not sure why bot aggressively marks this one 🤔

Thanks @jgujgu. Is there anything for npm?

Getting this error on an M1 Mac using node 19, but not on 18.

I'm getting this issue with the Node 16 docker image.

I've ran into similar issue with a bit uncommon setup, but maybe this will help shed some light.
I have a working setup on local node 18, using yarn. I wanted to create a sample Dockerfile using npm, so I ran npm i locally to generate package-lock.json. Then docker build ran up to the build point where it failed on Fallback bindings does not support filesystem access..
When installing @swc/core and @swc-cli in the build step in the container again, it worked well.
Then I removed node_modules and package-lock.json on the host and ran npm i again to get a new package-lock.json. And with this new lock the whole build ran successfully.
old-package-lock.json.txt
package-lock.json.txt
When compared, there are few @swc packages that didn't get "locked" with existing node_modules.
So, maybe the "work-around" is to rm -rf node_modules && rm package-lock.json && npm i on the host?

My issue was because I was mounting a volume in such a way the node_modules would be mounted to the host which could cause issues.
By adding node_modules in it's own volume in the docker-compose spec I can tell docker to preserve the node_modules folder from the underlying image and now it works.

Hi there!
I also had this issue and was able to resolve it. below are my "story".
Most beneficial (give me some food to think) to me were messages from @jgujgu and @wodCZ.
I was migrating from yarn to npm, and I wanted to have a dependency tree as similar as possible. So I did not delete node_modules folder and just run npm i. This caused package-lock.json file to be not fully valid, where swc package for my arch was missing (I figured out that later). So I did a couple of test setups, and they were OK. At some point, I decided to check "moving parts" of the swc software in the file system and found that arm64 file/package was missing.

Summary: if you got a subject error message -- make sure you have both arch package and arch binary in your FS
Advice to developers: maybe you should add/adjust a check if arch binary exists and make sure the error message for that is crystal clear

using node v16.18.1 also met this problem, on MBP 13 M1, problem performed like @btecu

Error: Bindings not found
at Compiler.transformSync (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/@swc+core@1.3.20/node_modules/@swc/core/index.js:250:15)
at Object.transformSync (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/@swc+core@1.3.20/node_modules/@swc/core/index.js:348:21)
at compile (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/@swc+register@0.1.10_@swc+core@1.3.20/node_modules/@swc/register/lib/node.js:76:22)
at compileHook (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/@swc+register@0.1.10_@swc+core@1.3.20/node_modules/@swc/register/lib/node.js:91:16)
at Module._compile (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/pirates@4.0.5/node_modules/pirates/lib/index.js:130:29)
at Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Object.newLoader [as .js] (/Users/buxiongyu/Desktop/zeus/node_modules/.pnpm/pirates@4.0.5/node_modules/pirates/lib/index.js:141:7)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Module.require (node:internal/modules/cjs/loader:1057:19)

i'm just wondering if it is cross platform problem of npm/pnpm ?

Same issue on
Node : 16.15.0
   OS   : darwin x64
   npm  : 8.10.0

Experience this while using @nrwl/nx npm package.

What helped me in my npm monorepo:

npm uninstall all swc related packages
remove package-lock.json
remove all node_modules directories
npm install
npm install the swc related packages again

Hey buddy, I have encountered the same issue as you and have solved it, I would like to share my experience with you to see if it can help.
Just a few days ago I was able to install Taro-cli without any issues, then after reinstalling the system, my project encountered the same error as yours. I searched for solutions in the Taro repository and the SWC repository, but there was no ready answer. However, they gave some directions to troubleshoot.So I tried switching the node version, package manager version and source, and Taro/cli version, but all failed. Finally, I debugged the source code with breakpoints, combined with my own experience, and found that the problem was related to the rust runtime environment, which needed to be installed. The specific installation method can be referred to the link below.
https://blog.csdn.net/u011149152/article/details/123518465

I think there is a bug in the postinstall.sh script in the swc module. Somewhere, it "trash" the @swc/wasm module instead of adding it.
the script however is discarded if @swc/wasm is added in the dependencies. What fixed it for me (in my dockers in CI), is to add the package in the dependencies.

@littleski I ran into the same problem and adding @swc/wasm solved it for me too...so yes, a bug in the post install maybe?

I ran into a similar problem when running a build with SWC in GitHub actions (worked fine on my M1 mac).
The build would fail with Fallback bindings does not support filesystem access.
After upgrading @swc/cli to 0.1.62 and @swc/core to 1.3.39 the build executed again in my workflow.

Does anyone have a solution?

I have the same issue when I use Github action on @swc/core 1.3.44. I try to downgrade to @swc/core 1.3.39.The action work again.

What have helped me

Create new clean project
manually install @swc/core of needed version there
manually copypaste core-darwin-x64 to node_modules/@swc

Indeed this solution is working well, btw installing @swc/core is enough and solves the problem, but I'm Interested if there are other dependencies that require it.

M1, node v18.12.1, pnpm (solved)
before I added  @swc/core-linux-arm64-musl as dev deps, had same err
  ● Test suite failed to run
    Bindings not found
      at Compiler.transformSync (node_modules/.pnpm/@swc+core@1.3.40/node_modules/@swc/core/index.js:250:15)

Having similar issues here.
M1 Pro
node v19.7.0 (tried various previous versions as well)
@swc/jest ^0.2.26
Error: Jest: Got error running globalSetup - /app/tests/globalSetup.ts, reason: Bindings not found

at Compiler.transformSync (/node_modules/@swc/core/index.js:250:15)

Tried going through the whole install/uninstall process with swc packages and node_modules that seemed to work for some people in the thread – not for me.

this issue is annoying I have to install swc manually each time after npm i, does anybody found a way to fix it once for all?

Primarily this is due to you have installed one binaries for the specific platform and tries to run on other platform which doesn't have corresponding binary. Upstream issues like https://github.com/npm/cli/issues/4828 make things more challenging.
We are open to accept fixes, but I don't believe there's no quick win for now.

@kwonoj well, we are sharing project among people with MacOS, Windows, Ubuntu but this is a normal situation when repo has collaborators

I'm not saying it's uncommon to share project across different platform users, saying there are some constraint of actions we can take. As said, we are open to accept fix / suggestions but afaik there is no clear win to any paths we can take.

I think that the approach how bindings are handled is not compatible to package-lock.json and npm ci.
When installing (generating package-lock) on one OS and running the CI task on another OS by using npm ci this will always fail because the wrong bindings are persisted in the package-lock.
Or maybe it's because swc doesn't use the expected postinstall scripts or so that would work with the recommended approach when using private repositories on a CI like described in this documentation: https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#use-private-packages
In short when using npm ci --ignore-scripts for security reasons swc doesn't setup properly when running npm rebuild && npm run prepare --if-present afterwards.

We switched to pnpm, it is not only faster it also doesn't have this issue as well as issues with legacy peer dependencies in lock file

Having the same issue. The only solution is to completely nuke the nvm (fnm) Node environment, and the local node_modules and do a full re-install. Seems like something gets written into the global scope, that has an effect on this?

Never mind, just did it again without node (nvm) nuking, just node_modules and it worked.
For us, the cause of this misalignment, I think, is Renovate Bot. Every time it updates a dep, and I do a pull, then the breakage will occur.

Same problem. Runs fine on MacOS in local env and throws while building on Docker

pnpm solved the build on CI, but my coworker is unable to run the project on Ubuntu (Node v18.16.0)

Getting same issue. pnpm does not work for me

What the hell ?

@jaybe78 https://kdy1.dev/posts/2023/1/plus-1-is-spam

@jaybe78 This is not a bug of swc

I think there is a bug in the postinstall.sh script in the swc module. Somewhere, it "trash" the @swc/wasm module instead of adding it. the script however is discarded if @swc/wasm is added in the dependencies. What fixed it for me (in my dockers in CI), is to add the package in the dependencies. But looking at the comments, i think there is multiple issues listed here, so it may not fix for everyone.

I put it again here, in case it helps someone.

adding the core modules as optional dependencies for the project fixed the error for me:
npm install --save-optional \
    "@swc/core-darwin-arm64" \
    "@swc/core-darwin-x64" \
    "@swc/core-linux-arm-gnueabihf" \
    "@swc/core-linux-arm64-gnu" \
    "@swc/core-linux-arm64-musl" \
    "@swc/core-linux-x64-gnu" \
    "@swc/core-linux-x64-musl" \
    "@swc/core-win32-arm64-msvc" \
    "@swc/core-win32-ia32-msvc" \
    "@swc/core-win32-x64-msvc"

you can also filter out the list of packages in case you are certain what is the OS / architecture of your development computer and the CI.
hope this helps for others until the issue is resolved!

I was having the same issue Fallback bindings does not support filesystem access. when running in GitHub Actions.
@pcdevil 's response solved the issue - thanks!!

thanks @pcdevil that was the solution for me (when compiling react-email in docker)

I'm having this issue re-appear with<EMAIL_ADDRESS>on Linux (MX Linux 23 on x64 -- Debian 12 based) with a mono repo using npm. If I explicitly install<EMAIL_ADDRESS>in my workspace it doesn't work but explicitly installing the previous version npm -w=backend i -D<EMAIL_ADDRESS>is a good workaround for now.

I can work around this by simply yarn add -D @swc/core@latest.

just clear node_modules files and do npm install

I worked around this with:
npm install --save-dev<EMAIL_ADDRESS><EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>
These are pretty old versions - there's likely newer ones that work, I just grabbed these from a project where I didn't have this issue.

I'm having same issue using @swc/core:1.5.2

@throrin19 there is a deprecation warning against 1.5.2 now<EMAIL_ADDRESS>Mac OS installation is broken. Upgrading to 1.5.3 fixes the issue.

Can someone provide a minimal repro?

@kdy1
The installation always fails on certain servers. For me specifically, in the cheap ones running on AMD vCPUs.
uname -m output is aarch64
lscpu output is:
Architecture:           aarch64
  CPU op-mode(s):       32-bit, 64-bit
  Byte Order:           Little Endian
CPU(s):                 4
  On-line CPU(s) list:  0-3
Vendor ID:              ARM
  Model name:           Neoverse-N1
    Model:              1
    Thread(s) per core: 1
    Core(s) per socket: 4
    Socket(s):          1
    Stepping:           r3p1
    BogoMIPS:           50.00
    Flags:              fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

Let me know if I can provide you with nay additional information.
(We have resorted to version locking swc manually in our monorepo for now, which isn't good. )

For those still struggling heres what worked for me

I've found a fix, apparently what happens (not sure why) is node_modules/@swc/core installs wrong optional packages within docker container.
Heres the fix:
Open docker image and find your WORKDIR
Remove core-darwin-x64 or core-win-32-x64-msvc or similar from node_modules/@swc/core.
There should be core-linux-x64-gnu and core-linux-x64-muscl (if your docker image is linux)
Run npm install from within docker container (this time you should see correct packages in @swc/core under node_modules/)
My understanding is that when you pull project and do npm install on host machine which is macOS or Windows, swc installs right packages for your host system.
I'm not sure why it skips installing correct ones on docker image but this is what causes issues.
I tried setting this up on windows and macbook and both times had the same issues where this was the fix.

https://github.com/orgs/adonisjs/discussions/4600

If your problem is locally, I mean, you are using docker-compose pay attention to the shared volumes, problem it is sharing the wrong file between your windows system and your container running windows.
You can solve it excluding your node_modules from the sharing volumes from you docker-compose.yml file like this:
volumes:
      - ./:/home/node/app # Here we are sharing all the content from local to your container
      - /home/node/app/node_modules/ # Here we are excluding the node_modules


Drop Udp Messages with Unknown Issues

959.log
Please find attached our complete test log

We are using the latest version of OTBR

Messages are dropped if the destination is unknown or unreachable:

The destination IPv6 address is an on-mesh address, but no device on the mesh claims to have this address (there is no response to an "Address Query" for the address).
There is no route toward the intended destination.

The logs provide the answer in your case, as there seems to be no response to the Address Query earlier:
> cat ~/Downloads/959.log | grep otbr-agent | grep fd9c:1c81:262e:1:67f6:b2f6:c04b:2a48 -B 2

12-02 06:08:49.819 I/otbr-agent( 1643): 00:01:34.254 [I] AddrResolver--: Timed out waiting for AddressNotify for fd9c:1c81:262e:1:67f6:b2f6:c04b:2a48, retry: 15
12-02 06:08:49.819 I/otbr-agent( 1643): 00:01:34.254 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:158, chksum:0baf, ecn:no, sec:yes, error:AddressQuery, prio:low
12-02 06:08:49.819 I/otbr-agent( 1643): 00:01:34.254 [N] MeshForwarder-:     src:[fd9c:1c81:262e:1:133b:c363:a00d:8bbf]:32992
12-02 06:08:49.819 I/otbr-agent( 1643): 00:01:34.254 [N] MeshForwarder-:     dst:[fd9c:1c81:262e:1:67f6:b2f6:c04b:2a48]:33521
--
...
--
12-02 06:08:59.436 I/otbr-agent( 1643): 00:01:43.872 [N] MeshForwarder-: Dropping IPv6 UDP msg, len:158, chksum:e028, ecn:no, sec:yes, error:Drop, prio:low
12-02 06:08:59.436 I/otbr-agent( 1643): 00:01:43.872 [N] MeshForwarder-:     src:[fd9c:1c81:262e:1:133b:c363:a00d:8bbf]:44134
12-02 06:08:59.436 I/otbr-agent( 1643): 00:01:43.872 [N] MeshForwarder-:     dst:[fd9c:1c81:262e:1:67f6:b2f6:c04b:2a48]:33521

@abtink Thank you for your reply.
To improve troubleshooting when full logs aren't available, could we add a reason to each "error: Drop" message?
For example, "error: AddressQuery". This would provide more context without needing full logs.

To improve troubleshooting when full logs aren't available, could we add a reason to each "error: Drop" message?

The reason is already included in the log as error:Drop, which indicates device has determined there is no route to this destination (which the device can reach due to a variety of earlier events or failures such as an earlier address query timeout)

For example, "error: AddressQuery". This would provide more context without needing full logs.

This would not be proper/correct, as there is no "Address Query" attempt made for this message.

@abtink Okay, I understand the meaning. When Drop occurs, it means that the destination address is unreachable. Thank you for your reply


Microsoft login

This is still WIP!
More testing is required, here are some instructions on how to do so (in the "UPDATE" section): https://github.com/Lea-fish/Leafish/issues/188#issue-1005061042

It looks like we've been trying to handle O2Auth ourselves but there's already a rust package that handles this.
Is anyone opposed if I add it as a dependency?

So I tried this (putting in my own client_id and secret from Azure), and it seemed to login... but then when I click on the imported account I get a crash because the application tries to call refresh which is not implemented: https://github.com/Lea-fish/Leafish/blob/microsoft-login/protocol/src/protocol/microsoft2.rs#L48

It fails to start with the following error:
[wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting.

It fails to start with the following error:
[wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting.

i think that error got fixed in #262 and #268 , this PR is pretty old so it is probably not included here

Has there been any work on this since then? Afaict this has to get done in order for anyone to be able to use this project at all, so it seems a shame to let it gather dust.

Superseded by https://github.com/Lea-fish/Leafish/pull/297 for now, we might consider reimplementing microsoft auth into the client itself at some point but then we should probably use https://github.com/azalea-rs/azalea/tree/main/azalea-auth/src