[flash_ctrl] Enable firmware dealing with multi-bit ECC and ICV errors

Before, these two errors types led to a fatal alert which is problematic during firmware selection and verification. This commit changes the design in the following way:

The two relevant bits in the FAULT_STATUS CSR are made clearable by software. Other bits in this register remain sticky.
The corresponding alert is no longer fatal.

This means the alert is only sent out until the two bits are cleared by software. To be on the safe side, firmware can still classify the alert as fatal on the receiver side (in the alert handler). For the other error sources, the alert keeps getting triggered as before, i.e., it remains fatal.
For more background information, refer to lowRISC/OpenTitan#21353.
This resolves lowRISC/OpenTitan#21637.

@matutem I've triggered a full DV regression locally and will report back once I have the results.

The results are here:
## FLASH_CTRL Simulation Results
### Thursday April 04 2024 17:05:55 UTC
### GitHub Revision: [`7dd8304be4`](https://github.com/lowrisc/opentitan/tree/7dd8304be4a590a1fb4b73c35611d3843938bd77)
### Branch: flash-ctrl-alert-fix
### [Testplan](https://opentitan.org/book/hw/ip/flash_ctrl/data/flash_ctrl_testplan.html)
### Simulator: VCS

### Test Results
|  Stage  |                   Name                    | Tests                                    |  Max Job Runtime  |  Simulated Time  |  Passing  |  Total  |  Pass Rate  |
|:-------:|:-----------------------------------------:|:-----------------------------------------|:-----------------:|:----------------:|:---------:|:-------:|:-----------:|
|   V1    |                   smoke                   | flash_ctrl_smoke                         |      4.257m       |     45.650us     |    50     |   50    |  100.00 %   |
|   V1    |                 smoke_hw                  | flash_ctrl_smoke_hw                      |      35.130s      |     31.717us     |     5     |    5    |  100.00 %   |
|   V1    |               csr_hw_reset                | flash_ctrl_csr_hw_reset                  |      1.003m       |     90.854us     |     5     |    5    |  100.00 %   |
|   V1    |                  csr_rw                   | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|   V1    |               csr_bit_bash                | flash_ctrl_csr_bit_bash                  |      44.970s      |    685.277us     |     5     |    5    |  100.00 %   |
|   V1    |               csr_aliasing                | flash_ctrl_csr_aliasing                  |      43.400s      |     2.226ms      |     5     |    5    |  100.00 %   |
|   V1    |        csr_mem_rw_with_rand_reset         | flash_ctrl_csr_mem_rw_with_rand_reset    |      25.010s      |    310.645us     |    20     |   20    |  100.00 %   |
|   V1    | regwen_csr_and_corresponding_lockable_csr | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_csr_aliasing                  |      43.400s      |     2.226ms      |     5     |    5    |  100.00 %   |
|   V1    |                 mem_walk                  | flash_ctrl_mem_walk                      |      19.910s      |     16.699us     |     5     |    5    |  100.00 %   |
|   V1    |            mem_partial_access             | flash_ctrl_mem_partial_access            |      21.020s      |    127.364us     |     5     |    5    |  100.00 %   |
|   V1    |                                           | **TOTAL**                                |                   |                  |    120    |   120   |  100.00 %   |
|   V2    |                   sw_op                   | flash_ctrl_sw_op                         |      38.950s      |     27.471us     |     5     |    5    |  100.00 %   |
|   V2    |             host_read_direct              | flash_ctrl_host_dir_rd                   |      1.456m       |     37.181us     |     5     |    5    |  100.00 %   |
|   V2    |                 rma_hw_if                 | flash_ctrl_hw_rma                        |      14.551m      |    167.433ms     |     3     |    3    |  100.00 %   |
|         |                                           | flash_ctrl_hw_rma_reset                  |      13.532m      |    760.496ms     |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_lcmgr_intg                    |      20.190s      |     15.558us     |    20     |   20    |  100.00 %   |
|   V2    |            host_controller_arb            | flash_ctrl_host_ctrl_arb                 |      36.867m      |    273.616ms     |     5     |    5    |  100.00 %   |
|   V2    |               erase_suspend               | flash_ctrl_erase_suspend                 |      8.778m       |     4.008ms      |     5     |    5    |  100.00 %   |
|   V2    |               program_reset               | flash_ctrl_prog_reset                    |      47.780s      |     2.437ms      |    30     |   30    |  100.00 %   |
|   V2    |            full_memory_access             | flash_ctrl_full_mem_access               |      34.667m      |    489.088ms     |     5     |    5    |  100.00 %   |
|   V2    |             rd_buff_eviction              | flash_ctrl_rd_buff_evict                 |      2.483m       |    110.554us     |     5     |    5    |  100.00 %   |
|   V2    |          rd_buff_eviction_w_ecc           | flash_ctrl_rw_evict                      |      46.250s      |     57.698us     |    40     |   40    |  100.00 %   |
|         |                                           | flash_ctrl_rw_evict_all_en               |      48.460s      |    128.617us     |    39     |   40    |   97.50 %   |
|         |                                           | flash_ctrl_re_evict                      |      53.070s      |     1.996ms      |    20     |   20    |  100.00 %   |
|   V2    |                 host_arb                  | flash_ctrl_phy_arb                       |      8.136m       |     5.129ms      |    20     |   20    |  100.00 %   |
|   V2    |              host_interleave              | flash_ctrl_phy_arb                       |      8.136m       |     5.129ms      |    20     |   20    |  100.00 %   |
|   V2    |             memory_protection             | flash_ctrl_mp_regions                    |      7.280m       |     15.803ms     |    20     |   20    |  100.00 %   |
|   V2    |                fetch_code                 | flash_ctrl_fetch_code                    |      30.910s      |    419.356us     |    10     |   10    |  100.00 %   |
|   V2    |              all_partitions               | flash_ctrl_rand_ops                      |      24.313m      |    151.534us     |    20     |   20    |  100.00 %   |
|   V2    |                 error_mp                  | flash_ctrl_error_mp                      |      40.071m      |     63.814ms     |    10     |   10    |  100.00 %   |
|   V2    |              error_prog_win               | flash_ctrl_error_prog_win                |      20.158m      |    801.255us     |    10     |   10    |  100.00 %   |
|   V2    |              error_prog_type              | flash_ctrl_error_prog_type               |      49.916m      |    964.553us     |     5     |    5    |  100.00 %   |
|   V2    |              error_read_seed              | flash_ctrl_hw_read_seed_err              |      20.970s      |    117.913us     |    20     |   20    |  100.00 %   |
|   V2    |            read_write_overflow            | flash_ctrl_oversize_error                |      2.249m       |     1.493ms      |     5     |    5    |  100.00 %   |
|   V2    |            flash_ctrl_disable             | flash_ctrl_disable                       |      32.190s      |     18.325us     |    50     |   50    |  100.00 %   |
|   V2    |            flash_ctrl_connect             | flash_ctrl_connect                       |      23.930s      |     13.447us     |    80     |   80    |  100.00 %   |
|   V2    |                stress_all                 | flash_ctrl_stress_all                    |      25.623m      |     13.720ms     |     5     |    5    |  100.00 %   |
|   V2    |             secret_partition              | flash_ctrl_hw_sec_otp                    |      2.933m       |     4.412ms      |    50     |   50    |  100.00 %   |
|         |                                           | flash_ctrl_otp_reset                     |      3.230m       |    110.209us     |    80     |   80    |  100.00 %   |
|   V2    |            isolation_partition            | flash_ctrl_hw_rma                        |      14.551m      |    167.433ms     |     3     |    3    |  100.00 %   |
|   V2    |                interrupts                 | flash_ctrl_intr_rd                       |      2.781m       |     2.455ms      |    40     |   40    |  100.00 %   |
|         |                                           | flash_ctrl_intr_wr                       |      1.410m       |     49.361ms     |    10     |   10    |  100.00 %   |
|         |                                           | flash_ctrl_intr_rd_slow_flash            |      4.207m       |     99.360ms     |    40     |   40    |  100.00 %   |
|         |                                           | flash_ctrl_intr_wr_slow_flash            |      5.195m       |     50.967ms     |    10     |   10    |  100.00 %   |
|   V2    |                invalid_op                 | flash_ctrl_invalid_op                    |      1.338m       |     29.410ms     |    20     |   20    |  100.00 %   |
|   V2    |                mid_op_rst                 | flash_ctrl_mid_op_rst                    |      1.585m       |     3.760ms      |     5     |    5    |  100.00 %   |
|   V2    |              double_bit_err               | flash_ctrl_read_word_sweep_derr          |      32.650s      |     37.058us     |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_ro_derr                       |      1.768m       |     1.446ms      |    10     |   10    |  100.00 %   |
|         |                                           | flash_ctrl_rw_derr                       |      5.026m       |     19.067ms     |    10     |   10    |  100.00 %   |
|         |                                           | flash_ctrl_derr_detect                   |      2.551m       |    457.467us     |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_integrity                     |      5.634m       |     12.694ms     |     5     |    5    |  100.00 %   |
|   V2    |              single_bit_err               | flash_ctrl_read_word_sweep_serr          |      33.090s      |    269.546us     |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_ro_serr                       |      1.810m       |    784.548us     |    10     |   10    |  100.00 %   |
|         |                                           | flash_ctrl_rw_serr                       |      5.583m       |     3.804ms      |    10     |   10    |  100.00 %   |
|   V2    |           singlebit_err_counter           | flash_ctrl_serr_counter                  |      55.270s      |    546.677us     |     5     |    5    |  100.00 %   |
|   V2    |           singlebit_err_address           | flash_ctrl_serr_address                  |      1.076m       |     3.310ms      |     5     |    5    |  100.00 %   |
|   V2    |                 scramble                  | flash_ctrl_wo                            |      2.022m       |     9.960ms      |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_write_word_sweep              |      20.200s      |     66.693us     |     1     |    1    |  100.00 %   |
|         |                                           | flash_ctrl_read_word_sweep               |      13.690s      |    252.042us     |     1     |    1    |  100.00 %   |
|         |                                           | flash_ctrl_ro                            |      1.220m       |    556.839us     |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_rw                            |      5.275m       |     7.721ms      |    20     |   20    |  100.00 %   |
|   V2    |            filesystem_support             | flash_ctrl_fs_sup                        |      32.370s      |    292.535us     |     5     |    5    |  100.00 %   |
|   V2    |          rma_write_process_error          | flash_ctrl_rma_err                       |      8.670m       |     93.554ms     |     3     |    3    |  100.00 %   |
|         |                                           | flash_ctrl_hw_prog_rma_wipe_err          |      2.291m       |     10.012ms     |    20     |   20    |  100.00 %   |
|   V2    |                alert_test                 | flash_ctrl_alert_test                    |      20.520s      |     87.260us     |    50     |   50    |  100.00 %   |
|   V2    |                 intr_test                 | flash_ctrl_intr_test                     |      20.270s      |     52.918us     |    50     |   50    |  100.00 %   |
|   V2    |           tl_d_oob_addr_access            | flash_ctrl_tl_errors                     |      26.340s      |     55.797us     |    20     |   20    |  100.00 %   |
|   V2    |            tl_d_illegal_access            | flash_ctrl_tl_errors                     |      26.340s      |     55.797us     |    20     |   20    |  100.00 %   |
|   V2    |          tl_d_outstanding_access          | flash_ctrl_csr_hw_reset                  |      1.003m       |     90.854us     |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_csr_aliasing                  |      43.400s      |     2.226ms      |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_same_csr_outstanding          |      40.900s      |    850.692us     |    20     |   20    |  100.00 %   |
|   V2    |            tl_d_partial_access            | flash_ctrl_csr_hw_reset                  |      1.003m       |     90.854us     |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|         |                                           | flash_ctrl_csr_aliasing                  |      43.400s      |     2.226ms      |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_same_csr_outstanding          |      40.900s      |    850.692us     |    20     |   20    |  100.00 %   |
|   V2    |                                           | **TOTAL**                                |                   |                  |   1012    |  1013   |   99.90 %   |
|   V2S   |          shadow_reg_update_error          | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |    shadow_reg_read_clear_staged_value     | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |         shadow_reg_storage_error          | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |           shadowed_reset_glitch           | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |    shadow_reg_update_error_with_csr_rw    | flash_ctrl_shadow_reg_errors_with_csr_rw |      24.300s      |     36.696us     |    20     |   20    |  100.00 %   |
|   V2S   |                tl_intg_err                | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|         |                                           | flash_ctrl_tl_intg_err                   |      20.563m      |    690.861us     |    20     |   20    |  100.00 %   |
|   V2S   |         sec_cm_reg_bus_integrity          | flash_ctrl_tl_intg_err                   |      20.563m      |    690.861us     |    20     |   20    |  100.00 %   |
|   V2S   |         sec_cm_host_bus_integrity         | flash_ctrl_tl_intg_err                   |      20.563m      |    690.861us     |    20     |   20    |  100.00 %   |
|   V2S   |         sec_cm_mem_bus_integrity          | flash_ctrl_rd_intg                       |      40.330s      |    101.278us     |     3     |    3    |  100.00 %   |
|         |                                           | flash_ctrl_wr_intg                       |      19.440s      |    162.959us     |     3     |    3    |  100.00 %   |
|   V2S   |       sec_cm_scramble_key_sideload        | flash_ctrl_smoke                         |      4.257m       |     45.650us     |    50     |   50    |  100.00 %   |
|   V2S   |       sec_cm_lc_ctrl_intersig_mubi        | flash_ctrl_otp_reset                     |      3.230m       |    110.209us     |    80     |   80    |  100.00 %   |
|         |                                           | flash_ctrl_disable                       |      32.190s      |     18.325us     |    50     |   50    |  100.00 %   |
|         |                                           | flash_ctrl_sec_info_access               |      1.134m       |     2.591ms      |    50     |   50    |  100.00 %   |
|         |                                           | flash_ctrl_connect                       |      23.930s      |     13.447us     |    80     |   80    |  100.00 %   |
|   V2S   |         sec_cm_ctrl_config_regwen         | flash_ctrl_config_regwen                 |      20.470s      |     66.891us     |     5     |    5    |  100.00 %   |
|   V2S   |     sec_cm_data_regions_config_regwen     | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|   V2S   |     sec_cm_data_regions_config_shadow     | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |     sec_cm_info_regions_config_regwen     | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|   V2S   |     sec_cm_info_regions_config_shadow     | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |         sec_cm_bank_config_regwen         | flash_ctrl_csr_rw                        |      22.960s      |    194.230us     |    20     |   20    |  100.00 %   |
|   V2S   |         sec_cm_bank_config_shadow         | flash_ctrl_shadow_reg_errors             |      24.200s      |     14.298us     |    20     |   20    |  100.00 %   |
|   V2S   |        sec_cm_mem_ctrl_global_esc         | flash_ctrl_disable                       |      32.190s      |     18.325us     |    50     |   50    |  100.00 %   |
|   V2S   |         sec_cm_mem_ctrl_local_esc         | flash_ctrl_rd_intg                       |      40.330s      |    101.278us     |     3     |    3    |  100.00 %   |
|         |                                           | flash_ctrl_access_after_disable          |      17.610s      |     41.032us     |     3     |    3    |  100.00 %   |
|   V2S   |      sec_cm_mem_disable_config_mubi       | flash_ctrl_disable                       |      32.190s      |     18.325us     |    50     |   50    |  100.00 %   |
|   V2S   |         sec_cm_exec_config_redun          | flash_ctrl_fetch_code                    |      30.910s      |    419.356us     |    10     |   10    |  100.00 %   |
|   V2S   |            sec_cm_mem_scramble            | flash_ctrl_rw                            |      5.275m       |     7.721ms      |    20     |   20    |  100.00 %   |
|   V2S   |           sec_cm_mem_integrity            | flash_ctrl_rw_serr                       |      5.583m       |     3.804ms      |    10     |   10    |  100.00 %   |
         |                                           | flash_ctrl_rw_derr                       |      5.026m       |     19.067ms     |    10     |   10    |  100.00 %   |
