Cannot Re-Compile LGTeleServices(LP)

Recompiling "LGTeleService.apk" With Original Signature,
in work area "_WorkArea4", using "apktool_2.0.0rc4.jar"
With Tickle My Android 10.4.1.
(tinyurl.com\ticklemyandroid)

I: Using Apktool 2.0.0-RC4
I: Smaling smali folder into classes.dex...
I: Building resources...
W/ResourceType( 3708): Entry identifier 0x9 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x6 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x7 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x4 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x5 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Entry identifier 0x3 is larger than entry count 0x2
W/ResourceType( 3708): Type identifier 0x11 does not exist.
C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:4: error: Error: No resource found that matches the given name (at 'id' with value '@id/txt_selected').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:4: error: Error: No resource found that matches the given name (at 'text' with value '@string/selected_info').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:4: error: Error: No resource found that matches the given name (at 'style' with value '@style/checkbox_multi_selection_extra_size').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:5: error: Error: No resource found that matches the given name (at 'id' with value '@id/check_selectArea').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:5: error: Error: No resource found that matches the given name (at 'layout_toStartOf' with value '@id/txt_selected').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:6: error: Error: No resource found that matches the given name (at 'id' with value '@id/chkbox_selectAll').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:7: error: Error: No resource found that matches the given name (at 'id' with value '@id/chkbox_selectText').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:7: error: Error: No resource found that matches the given name (at 'text' with value '@string/sp_SelectAll2_NORMAL').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\action_bar_select_all.xml:7: error: Error: No resource found that matches the given name (at 'style' with value '@style/checkbox_multi_selection_size').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\actionbar_custom.xml:2: error: Error: No resource found that matches the given name (at 'background' with value '@color/setupwizard_theme_sub_color').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\actionbar_custom.xml:4: error: Error: No resource found that matches the given name (at 'id' with value '@id/costum_title').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\actionbar_custom.xml:4: error: Error: No resource found that matches the given name (at 'style' with value '@style/startup_wizard_header').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:4: error: Error: No resource found that matches the given name (at 'id' with value '@id/iv_disclaimer_image').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:4: error: Error: No resource found that matches the given name (at 'src' with value '@drawable/smart_forward').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:6: error: Error: No resource found that matches the given name (at 'id' with value '@id/help_description').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:6: error: Error: No resource found that matches the given name (at 'text' with value '@string/sp_sf_disclaimer_text_NORMAL').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:6: error: Error: No resource found that matches the given name (at 'style' with value '@style/call_setting_help_list').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_disclaimer.xml:8: error: Error: No resource found that matches the given name (at 'layout' with value '@layout/cancel_ok_button').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:6: error: Error: No resource found that matches the given name (at 'id' with value '@id/iv_disclaimer_image').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:6: error: Error: No resource found that matches the given name (at 'src' with value '@drawable/smart_forward_land').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:10: error: Error: No resource found that matches the given name (at 'id' with value '@id/help_description').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:10: error: Error: No resource found that matches the given name (at 'text' with value '@string/sp_sf_disclaimer_text_NORMAL').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:10: error: Error: No resource found that matches the given name (at 'style' with value '@style/call_setting_help_list').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout-land\activity_xdiv_disclaimer.xml:14: error: Error: No resource found that matches the given name (at 'layout' with value '@layout/cancel_ok_button').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:2: error: Error: No resource found that matches the given name (at 'id' with value '@id/rl_main_layout').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:4: error: Error: No resource found that matches the given name (at 'id' with value '@id/ScrollView01').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:5: error: Error: No resource found that matches the given name (at 'id' with value '@id/rl_smart_forward').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:6: error: Error: No resource found that matches the given name (at 'id' with value '@id/rl_with_check_box_status').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:7: error: Error: No resource found that matches the given name (at 'id' with value '@id/tv_sub_title').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:7: error: Error: No resource found that matches the given name (at 'text' with value '@string/sp_sf_title_NORMAL').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:8: error: Error: No resource found that matches the given name (at 'id' with value '@id/cb_sf_enable_dissable').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:8: error: Error: No resource found that matches the given name (at 'layout_alignTop' with value '@id/tv_sub_title').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:10: error: Error: No resource found that matches the given name (at 'id' with value '@id/firstDivider').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:10: error: Error: No resource found that matches the given name (at 'background' with value '@drawable/list_line').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\layout\activity_xdiv_number.xml:10: error: Error: No resource found that matches the given name (at 'layout_below' with value '@id/rl_with_check_box_status').

C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res\menu\respond_via_message_settings_menu.xml:4: error: Error: No resource found that matches the given name (at 'title' with value '@string/respond_via_sms_menu_reset_default_activity').

Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [C:\Users\Developer Account\AppData\Local\Temp\brut_util_Jar_5948311022911722379.tmp, p, --forced-package-id, 2, --min-sdk-version, 21, --target-sdk-version, 21, --rename-manifest-package, com.android.phone, --version-code, 44002700, --version-name, 4.40.27, -F, C:\Users\Developer Account\AppData\Local\Temp\APKTOOL7052285139911701584.tmp, -0, arsc, -I, C:\Users\Developer Account\apktool\framework\1.apk, -I, C:\Users\Developer Account\apktool\framework\2.apk, -S, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res, -M, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\AndroidManifest.xml]
        at brut.androlib.Androlib.buildResourcesFull(Androlib.java:442)
        at brut.androlib.Androlib.buildResources(Androlib.java:379)
        at brut.androlib.Androlib.build(Androlib.java:282)
        at brut.androlib.Androlib.build(Androlib.java:255)
        at brut.apktool.Main.cmdBuild(Main.java:225)
        at brut.apktool.Main.main(Main.java:84)
Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [C:\Users\Developer Account\AppData\Local\Temp\brut_util_Jar_5948311022911722379.tmp, p, --forced-package-id, 2, --min-sdk-version, 21, --target-sdk-version, 21, --rename-manifest-package, com.android.phone, --version-code, 44002700, --version-name, 4.40.27, -F, C:\Users\Developer Account\AppData\Local\Temp\APKTOOL7052285139911701584.tmp, -0, arsc, -I, C:\Users\Developer Account\apktool\framework\1.apk, -I, C:\Users\Developer Account\apktool\framework\2.apk, -S, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res, -M, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\AndroidManifest.xml]
        at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:504)
        at brut.androlib.Androlib.buildResourcesFull(Androlib.java:428)
        ... 5 more
Caused by: brut.common.BrutException: could not exec command: [C:\Users\Developer Account\AppData\Local\Temp\brut_util_Jar_5948311022911722379.tmp, p, --forced-package-id, 2, --min-sdk-version, 21, --target-sdk-version, 21, --rename-manifest-package, com.android.phone, --version-code, 44002700, --version-name, 4.40.27, -F, C:\Users\Developer Account\AppData\Local\Temp\APKTOOL7052285139911701584.tmp, -0, arsc, -I, C:\Users\Developer Account\apktool\framework\1.apk, -I, C:\Users\Developer Account\apktool\framework\2.apk, -S, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\res, -M, C:\TickleMyAndroid\_WorkArea4\_working\LGTeleService.apk\AndroidManifest.xml]
        at brut.util.OS.exec(OS.java:89)
        at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:498)
        ... 6 more

Recompile Not Successful!

Duplicate of #857
While I know one is HTC & the other is LG. aapt failing badly is the commonality in both of these.


Support C++20 concepts

The suggestion would be to add a new section to the docs, just before types, say, to document concepts.

Now supported, see e.g. https://doxide.org/demo/parsing/


[BUG/Feature request] Subexpressions are not supported for named parameters

