Fix m7core

@bcostm please test

But in this changelist also i see M7 and M7F defined with SoftFP only and not hardfp?

@sandeepach it should be hardware floating-point using the soft-float ABI.
@bcostm Looking at this, is F746 double or single? In armcc for M7F core,  any m7 is considered as single. Now here in gcc as double :(
elif target.core == "Cortex-M7F":
            cpu = "Cortex-M7.fp.sp"
```

STM F7 has a single fpu
but in general a Cortex M7 mcu can have a double fpu - this feature is optional

@ohagendorf A change here for gcc self.cpu.append("-mfpu=fpv5-d16") should be self.cpu.append("-mfpu=fpv5-sp-d16"). At least for now, single precision only, same as armcc.

Atmel SAMS70/E70/V70/V71 have double. Better not to have something fixed in case of.
On 14 December 2015 09:42:25 CET, Olaf Hagendorf<EMAIL_ADDRESS>wrote:

STM F7 has a single fpu
but in general a Cortex M7 mcu can have a double fpu - this feature is
optional

Reply to this email directly or view it on GitHub:
https://github.com/mbedmicro/mbed/pull/1467#issuecomment-164378995

--
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.

Atmel SAMS70/E70/V70/V71 have double. Better not to have something fixed in case of.

Yes, defintely. But will happen separately to this changeset. We should add a new issue for this.

I tried with the version 111 of mbed with GNU GCC compiler.
I could not get a simple GPIO write to work with that. Is this somehow related to this changelist?

I was however able to get it working with the mbed-src. Not with the MBED Library.

I added new label RTOS_M4_M7 as they share the same files currently. Here are test results:
//GCC ARM
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result  | Target       | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK      | DISCO_F746NG | GCC_ARM   | DTCT_1      | Simple detect test                    |        0.51        |       10      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | EXAMPLE_1   | /dev/null                             |        3.44        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_10     | Hello World                           |        0.37        |       5       |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_11     | Ticker Int                            |       11.36        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_12     | C++                                   |        1.37        |       10      |  1/1  |
| FAIL    | DISCO_F746NG | GCC_ARM   | MBED_16     | RTC                                   |        6.57        |       20      |  0/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_2      | stdio                                 |        0.78        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_23     | Ticker Int us                         |       11.39        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_24     | Timeout Int us                        |        11.4        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_25     | Time us                               |       11.36        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_26     | Integer constant division             |        1.38        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_34     | Ticker Two callbacks                  |       11.37        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_37     | Serial NC RX                          |        10.9        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_38     | Serial NC TX                          |       15.39        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_A1     | Basic                                 |        1.34        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_A21    | Call function before main (mbed_main) |        1.41        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_A9     | Serial Echo at 115200                 |        6.51        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | MBED_BUSOUT | BusOut                                |        2.26        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_1      | Basic thread                          |       11.37        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_2      | Mutex resource lock                   |       11.35        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_3      | Semaphore resource lock               |        8.38        |       20      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_4      | Signals messaging                     |        6.37        |       20      |  1/1  |
| TIMEOUT | DISCO_F746NG | GCC_ARM   | RTOS_5      | Queue messaging                       |       40.38        |       20      |  0/1  |
| TIMEOUT | DISCO_F746NG | GCC_ARM   | RTOS_6      | Mail messaging                        |       40.38        |       20      |  0/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_7      | Timer                                 |       11.37        |       15      |  1/1  |
| OK      | DISCO_F746NG | GCC_ARM   | RTOS_8      | ISR (Queue)                           |        6.36        |       20      |  1/1  |
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 1 FAIL / 23 OK / 2 TIMEOUT

// ARM
+--------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result | Target       | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK     | DISCO_F746NG | ARM       | DTCT_1      | Simple detect test                    |        0.48        |       10      |  1/1  |
| OK     | DISCO_F746NG | ARM       | EXAMPLE_1   | /dev/null                             |        3.46        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_10     | Hello World                           |        0.39        |       5       |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_11     | Ticker Int                            |       11.36        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_12     | C++                                   |        1.37        |       10      |  1/1  |
| FAIL   | DISCO_F746NG | ARM       | MBED_16     | RTC                                   |        6.58        |       20      |  0/1  |
| OK     | DISCO_F746NG | ARM       | MBED_2      | stdio                                 |        0.8         |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_23     | Ticker Int us                         |       11.35        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_24     | Timeout Int us                        |       11.37        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_25     | Time us                               |       11.37        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_26     | Integer constant division             |        1.38        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_34     | Ticker Two callbacks                  |       11.36        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_37     | Serial NC RX                          |       10.89        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_38     | Serial NC TX                          |        15.4        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_A1     | Basic                                 |        1.36        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_A21    | Call function before main (mbed_main) |        1.43        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_A9     | Serial Echo at 115200                 |        6.5         |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | MBED_BUSOUT | BusOut                                |        2.26        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_1      | Basic thread                          |       11.35        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_2      | Mutex resource lock                   |       11.38        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_3      | Semaphore resource lock               |        8.38        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_4      | Signals messaging                     |        6.38        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_5      | Queue messaging                       |        2.36        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_6      | Mail messaging                        |        2.36        |       20      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_7      | Timer                                 |       11.36        |       15      |  1/1  |
| OK     | DISCO_F746NG | ARM       | RTOS_8      | ISR (Queue)                           |        6.36        |       20      |  1/1  |
+--------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 1 FAIL / 25 OK

//uARM
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result  | Target       | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK      | DISCO_F746NG | uARM      | DTCT_1      | Simple detect test                    |        0.51        |       10      |  1/1  |
| OK      | DISCO_F746NG | uARM      | EXAMPLE_1   | /dev/null                             |        3.45        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_10     | Hello World                           |        0.36        |       5       |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_11     | Ticker Int                            |       11.37        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_12     | C++                                   |        1.35        |       10      |  1/1  |
| FAIL    | DISCO_F746NG | uARM      | MBED_16     | RTC                                   |        6.58        |       20      |  0/1  |
| OK      | DISCO_F746NG | uARM      | MBED_2      | stdio                                 |        0.77        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_23     | Ticker Int us                         |       11.35        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_24     | Timeout Int us                        |       11.37        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_25     | Time us                               |       11.34        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_26     | Integer constant division             |        1.36        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_34     | Ticker Two callbacks                  |       11.38        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_37     | Serial NC RX                          |       10.89        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_38     | Serial NC TX                          |       15.38        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_A1     | Basic                                 |        1.36        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_A21    | Call function before main (mbed_main) |        1.41        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_A9     | Serial Echo at 115200                 |        6.5         |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | MBED_BUSOUT | BusOut                                |        2.26        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_1      | Basic thread                          |       11.36        |       15      |  1/1  |
| TIMEOUT | DISCO_F746NG | uARM      | RTOS_2      | Mutex resource lock                   |       40.23        |       20      |  0/1  |
| TIMEOUT | DISCO_F746NG | uARM      | RTOS_3      | Semaphore resource lock               |       40.26        |       20      |  0/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_4      | Signals messaging                     |        6.37        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_5      | Queue messaging                       |        2.38        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_6      | Mail messaging                        |        2.36        |       20      |  1/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_7      | Timer                                 |       11.36        |       15      |  1/1  |
| OK      | DISCO_F746NG | uARM      | RTOS_8      | ISR (Queue)                           |        6.37        |       20      |  1/1  |
+---------+--------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 1 FAIL / 23 OK / 2 TIMEOUT

There are those timeouts , @bcostm might know more?

Tested today on GCC. Same issue with RTOS_5 and 6. I don't know why.
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| Result  | Target             | Toolchain | Test ID | Test Description        | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_1  | Basic thread            |       11.42        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_2  | Mutex resource lock     |       11.55        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_3  | Semaphore resource lock |        8.49        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_4  | Signals messaging       |        6.42        |       20      |  1/1  |
| TIMEOUT | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_5  | Queue messaging         |       40.22        |       20      |  0/1  |
| TIMEOUT | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_6  | Mail messaging          |       40.21        |       20      |  0/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_7  | Timer                   |       11.43        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_8  | ISR (Queue)             |        6.43        |       20      |  1/1  |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+

Tested with uARM and ARM, all tests are in TIMEOUT. I got this message for all the tests:
HOST: Reset target...
HOST: Unknow property:

Tested with IAR, cannot build at all.
[DEBUG] Return: 3
[10:53:50] Error: There were errors while building MBED libs for DISCO_F746NG using IAR
Test summary:
+--------+--------+-----------+---------+------------------+--------------------+---------------+-------+
| Result | Target | Toolchain | Test ID | Test Description | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+--------+-----------+---------+------------------+--------------------+---------------+-------+
+--------+--------+-----------+---------+------------------+--------------------+---------------+-------+
Result:

IAR - can you build a library  , does your IAR support m7 ? I had some license issues which I have to resolve, for now as IAR is not released for the board. I receive an exception for older version that cortex m7 is not recognized cpu type.
Unknown property means something is wrong with the host tests, wrong baudrate? Use verbose and print all messages. Please create a new issue for this if you are having problems , we will look at this.

New tests done with latest compilers versions.
GCC Version 5.2 2015q4
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| Result  | Target             | Toolchain | Test ID | Test Description        | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_1  | Basic thread            |       11.39        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_2  | Mutex resource lock     |       11.48        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_3  | Semaphore resource lock |        8.45        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_4  | Signals messaging       |        6.45        |       20      |  1/1  |
| TIMEOUT | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_5  | Queue messaging         |       40.24        |       20      |  0/1  |
| TIMEOUT | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_6  | Mail messaging          |       40.21        |       20      |  0/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_7  | Timer                   |       11.42        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | GCC_ARM   | RTOS_8  | ISR (Queue)             |        6.46        |       20      |  1/1  |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+

ARM/uARM with uVision Version 5.17
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| Result  | Target             | Toolchain | Test ID | Test Description        | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_1  | Basic thread            |       11.38        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_2  | Mutex resource lock     |        11.5        |       20      |  1/1  |
| TIMEOUT | DISCO_F746NG[F82F] | uARM      | RTOS_3  | Semaphore resource lock |       42.32        |       21      |  0/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_4  | Signals messaging       |        6.44        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_5  | Queue messaging         |        2.42        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_6  | Mail messaging          |        2.4         |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_7  | Timer                   |       11.42        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | uARM      | RTOS_8  | ISR (Queue)             |        6.44        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_1  | Basic thread            |       11.42        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_2  | Mutex resource lock     |       11.48        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_3  | Semaphore resource lock |        8.49        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_4  | Signals messaging       |        6.4         |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_5  | Queue messaging         |        2.42        |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_6  | Mail messaging          |        2.4         |       20      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_7  | Timer                   |       11.41        |       15      |  1/1  |
| OK      | DISCO_F746NG[F82F] | ARM       | RTOS_8  | ISR (Queue)             |        6.46        |       20      |  1/1  |
+---------+--------------------+-----------+---------+-------------------------+--------------------+---------------+-------+

Build with IAR v<IP_ADDRESS>38 still not working.
Compile: startup_stm32f746xx.S
[DEBUG] Command: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.3\arm\bin\iasmarm --cpu Cortex-M7F -DMBED_BUILD_TIMESTAMP=1452868017.91 -DTAR
GET_STM32F746NG -DTARGET_STM32F746 -DARM_MATH_CM7 -DTARGET_CORTEX_M -D__CORTEX_M7 -D__FPU_PRESENT=1 -DTARGET_DISCO_F746NG -DTARGET_RTOS_M4_M7 -DTARGET
_STM -DTARGET_M7 -DTARGET_STM32F7 -DTOOLCHAIN_IAR -D__MBED__=1 -IC:\GITHUB\mbed\libraries\mbed\targets\cmsis -IC:\GITHUB\mbed\libraries\mbed\targets\c
msis\TARGET_STM -IC:\GITHUB\mbed\libraries\mbed\targets\cmsis\TARGET_STM\TARGET_STM32F7 -IC:\GITHUB\mbed\libraries\mbed\targets\cmsis\TARGET_STM\TARGE
T_STM32F7\TARGET_DISCO_F746NG -IC:\GITHUB\mbed\libraries\mbed\targets\cmsis\TARGET_STM\TARGET_STM32F7\TARGET_DISCO_F746NG\TOOLCHAIN_IAR -IC:\GITHUB\mb
ed\libraries\mbed\targets\cmsis\TOOLCHAIN_IAR -o C:\GITHUB\mbed\build\mbed\.temp\TARGET_DISCO_F746NG\TOOLCHAIN_IAR\TARGET_STM\TARGET_STM32F7\TARGET_DI
SCO_F746NG\TOOLCHAIN_IAR\startup_stm32f746xx.o C:\GITHUB\mbed\libraries\mbed\targets\cmsis\TARGET_STM\TARGET_STM32F7\TARGET_DISCO_F746NG\TOOLCHAIN_IAR
\startup_stm32f746xx.S
[DEBUG] Return: 3
Traceback (most recent call last):
  File "..\mbed\workspace_tools\build.py", line 234, in <module>
    macros=options.macros)
  File "C:\GITHUB\mbed\workspace_tools\build_api.py", line 445, in build_mbed_libs
    raise e
ToolException

Can you find out what is IAR saying, print exception on the line 445:
  File "C:\GITHUB\mbed\workspace_tools\build_api.py", line 445, in build_mbed_libs
    raise e

I put a print e before the "raise e" but nothing is displayed.


FLAKE: github/grpc/run_tests/objc_macos_opt_native/mac-test-basictests[default]

https://source.cloud.google.com/results/invocations/ad79ffd2-eddc-4977-9d5b-46b2b534ca99/targets/github%2Fgrpc%2Frun_tests%2Fobjc_macos_opt_native%2Fmac-test-basictests/tests
Looks like there were 4 test failures here:
Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API]' started.
Thu Mar 26 08:58:50 PDT 2020 - 2020-03-26 08:55:31.589654-0700 xctest[30836:1011362] [Metadata] Got error Connection invalid
Thu Mar 26 08:58:50 PDT 2020 - 2020-03-26 08:55:31.590454-0700 xctest[30836:1011369] DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
Thu Mar 26 08:58:50 PDT 2020 - <unknown>:0: error: -[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API] : Asynchronous wait failed: Exceeded timeout of 32 seconds, with unfulfilled expectations: "Received trailer for RPC 7", "Received trailer for RPC 5", "Received trailer for RPC 6", "Received trailer for RPC 4", "Received trailer for RPC 3", "Received trailer for RPC 9", "Received trailer for RPC 8", "Received trailer for RPC 2", "Received trailer for RPC 1", "Received trailer for RPC 0".
Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API]' failed (32.276 seconds).

Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testHijackingInterceptor]' started.
Thu Mar 26 08:58:50 PDT 2020 - /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/objective-c/tests/InteropTests/InteropTests.m:1656: error: -[InteropTestsRemote testHijackingInterceptor] : ((trailingMetadata) == nil) failed: "{
Thu Mar 26 08:58:50 PDT 2020 - }"
Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testHijackingInterceptor]' failed (29.555 seconds).

Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testKeepaliveWithV2API]' started.
Thu Mar 26 08:58:50 PDT 2020 - <unknown>:0: error: -[InteropTestsRemote testKeepaliveWithV2API] : Asynchronous wait failed: Exceeded timeout of 32 seconds, with unfulfilled expectations: "Keepalive".
Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testKeepaliveWithV2API]' failed (32.060 seconds).

Thu Mar 26 08:58:50 PDT 2020 - Test Case '-[InteropTestsRemote testLargeUnaryRPC]' started.
Thu Mar 26 08:58:50 PDT 2020 - E0326 08:57:59.022894000<PHONE_NUMBER>69632 chttp2_transport.cc:2881]     ipv4:<IP_ADDRESS>:443: Keepalive watchdog fired. Closing transport.
Thu Mar 26 08:58:50 PDT 2020 - 2020-03-26 08:57:59.023044-0700 xctest[30836:1014333] *** Assertion failure in -[XCTestCase _enqueueFailureWithDescription:inFile:atLine:expected:breakWhenDequeued:](), /Library/Caches/com.apple.xbs/Sources/XCTest/XCTest-13764/Sources/XCTestFramework/Core/XCTestCase.m:399
Thu Mar 26 08:58:50 PDT 2020 - 2020-03-26 08:57:59.023311-0700 xctest[30836:1014333] *** Assertion failure in -[XCTestCase _enqueueFailureWithDescription:inFile:atLine:expected:breakWhenDequeued:](), /Library/Caches/com.apple.xbs/Sources/XCTest/XCTest-13764/Sources/XCTestFramework/Core/XCTestCase.m:399
Thu Mar 26 08:58:50 PDT 2020 - 2020-03-26 08:57:59.030312-0700 xctest[30836:1014333] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Unable to report test assertion failure '((error.code) equal to (GRPC_STATUS_UNAVAILABLE)) failed: throwing "Unable to report test assertion failure '((error.code) equal to (GRPC_STATUS_UNAVAILABLE)) failed: ("1") is not equal to ("14") - Received status 1 instead of UNAVAILABLE (14).' from /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/objective-c/tests/InteropTests/InteropTests.m:1405 because it was raised inside test case -[InteropTestsRemote testKeepaliveWithV2API] which has no associated XCTestRun object. This may happen when test cases are constructed and invoked independently of standard XCTest infrastructure, or when the test has already finished." - Received status 1 instead of UNAVAILABLE (14).' from /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/objective-c/tests/InteropTests/InteropTests.m:1405 because it was raised inside test case -[InteropTestsRemote testKeepaliveWithV2API] which has no associated XCTestRun object. This may happen when test cases are constructed and invoked independently of standard XCTest infrastructure, or when the test has already finished.'
Thu Mar 26 08:58:50 PDT 2020 - *** First throw call stack:
Thu Mar 26 08:58:50 PDT 2020 - (
Thu Mar 26 08:58:50 PDT 2020 - 	0   CoreFoundation                      0x00007fff548eb66b __exceptionPreprocess + 171
Thu Mar 26 08:58:50 PDT 2020 - 	1   libobjc.A.dylib                     0x00007fff7bb3d942 objc_exception_throw + 48
Thu Mar 26 08:58:50 PDT 2020 - 	2   CoreFoundation                      0x00007fff548f1252 +[NSException raise:format:arguments:] + 98
Thu Mar 26 08:58:50 PDT 2020 - 	3   Foundation                          0x00007fff56a9fa0b -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 165
Thu Mar 26 08:58:50 PDT 2020 - 	4   XCTest                              0x0000000105ec81a8 -[XCTestCase _enqueueFailureWithDescription:inFile:atLine:expected:breakWhenDequeued:] + 1034
Thu Mar 26 08:58:50 PDT 2020 - 	5   XCTest                              0x0000000105ed20c0 _XCTFailureHandler + 408
Thu Mar 26 08:58:50 PDT 2020 - 	6   MacTests                            0x0000000108fd3a15 __38-[InteropTests testKeepaliveWithV2API]_block_invoke + 3045
Thu Mar 26 08:58:50 PDT 2020 - 	7   MacTests                            0x0000000108fff4fc -[InteropTestsBlockCallbacks didCloseWithTrailingMetadata:error:] + 124
Thu Mar 26 08:58:50 PDT 2020 - 	8   MacTests                            0x000000010922b4ac __61-[GRPCStreamingProtoCall didCloseWithTrailingMetadata:error:]_block_invoke + 135
Thu Mar 26 08:58:50 PDT 2020 - 	9   libdispatch.dylib                   0x00007fff7c7225fa _dispatch_call_block_and_release + 12
Thu Mar 26 08:58:50 PDT 2020 - 	10  libdispatch.dylib                   0x00007fff7c71adb8 _dispatch_client_callout + 8
Thu Mar 26 08:58:50 PDT 2020 - 	11  libdispatch.dylib                   0x00007fff7c72f217 _dispatch_queue_serial_drain + 635
Thu Mar 26 08:58:50 PDT 2020 - 	12  libdispatch.dylib                   0x00007fff7c722166 _dispatch_queue_invoke + 373
Thu Mar 26 08:58:50 PDT 2020 - 	13  libdispatch.dylib                   0x00007fff7c72f07a _dispatch_queue_serial_drain + 222
Thu Mar 26 08:58:50 PDT 2020 - 	14  libdispatch.dylib                   0x00007fff7c722166 _dispatch_queue_invoke + 373
Thu Mar 26 08:58:50 PDT 2020 - 	15  libdispatch.dylib                   0x00007fff7c72ff0d _dispatch_root_queue_drain_deferred_wlh + 332
Thu Mar 26 08:58:50 PDT 2020 - 	16  libdispatch.dylib                   0x00007fff7c733d21 _dispatch_workloop_worker_thread + 880
Thu Mar 26 08:58:50 PDT 2020 - 	17  libsystem_pthread.dylib             0x00007fff7ca6bfd2 _pthread_wqthread + 980
Thu Mar 26 08:58:50 PDT 2020 - 	18  libsystem_pthread.dylib             0x00007fff7ca6bbe9 start_wqthread + 13
Thu Mar 26 08:58:50 PDT 2020 - )
Thu Mar 26 08:58:50 PDT 2020 - libc++abi.dylib: terminating with uncaught exception of type NSException
Thu Mar 26 08:58:50 PDT 2020 -
Thu Mar 26 08:58:50 PDT 2020 - Restarting after unexpected exit or crash in InteropTestsRemote/testLargeUnaryRPC; summary will include totals from previous launches.

This has been fixed by #22687

https://source.cloud.google.com/results/invocations/1494e9c0-e279-4db7-8800-a00f5fd932fb/targets/github%2Fgrpc%2Ftoplevel_run_tests_invocations%2Frun_tests_objc_macos_opt_native/tests
Wed Jul 22 16:19:09 PDT 2020 - Test Case '-[InteropTestsRemote testHijackingInterceptor]' failed (32.259 seconds).

saw this test fail

Just saw this failure again:
Fri Aug 21 12:02:34 PDT 2020 - Test Case '-[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API]' started.
Fri Aug 21 12:02:34 PDT 2020 - 2020-08-21 12:02:06.415344-0700 xctest[33243:64929] [Metadata] Got error Connection invalid
Fri Aug 21 12:02:34 PDT 2020 - 2020-08-21 12:02:06.415964-0700 xctest[33243:65056] DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
Fri Aug 21 12:02:34 PDT 2020 - <unknown>:0: error: -[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API] : Asynchronous wait failed: Exceeded timeout of 32 seconds, with unfulfilled expectations: "Received trailer for RPC 2", "Received trailer for RPC 5", "Received trailer for RPC 7", "Received trailer for RPC 4", "Received trailer for RPC 8", "Received trailer for RPC 9", "Received trailer for RPC 0", "Received trailer for RPC 6", "Received trailer for RPC 3", "Received trailer for RPC 1".
Fri Aug 21 12:02:34 PDT 2020 - Test Case '-[InteropTestsRemote testConcurrentRPCsWithErrorsWithV2API]' failed (32.299 seconds).

Another failure:
Tue Dec 15 13:51:31 PST 2020 - Test Case '-[InteropTestsRemote testHijackingInterceptor]' started.
Tue Dec 15 13:52:04 PST 2020 - /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/objective-c/tests/InteropTests/InteropTests.m:1710: error: -[InteropTestsRemote testHijackingInterceptor] : Asynchronous wait failed: Exceeded timeout of 32 seconds, with unfulfilled expectations: "Internal gRPC call completed.".
Tue Dec 15 13:52:04 PST 2020 - Test Case '-[InteropTestsRemote testHijackingInterceptor]' failed (32.298 seconds).

Fixed: #25958


Git Repo with standard Service Connection templates in JSON?

Is it possible for Azure DevOps to provide their standard, default JSON Templates for the Service Endpoints in a Git repo?

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

ID: 209081c3-76a3-562e-3479-e6b63b7ec2c7
Version Independent ID: c0be31ee-9568-cddd-2ee4-af196aa318d8
Content: Create Service Endpoint using Azure DevOps CLI - Azure DevOps
Content Source: docs/cli/service_endpoint.md
Product: devops
Technology: devops-ref
GitHub Login: @KathrynEE
Microsoft Alias: gsaral

Thanks for the suggestion! The product teams aren’t always watching this repository, so to make sure it gets in front of them for triage, please submit your idea here.
cc @KathrynEE for awareness


Question regarding use of 'luci.sys.wifi.getiwinfo'

Hi Jo,
currently I would like to add WPA3 support to luci-app-travelmate. In the past I've used 'luci.sys.wifi.getiwinfo' to gather all relevant information on my wifi scan result page, e.g.:
	local iw    = luci.sys.wifi.getiwinfo(dev)
	luci.util.dumptable(iw.scanlist)

If I check the debug output, the encryption description is usually OK, even for the new WPA3 modes ... only the WPA2/WPA3 mixed mode seems to be broken, e.g.:
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 2	table: 0x55dfcad0
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	encryption	table: 0x55dfcb30
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		enabled	true
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		auth_algs	table: 0x55dfda80
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		description	WPA2 PSK (CCMP)
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		wep	false
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		auth_suites	table: 0x55dfda20
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 			1	PSK
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		wpa	6
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		pair_ciphers	table: 0x55dfcb80
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 			1	CCMP
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 		group_ciphers	table: 0x55dfd9f0
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	quality_max	70
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	ssid	WPA3
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	channel	1
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	signal	-34
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	bssid	06:F0:21:18:25:F9
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	mode	Master
Wed Oct 16 15:35:48 2019 daemon.err uhttpd[2813]: 	quality	70

In comparison the (correct) output of 'iwinfo radio1 scan' on the same device/configuration, e.g.:
Cell 02 - Address: 06:F0:21:18:25:F9
          ESSID: "WPA3"
          Mode: Master  Channel: 1
          Signal: -32 dBm  Quality: 70/70
          Encryption: mixed WPA2/WPA3 PSK/SAE (CCMP)

Is it still "allowed" to use the getiwinfo function or should I use another approach to get these kind of information?
BTW: Currently 'iwinfo scan' didn't list "hidden" APs, seems to be a regression IMHO.
Thanks for your support!

Hi,
I'll fix the mixed WPA3 reporting. About hidden scan results; what do
you expect to receive? An entry with the SSID set to an empty string
like iw does it?
Cheers,
Jo

Hi,
thanks for the fast response. If I remember correctly, iwinfo has reported "unknown" as ssid for hidden networks in the past.

This is right for the iwinfo ... scan cli output, but the Lua table data does not quote the SSIDs.

Yep, you're right. Travelmate backend uses iwinfo scan cli, while the luci frontend will use the lua table data ... maybe not the best approach. ;-)

Okay, I'm going to push my fixes now. For hidden networks, the .ssid field in the Lua tables will be unset / not existing, so you can use something like  local ssid = entry.ssid or "unknown"

Perfect, thanks again!

Updates pushed to master and 19.07


Fix: duplicate column selection issue in getMany with joins and pagination

This pull request proposes a fix for the duplicate column names encountered when using getMany with joins and pagination in NestJS CRUD #788.
The current solution in #788 excludes the "id" column, which might not be ideal for all relational scenarios. This pull request aims to address duplication directly within the column array, preserving the "id" column when necessary or any duplicated column.
Key points:

[X] Solves duplicate column issue identified in #788.
[X] Maintains "id" column inclusion for relational cases.
[X] Implements logic to remove duplication within the column array.

Please review and provide feedback on the proposed approach.
issue #32

@ZaidMaslouhi Thank you for your contribution.
The fix is released as 5.3.3


 when I said that object-path already had what he is "reinventing" (littering npm with an useless module called set-value).
object-path is missing a way to handle keys with escaped dots in it. it already does when you use the array notation (eg: ['some.dot.key', 'another.path']) and only a retarded person (IMHO) would write it as objectPath.get(obj, 'some\.****head\.is\.stupid');
sorry for the rant along, but it's amazing how people can be stupid now a days

As you said, object-path already has a way to set dotted properies. Escaping is not going to simplify things but rather complicate them. (Sorry for the late response, I'm on holidays)


Compiler is broken and generates code that behaves differently than running vite in dev server mode

Describe the bug
We have an app where you play a crossword board game like Scrabble. After updating our JS modules, several users reported that mobile drag-and-drop of the tiles was scrolling the entire page, instead of just dragging and dropping the tiles.
We eventually figured out that the error occurs if we run vite build then vite preview, but not if we run just plain vite. This implies to us that the vite compiler is broken.
Reproduction
https://github.com/woogles-io/liwords/pull/1359/files
Steps to reproduce
It is close to impossible for us to generate a minimal reproduction since we don't have the time to cross-check all the different variables / libraries. However, the following pull request, in which we replaced vite with rsbuild, and had no other changes besides dependencies to both those libraries, show that the problem lies with the vite compiler:
https://github.com/woogles-io/liwords/pull/1359/files
A video is attached that shows me running the error case with vite in preview mode (where dragging tiles drags the screen), then vite in dev server mode, where there is no bug.
We deployed the rsbuild change and that works fine on prod.
https://github.com/user-attachments/assets/d8322b11-3de5-4341-867c-b3585a1fd879
System Info
System:
    OS: Linux 6.10 Arch Linux
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12600K
    Memory: 55.09 GB / 62.59 GB
    Container: Yes
    Shell: 5.2.32 - /bin/bash
  Binaries:
    Node: 22.7.0 - /usr/bin/node
    npm: 10.8.2 - /usr/bin/npm
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1
    vite: ^5.4.2 => 5.4.2

### Used Package Manager

npm

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

We'd need a repro for this even though it may be hard to identify what's wrong. Many of us who triage and fix issues also don't have the time to dig into your project, especially since you'd know best around your codebase to trim down what's unnecessary for the issue. Perhaps it would be easier to try different Vite versions if a specific one was causing the bug. (If you're happy with rsbuild as a workaround, that's fine too.)

For future reference, probably this was a duplicate of #16065


Fixed for dgram needing buffer length

Encountered a RangeError on the below line, looked up similar code on StackOverflow, found that dgram needs a buffer length

Hey, thanks for taking the time to contribute! :D
From what I interpret of the node udp socker docs the start position and length should be optional fields. I wonder if perhaps this is changed behaviour in some version of node? Or I wonder if there's a bug where a not-a-buffer or 0 length buffer is being passed in that somehow causes the RangeError.
So of curiosity, which version of node are you using? And how often were you seeing this error pop up, and did this patch completely remove all symptoms of errors?

The error was preventing the program from doing anything, it returned "Could not send" repeatedly. After removing the try{}catch(e){}, we had this error http://paste.ee/p/2iMPy. Node version 4.2.6

This change removed the error entirely, the program works great now, it's very cool :D

Aha! I used node 5 when developing this. In node 4, the arguments were not optional. I'll merge this when I'm next in front of my PC. Thanks again :)


Pin transformers version <4.47

What does this PR do?
pins the transformers version to <4.47
fixes #2445

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Does this also need to be updated in the requirements.txt? as it still shows transformers>=4.46.0

@anhuong I believe the requirements.txt is used by the CI and the issue is fixed in the main branch...


Fix compile errors with base-4.8 & network >= 2.6

See commit messages for details

bump

I'm really not a fan of cabal flags. Let me see how I've delt with this elsewhere. I think all that was required was a base dependency on GHC >= 7.8.3, right?


[SPARK-14970][SQL] Prevent DataSource from enumerates all files in a directory if there is user specified schema

What changes were proposed in this pull request?
The FileCatalog object gets created even if the user specifies schema, which means files in the directory is enumerated even thought its not necessary. For large directories this is very slow. User would want to specify schema in such scenarios of large dirs, and this defeats the purpose quite a bit.
How was this patch tested?
Hard to test this with unit test.

@marmbrus Can you take a look.

Test build #57205 has started for PR 12748 at commit 4e4e8db.

Test build #57205 has finished for PR 12748 at commit 4e4e8db.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57205/
Test PASSed.

Merged build finished. Test PASSed.

We might still disable schema inference, but until then this LGTM.


SafeDocs requires MDE onboarding

Included reference to SafeDocs in related topics.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


fix(tf): bucket policy cur conditions

Issue #989, if available:
Description of changes:
Use us-east-1 for conditions on cur bucket policy cur definition bucket policy
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

duplicate of #991


add the https support and example

Https support
issue #1530
current wasmedge code: https://github.com/2019zhou/WasmEdge/tree/zhou/httpsreq

build the wasmedge

sudo apt-get install libssl-dev
cmake -DCMAKE_BUILD_TYPE=Release -DWASMEDGE_BUILD_TESTS=OFF -DWASMEDGE_PLUGIN_HTTPSREQ=true  .. && make -j4

use the https request
request::get("https://httpbin.org", &mut writer).unwrap();

print all the feed back
res.status_code(), res.headers(), res.reason() is not available()
problems

wasmedge host function cannot pass the string. If Wasmedge host function can pass the string, it can use the exact same API and by adding the few lines of code, that is res.status_code(), res.headers(), res.reason() is not available().

let mut resvec = Vec::new();
 let  res = Response::try_from(RESPONSE, &mut resvec).unwrap();
return Ok(res);

Now, it can only print all the feedback by calling post/get/head.

Is there any need to add more host functions other than the send_data function
Because WASM built-in types (aka. uint32_t, uint64_t, float, and double) are supported in host functions, it is possible to add a get_status function.

The problems have been solved. And now the APIs for HTTPS are identical to the original.

I honestly think it should be called ssl instead of httpsreq because more than HTTPS needs SSL connections. It should be an SSL wrapper(including but not limited to OpenSSL)

Is it better to rename the module to ssl wrapper?

Yes, and independent of the application layer protocol.


[CSL-118] [SSFK] [Research] Update system

@georgeee
Need to design update system for Cardano SL.
So, sysupdate feature includes:

SSFK: way to obtain keypair for signing system update
Block structure extended with:

SSFK
Version number (or some other reference to software version)

Sysupdate structure (inc. versioning)
Sysupdate propagation (i.e. download)
Sysupdate patching (i.e. applying binary patch to executable, and it should be cross-platform)

*** Sunsetted fork key
**** Send to review by Bernardo, Aggelos, Vincent
**** About
***** Part of block header
***** Information for secure app self-update
***** How to serve
****** List of mirrors
****** DHT

@georgeee
Proposal on SSFK implementation
SSFK — an expirable key for signing arbitrary data.
Implemented as a keypair, public part is for verification, private part — for signing.
There is a party (key-holder, KH) responsible for timely providing SSFK's and delivering them to the network.
We measure timeframes in terms of blockchain height.

SSFK for each timeframe is stored in the block header.
SSFK is signed with previous block's SSFK. (1)
SSFK signature is seeded/mixed with block height to avoid replay attacks.
SSFK expires when its block's depth exceeds some predefined constant value (2).
KH repeatedly broadcasts signed SSFKs for a range of recent blockchain depths.
Miner's incentive to include SSFK into the block header is that otherwise the block won't be accepted.

(1) Genesis block is the only exception.
(2) Block's depth — number of blocks that follow up to the chain's top. The top block has zero depth.

@georgeee
Brief overview of how sysupdates are done by various software: https://www.usenix.org/legacy/events/hotsec06/tech/full_papers/bellissimo/bellissimo.pdf

@georgeee
Regarding 4: let's stick now to list of mirrors

@georgeee
Software version should be first bytes of block, so that we can change block structure in any way from version to version

@georgeee
Old estimates:
CSL-118 [Research] Update system -- 1.5d
Development:
SSFK: way to obtain keypair for signing system update + include in block
Est.: 1d
Sysupdate structure & propagation
Binary instances for sysupdate
Utility to compose sysupdates given two compiled versions of cardano-node binary (or whatever)
Download from list of mirrors (simple HTTP)
Est.: 2d
Sysupdate patching (i.e. applying binary patch to executable, and it should be cross-platform)
??
Est.: 2d (hopefully, no idea yet)

Debugging & backlog

@georgeee
Due to update business requirements, this issue is outdated. Research is to be handled under CSL-121


Lint fails and states that an old version of Node.js is in use (with Node installed via n version management)

Version
3.0.0-rc.3
Reproduction link
https://github.com/DMeechan/meechan-co
Steps to reproduce
Summary:

Install latest version of Node (v10.5.0) using n
Create a Vue project with linting enabled on commit
When trying to create a commit, the linter fails and erroneously reports that I'm using Node v7.10.0

Detailed steps:

yarn global add n
n latest (installs Node v10.5.0 at time of writing)
yarn global add @vue/cli
vue create sample-project
Select Manually select features
Select Linter / Formatter
Select ESLint   Prettier
Select both Lint on save and Lint and fix on commit
Select In package.json
cd sample-project
yarn
git add .
git commit -m "init"

Error log appears (see below).
What is expected?
The linting and commit to succeed.
What is actually happening?
When attempting to create a commit, the linter fails and displays this error message:
 > running pre-commit hook: lint-staged
 ❯ Running tasks for *.js
   ✖ vue-cli-service lint
     → Please upgrade your Node version.
     git add
 ❯ Running tasks for *.vue
   ✖ vue-cli-service lint
     → Please upgrade your Node version.
     git add
✖ vue-cli-service lint found some errors. Please fix them and try committing again.

 ERROR  You are using Node v7.10.0, but vue-cli-service requires Node >=8.
Please upgrade your Node version.
✖ vue-cli-service lint found some errors. Please fix them and try committing again.

 ERROR  You are using Node v7.10.0, but vue-cli-service requires Node >=8.
Please upgrade your Node version.

pre-commit hook failed (add --no-verify to bypass)

Running node --version shows that I'm running Node v10.5.0.

While we still strugle for a setup to reproduce this in, can you quickly run:

npm run lint
node_modules/.bin/eslint /src

So test if this error is at al related to vue-cli?

If it is vue-cli, only the second command should run fine, while the first should throw an error.
If the first runs fine as well, the problem is more likely with the git hooks/package running those hooks (lint-staged).

can you do the following?

Create a small file called test.js anywhere. It should look like this:

 #!/usr/bin/env node

console.log(process.version)

make the file an executable:

chmode +x test.js

Run the executable

./test.js

My supicion is that this is a misconfiguration in your environment rather than a problem with vue-cli, and I would like to disprove that before risking to wreck my own env by installing n and nvm in parallel or anything.

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more information.

i reproduce it by upgrade @vue/cli-service from v3.0.0-beta.6 to  v3.0.1，when i run vue-cli-service lint on commit, the console displays errors as below
 > running pre-commit hook: lint-staged
 ❯ Running tasks for src/**/*.js
   ✖ vue-cli-service lint
     git add
 ↓ Running tasks for src/**/*.vue [skipped]
   → No staged files match src/**/*.vue
✖ "vue-cli-service lint" found some errors. Please fix them and try committing again.

 ERROR  You are using Node v6.11.0, but vue-cli-service requires Node >=8.
Please upgrade your Node version.

note that, my node version is v8.11.4 installed via nvm.


How are general subsystem updates handled?

We are clearly seeing a lot of activity here and have been given indication that a tremendous amount of work is going on to resolve the issues we're reporting and discovering.  This level of interaction from Microsoft proper is exciting.
How will updates be delivered to the Linux Subsystem?  Will we see these updates at faster intervals than updates that are issued to Windows?  It seems that many of us may want to see updates made specifically to the subsystem and Ubuntu vs also grabbing all of the other bundled Windows updates (eg, many of us can afford to tinker with a subsystem, but we don't want to deal with big holistic Windows problems that will blow up our dev workstations).
Also, can we assume that apt-get update && apt-get dist-upgrade will always get us to where we need to be with regards to the Ubuntu installation?

Thanks for the kind words.
To answer your question you will get updates to Windows Sybsystem for Linux when you receive new Windows flights. I agree it's not ideal to have to install a whole new OS to just receive updates to the subsystem, but currently that's the way things are set up.
For updates to the usermode pieces the current plan of record is to not update them without the user running apt or apt-get commands.  In a upcoming change we will update the apt package index and warn the user that updates are available, but updating is up to you.
Does that answer your questions?

There is an undocumented command that can be run from Cmd: lxrun /update /critical
But maybe it's the same as apt update && apt dist-upgrade

Internally we've changed what lxrun /update does to only update the apt package cache.

Each time a new Windows flight comes I have done lxrun /uninstall /full /y followed by bash in Command. Is this necessary or would it be enough to do sudo apt update && sudo apt -y dist-upgrade in Bash?

We do not modify the Ubuntu user mode bits on new flights. You can continue using your existing install.

No discussion on this topic for a few months, closing this out.


Remove orphaned-plugin exception

don't track nonPlugins
remove error tests

With the implementation of useService, plugins that supply React context must be registered to a token. Previously, this wasn't required.
We currently have no way of tracking the relationship between plugins and components, it's purely enforced during rendering since useService will throw if the plugin was not registered. We couldn't suspend throwing an error until rendering is complete since not every component is rendered.
The only purpose this exception served was to make you aware of whether you needed a token or not. Supplying a token and not using it has no effect on the application's correctness.
Previous work:

https://github.com/fusionjs/fusion-core/pull/331
https://github.com/fusionjs/fusion-core/pull/119 (old and busted, new hotness)

@ganemone Do you remember a previous discussion about testing/mocking plugins where this enforcement was a consideration? Also I think there may have been one regarding plugin ordering too.
If we remove this, I wonder if we should re-visit those.

Bikeshed recap:
Accidentally registering server-only configuration on the client is a huge footgun this functionality is designed to prevent. Instead we should keep this as-is but recommend alternatives:

Wrap value in plugin instead of registering as plain value.
Import value directly (don't use Fusion DI)
Consume/Mock via React Context instead (don't use Fusion DI)


Enabling Simple authorizer to manage ACL rules

SUMMARY
Kafka provides authorization mechanisms using different plugins. There is one called Simple Authorizer provided by default (but not enabled). The amq_streams_broker role should allow to enable or disabled it allowing the operators to manage ACL for the different users managed by the collection.
This feature should also include the capability to declare super users.
The role should implement the tasks to manage the ACLs using the kafka-acls.sh script (in a similar way as the topic and user management)
References:

AMQ Streams - Simple ACL Authorizer
AMQ Streams - Enabling authrization
AMQ Streams - Adding ACLs
AMQ Streams - Listing ACLs
AMQ Streams - Removing ACLs

ISSUE TYPE

Feature Idea

@rmarting I think #103 has laid the ground work. With that, user can create their own ACL query... WDYT? Should we do more than that or can we consider this issue "done" (at least for now)?


Relax redis dependency

Hi @tobymao, great project!
redis dependency is specified as >4.2,<4.4. Any reason why we need <4.4? Not a big deal but the readme only mention >4.2

It was failing in a few areas, as well as tossing up lots of uncaught exceptions. I just submitted a PR(#62) a few minutes ago which includes fixes and relaxed dependency (<5.0).

thanks yea, redis 4.4 broke a lot of projects with their changes to errors / cancellations.

https://github.com/redis/redis-py/pull/2104


Configurable keys

In most linux systems middle mouse button works like a ctrl+v and fills selection with copied text when mouse up. it's make your default key configuration for linux confusing and unusable.
So, i created config based on @plafue request (https://github.com/bigfive/atom-sublime-select/pull/49) with observers, human readable select boxes in settings, keyboard key configuration and changed default combination to shift+LMB.

Hello, @bigfive
I've watched other pull requests and issues, and they don't get any response from you since may.
Is this package still maintained?

I think I still have push permissions on this repo and the corresponding package. If I can find the chance to test on different platforms or some others can confirm it fits their setup I can push this if @bigfive is still MIA


How to set frame type to rdp server

Releated pull request for master:
I use freerdp on linux to connet windows server. I want to get H.264 data and render myself.
Now I can get H.264 data before decompress,  I want to control the frame type from windows server, How to set frame type?
Such as I want to reset frame type ,so I need next frame type is I frame.

you can not control this from the client side.
The function to render is part of SurfaceCommand in RdpgfxClientContext
For further questions please ask using IRC or mailing list.

hmmm... How about framerate? Can I control it?

and bitrate?


fix(resolve): respect order of browser in mainFields when resolving

Description
fixes #15134
Additional context

do we need an extra test for this?
is it a breaking change?

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

just pushed a fix for a blunder I made which would have resolved the browser field even if targetWeb was false.  The tests did not catch this, so to answer my own question above:
Yes we need  tests covering the resolve of browser in different scenarios.

Haven't checked deeply yet. But these are the related discussions.
https://github.com/webpack/webpack/issues/4674, https://github.com/vitejs/vite/issues/1154, https://twitter.com/youyuxi/status/1348413401299562497

Haven't checked deeply yet. But these are the related discussions I'm aware of. webpack/webpack#4674, #1154, twitter.com/youyuxi/status/1348413401299562497

Yeah I don't think we can remove the special heuristic yet. The packages aren't inherently incorrectly packaged I think, just that it wasn't clear in the past what browser and module means.


feat: Punchout User Management for cXML and OCI user

Add cXML punchout user management next to OCI punchout user manangement
pending: breadcrumb service for the punchout user management in order to navigate from creation/update page back to the right user tab via the breadcrumb
ToDos

[x] fix e2e tests
[ ] punchout user creation with ID only (no first and last name, e.g. for the UI)?
the user name doesn't has to be an email address, that's why we initially leave it as it is

Does this PR Introduce a Breaking Change?
[x] Yes
BREAKING CHANGES: required Intershop Commerce Management version: <IP_ADDRESS>
Other Information
Wait for ICM <IP_ADDRESS>

The cXMl Punchout User Management description does not fit.

We decided to omit the URL hint for the cXML punchout user, because the login process of the cXML user is more complex.


Unable to animate with CSSTransitionGroup

Is there full support for animations? I'm having trouble getting anything reasonable working. I've defaulted to CSSTransitionGroup because things at least appear and disappear but no animation is present.
import CSSTransitionGroup from 'react-transition-group/CSSTransitionGroup'
 <CSSTransitionGroup transitionName='mainnav' transitionEnterTimeout={500} transitionLeaveTimeout={300}>
          {
            this.state.mainNav ? null : <NavBar />
          }
 </CSSTransitionGroup>
 <CSSTransitionGroup transitionName='mininav' transitionEnterTimeout={500} transitionLeaveTimeout={300}>
          {
            this.state.mainNav ? <MiniNavBar /> : null
          }
  </CSSTransitionGroup>

         .mininav-enter {
          	opacity: 0.01;
          }

          .mininav-enter.mininav-enter-active {
          	opacity: 1.0;
          	-webkit-transition: opacity 2000ms, ease-in;
          }

          .mininav-leave {
          	opacity: 1;
          }

          .mininav-leave.mininav-leave-active {
          	opacity: 0.01;
          	-webkit-transition: opacity 2000ms ease-in;
          }

          .mainnav-enter {
          	opacity: 0.01;
          }

          .mainnav-enter.mainnav-enter-active {
          	opacity: 1.0;
          	-webkit-transition: opacity 2000ms, ease-in;
          }

          .mainnav-leave {
          	opacity: 1;
          }

          .mainnav-leave.mainnav-leave-active {
          	opacity: 0.01;
          	-webkit-transition: opacity 2000ms ease-in;
          }

If you mean between route transitions, no:
https://github.com/zeit/next.js/issues/88
There's no top level component that stays mounted between pages, yet.

Yep we're tracking it in #88. Thanks @cdock1029


similar to get-value

Heya there, Nico! :)
get review this jonschlinkert/get-value, his benchmarks and related projects like set-value, get-property and etc :)
Jon made one of the fastest implementations.

And boy, that description, lol.

Didn't know that project, just threw one together cause I needed it


Improve navigation between FAQs and help center

from @RebeccaRo

Closing as you can view FAQs on Help Center, and when on a FAQ, you can navigate back to Help Center in the navigation bar.


Versions dialog

On the overview component the dropdown menu should have a "view versions" button that opens a dialog listing all existing versions with the option to update and delete any of them. Only the latest version should not be possible to delete.

@Ktarnaj please have a look at this one and if style needs to be improved


RELATED: WEB-3902 Allow lowercase env variables

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-oss-check/49/ : SUCCESS in 4s

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-fossa-scanning-oss-zuul/31/ : SUCCESS in 59s (non-voting)
https://checklist.intgdc.com/job/compliance/job/gooddata-docs-theme-merge-compliance-check/16/ : SUCCESS in 12s


Add Sentinel-1 to v1 pipeline

Focus on Sentinel-1 GRD data first since its on AWS. Maybe later we can add terrain corrected imagery from other sources.

Done


Add a height parameter to Transaction

It would be nice to get the height of transactions (maybe just have 0 for unconfirmed/unknown)
All json representations of transactions seem to have a height field:
https://testnodes.wavesnodes.com/api-docs/index.html#!/transactions/addressLimit

Method Node.GetTransactionHeight(string transactionId) was added


Screenshot with Droste effect

Just for the fun of it...
It would be nice if we could have droste-effect on the documentation screenshot.
See the screenshot.
If visual changes happen, we have to recreate the screenshot. I'd suggest a Pillow script and a clear instruction to make creating the screenshot repeatable.
Mockup:

Can I work on this?
Though I did not understand it exactly. Should be make just a UI design of screenshot change?

Yes, you can!
Realise that this is a nice to have with super low priority. It is a fun coding exercise. Nothing more.

We have removed the screenshot from the docs (which I also prefer as this was always confusing to me). I think this can be closed now.


False Positive on zipkin-sender-activemq-client-2.11.0.jar

False positive on library zipkin-sender-activemq-client-2.11.0.jar - reported as cpe:2.3:a:apache:activemq:2.11.0:*:*:*:*:*:*:*
Transitive dependency of
runtimeOnly ('org.springframework.cloud:spring-cloud-starter-zipkin:2.2.0.RELEASE')

Looks similar to #1681 and #2334 (all activemq confusions)

Thanks @jeremylong!


{Compute} Modify license type

Feature request: #20667
Description

The request from https://github.com/Azure/azure-cli/issues/20667#issuecomment-994627630
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Compute


Fixes for the Windows build

These commits fix the Windows build which was broken before (tested with VS2017). I also tested on macOS (Xcode 10) to make sure I didn't introduce a regression here.

Thank you @znek !  Do you have any idea what the errors from the AppVeyor build means? https://ci.appveyor.com/project/twogood/unshield/builds/22931639

Do you have any idea what the errors from the AppVeyor build means? https://ci.appveyor.com/project/twogood/unshield/builds/22931639

I can only guess, but it looks like the linker cannot resolve the references to libz. It's unclear to determine why that is without having a look at the linker command line.
(I'm almost certain that reverting [00f4bed] will fix this, however, it's just a hackish workaround IMO).

Yeah maybe libz is there for a reason? :)

Yeah maybe libz is there for a reason? :)

It seems so. But it's just a kludge IMO. AppVeyor's build log states:

157 -- Found ZLIB: C:/Users/appveyor/scoop/apps/zlib-dev/current/lib/libz.dll.a (found version "1.2.3")

I'm pretty new to cmake, but I guess that ZLIB_LIBRARY must have been set also - and it seems to be wrong, as otherwise the kludge of providing a z argument (reversed by [00f4bed]) wouldn't be necessary.
Maybe a bit more context:
I built zlib 1.2.11 (current version) with VS2017 and cmake from source. I then provided ZLIB_INCLUDE_DIR and ZLIB_LIBRARY=C:\\Users\\…\\CMakeBuilds\\…\\install\\x64-Release\\lib\\zlibstatic.lib as arguments to the cmake build of unshield. I'd say that seems to be the modern native way to build both projects but I may be wrong. Without [00f4bed] this broke, however, due to a z library nowhere to be found (see above, there's only libzstatic.lib).

When you provide ZLIB* environment variables then you also get "Found ZLIB:" at that location, or?

David, sorry for the confusion - I just read up on cmake and now have a proper understanding what's really wrong. Could you just cherry-pick [b3aad49] and drop [00f4bed]? I'm preparing a proper fix for the latter separately.

Using ${ZLIB_LIBRARIES} looks very good. I'm not very good with CMake myself.

Is this still relevant?


Fix set app title dynamically

Set app title dynamically was broken. With this fix it's working again.

thank you!


Improve Handling of Development Dependencies

Add development dependencies as dev extra to the pyproject.toml, such that they are not installed in a standard installation (pip install gcnn), but when installed as pip install gcnn[dev]. This avoids unnecessary dependencies being installed for users and most use cases.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.


OutlinerSvgMaxLinePoints exceeded for some reason

This is a bug. Exceeded when feeding the Tischofer Höhle cave model to the cave-outliner.

Fixed.


implement missing features from openssh

retry command after adding host hash into .ssh3/known_hosts
try all available ssh agent keys
inherit PATH and other vars from daemon (actually do not know about openssh behavior, implement dropbear's -e option)

Thanks for the PR !
Can you reformat the code with go vet ?

Thanks for the PR !


[Product Homepage] Implement H1 change on the Product Home and OpCo pages

How easy would it be to implement your H1 change on the Product Home and OpCo pages?  Where I add the header (just like you did for the homepage) ?
I think it was here:  https://github.com/hlxsites/danaher-ls-aem/pull/537

Fixed by #593 537


Add func to create String and StringName Variant directly from native go string

Allows this:
NewVariantStringName(NewStringNameWithLatin1Chars("my string"))
NewVariantString(NewStringWithLatin1Chars("my string"))

It'll be nice to just need this:
NewVariantStringNameFromGoString("my string")
NewVariantStringFromGoString("my string")

going to close this out for now. a lot has changed since the ticket was opened. there are helpers to convert from go native string, godot String, and godot StringName types.


tar inside a tar

When I build a release of a test project with Elixir 1.0.5, OTP 18.0 and exrm 0.18.5, it generates me the following:

rel/test that contains the whole project, including...
rel/test/releases/0.0.1/test.tar.gz which contains the whole project including...
a smaller releases/0.0.1/test.tar.gz which contains the whole project without any following test.tar.gz

So I can understand why both the uncompressed release and the first .tar.gz would be generated, but I think the .tar.gz inside the .tar.gz is superflous (and make the thing twice bigger than necessary).
This has been tested on empty projects with just exrm 0.18.5 installed, both on Ubuntu Server 64bit and on Windows 8.1 64bit.

The nested tar is required for upgrades/downgrades, as it is used by the release installer. It does add some bulk, but as far as I can tell it is unavoidable unfortunately.

I have just test for this, and found nested tar is not necessary.
mix new test
cd test
sed 's/\[\]/[{:exrm, "~> 1.0.0-rc7"}]/' mix.exs | tee mix.exs
mix deps.get
mix release
cd rel/test/releases/0.0.1
tar xf test.tar.gz
cp -f releases/0.0.1/test.tar.gz .
rm -rf bin erts-* lib releases
cd ../../../..
sed 's/0\.0\.1/0.0.2/' mix.exs | tee mix.exs
mix release
cd rel/test/releases/0.0.2
tar xf test.tar.gz
cp -f releases/0.0.2/test.tar.gz .
rm -rf bin erts-* lib releases
cd ../..
bin/test start
bin/test upgrade 0.0.1
bin/test upgrade 0.0.2
bin/test upgrade 0.0.1
bin/test upgrade 0.0.2

You aren't deleting the tarball in your test, unless I'm missing something, seems like you just extract the contents, then delete them, but leave the tar in place. The release handler handles extracting the files it wants from the tarball. To properly test it, I believe you have to delete the nested tarball from the release tarball, and make sure it's repackaged without it, then replace the release tarball with the updated one.

The tarball is replaced by the nested tarball in previous test using cp -f releases/0.0.1/test.tar.gz ., and i have check it have no nested tarball any more.

@bitwalker Here is another test according to your suggest, it also passed.
mix new test
cd test
sed 's/\[\]/[{:exrm, "~> 1.0.0-rc7"}]/' mix.exs | tee mix.exs
mix deps.get
mix release
cd rel/test/releases/0.0.1
mkdir test
mv test.tar.gz test
cd test
tar xf test.tar.gz
find . -name *.tar.gz | xargs rm -f
tar czf test.tar.gz *
cp test.tar.gz ..
cd ..
rm -rf test
cd ../../../..
sed 's/0\.0\.1/0.0.2/' mix.exs | tee mix.exs
mix release
cd rel/test/releases/0.0.2
mkdir test
mv test.tar.gz test
cd test
tar xf test.tar.gz
find . -name *.tar.gz | xargs rm -f
tar czf test.tar.gz *
cp test.tar.gz ..
cd ..
rm -rf test
cd ../..
bin/test start
bin/test upgrade 0.0.1
bin/test upgrade 0.0.2
bin/test upgrade 0.0.1
bin/test upgrade 0.0.2

@laozhp Are you able to downgrade an upgrade as well? Going both ways is necessary for the full test.

@bitwalker Yes, upgrade|downgrade|install do the same thing, because the generated test.sh script is written as
    upgrade|downgrade|install)
        if [ -z "$2" ]; then
            echo "Missing package argument"
            echo "Usage: $REL_NAME $1 {package base name}"
            echo "NOTE {package base name} MUST NOT include the .tar.gz suffix"
            exit 1
        fi

        # Make sure a node IS running
        relx_nodetool "ping" > /dev/null
        exit_status=$?
        if [ "$exit_status" -ne 0 ]; then
            echo "Node is not running!"
            exit $exit_status
        fi

        # We have to unpack the release first in order to make sure the configuration
        # is properly updated. This also destroys the .tar.gz package (release_handler does)
        "$BINDIR/escript" "$ROOTDIR/bin/install_upgrade.escript" \
             "unpack" "$REL_NAME" "$NAME_TYPE" "$NAME" "$COOKIE" "$2"

        echo "Generating vm.args/sys.config for upgrade..."
        __release_conf="$RELEASES_DIR/$2/$REL_NAME.conf"
        __release_schema="$RELEASES_DIR/$2/$REL_NAME.schema.exs"
        __release_config="$RELEASES_DIR/$2/sys.config"
        __release_args="$RELEASES_DIR/$2/vm.args"
        __running_conf="$GENERATED_CONFIG_DIR/$REL_NAME.conf"
        __running_config="$GENERATED_CONFIG_DIR/sys.config"
        __running_args="$GENERATED_CONFIG_DIR/vm.args"
        # Make sure the .conf is copied to the running-config directory
        if [ -f "$__release_conf" ]; then
            # Preserve previous conf for reference
            if [ -f "$__running_conf" ]; then
                cp "$__running_conf" "$__running_conf.last"
            fi
            cp "$__release_conf" "$__running_conf"
        fi
        __conform="$RELEASES_DIR/$2/conform"
        # Handle the case where the target version did not bundle conform in the release
        if [ ! -f "$__conform" ]; then
            __conform="$ROOTDIR/bin/conform"
        fi
        # Generate the sys.config for the release
        # If a .conf is not provided, then preserve the last sys.config for reference, and copy the new sys.config
        # to running-config.
        if [ -f "$__running_conf" ]; then
            if [ -f "$__release_schema" ]; then
                result="$("$BINDIR/escript" "$__conform" --conf "$__running_conf" --schema "$__release_schema" --config "$__release_config" --output-dir "$RELEASES_DIR/$2")"
                exit_status="$?"
                if [ "$exit_status" -ne 0 ]; then
                    echo "Could not generate the sys.config for the new release. Please review the following files:"
                    echo "$REL_NAME.conf: $__running_conf"
                    echo "$REL_NAME.schema.exs: $__release_schema"
                    echo "sys.config: $__release_config"
                    exit "$exit_status"
                else
                  cp "$__release_config" "$__running_config"
                fi
            fi
        else
            if [ -f "$__running_config" ]; then
                cp "$__running_config" "$__running_config.last"
                cp "$__release_config" "$__running_config"
            fi
        fi
        echo "sys.config ready!"
        if [ -f "$__running_args" ]; then
          cp "$__release_args" "$__release_args.orig"
          cp "$__running_args" "$__release_args"
        else
          cp "$__release_args" "$__running_args"
        fi
        echo "vm.args ready!"

        exec "$BINDIR/escript" "$ROOTDIR/bin/install_upgrade.escript" \
             "install" "$REL_NAME" "$NAME_TYPE" "$NAME" "$COOKIE" "$2"
        ;;


Q: Disjoint Union

How do I type the function type of an object whose values are functions that take a disjoint union type as their parameter? For example:
// @flow

type Person = {
  type: 'person',
  name: string,
};

type Android = {
  type: 'android',
  manufacturer: string,
};

type Data = Person | Android;

const ToStringFuncs: { [*]: Function } = {
  person: ({ name }: Person) => name,
  android: ({ manufacturer }) => manufacturer,
};

const toString = (data: Data) => ToStringFuncs[data.type](data);

// no errors:
toString({ type: 'person', name: 'bob' });

How do I replace Function above with something more specific? If I try this:
const ToStringFuncs: { [*]: (data: Data) => string } = {

I get Property not found errors for name, manufacturer, and errors like this: Expected string literal 'android', got 'person' instead.
Is this possible with flow? Am I going about it the wrong way? Thanks!

Change your toString function to this:
const toString = (data: Data) => data.type === 'person'
  ? ToStringFuncs[data.type](data)
  : ToStringFuncs[data.type](data);

Flow needs you to make the pointless refinement first.

Thanks. Is there a way around the pointless refinement? I tried that already, and it works, but the example is artificial; in my real code there are lots more functions in the object map, so refining each one isn't super practical.
Here's a slightly more realistic example:
// @flow

type Person = {
  type: 'person',
  name: string,
};

type Android = {
  type: 'android',
  manufacturer: string,
};

type Animal = {
  type: 'animal',
  collarNum: string,
};

type Data = Person | Android | Animal;

const ToStringFuncs: { [*]: (params: any) => string } = {
  person: ({ name }) => name,
  android: ({ manufacturer }) => manufacturer,
  animal: ({ collarNum }) => collarNum,
};

const toString = (data: Data) => ToStringFuncs[data.type](data);

// no errors:
toString({ type: 'animal', collarNum: 'bob' });

I'd like to get rid of the any in the declaration of the ToStringFuncs value type, but putting in Data doesn't work.

Unfortunately I haven't figured out a way around it. There's almost no point to the ToStringFuncs object and you are probably better off with a switch:
const toString = (d: Data) => {
  switch (d.type) {
    case 'person': return d.name
    case 'android': return d.manufacturer
    case 'animal': return d.collarNum
    default: throw new Error(`Flow doesn't understand exhaustive checks`)
  }
}

