DF Template Enhancements: error when opening the templates measures settings

Module
DF Template Enhancements 1.2.0
When trying to open the templates measures settings

It appears to be working fine for me, not sure what's going on for yours. Maybe a module conflict? Could you try opening it with other mods disabled?

@flamewave000 No other modules.
Error on this as well : game.i18n.translations['DF_TEMPLATES']['TemplateConfig']['Options']

Maybe because I had an older version? Issue with the migration or smt?

Maybe because I'm not playing with the default language?

@DarKDinDoN what language are you using? I only have partial translations for Japanese (community submitted).

Ok, that's very very weird. I'll have to figure out how to change my localization to test this. My understanding is that if the language is not supported, it should default to the english language file.

@flamewave000 just go to the settings in game and change the language :D


BNtoConv: volumetric support

The original code actually already supports volumetric batchnorm integration, so I just allowed it.
Btw: I think you forgot to add utils to init.lua?

about utils in init.lua, I prefer to use it like this:
local utils = require 'inn.utils'
utils.foldBatchNorm(net)

without registering in inn table

Here you go.

thanks


Update cache-how-to-upgrade.md

Please refer this ICM for more information: https://portal.microsofticm.com/imp/v3/incidents/details/354095130/home
This is for scenarios where redis cache is having the private endpoint.

@flang-msft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@flang-msft
Can you review this old PR and determine whether it needs to be closed or merged?

@vishalk9040
I have merged your contribution into a private branch for editing. It will be published after that with you as a contributor.
Thanks for your commitment to the documentation.


./downr1n.sh: line 1298: cd: too many arguments