|         |                                           | flash_ctrl_integrity                     |      5.634m       |     12.694ms     |     5     |    5    |  100.00 %   |
|   V2S   |       sec_cm_rma_entry_mem_sec_wipe       | flash_ctrl_hw_rma                        |      14.551m      |    167.433ms     |     3     |    3    |  100.00 %   |
|   V2S   |          sec_cm_ctrl_fsm_sparse           | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |           sec_cm_phy_fsm_sparse           | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |        sec_cm_phy_prog_fsm_sparse         | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |             sec_cm_ctr_redun              | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |       sec_cm_phy_arbiter_ctrl_redun       | flash_ctrl_phy_arb_redun                 |      32.630s      |    705.312us     |     4     |    5    |   80.00 %   |
|   V2S   |  sec_cm_phy_host_grant_ctrl_consistency   | flash_ctrl_phy_host_grant_err            |      21.630s      |     16.284us     |     5     |    5    |  100.00 %   |
|   V2S   |      sec_cm_phy_ack_ctrl_consistency      | flash_ctrl_phy_ack_consistency           |      18.290s      |     16.032us     |     5     |    5    |  100.00 %   |
|   V2S   |           sec_cm_fifo_ctr_redun           | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |     sec_cm_mem_tl_lc_gate_fsm_sparse      | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |     sec_cm_prog_tl_lc_gate_fsm_sparse     | flash_ctrl_sec_cm                        |      1.535h       |     3.604ms      |     5     |    5    |  100.00 %   |
|   V2S   |                                           | **TOTAL**                                |                   |                  |    143    |   144   |   99.31 %   |
|   V3    |           asymmetric_read_path            | flash_ctrl_rd_ooo                        |      40.580s      |     1.373ms      |     1     |    1    |  100.00 %   |
|   V3    |                                           | **TOTAL**                                |                   |                  |     1     |    1    |  100.00 %   |
|         |                                           | **TOTAL**                                |                   |                  |   1276    |  1278   |   99.84 %   |

## Failure Buckets

* `UVM_ERROR (csr_utils_pkg.sv:466) [csr_utils::csr_rd_check] Check failed obs == exp (* [*] vs * [*]) Regname: flash_ctrl_core_reg_block.op_status.err reset value: *` has 1 failures:
    * Test flash_ctrl_rw_evict_all_en has 1 failures.
        * 2.flash_ctrl_rw_evict_all_en.98617306044765743469475087889531055493042539760567869114643958433207808827914\
          Line 72, in log /home/dev/src/scratch/flash-ctrl-alert-fix/flash_ctrl-sim-vcs/2.flash_ctrl_rw_evict_all_en/latest/run.log

                UVM_ERROR @ 68506.4 ns: (csr_utils_pkg.sv:466) [csr_utils::csr_rd_check] Check failed obs == exp (0 [0x0] vs 1 [0x1]) Regname: flash_ctrl_core_reg_block.op_status.err res
et value: 0x0
                UVM_INFO @ 68506.4 ns: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
                --- UVM Report catcher Summary ---

* `UVM_ERROR (cip_base_scoreboard.sv:241) [scoreboard] Check failed expected_alert[alert_name].expected == * (* [*] vs * [*]) alert recov_err triggered unexpectedly` has 1 failures:
    * Test flash_ctrl_phy_arb_redun has 1 failures.
        * 4.flash_ctrl_phy_arb_redun.79481903659732843559493199112123358250740252934694650912601330197783080465856\
          Line 72, in log /home/dev/src/scratch/flash-ctrl-alert-fix/flash_ctrl-sim-vcs/4.flash_ctrl_phy_arb_redun/latest/run.log

                UVM_ERROR @ 4794.1 ns: (cip_base_scoreboard.sv:241) [uvm_test_top.env.scoreboard] Check failed expected_alert[alert_name].expected == 1 (0 [0x0] vs 1 [0x1]) alert recov_e
rr triggered unexpectedly
                UVM_INFO @ 4794.1 ns: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
                --- UVM Report catcher Summary ---


bug: priority moves

http://bulbapedia.bulbagarden.net/wiki/Priority#Generation_I

data format now supports this, but still need battle mechanics to take this into account


fix: add test case for regex in split() method

Checklist:

[X] I have read and followed the contribution guidelines.
[X] I have read and followed the how to open a pull request guide.
[X] My pull request targets the main branch of freeCodeCamp.
[X] I have tested these changes either locally on my machine, or GitPod.

While testing this lesson, I noticed that there was no test for the regex code. I also edited the instruction to indicate the regex code. We can adjust the description and all, however, but I felt we should test for the regex code.