Closing since * are no longer supported


fix: remove POSTable models from cachable apis

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


The labels added into metadata of spark jobs are not added to its driver and executor pods.

Hi team, I am using Kustomize to submit my spark jobs for several environments. The labels that I try to patch in are applied to the metadata of my SparkApplication but are not applied to my worker and executor pods. I need these labels to easily filter over the pods on the basis of the environment. Following is an example to demonstrate the scenario:
kind: SparkApplication
  labels:
    environment: APPLIED_BY_KUSTOMIZE
spec:
  driver:
    labels:
      version: DRIVER_VERSION
  executor:
    labels:
      version: EXECUTOR_VERSION

Now when I try to do
kubectl get pods my-spark-driver --show-labels
The output is
NAME                READY   STATUS    RESTARTS   AGE   LABELS
my-spark-driver     1/1     Running   0          29h   version=DRIVER_VERSION, some_auto_generated_labels

The driver pod contains "version: DRIVER_VERSION" as the label but not "environment: APPLIED_BY_KUSTOMIZE". And the same behavior for executor as well. This causes a lot of problems to filter the drivers and executors on the basis of the environment and some other use cases.
Please help with this. Thank You

I think it's worth fixing(populate applicate labels to driver and executors pods, by default). It will have the consistent behavior as other default operators, such as deployment, replicaset, etc (although there are some differences on yaml file). The only use case which will be potentially broken is that we want application labels totally different from its driver and executors. But I doubt that is a real use case.
For the fix itself:

We could add label object under spec, and force the two values(from spec.label and metadata.label) are always the same, just like other default operators do. But I think it is un-necessary and breaks the backward-compatibility
We could simply let driver/executor inherent the application labels from the values of metadata.label which should be enough.

Maybe, we could add separate flag(something like 'labelsInherent') under spec block, by default the value is False and if the user want to populate the application labels, they can set as True. But I really do not think this is necessary.

@liyinan926 I would like to hear your suggestions on this one. If you are ok with it, i can start a RP on it.

@gongx Thanks for the detailed write up. I think option 2 sounds good as it would be backward compatible. I don't think it's necessary to have a field that controls label inheritance either. This could be as simple as applying labels in the SparkApplication resources and applying the ones defined in driver and executor specs. Labels defined in driver and executor specs will override the ones in metadata of the SparkApplication resource. Appreciate and looking forward to the PR.

@liyinan926 could you take a look at this PR: https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/940, please?

@gongx reviewed and merged your PR. Thanks for fixing this issue!


Add support for managing Azure AD Directory roles (graphrbac)

Feature Request
Can you add support for managing Azure AD Directory Roles to the SDK? (graphrbac)
MS Graph links:
https://docs.microsoft.com/en-us/graph/api/resources/directoryrole?view=graph-rest-beta
https://docs.microsoft.com/en-us/graph/api/resources/directoryroletemplate?view=graph-rest-beta
And here are the links for Azure AD API:
https://docs.microsoft.com/en-us/previous-versions/azure/ad/graph/api/directoryroles-operations