The bug
Guidance supports subexpressions, by which I mean the equivalently named feature for Handlebars (in parentheses):
{{function (function_two param)}}
However, the current implementation does not support the same functionality for named parameters. Hence, the above would work but not the following:
{{function param=(function_two param)}}
This will throw an error because this use-case is not a defined case in the grammar.
I think this could be argued either as a bug or a feature request depending on angle, but given that subexpressions for either case are a supported feature in handlebars (which we somewhat loosely claim parity with), the above is a deviation from expected behavior.
It creates issues with situations like {{#select options=(select_subfield_from_dict_that_is_an_array dict)}} which otherwise forces users to place a dependency on the order of the arguments in the select function and hence is more prone to version breakages.
To Reproduce
The following works:
def function(param):
    return param+"faz"
def function_two(param):
    return param+"bar"

p= guidance("""{{function (function_two param)}}""")
o= p(
    function=function,
    function_two=function_two,
    param="foo"
)

and produces the expected result 'foobarfaz'
The following does not:
def function(param):
    return param+"faz"
def function_two(param):
    return param+"bar"

p= guidance("""{{function param=(function_two param)}}""")
o= p(
    function=function,
    function_two=function_two,
    param="foo"
)

System info (please complete the following information):

OS (e.g. Ubuntu, Windows 11, Mac OS, etc.):  - OS (e.g. Ubuntu, Windows 11, Mac OS, etc.): Debian 11, both CPU and GPU inference
Guidance Version (guidance.__version__): 0.0.61

For what it's worth, I'm willing to take a crack at implementing this.

Thanks for reporting this! That is indeed an oversight and should be supported. If you are willing to send a PR addressing it that would be great! I think the changes should just be in:
https://github.com/microsoft/guidance/blob/0f7be47a567f8c63b5eedf748385c63c4c0ee9e3/guidance/_grammar.py#L37-L38

We did away with handlebars in the new release. Hopefully f-strings still serve your purposes :)


[BUG] sources_as_raw leads to error when calling repr of raw object

After creating an ICA object and calling get_sources. The created Raw object hast an empty filenames list mne.preprocessing.ica:_sources_as_raw.
This causes an IndexError when calling mne.io.Base:repr because the list is not None, but empty.

Looks like it should set _filenames = [None] instead of _filenames = []. Can you make a PR to fix it, and add a test? The test can just be a line in mne/preprocessing/tests/test_ica.py that does print(repr(ica_raw))

Wow, this seems like a time-warp, a regression?
Fix welcomed.
On Tue, Nov 29, 2016 at 5:04 PM ppasler<EMAIL_ADDRESS>wrote:

After creating an ICA object and calling get_sources. The created Raw
object hast an empty filenames list mne.preprocessing.ica:_sources_as_raw
https://github.com/mne-tools/mne-python/blob/master/mne/preprocessing/ica.py#L729
.
This causes an IndexError when calling repr
https://github.com/mne-tools/mne-python/blob/master/mne/io/base.py#L1884
because the list is not None, but empty.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/3804, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fiq_w9_7ryyAXTrVpVhgI85GOWQiAks5rDE0KgaJpZM4K_JoE
.

@Eric89GXL @dengemann sure.

@Eric89GXL @dengemann this is first time I contribute to an open source project.

fork the repo
create a branch from master
add a PullRequest with my changes

Is this correct?

Yep that's the idea.  It's possible to do it all graphically on GitHub to start. For frequent development it's easier to learn the git command-line interface.

I am familiar with git, but not with the workflow for OS projects :)
I'll try it now!

It seems not to connect the issue with the PR, do I have to use some specific branch name or commit text?


Check if output dir not exists

where receive dir is not exist
`
qrcp receive --output=/abcd/
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1410e68]
goroutine 1 [running]:
github.com/claudiodangelis/qrcp/server.(*Server).ReceiveTo(0xc00028c000, 0x7ffeefbffb5e, 0x6, 0x0, 0x0)
/Users/heyong/gomod-workspace/my-qrcp/server/server.go:45 +0x78
github.com/claudiodangelis/qrcp/cmd.receiveCmdFunc(0x18ea6a0, 0xc000068290, 0x0, 0x1, 0x0, 0x0)
/Users/heyong/gomod-workspace/my-qrcp/cmd/receive.go:24 +0x1c9
github.com/spf13/cobra.(*Command).execute(0x18ea6a0, 0xc000068280, 0x1, 0x1, 0x18ea6a0, 0xc000068280)
/Users/heyong/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842 +0x460
github.com/spf13/cobra.(*Command).ExecuteC(0x18ea400, 0xc0001b7f20, 0x103d0aa, 0x18a6120)
/Users/heyong/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
/Users/heyong/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
github.com/claudiodangelis/qrcp/cmd.Execute(0x10076cf, 0xc000094058)
/Users/heyong/gomod-workspace/my-qrcp/cmd/qrcp.go:45 +0x2d
main.main()
/Users/heyong/gomod-workspace/my-qrcp/main.go:10 +0x26
`

Thanks for this contribution @heyv5, I will review it in a few days & merge it.
Thanks!

@claudiodangelis Please check the code is OK ?

That's perfect now, thank you very much for spotting & resolving the issue! :tada:


feat(cloudflare): implemented a timeout based setImmediate

We are exploring using unenv for setImmediate.
The desired behavior is run the callback in a setTimeout(0) instead of right away.

@IgorMinar @pi0 helped me to get https://github.com/unjs/unenv/pull/303 in - it changes the setImmediate behavior to use a timeout.
The current behavior is to use globalThis || unenv.
This PR would make sure we always use unenv.

So...
  inject: {
    setImmediate: ["unenv/runtime/node/timers/$cloudflare", "setImmediate"],
    clearImmediate: ["unenv/runtime/node/timers/$cloudflare", "clearImmediate"],
  },

was not working with this code before the PR
// set-immediate.ts

export const clearImmediateFallback = function clearImmediate(...){...};

Because the code generated by wrangler was
// At this point clearImmediateFallback === undefined
globalThis.clearImmediate = clearImmediateFallback;

// ...

var setImmediateFallback = function (...) {...};
var clearImmediateFallback = function (...) {...};

// setImmediate is ok
globalThis.setImmediate = setImmediatefFallback;

By switching exports to functions, it solves the issue, the generated code is now
// At this point clearImmediateFallback === undefined
globalThis.clearImmediate = clearImmediateFallback;

// ...

function setImmediateFallback(...) {...}
function clearImmediateFallback(...) {...}

// setImmediate is ok
globalThis.setImmediate = setImmediatefFallback;

Note: wrangler is using an older version of esbuild but updating to the current 0.23.1 still exhibits the same behavior.

Thanks for the review and help @IgorMinar and @pi0.
I have updated the PR according to the feddback.

bah! I'm sorry @vicb, this must have been frustrating to debug. I'm glad that you got to the bottom of it and resolved it. Thank you!

It was fun to scrath our heads with @petebacondarwin this morning 🤔


Apps transforms not updating when worn

Right now, apps are not updating when we wear them.
The bind is getting called properly, the app is getting worn, the problem seems to be that wearupdate is not getting called on the remoteplayer. We need to make sure the wearupdate function gets called on both remote players and local players.

As it can be seen in the video, The Wearable items are not getting replicated in the remote instances.
https://user-images.githubusercontent.com/35926530/163594265-d5177dbd-f053-4174-8ec7-8e4382a01a6c.mp4

https://user-images.githubusercontent.com/99482765/164303556-b1e0eb96-185e-4613-928f-12d132b46258.mp4
Fixed this issue by changing the wearupdate function.

It can be seen in the give video, The Wearable items are not getting replicated in the remote instances even remote instance get hanged.
Steps to replicate

I open Erithor room in both windows
now remote player is moving like local player
When i pressed e, then local player grabbed the sword
And the screen of remote player was hanged
For reference, kindly see the attached [video]

It can be seen in the give video, The Wearable items are not getting replicated in the remote instances even remote instance get hanged.
Steps to replicate
I open Erithor room in both windows
now remote player is moving like local player
When i pressed e, then local player grabbed the sword
And the screen of remote player was hanged
For reference, kindly see the attached [video]
https://user-images.githubusercontent.com/101788714/164718109-6ec3ff3d-d478-47b4-9b63-eadf6f30baec.mp4

This has been fixed, was a separate null ref issue.

When I retested this issue, I found that both player are able to wear sword but animation is happening at only local player.
For reference, Kindly see the attached video:
https://www.awesomescreenshot.com/video/8727500?key=ec25a520c91d699410cd663abfe4d3a9


Update to latest partiql-tests

Some test have changed and more have been added.
It is expected that there might  appear to be some test regressions due to the changes.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Probably should update partiql-tests again after partiql/partiql-tests#128 is merged in.

That's the plan. I wanted to do this update first. Then pull that in to show only changes from  partiql/partiql-tests#128


Elarc Toon: Skip responses that do not start with "text/html"

Skip responses that do not start with "text/html", such as responses of image types, to improve extension performance.
Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

hi, can you provide screenshots that prove you built and tested these changes.

@AwkwardPeak7  Fully understood. Thank you for your review and all your contributions. ❤


