Disable webpack build progress reporting for Angular projects

Description
Webpack has started writing extra progress information to stderr, which we pass through into calls to LogError. This results in messages like
 to be shown in the console output when running a new Angular app. Note, that these are not error messages, but show up as errors. The app is still running.
Risk
Very low. We're not making any functional changes. Just preventing the messages to show up as errors.
User impact
The app stills runs successfully, and users will now not see any false 'fail' messages.
Addresses https://github.com/aspnet/AspNetCore-ManualTests/issues/43

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=419338

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/2409
https://github.com/aspnet/AspNetCore-Internal/issues/3295

Approved for GA, but please hold for the branch to open.

@mkArtakMSFT I'll merge this on Sunday/Monday once we get the all-clear on 3.1-preview3

That's fine, @wtgodbe. I'll try to bring this to a green state.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=419338

@wtgodbe feel free to force-merge this, if there won't be green builds by the time. The failures are caused by unrelated flaky tests. There are already existing issues for all of these and I've pinged the right folks to get these fixed.


Update hash of topo_2d.txt in inversion notebooks

Update the hash for data/topo_2d.txt with the one currently stored in main.

@dccowan I noticed that the hash for topo_2d.txt in the notebooks wasn't the same as the file we are storing in main. I opened this PR to fix that. Let me know if that's ok for you.

Close in favor of #37


Quotes are removed around data url

The following rule gets rendered without the quotes around the url.
.wingman :deep(.btn[disabled]::after) {
    content: url("data:image/svg+xml;charset=UTF-8, <svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='red' d='M256 8C119.034 8 8 119.033 8 256s111.034 248 248 248 248-111.034 248-248S392.967 8 256 8zm130.108 117.892c65.448 65.448 70 165.481 20.677 235.637L150.47 105.216c70.204-49.356 170.226-44.735 235.638 20.676zM125.892 386.108c-65.448-65.448-70-165.481-20.677-235.637L361.53 406.784c-70.203 49.356-170.226 44.736-235.638-20.676z'></path></svg>");
}

Hi @svieujot, By default we will remove the double quotes around the css property. That might be an issue here.

We are doing this becuase we have to use double quotes to make the followin css property value valid rust code "1.3em/1.2". We will remove these double quotes by default.
If you want to retain double quotes, then you have to use the raw_str("content").  Please let me know if this solves the problem. You can find reference here.