This is currently blocked by https://github.com/Azure/azure-rest-api-specs/issues/5383

Isn't the Azure AD Graph API deprecated and the MS Graph API should be used instead anyways?

Unfortunately, there is no golang binding yet for the MS Graph API yet. Vote for it on https://microsoftgraph.uservoice.com/forums/920506-microsoft-graph-feature-requests/suggestions/37576909-graph-api-golang-sdk

@ArcturusZhang, i can't seem to find support for directory roles in the SDK, am i just missing it? or should this not have been closed


[Wallet] Incorrect balance shown upon first app load in non USD currency

Expected Behavior
Loading icon / no balance shown instead of assuming 1:1 rate before it's fetched
Current Behavior
Short moment when exchange rate is loading that incorrect balance is shown as 1:1 rate is assumed- this can be a scary experience as the balance can be 100 times smaller for Kenyan Shillings for example. Note that this is more pronounced in low connectivity environments

I believe this has been addressed


kube-aws apply (update) The CIDR 'X.X.X.X/XX' conflicts with another subnet

Attempts to update an existing cluster encounters messages such as the below, leading to a failure and Rollback:
The CIDR 'X.X.X.X/XX' conflicts with another subnet (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSubnet.Conflict; Request ID: 5c450d2d-7c0a-474e-9e4e-da71ef7deb75)"