GET /v1/collections/{collection_uuid} incorrectly documents a 400 status code

See curation-api.
The Swagger API incorrectly documents that a 400 can be returned.
In general, it would be helpful to document the cause of error conditions because it helps to validate whether there is a scenario that might result in a specific status code.

I looked into easily adding validation of path/query parameter id's. It can be done easily using pattern: <uuid regex pattern> in the API definition, but that messes up our testing since we use human-readable (and meaningful) id's for our unit tests. Not worth it at the moment.


Add PHP 8.0 build

Tried this with enqueue, appears to work.

@makasim whenever you get to this please also publish the new tag to Docker Hub 🙌

@makasim whenever you get to this please also publish the new tag to Docker Hub 🙌

I have access to this repo.

I have access to this repo.

Can you add it here https://github.com/makasim/docker-nginx-php-fpm ?

Can you add it here https://github.com/makasim/docker-nginx-php-fpm ?

Added as https://github.com/makasim/docker-nginx-php-fpm/pull/2
Does it also mean a different docker hub namespace?

Added as https://github.com/makasim/docker-nginx-php-fpm/pull/2
Does it also mean a different docker hub namespace?

Sure, https://hub.docker.com/repository/docker/makasim/nginx-php-fpm

Sure, https://hub.docker.com/repository/docker/makasim/nginx-php-fpm


Remove SubscriptionFlowControl

Once we replace DefaultSubscriptionBatchSource with StreamingSubscriptionBatchSource we will be able to remove the SubscriptionFlowControl class, and that will allow us to cleanup several (internal-only) functions.

Fixed in #5224


Set version to 0.1.5

Codecov Report

Merging #36 (aaedad9) into main (3181dab) will decrease coverage by 36.17%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #36       +/-   ##
===========================================
- Coverage   76.98%   40.82%   -36.17%
===========================================
  Files          16       16
  Lines        2233     2195       -38
===========================================
- Hits         1719      896      -823
- Misses        514     1299      +785

see 14 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


HBASE-24165 maxPoolSize is logged incorrectly in ByteBufferPool (adde…

…ndum)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m  3s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 48s
branch-2.2 passed

+1 :green_heart:
compile
0m 23s
branch-2.2 passed

+1 :green_heart:
checkstyle
0m 28s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 40s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 21s
branch-2.2 passed

+0 :ok:
spotbugs
0m 55s
Used deprecated FindBugs config; considering switching to SpotBugs.

-1 :x:
findbugs
0m 52s
hbase-common in branch-2.2 has 1 extant findbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 19s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
checkstyle
0m 28s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 25s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
28m 23s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 55s
hbase-common generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

_ Other Tests _

+1 :green_heart:
unit
2m 56s
hbase-common in the patch passed.

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

66m 34s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1720

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 54a29ccb5ddd 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1720/out/precommit/personality/provided.sh

git revision
branch-2.2 / a6152af6cf

Default Java
1.8.0_181

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/1/artifact/out/branch-findbugs-hbase-common-warnings.html

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/1/testReport/

Max. process+thread count
291 (vs. ulimit of 10000)

modules
C: hbase-common U: hbase-common

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 16s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 40s
branch-2.2 passed

+1 :green_heart:
compile
0m 22s
branch-2.2 passed

+1 :green_heart:
checkstyle
0m 28s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 25s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 22s
branch-2.2 passed

+0 :ok:
spotbugs
0m 52s
Used deprecated FindBugs config; considering switching to SpotBugs.

-1 :x:
findbugs
0m 49s
hbase-common in branch-2.2 has 1 extant findbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 16s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
checkstyle
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 21s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
28m  1s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 21s
the patch passed

+1 :green_heart:
findbugs
1m  0s
hbase-common generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

_ Other Tests _

+1 :green_heart:
unit
2m 56s
hbase-common in the patch passed.

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

63m  8s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1720

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 12f52ffc3372 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1720/out/precommit/personality/provided.sh

git revision
branch-2.2 / 43d39ee265

Default Java
1.8.0_181

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/3/artifact/out/branch-findbugs-hbase-common-warnings.html

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/3/testReport/

Max. process+thread count
266 (vs. ulimit of 10000)

modules
C: hbase-common U: hbase-common

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1720/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

findbugs:check passed locally. But failed in precommit job. Let me rerun this check.

findbugs:check passed locally. But failed in precommit job. Let me rerun this check.

Findbugs failed on branch-2.2 but not with your patch. I think the overall -1 is a yetus bug.
hbase-common in branch-2.2 has 1 extant findbugs warnings.
hbase-common generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

findbugs:check passed locally. But failed in precommit job. Let me rerun this check.

Findbugs failed on branch-2.2 but not with your patch. I think the overall -1 is a yetus bug.
hbase-common in branch-2.2 has 1 extant findbugs warnings.
hbase-common generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1)

Thanks. Merged it.


Arcade Jan 2023 Release blog post

Import, format, edit, adjust images, etc. for the Arcade Jan 2023 Release blog post.
Closes #9342

Hi Galen - is this ready to merge?

I'm ready if you're ready.

Yeah!  Thanks!


[material-ui] After updating to 5.16.0, the theme default props are disabled.

Steps to reproduce
No response
Current behavior
No response
Expected behavior
No response
Context
Theme default props disabled after uploading from 5.15.21 to 5.16.0.
https://mui.com/material-ui/customization/theme-components/#theme-default-props
Your environment

npx @mui/envinfo
before
System:
    OS: macOS 14.5
  Binaries:
    Node: 20.14.0 - ~/.nodenv/versions/20.14.0/bin/node
    npm: 10.7.0 - ~/.nodenv/versions/20.14.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 126.0.6478.127
    Edge: Not Found
    Safari: 17.5
  npmPackages:
    @emotion/react: 11.11.4 => 11.11.4
    @emotion/styled: 11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.16.0
    @mui/icons-material: 5.15.21 => 5.15.21
    @mui/material: 5.15.21 => 5.15.21
    @mui/private-theming:  5.16.0
    @mui/styled-engine:  5.15.14
    @mui/system:  5.16.0
    @mui/types:  7.2.14
    @mui/utils:  5.16.0
    @mui/x-data-grid:  7.8.0
    @mui/x-data-grid-pro: 7.8.0 => 7.8.0
    @mui/x-date-pickers:  7.8.0
    @mui/x-date-pickers-pro: 7.8.0 => 7.8.0
    @mui/x-license: 7.8.0 => 7.8.0
    @types/react: 18.3.3 => 18.3.3
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1
    typescript: 5.5.3 => 5.5.3

after
  System:
    OS: macOS 14.5
  Binaries:
    Node: 20.14.0 - ~/.nodenv/versions/20.14.0/bin/node
    npm: 10.7.0 - ~/.nodenv/versions/20.14.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 126.0.6478.127
    Edge: Not Found
    Safari: 17.5
  npmPackages:
    @emotion/react: 11.11.4 => 11.11.4
    @emotion/styled: 11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.16.0
    @mui/icons-material: 5.16.0 => 5.16.0
    @mui/material: 5.16.0 => 5.16.0
    @mui/private-theming:  5.16.0
    @mui/styled-engine:  5.15.14
    @mui/system:  5.16.0
    @mui/types:  7.2.14
    @mui/utils:  5.16.0
    @mui/x-data-grid:  7.9.0
    @mui/x-data-grid-pro: 7.9.0 => 7.9.0
    @mui/x-date-pickers:  7.9.0
    @mui/x-date-pickers-pro: 7.9.0 => 7.9.0
    @mui/x-internals:  7.9.0
    @mui/x-license: 7.9.0 => 7.9.0
    @types/react: 18.3.3 => 18.3.3
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1
    typescript: 5.5.3 => 5.5.3

Search keywords: Theme default props, 5.16.0

@naro143 I didn't understand your issue. Are the default props passed to the theme not working? In the documentation link you provided, it shows that disableRipple: true disables the ripples which does work.

@ZeeshanTamboli
The default props passed to the theme not working.
The document disableRipple: true also works in 5.15.21, but not in 5.16.0.

I confirm that this is an issue in 5.16.0 as well

Can you provide a CodeSandbox or StackBlitz reproducing the issue? I cannot reproduce it on version 5.16.0: https://codesandbox.io/p/sandbox/dazzling-chebyshev-tl548c?file=%2Fsrc%2FDemo.tsx%3A8%2C21