This looks like a duplicate PR to this one
https://github.com/freeCodeCamp/freeCodeCamp/pull/53155/files
As such, I am going to close this one


Start button

Before opening an issue:

[X ] I tested the latest release
[ X] I looked at other issues (even the closed ones)
[ X] I read the Troubleshooting Guide
[ X] I'll fill this template properly

Describe the bug
When i give all the permission the app says "to start the script enter fgo" but when im in there's no play button, tried everything but still no button when i enter fgo
Device Info (please fill at-least 'Device model'):

Device model: Oppo a91
Screen size: 1080x2040
Android Version: 11
RAM: 8

I myself have had this problem before on my Realme (subbrand of Oppo) phone.
It's similar to the Accessibility problem which happens due to the app process being killed when AccessibilityService is still enabled.
Unfortunately, there's no real solution from our end. You can try playing with your device's battery optimisation settings, force stop the app, restart your phone, etc.
The way I counter this problem without changing any battery optimization settings is to turn OFF the Accessibility service after every use and only turn it back ON when I want to use the app. Realme has an option to toggle AccessibilityService using gestures, so I think Oppo might have that too, which makes it very convenient to turn it OFF/ON on demand.

Tried what you did but the play button still doesnt appear reeeeee

As a very sided side note, if your accessibility service shows "not working, tap for info", try turning it off and on again to enable it. When it shows that it's not working, it will not work.
See if your settings is like that. If not then I guess Android Emulator from Android Studio is always an option...

That won't solve it from my experience. Oppo/Realme phones stop providing configuration change (screen rotation) info sometimes, which we can't do much about.
One possibility I could think of is to have FGA in landscape orientation before clicking on Start Service.

Yooooo solved, you Just Need to put the automatic rotatoion, then start when the screen Is horizzontal


join: failing GNU tests

Since it seems like it could be useful to have this information somewhere, here are the remaining failing GNU tests for join:

[ ] 3c: no support for joins with a null field separator, -t "\0" (#2881)
[ ] 10b: broken comparisons with empty fields (#2908)
[x] sp-vs-blank: \f (form feed) seems to be interpreted as a newline (#2851)
[ ] 8-bit-t: 8-bit characters aren't valid unicode, cause a panic (first half:  #2851, second half: #2902)
[ ] bigfield1 and bigfield2: very large integers cause parsing as a field number to fail ( #2882)
[x] invalid-j: test expects the invalid -j error to trigger before the missing args error (patched upstream)
[ ] chkodr-4 and chkodr-7: GNU has relaxed order checks by default; see info join -n "General options in join" (#2908)
[x] chkodr-5, chkodr-5b, chkodr-5c, and header3: slight differences in "not sorted" error message (#2899)
[ ] chkodr-5d and chkodr-5e: missing additional error messages (#2908)
[x] z1, z4, z5, z6: -z flag (null-terminated lines) isn't supported (#2880)

Once all the open PRs are merged, all the GNU tests for join are passing (note that the CI won't reflect this until the workflows are updated to use the fixed invalid-j test).

Excellent! Could you open a PR to update the workflow?


[ProjectManager] PropertiesDialog theming fixes...

Before fix:

After:

@Meychi please check this pr

This is not correct, layout breaks as seen on your after image, i think you only need to set font.

Oh.. ok

@Meychi fixed

Merged, but note that one line has wrong formatting... I will fix it.

Merged, but note that one line has wrong formatting...
Sorry 👍


Fails to run on macOS
The app doesn't run on macOS 13.1 (22C65) with Xcode 14.1 out of the box. It works if I run in an iPad simulator.

I believe the error is due to code signing, since the huggingface credentials are hard coded.
Fails to build with CLI
I'm also seeing compile errors when trying to build the app from the CLI. When building from Xcode, the build phase succeeds however launch fails.
$ xcodebuild clean build CODE_SIGN_IDENTITY="" CODE_SIGNING_REQUIRED=NO

/swift-coreml-diffusers/Diffusion/Pipeline/Pipeline.swift:13:8: error: no such module 'StableDiffusion'
import StableDiffusion
       ^

** BUILD FAILED **

Edit: I successfully built and ran the app using this command:
xcodebuild clean build -scheme Diffusion CODE_SIGN_IDENTITY="" CODE_SIGNING_REQUIRED=NO

Should be fixed by https://github.com/huggingface/swift-coreml-diffusers/commit/7e9956725b892992c0ee6ce41d86b6fffc38df3c.


Yaml list not working as main pipeline variable

Hi Azure DevOps !
I'm working on a multistage pipeline with some template.
I wanted to create a list in variables like :
variables:
   deploy_services:
    - 'service'
    - 'serverfunction'

and use it in as template parameters:
stages:
  - stage: Build
    jobs:
    - template: jobs/template-build.yml
      parameters:
        pool: "Azure Pipelines"
        DEPLOY_SERVICES: $(deploy_services)
  - stage: Deploy
    jobs:
    - template: jobs/template-deploy.yaml
      parameters:
        deploy_services: $(deploy_services)

I tried with some [] and other format but Azure devops don't like it.
Is there a way to manage that ?

Unfortunately looking at how the pipeline is built, it doesn't seem to be possible.
name: string  # build numbering format
resources:
  pipelines: [ pipelineResource ]
  containers: [ containerResource ]
  repositories: [ repositoryResource ]
variables: { string: string } | [ variable | templateReference ]
trigger: trigger
pr: pr
stages: [ stage | templateReference ]

As you can see, variables can only be of type string or reference a template or a variable group.
Even if you reference a template, it won't work because you will use again the keyword variables that won't work like parameters.

Moved into Developer Community: https://developercommunity.visualstudio.com/content/problem/1007467/yaml-list-not-working-as-main-pipeline-variable.html
Please use "Follow" button on the right to track it

@EtienneDeneuve: Please go to this link and answer Microsoft team: https://developercommunity.visualstudio.com/content/problem/1007467/yaml-list-not-working-as-main-pipeline-variable.html


Reading from buffers should require Eff

Consider the following program:
module Main where

import Prelude
import qualified Node.Buffer as B
import Control.Monad.Eff.Console (log)

main = do
  let buf = B.fromArray [0]
  let x = B.read B.UInt8 0 buf
  B.write B.UInt8 1 0 buf
  let y = B.read B.UInt8 0 buf

  log ("x = " ++ show x)
  log ("y = " ++ show y)

Output:
x = 0
y = 1

This seems to be a subversion of the type system. I think we should require Eff to read or write from a buffer. Since they can be used in a similar way to IORef in Haskell, perhaps we also should require Eff to create them, like Haskell does.
(Unfortunately this program doesn't actually run at the moment but that problem is fixed by #4)

Agreed!

And creating them too, I think.
module Main where

import Prelude
import qualified Node.Buffer as B
import Control.Monad.Eff.Console (log)

main = do
  let buf = B.fromArray [0]
  B.write B.UInt8 1 0 buf

  let r = log <<< show <<< B.read B.UInt8 0

  r buf
  r (B.fromArray [0])

prints
1
0

Here, since we've defined buf = B.fromArray [0], it should therefore be possible to replace buf with B.fromArray [0] and not change the meaning. So I think we should have fromArray :: forall eff. Array Octet -> Eff (buffer :: BUFFER | eff) Buffer, and similar for create.

Yep, probably everything should have the effect because they are inherently mutable things. I think I'm responsible for the crimes in here. :wink:

Closed by #7


test: attempt to quote python interpreter path

Attempt to properly quote the python interpreter path in the lit configuration.  This
was quoted in some places but not others.  This attempts to homogenise the path quoting.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

CC: @tachoknight @drexin @yln

@swift-ci please test macOS platform

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - 6d63d957d83c339a3997428d13d29cde6d87ab74

@swift-ci please test Linux platform


Add prefixes to MIL-STD to make IDs unique

When I looked at the ontology files, I did not see a non-unique identifier issue. So moving this to TechDebt.

When I looked at the ontology files, I did not see a non-unique identifier issue. So moving this to TechDebt.


Fixes issue 202 - Allow SPICE FITS files with missing telemetry

PR Description
This addresses issue #202 . The code now ignores HDUs that are not primary or image HDUs.

pre-commit.ci autofix

Thanks for the PR @EdBehn!


Add a SourceOption type for loading specs from non-file sources

The key change here is to replace the "filename" option, storing a
string, with an instance of the newly added SourceOption class, that
lets us statically encode a data source which is (currently] either a
file or a string.
The immediate use for this will be supporting Shai to load modules from
a string (while maximizing code reuse), but this could also be used
to read in specs (or other data) from stdin or a socket etc.
This change, again, aims to be minimally invasive while extending functionality
in generally (and specifically) useful ways. As such, no tests are included
here, since no new functionality is yet exposed (i.e., the PR doesn't expose the
ability to load specs from stdin).
Tests to exercise the relevant portion in the SanyParserPassImpl will be
forthcoming in #1855.

[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[x] Documentation added for any new functionality

Codecov Report

Merging #1920 (ad973a1) into unstable (ec694c4) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##           unstable    #1920      +/-   ##
============================================
- Coverage     77.05%   77.01%   -0.04%
============================================
  Files           409      409
  Lines         12582    12588       +6
  Branches        588      597       +9
============================================
  Hits           9695     9695
- Misses         2887     2893       +6

Impacted Files
Coverage Δ

...e/apalache/infra/passes/WriteablePassOptions.scala
6.25% <ø> (ø)

.../apalache/tla/tooling/opt/AbstractCheckerCmd.scala
0.00% <0.00%> (ø)

...at/forsyte/apalache/tla/tooling/opt/ParseCmd.scala
0.00% <0.00%> (ø)

.../at/forsyte/apalache/tla/tooling/opt/TestCmd.scala
0.00% <0.00%> (ø)

...orsyte/apalache/tla/tooling/opt/TypeCheckCmd.scala
0.00% <0.00%> (ø)

...e/apalache/tla/imp/passes/SanyParserPassImpl.scala
0.00% <0.00%> (ø)

...apalache/tla/pp/passes/ConfigurationPassImpl.scala
0.00% <0.00%> (ø)

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 ec694c4...ad973a1. Read the comment docs.


Avoid preprocessing images that have already been preprocessed.

The ZX quantiser is slow, so we need this.
Happy to delay merging this until https://github.com/GoogleChromeLabs/squoosh/pull/124 is resolved, since it touches a lot of the same stuff.

@developit @kosamari @surma This is ready for review now


fix(datastore): ModelSyncedEvent dispatch consistency

Issue #, if available:
Description of changes:
SyncEventEmitter takes in both InitialSyncOrchestrator and ReconciliationQueue to receive events from. InitialSyncOrchestrator is responsible for providing events to each of the ModelSyncedEventEmitter's to increment a count of models received from the syncQuery, by filtering down to the modelName, and then using the events to figure out information like whether it was a full or delta sync, number of records received. ReconciliationQueue similarly provides events to each of the ModelSyncedEventEmitter's to increment the count of models reconciled. With the two stream of events, an on-going calculation is done to check and emit the ModelSyncedEvent when the reconciled number matches the received number.
In this PR, InitialSyncOperation will always send an .finished event whenever the operation itself finishes. The finished event is an event passed to the ModelSyncedEventEmitter to ensure calculation done correctly. When the .finished event is not sent from InitialSyncOperation,
ModelSyncedEventEmitter will never emit the ModelSyncedEvent because it doesn't think it has finished receiving the received record count. This would happen if InitialSyncOperation performs a successful syncQuery API call, followed by a failed one.
The second change in this PR, ReconcileAndLocalSaveOperation will emit the mutationEventDropped event in operation error cases as well. From ModelSyncedEventEmitter's prespective, a reconciled count is when a record was either reconciled (save/updated/deleted) or dropped (smaller or duplicate version). ReconcileAndLocalSaveOperation will emit the dropped event even in the case where the model was determined to be reconciled but failed (for example, local storage adapter failed to save). This will contribute to the overall calculation of ModelSyncedEventEmitter so that the records reconciled will eventually match the records received, despite errors within those reconciliation. Errors within reconciliation is not handled by ModelSyncedEventEmitter and is out of scope of this PR. Reconciliation errors in general should be sent back on the errorHandler for visibility.
Check points: (check or cross out if not relevant)

[x] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

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

Codecov Report

Merging #1823 (8c4acb6) into main (c88625f) will increase coverage by 0.16%.
The diff coverage is 80.76%.

@@            Coverage Diff             @@
##             main    #1823      +/-   ##
==========================================
+ Coverage   59.23%   59.39%   +0.16%
==========================================
  Files         716      716
  Lines       22002    22013      +11
==========================================
+ Hits        13033    13075      +42
+ Misses       8969     8938      -31

Flag
Coverage Δ

API_plugin_unit_test
62.51% <ø> (ø)

AWSPluginsCore
71.22% <ø> (-0.08%)
:arrow_down:

Amplify
46.87% <ø> (+0.03%)
:arrow_up:

Analytics_plugin_unit_test
71.09% <ø> (ø)

Auth_plugin_unit_test
78.67% <ø> (ø)

DataStore_plugin_unit_test
76.40% <80.76%> (+0.56%)
:arrow_up:

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...goryPlugin/Sync/InitialSync/SyncEventEmitter.swift
94.59% <0.00%> (ø)

...tionSync/AWSIncomingEventReconciliationQueue.swift
59.16% <0.00%> (ø)

...cileAndLocalSave/AWSModelReconciliationQueue.swift
80.59% <0.00%> (ø)

...eAndLocalSave/ReconcileAndLocalSaveOperation.swift
86.97% <85.18%> (-0.53%)
:arrow_down:

...Plugin/Sync/InitialSync/InitialSyncOperation.swift
73.75% <100.00%> (+0.90%)
:arrow_up:

...gin/Sync/InitialSync/InitialSyncOrchestrator.swift
75.78% <100.00%> (+25.01%)
:arrow_up:

...gin/Sync/InitialSync/ModelSyncedEventEmitter.swift
90.62% <100.00%> (+1.04%)
:arrow_up:

...e/AWSPluginsCore/Auth/AWSAuthServiceBehavior.swift
87.50% <0.00%> (-12.50%)
:arrow_down:

...gin/Subscribe/DataStoreObserveQueryOperation.swift
74.64% <0.00%> (-0.94%)
:arrow_down:

... and 3 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Add Delta Lake committers page to delta.io

We currently do not have committers guidelines and requirements on the delta.io website, we need to add a page that provides that context.

Updated the committers list via #145 and #151 and linked to the contribution guide.


[readme] specify an actual internal ingress for conditional DNS forwarding test

Noted a slight oopsiedoodle in the Home DNS resolution section referring to echo-server to test internal DNS resolution via dns conditional forwarding. We have Cilium's Hubble as an internal ingress so that should do the job just fine. Clarify that any internal class ingress would work too, if folks have added additional apps/services.

Thanks!


[CHERRY-PICK] further speed up recursive ls by not syncpersist when we are create file as part of a loadMetadata operation. (#7782)

@apc999 @gpang

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/480/
Test PASSed.


not working with localhost urls?

Thanks for this plugin!
I noticed that my local dev urls aren't being picked up by this plugin anymore.
Here are my settings:
)
Please let me know if I need to provide any additional information.

chrome v 57.0.2987.110.
Also, noticed an error on my console coming from the plugin. Not quite sure if this is the cause.

I talked about Tab Modifier version, force extensions update you'll get 0.18.4.

I reinstalled the extensions and I'm now on  0.18.4. Issue still perists. I think the issue is related to L16 I highlighted above. A type error is thrown and the rest of the code doesn't execute.

OK later today you'll get 0.18.5! Thanks!


MessageBodyReader for RDF/POST

Refactor RDFForm

https://github.com/Graphity/graphity-core/issues/14


mxgraph 3.8.0 not installing via npm

$ npm install --save mxgraph
><EMAIL_ADDRESS>postinstall C:\Users\Artur\Documents\web\sites\dipl\research\angular\node_modules\mxgraph
> grunt build
Loading "Gruntfile.js" tasks...ERROR
>> TypeError: Cannot read property 'map' of null
Warning: Task "build" not found. Use --force to continue.
Aborted due to warnings.

probably related to #116 #102 #83

I found the same problem


docs(decision-tree-widget): implement Operator Decision Tree widget

Implements the Operator Decision Tree widget, and add to both doc/index.md and doc/operators.md
Notice specially doc/decision-tree-widget/tree.yml which is the decision tree data encoded in YAML. Probably the decision tree YAML file still needs review and improvement, but we could update it separately from this PR.
To see this page live, open http://rxjs5-esdoc-decision-tree.surge.sh/

That is super cool.

Love this too. :cupid:

It seems the operator's url is not correct, such as mapTo links to http://rxjs5-esdoc-decision-tree.surge.sh/class/es6/Observable.js~Observable.html.

@todoubaba The links are correct, but they refer to a future version of the Observable.html page, we're depending on PR #1376 merged first.

Yeah, looking forward that :+1:

:heart: Change looks good to me.

I need to rebase, apparently

Rebased, but it will conflict with #1385 when that is merged. (and will need another rebase)

Rebossed.

So, you know what I'm going to say. This is really cool. We should probably implement it with RxJS 5 and annotate the code. :P
LOLOLOL... Too funny, @staltz

So, in reality it's not trolling and it's absolutely serious stuff. Cycle.js doesn't currently work with RxJS v5, we're working on getting that support up. In the meanwhile, RxJS v4 is quite huge in size to include to this page, specially because we already have full RxJS v5 loaded in the page. So I went for something small in size, and I chose a version of Cycle.js called Motorcycle.js, focused on performance.
If you'd prefer for PR purposes that I just use RxJS v4 even if it's larger, fine by me. Or, I can place the whole decision tree widget elsewhere, make it generic for any purposes, then just import it here. So, your call.

If you'd prefer for PR purposes that I just use RxJS v4 even if it's larger, fine by me.

Honestly, that's probably better. But ideally, we'd have it in RxJS 5 and it would be annotated.
Could write it in Angular 2 ;) haha.

Could write it in anything. I just wanted to get it done.

But ideally, we'd have it in RxJS 5 and it would be annotated.

Will do when the support is out. I'll update this PR with Rx4 to make y'all happy.

@staltz Now you can use only what you want of Rx instead of whole library https://github.com/Reactive-Extensions/RxJS/tree/master/src/modular

I updated the PR to use Rx v4, and uglifyjs.

Rebased

Looks good to me (but another rebase... :sweat: )

Rebombed. :)

@blesh are you serious about this PR having to use RxJS v5 for dogfooding purposes? Just want to know what are your intentions because I could honestly convert this to a pseudo-Cycle.js app, since it's so small I can give up a bit on the actual framework and just apply the same architectural ideas.

Ok, I just did what I said in my previous comment, so now it should be fully Blesh-Compliant Enterprise Software.

Rebased :white_check_mark:

I think change's ok to be checked in, will check this in around tomorrow unless other suggestion's around.

Merged with ffe71df, :tada: @staltz


Google Analytic 》 Reporting API V4, when I run php error

I read this document: https://developers.google.com/analytics/devguides/reporting/core/v4/quickstart/web-php
when I run php error:
Fatal error: Uncaught exception 'GuzzleHttp\Exception\RequestException' with message 'cURL error 60: SSL certificate problem: unable to get local issuer certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)' in D:\wamp\www\test_google\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php on line 187
( ! ) GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: unable to get local issuer certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) in D:\wamp\www\test_google\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php on line 187

If the SSL certificates are not properly installed in your system, you may get this error:
cURL error 60: SSL certificate problem: unable to get local issuer certificate.
You can solve this issue as follows:

Download a file with the updated list of certificates from https://curl.haxx.se/ca/cacert.pem

Move the downloaded cacert.pem file to some safe location in your system

Update your php.ini file and configure the path to that file:
; Linux and macOS systems
curl.cainfo = "/path/to/cacert.pem"

; Windows systems
curl.cainfo = "C:\path\to\cacert.pem"

Alternatively, add the cacert.pem file to your application and then set the Guzzle Client to use it:

$client = new Google_Client();
$client->setHttpClient(new GuzzleHttp\Client([
    'verify' => '/path/to/cacert.pem',
]);

@bshaffer It not work, problems still exist

My environment is wampserver2.5, win32

php.ini is in apache/bin

Strange, suddenly there is a change! Nothing different to change.

Problem solved

My issue has been resolved by adding a backslash () before GuzzleHttp:
$client->setHttpClient(new \GuzzleHttp\Client(['verify' => false]));


There is over 100 branches, most of which are fully merged. Why not delete them?

Just a curious question from a guy who cleans up after his colleagues who forget to delete branches all the time ;)

@Giszmo thanks for the observation :)
Just did some more clean up and have it down to 30 now :)
We have a very distributed team in different time zones so we don't delete relatively new branches in case the creator still wants to work on it or to refer back to it. Some features are POCs and experimental in nature so we may not merge them for a long time and continue to refer back to it.

@Giszmo thanks for the observation :)
Just did some more clean up and have it down to 30 now :)
We have a very distributed team in different time zones so we don't delete relatively new branches in case the creator still wants to work on it or to refer back to it. Some features are POCs and experimental in nature so we may not merge them for a long time and continue to refer back to it.

Deleting branches on GitHub does not affect branches on the machine of the developer who introduced or worked on that branch locally. To get rid of upstream deleted branches they have to run
git remote prune origin

so if they want to revive the branch, they can still just git checkout featureX; git merge master # which is a fast forward and hack on using the upstream deleted but soon to be revived branch name.

Deleting branches on GitHub does not affect branches on the machine of the developer who introduced or worked on that branch locally. To get rid of upstream deleted branches they have to run
git remote prune origin

so if they want to revive the branch, they can still just git checkout featureX; git merge master # which is a fast forward and hack on using the upstream deleted but soon to be revived branch name.


Add Kevin Ortega as approver

I am the primary maintainer of the cloudfoundry/ibm-websphere-liberty-buildpack repo.
My contributions are documented in this PR (https://github.com/cloudfoundry/community/pull/716).
I update the repo every 4 weeks to coincide with each new release of WebSphere Liberty.
IBM will stop supporting this buildpack in Aug, 2024.  After Aug, 2024 I will no longer be contributing to this buildpack.

@cloudfoundry/toc given that this seemed like an oversight during initial working group creation, would you be open to fast-tracking this? I don't think the current java buildpack maintainers will have much to contribute to this request.

Related: https://github.com/cloudfoundry/community/issues/528


[Insight] Text files should end with a newline character - in LICENSE, line 21

in LICENSE, line 21

This file ends with no newline character. It won't render properly on a terminal, and it's considered a bad practice. Add a simple line feed as the last character to fix it.

IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Posted from SensioLabsInsight

Missed that one.


Add prefer-class-properties rule

One more rule! Also updated some docs for all the new rules.
cc/ @GoodForOneFare

The usual pedantry from me, but  👍.  The only blocker is a typo and the When Not To Use It section.


Version of packages in diffusion distillation

I checked requirement.txt under diffusion_distillation, it shows:
numpy
matplotlib
tensorflow
tensorflow_datasets
jax
jaxlib
pillow
flax
ml_collections
clu
But what are the version of these packages? I think there are some compatible problems among these packages. For example I get this error: AttributeError: module 'flax' has no attribute 'optim'
Could you specify the version of these packages? Thanks!

Hello, have you solved your problem? I also get this problem.


Register - Validation & Internal Server Errors

There are errors in the Registration part. Getting "500 - Error: Internal Server Error" and "422 - Validation Error"

Example data mismatch too

This also includes nickname/username validation for length and characters it contains.


Allow configuration of vector index name.

At the moment, it is not possible to configure SpringAI to use an existing index in the database.
This commit enables the user to provide the index name for auto configuration or builder usage.

Thanks for the contribution @meistermeier !
will review it shortly.

Btw @meistermeier , would you be interested to explore the possibility to add filter expression support for the Neo4j store?

https://docs.spring.io/spring-ai/reference/api/vectordbs.html#_metadata_filters
https://github.com/spring-projects/spring-ai/tree/main/spring-ai-core/src/main/java/org/springframework/ai/vectorstore/filter

I will have a look

I will have a look

Thanks! I'm closing this PR as merged, but created a related filter-expression issue here: https://github.com/spring-projects/spring-ai/issues/318


Missing Create(int ID)

currently there is no possibility to pass an ID to create an entry in the table. (as far as I know)
We have the usecase to receive data which is already indexed, so it would be great to use these indexes as the Entity ID, which saves us an additional field and a lot of additional code.
It would be great to have an extra function like:
ent.client.MyEntity.Create(id).
to pass the ID directly

Hey @sharpSteff,
You can provide your own IDs (using SetID) if the id field is configured in the schema. If it wasn't provided to the builder, the database will generate one for you - see the full docs for more info.
Closing, thanks!

@a8m Thanks for the quick response!
That’s exactly what I was looking for


xr.where() with numpy inputs produces error if global options changed

What happened?
https://github.com/pydata/xarray/pull/7229 seems to have introduced a possibility for errors if the set_options(keep_attrs=True) is used and then subsequently xr.where() is called using numpy inputs
What did you expect to happen?
Previous to xarray v2022.12.0, this did not occur. xr.where should have a check for non-Dataset inputs before trying to access attrs
Minimal Complete Verifiable Example
>>> import xarray as xr
>>> import numpy as np
>>> xr.set_options(keep_attrs=True)
<xarray.core.options.set_options object at 0x100cb8760>
>>> a = np.arange(10)
>>> b = np.arange(15,25)
>>> b = xr.where(a < 5, a, b)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/anissaz/opt/miniconda3/envs/geocat_comp_build/lib/python3.10/site-packages/xarray/core/computation.py", line 1887, in where
    result.attrs = getattr(x, "attrs", {})
AttributeError: 'numpy.ndarray' object has no attribute 'attrs'

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
No response
Anything else we need to know?
 We could raise a nicer error here.
But I'm not sure how it worked earlier. Des apply_ufunc return numpy output for all numpy inputs?

@dcherian That's a fair point. The function we wrote is supposed to support numpy and xarray input, and previously it was easier to use xr.where() for both cases instead of checking for input type repeatedly.
I just walked through my debugger with one of my failing tests and yes, it does appear that apply_ufunc is returning numpy output for all numpy input.

Great, thank you! We're actually planning to removing the set_options that triggered the edge case here in geocat-comp, but I still think the check in #7364 is useful and might save someone else (possibly me again 😆 ) in the future some trouble.


error on building

hello,
when I build the component react-native-animateable-text I have an error which is returned to me knowing that I installed Reanimated 1 and 2 and also react-native-redash with yarn.
Here is the error:
Android Bundling failed 123ms
error: node_modules/react-native-reanimated/src/index.ts: /Users/youssef/applis-react/react-native/test-animated/node_modules/react-native-reanimated/src/index.ts: Export namespace should be first transformed by @babel/plugin-proposal-export-namespace-from.
5 | export * from './reanimated1';
6 | export * from './reanimated2';

7 | export * as default from './Animated';
|
apparently webpack is used on the component but I don't know webpack how can I disable the fact that Animated is by default?

Cordially.
error.pdf

Install @babel/plugin-proposal-export-namespace-from and add @babel/plugin-proposal-export-namespace-from to your babel config


[OSF-8519] Test failure test_get_preprint_count

Purpose
The test test_get_preprint_count needs Keen which doesn't allow same-day dates to be queried, you can't for example ask them how many users visited the site on Sept 25th 2018 if Sept 25th 2018 hasn't happen or isn't over yet. This means we have to query for dates in the past. On top of that since we aren't querying for a specific time all out dates are rounded to midnight so dates at 11 round to the next day causing an error, this PR fixes that.
Changes
Pushes date back another hour so we avoid the rounding error.
Side effects
None that I know of.
Ticket
https://openscience.atlassian.net/browse/OSF-8519

I know these are mostly still relative dates, but I can't think of better ones. I still don't know definitively what causes the failure.


Added aaryachopkar.json

My First Contribution to EddieHub Community
Changes proposed

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[X] I have updated the documentation accordingly.
[X] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers
Thank you in advance!

All mentioned Changed were made.
Thank you!

Sorry for the typo
Thanks for your patience and help!


invoke chrome with "exec"

I think this should solve #2. I've seen a similar issue with another docker image. The issue is that not every implementation of sh uses exec by default and if it is not used, then signals do not get handled properly.
There might be an alternative solution that avoids the sh -c in this line, but I'm not a bash expert enough to know it by heart.

I'm going to close this. Feel free to open a new issue if you have any other issues!


HTTPS and offline cache working with LittleProxy

It's derived from the OWASP Zed Attack Proxy Project, which is licensed
under the Apache License, Version 2.0. The certificate authority is
created lazily with Bouncy Castle. The key store type is PKCS12, which
has to be implemented by every vendor. The server certificates won't be
cached, but the connection is already cached. It lacks upstream
certificate validation(!) and a proper exception handling.

I like this. It looks like it's an implementation of previous PR #171, but implemented with Bouncy Castle instead of the internal sun classes. A couple questions:

Generally speaking, how long does it take to generate a certificate? I'm wondering if maybe we should cache them for a short period of time.
Should we make the bouncycastle dependency optional in the POM, so only clients that want to use this functionality get the bouncy castle jars? (I think the idea is to eventually move this to a separate 'extras' project.)

Generally speaking, how long does it take to generate a certificate?
I'm wondering if maybe we should cache them for a short period of time.

With my Laptop, Core 2 Duo, 2.4GHz, Linux: regulary 50 - 150ms
9339  2015-01-24 09:13:23,402 INFO  [MoCuishle-ClientToProxyWorker-0]
mitm.McSslEngineSource - Impersonated github.com in 618ms
21002  2015-01-24 09:13:25,065 INFO  [MoCuishle-ClientToProxyWorker-1]
mitm.McSslEngineSource - Impersonated collector.githubapp.com in 453ms
32898  2015-01-24 09:13:36,961 INFO  [MoCuishle-ClientToProxyWorker-6]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
143ms
33213  2015-01-24 09:13:37,276 INFO  [MoCuishle-ClientToProxyWorker-7]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
200ms
44493  2015-01-24 09:13:48,556 INFO  [MoCuishle-ClientToProxyWorker-5]
mitm.McSslEngineSource - Impersonated github.com in 83ms
45493  2015-01-24 09:13:49,556 INFO  [MoCuishle-ClientToProxyWorker-6]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
333ms
45638  2015-01-24 09:13:49,701 INFO  [MoCuishle-ClientToProxyWorker-1]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
460ms
45766  2015-01-24 09:13:49,829 INFO  [MoCuishle-ClientToProxyWorker-7]
mitm.McSslEngineSource - Impersonated avatars2.githubusercontent.com in
310ms
45784  2015-01-24 09:13:49,847 INFO  [MoCuishle-ClientToProxyWorker-2]
mitm.McSslEngineSource - Impersonated avatars2.githubusercontent.com in
328ms
46124  2015-01-24 09:13:50,187 INFO  [MoCuishle-ClientToProxyWorker-0]
mitm.McSslEngineSource - Impersonated cloud.githubusercontent.com in 157ms
57942  2015-01-24 09:14:02,005 INFO  [MoCuishle-ClientToProxyWorker-3]
mitm.McSslEngineSource - Impersonated avatars1.githubusercontent.com in
279ms
57988  2015-01-24 09:14:02,051 INFO  [MoCuishle-ClientToProxyWorker-2]
mitm.McSslEngineSource - Impersonated avatars2.githubusercontent.com in
379ms
58042  2015-01-24 09:14:02,105 INFO  [MoCuishle-ClientToProxyWorker-0]
mitm.McSslEngineSource - Impersonated camo.githubusercontent.com in 349ms
58043  2015-01-24 09:14:02,106 INFO  [MoCuishle-ClientToProxyWorker-6]
mitm.McSslEngineSource - Impersonated avatars1.githubusercontent.com in
403ms
58051  2015-01-24 09:14:02,114 INFO  [MoCuishle-ClientToProxyWorker-1]
mitm.McSslEngineSource - Impersonated avatars0.githubusercontent.com in
361ms
58167  2015-01-24 09:14:02,230 INFO  [MoCuishle-ClientToProxyWorker-4]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
525ms
58350  2015-01-24 09:14:02,413 INFO  [MoCuishle-ClientToProxyWorker-7]
mitm.McSslEngineSource - Impersonated avatars3.githubusercontent.com in
682ms
65915  2015-01-24 09:14:09,978 INFO  [MoCuishle-ClientToProxyWorker-4]
mitm.McSslEngineSource - Impersonated camo.githubusercontent.com in 64ms
69002  2015-01-24 09:14:13,065 INFO  [MoCuishle-ClientToProxyWorker-3]
mitm.McSslEngineSource - Impersonated avatars2.githubusercontent.com in 76ms
69042  2015-01-24 09:14:13,105 INFO  [MoCuishle-ClientToProxyWorker-4]
mitm.McSslEngineSource - Impersonated avatars2.githubusercontent.com in
123ms
71423  2015-01-24 09:14:15,486 INFO  [MoCuishle-ClientToProxyWorker-4]
mitm.McSslEngineSource - Impersonated avatars0.githubusercontent.com in 94ms
71438  2015-01-24 09:14:15,501 INFO  [MoCuishle-ClientToProxyWorker-3]
mitm.McSslEngineSource - Impersonated avatars0.githubusercontent.com in
109ms
It benefits from connection caching. High load to one site - less
impersonations. It feels good with my single user caching proxy, but I
will give it a try with a memory cache, too.

Should we make the bouncycastle dependency optional in the POM, ...
Yes, but this depends the place for it. It's a draft. I've factored out
an Authority class for modular use now, but this is obsolete if it's an
example only.

I really think this additionally caching is obsolete. It feels not better for me. Please double check this in your environments.

I really think this additionally caching is obsolete. It feels not better for me. Please double check this in your environments.

Despite this, I see you did indeed add caching :) I like the guava cache implementation and I think it's a worthwhile addition. I did add a couple in-line comments for you to review.
I think this is a GREAT PR, thank you for putting it together! It's going to be a big help for browsermob-proxy once our littleproxy integration is complete.

... I did add a
couple in-line comments for you to review.
Sorry, what is that - I mean where is that?

@ganskef -- it looks like the bcprov-jdk16 artifact is pretty out-of-date (Feb 2011) and not actively maintained. bcprov-jdk15on works with Java 1.5+ and is actively maintained (latest release Jul 2014). Would it be possible to update this PR to work with the jdk15on versions of bouncy castle?

Also, could you add some unit tests? That would have the secondary benefit of showing people how to use the new functionality.

Thanks @ganskef! I agree with @jekh that a quick unit test would be super helpful. You mind adding that to the PR?

Hello Myle,
yes, I'm working on it. Its not so easy. I need a SSL enabled server and
client with proper certificate handling. I'm confused about the tests in
LittleProxy and its dependencies.
I'm thinking about more composition than inheritance. I plan tests for
this directly based on Netty instead of other frameworks.
Regards Frank
Am 01.03.2015 um 07:47 schrieb myleshorton:

Thanks @ganskef https://github.com/ganskef! I agree with @jekh
https://github.com/jekh that a quick unit test would be super helpful.
You mind adding that to the PR?
—
Reply to this email directly or view it on GitHub
https://github.com/adamfisk/LittleProxy/pull/174#issuecomment-76584468.

Hi @ganskef -- I see the MITM functionality has been removed from this PR, but where did it go? I'm very excited about that and I would love to help you test it :)
Regarding the rest of the PR, I wanted to ask: what functionality is it implementing? I see it is now titled "HTTPS and offline cache" (instead of the previous title "HTTPS impersonation"), but what exactly is the offline cache doing? What is the use case you have in mind?
Since the purpose of this PR has completely changed, could you at least squash the commits related to the MITM impersonation, since they are not part of this change anymore? The extra noise makes understanding the offline caching change a bit confusing.
For future reference, if you want to implement a different feature, it's usually easiest and cleanest to just create a new PR and close the old one (if you no longer want to merge it).

has been removed from this PR, but where did it go? I'm very excited
about that and I would love to help you test it :)

Sorry for confusion. The new location is
https://github.com/ganskef/LittleProxy-mitm
I would love it to see it in LittleProxy, but it seems not to be
recommended, see #173. It could be moved again, of course.
Testing LittleProxy-mitm is on going. I will push something later this
evening.

Regarding the rest of the PR, I wanted to ask: what functionality is it

I've built a proxy on top of LittleProxy for my daily use. It's a lib,
an executable Jar, a Mozilla Firefox Add-on and an Android App. The
Add-on works with Linux, OS X, Windows and Android, but there you need
the App, since it's Dalvik VM. It provides offline caching for HTTP and
freshly HTTPS (fails with Android at the moment).
To build this proxy, to make it working, I need this little
modifications here in a LittleProxy release, please.
I'm considering to publish my project, but I am unsure. Its a kind of
responsibility... Its not hurry, I think. You seems to bee the only one
who missed it. Adam Fisk points me to a forum. Who is the maintainer? Is
there a list or something I've missed?
Regards Frank

It sounds like you're implementing some sort of response caching for when the proxy cannot connect to the remote server, is that right? Doesn't the existing HttpFilters infrastructure support this? Have you tried implementing the proxyToClientResponse() method and returning the cached page there if the proxy cannot connect to the server? I guess I still don't understand what the use case is currently, or what in LittleProxy is proving to be a limitation. Some example use cases and/or unit tests would definitely be helpful.

Hello Jason,
this PR targets the following issues:

Chunk aggregation and and content expansion is disabled when
detecting a CONNECT. This disables it for MITM use. (see PR #175)

A handshake with the proxy initiates always a connection to the
server. Therefore MITM while offline is impossible. I've written a test
now. What do you think?

A MitmManager and EngineSource implements a full Certificate
Authority to sign server certificates on the fly. It can be imported in
the browser as a trusted CA. It is moved caused by #173, but it could
moved back again. I have it in my daily use and it's working fine, but
this proxy depends on 1 and 2, too.

What should I do? I'm helpless. Please, give me some suggestions.
Should I close this request and create new PRs more dedicated?
Should I delete the forked LittleProxy to get a clean master?
Should I create a branch for each feature like I've done in PR #175?
Regards Frank

@jekh sorry, I've forgotten an issue:

An offline proxy needs an additional parameter host name in MitmManager#clientSslEngineFor. The host name is available in the proxy to client connection, without a server connection. The MITM server certificate will be allways created with the host name instead of the original given common name or the subject alternative names. The upstream certificate should be available even though.

nice work @ganskef . I think your https://github.com/ganskef/LittleProxy-mitm repo should be atleast mentioned in the readme of this repo. What do you think @jekh?

I will create a separate branch for this, since I've started to mix incidents in the master. So I'm going to close this pull request.


Add a possibility to specify expected IR lengths for JTAG capabilities of debug probes

See https://github.com/probe-rs/probe-rs/pull/1462#issuecomment-1642911723

@Yatekii, how do you think this should be done? One idea I have is that something can be added to the target.yaml file that describes the scan chain. This could also be a solution for https://github.com/probe-rs/probe-rs/issues/1683 where the yaml file could contain the index of the wanted DAP.
Both could be optional, where if not provided we fall back to the default behavior as it is today.

Yeah, I think the target specifications are the right place :) Is this a fixed value? We already have special values for denoting the DAP on some multidrop chips (rp2040) or unconventionaly enumerated DAPs :)
So this should fit right in :)