The conflict occurs as part of the process to create the Network Stack
kube-aws version v0.11.0

Yeah! Can you (1) remove the another, conflicting subnet in your VPC, or (2) change your subnet's instanceCIDR not to conflict with existing ones (3) use another VPC?

Yes. Or how about reusing existing subnets?

The subnets we have in cluster.yaml are the same subnets we set the cluster up on, Hence were hoping to keep using them as part of the upgrade.
However looks like this will not be possible

Oh, are you saying that you have not altered subnets: section of your cluster.yaml at all, from the initial creation to the upgrade?

Are you sure you've specified subnets[].id in your cluster.yaml?

Yes I have populated the cluster.yaml with the subnet information
This config was used to bring up the cluster, and has remained unchanged as part of the update
subnets:
    - name: kservice-apse2a-sn
      private: false
      availabilityZone: ap-southeast-2a
      instanceCIDR: "<IP_ADDRESS>/26"
      routeTable:
       id: "rtb-123456"

    - name: kservice-apse2b-sn
      private: false
      availabilityZone: ap-southeast-2b
      instanceCIDR: "<IP_ADDRESS>/26"
      routeTable:
        id: "rtb-123456"

    - name: knode-apse2a-sn
      private: true
      availabilityZone: ap-southeast-2a
      instanceCIDR: "<IP_ADDRESS>/26"
      routeTable:
        id: "rtb-abcdbb"

    - name: knode-apse2b-sn
      private: true
      availabilityZone: ap-southeast-2b
      instanceCIDR: "<IP_ADDRESS>/26"
      routeTable:
        id: "rtb-abcdbb"