I can confirm, that this is not an issue with Material UI.
The issue is in our application:
// import { ThemeProvider } from '@emotion/react'
import { ThemeProvider } from '@mui/material'

We supposedly did auto import on the ThemeProvider dependency, which resulted in import from emotion itself. This worked until 5.16.0
@naro143 Check whether you don't have the same issue

@naro143 I didn't understand your issue. Are the default props passed to the theme not working? In the documentation link you provided, it shows that disableRipple: true disables the ripples which does work.

sorry but have you tried setting other props in your sandbox for eg
variant: 'contained',
size: 'small',

does it work ?

@choutkamartin

We supposedly did auto import on the ThemeProvider dependency, which resulted in import from emotion itself. This worked until 5.16.0

The same was imported from @emotion/react.
Importing from @mui/material solved the problem.
Thanks for the great research!

Happens to us as well when we updated from 5.13.4 to 5.16.6
We're not importing ThemeProvider from "emotion" , but from "@mui/material" as needed...


catch err logs if umount failed

Describe what this PR does / why we need it
catch err logs if umount failed
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 21.12% // Head: 21.12% // No change to project coverage :thumbsup:

Coverage data is based on head (f10dbb8) compared to base (145eb4c).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1869   +/-   ##
=======================================
  Coverage   21.12%   21.12%
=======================================
  Files          74       74
  Lines        6760     6760
=======================================
  Hits         1428     1428
  Misses       5146     5146
  Partials      186      186

Impacted Files
Coverage Δ

pkg/imagedistributor/mount.go
2.77% <0.00%> (ø)

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.


The example does not work as expected

The documentation provides the following example:
produce \emit -> do
  log "Working..."
  emit (Left "progress")
  log "Done!"
  emit (Right "finished")

I expect this output:
Working...
progress
Done!
finished

But I see this:
Working...
Done!

which I think shows that the consumer does not receive any value.
The Aff example (with produceAff) does work as expected.
Below is the full code. I've used version 6.0.0 and Aff 4.1.1.
module Main where

import Control.Monad.Eff (Eff)
import Control.Coroutine (Consumer, Producer, consumer, runProcess, ($$))
import Control.Coroutine.Aff (produce)
import Control.Monad.Aff (Aff, runAff)
import Control.Monad.Eff.AVar (AVAR)
import Control.Monad.Eff.Class (liftEff)
import Control.Monad.Eff.Console (CONSOLE, log, logShow)
import Control.Monad.Eff.Exception (EXCEPTION)
import Data.Either (Either(..))
import Data.Maybe (Maybe(..))
import Prelude

type EmitFunction a r eff = (Either a r -> Eff (avar :: AVAR | eff) Unit)

p :: forall eff. Producer String (Aff (console :: CONSOLE, avar :: AVAR | eff)) String
p = produce f
  where

  f :: EmitFunction String String (console :: CONSOLE | eff) -> Eff (avar :: AVAR, console :: CONSOLE | eff) Unit
  f emit = do
    log "Working..."
    emit (Left "progress")
    log "Done!!!"
    emit (Right "finished")

c :: forall eff. Consumer String (Aff (console :: CONSOLE | eff)) String
c = consumer \s -> liftEff (log s) $> Nothing

main :: forall eff. Eff (console :: CONSOLE, avar :: AVAR, err :: EXCEPTION | eff) Unit
main = void $ runAff logShow $ runProcess (p $$ c)

{-
$ pulp run
* Building project in /Users/joopringelberg/Code/purescript-node-net
* Build successful.
Working...
Done!!!
-}

The problem appears to be in the produce function, because the produceAff function works as expected.
produce
  :: forall a r eff
   . ((Either a r -> Eff (avar :: AVAR | eff) Unit) -> Eff (avar :: AVAR | eff) Unit)
  -> Producer a (Aff (avar :: AVAR | eff)) r
produce recv = produceAff \send ->
  liftEff (recv (void <<< runAff (const (pure unit)) <<< send))

In other words, the problem is in the argument to produceAff. Here is a (verbose) version of produce that works:
produce (recv :: (Either a r -> Eff (avar :: AVAR | eff) Unit) -> Eff (avar :: AVAR | eff) Unit) = produceAff f
  where
    f :: (Either a r -> Aff (avar :: AVAR | eff) Unit) -> Aff (avar :: AVAR | eff) Unit
    f send = liftEff $ recv send'
      where
        send' :: (Either a r -> Eff (avar :: AVAR | eff) Unit)
        send' ear = void $ runAff (const (pure unit)) (send ear)

The signature of f is taken from the argument to produceAff. This clearly exposes the main puzzle of the function produce, that is: it receives a function recv that takes a function with argument (Either a r -> Eff (avar :: AVAR | eff) Unit), that is, a function in Eff, but needs, for f, a function with similar type but in Aff. So we postulate the solution send' that conforms to that signature.
Then, writing out send' with the (Either a r) argument made explicit, it is clear we have to runAff the original send function on that argument, voiding the result.
All in all it boils down to this:
void <<< runAff (const (pure unit)) <<< send

is not equal to:
\ear -> void $ runAff (const (pure unit)) (send ear)

And we need the former. So the correct definition of produce should be:
produce recv = produceAff \send ->
  liftEff $ recv \ear -> void $ runAff (const (pure unit)) (send ear)

Ah. I closed the issue, but obviously the change has yet to be made to the library!

The current version in master does not appear to behave the way you're describing:
p' :: Producer String Aff String
p' = produce \emitter -> do
  log "Working..."
  emit emitter "progress"
  log "Done!"
  close emitter "finished"

c :: Consumer String Aff String
c = consumer \s -> liftEffect (log s) $> Nothing