Hello @abishekatp . Thank you for the feedback.
I tried several combinations of those but I can't make it work.
Please see this test:
#[test]
fn test_55() {
    let style = style_test! {
        .btn.disabled::after {
            content: url(raw_str(r#"data:image/svg+xml;charset=UTF-8, <svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='red' d='M256 8C119.034 8 8 z'></path></svg>"#));
        }
    };
    assert_eq!(
        style,
        r#".btn.disabled.test::after{content: url("data:image/svg+xml;charset=UTF-8, <svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='red' d='M256 8C119.034 8 8 z'></path></svg>");}"#
    );
}

Am I doing something wrong ?

I think the following code will solve this problem.(Thank you for you patience 😀)
#[test]
fn test_55() {
    let style = style_test! {
        .btn.disabled::after {
            content: r#"url("data:image/svg+xml;charset=UTF-8, <svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='red' d='M256 8C119.034 8 8 z'></path></svg>")"#;
        }
    };
    assert_eq!(
        style,
        r#".btn.disabled.test::after{content: url("data:image/svg+xml;charset=UTF-8, <svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 512 512'><path fill='red' d='M256 8C119.034 8 8 z'></path></svg>");}"#
    );
}

Indeed it does.
Thank you !


How to speed up when preprocess the corpus ?

Dear all,
According to the issue, I follow this tutorial to train wmt15.
When I perform preprocess the corpus, and set preprocess_pthreads as 10, but it doesn't seem to speed up as I expected.
How could I speed up this step ?
Thank you for your help.
th preprocess.lua -train_src ../wmt15-de-en/wmt15-all-de-en.en.tok -train_tgt ../wmt15-de-en/wmt15-all-de-en.de.tok -valid_src ../wmt15-de-en/newstest2013.en.tok -valid_tgt ../wmt15-de-en/newstest2013.de.tok -save_data ../wmt15-de-en/wmt15-all-en-de -preprocess_pthreads 10

<p.s.> My CPU has 40 thread

Hi all,
You can following here from OpenNMT Forum.
Thank you.


wiring esp32 <-> ikea pcb

where can i find the connection between esp and ikea pcb ?

only  1 think on the mqtt motor_version it write
announce = awoke
framework_version = Jan 11 2021-08:26:42
version = Jan 11 2021-08:26:42
motor_version = Not detected!
when i plug in the esp it drives up and then nothing more

only  1 think on the mqtt motor_version it write
announce = awoke
framework_version = Jan 11 2021-08:26:42
version = Jan 11 2021-08:26:42
motor_version = Not detected!
when i plug in the esp it drives up and then nothing more

Your terminal application does not support escape sequences.
Line editing and history features are disabled.
On Windows, try using Putty instead.
←[0;33mW (2748) fyrtur-esp32: Stack: 2188←[0m
←[0;31mE (2758) fyrtur-esp32: Temperature sensor not found!←[0m
←[0;32mI (2758) UART: Configuring motor unit UART..←[0m
←[0;32mI (2758) BLINDS: Running on core #1←[0m
←[0;32mI (2758) BLINDS_UART: Running on core #1←[0m
←[0;33mW (2758) BLINDS: blinds_task_read_status_reg - Stack: 2140←[0m
←[0;32mI (3768) BLINDS: Checking motor module...←[0m
←[0;33mW (3768) BLINDS: blinds_task_read_status_reg - Stack: 2028←[0m
←[0;31mE (8768) BLINDS: Fyrtur motor not connected!←[0m
←[0;32mI (8768) NODE-FRAMEWORK: [APP] Free memory: 254748 bytes←[0m
←[0;32mI (8768) NODE-FRAMEWORK: [APP] IDF version: v4.3-dev-1901-g178b122c1←[0m
←[0;32mI (8778) NODE-FRAMEWORK: Running on core #0←[0m
←[0;32mI (8778) NODE-FRAMEWORK: Using project/base name 'fyrtur-esp32'←[0m
←[0;32mI (8828) NODE-FRAMEWORK: NVS open OK←[0m
Create led task..
←[0;32mI (8838) wifi_manager: Set STA IP String to: <IP_ADDRESS>←[0m
←[0;32mI (8838) LED: [LED] Running on core #1←[0m
←[0;32mI (8848) system_api: Base MAC address is not set←[0m
D (8848) LED: stack: 1672←[0m
←[0;32mI (8848) system_api: read default base MAC address from EFUSE←[0m
←[0;32mI (8878) wifi_init: rx ba win: 6←[0m
←[0;32mI (8878) wifi_init: tcpip mbox: 32←[0m
←[0;32mI (8878) wifi_init: udp mbox: 6←[0m
←[0;32mI (8888) wifi_init: tcp mbox: 6←[0m
←[0;32mI (8898) wifi_init: tcp tx win: 5744←[0m
←[0;32mI (8898) wifi_init: tcp rx win: 5744←[0m
←[0;32mI (8898) wifi_init: tcp mss: 1440←[0m
←[0;32mI (8908) wifi_init: WiFi IRAM OP enabled←[0m
←[0;32mI (8908) wifi_init: WiFi RX IRAM OP enabled←[0m
←[0;32mI (8908) wifi_manager: AP SSID: fyrtur-esp32-7baf1c←[0m
←[0;32mI (9738) phy: phy_version: 4500, 0cd6843, Sep 17 2020, 15:37:07, 0, 0←[0m
D (9738) wifi_manager: wifi_manager_event_handler Stack: 2700←[0m
←[0;32mI (9738) wifi_manager: WIFI_EVENT_STA_START←[0m
←[0;32mI (9738) http_server: Registering URI handlers←[0m
←[0;32mI (9758) wifi_manager: Set AP auto shutdown to enabled←[0m
D (9758) wifi_manager: wifi_manager queue loop - free heap 191192, stack: 1180←[0m
←[0;32mI (9768) wifi_manager: MESSAGE: ORDER_LOAD_AND_RESTORE_STA←[0m
←[0;32mI (9768) wifi_manager: wifi_manager_fetch_wifi_sta_config: ssid:Altersheim E.V. password:syncm4st3r1sb3st←[0m
D (9788) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_ssid:fyrtur-esp32-7baf1c←[0m
D (9798) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_pwd:esp32pwd←[0m
D (9798) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_channel:1←[0m
D (9808) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_hidden (1 = yes):0←[0m
D (9808) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_bandwidth (1 = 20MHz, 2 = 40MHz)1←[0m
D (9818) wifi_manager: wifi_manager_fetch_wifi_settings: sta_only (0 = APSTA, 1 = STA when connected):1←[0m
D (9828) wifi_manager: wifi_manager_fetch_wifi_settings: sta_power_save (1 = yes):0←[0m
D (9838) wifi_manager: wifi_manager_fetch_wifi_settings: sta_static_ip (0 = dhcp client, 1 = static ip):0←[0m
←[0;32mI (9848) wifi_manager: Saved wifi found on startup. Will attempt to connect.←[0m
D (9858) wifi_manager: wifi_manager queue loop - free heap 191108, stack: 1180←[0m
←[0;32mI (9858) wifi_manager: MESSAGE: ORDER_CONNECT_STA←[0m
←[0;32mI (9768) NODE-FRAMEWORK: Publishing as fyrtur-esp32-7baf1c←[0m
←[0;32mI (9878) mqtt_manager: MQTT manager start←[0m
D (9878) mqtt_manager: mqtt_manager_do_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0m
←[0;32mI (9888) mqtt_manager: mqtt_manager_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0m
←[0;32mI (9898) mqtt_manager: MQTT config reloaded succesfully. Starting AP temporarily...←[0m
←[0;32mI (9908) wifi_manager: Set AP auto shutdown to enabled←[0m
D (9918) wifi_manager: wifi_manager queue loop - free heap 190668, stack: 1180←[0m
←[0;32mI (9928) wifi_manager: MESSAGE: ORDER_START_AP←[0m
←[0;32mI (9918) mqtt_manager: Create MQTT manager task..←[0m
D (9938) wifi_manager: wifi_manager_event_handler Stack: 1084←[0m
←[0;32mI (9938) wifi_manager: WIFI_EVENT_AP_START←[0m
D (9938) LED: queue rcv stack: 1672←[0m
←[0;32mI (9938) mqtt_manager: [MQTT] Running on core #1←[0m
←[0;32mI (9948) LED: led 0 : 0 0 30 (1000 ms)←[0m
←[0;32mI (9938) fyrtur-esp32: Setting verbose motor MQTT diagnostics to 0←[0m
esp32> ←[0;32mI (10028) http_server: Registering URI handlers←[0m
←[0;32mI (10028) dns_server: DNS server listening on address: <IP_ADDRESS>←[0m
←[0;32mI (10028) dns_server: DNS Server listening on 53/udp←[0m
D (11538) wifi_manager: wifi_manager_event_handler Stack: 1084←[0m
←[0;32mI (11538) wifi_manager: WIFI_EVENT_STA_CONNECTED←[0m
←[0;32mI (11538) mqtt_manager: WIFI_EVENT_STA_CONNECTED←[0m
←[0;33mW (11548) mqtt_manager:  Heap: 173092←[0m
D (11558) mqtt_manager: loop - stack: 1556←[0m
←[0;32mI (13338) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>←[0m
D (13338) wifi_manager: wifi_manager_event_handler Stack: 1004←[0m
←[0;32mI (13348) wifi_manager: IP_EVENT_STA_GOT_IP←[0m
←[0;32mI (13348) mqtt_manager: IP_EVENT_STA_GOT_IP←[0m
D (13348) wifi_manager: wifi_manager queue loop - free heap 173044, stack: 1180←[0m
←[0;33mW (13348) mqtt_manager:  Heap: 172984←[0m
D (13358) mqtt_manager: loop - stack: 1556←[0m
←[0;32mI (13358) wifi_manager: WM_EVENT_STA_GOT_IP←[0m
←[0;33mW (13378) mqtt_manager:  Heap: 172984←[0m
←[0;32mI (13378) mqtt_manager: Connecting to the MQTT server (mqtt://<IP_ADDRESS>:1883) (reconnect=1)..←[0m
←[0;32mI (13378) wifi_manager: Set STA IP String to: <IP_ADDRESS>←[0m
←[0;32mI (13388) mqtt_manager: json {"uri":"mqtt://<IP_ADDRESS>:1883","urc":1, "error":""}
←[0m
←[0;32mI (13398) wifi_manager: Start AP shutdown timer...←[0m
←[0;33mW (13398) mqtt_manager:  Heap: 171072←[0m
←[0;32mI (13408) mqtt_manager: Starting MQTT client ..←[0m
D (13418) LED: queue rcv stack: 1672←[0m
D (13418) mqtt_manager: loop - stack: 1508←[0m
←[0;32mI (13428) LED: led 0 : 30 0 30 (50 ms)←[0m
D (13418) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=7←[0m
D (13458) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=1←[0m
←[0;32mI (13458) mqtt_manager: MQTT_EVENT_CONNECTED←[0m
←[0;33mW (13458) mqtt_manager:  Heap: 163724←[0m
←[0;32mI (13478) NODE-FRAMEWORK: MQTT_EVENT_CONNECTED←[0m
←[0;33mW (13478) mqtt_manager:  Heap: 163912←[0m
←[0;33mW (13478) NODE-FRAMEWORK: [EVENT] Stack: 3352 heap: 163828←[0m
←[0;32mI (13488) mqtt_manager: Subscribe to /home/control/all/#←[0m
←[0;32mI (13488) mqtt_manager: MQTT server connected!←[0m
←[0;32mI (13498) mqtt_manager: json {"uri":"mqtt://<IP_ADDRESS>:1883","urc":2, "error":""}
←[0m
←[0;32mI (13498) mqtt_manager: Subscribe to /home/control/fyrtur-esp32/#←[0m
←[0;32mI (13518) mqtt_manager: Subscribe to /home/control/fyrtur-esp32-7baf1c/#←[0m
←[0;32mI (13518) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/announce : awoke←[0m
←[0;32mI (13528) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/framework_version : Jan 11 2021-08:26:42←[0m
D (13538) mqtt_manager: mqtt_manager_do_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0;32mI (13538) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/config : {    "name": "fyrtur-esp32-7baf1c",     "uniq←[0m
ue_id": "fyrtur-esp32-7baf1c",     "device_class": "blind",     "command_topic": "/home/control/fyrtur-esp32-7baf1c/command",     "position_topic": "/home/cover/fyrtur-esp32-7baf1c/position",     "set_position_topic": "/home/control/fyrtur-esp32-7baf1c/setD (13538) LED: queue rcv stack: 1672←[0m
/target_position",     "position_open": 1000     }←[0m
←[0;32mI (13568) mqtt_manager: MQTT config was not saved to flash because no change has been detected.←[0m
←[0;32mI (13588) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/version : Jan 11 2021-08:26:42←[0m
←[0;32mI (13588) LED: led 0 : 30 0 30 (2000 ms)←[0m
←[0;32mI (13598) wifi_manager: Set AP auto shutdown to enabled←[0m
←[0;32mI (13618) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/motor_version : Not detected!←[0m
←[0;32mI (13628) wifi_manager: Start AP shutdown timer...←[0m
D (13638) mqtt_manager: loop - stack: 628←[0m
←[0;32mI (13638) mqtt_manager: Subscribe to /home/control/fyrtur-blinds/#←[0m
D (13658) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13658) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=54508←[0m
D (13678) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13678) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=16068←[0m
D (13688) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13688) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=11200←[0m
D (13708) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13708) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=3197←[0m

Your terminal application does not support escape sequences.
Line editing and history features are disabled.
On Windows, try using Putty instead.
←[0;33mW (2748) fyrtur-esp32: Stack: 2188←[0m
←[0;31mE (2758) fyrtur-esp32: Temperature sensor not found!←[0m
←[0;32mI (2758) UART: Configuring motor unit UART..←[0m
←[0;32mI (2758) BLINDS: Running on core #1←[0m
←[0;32mI (2758) BLINDS_UART: Running on core #1←[0m
←[0;33mW (2758) BLINDS: blinds_task_read_status_reg - Stack: 2140←[0m
←[0;32mI (3768) BLINDS: Checking motor module...←[0m
←[0;33mW (3768) BLINDS: blinds_task_read_status_reg - Stack: 2028←[0m
←[0;31mE (8768) BLINDS: Fyrtur motor not connected!←[0m
←[0;32mI (8768) NODE-FRAMEWORK: [APP] Free memory: 254748 bytes←[0m
←[0;32mI (8768) NODE-FRAMEWORK: [APP] IDF version: v4.3-dev-1901-g178b122c1←[0m
←[0;32mI (8778) NODE-FRAMEWORK: Running on core #0←[0m
←[0;32mI (8778) NODE-FRAMEWORK: Using project/base name 'fyrtur-esp32'←[0m
←[0;32mI (8828) NODE-FRAMEWORK: NVS open OK←[0m
Create led task..
←[0;32mI (8838) wifi_manager: Set STA IP String to: <IP_ADDRESS>←[0m
←[0;32mI (8838) LED: [LED] Running on core #1←[0m
←[0;32mI (8848) system_api: Base MAC address is not set←[0m
D (8848) LED: stack: 1672←[0m
←[0;32mI (8848) system_api: read default base MAC address from EFUSE←[0m
←[0;32mI (8878) wifi_init: rx ba win: 6←[0m
←[0;32mI (8878) wifi_init: tcpip mbox: 32←[0m
←[0;32mI (8878) wifi_init: udp mbox: 6←[0m
←[0;32mI (8888) wifi_init: tcp mbox: 6←[0m
←[0;32mI (8898) wifi_init: tcp tx win: 5744←[0m
←[0;32mI (8898) wifi_init: tcp rx win: 5744←[0m
←[0;32mI (8898) wifi_init: tcp mss: 1440←[0m
←[0;32mI (8908) wifi_init: WiFi IRAM OP enabled←[0m
←[0;32mI (8908) wifi_init: WiFi RX IRAM OP enabled←[0m
←[0;32mI (8908) wifi_manager: AP SSID: fyrtur-esp32-7baf1c←[0m
←[0;32mI (9738) phy: phy_version: 4500, 0cd6843, Sep 17 2020, 15:37:07, 0, 0←[0m
D (9738) wifi_manager: wifi_manager_event_handler Stack: 2700←[0m
←[0;32mI (9738) wifi_manager: WIFI_EVENT_STA_START←[0m
←[0;32mI (9738) http_server: Registering URI handlers←[0m
←[0;32mI (9758) wifi_manager: Set AP auto shutdown to enabled←[0m
D (9758) wifi_manager: wifi_manager queue loop - free heap 191192, stack: 1180←[0m
←[0;32mI (9768) wifi_manager: MESSAGE: ORDER_LOAD_AND_RESTORE_STA←[0m
←[0;32mI (9768) wifi_manager: wifi_manager_fetch_wifi_sta_config: ssid:Altersheim E.V. password:syncm4st3r1sb3st←[0m
D (9788) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_ssid:fyrtur-esp32-7baf1c←[0m
D (9798) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_pwd:esp32pwd←[0m
D (9798) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_channel:1←[0m
D (9808) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_hidden (1 = yes):0←[0m
D (9808) wifi_manager: wifi_manager_fetch_wifi_settings: SoftAP_bandwidth (1 = 20MHz, 2 = 40MHz)1←[0m
D (9818) wifi_manager: wifi_manager_fetch_wifi_settings: sta_only (0 = APSTA, 1 = STA when connected):1←[0m
D (9828) wifi_manager: wifi_manager_fetch_wifi_settings: sta_power_save (1 = yes):0←[0m
D (9838) wifi_manager: wifi_manager_fetch_wifi_settings: sta_static_ip (0 = dhcp client, 1 = static ip):0←[0m
←[0;32mI (9848) wifi_manager: Saved wifi found on startup. Will attempt to connect.←[0m
D (9858) wifi_manager: wifi_manager queue loop - free heap 191108, stack: 1180←[0m
←[0;32mI (9858) wifi_manager: MESSAGE: ORDER_CONNECT_STA←[0m
←[0;32mI (9768) NODE-FRAMEWORK: Publishing as fyrtur-esp32-7baf1c←[0m
←[0;32mI (9878) mqtt_manager: MQTT manager start←[0m
D (9878) mqtt_manager: mqtt_manager_do_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0m
←[0;32mI (9888) mqtt_manager: mqtt_manager_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0m
←[0;32mI (9898) mqtt_manager: MQTT config reloaded succesfully. Starting AP temporarily...←[0m
←[0;32mI (9908) wifi_manager: Set AP auto shutdown to enabled←[0m
D (9918) wifi_manager: wifi_manager queue loop - free heap 190668, stack: 1180←[0m
←[0;32mI (9928) wifi_manager: MESSAGE: ORDER_START_AP←[0m
←[0;32mI (9918) mqtt_manager: Create MQTT manager task..←[0m
D (9938) wifi_manager: wifi_manager_event_handler Stack: 1084←[0m
←[0;32mI (9938) wifi_manager: WIFI_EVENT_AP_START←[0m
D (9938) LED: queue rcv stack: 1672←[0m
←[0;32mI (9938) mqtt_manager: [MQTT] Running on core #1←[0m
←[0;32mI (9948) LED: led 0 : 0 0 30 (1000 ms)←[0m
←[0;32mI (9938) fyrtur-esp32: Setting verbose motor MQTT diagnostics to 0←[0m
esp32> ←[0;32mI (10028) http_server: Registering URI handlers←[0m
←[0;32mI (10028) dns_server: DNS server listening on address: <IP_ADDRESS>←[0m
←[0;32mI (10028) dns_server: DNS Server listening on 53/udp←[0m
D (11538) wifi_manager: wifi_manager_event_handler Stack: 1084←[0m
←[0;32mI (11538) wifi_manager: WIFI_EVENT_STA_CONNECTED←[0m
←[0;32mI (11538) mqtt_manager: WIFI_EVENT_STA_CONNECTED←[0m
←[0;33mW (11548) mqtt_manager:  Heap: 173092←[0m
D (11558) mqtt_manager: loop - stack: 1556←[0m
←[0;32mI (13338) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>←[0m
D (13338) wifi_manager: wifi_manager_event_handler Stack: 1004←[0m
←[0;32mI (13348) wifi_manager: IP_EVENT_STA_GOT_IP←[0m
←[0;32mI (13348) mqtt_manager: IP_EVENT_STA_GOT_IP←[0m
D (13348) wifi_manager: wifi_manager queue loop - free heap 173044, stack: 1180←[0m
←[0;33mW (13348) mqtt_manager:  Heap: 172984←[0m
D (13358) mqtt_manager: loop - stack: 1556←[0m
←[0;32mI (13358) wifi_manager: WM_EVENT_STA_GOT_IP←[0m
←[0;33mW (13378) mqtt_manager:  Heap: 172984←[0m
←[0;32mI (13378) mqtt_manager: Connecting to the MQTT server (mqtt://<IP_ADDRESS>:1883) (reconnect=1)..←[0m
←[0;32mI (13378) wifi_manager: Set STA IP String to: <IP_ADDRESS>←[0m
←[0;32mI (13388) mqtt_manager: json {"uri":"mqtt://<IP_ADDRESS>:1883","urc":1, "error":""}
←[0m
←[0;32mI (13398) wifi_manager: Start AP shutdown timer...←[0m
←[0;33mW (13398) mqtt_manager:  Heap: 171072←[0m
←[0;32mI (13408) mqtt_manager: Starting MQTT client ..←[0m
D (13418) LED: queue rcv stack: 1672←[0m
D (13418) mqtt_manager: loop - stack: 1508←[0m
←[0;32mI (13428) LED: led 0 : 30 0 30 (50 ms)←[0m
D (13418) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=7←[0m
D (13458) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=1←[0m
←[0;32mI (13458) mqtt_manager: MQTT_EVENT_CONNECTED←[0m
←[0;33mW (13458) mqtt_manager:  Heap: 163724←[0m
←[0;32mI (13478) NODE-FRAMEWORK: MQTT_EVENT_CONNECTED←[0m
←[0;33mW (13478) mqtt_manager:  Heap: 163912←[0m
←[0;33mW (13478) NODE-FRAMEWORK: [EVENT] Stack: 3352 heap: 163828←[0m
←[0;32mI (13488) mqtt_manager: Subscribe to /home/control/all/#←[0m
←[0;32mI (13488) mqtt_manager: MQTT server connected!←[0m
←[0;32mI (13498) mqtt_manager: json {"uri":"mqtt://<IP_ADDRESS>:1883","urc":2, "error":""}
←[0m
←[0;32mI (13498) mqtt_manager: Subscribe to /home/control/fyrtur-esp32/#←[0m
←[0;32mI (13518) mqtt_manager: Subscribe to /home/control/fyrtur-esp32-7baf1c/#←[0m
←[0;32mI (13518) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/announce : awoke←[0m
←[0;32mI (13528) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/framework_version : Jan 11 2021-08:26:42←[0m
D (13538) mqtt_manager: mqtt_manager_do_fetch_config: URI:'mqtt://<IP_ADDRESS>:1883' username:'' password:'' auto-reconnect: 1←[0;32mI (13538) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/config : {    "name": "fyrtur-esp32-7baf1c",     "uniq←[0m
ue_id": "fyrtur-esp32-7baf1c",     "device_class": "blind",     "command_topic": "/home/control/fyrtur-esp32-7baf1c/command",     "position_topic": "/home/cover/fyrtur-esp32-7baf1c/position",     "set_position_topic": "/home/control/fyrtur-esp32-7baf1c/setD (13538) LED: queue rcv stack: 1672←[0m
/target_position",     "position_open": 1000     }←[0m
←[0;32mI (13568) mqtt_manager: MQTT config was not saved to flash because no change has been detected.←[0m
←[0;32mI (13588) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/version : Jan 11 2021-08:26:42←[0m
←[0;32mI (13588) LED: led 0 : 30 0 30 (2000 ms)←[0m
←[0;32mI (13598) wifi_manager: Set AP auto shutdown to enabled←[0m
←[0;32mI (13618) NODE-FRAMEWORK: Publish: /home/node/fyrtur-esp32-7baf1c/motor_version : Not detected!←[0m
←[0;32mI (13628) wifi_manager: Start AP shutdown timer...←[0m
D (13638) mqtt_manager: loop - stack: 628←[0m
←[0;32mI (13638) mqtt_manager: Subscribe to /home/control/fyrtur-blinds/#←[0m
D (13658) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13658) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=54508←[0m
D (13678) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13678) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=16068←[0m
D (13688) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13688) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=11200←[0m
D (13708) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=3←[0m
←[0;32mI (13708) mqtt_manager: MQTT_EVENT_SUBSCRIBED, msg_id=3197←[0m

ANDLE MSG: control:command : open
←[0;31mE (113948) fyrtur-esp32: command: invalid cmd!←[0m
D (113958) LED: queue rcv stack: 1672←[0m
←[0;32mI (113958) LED: led 0 : 30 0 30 (100 ms)←[0m
D (120778) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6←[0m
←[0;32mI (120778) NODE-FRAMEWORK: MQTT_EVENT_DATA←[0m
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
←[0;31mE (120788) fyrtur-esp32: command: invalid cmd!←[0m
D (120808) LED: queue rcv stack: 1672←[0m
←[0;32mI (120808) LED: led 0 : 30 0 30 (100 ms)←[0m
D (122148) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6←[0m
←[0;32mI (122148) NODE-FRAMEWORK: MQTT_EVENT_DATA←[0m
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
←[0;31mE (122158) fyrtur-esp32: command: invalid cmd!←[0m
D (122178) LED: queue rcv stack: 1672←[0m
←[0;32mI (122178) LED: led 0 : 30 0 30 (100 ms)←[0m

ANDLE MSG: control:command : open
←[0;31mE (113948) fyrtur-esp32: command: invalid cmd!←[0m
D (113958) LED: queue rcv stack: 1672←[0m
←[0;32mI (113958) LED: led 0 : 30 0 30 (100 ms)←[0m
D (120778) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6←[0m
←[0;32mI (120778) NODE-FRAMEWORK: MQTT_EVENT_DATA←[0m
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
←[0;31mE (120788) fyrtur-esp32: command: invalid cmd!←[0m
D (120808) LED: queue rcv stack: 1672←[0m
←[0;32mI (120808) LED: led 0 : 30 0 30 (100 ms)←[0m
D (122148) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6←[0m
←[0;32mI (122148) NODE-FRAMEWORK: MQTT_EVENT_DATA←[0m
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
←[0;31mE (122158) fyrtur-esp32: command: invalid cmd!←[0m
D (122178) LED: queue rcv stack: 1672←[0m
←[0;32mI (122178) LED: led 0 : 30 0 30 (100 ms)←[0m

D (98568) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6
I (98568) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
D (98588) LED: queue rcv stack: 1672
I (98588) LED: led 0 : 30 0 30 (100 ms)
W (98588) BLINDS: queue - Stack: 1688
I (98598) BLINDS: Move (direction Up, revs 0.00, force_small_steps-flag 0, override_limits: 0
I (98608) blinds_task_move: Move: Up - 0.00 revs, target -1.00, force_small_steps 0, force_mov 0
I (98618) blinds_task_move: Starting continuous movement
E (98628) BLINDS: Already up!
D (109848) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6
I (109858) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=CLOSE
HANDLE MSG: control:command : CLOSE
D (109868) LED: queue rcv stack: 1672
I (109868) LED: led 0 : 30 0 30 (100 ms)
W (109868) BLINDS: queue - Stack: 1528
I (109878) BLINDS: Move (direction Down, revs 0.00, force_small_steps-flag 0, override_limits: 0
I (109888) blinds_task_move: Move: Down - 0.00 revs, target -1.00, force_small_steps 0, force_mov 0
I (109908) blinds_task_move: Starting continuous movement
I (109908) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/status : Moving
I (109918) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/direction : Down
I (109918) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/target_position : 0
W (109938) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (110458) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (199218) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (199738) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (200258) BLINDS: blinds_task_read_status_reg - Stack: 1400
D (200288) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, even                  t_id=6
I (200288) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=STOP
HANDLE MSG: control:command : STOP
D (200308) LED: queue rcv stack: 1672
I (200308) LED: led 0 : 30 0 30 (100 ms)
W (200308) BLINDS: queue - Stack: 1400
I (200318) BLINDS: Stop
W (200778) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (201298) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (201818) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (202338) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (202858) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (203378) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (203898) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (204418) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (204938) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (205458) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (205978) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (206498) BLINDS: blinds_task_read_status_reg - Stack: 1400
the motor not doing anything

D (98568) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6
I (98568) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=OPEN
HANDLE MSG: control:command : OPEN
D (98588) LED: queue rcv stack: 1672
I (98588) LED: led 0 : 30 0 30 (100 ms)
W (98588) BLINDS: queue - Stack: 1688
I (98598) BLINDS: Move (direction Up, revs 0.00, force_small_steps-flag 0, override_limits: 0
I (98608) blinds_task_move: Move: Up - 0.00 revs, target -1.00, force_small_steps 0, force_mov 0
I (98618) blinds_task_move: Starting continuous movement
E (98628) BLINDS: Already up!
D (109848) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, event_id=6
I (109858) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=CLOSE
HANDLE MSG: control:command : CLOSE
D (109868) LED: queue rcv stack: 1672
I (109868) LED: led 0 : 30 0 30 (100 ms)
W (109868) BLINDS: queue - Stack: 1528
I (109878) BLINDS: Move (direction Down, revs 0.00, force_small_steps-flag 0, override_limits: 0
I (109888) blinds_task_move: Move: Down - 0.00 revs, target -1.00, force_small_steps 0, force_mov 0
I (109908) blinds_task_move: Starting continuous movement
I (109908) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/status : Moving
I (109918) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/direction : Down
I (109918) NODE-FRAMEWORK: Publish: /home/cover/fyrtur-esp32-7baf1c/target_position : 0
W (109938) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (110458) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (199218) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (199738) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (200258) BLINDS: blinds_task_read_status_reg - Stack: 1400
D (200288) mqtt_manager: Event dispatched from event loop base=MQTT_EVENTS, even                  t_id=6
I (200288) NODE-FRAMEWORK: MQTT_EVENT_DATA
TOPIC=/home/control/fyrtur-esp32-7baf1c/command
DATA=STOP
HANDLE MSG: control:command : STOP
D (200308) LED: queue rcv stack: 1672
I (200308) LED: led 0 : 30 0 30 (100 ms)
W (200308) BLINDS: queue - Stack: 1400
I (200318) BLINDS: Stop
W (200778) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (201298) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (201818) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (202338) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (202858) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (203378) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (203898) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (204418) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (204938) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (205458) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (205978) BLINDS: blinds_task_read_status_reg - Stack: 1400
W (206498) BLINDS: blinds_task_read_status_reg - Stack: 1400
the motor not doing anything

W (48748) BLINDS: queue - Stack: 2216
E (48758) BLINDS: Setting minimum voltage not supported on original firmware!

W (48748) BLINDS: queue - Stack: 2216
E (48758) BLINDS: Setting minimum voltage not supported on original firmware!

okay connection between motor and esp its ok
RX      PIN 5
TX       PIN 23
LED     PIN 18
BUTTON UP PIN 21
BUTTON DOWN 22

okay connection between motor and esp its ok
RX      PIN 5
TX       PIN 23
LED     PIN 18
BUTTON UP PIN 21
BUTTON DOWN 22

now it works the motor tries to move but it end in error
i use the 5V USB from charger

now it works the motor tries to move but it end in error
i use the 5V USB from charger

with the batterie it works
5V its too low

with the batterie it works
5V its too low

where can i find the connection between esp and ikea pcb ?

Same question here. Did I miss something?

RX PIN 5
TX PIN 23
LED PIN 18
BUTTON UP PIN 21
BUTTON DOWN 22

Thanks, I thought you mean the connection between custom PCB and motor in your previous post. Now its clear :)


Running loop using random match numer in Boundary Extractor will result to same values

Expected behavior
when defining a random match number in Boundary Extractor each iteration should random a new value
Actual behavior
when running the script in loops (1 user at a time) the value is always the same
Steps to reproduce the problem

use in scripte a Boundary Extractor with random match number in at least one of the responses

run the script with threads (a few users simultaneously) - the random works fine

run the script with loops (1 user at a time) - the value is only being randomed once and all requests are always using same value

JMeter Version
5.4.1
Java Version
No response
OS Version
No response

Would you please share a test plan that reproduces the issue?


Repeat or unnecessary requests for related artists from artist pages`

Loading a single artist page (like /artist/lynn-chadwick) triggers 5 separate API requests for related artists. E.g.:
/api/v1/related/layer/main/artists?artist%5B%5D=lynn-chadwick&exclude_artists_without_artworks=true&size=0&total_count=1
/api/v1/related/layer/contemporary/artists?artist%5B%5D=lynn-chadwick&exclude_artists_without_artworks=true&size=0&total_count=1
/api/v1/related/layer/main/artists?artist=lynn-chadwick&size=0&total_count=1
/api/v1/related/layer/main/artists?artist%5B%5D=lynn-chadwick&exclude_artists_without_artworks=true&size=1
/api/v1/related/layer/main/artists?artist%5B%5D=lynn-chadwick&exclude_artists_without_artworks=true&size=15

Some of these are slightly different, but 3 (#1, 4, and 5) are identical except for size and total_count parameters, so could presumably be satisfied by a single request.
I'm not sure where these originate but the repetition causes significant API load and seems unnecessary.

Looking at the page again, there doesn't seem to be any related artists data actually presented. Maybe these could all just go away?

I was able to identify consistently three places where these requests are happening on the overview page:

To generate a list of artist statuses to determine which tabs to show on the artist page
To pull a similar artist to use in the CTA that asks you to create an account

This was happening on every pageload (even if logged in already): https://github.com/artsy/force/pull/2260

To determine whether or not to populate (and how to style) a rail of related artists that appears at the bottom of the page (once you scroll through all of the artworks)

We actually do need the count here. Currently, the count of related artists comes through metaphysics so there's not an easy way to just swap in the x-total-count header here, so I'm not sure if it's worth digging in further.


Support Different EPSG Specifications for WMSTile url builder

Does any other open PR do the same thing?

No
What issue is this PR fixing?
Adds support for WMSTile url builder to support different EPSG spec. Currently support EPSG4326 and EPSG900913.
currently android uses epsgbox library. ios cocoapod build uses EPSGBox. non cocoapod build uses bundled source. There is an api available for consumers to add additional spec implementation if required.
How did you test this PR?

WMSTile example in the AirMap explorer app

Hi @netmaxt3r when you merge this task to master?

a


Add the requirements-autoupdate workflow, add type hints and fix crash when no client secrets file is provided

EDIT: I programmed further in my fork and thought I could open a new pull request, but apperently I cannot (or I am too dumb to find the option). This pull request should be split into three, but I dont know how.
As described in #9, here is the workflow.
Changes made since suggestion:

Added workflow_dispatch trigger to allow manual run

We might also want to add an autoupdater to the lock-file using poetry lock

Or does that kinda defeat the whole purpose of a lockfile?

I am also thinking about letting ruff or so run to autoformat the code...

Alright @HomerusJa we'll figure it out! Is the '.idea' directory necessary for the app to run remotely or is it for your local machine's IDE?

The .idea folder contains Jetbrains configuration files. If you want, we can just throw it out. I'd rather opt of a more gentle solution using the updated .gitignore as like that, the IDE settings are kept, but this is your project. Do as you wish!

@HomerusJa I am not sorry to say but this is no longer "my" project 😆. We could add it to the .gitignore. That should work!

Also, I just remembered I also added methods to download subtitles as in #11
It is not fully integrated in the UI nor is it tested.

Great! In that case, I'll assign the task to you. If you require assistance on that particular task #11. Feel free to leave a comment or create another issue. For now I'll leave the 'help wanted' tag on whilst it's assigned to you.


Use proc instead of lambda to fix S#sync regression

Fixes regression introduced in cd1a68e1a8329d8449c75f436f2d21b49a61fb18

Just out of curiosity, what is the difference between proc and lambda? I nearly always use lambda, is there a case where you should pick one over the other?

http://stackoverflow.com/questions/626/when-to-use-lambda-when-to-use-proc-new
In this particular case the difference is basically that return will only return from the lambda, executing the rest of #sync, whereas the proc-variant will return from the whole method.

woah, interesting!
Thanks, I can now go forth and confuse n00bs with that knowledge :D

:)


Add getFactors() implementation for SequenceRandom

It's really the only necessary sequence that doesn't yet have factorizations, even once #153 is merged. Implementing this will require refactoring the factorizer from SequenceFormula into its own shared module and using it in both SequenceRandom and SequenceFormula. While that is happening, the implementation should also be improved to cache the factorizations of numbers it sees.

I suppose it could also dynamically add new primes it finds as it is working to its list of primes. But knowing when it can increase the limit on numbers it is certain to factor is a whole different ball of wax, so I doubt it's worth trying to do that.


It seems like predicted price is off 1 day on IBM or maybe i missunderstood something

Hi,
I was very impressed with the result of prediction graph of IBM but than i noticed that actual prediction is going after next day of actual data, so i decide to print out some piece of data with this :
print("Actual/Predicted prices:") for i in range(len(data_close_price)):     print(str(data_close_price[i]) + '\t ' + str(to_plot_data_y_train_pred[i]) + '\t' + str(to_plot_data_y_val_pred[i]))
and here is a piece of output ( i grabbed a piece where the stock went up to make it clear):
data_close_price         to_plot_data_y_train_pred       to_plot_data_y_val_pred
61.5541637158	 62.48051591375582	None
63.1859297539	 61.81105258680695	None
65.5087283847	 63.22269362984531	None
65.2532205353	 65.42579108472087	None
70.2646585813	 65.24432286147622	None
69.5387840091	 70.2044966634442	None
lets check 2nd row, date_close_price showing 63.1859 while prediction price is 61.8110
and then on next day data_close_price 65.508 and prediction 63.222 ,
so it seems that prediction price is one day behind ???
Please advice, maybe i dont understand it

to be clear, to me it looks like  next day prediction price is very close to previous day actual price

Same problem. I don't get it.

I am just leaving a comment here to catch your solution. I am also working on this problem right now.

how did you go with this? I am looking at the same problem.

Ok, my idea is that the machine is cheating. It gives you back a value very close to the previous day, since it should be the closest one to the real value without doing prediction.
I used different networks and the result was usually the same. Doublechecked every variable, label, etc. That wasnt the problem.

Perhaps a little late, but...
Making price predictions based on past prices is a poorly feasible task (I think generally impossible). The first thing that stands out is that the predictions are perfect (but "shifted"). The data link is not good enough for the model to make such good predictions.
If you want at least some predictions based on previous courses, you can try the step not for a day, but for a week or a month. In such a case, a stable market can have a normal result (when was the market last stable?).
If you still want to analyse (whether for a day or for a week does not matter), then add at least a hundred economic parameters to the model. The problem with learning is not writing code (with libraries like Python or TensorFlow it is not very difficult), but preparing the data. alphavintage offers a handy API, but you need data, for example from any statistical office. Analyze other "crypto parameters" besides prices. For example, Network Value to Transactions, Hash Rate, Realized Market Cap, Fear and Greed Index. Be sure to watch all reports and the US economy (there are economic calendars, although APIs are paid for historical data almost everywhere), a little China, Japan and the EU. But sometimes you can see that can also affect the decision on the rate in Canada, and sometimes not.
In general, machine learning is not a panacea. If you have several trillion parameters, then maybe it will. Right now you can add a hundred parameters and see if there is a prediction (it does not matter if it is inaccurate). I have not tried it, but you can use fingpt, for example, to analyze non-numeric data. Then give it your predicted numbers and listen to the advice for the next day.

@egorpes You can also simplify (current - previous) / previous to current / previous - 1.0

Hi, I would like to know if someone can objectively and comprehensively explain the main reasons why the model returns the last value of the input sequence, and not the next "predicted" one.  I see the following: during training, the model tries to converge to the predicted values and this is clearly visible, but when moving to validation, everything changes dramatically.  For myself, I explain this by the backward method and the overall approach to the network, which gives the network the ability to cheat.  It’s as if it’s worth considering the problem from the other side or a completely different learning method, for example, a classification task - to determine not a specific value, but a movement trend through q-learning.  I’m very interested to see if anyone has any progress in this regard.  I would also like to express my disagreement with the post above that this problem cannot be solved at all within the framework of machine learning.  From my point of view, there is no need to predict a 100% match with the price; it is enough to be right in 50%+ cases.  The news is perfectly reflected on the charts themselves in the form of signals, which allows you to stay within the technical limits.  analysis.  A good example is a human trader: he tries to recognize some patterns, patterns and predict the next trend, of course he does not do it perfectly, but the fact is that there are successful cases and they are not based on luck.  The essence of using machine learning here is to minimize human errors as much as possible and make trading more or less stable in terms of forecasts.  Of course, the task is quite difficult from the point of view of understanding and I think that relying on one neural network to solve it is somewhat stupid; perhaps it is worth backing it all up with a complex of interconnected networks and algorithms.  Thank you for reading

From the perspective of the neural network:
Since the prediction of the next timepoint can be either lower, or higher than the present value, betting in either direction would give back larger loss value. The emphasis is on betting, because it sees no indicator that could be used to predict the change of price.
You can also translate this from another perspective. The model sees no value that indicates change in either direction. This means, value of the next price is dependent largely on the current price, and an external factor that is not included on the training dataset. So current price is the only one that can be used.
I am not great on explaining it, but trust me timescale analysis is not suitable for trading. It can be used to predict for example room temperature, if you know how long you turn on the heater. But in that case, you know the external factor that changes the room temperature.
I recommend classificatiom and reinforcement learning for price prediction. I've done this for a long time, i tried almost everything that can be tried. Nothing helps.


Store the Shipper deployment object in our repository

Currently, Shipper's deployment object is a release artefact that we're keeping in Github.

We should bring it into our repository, so that it's easy to modify, and takes no extra toil
We should update the documentation to point to this new URL

The first item is done in pull request #60, so we should wait for that to be merged first. Once that's done, we can clean it up and update it, then update the documentation to point to it.

We now have a deployment object that we use in our CI pipeline after #86 got merged, so now we just need to point our documentation to it.

Fixed by #182


MolangVariableMap Class Documentation need an example

Documentation don't tell you how the Molang variable build for particles, In fact particles that spawned can't read the Molang variable you given.

Hello!
It looks like we've made some progress on this. Since it's been a while, I'm going to close this issue, but if you have any additional feedback, please reach out to us!
Thanks!


Please add Virgin Media "Four" to the Ireland EPG

Source
https://www.virginmediatelevision.ie/tv-guide
Channels
-Four (aka "Virgin Media Four")
Notes
No response

I have added this channel to the file but i have no experience with Github so have no idea how to create the pull request described in the contribution guide. Have attached the database zip here in case that helps?
database-master.zip

@PopeyeTheSai10r is this channel available to grab using the epg-grabber package or is that not possible? I couldn't find it listed anywhere in the /sites folder. Apologies I know this is slightly unrelated to this specific issue.

Hey @niallobr, The station was added to the Database. We don't have a working source yet so can't be grabbed yet.
The other possible solutions is creating a config file for https://www.virginmediatelevision.ie/tv-guide or https://www.virginmediatv.ie/en/epg. As those are the only source I was able to find that have the station and it's information.

Ok great, thanks for explaining @PopeyeTheSai10r !

The guide for Virgin Media Four is now available at:
https://iptv-org.github.io/epg/guides/en/virginmediatelevision.ie.xml


The driver received an unexpected pre-login response.

Description
This isn't so much a dbeaver issue, but curious if anyone has encountered it. My platform team can't figure it out (not a huge surprise). I'm connecting to a sql server and getting this error. I'm the only one who can't connect, but also the only person on a mac.
The TCP/IP connection to the host server.database.windows.net, port 1433 has failed. Error: "The driver received an unexpected pre-login response. Verify the connection properties and check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. This driver can be used only with SQL Server 2005 or later.". ClientConnectionId:2acb2450-5e18-4e9b-b791-1b1b186519b2
The TCP/IP connection to the host sql-shared-general-dev-eus2-01.database.windows.net, port 1433 has failed. Error: "The driver received an unexpected pre-login response. Verify the connection properties and check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. This driver can be used only with SQL Server 2005 or later.". ClientConnectionId:2acb2450-5e18-4e9b-b791-1b1b186519b2
DBeaver Version
Version <IP_ADDRESS>403110838
Operating System
Apple M3 Pro Version 14.6.1 (23G93)
Database and driver
jdbc driver
Azure sql server
Steps to reproduce
No response
Additional context
No response

I'm seeing the same error attempting to connect to a DB running in a Docker container, which was working immediately before updating

@mrhargro Can you check if your IP is in the list of the accepted IPs on your server? That looks like your address is not allowed to connect to that server.


Add standard scoop maintenance tools and tests

This will allow me to add this bucket to the Excavator Service

Thanks! :smiley:
PS: I added you as a collaborator to this repository so that it can stay maintained in case I become unavailable for any reason.


Add configurable list of users to NOT revoke login

Sometimes when running "revoke-logins", some users needs to be excluded. From this.
It would be nice if this were baked into pgbelt somehow, an ignore list of users when revoking logins.

We should fix up the revoke-logins code.
It seems we have a global list of users to NOT revoke, which is fine.
It seems it uses the other_users key as a list of ALL other users in the database other than root, schema owner and pglogical, unless you specify what users are to be in that list.
The code then forces the owner to for sure be revoked, and then every other other in other_users as long as it is not globally excluded.
This is very confusing.

The revoke-logins code should instead do the following:

Obtain all users with login, and the revoke logins from all of them except ones in the global exclude list.

There should be a key in the config to exclude more users from getting their logins revoked.


Drag-n-Drop support

Would love to see the ability to drag and drop timelines, events, clips or titles directly into a folder instead of copy-pasting them. Support for fcpxml to quickly share assets would be a welcome addition

This is a great idea! Will investigate.

This will be added in the next build.


The first step from the section 'Option B: Resource-based Kerberos constrained delegation' is not correct.

Hi,
The first step in the section 'Option B: Resource-based Kerberos constrained delegation' indicates:
1. Use the Active Directory Users and Computers MMC snap-in on the domain controller for the ContosoFrontEnd domain and verify no delegation settings are applied for the gateway service account

Based on my experience performing some tests with the gateway and the target service in different domains, this statement is wrong.

As I understand (and the only way that I could make this scenario work), the gateway service account must be configured with Standard Kerberos constrained delegation  before configuring Resource-based constrained delegation  into the target service account.

Instead of selecting the Do not trust this user for delegation  option, which is the order of this step.

Also, the screenshot should be updated too.

Please, correct me if some of the statements are not right.
Regards,
Carlos

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

ID: e8d4509b-ab31-a917-16a2-8ed7ce834c41
Version Independent ID: 31f21190-cd0d-f369-fc4a-48ca7ac1ccb0
Content: Configure Kerberos-based SSO from Power BI service to on-premises data sources - Power BI
Content Source: powerbi-docs/connect-data/service-gateway-sso-kerberos.md
Service: powerbi
Sub-service: powerbi-gateways
GitHub Login: @paulinbar
Microsoft Alias: painbar

Thanks for your comment, @omeuid. This issue has been assigned to the doc author for review.

Hi Carlos, given this statement:
As I understand (and the only way that I could make this scenario work), the gateway service account must be configured with Standard Kerberos constrained delegation  before configuring Resource-based constrained delegation  into the target service account.
Likely the gateway is not doing Resource-based constrained delegation but Standard constrained Kerberos delegation. We have had customers in the past successfully use Resource-based constrained delegation using the steps in the documentation.
Unfortunately, setting up gateway sso in a multiple domain scenario is complicated given the variety of possible Active Directory deployments. Therefore, if you are having difficulties, I recommend you reach out to PBI support to troubleshoot your specific issues.

Hi @ms-kgorgi,
Some details regarding your comment:

Likely the gateway is not doing Resource-based constrained delegation but Standard constrained Kerberos delegation. We have had customers in the past successfully use Resource-based constrained delegation using the steps in the documentation.

First, My testing environment was built using two domains created with two Active Directory 2019 (with its default functional level).
As I understand Standard constrained delegation cannot be done between accounts of different domains. So, could you explain why you think that?
Also, If Resource-base constrained delegation can be configured using those steps, could you provide some details about an environment where those steps could be followed without any issue?

Unfortunately, setting up gateway sso in a multiple domain scenario is complicated given the variety of possible Active Directory deployments. Therefore, if you are having difficulties, I recommend you reach out to PBI support to troubleshoot your specific issues.

Sorry if my explanation was not clear enough, I was able to configure PowerBI gateway correctly but not following your documentation, which seems to be wrong (at least for my scenario with two Windows Server 2019 domains).
Regards,
Carlos

Hi @omeuid,
Standard delegation can be used depending on the trust relationship of the domains. One quick way to test is remove the Resource-based settings and checking if your scenario still works. If it still works, then you are using Standard delegation.
Regards,
Kian


feature(custom-jhlite): setup custom npm and maven version reader to handle custom npm/java dependencies

Fixes #10850 and fixes #10851

FYI I've updated https://github.com/jhipster/jhipster-lite-extension/pull/85 that shows the purpose of this PR.
The first commit (https://github.com/jhipster/jhipster-lite-extension/pull/85/commits/f0653240da81d8b7324f55ce2a5aeb51664a9233) corresponds to the application of the changes of the custom-jhlite module made in this PR.

Thanks for the reviews @renanfranca, it's really appreciated! 👍

Thanks for the reviews @renanfranca, it's really appreciated! 👍

You're welcome 😊

@murdos : approved


311 memories :: 311 memories' 4/7/16 & 4/11/16 imports are not appearing on the JDA website.

311 memories' 4/7/16 & 4/11/16 imports are not appearing on the JDA website.
The re-index probably solves the problem.

This is an update for the 311 memories' items.
15,684 items are not appearing on the JDA site.  April 7,11,14,18, 21, 25, 28 and May 2, 5, 9,12 &16 imports are not appearing.

How can you tell these are missing?
I'm re-indexing now, i'll check after I'm done.

Admin page user id 426 and the jda headline category numbers should match.
As of 5/17/16, the user id 426 total item number and the headline search number do not match.

thanks! And how did you know the individual missing dates?

Ok, the re-index looks like it's recovered all but 1 item

Great!
I think, the1 item is the user collection which is not published.
Thank you very much!


package compile order

When I build mpv with this script, It's have a very strange behavior, sometime can build sucess, sometime failed, after some digging, I found maybe some package building depending on other package, but at this time the other package still building or downloading, and so the error happenning.
but sometime the being depended package building finnish first, it's can go through and build success.
Like for building libdvdread, it rely on libdvdcss, but often happen, libdvdread being building before libdvdcss finish it job. it's make libdvdread failed.
sorry for my pool english.
thanks.

That shouldn’t happen. What’s your operating system and CMake version?

ubuntu 14.01(64bit) + cmake version <IP_ADDRESS>

Try updating to CMake 3.3.

update to cmake upgrade to 3.3.2,  but the problem still exist.
at this time at lease two package had failed at configure stage.
lame-configure-err.log:
    /home/lachs0r.git/build-64/packages/lame-prefix/src/lame/configure: line 16126: syntax error near unexpected token `SNDFILE,'
    /home/lachs0r.git/build-64/packages/lame-prefix/src/lame/configure: line 16126: `  PKG_CHECK_MODULES(SNDFILE, sndfile >= 1.0.2, HAVE_SNDFILE="yes", HAVE_SNDFILE="no")'

libdvdread-configure-error.log:
    /home/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread/configure: line 12769: syntax error near unexpected token `CSS,'
    /home/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread/configure: line 12769: `  PKG_CHECK_MODULES(CSS, $CSS_REQUIRES)'

this is only build only the libdvdread
~/lachs0r.git/build-64$ ninja libdvdread
[2/18] Performing force-update step for 'libdvdcss'
-- libdvdcss force-update command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdcss-prefix/src/libdvdcss-stamp/libdvdcss-force-update-*.log

[4/17] Performing force-update step for 'libdvdread'
-- libdvdread force-update command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-stamp/libdvdread-force-update-*.log

[4/14] Performing autoreconf step for 'libdvdcss'
-- libdvdcss autoreconf command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdcss-prefix/src/libdvdcss-stamp/libdvdcss-autoreconf-*.log

[5/14] Performing configure step for 'libdvdcss'
-- libdvdcss configure command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdcss-prefix/src/libdvdcss-stamp/libdvdcss-configure-*.log

[6/14] Performing build step for 'libdvdcss'
-- libdvdcss build command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdcss-prefix/src/libdvdcss-stamp/libdvdcss-build-*.log

[8/14] Performing install step for 'libdvdcss'
-- libdvdcss install command succeeded.  See also /home/phantom/lachs0r.git/build-64/packages/libdvdcss-prefix/src/libdvdcss-stamp/libdvdcss-install-*.log

[10/14] Performing configure step for 'libdvdread'
FAILED: cd /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-build && /usr/bin/cmake -P /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-stamp/libdvdread-configure.cmake && /usr/bin/cmake -E touch /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-stamp/libdvdread-configure
CMake Error at /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-stamp/libdvdread-configure.cmake:16 (message):
  Command failed: 2

   '/home/phantom/lachs0r.git/build-64/exec' '/home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread/configure' '--host=x86_64-w64-mingw32' '--prefix=/home/phantom/lachs0r.git/build-64/prefix/mingw' '--disable-shared' '--with-libdvdcss'

  See also

    /home/phantom/lachs0r.git/build-64/packages/libdvdread-prefix/src/libdvdread-stamp/libdvdread-configure-*.log

ninja: build stopped: subcommand failed.

Well, I cannot reproduce this at all. I’m just going to blame Ubuntu LTS
because it’s the Windows XP of Linux distributions.
Most of its packages were outdated two years ago and it’s just not worth
trying to support such old and broken crap with this toolchain.
Try using the VM image.

very strange, sometime build would sucess, but after I make some code modify of mpv, and build again,
this issue happen, but the building stage far away to mpv.

That’s because by default, it updates and rebuilds packages that are pulled
from version control sources (Git, SVN).

I have try "-DENABLE_VCS_UPDATES=false" as you mention in README, building step would skip git download, but would still run patch command, and make some error, so I give up use "-DENABLE_VCS_UPDATES=false" option.

Did you try this on a clean build directory?

ok, I'll try again later

'libvpx' should depend on 'gcc', not 'winpthreads'

That’s fixed now.


Integrate WMMA

Integrate WMMA changes into main.

@sdrabenh - I've created PRs in GMAO_Shared, GEOSgcm_GridComp, GEOS_OceanGridComp and GEOSgcm_App. The WMMA (WAVEWATCH, UMWM, sea spray) changes in these fixtures are in branches named 'feature/adarmenov/integrate-wmma'.

The PRs are:

[ ] https://github.com/GEOS-ESM/GMAO_Shared/pull/339
[ ] https://github.com/GEOS-ESM/GEOSgcm_App/pull/552
[ ] https://github.com/GEOS-ESM/GEOS_OceanGridComp/pull/59
[ ] https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/872
[ ] https://github.com/GEOS-ESM/GEOSgcm/pull/724

The first GNU CI failure is due to using an Intel compiler flag with GNU. I'm going to try and fix this up.
I might also propose some changes to some of the CMake. What's there works, but it's not quite the style we currently use in GEOS CMake.
I assume @sanAkel is looking at the coupled run failure.

...
I assume @sanAkel is looking at the coupled run failure.

The reason for the coupled run failure is that only datasea has the 'DW' export. If ocean depth is not an export that would be required in the foreseeable future by GCs other than WGCM, then IMO it will be easier if this variable is handled by WGCM. Thoughts @sanAkel?

Okay. I have two new PRs in GEOSgcm_GridComp and WW3:

https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/876
https://github.com/GEOS-ESM/WW3/pull/3

with the changes I needed for GNU builds. I'll try and retrigger the CI here to see if it gets further.
In my testing, these are zero-diff for an AMIP Intel run where waves aren't used.

I'll try and retrigger the CI here to see if it gets further.

Sigh.  The CI won't work until these are in the anton branches. Friday brain.


_nodes_by_depth attribute error when inheriting from Sequential model

I got exactly the same error as the one described in  #7096
Should I avoid inheriting keras.models.Sequential?
Versions I am using:

Keras : 2.1.6
tensorflow-gpu: 1.8.0

I got the same error with Keras 2.2 and tf-gpu 1.11, please see code below to reproduce:
``from keras.models import Sequential
from keras.layers import Dense
from keras.optimizers import SGD
import numpy as np
class SequentialChild(Sequential):
def init(self):
self._output_tensor_cache = [] # This list was not initialized as empty and also caused a bug.
super(SequentialChild, self).init()
model = SequentialChild()
model.add(Dense(10))
model.compile(optimizer=SGD())
model.predict(np.random.normal(0, 1, size=(64, 10)))``

I got same error ...


TA Meeting - 2024-10-21

Purpose of Meeting
Hazard Analysis informal presentation
Date and Time
Oct 21/24, 4:00pm
Attendance

[x] Emily Perica
[x] Ian Algenio
[x] Jackson Lippert
[x] Mark Kogan

Questions to Ask
Potential questions for TA:

Should we include stretch goals as design functions? Consider their hazards?
Are the hazards of inflicted medical conditions (heart attack, etc.) something that should be considered?
Redundancy of failure modes?
Focus on hazards that can be produced by outside systems (interfacing systems like the users laptop)?
Deadline extension?

More = better
Too much content (stretch goals)  don’t worry about it, can always add something in later for Rev 1
Length for table (functions)  Follow example, makes sense according to the rubric, no minimum since especially for us there isn’t really any safety risks

Could make up hazards  for users there’s user data (we aren’t implementing user account but this COULD be a hazard)
Make sure our model doesn’t get influenced by other things, model in database, database encrypted
Not an issue if we don’t have a lot of things
o	Blurb: Due to design of our project, we don’t have many hazards, include justification for any hazards we do have
External systems for hazards?
o	Valid if were doing things that
o	Won’t mitigate these risks
o	‘These COULD happen’ (in critical assumptions)
	Include a lot of assumptions that say physical hazards aren’t going to be mitigated by us
	Or we include these as a hazard and say our way of mitigating it is a safety disclaimer/warning (might be worthwhile to include these in our hazards)
	Ex. strings breaking, we wont have a warning for this so this would go in assumptions
o	Focus on user satisfaction ‘risks’
	Ex. someone is performing/inputing music and app crashes, how do we deal with that.
Redundancy  try to not be redundant, be as clear and concise as possible do this by linking back to SRS, requirements
o	The file example is NOT considered redundant, since this adds to the quality of our table
Peer reviews:
o	Only marking if we add issues to our assigned teams repo, dont have to implement other team's issues into ours if we dont want to


(MAINT) Make cli .erb files more robust

Make the cli .erb files more robust by adding quotes around the
JAVA_BIN and CONFIG environment variables.
This implements the changes suggested by @jeffmccune in https://github.com/puppetlabs/pe-puppet-server-extensions/pull/162. I thought this belonged in stable since it's a minor change and since it's going into 3.7.2, it might as well go into 1.0.1 as well.

:+1:

:+1:


Aurora/Aurora-Updater crashes when putting computer to sleep.

Expected Behaviour
Not crashing
Actual Behaviour
Putting Windows 11 Pro to sleep, resume from sleep and see that the aurora process died.  Multiple event logs show the following (pasted in order from earliest to latest)
Event 1026, .NET Runtime - 11:53:14 PM EST
Application: Aurora-Updater.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Aurora.Settings.Configuration..ctor()
at Aurora_Updater.UpdateManager.LoadSettings()
at Aurora_Updater.UpdateManager..ctor(SemVer.Version, System.String, System.String)
at Aurora_Updater.Program.Main(System.String[])
Event 1000, Application Error - 11:53:14 PM EST
Faulting application name: Aurora-Updater.exe, version: <IP_ADDRESS>, time stamp: 0x9462715c
Faulting module name: KERNELBASE.dll, version: 10.0.22000.918, time stamp: 0xb42fa627
Exception code: 0xe0434352
Fault offset: 0x000000000004474c
Faulting process id: 0x64b0
Faulting application start time: 0x01d8c011dbdc8946
Faulting application path: C:\Program Files\Aurora\Aurora-Updater.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 0af233b3-757d-43b4-ae5c-23eeeb130467
Faulting package full name:
Faulting package-relative application ID:
Event 1026, .NET Runtime - 11:58:41 PM EST
Application: Aurora.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at LightFXAPI.LightFXSDK.LFX_Reset()
at Aurora.Devices.LightFX.LightFxDevice.UpdateDevice(System.Collections.Generic.Dictionary`2<Aurora.Devices.DeviceKeys,System.Drawing.Color>, System.ComponentModel.DoWorkEventArgs, Boolean)
at Aurora.Devices.LightFX.LightFxDevice.UpdateDevice(Aurora.Devices.DeviceColorComposition, System.ComponentModel.DoWorkEventArgs, Boolean)
at Aurora.Devices.DeviceContainer.WorkerOnDoWork(System.ComponentModel.DoWorkEventArgs)
at Amib.Threading.Internal.WorkItemsGroupBase+<>c__DisplayClass40_0.b__0(System.Object)
at Amib.Threading.Internal.WorkItem.ExecuteWorkItem()
at Amib.Threading.Internal.WorkItem.Execute()
at Amib.Threading.SmartThreadPool.ExecuteWorkItem(Amib.Threading.Internal.WorkItem)
at Amib.Threading.SmartThreadPool.ProcessQueuedItems()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Event 1000, Application Error - 11:58:41 PM EST
Faulting application name: Aurora.exe, version: <IP_ADDRESS>, time stamp: 0xb3b1d5f6
Faulting module name: LightFX.dll, version: <IP_ADDRESS>, time stamp: 0x62e20cf5
Exception code: 0xc0000005
Fault offset: 0x0000000000001244
Faulting process id: 0x782c
Faulting application start time: 0x01d8c011db6302e4
Faulting application path: C:\Program Files\Aurora\Aurora.exe
Faulting module path: C:\WINDOWS\SYSTEM32\LightFX.dll
Report Id: 884868e6-d2ec-4ddc-802f-0196a3cef61f
Faulting package full name:
Faulting package-relative application ID:
Reproduction steps
Put Windows 11 Pro to sleep
Frequency
Every time
Aurora Version:
v65 Aurora-RGB/Aurora
Previously an Issue?
Don't know
Logs attached from event time:
2022-09-03 23.53.13.log

Seems like a problem with LightFX controller in Aurora. Probably needs disabling/restarting with account lock. If you're not using LightFX devices you should disable it

You are 100% correct.. Disabling LightFX controller (and all other things not Razer) made it not crash anymore


init() missing 1 required positional argument: 'param'

Thanks for this great example. Unfortunately I'm having trouble getting this to work.
In Step: "Let's run our completion task with our LLM" i get the error:
init() missing 1 required positional argument: 'param'
Do you have any idea how to fix it?

@ezhilvendhan thank you for your quick response.
I think it has to do with the setting for OpenAI. Can you check in my screenshot below, if the values were entered correctly in the "config.env" file? I previously registered AzureOpenAI and deployed a model "GPT-35-turbo". Are there any additional steps required within AzureOpenAI?

Looks like OPENAI_API_VERSION is missing in your env file. You can you provide it from the Model deployments page in Azure console


Add telemetry controllers

Codecov Report

Merging #30 (3f0adc3) into main (3ff9de2) will decrease coverage by 1.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
- Coverage   98.61%   97.43%   -1.18%
==========================================
  Files          11        2       -9
  Lines          72       39      -33
  Branches        3        1       -2
==========================================
- Hits           71       38      -33
  Misses          1        1

Impacted Files
Coverage Δ

...tics-extension/src/services/fake_telemetry.data.ts
100.00% <ø> (ø)

diagnostics-extension/src/services/telemetry.ts
96.55% <ø> (ø)

diagnostics-app/src/app/core/enums/global.enums.ts

diagnostics-app/src/app/shared/material.module.ts

...nostics-app/src/app/core/services/theme.service.ts

diagnostics-app/src/app/shared/shared.module.ts

diagnostics-app/src/test.ts

diagnostics-app/src/app/app.component.ts

...tics-app/src/app/layout/header/header.component.ts

.../layout/content-layout/content-layout.component.ts

Continue to review full report at Codecov.

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


Add license?

Thanks for adding this library to the Node.js ecosystem, I was wondering if you could add a license so that people can whose GitHub is associated with their employer can still submit patches? Thanks!

The license was in the README. Moved to a LICENSE file.


[Core] Fix more C99 compliance issues

This fixes almost all the C99 compliance issues in the implementation of Clay.
Now the only issues remaining are:

##__VA_ARGS__, which isn't easy to solve without switching to C23.
Defining a struct within offsetof to get the alignment of a type, which also isn't easy to solve without switching to C11.
A number of times that signed integers are compared with unsigned integers, which will need some rethinking of all the types for lengths and indices etc.
Some strangeness with the CLAY_SIZING_FIT and CLAY_SIZING_GROW macros, which don't compile without specifying -std=gnu99 rather than -std=c99 for some reason.

Would you mind also fixing MSVC C99 compliance issues in your PR ?
ATM it forces the rust bindings to use a .cpp file for compilation of clay under windows.
The main issue is https://github.com/nicbarker/clay/blob/main/clay.h#L124, a potential fix was provided by emoon:
#ifdef _MSC_VER
    #define CLAY_PACKED_ENUM __pragma(pack(push, 1)) enum __pragma(pack(pop))
#else
    #define CLAY_PACKED_ENUM enum __attribute__((__packed__))
#endif

I really can't figure out why the GCC test is failing :-(. I can reproduce it, but I can't figure out which of the changes in this PR are causing it.

I've figured out what the issue is, but unfortunately it's not easy to fix... I'll have a think and come back on this soon.

Would you mind expanding on what the issue is ?
Also is it for a specific reason you keep some CLAY_INIT calls, and remove others ?

Would you mind expanding on what the issue is ? Also is it for a specific reason you keep some CLAY_INIT calls, and remove others ?

It's to do with the fact that we're now initialising the structs with {0} rather than {}, as {} is only added in C23. However, it does mean that the 0 could be initialising a field in a subobject rather than directly in the struct. GCC wants us to add braces around the 0 in that case to make it clear to the programmer that it's initialising a subobject, but that is difficult to do if you want to do it generically for all structs.
My general idea with removing the CLAY__INIT calls is to reduce the number of casts as much as possible. When initialising a struct, it's unnecessary to cast the braces to the right type, as it's already given in the variable declaration. Adding these casts mostly just adds possibilities for type errors to occur, because casts often implicitly tell compilers to not warn about type errors. The only CLAY__INIT calls I've left in are those that are necessary, like when you're creating a struct in the arguments to a function.

Confirming for posterity that we're going to move forward assuming a compiler that has support for ##__VA_ARGS__ 🙂

A number of times that signed integers are compared with unsigned integers, which will need some rethinking of all the types for lengths and indices etc.

We will tackle this in a separate PR so we can get this over the line!


Adding eye button in password field in Signup/login Page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Will add a eye button in the password field for toggling visibility.
Additional context

Assigned @pani2004


Stop sending device-mapper metrics

Filesystem usage metrics on device-mapper virtual devices are not useful.
Docker creates many device-mapper device nodes.

Coverage decreased (-0.07%) when pulling b1c8e9b1ee4ac3d0f7385ff75a21125d0ec6e291 on device_mapper into 89fd930c84f30b2822b72ef7079e49b855be2473 on master.

LTGM!

thx!


[20.03] openjpeg: patch CVE-2020-6851 and CVE-2020-8112

Backport of #82426. Should I do one for 19.09 as well?
Motivation for this change

#77939, https://nvd.nist.gov/vuln/detail/CVE-2020-6851, https://github.com/uclouvain/openjpeg/issues/1228
#79726, https://nvd.nist.gov/vuln/detail/CVE-2020-8112, https://github.com/uclouvain/openjpeg/issues/1231

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Should I do one for 19.09 as well?

Yes, please.


Add QEDprocess functionality

This adds the functionality from QEDprocesses again which was temporarily removed from #6 / #23 to have a working state.
Must be merged after QEDbase is released with the new interfaces from QEDprocesses.

This should be ready to merge and successfully test once https://github.com/QEDjl-project/QEDbase.jl/pull/68 is merged

@AntonReinhard please update QEDbase and push again.


Bumping version to try 1.12.x

test this please

test this please

test this please

test this please

test this please

test this please

test this please

/lgtm
/approve


Loader moved below heading in example page

Moved Loader below Heading "Some Examples Of sButtons" in Example Page

Issue: Move Loader in Examples Page below heading #1257

Great work thank you!
@all-contributors please add @harshpandey002 for code


Styling question about border-radius on code snippets in main docs

This might be intended and therefore not an issue, but I wanted to ask about it.
I noticed the multi line code blocks wrapped in <pre> tags on the site use border-radius: 3em for viewports > 710px.
@media (min-width: 44.375em)
pre {

    border-radius: .3em;
}

At 1024px the sidebar collapses and the main content fills the width of the page, this is where I noticed there is a small bit of white space visible on each of the code block corners due to the rounded edge from border-radius.
Removing the border-radius for <pre> tags for viewports < 1024px would get rid of the extra white space so the code blocks have squared corners that occupy all of the white space covered by the container.
Currently, the stylesheet removes border-radius for viewports less than 710px. Thoughts on bumping the media query to 1024px or adding another media query to account for this?
Let me know your thoughts! @zachleat

Screenshot with border-radius (viewports > 710px & < 1024px when sidebar collapses)

Screenshot without border-radius (viewports < 710px)

It's been quite awhile and this is only a cosmetic change, so I'm going to close this for now.

It's been quite awhile and this is only a cosmetic change, so I'm going to close this for now.


Allow invalid ssl

This change allows for invalid SSL certs. Simply pass verify=False into the client.connect method as a kwarg.

Is there any way this can get merged in?

Ping

Thanks for the PR, we will take a look

Thanks for your patience @mew1033

Thanks so much! How often do you push new builds to Pypi?

@mew1033 I saw your email this morning, we're working on getting a release out ASAP. Please be patient

Will do, thanks again


enable generate markup enhanced markdown file with Obsidian canvas

Obsidian Canvas is a mindmap of Obsidian notes.
Canvas also supports groups, cards, links, which make it very powerful for thinking and writing.

xx.canvas file is in below format, raw json.
{
	"nodes":[
		{"type":"text","text":"root","id":"1f30eddad51710e4","x":-420,"y":-280,"width":200,"height":60},
		{"type":"file","file":"notes/2303261040.md","id":"98977e30971a598e","x":-80,"y":-315,"width":400,"height":130},
		{"type":"file","file":"notes/2303261047.md","id":"98c0a6f954857102","x":-80,"y":-85,"width":400,"height":400},
		{"type":"text","text":"FOO","id":"fbb65b30199c225f","x":560,"y":520,"width":250,"height":60}
	],
	"edges":[
		{"id":"e25d15f99c8c2fcc","fromNode":"1f30eddad51710e4","fromSide":"right","toNode":"98977e30971a598e","toSide":"left","label":"HA_1"},
		{"id":"be9b964fee986806","fromNode":"1f30eddad51710e4","fromSide":"bottom","toNode":"fbb65b30199c225f","toSide":"left"},
		{"id":"fee0d961ae334fcd","fromNode":"1f30eddad51710e4","fromSide":"bottom","toNode":"98c0a6f954857102","toSide":"left"}
	]
}

When considering generate a markdown file with canvas, the coordinate system is like below.

By navigating children of root node, and sorting siblings with XY axis, also parsing attributes in link label, it generates a markup markdown file.

Even group is very useful, but nodes and edges are good enough for generating markdown file.

Labels
Label is convenient to add some configuration information: attributes.
Attributes are separated by line break, \n,  e.g. NAME=VALUE\nFLAG1\NAME2=VALUE2

Tree data transformed from canvas json
For a given canvas raw file, get the children data for a node as below, as a tree layout.
 [
  {
    "type": "text",
    "text": "FOO",
    "id": "fbb65b30199c225f",
    "x": -70,
    "y": -660,
    "width": 250,
    "height": 60,
    "edge": {
      "id": "be9b964fee986806",
      "fromNode": "1f30eddad51710e4",
      "fromSide": "bottom",
      "toNode": "fbb65b30199c225f",
      "toSide": "left"
    },
    "children": []
  },
  {
    "type": "file",
    "file": "notes/2303261047.md",
    "id": "98c0a6f954857102",
    "x": -80,
    "y": -85,
    "width": 400,
    "height": 400,
    "edge": {
      "id": "fee0d961ae334fcd",
      "fromNode": "1f30eddad51710e4",
      "fromSide": "bottom",
      "toNode": "98c0a6f954857102",
      "toSide": "left"
    },
    "children": []
  },
  {
    "type": "file",
    "file": "notes/2303261040.md",
    "id": "98977e30971a598e",
    "x": -120,
    "y": 440,
    "width": 260,
    "height": 175,
    "edge": {
      "id": "e25d15f99c8c2fcc",
      "fromNode": "1f30eddad51710e4",
      "fromSide": "right",
      "toNode": "98977e30971a598e",
      "toSide": "left",
      "label": "HA=1\nB=1"
    },
    "children": [
      {
        "id": "a4aa70ec09702da7",
        "x": 340,
        "y": -267,
        "width": 250,
        "height": 60,
        "type": "text",
        "text": "fiio2",
        "edge": {
          "id": "7d8eb6ac1366f086",
          "fromNode": "98977e30971a598e",
          "fromSide": "right",
          "toNode": "a4aa70ec09702da7",
          "toSide": "bottom"
        },
        "children": []
      },
      {
        "id": "803771a6e597a7f2",
        "x": 465,
        "y": 20,
        "width": 250,
        "height": 60,
        "type": "text",
        "text": "bar",
        "edge": {
          "id": "ac13b1d46c90bfce",
          "fromNode": "98977e30971a598e",
          "fromSide": "right",
          "toNode": "803771a6e597a7f2",
          "toSide": "top"
        },
        "children": []
      }
    ]
  }
]


Defined new revisions for golang dep: github.com/itchyny/go-flags

Ran component through the scanners since I noticed it had not been harvested yet. PR matches curation site. Closing.


Granular categorisation of Iris warnings

Introduce subclasses of IrisWarning to precisely categorise all the types of warning relating to Iris behaviour. This will enable easy suppression of specific types of warning if a user knows this does not matter for their workflow.
Worldwide recognised warning categories - e.g. DeprecationWarning - should keep these categorisations and not be brought into the IrisWarning hierarchy.
Illustrative examples

IrisWarning

CFWarning

NotStdNameWarning
MissingCoordWarning

DemotedCoordWarning

Initial thoughts
Top class name
The annoying volume of warnings are primarily UserWarnings - those that relate to something the user is doing e.g. loading malformed data, plotting non-bounded coordinates etc. These create the noise so they are the ones we want to subcategorise. Top class should therefore by IrisUserWarning(UserWarning), to help clarify that filtering these will not filter other, rarer warnings such as DeprecationWarning.
Warning location
To ease user filtering, all IrisUserWarning subclasses should all be available from a single module. We already have an established precedent: iris.exceptions. This is ideal since Warning is a subclass of Exception.
The precedent of iris.exceptions is that this is the primary place the exceptions are defined, then they are imported by the modules that use them. This creates an unfortunate element of separation for future developers, however I think it is better than the inverse (creating in the location-of-use, which requires the creator to remember to import into iris.exceptions, and also potentially risks circular imports).
Existing warning classes
Iris currently has 3 subcategories of warning, spread throughout the code.

https://github.com/SciTools/iris/blob/c526ce0e5e9f1715fc81c29c9526bfda0a78deca/lib/iris/fileformats/nimrod_load_rules.py#L31
https://github.com/SciTools/iris/blob/c526ce0e5e9f1715fc81c29c9526bfda0a78deca/lib/iris/fileformats/_nc_load_rules/helpers.py#L285
https://github.com/SciTools/iris/blob/c526ce0e5e9f1715fc81c29c9526bfda0a78deca/lib/iris/fileformats/netcdf/saver.py#L311

These will be brought into the new hierarchy. Making TranslationWarning and UnkownCellMethodWarning subclasses of UserWarning has a minor potential to cause a breaking change in existing user filtering, but this is thought to be a niche case.
They will also be moved into iris.exceptions, then simply imported into their previous locations. There will be no breaking changes from this migration.


Add -ifChanged option to tsc

As TSC resolves the graph of inputs, it can collect timestamps on file and compare with output[s] timestamp[s].
Currently this check needs to be done in external tooling, and cannot be very precise (indeed there were bugs in TS build dependency calculation itself!)
TSC is in the best position to know the full dependencies/outputs graph -- and can skip emit if outputs are younger than inputs.

covered by https://github.com/Microsoft/TypeScript/issues/10879


Personalized data generation

hey, I cloned the repo. Its working fine with the pretrained model and data generated.
But, I wish to train model on new face, and how to generate data for the new face.
Is there any source code available?? if yes, whether it is included in this repo? If not can you please provide the same.
If anyone has worked on personalized datasets. please do comment. Your help is appreciated.
Thanks

I'm looking for same thing, do you have any solution ?

options folder ([https://github.com/YuanxunLu/LiveSpeechPortraits/tree/main/options]) contained training and testing code, but i don't know how to use this code. If anyone has knowledge of these use cases, please let me know.

please share your train.py


[AppConfig] Update code snippet

Resolves https://github.com/Azure/azure-sdk-for-python/issues/32678

API change check
API changes are not detected in this pull request.


Unable to build

I'm trying to build the binaries within Docker. While building, getting errors. The below-mentioned Docker file is used.
FROM golang:1.14
RUN cd / &&
git clone https://github.com/augmentable-dev/gitqlite.git &&
cd /gitqlite &&
make build
The error message is:
go<EMAIL_ADDRESS>parsing git2go/go.mod: open /gitqlite/git2go/go.mod: no such file or directory
make: *** [Makefile:59: build] Error 1
The command '/bin/sh -c cd / &&    git clone https://github.com/augmentable-dev/gitqlite.git &&    cd /gitqlite &&    make build' returned a non-zero code: 2
Please take a look and let me know how to proceed with the same.

Hi @nidhin077  - this looks like a very old Docker file, please see this one: https://github.com/mergestat/mergestat/blob/main/Dockerfile
Let me know if that helps!


add an applied_by attribute to suggested_changes objects?

I'm thinking that having an 'Applied by' column in the entity revisions lists would be good to have, and I bet we get asked for it eventually. Could we add an 'applied_by' attribute to objects returned from the various entities' suggested_changes endpoints? It might then make sense to change name of the 'user' attribute to 'created_by'. I don't consider this to be a high priority request, just thought it would be a good enhancement and didn't want to forget it.

OK, this might be premature optimization, but in order to support multiple revision states possibly with different users moving them into/out of those states, perhaps we should have a 'users' attribute that contains an object like:
"users": {
  "created": { "name": "Bob", "..." },
  "applied": { "name": "Alice", "..." },
  "some_future_state": { "name": "Carol", "..." }
}

This issue has been superseded by the lifecycle events stuff. Going to go ahead and close it.


Support import "module-name";

Formatting sources containing an import "foo"; line results in the following assertion:
../src/CodeGenerator.js:158
                throw new Error("AssertionError: " + message.replace(/\n/g, "\\n"));
                      ^
Error: tests/ProxyCase.js: AssertionError: currentValue should equal string: ""../src/misc/Lifetime"" == "{" at 9:7
    at CodeGenerator.assert (../src/CodeGenerator.js:158:23)
    at CodeGenerator.ensure (../src/CodeGenerator.js:490:18)
    at CodeGenerator._processSpecifiers (../../src/generators/modules.js:93:14)
    at CodeGenerator.ImportDeclaration (../../src/generators/modules.js:153:10)
    at CodeGenerator.print (../src/CodeGenerator.js:606:32)
    at ../../src/generators/index.js:17:14
    at arrayEach (/disks/protofroot/home/rousskov/Edit/pretty-generator/node_modules/lodash.foreach/node_modules/lodash._arrayeach/index.js:24:9)
    at /disks/protofroot/home/rousskov/Edit/pretty-generator/node_modules/lodash.foreach/index.js:25:9
    at CodeGenerator._statements (../../src/generators/index.js:16:5)
    at CodeGenerator.Program (../../src/generators/statements.js:6:10)

Please confirm this is fixed in versions past v1.5.1. npm update -g attractifier to update attractifier given default install method.

Confirmed as fixed.


Dockerlization and update workflow

Currently, the UI and API are separated, we want to update the workflow so that they can run as a whole system:

Backend host frontend itself: update frontend webpack and backend routing to host frontend files as static files
For developer, only one command make dev can start the system on local
Dockerlize the project

The branch will be based on dev-client

Done and update the README in dev-client branch


feature: server info

references: https://github.com/jrgp/linfo

I will look into this soon. thanks

I think this should be a plugin and not a core feature, I will close this, I have no idea where we will keep oficial plugins at the moment (or ideas)


Update Rise of Nations Extended Edition

to include DirectPlay for more reliable multiplayer connections.

I have not personally tested this yet but I have seen many reports of this helping. The latest report being from 1 month ago.
https://www.protondb.com/app/287450
On vanilla Proton, game matches will randomly disconnect and then crash about 1 hour into the game. That is a problem when games can last many hours. My last match took 2.5 hours.
Luckily, this game has a unique multiplayer save feature. My friends and I have been using that as a short-term workaround to save and reload games when they crash (the person whose game did not crash is still able to save).

I'm not sure this fix is necessary. Others say that directmusic and sound=alsa are sufficient. It would be nice if someone could give feedback on the current fix.

Most people are not playing multiplayer. directmusic and sound=alsa only affects being about to hear the music and sound affects throughout the game.
There are 2 reports in the GitHub Issue and 15 reports in the ProtonDB page that directplay is needed for online play. I am able to play online with no workarounds but me and my other friends on Linux constantly run into random connection issues. I believe DirectPlay will fix that.
I will test this out with my friends next time we play online and report back (by applying protontricks directplay to everyone's game).


Project Structure

Move core library (without CLI) to typings/core
Create docs as part of website repo
Make typings the main entry repo, but utilize core

Closing as I've created core. There's an issue around the website at https://github.com/typings/discussions/issues/5 where we can use help :+1:


Add ChainProvider

For various reasons texts aren't delivered (insufficient credentials etc) it would be handy to use a fallback options. I suggest adding a ChainProvider which can contain a list of configured providers. If one fail the next will be used.

Good idea!


Infer schemas from dependencies data

Given schema with dependencies data:
{
  "type": "object",
  "properties": {
    "name": { "type": "string" },
    "credit_card": { "type": "number" }
  },
  "required": ["name"],
  "dependencies": {
    "credit_card": {
      "properties": {
        "billing_address": { "type": "string" }
      },
      "required": ["billing_address"]
    }
  }
}

should be transformed and simplified:
{
  oneOf: [
    {
      "type": "object",
      "properties": {
        "name": { "type": "string" },
        "credit_card": { "type": "number" },
        "billing_address": { "type": "string" }
      },
      "required": ["name", "credit_card", "billing_address"]
    },
    {
      "type": "object",
      "properties": {
        "name": { "type": "string" }
      },
      "required": ["name"]
    }
  ]
}

Related to https://github.com/asyncapi/generator-model-sdk/issues/79

This is also relevant to propertyDependencies as the models can then be split accordingly based on the dependencies.

Already implemented to the extend that the type is implied, it however does not give you a strongly typed model.


Adding Support for JDK "only" and JAVA_HOME environment variable to Windows Installer

Since Java 11 Oracle distributes no separate JRE and renamed the windows registry key for the JDK. This patch will find the JDK with registry key HKLM “SOFTWARE\JavaSoft\JDK". As a last failback this patch looks for Java in the environment variable JAVA_HOME.

Can you please squash your changes?!

Thanks for the Pull Request. I applied it manually as I wanted to re-word the documentation change. I also added a changelog entry.
Fixed in:

master for 9.0.30 onwards
8.5.x for 8.5.50 onwards
7.0.x for 7.0.99 onwards


Fixed cursor projection

Even if we don't process the pick event, we should examine the list of picked objects to determine how to update the cursor
This fixes issue #1846
GearVRF DCO signed off by: Nola Donato<EMAIL_ADDRESS>

Planning to merge on Friday.


Error compiling shaders on linux

Hello
When I try to build anything using haxelib i get the following errors:

Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-video.vert.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-video.frag.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-text.vert.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-text.frag.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-image.vert.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-image.frag.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-colored.vert.glsl
Shader compiler process exited with code 1 while trying to compile /usr/lib/haxe/lib/kha/15,7,3/Sources/Shaders/painter-colored.frag.glsl

Do I need to install an extra package in order to be able compile shaders?
I'm using OpenSuse 13.2
Thanks.

I would guess the version of glibc I used to compile it is missing. Can you call the compiler manually and see what that outputs? It's in Kore/Tools/krafix

Ok, I updated glibc and gcc to the latest version and now it works.


Log a warning for unknown config keys and don't crash

jenkins: test this please

jenkins, test this please


Add Pull request and Issue templates

Overview
PRs and issues can really benefit from standardized descriptions and outlined details, whether it is for reviewers to understand what was done or for devs picking up new tasks.
This PR just adds a template for the PRs and issues so that every time one is created moving forward this can be used as a guideline.
Thanks 😄

Did you discuss with @ZoeSimon & @micheal-w-wells?

Not yet as they are away today, just something that I thought having a layout for would be beneficial (especially for the PRs)


refactor(homekit): replace slices.Max with custom maxByteSlice function

Removed dependency on the 'slices' package by implementing a custom function, maxByteSlice, to determine the maximum value in a slice of bytes. Tests for the new function have also been added to ensure correctness.
The change was made to reduce external dependencies and potentially improve the performance or maintainability of the code by using a simple native implementation instead of a package function. The unit tests included verify various scenarios for the new maxByteSlice function, ensuring it behaves as expected.

No longer relevant


Replace timestamp with block height in atomic_bridge_counterparty module

Summary
Updated atomic_bridge_counterparty module to use block height instead of timestamp for time lock.
Changelog
Substituted

block::get_current_block_height() for timestamp::now_seconds() and
genesis::setup() for timestamp::set_time_has_started_for_testing(aptos_framework)

Testing
All unit tests pass.
Outstanding issues
E2E tests should be done for abort_bridge_transfer (see issue https://github.com/movementlabsxyz/movement/issues/272 regarding challenges simulating incrementing block height in unit tests).

Thanks for the effort here, but as discussed, we will be using timestamp going forward.


MGDCTRS-566: help text/tooltips for Camel forms

Add a custom JSON schema bridge to further customize field definitions
and add appropriate field definitions for uniforms-patternfly.

I would appreciate any correction on the translation :smile:

@indraraj and @uidoyen : Mind a review?

Cool!  This seemed to be the way to go from the uniforms docs but I thought we didn't really need a complete custom implementation but a way to map our data to the uniforms-patternfly controls nicely.  It this good to merge then?

Cool! This seemed to be the way to go from the uniforms docs but I thought we didn't really need a complete custom implementation but a way to map our data to the uniforms-patternfly controls nicely. It this good to merge then?

yes


Remove vggish smoke test, add orca smoke test

Since vggish_model.py can be directly run to test instantiating the model and loading weights, that should be sufficient.