Is this a fixed value?

Yep! Its fixed in the HW, but not by the spec. Different vendors can implement different ir lengths.
I found a scanchain description as part of the System Description File which looks like it would do exactly the trick.
Converting this to yaml would look like:
scanchain:
    - !Dap
        name: core0
        type: Cortex-M0+
        ir_len: 4
        protocol:
        - jtag
        - swd
    - !Device
        name: ICEPICK
        type: Other
        ir_len: 6

Following that format means I think we could try to automatically parse and populate this from target-gen if it exists in the pack. Then, if the target file has a scanchain specified, we could use that to specify the ir_lengths before connect.

Looking great! I am not sure we should use terms such as Cortex-M0+ rather than thumbv6 because other stuff uses it that way, but other than that its nice!

I have the scanchain added to the target now.
Do you have any recommendations on how to connect that to configure_jtag?
Is it through session? I basically need something that knows about the interface and target.

I would give it the interface and target as separate params directly :)


Allow custom Fancy Zones to exceed the bounds of the screen

Description of the new feature / enhancement
Allow custom Fancy Zones to exceed the bounds of the screen
Scenario when this would be used?
When you only require a % of a window to be on screen and wish to create snap zones to facilitate this
Supporting information
No response

What apps would you want to be outside the boundaries of your window?