main :: Effect Unit
main = void $ runAff (either logShow log) $ runProcess (p' $$ c)

Produces:
Working...
Done!
progress
finished

The ordering isn't exactly right due to the way the process is fused, but you can see it is hitting each of the logs and emits as expected though.
It's very odd that the curried version does not appear to behave the same as the eta-expanded version for you... the compiler actually rewrites the former into the latter! I suspect maybe there's something else going on?

That is odd indeed! It must be some effect then of the package versions I've used? See the bower.json file below.
I've checked again in new project directory, this time based on the package-set psc-0.11.7-20180524 and you are quite right, there is no error then.
Same compiler version, same Node version.
It is beyond me.
{
  "name": "purescript-node-net",
  "version": "0.0.1",
  "moduleType": [
    "node"
  ],
  "ignore": [
    "**/.*",
    "node_modules",
    "bower_components",
    "output"
  ],
  "dependencies": {
    "purescript-aff": "4.1.1",
    "purescript-foreign": "4.0.1",
    "purescript-exceptions": "3.0.0",
    "purescript-debug": "3.0.0",
    "purescript-node-process": "4.0.0",
    "purescript-aff-coroutines": "6.0.0"
  },
  "devDependencies": {
    "purescript-yargs": "3.0.0",
    "purescript-node-readline": "3.0.1"
  }
}


IGNORE: Test for deploy previews

Ignore, tests for Deploy Preview workflow

!preview

!preview

Hey @LekoArts, your preview is currently deploying and should be available shortly.

Status
Preview
Updated (UTC)

:cook: Deploying...
Inspect
Nov 09, 2023 09:45 AM


Swarms of size 20,50,100 don't complete

Repro: Uncomment the commented-out-tests in tracker_test.go
Might be some sort of OS-level resource starvation or race condition. Tested on OSX. Fails reproducibly. (Which tends to indicate that it's not a race condition.)

I tried to debug this issue, 2 different bugs seem to produce a fail on a debian 8
1st thing is to make sure that all the ports used for testing the swarm are available, right now it is hardcoded from 7000 to 7000+1+n (n being the size of the swarm, 7000 is seed). If a port is already in use the client just fails to run. a grep "Listen failed" on the output shows the "failing" nodes. I submitted PR #100 with a small fix regarding the use of port 0, to avoid this case of unavailable ports
once this is put aside, the test randomly pass or fails with timeout, with some log.Print I found that the timeouts occur because 1 or more clients don't properly exit, the p.cmd.Wait() blocks while the loop popping the doneCh is waiting for these last few to return (rarely more than 1). I didn't find where they are stuck, but a diff on the data file for the corresponding hanged clients show that it was properly downloaded. Also they don't seem to be in the DoTorrents loop since at this point in the test I only see the heartbeat log of the seed, the missing leech clients don't appear anymore.

sorry about 48ab793, I did a push -f to also include the ts.HintNewPeer parts, while ts.AcceptPeer is the one I think is most susceptible to hanging, I think the former may hang too.

Closing since swarms of size 20,50,100 have been completing successfully since commit 48ab793.


CLOUDSTACK-9534: Allow VR to be destroy in UI when in running state

This allows us to destroy a VR that is in running state from the UI. This action is possible via cloudmonkey/APIs, and would be useful for anyone who wants to simply destroy a VR from the UI without having to stop it first.
As this is a pure UI fix, manual testing would be needed but no regression integration testing is necessary.
/cc @jburwell @karuturi
@blueorangutan package
Screenshot:

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✖centos6 ✖centos7 ✖debian. JID-51

Packaging result: ✖centos6 ✔centos7 ✔debian. JID-52

Ignore centos6 failure, it succeeded but something went wrong at the backend.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-53

@rhtyd Will destroy router show a similar message as stop router in UI?
All services provided by this virtual router will be interrupted. Please confirm that you want to stop this router.

@koushik-das it'll display whatever message is currently displayed for destroy router action, which is not same as stop router action:

Since services are disrupted when VR is destroyed, I think it would be useful to provide a message similar to stop VR. Earlier only destroying a stopped VR was possible from UI so caller was already aware.

@koushik-das this is available/shown only to the admin, can we assume admin would know that it may cause network disruption for guest vms? The translation can be fixed, though in case the VR is stopped -- the message won't make sense when destroy router action is performed.

@rhtyd You are right, the message only makes sense for destroying running VR. So some conditional check needs to be there for displaying the proper message.
Based on the discussion it appears that may be destroy option was intentionally not shown earlier to avoid the effort of showing conditional messages :)

@koushik-das I'll see if I can add a conditional in the pop-up :)

@koushik-das alright I've fixed the message. It shows as follows:

When router is in running state:

When router is in stopped state:

LGTM. Small comment on the message for running VR. "Please confirm... " is appearing twice, only one would suffice.

@koushik-das I actually have appended the two translated messages in the conditional, as destroy router would stop the VR first.

Is this good to merge, purely UI change? /cc @murali-reddy @abhinandanprateek @karuturi

@rhtyd LGTM on code review...add more such admin UI stuff that admin end up using manually

Since this is a pure UI change, merging based on manual test LGTMs and code review.

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-117


Upstream changed the user on us, so buildkit image doesn't build

The previous PR (#246) updated how the helm chart references the buildkit images, but our build process to vendor the buildkit images uses that chart's values, using the same string substitution separately, to determine the base image. This causes us to use the incorrect image when vendoring buildkit.

CI skips buildkit in PRs here, so I ran it locally like this:
[anglerfish : 0 : 3:00PM] buildkit>docker buildx build --target root --build-arg BUILDKIT_TAG=$(yq '.buildkit.image.tag' ../../deployments/helm/hephaestus/values.yaml) . -t buildkit:root
[+] Building 0.8s (6/6) FINISHED                                                                               docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                           0.0s
 => => transferring dockerfile: 879B                                                                                0.0s
 => [internal] load metadata for docker.io/moby/buildkit:v0.16.0                                                               0.7s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [root 1/2] FROM docker.io/moby/buildkit:v0.16.0@sha256:bc1fe18224dbcb92599139db0c745696c48ba9fd4ac24038d1fa81fdd7dcac27    0.0s
 => CACHED [root 2/2] RUN apk update &&     apk upgrade &&     rm -rf /var/cache/apk                                           0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:92d43ebbf835f0cd925f6abf69f021bb455f831837a5630098955cd76d3d400c                                   0.0s
 => => naming to docker.io/library/buildkit:root                                                                               0.0s
[anglerfish : 0 : 3:00PM] buildkit>docker buildx build --target rootless --build-arg BUILDKIT_TAG=$(yq '.buildkit.rootlessImage.tag' ../../deployments/helm/hephaestus/values.yaml) . -t buildkit:rootless
[+] Building 0.4s (8/8) FINISHED                                                                               docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                           0.0s
 => => transferring dockerfile: 879B                                                                                0.0s
 => [internal] load metadata for docker.io/moby/buildkit:v0.16.0-rootless                                                      0.4s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [rootless 1/4] FROM docker.io/moby/buildkit:v0.16.0-rootless@sha256:fed5f1fd2f8c2b246bc227e3f72953981dbe163a09add4c8cb9cc  0.0s
 => CACHED [rootless 2/4] RUN apk update &&     apk upgrade &&     rm -rf /var/cache/apk                                       0.0s
 => CACHED [rootless 3/4] RUN deluser user &&     adduser -u 1000 -D user &&     chown -R user:user /home/user &&     mkdir -  0.0s
 => CACHED [rootless 4/4] RUN addgroup -S -g 1337 istio &&     addgroup user istio &&     echo user:100000:150000 | tee /etc/  0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:29cc737b56d4e2bcb8d5e90ece0f3e5aa12a48e666bb53d856189e914b0de001                                   0.0s
 => => naming to docker.io/library/buildkit:rootless


Making dialog JQuery 3.x compliant

Jquery deleted .load in 3.x, recomended to use .on("load" instead.
https://jquery.com/upgrade-guide/3.0/#breaking-change-load-unload-and-error-removed

@EisenbergEffect I've pulled down this change, plugged it into a starter kit with jQuery 3.0.0, and had 0 errors. I did the same with JQuery 1.9.1 and 0 errors. I think it is safe to pull this in.

Thanks all!


Ability to set entrypoint on working container

Currently, only target_image context supports the setup of the entrypoint, which is affects only "production" image.
In cases, where base image already has an entrypoint, ansible-bender will stuck during the build, due endless process running by container.
This problem can be solved by adding the ability to setup entrypoint for working container , this entrypoint will override the entrypoint of the base image:
 vars:
    ansible_bender:
      working_container:
        entrypoint: <an_entrypoint>

Any one working on this?
Does the tag "good first issue" mean that it's a good issue to start with if someone wants to contribute?

Does the tag "good first issue" mean that it's a good issue to start with if someone wants to contribute?

Yes. This is a good issue to start with :)

I made a pull request (#232 ) that will add the option of setting entrypoint for working_container. This at least solves my problem with getting stuck during the build phase.


use prefix option as prefix to path, not only the db

This code currently creates .fsdown/datamydb.json, but I’d expect data/mydb.json as the leveldb adapter does it.
var PouchDB = require('pouchdb-core')
  .plugin(require('pouchdb-adapter-fs'))
  .defaults({
    prefix: 'data/'
  })

new PouchDB('mydb')

Would you agree?
For Hoodie we need the folder where the databases are stored to be configurable.
I’d suggest that we default to .fsdown/ unless the prefix option is set.

This sounds reasonable to me. I'm actually also open to just removing the whole .fsdown prefix and just pushing a 2.0.0 version. This project is young and I'm sure not many people are using it.

I'm actually also open to just removing the whole .fsdown prefix

Agree 👍 I think it’s best to match the leveldb adapter’s behavior. I’ll work on a PR, thanks Nolan :)

Can you invite me to this repository, so we can collab on the PR if needed?

sure thing!

sorry can you add me to https://github.com/nolanlawson/fsdown, too? Sorry for pinging you on slack, too I got distracted shortly and forgot I already pinged you on GitHub

shipped in v2


fixes #8209 - redirects from actions don't honor the provided status code

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Thank you! Could you add a changeset (patch version)?


[PE-D][Tester C] Export: Transaction Export does not maintain sort/filter

In my transaction list, I sorted transactions by descending date, and then filtered for only expenses. However, when I exported the transaction, it still reverted to its original form (all transactions arranged by ID)

Users might appreciate being able to export the data that they're currently viewing instead of having to manually filter/sort the csv file after export.

Labels: severity.Medium type.FeatureFlaw
original: phiphi-tan/ped#14

Requires feature change, not a bug.


#1131 complex method should be less strict with simple when entries

This fixes #1131 by weighing simple when entries to 0.5 (was 1.0) by default, and allowing users to customise the weight if they want to.
This requires the McCabe visitor to internally keep a floating-point sum of the complexities, but we still emit an integer value to keep backwards compatibility (and for simplicity).
This PR also improves ComplexMethod's tests, and adds better facilities to test Findings and ThresholdedCodeSmells.

CC @Mauin

Ticket opened: #1137

@Mauin can you re-trigger the JDK 9 build on AppVeyor? It failed with some random socket error.

To be honest, I do not like this change. As @schalkms mentioned, McCabe is all about "number of linearly independent paths" within a program. When using floating values this should be another rule then.
I propose to not count the complexity of simple paths within when when a config property is true. If all paths are simple, just count the whole when expressions as mccabe=1.

Happy to make the change if there's a consensus, I take the point.

I have created a PR on my fork comparing this solution and an ignore-based solution which adheres better to the definition of MCC. Please review it here: https://github.com/rock3r/detekt/pull/2

@rock3r jap that's 90% how I would want this rule to be :). The other 10% is when if (entries.filter { it is KtBlockExpression}.size == 0) return 1 :)

I guess we go with the simple=0 variant?
Can you please open a PR with your new branch?/

Thank you!

Still WIP but have merged master in, should at least not have conflicts anymore

Finally managed to get the changes @arturbosch requested in.

Thank you for the changes!
I rebased and merged this manually. Please use rebase when merging the master branch :)
We rebase everything to get a cleaner history ^^


[Tables] fixing link

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

The errors are because of an issue with the test proxy on windows. Ignoring for now and merging as this is only a change to links

/check-enforcer override


Storage: Mount reference counting

Includes https://github.com/lxc/lxd/pull/8157
Introduces the concept of storage volume mount/unmount reference counting.
When a storage volume is mounted for the first time, a global reference counter is created and incremented to 1.
If other operations on the storage volume also need it while it is already mounted, then subsequent requests to mount the volume will just increment the reference counter again.
Then once each operation has finished with the volume they unmount the volume, and the reference counter is decremented.
If the reference counter is not yet at zero, then other operations are still using the volume and an ErrInUse error is returned.
The last unmount request that detects the reference counter is at zero will actually perform the unmount of the volume.
This work was done primarily to address the following group of issues related to copying ZFS VM snapshot as another instance:

Fixes https://github.com/lxc/lxd/issues/8113
https://discuss.linuxcontainers.org/t/copying-vm-snapshot-to-other-host-not-working-attempts-to-create-a-container/9363
https://discuss.linuxcontainers.org/t/lxc-copy-container-ok-lxc-copy-vm-fails-with-failed-to-mount-permission-denied/9237

Reference counting is required to solve these problems because in order to activate a ZFS block volume snapshot, the parent volume also needs to be activated. However the current storage interface didn't provide a clean way for the parent volume to be unmounted (if needed) once the snapshot volume was unmounted.
By introducing reference counters we can just request that the parent volume always be unmounted when unmounting a snapshot, and if others are using it, the unmount request will fail.
However reference counting also helps with several other classes of problems:

Long running Instance file operations (push/pull/delete etc) when the instance is running and stopped while file operation is ongoing.
Detecting when a custom volume is mounted in multiple running instances and deciding whether to unmount when one instance is stopped (which was causing shutdown delays and errors).

In order to support reference counting, everywhere that mounts a volume needed to be reviewed to ensure that where appropriate the equivalent unmount request was made when the operation completed, otherwise the reference counter would not be decremented and the volume would be left mounted.

Testsuite passed

Looks good, just found that one typo in a commit message and branch needs a quick rebase on master.
I'll do both those fixes now and then merge once jenkins is done.

Testsuite passed

Thanks!


Network Error at XMLHttpRequest.handleError

I have this error when I try to retrieve gitlab repo..
/home/os/.atom/packages/gitlab/node_modules/axios/lib/adapters/xhr.js:171 GET file:///usr/share/atom/resources/app.asar/static/undefined/api/v3/projects net::ERR_FILE_NOT_FOUND
xhrAdapter @ /home/os/.atom/packages/gitlab/node_modules/axios/lib/adapters/xhr.js:171
executor @ /home/os/.atom/packages/gitlab/node_modules/axios/lib/core/dispatchRequest.js:27
dispatchRequest @ /home/os/.atom/packages/gitlab/node_modules/axios/lib/core/dispatchRequest.js:11
projects-view.coffee [sm]:45

Error: Network Error
    at XMLHttpRequest.handleError (/home/os/.atom/packages/gitlab/node_modules/axios/lib/adapters/xhr.js:90)

Project deprecated


dotnet core 2.1.0 package updates

updated to 2.1.0-preview1-final, leaving open until the stable version is released


No working in multi tenant environments

I have tried this moving an snapshot between two subscriptions associated to the same Az AD tenant and it works smoothly.
However, if I do exactly the same but using subscriptions associated to different Az AD tenants it fails with the following error.
The client has permission to perform action 'Microsoft.Compute/disks/beginGetAccess/action' on scope '/subscriptions/xxxxxxxxxxx/resourceGroups/RGTEST/providers/Microsoft.Compute/snapshots/testsnap', however the current tenant 'xxxxxxxxxxxx' is not authorized to access linked subscription 'xxxxxxxxxxxxxx'.
I have tried to add the user to gloabal admins in both AD tenants but nothing changes.
Any idea how can get this operation done?
If this error is expected, could be nice update the documentation to reflect it.

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

ID: 13002dff-5820-5a23-45de-a73b5b279bdd
Version Independent ID: 51a66ed3-472b-ce60-63d7-d01d1aae03e8
Content: Copy snapshot of a managed disk to a subscription - CLI Sample
Content Source: articles/virtual-machines/scripts/virtual-machines-windows-cli-sample-copy-snapshot-to-same-or-different-subscription.md
Service: virtual-machines-windows
GitHub Login: @ramankumarlive
Microsoft Alias: ramankum

Thanks for the feedback! We are currently investigating and will update you shortly.

Resources cannot be moved across subscriptions belonging to different tenant directly. These subscriptions has to be brought under one Tenant to make the move possible across subscription
Since the subscriptions are not in the same tenants, you would not be able to move the snapshot directly based on the doc you referred to. Given the situation, the workaround will be:
-Create a VHD file from the snapshot in a storage account of the source subscription with below commands:
$rgname = ""
$SARGname=""
$snapshotname = ""
$storageaccountname = ""
$imagecontainername = ""
$imageblobname = "blobname.vhd"
$snap = Get-AzureRmSnapshot -ResourceGroupName $rgname -SnapshotName $snapshotname
$snapsasurl = grant-azurermsnapshotaccess -ResourceGroupName $rgname -SnapshotName $snapshotname -DurationInSecond 40000 -Access read
$targetstoragecontext = (Get-AzureRmStorageAccount -ResourceGroupName $SARGname -Name $storageaccountname).context
New-AzureStorageContainer -Name $imagecontainername -Context $targetstoragecontext -Permission container
$blobcopy=start-azurestorageblobcopy -AbsoluteUri $snapsasurl.AccessSAS -DestContainer $imagecontainername -DestContext $targetstoragecontext -DestBlob $imageblobname
$blobcopy | Get-AzureStorageBlobCopyState
-Copy this VHD file to a storage account of the destination subscription
-Download and install  Microsoft Azure Storage Explorer.
-Access the portal https://portal.azure.com >Click Storage accounts on the left panel>Click on the storage account name> Blobs> The container of the VHD file> Click on VHD, and you will see an URI, like https://linux905.blob.core.windows.net/vhds/cent12016729144748.vhd, linux905 is the name of the storage account and vhds is the container name.
-Click Storage accounts on the left pane and go to the storage page> Click on the name of the corresponding storage account>Keys>Copy the primary key
-Open the tool Azure Storage Explorer, and follow the steps below to connect to the storage account
-After the storage account is connected, please follow the steps below to create a copy for the OS disk
-Create a storage account in the destination subscription, and get it connected over Storage Explore as well.
-Access the container of the destination storage account and copy the VHD from the source storage account to it
After the copy is done, you will be able to create a managed disk from this copied VHD file.


Data viewer ignores precision parameter for timestamp data type

If the column data type is timestamp(3), 6 more zeros will be displayed. As shown in the figure:

System information:

Operating system：win10 LTSC 2018
DBeaver version：21.0.4

Thank you for the report. I reproduced it in MySQL database. Can you add what database is used on your screenshot?

Thank you for the report. I reproduced it in MySQL database. Can you add what database is used on your screenshot?

thank you for your reply！I use MySQL database

The same bug on Datetime datatype #12654

@git10135405 This additional zeroes are added by the driver and are not influenced by Dbeaver. As a workaround you can either use another driver or enable data formatting in connection settings.

Thank you @Matvey16 for the tip. Unfortunaly now regular DATETIME(0) columns get an extra triplet of zeroes.
Would you advise to report that to the MySQL crew as a bug?

@CComparon In my example I just added three f to see fractions, if you don't need them you can adjust it as you like. If you want precision to be 0, just don't add them and leave it as is yyyy-MM-dd HH:mm;ss
It is not necessarily a bug, this is just how their driver sends unformatted data to any tool. And for this reason among others we have an option to format data to your needs.

@Matvey16 thank you for your reply. My misunderstanding revolves around the fact that MySQL datetime has an associated precision subscript e.g. datetime(0) or datetime(3) meaning with second precision (resp millisecond). Our db schemas make extensive use of various precision levels for various usage. Ideally dbeaver would offer such a client side formatting per subscript too instead of for all datetime columns at once to make this possible. Please confirm if I didn't get confused with the driver vs client side distinction.

MySQL database uses this precision parameter for storing data, so it will just delete all excessive milliseconds in time of inserting. But when sending data to client, the driver sends them unformatted with maximum precision.
For now Dbeaver client side formatting only works for the entire connection.
If you have a means to do it, you can propose an option to MySQL team, so they add a property for their driver to only send datetime data according to chosen precision.
Also you can try using earlier drivers for this connection because our tests showed that on earlier versions it was working just as like you are asking.

@Matvey16
awesome! I tried to update the mysql driver and the problem was solved!

Here is a step-by-step guide：

@git10135405 That's great, so they already fixed it.
@CComparon You can update the MySQL driver. It looks like someone already decided to fix this in their latest version.

@git10135405
Thanks a bunch! It works like a charm...
@Matvey16
... except that I started liking the fact that DBeaver was converting datetimes to my local timezone (DB in UTC, locale is PST). Back to doing conversions on the fly ;)