I just fixed the old error: TypeError: function missing required argument 'initial_buffer_values' (pos 2)
And now, I got the new error:
[*] Command ran: sudo ./downr1n.sh --downgrade 14.0
[21:13:08.413][3] usbmuxd v1.1.1 starting up
[21:13:08.414][3] Using libusb 1.0.25
[21:13:08.418][3] Initialization complete
[21:13:08.419][3] Connecting to new device on location 0x30021 as ID 1
[21:13:08.419][3] Connected to v2.0 device 1 on location 0x30021 with serial number ramdisk tool Sep 18 2022 20:14:43
downr1n | Version 3.0
Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices
[] Detected ramdisk mode device
[] Rebooting device in SSH Ramdisk
[21:13:09.426][2] device_control_input: Got unhandled payload type 5
[21:13:14.616][3] Removed device 1 on location 0x30021
[] Waiting for device in recovery mode
[] Waiting for devices
[] Detected recovery mode device
[] Getting device info...
Detected cpid, your cpid is 0x8003
Detected model, your model is n66map
Detected deviceid, your deviceid is iPhone8,2
[] To get into DFU mode, you will be guided through 2 steps:
[] Press any key when ready for DFU mode
Get ready (0)
Release power button, but keep holding home button (9)
Release power button, but keep holding home button (2)
[] Device entered DFU!
[-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no
yes
ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw
[] Checking if the ipsw is for your device
[] Checking ipsw version
[] Extracting ipsw, hang on please ...
[] Got extract the IPSW successfully
[] Creating ramdisk
[-] Ramdisk is already created so SKIPPING ...
[] Booting ramdisk
[/] We couldn't get the ipsw curl. we will proceed with -k option with curl
usb_timeout: 5
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: RESET
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: SETUP
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: PATCH
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Now you can boot untrusted images.
usb_timeout: 5
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
Found the USB handle.
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[] Waiting for the ramdisk to finish booting
libusb: warning [op_get_configuration] device unconfigured
libusb: error [op_get_active_config_descriptor] device unconfigured
[21:14:23.888][3] Could not get old configuration descriptor for device 3-41: LIBUSB_ERROR_NOT_FOUND
[21:14:23.902][3] Connecting to new device on location 0x30029 as ID 2
[21:14:23.942][3] Connected to v2.0 device 2 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43
[21:14:23.942][2] device_control_input: Got unhandled payload type 5
[21:14:24.850][2] device_control_input: Got unhandled payload type 5
Error connecting to device: No error information
[] Mounting filesystems ...
[] Dumpped SHSH
[] Checking device version
the version that the device is currently in is 15.8
[] extracting kernel ...
TypeError: function missing required argument 'initial_buffer_values' (pos 2)
^C
yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3.9 -m pip uninstall pylzss lzss
sudo: python3.9: command not found
yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3 -m pip uninstall pylzss lzss
WARNING: Skipping pylzss as it is not installed.
Found existing installation: lzss 0.3
Uninstalling lzss-0.3:
Would remove:
/usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg
Proceed (Y/n)? y
Successfully uninstalled lzss-0.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo ./downr1n.sh --downgrade 14.0
[] Command ran: sudo ./downr1n.sh --downgrade 14.0
[21:22:31.836][3] usbmuxd v1.1.1 starting up
[21:22:31.836][3] Using libusb 1.0.25
[21:22:31.840][3] Initialization complete
[21:22:31.841][3] Connecting to new device on location 0x30029 as ID 1
[21:22:31.841][3] Connected to v2.0 device 1 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43
[-] lzss is not installed. we can installl it for you, press any key to start installing lzss, or press ctrl + c to cancel
[21:22:32.849][2] device_control_input: Got unhandled payload type 5
Cloning into '/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main/binaries/Linux/pylzss'...
Note: switching to '8efcda0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 8efcda0 Merge pull request #8 from quiple/master
running install
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 1.1build1 is an invalid version and will not be supported in a future release
warnings.warn(
/usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 0.1.43ubuntu1 is an invalid version and will not be supported in a future release
warnings.warn(
running bdist_egg
running egg_info
creating lzss.egg-info
writing lzss.egg-info/PKG-INFO
writing dependency_links to lzss.egg-info/dependency_links.txt
writing top-level names to lzss.egg-info/top_level.txt
writing manifest file 'lzss.egg-info/SOURCES.txt'
reading manifest file 'lzss.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'COPYING'
adding license file 'COPYING.LESSER'
writing manifest file 'lzss.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
building 'lzss' extension
creating build
creating build/temp.linux-x86_64-3.10
x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I./include -I/usr/include/python3.10 -c pylzss.c -o build/temp.linux-x86_64-3.10/pylzss.o
pylzss.c:20:23: warning: ‘LZSS_P’ defined but not used [-Wunused-const-variable=]
20 | static const unsigned LZSS_P = 1;
|                       ^~~~~~
creating build/lib.linux-x86_64-3.10
x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-Bsymbolic-functions -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.10/pylzss.o -o build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
copying build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/egg
creating stub loader for lzss.cpython-310-x86_64-linux-gnu.so
byte-compiling build/bdist.linux-x86_64/egg/lzss.py to lzss.cpython-310.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying lzss.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying lzss.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying lzss.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying lzss.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
zip_safe flag not set; analyzing archive contents...
pycache.lzss.cpython-310: module references file
creating dist
creating 'dist/lzss-0.3-py3.10-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing lzss-0.3-py3.10-linux-x86_64.egg
creating /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg
Extracting lzss-0.3-py3.10-linux-x86_64.egg to /usr/local/lib/python3.10/dist-packages
Adding lzss 0.3 to easy-install.pth file
Installed /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg
Processing dependencies for lzss==0.3
Finished processing dependencies for lzss==0.3
downr1n | Version 3.0
Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices
[] Detected ramdisk mode device
[] Rebooting device in SSH Ramdisk
[21:22:46.994][3] Removed device 1 on location 0x30029
[] Waiting for device in recovery mode
[] Waiting for devices
[] Detected recovery mode device
[] Getting device info...
Detected cpid, your cpid is 0x8003
Detected model, your model is n66map
Detected deviceid, your deviceid is iPhone8,2
[] To get into DFU mode, you will be guided through 2 steps:
[] Press any key when ready for DFU mode
Get ready (0)
Release power button, but keep holding home button (9)
Release power button, but keep holding home button (1)
[] To get into DFU mode, you will be guided through 2 steps:
[] Press any key when ready for DFU mode
Get ready (0)
Release power button, but keep holding home button (9)
Release power button, but keep holding home button (3)
[] Device entered DFU!
[] Device entered DFU!
[-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no
yes
ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw
[] Checking if the ipsw is for your device
[] Checking ipsw version
[] Extracting ipsw, hang on please ...
[] Got extract the IPSW successfully
[] Creating ramdisk
[-] Ramdisk is already created so SKIPPING ...
[] Booting ramdisk
[/] We couldn't get the ipsw curl. we will proceed with -k option with curl
usb_timeout: 5
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: RESET
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: SETUP
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: PATCH
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Now you can boot untrusted images.
usb_timeout: 5
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
Found the USB handle.
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[==================================================] 100.0%
[] Waiting for the ramdisk to finish booting
libusb: warning [op_get_configuration] device unconfigured
libusb: error [op_get_active_config_descriptor] device unconfigured
[21:24:18.665][3] Could not get old configuration descriptor for device 3-49: LIBUSB_ERROR_NOT_FOUND
[21:24:18.670][3] Connecting to new device on location 0x30031 as ID 2
[21:24:18.719][3] Connected to v2.0 device 2 on location 0x30031 with serial number ramdisk tool Sep 18 2022 20:14:43
[21:24:18.719][2] device_control_input: Got unhandled payload type 5
[21:24:19.363][2] device_control_input: Got unhandled payload type 5
Error connecting to device: No error information
[] Mounting filesystems ...
[] Dumpped SHSH
[] Checking device version
the version that the device is currently in is 15.8
[] extracting kernel ...
[] extracted
Reboot into recovery mode ...
[21:25:09.012][3] Removed device 2 on location 0x30031
[] To get into DFU mode, you will be guided through 2 steps:
[] Press any key when ready for DFU mode
Get ready (0)
Release power button, but keep holding home button (9)
Release power button, but keep holding home button (3)
[] To get into DFU mode, you will be guided through 2 steps:
[] Press any key when ready for DFU mode
Get ready (0)
Release power button, but keep holding home button (9)
Release power button, but keep holding home button (3)
[] Device entered DFU!
[] Device entered DFU!
[ ]Patching some boot files...
[] Finished moving the boot files to work
[] Decrypthing ibss and iboot
usb_timeout: 5
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: RESET
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: SETUP
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Stage: PATCH
ret: true
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
CPID: 0x8003
Found the USB handle.
Now you can boot untrusted images.
[libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227
Found the USB handle.
[] Patching the kernel
[] Patching the kernel to restore using futurerestore
[] Patching devicetree
[] Patching the restored_external and asr, and saving them into the ramdisk ...
'work/devicetree.img4' -> 'boot/iPhone8,2/devicetree.img4'
'work/iBEC.img4' -> 'boot/iPhone8,2/iBEC.img4'
'work/iBSS.img4' -> 'boot/iPhone8,2/iBSS.img4'
'work/kernelcache.img4' -> 'boot/iPhone8,2/kernelcache.img4'
'work/trustcache.img4' -> 'boot/iPhone8,2/trustcache.img4'
[] Sucess Patching the boot files
[] Checking if the llb was already replaced
[] Patching the llb in the ipsw to avoid false dfu mode
[=] Hi, please i need that you write the ios version that this device is on or the version of the ios that it was on (if this device is already downgraded), most of the time is the lastest version of ios. write 0 if you want to skip this (it is not recommended to skip this as this can avoid false dfu mode)
Version detected!. we are gonna use 15.8
[] LLB downloaded correctly
[*] putting this LLB into the ipsw
zip warning: Local Version Needed To Extract does not match CD: Firmware/
zip warning: Local Version Needed To Extract does not match CD: Firmware/AOP/
zip warning: Local Version Needed To Extract does not match CD: Firmware/all_flash/
updating: Firmware/all_flash/LLB.n66m.RELEASE.im4p (deflated 0%)
zip warning: Local Version Needed To Extract does not match CD: Firmware/dfu/
zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/
zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/local/
adding: Firmware/all_flash//LLB.n66m.RELEASE.im4p (deflated 0%)
*ERROR:
./downr1n.sh: line 1298: cd: too many arguments

couldn't you just open again the other pull request instead of creating another one ?

I just fixed the old error: TypeError: function missing required argument 'initial_buffer_values' (pos 2) And now, I got the new error: [*] Command ran: sudo ./downr1n.sh --downgrade 14.0 [21:13:08.413][3] usbmuxd v1.1.1 starting up [21:13:08.414][3] Using libusb 1.0.25 [21:13:08.418][3] Initialization complete [21:13:08.419][3] Connecting to new device on location 0x30021 as ID 1 [21:13:08.419][3] Connected to v2.0 device 1 on location 0x30021 with serial number ramdisk tool Sep 18 2022 20:14:43 downr1n | Version 3.0 Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices [] Detected ramdisk mode device [] Rebooting device in SSH Ramdisk [21:13:09.426][2] device_control_input: Got unhandled payload type 5 [21:13:14.616][3] Removed device 1 on location 0x30021 [] Waiting for device in recovery mode [] Waiting for devices [] Detected recovery mode device [] Getting device info... Detected cpid, your cpid is 0x8003 Detected model, your model is n66map Detected deviceid, your deviceid is iPhone8,2 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (2) [] Device entered DFU! [-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no yes ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw [] Checking if the ipsw is for your device [] Checking ipsw version [] Extracting ipsw, hang on please ... [] Got extract the IPSW successfully [] Creating ramdisk [-] Ramdisk is already created so SKIPPING ... [] Booting ramdisk [/] We couldn't get the ipsw curl. we will proceed with -k option with curl usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [] Waiting for the ramdisk to finish booting libusb: warning [op_get_configuration] device unconfigured libusb: error [op_get_active_config_descriptor] device unconfigured [21:14:23.888][3] Could not get old configuration descriptor for device 3-41: LIBUSB_ERROR_NOT_FOUND [21:14:23.902][3] Connecting to new device on location 0x30029 as ID 2 [21:14:23.942][3] Connected to v2.0 device 2 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43 [21:14:23.942][2] device_control_input: Got unhandled payload type 5 [21:14:24.850][2] device_control_input: Got unhandled payload type 5 Error connecting to device: No error information [] Mounting filesystems ... [] Dumpped SHSH [] Checking device version the version that the device is currently in is 15.8 [] extracting kernel ... TypeError: function missing required argument 'initial_buffer_values' (pos 2) ^C yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3.9 -m pip uninstall pylzss lzss sudo: python3.9: command not found yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3 -m pip uninstall pylzss lzss WARNING: Skipping pylzss as it is not installed. Found existing installation: lzss 0.3 Uninstalling lzss-0.3: Would remove: /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Proceed (Y/n)? y Successfully uninstalled lzss-0.3 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo ./downr1n.sh --downgrade 14.0 [] Command ran: sudo ./downr1n.sh --downgrade 14.0 [21:22:31.836][3] usbmuxd v1.1.1 starting up [21:22:31.836][3] Using libusb 1.0.25 [21:22:31.840][3] Initialization complete [21:22:31.841][3] Connecting to new device on location 0x30029 as ID 1 [21:22:31.841][3] Connected to v2.0 device 1 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43 [-] lzss is not installed. we can installl it for you, press any key to start installing lzss, or press ctrl + c to cancel [21:22:32.849][2] device_control_input: Got unhandled payload type 5 Cloning into '/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main/binaries/Linux/pylzss'... Note: switching to '8efcda0'.
You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 8efcda0 Merge pull request #8 from quiple/master running install /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools. warnings.warn( /usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 1.1build1 is an invalid version and will not be supported in a future release warnings.warn( /usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 0.1.43ubuntu1 is an invalid version and will not be supported in a future release warnings.warn( running bdist_egg running egg_info creating lzss.egg-info writing lzss.egg-info/PKG-INFO writing dependency_links to lzss.egg-info/dependency_links.txt writing top-level names to lzss.egg-info/top_level.txt writing manifest file 'lzss.egg-info/SOURCES.txt' reading manifest file 'lzss.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'COPYING.LESSER' writing manifest file 'lzss.egg-info/SOURCES.txt' installing library code to build/bdist.linux-x86_64/egg running install_lib running build_ext building 'lzss' extension creating build creating build/temp.linux-x86_64-3.10 x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I./include -I/usr/include/python3.10 -c pylzss.c -o build/temp.linux-x86_64-3.10/pylzss.o pylzss.c:20:23: warning: ‘LZSS_P’ defined but not used [-Wunused-const-variable=] 20 | static const unsigned LZSS_P = 1; | ^~~~~~ creating build/lib.linux-x86_64-3.10 x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-Bsymbolic-functions -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.10/pylzss.o -o build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/egg copying build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/egg creating stub loader for lzss.cpython-310-x86_64-linux-gnu.so byte-compiling build/bdist.linux-x86_64/egg/lzss.py to lzss.cpython-310.pyc creating build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... pycache.lzss.cpython-310: module references file creating dist creating 'dist/lzss-0.3-py3.10-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it removing 'build/bdist.linux-x86_64/egg' (and everything under it) Processing lzss-0.3-py3.10-linux-x86_64.egg creating /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Extracting lzss-0.3-py3.10-linux-x86_64.egg to /usr/local/lib/python3.10/dist-packages Adding lzss 0.3 to easy-install.pth file
Installed /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Processing dependencies for lzss==0.3 Finished processing dependencies for lzss==0.3 downr1n | Version 3.0 Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices [] Detected ramdisk mode device [] Rebooting device in SSH Ramdisk [21:22:46.994][3] Removed device 1 on location 0x30029 [] Waiting for device in recovery mode [] Waiting for devices [] Detected recovery mode device [] Getting device info... Detected cpid, your cpid is 0x8003 Detected model, your model is n66map Detected deviceid, your deviceid is iPhone8,2 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (1) [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] Device entered DFU! [] Device entered DFU! [-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no yes ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw [] Checking if the ipsw is for your device [] Checking ipsw version [] Extracting ipsw, hang on please ... [] Got extract the IPSW successfully [] Creating ramdisk [-] Ramdisk is already created so SKIPPING ... [] Booting ramdisk [/] We couldn't get the ipsw curl. we will proceed with -k option with curl usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [] Waiting for the ramdisk to finish booting libusb: warning [op_get_configuration] device unconfigured libusb: error [op_get_active_config_descriptor] device unconfigured [21:24:18.665][3] Could not get old configuration descriptor for device 3-49: LIBUSB_ERROR_NOT_FOUND [21:24:18.670][3] Connecting to new device on location 0x30031 as ID 2 [21:24:18.719][3] Connected to v2.0 device 2 on location 0x30031 with serial number ramdisk tool Sep 18 2022 20:14:43 [21:24:18.719][2] device_control_input: Got unhandled payload type 5 [21:24:19.363][2] device_control_input: Got unhandled payload type 5 Error connecting to device: No error information [] Mounting filesystems ... [] Dumpped SHSH [] Checking device version the version that the device is currently in is 15.8 [] extracting kernel ... [] extracted Reboot into recovery mode ... [21:25:09.012][3] Removed device 2 on location 0x30031 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] Device entered DFU! [] Device entered DFU! [ ]Patching some boot files... [] Finished moving the boot files to work [] Decrypthing ibss and iboot usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [] Patching the kernel [] Patching the kernel to restore using futurerestore [] Patching devicetree [] Patching the restored_external and asr, and saving them into the ramdisk ... 'work/devicetree.img4' -> 'boot/iPhone8,2/devicetree.img4' 'work/iBEC.img4' -> 'boot/iPhone8,2/iBEC.img4' 'work/iBSS.img4' -> 'boot/iPhone8,2/iBSS.img4' 'work/kernelcache.img4' -> 'boot/iPhone8,2/kernelcache.img4' 'work/trustcache.img4' -> 'boot/iPhone8,2/trustcache.img4' [] Sucess Patching the boot files [] Checking if the llb was already replaced [] Patching the llb in the ipsw to avoid false dfu mode [=] Hi, please i need that you write the ios version that this device is on or the version of the ios that it was on (if this device is already downgraded), most of the time is the lastest version of ios. write 0 if you want to skip this (it is not recommended to skip this as this can avoid false dfu mode) Version detected!. we are gonna use 15.8 [] LLB downloaded correctly [*] putting this LLB into the ipsw zip warning: Local Version Needed To Extract does not match CD: Firmware/ zip warning: Local Version Needed To Extract does not match CD: Firmware/AOP/ zip warning: Local Version Needed To Extract does not match CD: Firmware/all_flash/ updating: Firmware/all_flash/LLB.n66m.RELEASE.im4p (deflated 0%) zip warning: Local Version Needed To Extract does not match CD: Firmware/dfu/ zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/ zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/local/ adding: Firmware/all_flash//LLB.n66m.RELEASE.im4p (deflated 0%) *ERROR: ./downr1n.sh: line 1298: cd: too many arguments

touch boot/iPhone8,2/.llbreplaced

I just fixed the old error: TypeError: function missing required argument 'initial_buffer_values' (pos 2) And now, I got the new error: [] Command ran: sudo ./downr1n.sh --downgrade 14.0 [21:13:08.413][3] usbmuxd v1.1.1 starting up [21:13:08.414][3] Using libusb 1.0.25 [21:13:08.418][3] Initialization complete [21:13:08.419][3] Connecting to new device on location 0x30021 as ID 1 [21:13:08.419][3] Connected to v2.0 device 1 on location 0x30021 with serial number ramdisk tool Sep 18 2022 20:14:43 downr1n | Version 3.0 Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices [] Detected ramdisk mode device [] Rebooting device in SSH Ramdisk [21:13:09.426][2] device_control_input: Got unhandled payload type 5 [21:13:14.616][3] Removed device 1 on location 0x30021 [] Waiting for device in recovery mode [] Waiting for devices [] Detected recovery mode device [] Getting device info... Detected cpid, your cpid is 0x8003 Detected model, your model is n66map Detected deviceid, your deviceid is iPhone8,2 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (2) [] Device entered DFU! [-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no yes ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw [] Checking if the ipsw is for your device [] Checking ipsw version [] Extracting ipsw, hang on please ... [] Got extract the IPSW successfully [] Creating ramdisk [-] Ramdisk is already created so SKIPPING ... [] Booting ramdisk [/] We couldn't get the ipsw curl. we will proceed with -k option with curl usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [] Waiting for the ramdisk to finish booting libusb: warning [op_get_configuration] device unconfigured libusb: error [op_get_active_config_descriptor] device unconfigured [21:14:23.888][3] Could not get old configuration descriptor for device 3-41: LIBUSB_ERROR_NOT_FOUND [21:14:23.902][3] Connecting to new device on location 0x30029 as ID 2 [21:14:23.942][3] Connected to v2.0 device 2 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43 [21:14:23.942][2] device_control_input: Got unhandled payload type 5 [21:14:24.850][2] device_control_input: Got unhandled payload type 5 Error connecting to device: No error information [] Mounting filesystems ... [] Dumpped SHSH [] Checking device version the version that the device is currently in is 15.8 [] extracting kernel ... TypeError: function missing required argument 'initial_buffer_values' (pos 2) ^C yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3.9 -m pip uninstall pylzss lzss sudo: python3.9: command not found yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo python3 -m pip uninstall pylzss lzss WARNING: Skipping pylzss as it is not installed. Found existing installation: lzss 0.3 Uninstalling lzss-0.3: Would remove: /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Proceed (Y/n)? y Successfully uninstalled lzss-0.3 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv yenminh@yenminh-FMVD04001:/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main$ sudo ./downr1n.sh --downgrade 14.0 [] Command ran: sudo ./downr1n.sh --downgrade 14.0 [21:22:31.836][3] usbmuxd v1.1.1 starting up [21:22:31.836][3] Using libusb 1.0.25 [21:22:31.840][3] Initialization complete [21:22:31.841][3] Connecting to new device on location 0x30029 as ID 1 [21:22:31.841][3] Connected to v2.0 device 1 on location 0x30029 with serial number ramdisk tool Sep 18 2022 20:14:43 [-] lzss is not installed. we can installl it for you, press any key to start installing lzss, or press ctrl + c to cancel [21:22:32.849][2] device_control_input: Got unhandled payload type 5 Cloning into '/media/yenminh/MOBILE/DowngradeiOS Tethered with Linux/downr1n-main/downr1n-main/binaries/Linux/pylzss'... Note: switching to '8efcda0'.
You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 8efcda0 Merge pull request #8 from quiple/master running install /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools. warnings.warn( /usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 1.1build1 is an invalid version and will not be supported in a future release warnings.warn( /usr/lib/python3/dist-packages/pkg_resources/init.py:116: PkgResourcesDeprecationWarning: 0.1.43ubuntu1 is an invalid version and will not be supported in a future release warnings.warn( running bdist_egg running egg_info creating lzss.egg-info writing lzss.egg-info/PKG-INFO writing dependency_links to lzss.egg-info/dependency_links.txt writing top-level names to lzss.egg-info/top_level.txt writing manifest file 'lzss.egg-info/SOURCES.txt' reading manifest file 'lzss.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING' adding license file 'COPYING.LESSER' writing manifest file 'lzss.egg-info/SOURCES.txt' installing library code to build/bdist.linux-x86_64/egg running install_lib running build_ext building 'lzss' extension creating build creating build/temp.linux-x86_64-3.10 x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I./include -I/usr/include/python3.10 -c pylzss.c -o build/temp.linux-x86_64-3.10/pylzss.o pylzss.c:20:23: warning: ‘LZSS_P’ defined but not used [-Wunused-const-variable=] 20 | static const unsigned LZSS_P = 1; | ^~~~~~ creating build/lib.linux-x86_64-3.10 x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-Bsymbolic-functions -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.10/pylzss.o -o build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/egg copying build/lib.linux-x86_64-3.10/lzss.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/egg creating stub loader for lzss.cpython-310-x86_64-linux-gnu.so byte-compiling build/bdist.linux-x86_64/egg/lzss.py to lzss.cpython-310.pyc creating build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO copying lzss.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... pycache.lzss.cpython-310: module references file creating dist creating 'dist/lzss-0.3-py3.10-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it removing 'build/bdist.linux-x86_64/egg' (and everything under it) Processing lzss-0.3-py3.10-linux-x86_64.egg creating /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Extracting lzss-0.3-py3.10-linux-x86_64.egg to /usr/local/lib/python3.10/dist-packages Adding lzss 0.3 to easy-install.pth file
Installed /usr/local/lib/python3.10/dist-packages/lzss-0.3-py3.10-linux-x86_64.egg Processing dependencies for lzss==0.3 Finished processing dependencies for lzss==0.3 downr1n | Version 3.0 Created by edwin, thanks palera1, and all people creator of path file boot
[] Waiting for devices [] Detected ramdisk mode device [] Rebooting device in SSH Ramdisk [21:22:46.994][3] Removed device 1 on location 0x30029 [] Waiting for device in recovery mode [] Waiting for devices [] Detected recovery mode device [] Getting device info... Detected cpid, your cpid is 0x8003 Detected model, your model is n66map Detected deviceid, your deviceid is iPhone8,2 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (1) [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] Device entered DFU! [] Device entered DFU! [-] we found ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw, do you want to use it ? please write, yes or no yes ipsw/iPhone_5.5_14.0_18A373_Restore.ipsw [] Checking if the ipsw is for your device [] Checking ipsw version [] Extracting ipsw, hang on please ... [] Got extract the IPSW successfully [] Creating ramdisk [-] Ramdisk is already created so SKIPPING ... [] Booting ramdisk [/] We couldn't get the ipsw curl. we will proceed with -k option with curl usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [==================================================] 100.0% [] Waiting for the ramdisk to finish booting libusb: warning [op_get_configuration] device unconfigured libusb: error [op_get_active_config_descriptor] device unconfigured [21:24:18.665][3] Could not get old configuration descriptor for device 3-49: LIBUSB_ERROR_NOT_FOUND [21:24:18.670][3] Connecting to new device on location 0x30031 as ID 2 [21:24:18.719][3] Connected to v2.0 device 2 on location 0x30031 with serial number ramdisk tool Sep 18 2022 20:14:43 [21:24:18.719][2] device_control_input: Got unhandled payload type 5 [21:24:19.363][2] device_control_input: Got unhandled payload type 5 Error connecting to device: No error information [] Mounting filesystems ... [] Dumpped SHSH [] Checking device version the version that the device is currently in is 15.8 [] extracting kernel ... [] extracted Reboot into recovery mode ... [21:25:09.012][3] Removed device 2 on location 0x30031 [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] To get into DFU mode, you will be guided through 2 steps: [] Press any key when ready for DFU mode Get ready (0) Release power button, but keep holding home button (9) Release power button, but keep holding home button (3) [] Device entered DFU! [] Device entered DFU! [ ]Patching some boot files... [] Finished moving the boot files to work [] Decrypthing ibss and iboot usb_timeout: 5 [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: RESET ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: SETUP ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Stage: PATCH ret: true [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 CPID: 0x8003 Found the USB handle. Now you can boot untrusted images. [libusb] Waiting for the USB handle with VID: 0x5AC, PID: 0x1227 Found the USB handle. [] Patching the kernel [] Patching the kernel to restore using futurerestore [] Patching devicetree [] Patching the restored_external and asr, and saving them into the ramdisk ... 'work/devicetree.img4' -> 'boot/iPhone8,2/devicetree.img4' 'work/iBEC.img4' -> 'boot/iPhone8,2/iBEC.img4' 'work/iBSS.img4' -> 'boot/iPhone8,2/iBSS.img4' 'work/kernelcache.img4' -> 'boot/iPhone8,2/kernelcache.img4' 'work/trustcache.img4' -> 'boot/iPhone8,2/trustcache.img4' [] Sucess Patching the boot files [] Checking if the llb was already replaced [] Patching the llb in the ipsw to avoid false dfu mode [=] Hi, please i need that you write the ios version that this device is on or the version of the ios that it was on (if this device is already downgraded), most of the time is the lastest version of ios. write 0 if you want to skip this (it is not recommended to skip this as this can avoid false dfu mode) Version detected!. we are gonna use 15.8 [] LLB downloaded correctly [] putting this LLB into the ipsw zip warning: Local Version Needed To Extract does not match CD: Firmware/ zip warning: Local Version Needed To Extract does not match CD: Firmware/AOP/ zip warning: Local Version Needed To Extract does not match CD: Firmware/all_flash/ updating: Firmware/all_flash/LLB.n66m.RELEASE.im4p (deflated 0%) zip warning: Local Version Needed To Extract does not match CD: Firmware/dfu/ zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/ zip warning: Local Version Needed To Extract does not match CD: Firmware/usr/local/ adding: Firmware/all_flash//LLB.n66m.RELEASE.im4p (deflated 0%) *ERROR: ./downr1n.sh: line 1298: cd: too many arguments

touch boot/iPhone8,2/.llbreplaced

Well, what is this mean?
I'm a beginner that can't understand it. Can you to be more specific?


Add image column in configurable products for variants

For variants products, there should be an image column must be available in parent/configurable product

This repository is only for reporting bugs or issues. If you need support, please use
other channels:

Write an email -<EMAIL_ADDRESS>

Create support ticket on https://bagisto.uvdesk.com

Visit forums to get support from our community (https://forums.bagisto.com)

Alternatively, you may use Facebook (https://www.facebook.com/groups/bagisto/).
We promise that more channels are coming soon!!!

Same Issue and it is mandatory

Hi @vaishaliwebkul on choosing variations images need to be change according to chosen variation. Is their any way to do so. Currently I have tried to do it but I can find any clue to do that.

@musawirjon
please specify your current bagisto version?

it's latest one. v1.2.0

Please see the screenshot for what functionality I need in here.
https://prnt.sc/ya5fp1

@musawirjon
Thanks for reporting this, could you please raise a new issue which you're getting right now, as this issue in which you have commented is different and marked as enhancement.

Those are products I imported from aliexpress. and also for variation url key and images aren't importing. If I want to change something in variation then I have to manually do that with description, url_slug, images, and any other required by editing variation.
But I have tons of products and most product has more then 10 variants. So would be much ease if bagisto aliexpress dropship extension could import those things as well.

@musawirjon
Thanks for reporting this, could you please raise a new issue which you're getting right now, as this issue in which you have commented is different and marked as enhancement.

Yes please add a ticket for it. As this is what I am trying to do it by my-self from almost 6 days.

@musawirjon
please get an update with this issue link https://github.com/bagisto/bagisto/issues/4558 in which I have mentioned the issue you're getting.


[WIP] Pmtiles implementation

Requires #516 and #511
Incomplete implementation of #508

Codecov Report
Base: 60.42% // Head: 58.95% // Decreases project coverage by -1.46% :warning:

Coverage data is based on head (50cb711) compared to base (18d65a2).
Patch coverage: 50.19% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #517      +/-   ##
==========================================
- Coverage   60.42%   58.95%   -1.47%
==========================================
  Files          23       27       +4
  Lines        1933     2171     +238
==========================================
+ Hits         1168     1280     +112
- Misses        765      891     +126

Impacted Files
Coverage Δ

src/lib.rs
42.97% <ø> (-1.14%)
:arrow_down:

src/pmtiles/utils.rs
0.00% <0.00%> (ø)

src/source.rs
82.85% <0.00%> (ø)

src/pmtiles/source.rs
32.20% <32.20%> (ø)

src/pmtiles/config.rs
36.95% <36.95%> (ø)

src/config.rs
63.38% <72.72%> (+5.56%)
:arrow_up:

src/file_config.rs
79.16% <79.16%> (ø)

src/utils/utilities.rs
55.29% <84.61%> (+3.29%)
:arrow_up:

src/args/pg.rs
83.45% <100.00%> (-0.58%)
:arrow_down:

src/args/root.rs
92.85% <100.00%> (+0.14%)
:arrow_up:

... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Prevent crash with Noice

Hi!
I'm the author of noice.nvim and I'm currently investigating issues with Noice withing Guis.
There's currently a Neovim issue that prevenst Noice to work with GUIs with multigrid enabled, but I have an upstream PR for that already.
With that fix, Goneovim still crashes, since it will potentially receive cmdline and messages events, while the settings for that are disabled.
I assume that's because Goneovim tries to process the event, but didnt do internal setup first.
Goneovim should skip messages and cmdline events when it's not configured in it's settings I think.
Thank you!

crash report
❯ panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x762eae]
goroutine 1 [running, locked to thread]:
github.com/akiyosi/goneovim/editor.(*Message).msgShow(0x0, {0xc0003f69d0, 0x1, 0x55c565?})
github.com/akiyosi/goneovim/editor/message.go:291 +0x1ee
github.com/akiyosi/goneovim/editor.(*Workspace).handleRedraw(0xc00016e000, {0xc00017e0b0?, 0x7, 0xc00014ee78?})
github.com/akiyosi/goneovim/editor/workspace.go:1594 +0x385
github.com/akiyosi/goneovim/editor.(*Workspace).registerSignal.func1()
github.com/akiyosi/goneovim/editor/workspace.go:341 +0xb7
github.com/akiyosi/goneovim/editor.callbackworkspaceSignalada841_RedrawSignal(0xc0000021a0?)
github.com/akiyosi/goneovim/editor/moc.go:4097 +0x3c
github.com/akiyosi/goneovim/editor._Cfunc_workspaceSignalada841_EventDefault(0x2d08f40, 0x7efbf8003f50)
_cgo_gotypes.go:6970 +0x49
github.com/akiyosi/goneovim/editor.(*workspaceSignal).EventDefault.func1(0x8?, {0x14425b8?, 0xc0000e6d28?})
github.com/akiyosi/goneovim/editor/moc.go:4711 +0x9f
github.com/akiyosi/goneovim/editor.(*workspaceSignal).EventDefault(0x2d08f40?, {0x14425b8?, 0xc0000e6d28?})
github.com/akiyosi/goneovim/editor/moc.go:4711 +0x37
github.com/akiyosi/goneovim/editor.callbackworkspaceSignalada841_Event(0x54cee6?, 0x7efbf8003f50)
github.com/akiyosi/goneovim/editor/moc.go:4706 +0xf1
github.com/therecipe/qt/widgets._Cfunc_QApplication_QApplication_Exec()
_cgo_gotypes.go:2602 +0x48
github.com/therecipe/qt/widgets.QApplication_Exec(...)
github.com/therecipe/qt/widgets/widgets-minimal.go:2934
github.com/akiyosi/goneovim/editor.InitEditor({{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, {0x7ffcbb6e1387, 0x10}, {0x0, 0x0}, ...}, ...)
github.com/akiyosi/goneovim/editor/editor.go:392 +0xec5
main.main()
github.com/akiyosi/goneovim/cmd/goneovim/main.go:72 +0x1bb

@folke
Hi :)
Thanks for this issue report.
I investigated the implementation and found that goneovim was not implemented with the expectation that other UIs would enable ext-options.
I have fixed this issue in https://github.com/akiyosi/goneovim/commit/5deb344616313bb848cff1c26f494cbcf924b383.
By the way, noice.nvim is a great plugin.
ext-options in Neovim has been used only by a very few GUIs and is a rarely used feature.
I hope that as noice.nvim becomes more popular, the UI externalization feature with ext-options will become more sophisticated.

That's awesome, thanks!
Now wait till my upstream PR gets merged :)

@akiyosi thanks for https://github.com/akiyosi/goneovim/commit/5deb344616313bb848cff1c26f494cbcf924b383 and  releasing nightly build with it.

The upstream PR got merged, so closing this. Thanks again!


Error: Cannot find module 'webpack-cli/bin/config-yargs'[webpack-cli] Error: Cannot find module 'webpack/lib/BasicEvaluatedExpression'

Bug report

What is the current behavior?
1.
[webpack-cli] Error: Cannot find module 'webpack/lib/BasicEvaluatedExpression'

Error: Cannot find module 'webpack-cli/bin/config-yargs'

What is the expected behavior?
No errors should occur when using "webpack-cli" and "webpack-dev-server"

Other relevant information:
webpack version:  5.37.0
Node.js version: 14.15.4
Operating System:
Linux localhost 4.19.113-perf-g8fa0212 #1 SMP PREEMPT Fri Apr 23 02:52:00 CST 2021 aarch64 Android
Additional tools:
https://github.com/masx200/webpack-react-vue-spa-awesome-config
If the current behavior is a bug, please provide the steps to reproduce.
~ $ cd webpack-react-vue-spa-awesome-config             ~/webpack-react-vue-spa-awesome-config
$ cat package.json
{
"types": "./release/config/webpack.config.d.ts",
"type": "commonjs",
"version": "2.8.2",
"publishConfig": {
"registry": "https://registry.npmjs.org/"
},
"bin": "./bin/index.js",
"main": "./release/config/webpack.config.js",
"scripts": {
"start": "webpack-dev-server  --config ./release/config/webpack.config.js  --mode=development",
"build": "webpack  --config ./release/config/webpack.config.js     --mode=production",
"rollup": "rollup -c rollup.config.js",
"prettier": "prettier --write **/.ts .md .json **/.js   .js .ts ./cli/src/.js ./release/config/.js **/.css **/.html",
"test1": "node ./bin/index.js start",
"test2": "node ./bin/index.js --mode=development",
"test3": "node ./bin/index.js build"
},
"name": "@masx200/webpack-react-vue-spa-awesome-config",
"license": "MIT",
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
},
"dependencies": {
"@babel/core": "^7.14.0",
"@babel/plugin-proposal-class-properties": "^7.13.0",
"@babel/plugin-proposal-decorators": "^7.13.15",
"@babel/plugin-syntax-dynamic-import": "^7.8.3",
"@babel/preset-env": "^7.14.1",
"@babel/preset-react": "^7.13.13",
"@babel/runtime": "^7.14.0",
"@types/html-webpack-plugin": "^3.2.5",
"@types/mini-css-extract-plugin": "^1.4.3",
"@types/node": "^15.0.2",
"@types/optimize-css-assets-webpack-plugin": "^5.0.3",
"@types/react": "^17.0.5",
"@types/terser-webpack-plugin": "^5.0.3",
"@types/webpack": "^5.28.0",
"@types/workbox-webpack-plugin": "^5.1.6",
"babel-loader": "^8.2.2",
"babel-plugin-htm": "^3.0.0",
"babel-plugin-named-asset-import": "^0.3.7",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-react-app": "^10.0.0",
"banner-content-loader": "^0.1.1",
"clean-webpack-plugin": "^4.0.0-alpha.0",
"css-loader": "^5.2.4",
"fast-sass-loader": "^2.0.0",
"file-loader": "^6.2.0",
"html-webpack-plugin": "^5.3.1",
"json-loader": "^0.5.7",
"less": "^4.1.1",
"less-loader": "^8.1.1",
"mini-css-extract-plugin": "^1.6.0",
"node-sass": "^6.0.0",
"optimize-css-assets-webpack-plugin": "^5.0.4",
"postcss": "8.2.15",
"postcss-flexbugs-fixes": "^5.0.2",
"postcss-loader": "^5.2.0",
"postcss-normalize": "^10.0.0",
"postcss-preset-env": "^6.7.0",
"postcss-safe-parser": "^5.0.2",
"purgecss-webpack-plugin": "4.0.3",
"purify-css": "^1.2.5",
"purifycss-webpack": "^0.7.0",
"react-app-polyfill": "^2.0.0",
"react-hot-loader": "^4.13.0",
"regenerator-runtime": "^0.13.7",
"sass": "1.32.12",
"style-loader": "^2.0.0",
"terser": "^5.7.0",
"terser-webpack-plugin": "^5.1.1",
"to-string-loader": "^1.1.6",
"uglifyjs-webpack-plugin": "^2.2.0",
"unicode-loader": "^1.0.7",
"url-loader": "^4.1.1",
"vue-loader": "^15.9.7",
"vue-style-loader": "^4.1.3",
"vue-template-compiler": "^2.6.12",
"webpack": "^5.37.0",
"webpack-cli": "^4.7.0",
"webpack-copyfiles-plugin": "^1.0.9",
"webpack-deep-scope-plugin": "^1.6.2",
"webpack-dev-server": "^3.11.2",
"workbox-webpack-plugin": "^6.1.5",
"worker-loader": "3.0.8"
},
"devDependencies": {
"@rollup/plugin-babel": "5.3.0",
"@rollup/plugin-commonjs": "^19.0.0",
"@rollup/plugin-json": "^4.1.0",
"@rollup/plugin-node-resolve": "^13.0.0",
"acorn": "^8.2.4",
"core-js-pure": "^3.12.1",
"event-target-shim": "^6.0.2",
"lodash": "^4.17.21",
"minimist": "^1.2.5",
"prettier": "^2.3.0",
"react": "^16.13.1",
"rollup": "^2.47.0",
"rollup-plugin-babel": "^4.4.0",
"rollup-plugin-terser": "^7.0.2",
"serialize-javascript": "^5.0.1",
"tslib": "2.2.0",
"typescript": "^4.2.4",
"vue": "^2.6.11",
"yargs-parser": "20.2.7"
},
"repository": "https://github.com/masx200/webpack-react-vue-spa-awesome-config.git",
"author": "masx200<EMAIL_ADDRESS>"description": "极速、零配置的 web 应用打包工具, 同 时支持 react 和 vue 的单页面应用,提供开箱即用支持  Fast, zero-configuration web application packaging tool that supports both single-page applications for react and vue, out-of-the-box support， 基于 webpack4.x,同时支持 react 和 vue 的单页面应用 通用的 webpack 配置文件,提供开箱即用支持 ，您无需学习和配置许多构建工具。即时重新加载可帮 助您专注于开发。在部署时，您的捆绑包会自动优化",
"peerDependencies": {
"react": "16.13.1",
"vue": "2.6.12"
},
"optionalDependencies": {
"react": "17.0.2",
"vue": "2.6.12"
}
}
~/webpack-react-vue-spa-awesome-config
$ yarn start
yarn run v1.22.10
warning package.json: "optionalDependencies" has dependency "react" with range "17.0.2" that collides with a dependency in "devDependencies" of the same name with version "^16.13.1"
warning package.json: "optionalDependencies" has dependency "vue" with range "2.6.12" that collides with a dependency in "devDependencies" of the same name with version "^2.6.11"
$ webpack-dev-server  --config ./release/config/webpack.config.js  --mode=development
internal/modules/cjs/loader.js:883
throw err;
^
Error: Cannot find module 'webpack-cli/bin/config-yargs'
Require stack:

/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-dev-server/bin/webpack-dev-server.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-dev-server/bin/webpack-dev-server.js:65:1)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-dev-server/bin/webpack-dev-server.js'
]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
~/webpack-react-vue-spa-awesome-config

$ yarn build
yarn run v1.22.10
warning package.json: "optionalDependencies" has dependency "react" with range "17.0.2" that collides with a dependency in "devDependencies" of the same name with version "^16.13.1"
warning package.json: "optionalDependencies" has dependency "vue" with range "2.6.12" that collides with a dependency in "devDependencies" of the same name with version "^2.6.11"
$ webpack  --config ./release/config/webpack.config.js     --mode=production
输入的参数:
[
"/data/data/com.termux/files/usr/bin/node",
"/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/.bin/webpack",
"--config",
"./release/config/webpack.config.js",
"--mode=production"
]
解析的参数:
{
"mode": "production"
}
webpack config filename : /data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/release/config/webpack.config.js
working directory : /data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config
webpack mode : production
[webpack-cli] Failed to load '/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/release/config/webpack.config.js' config
[webpack-cli] Error: Cannot find module 'webpack/lib/BasicEvaluatedExpression'
Require stack:

/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-copyfiles-plugin/index.js
/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/release/config/webpack.config.js
/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/lib/webpack-cli.js
/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/lib/bootstrap.js
/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/bin/cli.js
/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack/bin/webpack.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object. (/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-copyfiles-plugin/index.js:26:34)
at Module._compile (/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-copyfiles-plugin/index.js',
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/release/config/webpack.config.js',
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/lib/webpack-cli.js',
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/lib/bootstrap.js',
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack-cli/bin/cli.js',
'/data/data/com.termux/files/home/webpack-react-vue-spa-awesome-config/node_modules/webpack/bin/webpack.js'
]
}
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
~/webpack-react-vue-spa-awesome-config $

For maintainers only:

[ ]  webpack-4
[x]  webpack-5
[x]  bug
[x]  critical-bug
[ ]  enhancement
[ ]  documentation
[ ]  performance
[ ]  dependencies
[ ]  question

Update webpack-cli to the latest version and change "start": "webpack-dev-server --config ./release/config/webpack.config.js --mode=development", to "start": "webpack serve --config ./release/config/webpack.config.js --mode=development",
In future please use github repos, your problem is not readable

Also please report problem in webpack-copyfiles-plugin for webpack v5 compatibility, but I recommend to use https://github.com/webpack-contrib/copy-webpack-plugin


recursive binary operator problem

		describe("iterative factorial", () => {
			/*ts
				factIter	:.((].=0 [) .(*$ ].-1).(factIter$))?
				fact		1factIter
			*/
			it(`fact(4)=24`, () => expect(fact(4)).eql(24));
		});

Error: Unable to resolve dynamic function application: 1(Fn)
  Evaluating http://<IP_ADDRESS>:5500/test/logic/main.js
  Loading test/logic/main.js

So this issue came up again in trying to determine a binary recursive gcd (greatest common denominator) operator.
During the investigation, it became apparent that recursive binary operators cannot currently be supported.
The problem is that we cannot determine, or defer determination, of the type of a recursive operator. There is an existing hack in which we force the type of a recursive operator to VV - so trying to define a recursive binary operator will fail.
Tried some different approaches (deferring the determination, or using mutually recursive functions) - but these failed. I'm not sure if this is a tractable problem - but interesting if there is a solution.

This problem has been inverted.
Now we can only define binary recursive operators. The reason we can't support both is that currently there is no way to determine the type of an operator defined recursively. We cannot work it out and cannot defer that calculation. So the way the function applies fails.
We used to have a hack that encases recursive definitions in a x => (function body)(x) - this fails for binary operators.
Since it's easier to support unary operators as a special case of binary operators (the reverse is not possible) - we currently support only binary operator recursion.
Also note, that to help resolution, we have to give a few type signature guesses for the operator. These are currently: (VVV)VV, (VV)VV and VVV.
Tried extending supported types to binary operators. This does not work.
Can we ever support both binary and unary operator recursion?


Participants to be able to request read/write access in live share

Hi,
I was thinking of using the Live Share option in a coding workshop. I would like for participants to be able to request read/write access. Is it possible to allow participants to request read/write access that the person who started the Live Share session then approves or denies?
Thanks!

Please file an issue in the extension's repository. Thank you!


A fix for the <?php thing

Unfortunately removing open and close tags will not work.
As you show in example.
I have tested on a script and it does not good.
I am using this fix in your Obfuscator class.
    public function __construct($sData, $sName)
    {
        $this->sName = $sName;
        $this->sData = $sData;
        if (substr($this->sData, 0, 5) == '<?php') {
            $this->sData = substr($this->sData, 5);
        }

Hi again @halojoy
Please remove the PHP open/close tags before calling the class like I show you (my example works).
https://github.com/pH-7/Obfuscator-Class#example-3
Happy New Year's Eve
Good luck!

Hi again @halojoy
Please remove the PHP open/close tags before calling Obfuscator class like I show you (my example works).
$sData = str_replace(array('<?php', '<?', '?>'), '', $sData); // Strip PHP open/close tags
$sObfusationData = new Obfuscator($sData, 'My Class'); // Now, I instance the class!

https://github.com/pH-7/Obfuscator-Class#example-3
Happy New Year's Eve
Good luck!

And don't forget to Star the repo 😺

And don't forget to Star the repo 😺  @halojoy


Add pre-commit hooks

@DaniilKl This config now matches the one in meta-dts. The PR is redy for another review.

@macpijan

Do we base on: https://github.com/3mdeb/hooks/tree/main/pre-commit-init ? We have a python script allowing to setup hooks for new repo from common base.

Yes, the base config came from that repo, with some repo-specific changes to codespell and shellcheck. I didn't use the script, but it seems pretty straightforward. I can add a new yocto category with the oelint-adv config to the script.

Good work, thanks.


parse_corpus crashes with

After trying to run the tutorial a couple of time, I must have somehow corrupted the db, the cp.parse_corpus crashes (after all sentences are parsed) with the following error
IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: context.stable_id [SQL: u'INSERT INTO context (type, stable_id) VALUES (?, ?)'] [parameters: ('document', u'c9843f4e-9c43-4eca-9665-37aef78f5ea3::document:0:0')]

Removing the database and restarting will fix this (probably), but, it's a bit annoying because parsing the document takes a while.

Hi @Gijs-Koot ,
This is just the database throwing a unique error because you're trying to re-insert the same document or sentence presumably.  We don't want to assume that if you try to insert a document/sentence/etc. with the same ID, it's the same document, because this can lead to bad (silent) issues...
Deleting all rows from the corresponding table, or creating a new db will fix this.
But it's on our list to put some nicer options here to make it easy e.g. if you know you just want to restart preprocessing.  Stay tuned and thanks for the patience!
-Alex

Closed in v0.5.0

how can we insert two different contexts in two individuals rows without replacing the old context document?


Random tweet button in example is broken

The "Click here to get a random tweet" button is broken in the Next.js example.

@DaniGuardiola is this still broken for you?
It's working for me in prod https://react-static-tweets.vercel.app/

Yep, it's still broken locally for me, both when using yarn dev and yarn build && yarn start. Seems like the api call is returning a 404 (that HTML code is the default Next 404 page).
I'm going to close this issue for now since it's working in production.

Ah, okay, gotcha. Maybe that could be briefly documented somewhere.


fix: fixed modal and integration tests

Pull Request Test Coverage Report for Build 200

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 75.039%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Modal/index.js
2
3
66.67%

Totals

Change from base Build 195:
-0.5%

Covered Lines:
1119

Relevant Lines:
1422

💛  - Coveralls


Better styling for tree grids in Excel exports

Excel exports for tree grids include the hierarchy in the form of expand/collapse group buttons, but the default Excel table styling does not make it clear which level a row is at.  (Instead it uses the banded rows throughout).
Client asks if its possible to make the export styling more clear w.r.t. different levels in the tree.

I figured out how to get POI to set row background color, and used that to alternate the table colors based on tree depth.

We can discuss of this helps improve readability, or if a different approach could be more usable.
PR here: https://github.com/xh/hoist-core/pull/135

Here is an alternate coloring approach that blends between blue and white based on tree depth:

Concern here is it that it the color distinction may become insignificant if your tree has many levels

Hi Tom -- I think the alternating is more confusing -- like the blending idea alot!!
Seems like you could start the root depth a bit darker.  Am all for taking this change and closing this ticket.


Recipes of new Japanese singing voice databases

Hello, I made some recipes of Japanese singing voice databases.

Ofuton P Utagoe DB (singing voice database) (male) [1]
Yuuri Natsume's singing voice database (male) [2]
Oniku Kurumi Utagoe DB (female) [3]

There are some known issues:
(1)  These databases have some mismatches between HTS mono-phone label files and musicxml files(especially Yuuri Natsume's singing voice database), so I borrowed the python codes  from kiritan_singing[4] to keep their consistency.
(2) The term of service of these singing voice databases are written in Japanese only, so it may be difficult for non-Japanese speaker to agree their license.
(3) Some of these databases contain the label of unvoiced vowels and make use of the modified version of sinsy dictionary.  The copyright notice of the dictionary is under egs/{ofuton_p_utagoe_db, natsume_singing, oniku_kurumi_utagoe_db}/dic/COPYING.

https://sites.google.com/view/oftn-utagoedb/ホーム
https://amanokei.hatenablog.com/entry/2020/04/30/230003
http://onikuru.info/db-download/
https://github.com/r9y9/kiritan_singing

As far as I know, sinsy requires all japanese dictionaries even if we don't use them[1], because src/lib/converter/ConfManager.cpp reads them in parallel[2].  If we want to delete the unnecessary dictionaries, we have to hack sinsy first of all(it may be quite easy).

https://gist.github.com/taroushirani/02e9eeba57cbd6265e7d00e2ccbcc405
https://github.com/r9y9/sinsy/blob/31e372e61ac83a15cb48a6d2bdbcb5e64df60b97/src/lib/converter/ConfManager.cpp#L134

It will be easy for us to unify the modified sinsy dictionaries for unvoiced vowels, but the python codes are customized for each singing voice databases to absorb the differences such as directory structure, time unit, handling of "cl" phoneme and so on.  I'll need some more time to unify them.

Ah I see..... For the dictionary issues, it could be fixed on the sinsy side. It's okay to keep as is.

It will be easy for us to unify the modified sinsy dictionaries for unvoiced vowels, but the python codes are customized for each singing voice databases to absorb the differences such as directory structure, time unit, handling of "cl" phoneme and so on. I'll need some more time to unify them.

It's okay If there's a reason to do this. We can revisit it in the future if we might want to improve. Thanks for your explanation.
Let me know once you think it is good to go. I will merge this PR.

BTW, I like the idea using the yaml config for run.sh. (looks like you are using https://stackoverflow.com/questions/5014632/how-can-i-parse-a-yaml-file-from-a-linux-shell-script?). How about putting it into https://github.com/r9y9/nnsvs/tree/master/utils?

Thank you for your comments.  I used "--alow-unrelated-histories" option to preserve log when importing the recipes from my own repositories, but I noticed that this may destroy the repository when someone use git rebase.  I'll submit PR from the another branch which is newly created.


Crash in MutableLiveQueue

There is crash in MutableLiveQueue, please look at the stack trace below
java.lang.NullPointerException: Attempt to invoke interface method 'void androidx.lifecycle.Observer.onChanged(java.lang.Object)' on a null object reference
at com.spotify.mobius.android.MutableLiveQueue.lambda$post$0(MutableLiveQueue.java:124)
at com.spotify.mobius.android.-$$Lambda$MutableLiveQueue$vOf0H-vBAqo2vnbWBOWfiBCGWLc.run
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:198)
at android.app.ActivityThread.main(ActivityThread.java:6732)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Hi, thank you for the report, I've opened a PR to address this issue here: https://github.com/spotify/mobius/pull/130

Thanks for putting up the PR

Hi sorry for delayed response, but the fix for this has been merged, and should be available in the next release of the library.

Hi @kapilsukhyani - I just noticed this issue is still open. Can you confirm that the fix that was merged has addressed your issue so we can close this?

Hey @milchopenchev , we just have consumed the fix, will see if we get any reports of this issue and if not I will update here again for you to close the issue.
Thanks!


Please add details as how can CPUs can be limited for RHEL

File: engine/admin/resource_constraints.md, CC @mstanleyjones

Hi, I'm not sure what you mean. These settings are not distribution-specific. Did you notice https://docs.docker.com/engine/admin/resource_constraints/#cpu on the page you linked? If this isn't answering your questions, please provide more details. Thanks!

I'd use cgroups aimed at the particular container.

@trapier @cpuguy83 do you have any insight into that approach?

I don't think there's anything to do here.
Docs are correct for any distribution.

Thanks, @srkadiyala - just use the standard commands. :)


Support FreeBSD

Is your feature request related to a problem? Please describe.
https://twitter.com/HackacadNet/status/1419267845704323080
Describe the solution you'd like
Upstream changes, provide a distribution.
Additional context
Not sure what it takes to do a FreeBSD distribution, but at the very least no code changes should be required.

Not sure about the roadmap (separate packages for very os/distro? rpm, pkg, deb etc.), but imho the shebang fixes should be done during packaging. RC scripts can be added anyway.

I added some basic checks and env in the following PRs.
This would help to create a FreeBSD port.
https://github.com/opensearch-project/OpenSearch/pull/1013
https://github.com/opensearch-project/OpenSearch/pull/1014
https://github.com/opensearch-project/OpenSearch-Dashboards/pull/678

Hello!
Overview of FreeBSD ports and packages
For some years now, FreeBSD provide packages for the ports: users do not need to compile all software they want to use anymore, they can just install packages using the pkg command.
The ports are basically a recipe to handle build dependencies, download the source code of a program, compile it, install it, and generate a package.  The FreeBSD packages are built using the ports in the FreeBSD ports tree.  New packages are built regularly (weekly), FreeBSD basically follow a rolling release pattern: new software is published ⇒ the port is updated ⇒ a new package is available.
For this reason, I would recommend not to try to ship FreeBSD packages on the OpenSearch website, but make it easier for FreeBSD contributors to maintain a port of OpenSearch which will make OpenSearch available as a regular package for all FreeBSD users.
Packaging of OpenSearch
For Java applications, the process described above is often a bit different: build dependencies are sometimes tedious to manage at the port level, and since java code is portable (can run on any platform with a JVM), a lot of FreeBSD ports for Java application download an artifact from the vendor and not the source code.  The port maintainer has then just to manage dependencies, ensure the right files are placed at the right place, manage rc.d scripts and it is basically all: no "compilation" step is required.  A drawback is of course if some modification of the source is required, then the maintainer has no real other choice than integrate the change with upstream and wait for the next release.
The FreeBSD packages shipped by FreeBSD are built using a set of "default" options which a user can override by compiling their ports (in the old-school way, before we had packages), or building their own packages.  This can be useful for example to use a specific version of say python, ruby, PostgreSQL, java and so on.
This mean that an OpenSearch FreeBSD package will not ship with a JVM.  The port will say "You need at least Java X", the FreeBSD port will be built with Java Y so the package will have a dependency on Java Y, and user will be able to build their packages using Java Z if that is what they want/need.
So, the tarball made available for 1.0.0 basically fit as a FreeBSD "source" tarball, even if it bundle a lot of thing we do not care about (mainly the non-portable stuff that lead you to ship multiple packages for different architectures).
Maybe a "lite" / "portable" tarball which does not bundle java and sample certificates would be a better fit, avoiding to download unneeded data?

Packaging of OpenSearch-Dashboards
Just like OpenSearch, a FreeBSD package would not bundle node.
Currently, as far as I understand, the kibana package is built using the kibana-7.14.0-darwin-x86_64.tar.gz archive as a source, applying some local patches on top of it, and rebuilding the shipped node libraries (which contain some C/C++ that has to be rebuilt).
This look quite ugly, but I am not aware of a cleaner way for projects in JS which include some C/C++ code (I do not hack in JS at all).
We can probably apply a similar strategy for opensearch-dashboards?
I am available for chatting about this :smile: Thanks!
(I try to attend the Community Meeting)

I'm going to un-assign myself and @nknize because we're not working on this, but I think we do have most bits and pieces to make this happen. I would start by trying to building the bundle from the top on FreeBSD and opening specific issues, such as "remove JDK in opensearch-min on FreeBSD". If anyone wants to take it on, I'd be happy to help/review PRs.

Note that the OpenSearch PRs @hackacad made (thanks!) were merged. The one on dashboards is still open, but hopefully soon.

We are working with @hackacad in a fork of the FreeBSD ports repo to complete the opensearch and opensearch-dashboards ports (opensearch branch):
https://github.com/smortex/freebsd-ports/tree/opensearch
We probably still have a few minor issues, but while I am typing, I could pkg install opensearch opensearch-dashboard in a jail and ingest data.  So I expect we will be able to commit this soon in the official FreeBSD ports tree.

We are working with @hackacad in a fork of the FreeBSD ports repo to complete the opensearch and opensearch-dashboards ports (opensearch branch):
https://github.com/smortex/freebsd-ports/tree/opensearch
We probably still have a few minor issues, but while I am typing, I could pkg install opensearch opensearch-dashboard in a jail and ingest data. So I expect we will be able to commit this soon in the official FreeBSD ports tree.

Well, this is ... rad. :shipit:

[Traige] @dblock What should we require to resolve this issue, do we need the whole distribution or just min?

@peternied if I am right, the minimal archives do not include plugins such as the security which is definitively something we want to have support for on FreeBSD.
For now, the WIP port is based on the "full" Linux distribution and ignore the non-portable content.  The port is being tested by a few people who are working on it, we still have a few minor things to tweak but I think that we will commit it to the FreeBSD ports tree soon™ :wink:
PR: https://github.com/smortex/freebsd-ports/pull/3
I can follow-up here when we have committed the port and it is available to all FreeBSD users and request the issue to be closed?

@dblock, @peternied the ports have just been committed to the FreeBSD ports tree:
https://cgit.freebsd.org/ports/commit/?id=7fe660d7479c2a88f1c3aac267470f2a507757a0
https://cgit.freebsd.org/ports/commit/?id=19e156d5142115dcd542d47ee329a2656798d789
User of FreeBSD can now build OpenSearch and OpenSearch-Dashboards, and in a few days packages should be available for them.
Do you want we add some kind of installation instructions for FreeBSD on the OpenSearch website?
And I think this issue can now be closed.

Yes, we should! @smortex those docs are https://github.com/opensearch-project/project-website, and I think we should spell out how to install on FreeBSD.
Also, after 1.1 is released, what's there to do to make a FreeBSD release? We should have those instructions somewhere (maybe here)?

Yes, we should! @smortex those docs are opensearch-project/project-website, and I think we should spell out how to install on FreeBSD.

Here we go: https://github.com/opensearch-project/project-website/pull/321

Also, after 1.1 is released, what's there to do to make a FreeBSD release? We should have those instructions somewhere (maybe here)?

We have setup a FreeBSD OpenSearch Team composed of both committers and external contributors (and this group will be happy to see more contributors).  So we will try to keep the port updated in a timely fashion when a new release is available.  The process being open, if people think we are too slow, they can work themself on the update and propose the change.  This whole process is documented in the FreeBSD Porter's Handbook, the most relevant sections being:

Upgrading a Port
Submitting the New Port

Thanks!

@smortex 🚀 I've made a placeholder for releasing OpenSearch here. We'll be populating this with a ton of things that we do before a release. Care to add a "Releasing for FreeBSD" section?

@stockholmux Could you update when we have next steps?

@peternied Based on the udpate to #546, I think we're good to go on this.

Let's close this! @smortex thank you & everyone else who contributed.


[FLINK-11404][web] add load more feature in exception page

What is the purpose of the change
ref https://issues.apache.org/jira/browse/FLINK-11404
Brief change log
support more metric display at once
Verifying this change

Submit a failover job
Go to the exception (more than 10 exceptions)
check if the load more button works

before:

after:

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)

I am reviewing this but it would be good if someone with more experience in TypeScript can give it another pass.

I am reviewing this but it would be good if someone with more experience in TypeScript can give it another pass.

Hi @sorahn
do you have time to take a look?

Merging.


A question about the design choice - sparse mm vs scatter

Thanks for the great library! This is a question regarding to the design choices of using "indexing+ scatter" as the message propagation operator (in many cases can be expressed as AH where A is a sparse adj matrix, and H is dense node hidden state matrix). And the sparse mm is only utilized few times. I was wondering if this is due to the efficiency concerns, or simply API convenience? Could you please elaborate? Thanks in advance!

Hi, there is not a single place in PyG where we use spmm instead of gather and scatter. Thus is due one the one hand due to efficiency, on the other it allows fir a more flexible message passing (e.g. integrating edge features). Please see Appendix A of our paper for more details.

hi @rusty1s , thanks for the clarification !
Could you provide additional hints on why the gather+scatter scheme "can still be improved" for dense graph settings ?

Hi,
scatter ops rely on atomic operations, which ideally run in constant time. However, with higher degrees, you have more threads which want to write the same storage (which slows down scatter ops and favors sparse matmuls).

Hmm ok I see, that makes sense ! Thanks for the clarification !


Ability to delete/unregister druid nodes

Use case: When I select different characters in my game, I create GUI nodes to display all the skills they have. If I register them as druid buttons, I could display information about the skills as a tooltip. When I switch the characters and delete the associated nodes, I get an error.

Hello!
druid:remove should work well. Which type of error you get?
Druid will no delete gui nodes, you will do it by yourself, but druid components can be deleted with druid:remove

Thanks for the response! Sorry, I didn't find druid:remove in the documentation so I didn't realise it existed. Just testing it now and I am getting errors anyway.
I wrote this test:
        local test = gui.new_box_node(vmath.vector3(100,100,0), vmath.vector3(100,100,0))
	gui.set_id(test, "test")
	self.druid:new_button("test", function()print("press!") end)

	timer.delay(2,false,function()
		self.druid:remove("test")
	end)

I get this error:

ERROR:SCRIPT: /druid/system/druid_instance.lua:211: attempt to call method 'get_interests' (a nil value)
stack traceback:
	/druid/system/druid_instance.lua:211: in function 'remove'

The "test" button does work as expected before druid:remove is called. I also tested it with a button that was manually created in the GUI file (not using gui.new_box_node) and I get the same error.
Am I making a mistake?

Yea, I found the lack of documentation about druid:remove. It's pointed only in API list. I will add more info about this functions. Thanks!
You should remove the button instance, which returned from :new_button
Like this:
local button = self.druid:new_button("test")
self.druid:remove(button)

You should remove the button instance, which returned from :new_button

Thank you - I confirm that this works as expected.