I find so many apps display data that is unnescisarry and have ui that cannot be configured or rearranged so to just move a window or app partially off screen allows for more useful screen real estate. I think the use case would be so general to specify the apps would take too long.

Zones could also be overlappable

@DeviantNature in a canvas based layout, overlapping is allowed. Grid based are a single screen.

This looks like a duplicate of #296 :)


drivers: nxp_enet: Performance is very poor

Observations:

Interestingly, enabling debug optimizations or speed optimizations will fix the issue, again probably due to a different image causing different prefetch pattern in flexspi?
relocating net/ip stack to itcm also improves performance significantly

ideas:

implement zero copy TX/RX
move net_bufs to DTCM
rework solution to take advantage of the multiple buffer descriptor rings on some platforms, like RT11XX
some way to choose how code sections are linked in relation to each other so that we can improve flexspi prefetch / cache hits

+1 for this.
We use ENET1G for a demo and enabled speed optimization as well as relocating to itcm but the speed is still very poor than expected.


Privacy Policy page addition to the website

Is your feature request related to a problem? Please describe.
It is helpful when we are aware of the privacy policy terms of a website therefore it is always good to add this section
Describe the solution you'd like
I would like to add link your website to privacy policy page for your website, this  enhances user experience. I would like to add this section in the footer section
Additional context