@devdemos Ah, gotcha. Sry I had missed that you're upgrading from the old release of kube-aws that didn't have the Network stack.
Yeah, as CloudFormation on which kube-aws depends doesn't support migrating subnets from one stack to another, we have no way other than adding an another subnet which different CIDR while migrating.

Ok, Thank you


Vim crashes at start

Describe the bug
Vim crashes at start.
To Reproduce
Detailed steps to reproduce the behavior:

Run vim or gvim after fresh install on Windows 10 machine

Expected behavior
Vim starts
Environment:

Vim version: 8.2.3444.0
OS: Windows 10

Additional context
Error: The application was unable to start correctly (0xc0000005)
ID of the faulty procces: 0xdec
I don't know how to deal with this problem or how to debug it further.
If you deem this report not sufficient please tell me how to obtain more information about the problem.

Does it work when starting vim --clean

No, it doesn't.
Exactly same behaviour is observed => nothing happens at all, AppCrash log can be seen in Event Viewer

So is this the release from https://github.com/vim/vim-win32-installer/releases ? The current information isn't very useful. We may need your help to produce better stack traces. You can possibly use the .pdb files for your release from https://github.com/vim/vim-win32-installer/releases
However I do not actually know how to use those. According to this microsoft documentation https://docs.microsoft.com/en-us/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger?view=vs-2019 you would need microsoft visual studio to debug this crash