Application drilldowns

Updated yaml structure after speaking with Eric:
All TTP, Anomaly and Correlation detections will have drilldown search associated with it
drilldown_searches:
- name: View the detection results for $user$ and $dest$
  search: '%orginal_detection_search% | search  user = $user$ dest = $dest$'

%orginal_detection_search% -> this is written in such syntax so that we can dynamically update drilldown search when the seach is updated, and to keep the yaml clean
%orginal_detection_search%->  this field will be replaced by the search string during build time from contentctl
Contentctl to make updates such that the following fields are optional in the yaml, if not present we use the following default,
earliest_offset: $info_min_time$
 latest_offset: $info_max_time$

FYI, I committed to this branch with the following fix.
All the updated detections went from the typo
%orginal_detection_search% to
%original_detection_search%


SessionService sometimes failing to fillProfileTextures

Sometimes, and I don't know why. When requesting a player profile data from https://sessionserver.mojang.com/session/minecraft/profile/{UUID} a singnature is added and the value returns a whole different JSON.
For example, I have attached 2 responses recieved from sessionserver.mojang.com one which SessionService can handle and one which it can't. The main difference between the two is the signature is missing from one of them and value is extremely different. This happens very rarely and can happen to any UUID with enough tries.

(FAILS) cee3f57caa5445f8ad5f7faa5a6a1daf.txt
(OK) c081aab64fef493b87066b2313ef6e5a.txt