@ANSHIKA-26 I believe that there is no such issue raised as there, as I have checked for them
so please assign me this issue under the label of hacktoberfest and GSSOC extd


Updates

Updated ts-loader, sass-loader, and devDependencies.

The major sass-loader update breaks a few tests, so I need to look into what changed.

So far, it appears the options structure has changed (only 5 tests are affected):
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
ValidationError: Invalid options object. Sass Loader has been initialized using an options object that does not match the API schema.

More specifically, sass-loader option prependData (used by scss property) seems to be what changed.

Now only the SCSS Data Function test is failing.

There is a breaking change that affects the API because additionalData functions should return the entire content of the file (this would explain the name change as the function can insert anywhere now) instead of the code to prepend.
So this:
scss: () => "body{color: rgb(255, 0, 0)}"

becomes this:
scss: (content) => content + "body{color: rgb(255, 0, 0)}"

Now I wonder if I might as well solve #527 too: it was postponed for the next major version, but it's unlikely to be a small change.

Last time I looked into it, the main issue was that node-sass doesn't support @use, so I have to use sass package (and fibers to make it faster).
So let's see if it is compatible with the test fixtures first.

After all, I'm not going to support @use because @import still works fine in both compilers, and it would require switching to a slower compiler: https://github.com/wildpeaks/package-webpack-configs/issues/527#issuecomment-661995202
I do hope node-sass will add the feature eventually as @use is a nicer syntax, but it's not worth changing compiler just for that.


Provide reasonable defaults for low_flap_threshold, high_flap_threshold

The docs on low_flap_threshold, high_flap_threshold would be more helpful if they mentioned reasonable defaults.  Perhaps something like:
The flap detection low threshold (% state change) for the check. Sensu uses the same flap detection algorithm as Nagios.  Events that were tagged as flapping will be untagged once the % of the last 21 occurrences drops below this percentage.  Typical values are in the 10%-30% range.
``

Oops, wrong repo.


There are new MediaFeedType in PlayOff

Hi,
new ones started showing up MediaFeedType: US NATIONAL and CA NATIONAL.
In default: US NATIONAL
National = "US NATIONAL", in nhlStatsApi.ts

I'm confused why you want to change National to "US NATIONAL". Won't some people want "CA NATIONAL"? It's been a while since I've been in the code, I thought this was mostly just for helping to know which feed to pick. If this is breaking some functionality for you then it would help to explain what broke.

Everything works fine, there are no problems, only when you make a -passive method, it does not start because it cannot find the source.

I pushed a change that hopefully handles it. Let me know if it doesn't work for you.


Command runs successfully, but returns an error message

OrientDB Version: 3.1.1
Java Version: openjdk 14.0.1 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (build 14.0.1+7)
Eclipse OpenJ9 VM AdoptOpenJDK (build openj9-0.20.0, JRE 14 Linux amd64-64-Bit Compressed References 20200416_44 (JIT enabled, AOT enabled)
OpenJ9   - 05fa2d361
OMR      - d4365f371
JCL      - 5757187cae based on jdk-14.0.1+7)
OS: Ubuntu 20.04 Linux 5.4.0-42-generic x86_64 GNU/Linux
Expected behavior
Return success message when changing property restrictions
Actual behavior
returns an error message: 'Command failed.'
Steps to reproduce

create class Student
create property Student.name string
alter property  Student.name max 60 (or any other command to change ownership restrictions)

Resolved on the latest 3.1.x. Please upgrade.


Make the mutex private in the structure

The mutex's methods are exposed - the client has public methods Lock and Unlock, which is kind of misleading - they're present in the autocomplete. It would be great to simply name the field like mtx (lowercase) to make it private.
https://github.com/plutov/paypal/blob/1a2c109908d6b7b98541396f175687c2d08ee263/types.go#L396

Is this still open ? I'd like to contribute?

Hi , @bartek1912  can this be closed, since this commit was approved and addresses this issue?


Add a process fidelity utility function

This is for issue #2763

What are U and V? time-evolution operators that are nearly unitary? I skimmed the linked preprint and I don't think this is exactly what we'd want as the main process_fidelity function. It should be defined on two CPTP maps aka quantum channels aka something that turns one density matrix into another.
The function from qiskit is probably a good starting point: https://qiskit.org/documentation/stubs/qiskit.quantum_info.process_fidelity.html#qiskit.quantum_info.process_fidelity. Of course, this would require introducing a superoperator representation for processes. The different representations are described here, for example https://arxiv.org/abs/1111.6950

I agree with @mpharrigan. Any utility for process fidelity needs to be explicit about what representation of a CPTP map it accepts. Also, a few common maps are already implemented in cirq. We should use one representation consistently throughout the library and if you find that the present representation is insufficient we should generalize it appropriately rather than adding another.

Hello,
Sorry for the delay. I have now a new user name and it took me a while to understand the paper you gave me (sorry and thank you for the help). I would suggest closing this PR and moving the review to:
https://github.com/quantumlib/Cirq/pull/3226

I would suggest closing this PR and moving the review to:
#3226

Sounds good - closing this one.


Not Getting It

Hi, hope all is well? I installed Django-easy-maps, and I'm confused on how to use it.
I created a view and a template for it, but when I visit the page, it's always bringing a blank page. What I'm I missing?
Template:
% load easy_maps_tags %}

{# {% easy_map "Russia, Ekaterinburg, Mira 32" 300 400 %} #}

{% easy_map address 200 200 5 using 'easy_maps/map.html' %}
View:
def geo(request):
return render_to_response('geomap.html')
I'm thinking its supposed to bring a field where I can iput where I want to locate. Or is that not so? Please kindly help a niib out.
Thanks!

Bitbucket: https://bitbucket.org/kmike/django-easy-maps/issue/6
Originally reported by: skizzy
Originally created at: 2012-02-14T13:09:07.410

Hi skizzy,
Doesn't
{{{

{% load easy_maps_tags %}
{% easy_map "Russia, Ekaterinburg, Mira 32" 300 400 %}

}}}
work?
easy_map tag just accepts string with the address and this address can come from the model field or be hardcoded in template.

Original comment by: Mikhail Korobov

What is the result html of the template rendering?

Original comment by: Mikhail Korobov

One more thing, I'm developing on windows machine through localhost:8000. :)

Original comment by: skizzy

Thanks for the reply. Yeah, it's not working. Should I create a model or what? Sorry, I didn't get you. Hope to hear from you soon. Take care.

Original comment by: skizzy

Just A blank Page! Nothing more, nothing less. :)

Original comment by: skizzy

Just a white blank Page! Nothing more, nothing less. :)

Original comment by: skizzy

Can you please post the result html source code here?

Original comment by: Mikhail Korobov

Original comment by: skizzy

Can you please post the HTML of this blank page? Use 'view source' or 'save as' in your browser. If the html looks good then check the javascript errors in browser console.

Original comment by: Mikhail Korobov

Template:

{% load easy_maps_tags %}
{% easy_map "Russia, Ekaterinburg, Mira 32" 300 400 %}
{% easy_map address 200 200 5 using 'easy_maps/map.html' %}

Views:
def geomap(request):
return render_to_response('geomap.html')
When I visit, localhost:8000/geomap , It will only load a blank page! Just white blank page. That's all.

Original comment by: skizzy

You mean I should delete the address instance through my admin dashboard? I've set the Google map API key.  What other solution do you know about? Thanks big bro. You rock!

Original comment by: Anonymous

What do you think is wrong? :)

Original comment by: skizzy

Geocoder wasn't able to get the coordinates for some reason. Try deleting the Address instance in your admin and trying again (and maybe setting the EASY_MAPS_GOOGLE_KEY option).
Unfortunately geocoding error debugging is not supported well in django-easy-maps now (it only sets a 'geocode_error' flag on Address instance, the reason gets lost), patches that will improve this are welcome.

Original comment by: Mikhail Korobov

Oops, I missed your updates. Yes, I mean deleting the address instance through admin dashboard. Is the problem resolved?

Original comment by: Mikhail Korobov

Its me skizzy. I'm commenting through mobile.

Original comment by: Anonymous

I have the same problem with the same code, {{ lat }} and {{ long }} return nothing.
I don't have an address instance in the admin dashboard ( if I understand you well )

Original comment by: Anonymous

Yes, it returns multiple solutions, and geocode raises ValueError.
For me worked changing:
{{{
#!python
self.computed_address, (self.latitude, self.longitude,) = g.geocode(address)
}}}
to
{{{
#!python
self.computed_address, (self.latitude, self.longitude,) = g.geocode(address, exactly_one=False)[0]
}}}
in models.py

Original comment by: Dmytro Buts

I have checked geopy, they recommend using resource="map/geo" instead of "map".
But Geopy is working anyway.
I got it:
"Russia, Ekaterinburg, Mira 32" as 2 solution according to geopy. May be I should render this kind of error on my template.
Plus I didn't wrote the address instance in the admin dashboard.
( Love this app by the way )

Original comment by: Anonymous