Yes it is a release from https://github.com/vim/vim-win32-installer/releases
I opened gVim in a Visual Studio and included .pdb files but as soon as I started debugging I received a Search Folder dialog VS prompting me to locate mbyte.c which I don't have
I suppose I need vim source code to succesfully debug this problem

yes, quite possible. Can you try with the source and point us to a useful stacktrace?

@ https://github.com/vim/vim/issues/8916#issuecomment-930335789
Hello ! Could you build from vim source code ( the src vim folder ) on you windozs in debug mode with nmake script make_mvc,mak ?
To help   find the crash line change in make_mvc,mak file the CFLAGS, and add these options to cl compiler:

/FAcs /Fa$(OUTDIR) /Fo$(OUTDIR)
also conflags
conflags = /nologo /subsystem:$(SUBSYSTEM) /DYNAMICBASE:NO /FIXED /NXCOMPAT /MACHINE:X86 /opt:ref
I attached a modified file of make_mvc,mak ...
Before to compile, in VS studio 2019 Community ed, you have to start the cmd :

x86 Native Tools Command Prompt for VS 2019,
to configure compiler and linker PATH.

In command prompt windows build vim executable with, change to the vim source code, src folder, by example  ;

cd  c:\your_vim_folder\vim-51491adfa86fd66a857cd7ec50d0b57dbdf3da59\src