For clarification, what is the problem you're getting as a result of this different data? Is it throwing an exception, or something else? Because I believe the current auth code should support the signature field already.
I will make sure to take a look sometime soon and see if any auth stuff has changed since the last the code was updated, regardless.

Actually, I think I see the problem: the requireSecure argument to fillProfileTextures does not affect the signature check, so payloads without signatures are unusable. This will be corrected soon.

The actual exception being thrown is "Decrypted textures payload for for another user. (expected name null)"

Ah, it's because the profile instance you're filling doesn't have a username set. I'll just relax the requirements so that works.

Maybe. But if you decode the "value" for both the ok file and the fail file. You'll see how vastly different the return json is. I dont think fillProfileTextures can process the different json at all.

I've pushed changes bringing the code up to speed with the way Mojang handles it in 1.15.2. It seems they ignore most of the fields, which is why the different format works with their code.
Let me know if the latest changes fix your issue, or if there are still problems.

Gonna assume this is fixed and close the issue, since it worked in my testing. Let me know if this is not the case and I'll reopen the issue.


[BUG] Installer URL and other missing from Package Details screen

Please confirm these before moving forward

[X] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions.
[X] This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version
3.1.1
Windows version, edition, and architecture
Windows 10 Pro x64
Describe your issue
Installer URL missing for all (most?) packages, as well as other info
Steps to reproduce the issue
Right click on an available update in the Software Updates tab, choose Package Details, see empty Installer URL and other info
The Manifest link is present, and following that you can find the package's *.Installer.yaml and look inside it to find the URL manually, so the data does exist for these packages
UniGetUI Log
n/a

Package Managers Logs
n/a

Relevant information
No response
Screenshots and videos
No response

Which packages are you trying to load?
Please share both your UniGetUI logs and the Package Manager logs

I'm not able to get the logs right now.
I've had this issue on several packages:  Miro, Figma, 7zip, Adobe Acrobat Reader, Microsoft Edge WebView2 Runtime, Zoom, etc
It seems to be all of them that have had updates in the last week or two.

I will investigate, but please, when possible, reproduce the bug and attach the logs

Hello @stevehoek, yoou seem to have a corrupt WinGet installation.
Please try to enable "Use Bundled WinGet instead of the WinGet COM API" under WinGet Settings, on UniGetUI Settings

Hi @marticliment
unfortunately that did not change anything for me.  When I run winget.exe from the CLI (the system version or the bundled version) it does show the package installer URL data correctly
winget show --id Microsoft.EdgeWebView2Runtime
Found Microsoft Edge WebView2 Runtime [Microsoft.EdgeWebView2Runtime]
Version: 127.0.2651.86
Publisher: Microsoft Corporation
Publisher Url: https://www.microsoft.com/
Publisher Support Url: https://github.com/MicrosoftEdge/WebView2Feedback/issues
Author: Microsoft Corporation
Moniker: webview2
Description: Embed web content (HTML, CSS, and JavaScript) in your native applications with Microsoft Edge WebView2.
Homepage: https://developer.microsoft.com/microsoft-edge/webview2/
License: Proprietary
License Url: https://www.microsoft.com/legal/terms-of-use
Privacy Url: https://privacy.microsoft.com/privacystatement
Copyright: © 2024 Microsoft Corporation. All rights reserved.
Copyright Url: https://www.microsoft.com/legal/intellectualproperty/trademarks
Release Notes Url: https://learn.microsoft.com/microsoft-edge/webview2/release-notes/
Documentation:
  Documentation: https://learn.microsoft.com/microsoft-edge/webview2/
Tags:
  webview
Installer:
  Installer Type: exe
  Installer Url: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/c638b5d5-4b2f-4845-baab-c9f4fd6c58ab/MicrosoftEdgeWebView2RuntimeInstallerX64.exe
  Installer SHA256: 8f0165de2f83174697bbdb273b6b53ea7d66bbc561d9a4ead5dacbfcbf8e8837
  Offline Distribution Supported: true

But in UniGetUI I only see this

Ok, thanks, i will investigate


Use the new name amazon.aws.s3_object

🗣 Description
This pull request modifies the role to use the new name amazon.aws_s3_object instead of the old, deprecated name amazon.aws.aws_s3.
💭 Motivation and context
The old name amazon.aws.aws_s3 is still accepted but not preferred.
🧪 Testing
All automated tests pass.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[ ] All new and existing tests pass.

The tests should pass once #49 is merged and this branch is rebased on top of develop.


fix: collect both app and client deps for license book

Closes #3714