Added ltr tests

node-semvar ltr tests here https://github.com/npm/node-semver/blob/master/test/ltr.js
#1 ltr tests, I've kept the comments for each pair from the node version of this one, I didn't on the gtr but can add them in if you like.
Would you prefer loops? I did initially add it as a loop but when you run the tests it can be hard to see where an error is actually coming from so I kept it verbose.

Thanks again @krishandley, I didn't notice initially but the args in the tests in node-semver are actually reversed, I flipped them back again here: https://github.com/librariesio/semantic_range/commit/c8a18330754cab18a34c55922efae54d1882e048
Can you flip the args on all of them to put version first and range second?
I prefer each line to loops as well, much easier to debug!
Comments are handy but we can always refer back to the node-semver code if something isn't clear

Swapped and squashed

:+1:


Log errors during tests

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9701/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9704/
Test PASSed.

LGTM

alluxio-bot, merge this please


Questioin about set function

I recently upgraded from version 1.9.8 to version 1.9.35 - thus causing some issues that I am trying to work through.  In previous versions you could initialize fields with formatting already set in the input for example <input value="$100.00" /> could be run through as long as the field allowed dollar signs.
But in the new code the set function is not stripping out the preset dollar sign before checking the validity of the value - causing a $.error on line 1139.
I noticed that the autostrip was being called just above but I had to comment the testValue !== $this.attr('value') check to make it work...
Line 1130 - 1133:
if (/*testValue !== $this.attr('value') &&*/ $this.prop('tagName').toLowerCase() === 'input' && settings.runOnce === false) {
    value = (settings.nBracket !== null) ? negativeBracket($this.val(), settings) : value;
    value = autoStrip(value, settings);
}

Is this check really necessary?

The option "aForm" controls formatting of default values - if you set  "aForm: false" it should accomplish what you require.
I am out of the office for a week but will look at this in detail when i return.
--------- Original Message --------- Subject: [autoNumeric] Questioin about set function (#131)
From: "alberr"<EMAIL_ADDRESS>Date: 4/29/15 9:09 am
To: "BobKnothe/autoNumeric"<EMAIL_ADDRESS>I recently upgraded from version 1.9.8 to version 1.9.35 - thus causing some issues that I am trying to work through. In previous versions you could initialize fields with formatting already set in the input for example  could be run through as long as the field allowed dollar signs.
But in the new code the set function is not stripping out the preset dollar sign before checking the validity of the value - causing a $.error on line 1139.
I noticed that the autostrip was being called just above but I had to comment the testValue !== $this.attr('value') check to make it work...
Line 1130 - 1133:
if (/testValue !== $this.attr('value') &&/ $this.prop('tagName').toLowerCase() === 'input' && settings.runOnce === false) {
value = (settings.nBracket !== null) ? negativeBracket($this.val(), settings) : value;
value = autoStrip(value, settings);
}
Is this check really necessary?
Reply to this email directly or view it on GitHub.


ZSH autocompletion URL is a 404

https://cdn.rawgit.com/pimterry/notes/v0.2.0/notes._notes spits out a 404. This breaks the line
curl https://cdn.rawgit.com/pimterry/notes/v0.2.0/notes._notes > /usr/share/zsh/site-functions/_notes

Good catch, thanks, now fixed: https://github.com/pimterry/notes/commit/8ebe0aefdfdfc6057b7c16a7a871ab8d9dbd85ca


Empty array element parsing

I found out that parsing the string "[a,,b]" produces an array with 2 elements, while a browser interprets it as a 3-element array, where the second is undefined.
I don't know if you will find this useful, but i wrote a patch to parse the empty second array element as an empty string.

Bitbucket: https://bitbucket.org/zserge/jsmn/issue/41
Originally reported by: Anonymous
Originally created at: 2014-12-02T16:00:40.825

Parsing such array as 3 elements is definitely incorrect, in browser as well:
JSON.parse('[1,,3]')
SyntaxError: JSON.parse: unexpected character at line 1 column 4 of the JSON data

The fact that it works in strict mode is a bug.

Related to #52


WIP: more complete CJS <-> ES interop

Via rollup/rollup#866.  I think our current approach is incomplete but I'm not sure what the best one is. Stream of consciousness ahead as I try to get my thoughts straight.
There are three situations this plugin needs to handle: ES imports CJS, CJS imports CJS, CJS imports ES.
Right now there's interop fudging at export time and at require time. It causes problems when CJS files require other CJS files that were generated by a transpiler, as is the case in rollup/rollup#866 – react-apollo/index.js does things like this:
var ApolloProvider_1 = require('./ApolloProvider');
exports.ApolloProvider = ApolloProvider_1.default;

This plugin borks things up because it massages the exports of ApolloProvider on the assumption that the importer will be an ES module, not another CJS module.
Taking each situation in turn:
ES imports CJS
import foo from './commonjs/foo.js';
import { bar } from './commonjs/bar.js';

This case is relatively straightforward – foo.js just exports the value of module.exports (or module.exports.default if it's a transpiler-generated module – tbh we should probably only do that if exports.__esModule === true, because that's how transpilers mark their territory). bar.js has a named bar export in addition (either automatically, because the plugin detects an exports.bar = whatever' assignment, or manually because we've used options.namedExports.
CJS imports CJS
const x = require( './commonjs/foo.js' );

It seems fair to say that in this situation, no export massaging should occur – x should simply be the value of module.exports in foo.js. That's not what currently happens, meaning that when a CommonJS module expects to find a .default property on a required module, things blow up.
Unfortunately, there's no (robust, reliable) way for this plugin transformer to know whether its consumer will be ES or CJS (or both!).
CJS imports ES
const y = require( './es/bar.js' );

Because of this requirement, all require statements result in namespace imports rather than default imports – since we don't know if bar.js exports default or not, we have to import a namespace and futz around with it. This is really bad news, because it results in more code and complexity and prevents tree-shaking.

The approach in https://github.com/rollup/rollup-plugin-commonjs/commit/61c6e00e61134990ce4c92553affc2a8e562056e fixes rollup/rollup#866 but in a horrible way – by adding a .default property to the .default property, so that an importer of the transformed module will find what it expects whether it's ES or CJS. (It doesn't currently hang any named properties off the default export, so isn't a complete solution in any case.)
There has to be a better way. I'm wondering about something involving virtual 'proxy' modules that do the interop stuff – i.e. an ES module imports the transformed module directly, whereas a CJS module imports the proxy. Or vice versa! Though my thinking hasn't progressed far beyond that right now.
If anyone can see anything obvious I'm missing let me know... you might save me from being driven insane by this stuff.

Closing in favour of #92


Bump Apache Arrow 2.0.0

Reporter: Fokko Driesprong / @Fokko
Assignee: Fokko Driesprong / @Fokko
Note: This issue was originally created as PARQUET-1942. Please see the migration documentation for further details.

Gabor Szadovszky / @gszadovszky:
@Fokko, do you want to work on it for 1.12.0? We would like to start the release process for 1.12.0 soon.


Make image views a separate type from images

Mentioned in https://github.com/vulkano-rs/vulkano/issues/1392#issuecomment-653622619, https://github.com/vulkano-rs/vulkano/pull/1444#issue-529094324, https://github.com/vulkano-rs/vulkano/pull/1444#discussion_r572160885 and https://github.com/vulkano-rs/vulkano/pull/1449#issuecomment-740042773. I propose making a separate ImageView type, that is created from an image (presumably with an Arc, as one image can have many views). Images would no longer contain image views inside them, but instead the user would have to create a view, if their use case requires it.
This would lift some restrictions on particular use cases. Vulkano currently creates views for every image, whether a view is needed or not, and views bring limitations with them. In particular, certain image usage flags are required when creating a view, but not every image needs such usage in practice (e.g. swapchain images that are only transferred onto).
The new type would be a safe wrapper around the current UnsafeImageView, and most likely the safety checks currently in the latter should be in this new type, and implemented in a better way than with asserts. This follows the Vulkano practice that the low-level "unsafe" types do not check for correctness, but leave this to higher-level wrappers. ImageViewAccess would naturally no longer be implemented on the images, but rather on this new type, although it may no longer be necessary if there is only one single view type.

I like this idea :+1:


KAFKA-15219: KRaft support for DelegationTokens

This PR includes KRaft Metadata support for DelelegationTokens, updated tests for DelegationTokens to run in Zk and KRaft mode, and a bump of the metadata version specifically for DelelegationTokens.

I just took a quick look and I can see multiple protocol change, quite a big refactor to make it working with KRaft and it feels like we should write a KIP about this. What do you think?

I just took a quick look and I can see multiple protocol change, quite a big refactor to make it working with KRaft and it feels like we should write a KIP about this. What do you think?

There isn't an API change for using the the Kafka client API so customers shouldn't need to change how they use delegation tokens so we are covered there. The conversion of using Zk to using metadata should be covered with KIP-833. Updating the Inter Broker Protocol with new records is allowed with a bump in the IBP version which is included in the PR. I bumped it from IBP_3_6_IV0 to IBP_3_6_IV1 similar to what I did for Scram. So, I think we are covered from any KIP requirements.
@cmccabe  can you chime in here?

@pprovenzano Thanks for the PR. left few comments
can we also update delegation token docs if required (like any configs for controller nodes etc..) https://github.com/apache/kafka/blob/trunk/docs/security.html#L1178

I'm going to do that with a separate PR

I think this starts to look good. There are some parts I haven't reviewed yet, I'll try to get them in the next few days.

Thank you for the review comments. I think I have addressed all the ones you have given.

Merged to 3.6

Hey folks
We have kafka.api.DelegationTokenEndToEndAuthorizationWithOwnerTest failing in a flaky manner since this change was merged. I deduced this based on the sudden spike in failures starting on the day this was merged. see: https://ge.apache.org/scans/tests?search.relativeStartTime=P28D&search.rootProjectNames=kafka&search.tags=trunk&search.timeZoneId=Europe/Berlin&tests.container=kafka.api.DelegationTokenEndToEndAuthorizationWithOwnerTest

@pprovenzano can you please take a look and fix the flakiness if it is related to this change.
(cc: @satishd , RM for 3.6)

DelegationTokenEndToEndAuthorizationWithOwnerTest

I created https://issues.apache.org/jira/browse/KAFKA-15411 and will start looking at it today.