and compile

nmake -f make_mvc.mak FEATURES=HUGE MBYTE=YES GETTEXT=NO MAP=YES
Make_mvc.mak.txt

Actually, you don't need to compile Vim by yourself.

2. I opened gVim in a Visual Studio and included .pdb files but as soon as I started debugging I received a Search Folder dialog VS prompting me to locate mbyte.c which I don't have

You should download the corresponding version of the Vim source code by the following commands (using Git for Windows):
git clone https://github.com/vim/vim
cd vim
git checkout v8.2.XXXX

any update or can this issue be closed?

Sorry I didn't have time to sit down and work on it.
@zuloloxi
This part is confusing me a lot and I don't know what to do:
/FAcs /Fa$(OUTDIR) /Fo$(OUTDIR)
also conflags
conflags = /nologo /subsystem:$(SUBSYSTEM) /DYNAMICBASE:NO /FIXED /NXCOMPAT /MACHINE:X86 /opt:ref
I attached a modified file of make_mvc,mak ...
Before to compile, in VS studio 2019 Community ed, you have to start the cmd :
x86 Native Tools Command Prompt for VS 2019,
to configure compiler and linker PATH.

any update here?

So the issue was caused by my windows account user name. It contained characters from czech alphabet which broke the program.
My username: Tomáš
Issue was solved by creating account with ascii characters


Service Principal to a group

Hello team,
I've a question regarding the statement found in the Wiki:
"currently if you add a service principal to a group, and then assign an app role to that group, Azure AD does not add the roles claim to tokens it issues."
It seems to me a glitch, is there a bug filled somewhere on github ? Or, do you have any ETA for when it will be fixed ?
Thanks,
Christian.
[Enter feedback here]

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

ID: 9939fc33-8762-3104-eae0-08250c508100
Version Independent ID: 9c6fa664-df37-40aa-f46e-9e59f79ae215
Content: Add app roles and get them from a token - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md
Service: active-directory
Sub-service: develop
GitHub Login: @kalyankrishna1
Microsoft Alias: kkrishna

@beowulf79
Thanks for your feedback! We will investigate and update as appropriate.

@beowulf79
Thank you for your time and patience throughout this issue. I've reached out to our engineering team and will update as soon as possible.

Thanks for the update.
Christian.
On Fri, 9 Jul 2021, 19:54 James Tran-MSFT, @.***> wrote:

@beowulf79 https://github.com/beowulf79
Thank you for your time and patience throughout this issue. I've reached
out to our engineering team and will update as soon as possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/78063#issuecomment-877357900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5R3EUMF4DTEAJXLTLGRCLTW4ZWXANCNFSM5AAX64VA
.

@beowulf79
Thank you for your time and patience throughout this issue.
When it comes to getting the roles claim after adding your service principal to a group, are you able to share the token you received? Or were you able to reproduce this within your environment?

Closing this issue since this is by design.


add API to get progress of subtasks with given state

With this API, we can get

Progress of subtasks with given state of specified minion worker IDs, or
Progress of subtasks with given state of all minion workers if no minion worker ID is specified

This API is helpful for minion debugging.

Codecov Report

Merging #10132 (f03fabd) into master (7de02e8) will decrease coverage by 45.89%.
The diff coverage is 12.34%.

@@              Coverage Diff              @@
##             master   #10132       +/-   ##
=============================================
- Coverage     70.55%   24.66%   -45.90%
+ Complexity     5745       44     -5701
=============================================
  Files          1995     1989        -6
  Lines        108195   108177       -18
  Branches      16436    16450       +14
=============================================
- Hits          76341    26678    -49663
- Misses        26523    78687    +52164
+ Partials       5331     2812     -2519

Flag
Coverage Δ

integration1
24.66% <12.34%> (-0.16%)
:arrow_down:

integration2
?

unittests1
?

unittests2
?

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

Impacted Files
Coverage Δ

...roller/api/resources/PinotTaskRestletResource.java
2.67% <0.00%> (-0.30%)
:arrow_down:

...lix/core/minion/PinotHelixTaskResourceManager.java
34.74% <0.00%> (-13.97%)
:arrow_down:

...inion/api/resources/PinotTaskProgressResource.java
0.00% <0.00%> (ø)

...apache/pinot/minion/event/MinionEventObserver.java
25.00% <0.00%> (-25.00%)
:arrow_down:

...pache/pinot/minion/event/MinionEventObservers.java
41.53% <0.00%> (-45.56%)
:arrow_down:

...che/pinot/minion/event/MinionProgressObserver.java
56.81% <44.44%> (-20.69%)
:arrow_down:

...org/apache/pinot/minion/event/MinionTaskState.java
100.00% <100.00%> (ø)

...in/java/org/apache/pinot/spi/utils/BytesUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/BaseRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/NoOpRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1487 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

cc @sajjad-moradi

@zhtaoxiang Thanks for writing an extensive testing cases 👍 Merging PR. This looks good to me.

Thanks for adding this new API! Please also update the pinot documentation about this change


add pagerduty pack

sorely missing :)

@pdeva Awesome! Thanks for the suggestion. We'll add this to our list of integrations in progress. :+1:

Resolved by https://github.com/StackStorm/st2contrib/pull/123


Make possible to use models in pydeeplearn to be online

It would be nice if neural network could be used for online training (ok ptretraining should be offline or none pretraining at all (as there is another issue)). This could aim for temporal difference learning techniques, when neural network needs to be online  (there is no offline version of it)

possible solution would be adding onlineTrain method which will cal ffineTune method wtih 1 epoch.

I currently have no plans to implement online learning for pydeeplearn, but feel free to send a PR if you want to implement it and I will have a look.

well... :) I've started learning theano for this purpose. I am going to use your library in my comming thesis, I really need to get into python and theano, but there is no time.


Github: Specific action versions

Fixed Github action versions.

I think that we can update dependabot for that. I'll investigate it.


Question about generating trajectory command token in ARTRACK v2

Hi.
Thanks for your great work !
I was reading paper but i couldn't understand  about generating trajectory command token, the green one.
I understand about not using intra-frame autoregression, not generating xmin, ymin, xmax, ymax one by one.
Could you explain about how does the past trajectories are utilized to make command token?
Maybe concating past trajectories and learnable command tokens and use self-attention?

The command tokens are just 4 learnable tokens. The past trajectories is not used to make command token, which just concat with the 4 command tokens. Maybe our figure is not very clear about that, sorry for make you misunderstand that.
And answer is yes, we concat the past trajectories and command tokens with self-attention.

Thanks for a quick reply!
"And answer is yes, we concat the past trajectories and command tokens with self-attention." when doing this
another transformer encoder is utilized and than you take only command token variable part from the output of the encoder and feed to the main transformer encoder in the Figure 2 ?
or
The concat(trajectories, command token) is directly fed to the transformer encoder(the one in the figure 2 of ARTRACKv2 paper)  along with search, template, appearance token, confidence token ?
and also I couldn't figure out which part of the code I should take a look to check trajectory token part. Can you  show me where to look?

We concat trajectory, command tokens, search, template and appearance, and confidence tokens. Then we fed them into the encoder.
You can check that in lib/models/ostrack/base_backbone.py, you can find that in function forward_features

Thank you!


Missing gettext on Jessie (not tried for others)

When attempting to edit my crontab, I got an error about missing gettext. It's used by the /usr/bin/select-editor script, and probably others as well.
Steps to reproduce:

Install a fresh Jessie
Log in
Enter the command "crontab -e"

Result:
# crontab -e
no crontab for root - using an empty one

/usr/bin/select-editor: 1: /usr/bin/select-editor: gettext: not found
 'select-editor'.
/usr/bin/select-editor: 1: /usr/bin/select-editor: gettext: not found
  1. /bin/nano        <----
  2. /usr/bin/mg
  3. /usr/bin/vim.basic

/usr/bin/select-editor: 32: /usr/bin/select-editor: gettext: not found
 1-3 [1]:

Expected result:
# crontab -e
no crontab for root - using an empty one

Select an editor.  To change later, run 'select-editor'.
  1. /bin/nano        <---- easiest
  2. /usr/bin/mg
  3. /usr/bin/vim.basic

Choose 1-3 [1]:

Or you can just reproduce by typing "select-editor" obviously. But I had the output of crontab ready to copy/paste...


Feature request - SQL queries for active record

Big feature request I know.  :)
If this library could build active record scopes based on the filter params it would be god like!
Also of interest, generic SQL queries.   (That might be easier than using active record)

Hi @montulli
Thanks for the request!
This has sort of already been built.
https://querybuilder.js.org/plugins.html#sql-support
The jQuery plugin can generate the sql for you - you could then send that through to your server.
Pretty scary getting sql from a frontend... It should be possible to use something like https://github.com/cowboyd/therubyracer to run it server-side tho.

I can't trust SQL coming from the front end and running JavaScript on the server side seems inefficient.    I have  a working implementation now of SQL generation in RUBY in my branch that is here:  https://github.com/jetinsight/jquery_query_builder-rails
If you are interested, I can make a pull request so you can review it.   I'm happy to make changes to suit your requirements.


refactor: remove wandb from feature generation

Current dependencies on/for this PR:

main

PR #759   👈

This stack of pull requests is managed by Graphite.


document required storage

Update documentation to tell users how much disk storage is required for each UCVMC directory.
-bash-4.2$ du -sh largefiles
7.8G	largefiles
-bash-4.2$ du -sh test3
25G	test3
-bash-4.2$ du -sh /home/scec-00/maechlin/t1
20G	/home/scec-00/maechlin/t1

Added storage requirements into installation discussion on github wiki