This is the first step to fix https://github.com/camunda/camunda-modeler/issues/3714
Some information needs to be manually submitted:
missing license text: https-proxy-agent
missing license text: agent-base
missing license text: lru_map
missing license text: err-code
missing license text: typed-duration
missing license text: keyv
missing license text: @camunda/linting
missing license text: mitt
missing repository: @bpmn-io/cm-theme
missing license text: @bpmn-io/moddle-utils
missing repository: preact-compat
missing license text: preact-compat
missing repository: preact-hooks
missing license text: preact-hooks
missing repository: jsx-runtime
missing license text: jsx-runtime
missing repository: @camunda/form-linting
missing license text: bpmn-js
missing repository: feelers
missing repository: undefined
missing license text: undefined
missing repository: style-mod
missing repository: htm_preact
missing license text: htm_preact
missing license text: dmn-js-decision-table
missing license text: dmn-js-drd
missing license text: dmn-js-literal-expression
missing license text: dmn-js-shared
missing license text: dmn-js
missing repository: @bpmn-io/variable-resolver
missing license text: bpmn-js-color-picker
missing license text: bpmn-js-executable-fix
missing license text: cmmn-js
missing license text: hat
missing license text: @bpmn-io/form-js-editor
missing license text: @bpmn-io/form-js-playground
missing license text: @bpmn-io/form-js-viewer
missing repository: @camunda/example-data-properties-provider

Also, we need to figure out unknown licenses. This should however be resolved if we give the information above to the tool:
Summary of used third party licenses:
- MIT - 199
- Apache-2.0 - 6
- ISC - 10
- BSD-3-Clause - 13
- BSD-2-Clause - 1
- unknown - 3
- SEE LICENSE IN LICENSE - 10
- OFL-1.1 - 1
- MIT OR SEE LICENSE IN FEEL-FREE.md - 1
- MIT/X11 - 1

Also, we don't handle optional dependencies correctly right now. I believe the final license book should be composed of dependencies belonging to each platform. Still, it already looks much better and we could just manually supplement the single-platform deps' licenses instead.

I missed the optional dependencies' licenses.

Ready.


Compilation error: AnyCodable.swift not found

Schema.swift line 89 shows that "AnyCodable" is generated as the swift type for Any. However, AnyCodable.swift was intended to be an internal file only, so this breaks. We either need to copy the file into the generated files or find some other representation for this.

As a temporary workaround, the AnyCodable.swift file can be copied manually into the source (outside the Generated folder), which should resolve the compilation errors.

@PotterDai when you generate code, you will likely get a compilation error that type Any doesn't conform to RequestStringConvertible. Internally, Autorest will map the swagger "any" type to the AnyObject Swift type, which will not conform to the necessary protocol, so it may actually create more headache for you than when it was "broken". It will certainly require custom code.

@tjprescott  What would be the down side if we include AnyCodable.swift file as part of the generated code?


Index Nested Loop Join

For cases where we know the RHS is much smaller than the LHS of a join, and we have an index on the join key, we can do an index nested loop join. In the index nested loop join you use the keys on the RHS to do an index lookup into the LHS. As we are using unclustered indexes, this is generally only worth it if the RHS is very small (e.g. less than 0.1% of the LHS).
This is the case though if e.g. we have an IN() list that has been folded into a join; we know the exact cardinality of the IN() list, hence we can reliably determine if it is worth it or not.

Are you guys in a hurry with this one? If not can I pickt it up?

Hey, @aris-koning I'm currently developing an ART as a default secondary index, but I got a bit stuck because of a VLDB revision I got. I guess this task is dependent on the actual existence of indexes, but there is a (pretty bad) order index implementation there that you can use as a basis there.

I am not in a hurry myself and I can take a look at the order index. With ART you mean Adaptive Radix Tree? Is your ongoing work in a branch or fork somewhere? It would already be helpful if these indices are going to have a common interface layout.

Yeah, all indexes will have the same interface and Art is the adaptive radix tree.
Tbh, I guess the plan is to actually drop the order index (I only did it to have a feeling on how to actually implement the indexes in the system) and replace it with a bw-tree or b+tree in the near future since (I think) they are more efficient for range queries than an ART.
@Mytherin can correct me if I'm wrong, but I think for this task you just need to change the index optimizer layer, but I only have it in the ART branch as well.

For this task you need to create a new join operator, IndexNestedLoopJoin, that would replace a scan that would be fed into the join on the LHS with index lookups based on the values obtained from the RHS. I think you can internally use the PhysicalIndexScan to perform the lookups on the LHS inside the IndexNestedLoopJoin implementation. In that way, I think any future changes to the interface shouldn't break anything too much as any changes to the index will also update the PhysicalIndexScan to work with the index (obviously).
To answer your other question @aris-koning this is not a high priority issue, it is fine if you take it, I think you can work on it in parallel to @pholanda working on the actual index without conflicts.


App doesn't seem to use the fixtures file

removed it for now. this will most likely be replaced with the updated database code anyway

removed it for now. this will most likely be replaced with the updated database code anyway


dccm initialization

Hi, I was trying to understand how dccm works, but it keep reporting assertion fail for output data port of dccm is always x. I was trying to use '.word' in my assembly file, and change the link.ld file to make the address fit the dccm region, but the dccm is never loaded with those word i write. I am curious about when and how dccm load the word from my data.hex file?

try to understand hello_world_dccm.ld/cmark_dccm.ld - examples how to create executables with DCCM preload for simulations. In real life, CPU has to write DCCM with aligned word size stores before use in program. CPU Boot code is the place for DCCM initialization.

try to understand hello_world_dccm.ld/cmark_dccm.ld - examples how to create executables with DCCM preload for simulations. In real life, CPU has to write DCCM with aligned word size stores before use in program. CPU Boot code is the place for DCCM initialization.

Thanks for explaining that, I will check it later, and yesterday I noticed another problem. The store instruction get permission to write back to dccm at dc5 stage, but if I launch an instruction to load data from the same memory space right after that store instruction, the load instruction tried to read data from dccm at dc2 stage and find x in its output port. Then it will raise an assertion failure and I can't find the logic that stop the load instruction from launching.
example code
li x1, 0xf004000
li x2, 0xffffffff
sw x2, 0x0(x1)
lw x3, 0x0(x1)

Thanks for explaining that, I thought it is the hardware's job to link data between dccm with memory. I noticed another problem yesterday. The store instruction write data back to dccm at dc5 stage, but if I launch a load instruction accessing the same memory space, it tried to read data from dccm at dc2 stage. Since the data has not been written yet, it will read x in the output port and raise several assertion failure.  So I'll be very grateful if you can help me understand how eh1 deal with these sort of reference (if it does) , so I can eliminate those assertion failure.
sample code
li x2, 0xf004000
li x3, 0xffffffff
sw x3, 0x0(x2)
lw x4, 0x0(x2)

try to understand hello_world_dccm.ld/cmark_dccm.ld - examples how to create executables with DCCM preload for simulations. In real life, CPU has to write DCCM with aligned word size stores before use in program. CPU Boot code is the place for DCCM initialization.

Thanks for explaining that, I thought it is the hardware's job to link data between dccm and memory. I noticed another problem yesterday. The store instruction write data back to dccm at dc5 stage, but if I launch a load instruction accessing the same memory space, it tried to read data from dccm at dc2 stage. Since the data has not been written yet, it will read x in the output port and raise several assertion failures. So I'll be very grateful if you can help me understand how eh1 deal with these sort of references or data hazard (if it does).
sample code
li x2, 0xf004000
li x3, 0xffffffff
sw x3, 0x0(x2)
lw x4, 0x0(x2)

Comments in issue #36 may clarify this for you..


about server setup?

How can I edit the ... /config/config.ini file and put it on the server?
can you also explain how to put this project on the server and run it?

Having the same issue.
Any solutions?

Same problem/doubt here

No server needed. 😃
Following the Mozilla signaling documentation and the flutter demo repository, you can make the signaling flow with a simple Firebase Database (Cloud Firestore or Realtime Database).
Replacing the _send() method with your Firebase implementation:
Future setCallData(String groupId, String userId, String type, Map<String, dynamic> data) async {
  try {
    final DocumentReference ref = FirebaseFirestore.instance
        .collection(GroupsRepository.collection)
        .doc(groupId);

    await ref.update({
      "members.$userId.callData.type": type,
      "members.$userId.callData.data": data,
    });
  } catch (e) {
    print(e);
  }
}

When observing the changes in the group, check all the members/$any_userId/callData and handle anything related with the current user (when $userId == members/$any_userId/callData/data/to) with the onMessage() method.
{
 'to': id,
 'from': _selfId,
 'candidate': {
          ....
  },
  'session_id': this._sessionId,
}

This guy shows this concept in a React app.


⚠ ClamAV has degraded performance

In 4aa7e34, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in 6bd9af6.