COMPILE_ERROR_OUTPUT : [2023-02-27 16:36:39] [build-stderr] In file included from /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/CStandardLibraryHeadersAreDeprecated.cpp:27:
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:40:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic _Bool atomic_bool;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:41:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic char atomic_char;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:42:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic signed char atomic_schar;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:43:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned char atomic_uchar;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:44:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic short atomic_short;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:45:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned short atomic_ushort;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:46:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic int atomic_int;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:47:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned int atomic_uint;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:48:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic long atomic_long;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:49:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned long atomic_ulong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:50:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic long long atomic_llong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:51:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned long long atomic_ullong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:52:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __CHAR16_TYPE__ atomic_char16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:53:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __CHAR32_TYPE__ atomic_char32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:54:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __WCHAR_TYPE__ atomic_wchar_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:55:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST8_TYPE__ atomic_int_least8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:56:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST8_TYPE__ atomic_uint_least8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:57:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST16_TYPE__ atomic_int_least16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:58:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST16_TYPE__ atomic_uint_least16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:59:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST32_TYPE__ atomic_int_least32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:60:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST32_TYPE__ atomic_uint_least32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:61:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST64_TYPE__ atomic_int_least64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:62:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST64_TYPE__ atomic_uint_least64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:63:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST8_TYPE__ atomic_int_fast8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:64:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST8_TYPE__ atomic_uint_fast8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:65:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST16_TYPE__ atomic_int_fast16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:66:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST16_TYPE__ atomic_uint_fast16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:67:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST32_TYPE__ atomic_int_fast32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:68:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST32_TYPE__ atomic_uint_fast32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:69:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST64_TYPE__ atomic_int_fast64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:70:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST64_TYPE__ atomic_uint_fast64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:71:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INTPTR_TYPE__ atomic_intptr_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:72:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINTPTR_TYPE__ atomic_uintptr_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:73:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __SIZE_TYPE__ atomic_size_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:74:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __PTRDIFF_TYPE__ atomic_ptrdiff_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:75:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INTMAX_TYPE__ atomic_intmax_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:76:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINTMAX_TYPE__ atomic_uintmax_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:218:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic struct
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:225:3: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  } atomic_flag;
                       [2023-02-27 16:36:39] [build-stderr]    ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]    atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:230:49: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern _Bool atomic_flag_test_and_set (volatile atomic_flag *);
                       [2023-02-27 16:36:39] [build-stderr]                                                  ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                  atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:233:58: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern _Bool atomic_flag_test_and_set_explicit (volatile atomic_flag *,
                       [2023-02-27 16:36:39] [build-stderr]                                                           ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                           atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:238:41: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern void atomic_flag_clear (volatile atomic_flag *);
                       [2023-02-27 16:36:39] [build-stderr]                                          ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                          atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:240:50: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern void atomic_flag_clear_explicit (volatile atomic_flag *, memory_order);
                       [2023-02-27 16:36:39] [build-stderr]                                                   ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                   atomic_load
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:1:19: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]  void test_des_1() throw(int);        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                    ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:2:19: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]  void test_des_2() throw(int, float); // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                    ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:8:13: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    Foo(bool) throw(int);            // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]              ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:9:18: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    Foo(int, bool) throw(int, bool); // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                   ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp: In member function 'Ref& Ref::operator=(Ref)':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:5:24: warning: no return statement in function returning non-void [-Wreturn-type]
                       [2023-02-27 16:36:40] [build-stderr]    Ref &operator=(Ref) {}
                       [2023-02-27 16:36:40] [build-stderr]                         ^
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp: In function 'void test()':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:16:5: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    ++b;        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]      ^
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:17:4: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    b++;        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]     ^~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:18:11: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    r.getX()++; // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]            ^~
                       [2023-02-27 16:36:40] [build-stderr] In file included from /usr/include/c++/8/backward/strstream:50,
                       [2023-02-27 16:36:40] [build-stderr]                  from /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp:1:
                       [2023-02-27 16:36:40] [build-stderr] /usr/include/c++/8/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. [-Wcpp]
                       [2023-02-27 16:36:40] [build-stderr]  #warning \
                       [2023-02-27 16:36:40] [build-stderr]   ^~~~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp: In function 'void test_istrstream()':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp:13:13: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
                       [2023-02-27 16:36:40] [build-stderr]    char *s = "foo";
                       [2023-02-27 16:36:40] [build-stderr]              ^~~~~
                       [2023-02-27 16:36:41] [ERROR] Spawned process exited abnormally (code 1; tried to run: [/__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql/tools/linux64/preload_tracer, g++, -std=c++14, -fsyntax-only, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/CStandardLibraryHeadersAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/ImplicitCopyAssignmentOperatorIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/ImplicitCopyConstructorIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/RegisterKeywordIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/test.cpp])

PACKAGE              : Toolchain
SUITE                : AUTOSAR
RULE                 : A1-1-1
COMPILE_PASS         : False
TEST_DIFFERENCE      :
TEST_PASS            : False
QUERY                : StrstreamTypesAreDeprecated
COMPILE_ERROR_OUTPUT : [2023-02-27 16:36:39] [build-stderr] In file included from /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/CStandardLibraryHeadersAreDeprecated.cpp:27:
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:40:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic _Bool atomic_bool;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:41:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic char atomic_char;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:42:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic signed char atomic_schar;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:43:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned char atomic_uchar;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:44:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic short atomic_short;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:45:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned short atomic_ushort;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:46:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic int atomic_int;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:47:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned int atomic_uint;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:48:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic long atomic_long;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:49:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned long atomic_ulong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:50:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic long long atomic_llong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:51:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic unsigned long long atomic_ullong;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:52:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __CHAR16_TYPE__ atomic_char16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:53:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __CHAR32_TYPE__ atomic_char32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:54:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __WCHAR_TYPE__ atomic_wchar_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:55:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST8_TYPE__ atomic_int_least8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:56:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST8_TYPE__ atomic_uint_least8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:57:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST16_TYPE__ atomic_int_least16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:58:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST16_TYPE__ atomic_uint_least16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:59:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST32_TYPE__ atomic_int_least32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:60:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST32_TYPE__ atomic_uint_least32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:61:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_LEAST64_TYPE__ atomic_int_least64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:62:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_LEAST64_TYPE__ atomic_uint_least64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:63:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST8_TYPE__ atomic_int_fast8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:64:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST8_TYPE__ atomic_uint_fast8_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:65:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST16_TYPE__ atomic_int_fast16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:66:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST16_TYPE__ atomic_uint_fast16_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:67:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST32_TYPE__ atomic_int_fast32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:68:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST32_TYPE__ atomic_uint_fast32_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:69:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INT_FAST64_TYPE__ atomic_int_fast64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:70:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINT_FAST64_TYPE__ atomic_uint_fast64_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:71:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INTPTR_TYPE__ atomic_intptr_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:72:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINTPTR_TYPE__ atomic_uintptr_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:73:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __SIZE_TYPE__ atomic_size_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:74:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __PTRDIFF_TYPE__ atomic_ptrdiff_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:75:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __INTMAX_TYPE__ atomic_intmax_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:76:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic __UINTMAX_TYPE__ atomic_uintmax_t;
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:218:9: error: '_Atomic' does not name a type
                       [2023-02-27 16:36:39] [build-stderr]  typedef _Atomic struct
                       [2023-02-27 16:36:39] [build-stderr]          ^~~~~~~
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:225:3: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  } atomic_flag;
                       [2023-02-27 16:36:39] [build-stderr]    ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]    atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:230:49: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern _Bool atomic_flag_test_and_set (volatile atomic_flag *);
                       [2023-02-27 16:36:39] [build-stderr]                                                  ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                  atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:233:58: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern _Bool atomic_flag_test_and_set_explicit (volatile atomic_flag *,
                       [2023-02-27 16:36:39] [build-stderr]                                                           ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                           atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:238:41: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern void atomic_flag_clear (volatile atomic_flag *);
                       [2023-02-27 16:36:39] [build-stderr]                                          ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                          atomic_load
                       [2023-02-27 16:36:39] [build-stderr] /usr/lib/gcc/x86_64-linux-gnu/8/include/stdatomic.h:240:50: error: 'atomic_flag' does not name a type; did you mean 'atomic_load'?
                       [2023-02-27 16:36:39] [build-stderr]  extern void atomic_flag_clear_explicit (volatile atomic_flag *, memory_order);
                       [2023-02-27 16:36:39] [build-stderr]                                                   ^~~~~~~~~~~
                       [2023-02-27 16:36:39] [build-stderr]                                                   atomic_load
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:1:19: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]  void test_des_1() throw(int);        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                    ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:2:19: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]  void test_des_2() throw(int, float); // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                    ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:8:13: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    Foo(bool) throw(int);            // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]              ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp:9:18: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    Foo(int, bool) throw(int, bool); // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]                   ^~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp: In member function 'Ref& Ref::operator=(Ref)':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:5:24: warning: no return statement in function returning non-void [-Wreturn-type]
                       [2023-02-27 16:36:40] [build-stderr]    Ref &operator=(Ref) {}
                       [2023-02-27 16:36:40] [build-stderr]                         ^
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp: In function 'void test()':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:16:5: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    ++b;        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]      ^
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:17:4: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    b++;        // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]     ^~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp:18:11: warning: use of an operand of type 'bool' in 'operator++' is deprecated [-Wdeprecated]
                       [2023-02-27 16:36:40] [build-stderr]    r.getX()++; // NON_COMPLIANT
                       [2023-02-27 16:36:40] [build-stderr]            ^~
                       [2023-02-27 16:36:40] [build-stderr] In file included from /usr/include/c++/8/backward/strstream:50,
                       [2023-02-27 16:36:40] [build-stderr]                  from /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp:1:
                       [2023-02-27 16:36:40] [build-stderr] /usr/include/c++/8/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. [-Wcpp]
                       [2023-02-27 16:36:40] [build-stderr]  #warning \
                       [2023-02-27 16:36:40] [build-stderr]   ^~~~~~~
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp: In function 'void test_istrstream()':
                       [2023-02-27 16:36:40] [build-stderr] /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp:13:13: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
                       [2023-02-27 16:36:40] [build-stderr]    char *s = "foo";
                       [2023-02-27 16:36:40] [build-stderr]              ^~~~~
                       [2023-02-27 16:36:41] [ERROR] Spawned process exited abnormally (code 1; tried to run: [/__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql/tools/linux64/preload_tracer, g++, -std=c++14, -fsyntax-only, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/CStandardLibraryHeadersAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/DynamicExceptionsAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/ImplicitCopyAssignmentOperatorIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/ImplicitCopyConstructorIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/IncrementOperatorWithBoolOperandIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/RegisterKeywordIsDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.cpp, /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/test.cpp])

PACKAGE              : Pointers
SUITE                : CERT-C++
RULE                 : EXP57-CPP
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : DeletingPointerToIncompleteClass
COMPILE_ERROR_OUTPUT :

PACKAGE              : Pointers
SUITE                : CERT-C++
RULE                 : EXP57-CPP
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : CastOfPointerToIncompleteClass
COMPILE_ERROR_OUTPUT :

PACKAGE              : Pointers
SUITE                : AUTOSAR
RULE                 : A5-3-3
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : DeletingPointerToIncompleteType
COMPILE_ERROR_OUTPUT :

PACKAGE              : Iterators
SUITE                : CERT-C++
RULE                 : CTR51-CPP
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : UsesValidContainerElementAccess
COMPILE_ERROR_OUTPUT :

PACKAGE              : Iterators
SUITE                : CERT-C++
RULE                 : STR52-CPP
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : UseValidReferencesForElementsOfString
COMPILE_ERROR_OUTPUT :

PACKAGE              : Iterators
SUITE                : AUTOSAR
RULE                 : A23-0-2
COMPILE_PASS         : True
TEST_DIFFERENCE      :
TEST_PASS            : True
QUERY                : ValidContainerElementAccess
COMPILE_ERROR_OUTPUT :

🤖 Beep Boop! clang/cpp/x86_64 Matrix Testing for this PR has been completed. See below for the results!

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : RegisterKeywordIsDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : CStandardLibraryHeadersAreDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : ImplicitCopyAssignmentOperatorIsDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : ImplicitCopyConstructorIsDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : IncrementOperatorWithBoolOperandIsDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      : --- expected
                       +++ actual
                       @@ -1,14 +1,21 @@
                       +| StrstreamTypesAreDeprecated.cpp:4:21:4:21 | call to strstreambuf | Use of <strstream> class 'std::strstreambuf' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:4:21:4:21 | x | Use of <strstream> class 'std::strstreambuf' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:5:1:5:1 | call to ~strstreambuf | Use of <strstream> class 'std::strstreambuf' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:7:20:7:21 | f1 | Use of <strstream> class 'std::strstreambuf' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:8:10:8:32 | call to strstreambuf | Use of <strstream> class 'std::strstreambuf' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:12:19:12:20 | i1 | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:12:22:12:27 | call to istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:14:19:14:20 | i2 | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:14:22:14:23 | call to istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:16:19:16:20 | i3 | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:16:22:16:37 | call to istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:17:1:17:1 | call to ~istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:17:1:17:1 | call to ~istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:17:1:17:1 | call to ~istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:19:18:19:19 | f2 | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:20:10:20:31 | call to istrstream | Use of <strstream> class 'std::istrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:24:19:24:19 | call to ostrstream | Use of <strstream> class 'std::ostrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:24:19:24:19 | o | Use of <strstream> class 'std::ostrstream' is deprecated. |
                       +| StrstreamTypesAreDeprecated.cpp:25:1:25:1 | call to ~ostrstream | Use of <strstream> class 'std::ostrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:27:18:27:19 | f3 | Use of <strstream> class 'std::ostrstream' is deprecated. |
                        | StrstreamTypesAreDeprecated.cpp:28:10:28:30 | call to ostrstream | Use of <strstream> class 'std::ostrstream' is deprecated. |
                       [1/1 comp 1m16s eval 5.8s] FAILED(RESULT) /__w/codeql-coding-standards-release-engineering/codeql-coding-standards-release-engineering/codeql-coding-standards/cpp/autosar/test/rules/A1-1-1/StrstreamTypesAreDeprecated.qlref

RULE                 : A1-1-1
TEST_PASS            : False
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : StrstreamTypesAreDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A1-1-1
TEST_PASS            : True
PACKAGE              : Toolchain
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : DynamicExceptionsAreDeprecated

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : EXP57-CPP
TEST_PASS            : True
PACKAGE              : Pointers
SUITE                : CERT-C++
COMPILE_ERROR_OUTPUT :
QUERY                : DeletingPointerToIncompleteClass

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : EXP57-CPP
TEST_PASS            : True
PACKAGE              : Pointers
SUITE                : CERT-C++
COMPILE_ERROR_OUTPUT :
QUERY                : CastOfPointerToIncompleteClass

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A5-3-3
TEST_PASS            : True
PACKAGE              : Pointers
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : DeletingPointerToIncompleteType

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : CTR51-CPP
TEST_PASS            : True
PACKAGE              : Iterators
SUITE                : CERT-C++
COMPILE_ERROR_OUTPUT :
QUERY                : UsesValidContainerElementAccess

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : STR52-CPP
TEST_PASS            : True
PACKAGE              : Iterators
SUITE                : CERT-C++
COMPILE_ERROR_OUTPUT :
QUERY                : UseValidReferencesForElementsOfString

COMPILE_PASS         : True
TEST_DIFFERENCE      :
RULE                 : A23-0-2
TEST_PASS            : True
PACKAGE              : Iterators
SUITE                : AUTOSAR
COMPILE_ERROR_OUTPUT :
QUERY                : ValidContainerElementAccess

🤖 Beep Boop! Matrix Testing for this PR has been completed. If no reports were posted it means this PR does not contain things that need matrix testing!


add export for module augmentation

in order to prevent the module augmentation being discarded by e.g. tree shaking

Fixes #

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

in order to prevent the module augmentation being discarded by e.g. tree shaking

not sure i understand what this means. the export is optional here, since it is inside an ambient declaration, and all ambient declarations are assumed to be exported.
This is an interface, and should not have any tree shaking implications.

@mhegazy we faced a problem when using module augmentation without redeclaring the export, where the compiler did not recognized the merged declaration. We were able to solve it with the export keyword.
Moreover, for unit tests with karma, in the file augmenting a module, we needed to explicitly re-export the interface and import it in a test in order for the compiler to know about the augmented interface and prevent tree shaking.
However, if you think this is not directly related to TypeScript, but to the deployment software (angular CLI, karma, etc.), you can close the pull request.

This does not sound like a documentation issue but more of a bug. feel free to file a new issue with more details on https://github.com/Microsoft/TypeScript


Add pagination to admin cluster list API

What this PR does / why we need it:
This PR makes the cluster list API pageable. Here is the corresponding change to the geneva action codebase.
This PR overrides https://github.com/Azure/ARO-RP/pull/705 (I couldn't push to that PR)
fixes #703
My changes ontop of Jim's
@jim-minter I added a commit to your PR that fixes listing with a filter, the problem is

we have changed from [cluster, cluster] to {value: [cluster, cluster], nextPageLink: "url"}
the jsmespath is run on the server so we have to page and run the filter multiple times

My solution to the above is to attempt to "scope" the jmespath query to ".value" so that the nextPageLink is never butchered. My specific implementation in adminJmespathFilter() does not feel very elegant, so open to better ones..
Note: by running jmespath on the server with paging we will break things like [8:12] (our paging default is 10 clusters per page). so instead of getting 8,9,10,11 we will get 8,9,18,19,...
Test plan for issue:

Added unit tests for jmespath filtering
Manually tested the GA PR against this PR in a dev setup.

It would be great to get the admin e2e tests (#802)  in so we can start adding to them..
Is there any documentation that needs to be updated for this PR?
No, the geneva action will behave the same.

Note: by running jmespath on the server with paging we will break things like [8:12] (our paging default is 10 clusters per page). so instead of getting 8,9,10,11 we will get 8,9,18,19,...

Opened #862 for this.

https://github.com/Azure/ARO-RP/pull/869 introduces a TODO in an e2e which this PR will need to fix to avoid a potential flake.

@m1kola @mjudeikis can you PTAL?

fyi: https://msazure.visualstudio.com/One/_git/Compute-ARO-GenevaActions/pullrequest/3381555

All looks good to me exept from one remaining thing with code duplication.
I'll be happy to approve this PR as soon as we get rid of this duplication.

Sorry @m1kola this just totally slipped off my radar. I'll update now.

/azp run e2e

/azp run e2e

/azp run e2e

/azp run e2e


Support Arbitrary Quad Zones

Using 4 points to determine a zone will be better than 2. Having only 2 points to represent a zone is very limiting.

Yeah I agree.


Control of heating valve

Hi, I found your project very interesting.
I have experiance with domoticz but not with HA so it will be a HA learning proces.
I have a small question. Can you also control a 3 way valve for EPMD salor panels?
Kind regards
Koen

Probably, you could control everything you want with HA and proper remote controlled 3-way valve.
I figure you want to change the way of water between direct or solar panels in function of temperature pool, temperature panels, etc... to make an intelligent pool hotter. I think it goes out of scope of this project, but can be inetgrated in it.
One of the great of HA is that people can "easy" make their own modifications over the base system.


Support private feeds

Describe the solution you'd like
https://github.com/loic-sharma/BaGet/issues/36
Describe alternatives you've considered
Didnt find any open source nuget with private feeds

This is a topic we know about and is definitely on our todo list.
But we have no date when it will be done.
If have interest you can give us a first draft as pr and we give our feedback.

@seriouz Draft is there. LMK if you want anything. I have tested it and everything seems to work without any breaking change. Its activated only by setting the Env variables (Docker compose, or appsettings directly)


Interface to debug pandas dataframes

Feature requested via feedback:

if possible provide an interface to debug pandas dataframes.
Thank you very much

Like other IDEs, Pandas data frames have become a crucial part of the development process for data analysis. So the ability to debug dataframes are crucial to a better development workflow

You can view the data in Pandas data frames in the variables window during debugging. Feel free to reopen the issue if you're looking something else.


Do not attempt to launch any servers in case when Python is not installed

https://github.com/microsoft/vscode-python-tools-extension-template/issues/25

This will be handled in the template and propagated here.


Authorization > Check canCreate flag to toggle create button visibility (companies/sites)

Example: the admin user can create a payment method for the Billing but only for himself in his user's profile but cannot create one for the other users. In that case we have to hide the Create button. This enhancement will further improve the authorization's granularity.
This issue covers companies and sites.

@Fonsu You can also align the DataResult types with the backend


Proposal for adding a case study section

Currently, our website features some excellent examples. However, I believe it would be beneficial to have a case study similar to the one we had in {gt}.
I've followed the case study and successfully reproduced a similar table (excluding the tab_footnote part) using Polars. While this was a self-exercise and the code might be a bit messy, I'm wondering if it would be a good idea to create a case study section based on this exercise. @rich-iannone and @machow , what do you think about this idea?

I've just discovered that I can publish the result using Quarto Pub after seeing PR323. Although the CSS appears slightly different compared to viewing it in the Jupyter notebook, it renders better than the GitHub gist.

As there has been no further discussion, I will close this issue for now.


#3825 - Clamav timeout fix

Cherry-pick from the main branch for the ClamAV timeout fix.

Already taken care of in the previous PR with all required hotfixes.


Red Faction 2 - crash on exit

The game stopped behaving nicely on exit at some point, although it used to work just fine. WineD3D still behaves nicely on exit, so I don't think it's a Wine problem. I'll have to bisect it some day, but I'm raising this issue so that we don't forget it's a regression.
I've captured a trace but I couldn't reproduce the crash while capturing, so it's sort of useless.
Software information
Red Faction 2
System information

GPU: RTX 3060
Driver: 525.85.05
Wine version: 8.4 Staging
DXVK version: 2c56a1a

Apitrace file(s)
rf2.trace.tar.xz
Log files

d3d8.log: rf2_d3d8.log

I haven't done an actual bisect yet, but can confirm the regression predates the 0.10 release. So, note to self (or anyone else who wants to beat me to it), the bisect range should be between 0585064 and 03ff0bb.

faff2d700cda52641d0c54b09ecc34bed7fb25f2 is the first bad commit
commit faff2d700cda52641d0c54b09ecc34bed7fb25f2
Author: Alpyne<EMAIL_ADDRESS>Date:   Sat Nov 5 23:58:17 2022 -0800

    [d3d8] Cleanup texture and surface

 src/d3d8/d3d8_surface.h |  9 ---------
 src/d3d8/d3d8_texture.h | 21 ---------------------
 2 files changed, 30 deletions(-)

I'll see if I can figure out what the game doesn't like from the above.

*Sigh*. Apparently this is not a regression, but an older problem resurfacing. The game has always had problems with crashing on exit, even with the commits I considered problem-free, only they used to be far less frequent. The addition of subresource caching (1652611) somehow made them more prevalent, but there are still times when the game exists just fine even with latest main.
I can't reproduce the issue at all with WineD3D, so this is definitely something related to d8vk/dxvk.

Fixed by bd394b8 :tada: .


Handle last line process output without new line end

Consider process like echo -n "text", it prints "text" without
new line at the end and exit. Current overmind's output writer read
from processes output pipe line by line and in this case
it won't process "text" before overmind exit.
Therefore we must ensure that lines passed to the output writer
are always end with new line char. Fixes #81

well that fix have problems with long line outputs


Re-enable "Check Scripts" and fix the violations

Resolves #7861.
This PR fixes the force-merged ShellCheck violations and re-enables the "Check Scripts" task as disabled by #7862.
It also addresses the array-building issues discovered in #7880.
/cc @gargnupur @ozevren @rkpagadala @mandarjog @kyessenov

I'm not sure the validations are valid - from what I've seen it forces a lot of quotes that are not needed.
It can certainly not be made required until it is reviewed and approved, and I'm not sure it needs to be a pre-submit check.

Also - please send an email to istio-dev before making any changes to the pre-submit infrastructure.

LGTM
This is just a deterministic linter. There is nothing flaky about it. I don't think it's necessary to wait for a week of green tests.

Can this simply be part of "make lint"? It would be nice to have a simple command-line experience for the developers that align with how we tests things in the check-in system.
I've been using "make lint" to do lint checks, and it mostly works (well, except for depend diff check, which I think should be part of make lint as well, but that is a separate story).

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
8d0706e3e4945f5b5f39265d8ed439877add8130
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
8d0706e3e4945f5b5f39265d8ed439877add8130
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
8d0706e3e4945f5b5f39265d8ed439877add8130
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
8e71ea9d81365602922e52dea7e361985014c4cb
link
/test istio-pilot-multicluster-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
8d0706e3e4945f5b5f39265d8ed439877add8130
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I am not familiar with most of the actual scripts, so I'll refrain from lgtming and let other people who are more familiar take a closer look. I assume you tried running these scripts to see if they work as intended?
I think it looks good overall. However, splitting this into multiple PRs and landing them over a course of days may help track any issues that might arise. It will also reduce the blast radius in case these create any issues (and also reduce blast radius, in case any of your checkins got reverted).

That's fair. I'm definitely making this PR too broad now.
I'll split this into:

Re-enable it as optional / always passing
Add it to make lint
Fix the violations
Fix the typo

FYI I dropped the shell script fixes from this PR and will move them to another PR after this one lands.

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
9ccd6c51a6721053c6e6c91ffd9875c7e0d18a1e
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
9ccd6c51a6721053c6e6c91ffd9875c7e0d18a1e
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
9ccd6c51a6721053c6e6c91ffd9875c7e0d18a1e
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3
/test istio-pilot-multicluster-e2e

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mandarjog
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mandarjog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

The shellCheck command will always pass after printing out violations.

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
9ccd6c51a6721053c6e6c91ffd9875c7e0d18a1e
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

New changes are detected. LGTM label has been removed.

I agree with Costin that if it is going to be optional, it should be a separate job so that it encourages a click to see the errors. Unfortunately, that means it can't be part of make lint (except by also changing the current lint job). It also means new PRs are going to see errors irrelevant to their PR...

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
705d261d6c02ef5ede787d732e7b01e7e68b3c95
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-multicluster-e2e


Update version for Azure Services App Authentication

See https://github.com/aspnet/Configuration/pull/881/files
/cc @HaoK @joshgav @nonik0

@joshgav @nonik0 Could you give some more details on why the original PR was sent?

See also https://github.com/aspnet/Extensions/blob/master/eng/Dependencies.props#L63. The config packages don't build from this repo anymore.

@ajcvickers from the thread in https://github.com/aspnet/Configuration/pull/881:
to pick up this update: https://github.com/Azure/azure-sdk-for-net/pull/4427, which updates the IMDS endpoint used. The old one no longer works.
Workaround is to manually dotnet add package ... with latest version but I didn't recognize the issue for a while :)
Thanks!

Yes, I think we have multiple packages that use this dependency.


doc: Clean up wrong c function links

Resolve wrong documentation c function links for:

irq: z_shared_isr
rtio: rtio_cqe_get_mempool_buffer
sensor: sensor_read

Added @kartben as Assignee and reviewer because it touches documentation only as in: #66497


Execute the Action service under a dedicated non-root user account

Motivation and Context
The principle of using least privilege should be followed when executing code within containers. Specifically, not running as root.
IMPORTANT: Note that this change must be merged at the same time as the pull request to update the Kubernetes manifests for this change.
What has changed
The ActionBeanMapper has been changed so the configureFactoryBuilder method is no longer overridden to specify the EclipseJdtCompilerStrategy. Detailed investigation revealed that using this compiler strategy causes Orika to try to write Java source files to a directory named /file: at runtime. This was failing during container start-up when running as a non-root user. Not overriding the method means Orika will use the default JavassistCompilerStrategy, which is what the other RM Java microservices use.
The Dockerfile has been changed:

Create a dedicated non-root user account for executing the Java code
The existing ENTRYPOINT command was poorly-formed:

The use of sh -c does not pass Unix signals to the Java process
When using the exec form of ENTRYPOINT each argument should be its own array element
The JAVA_OPTS environment variable is Tomcat-specific and may be omitted. A separate PR linked below addresses passing options to the JVM via the standard JAVA_TOOL_OPTIONS environment variable

How to test?
I tested this change by creating a differently tagged Docker image and deploying to my Kubernetes cluster. I verified that:

The pod started successfully
The Kubernetes readiness and liveness probes succeeded
There were no errors in the container logs
exec-ing into the container showed the Java process running as the expected non-root user account

Links

https://docs.docker.com/engine/reference/builder/#entrypoint
https://github.com/ONSdigital/census-rm-kubernetes/pull/14
https://github.com/ONSdigital/census-rm-kubernetes/pull/29

Do not merge - changes required if https://github.com/ONSdigital/census-rm-kubernetes/pull/4 is merged first.

If this is still required, please rebase and open a new PR


best practice for mapping two measurement concepts that take different units

Example 1:
subject = "s:depth"
object = "o:depth"
conceptually these are the same, but subject is for a property whose range is a literal with implicit unit of meters and object is for a property whose range is a literal with implicit unit of cm
Example 2:
subject = "s:depth_in_meters"
object = "o:depth"
conceptually these are the same, but subject is for a property whose range is a literal with unit of meters and object is for a property whose range is a string conforming to "{number} {unit}" syntax
I would say in both cases it is incorrect to use skos:exactMatch because the CURIE pairs denote different concepts, although the CURIEs are about the same concept. So we would instead go to skos:closeMatch. This is not wrong, however, it seems unsatisfactory as the concepts are "conceptually closer" than other close matches
Proposed recommendation:

skos:closeMatch is not wrong
define a new predicate is_about_identical_concepts. Formally: S is_about sc, O is_about oc, sc exactMatch oc.
add a new column intended for the unit case

cc @wdduncan @pbuttigieg

I agree that that there is a difference that needs to be represented, but from what I've read about skos:exactMatch (here), skos:exactMatch links between concepts. So, depth (with an implicit unit of meter) can be a skos:exactMatch to depth_in_meters.  As an aside, if the implicit unit for depth was centimeters, then I suppose skos:relatedMatch would work.
If we need to capture the syntactic (or representational) dimension, how about using predicates such as syntaxExactMatch, syntaxCloseMatch, etc.?

@rmoffitt or @DaveraGabriel may have good examples for how unit reconciliation is captured algorithmically for transformations

Closing in favour of #61


Method to move an item in a list to a specific index

Right now there is only swap. Which really only works for an interface with up down arrows. That interface is terrible. You have to move mouse and click so many times. I built a drag&drop version, but I need to update the state in redux, however if I do 500 swap operations it'll mess things up because it will pass down props, putting aside the performance issues.
I suggest calling it 'move' It's pretty easy to write, but I wanna create this issue to any design stuff is agreed upon before hand since this is your project.

Why not just have a sort method that can use any function you want to sort an array as usual? Then swap / move to top or bottom / move to index, etc., would all be easy to write.

You can create your own moveArrayValue action.
function moveArrayValue(form, path, sourceIndex, targetIndex) {
  return (dispatch, getState) => {
    const formValues = getValues(getState().form[form])
    const fieldValues = _.get(formValues, `path[${sourceIndex}]`)

    dispatch(removeArrayValue(form, path, sourceIndex))
    dispatch(addArrayValue(form, path, targetIndex, fieldValues))
  }
}

Disclaimer: The above function is not tested and is really REALLY clumsy. It only illustrates the idea. However it may be a good addition to Redux Form API. cc @erikras

I'm just now implementing the v6 array field API. I will include a move() function.

@erikras Is this still being developed? Noticed it's not yet in the alpha API

Published as 6.0.0-alpha-15.

Can someone confirm that this is working for them? I'm having issues with this currently: #1197


Allow invalid UNTIL DATE-TIME rules for Google Calendar ics

Allow invalid UNTIL DATE-TIME rules for Google Calendar ics files.
Google calendar may export .ics files like this:
BEGIN:VEVENT
DTSTART;VALUE=DATE:20110806
DTEND;VALUE=DATE:20110807
RRULE:FREQ=WEEKLY;UNTIL=20110812T070000Z;BYDAY=SA
...
END:VEVENT

The specific validation rule this is implementing comes from https://www.rfc-editor.org/rfc/rfc5545#section-3.3.10
The UNTIL rule part defines a DATE or DATE-TIME value that bounds
the recurrence rule in an inclusive manner.  ...
... The value of the UNTIL rule part MUST have the same
value type as the "DTSTART" property.  Furthermore, if the
"DTSTART" property is specified as a date with local time, then
the UNTIL rule part MUST also be specified as a date with local
time.  If the "DTSTART" property is specified as a date with UTC
time or a date with local time and time zone reference, then the
UNTIL rule part MUST be specified as a date with UTC time.

The existing interpretation of the RFC is correct, but we'll instead prefer to be compatible and just coerce the data to be valid in the validation layer.
Issue #176

Codecov Report

Merging #177 (7964e9c) into main (ba9c200) will decrease coverage by 0.07%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##             main     #177      +/-   ##
==========================================
- Coverage   96.74%   96.68%   -0.07%
==========================================
  Files          44       44
  Lines        2583     2591       +8
==========================================
+ Hits         2499     2505       +6
- Misses         84       86       +2

Impacted Files
Coverage Δ

ical/component.py
94.33% <88.23%> (-1.03%)
:arrow_down:

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


Womanium Submission 2

Assignment 6.12 submission on a different branch  (Corrected)

Well done!
Score 9/10.

Well done! Score 9/10
@NadavClassiq Thanks a lot!


Failed parsing MLSD response on some servers

Log fragment:
goftp: 0.110 #1 sending command MLSD /somedir
goftp: 0.144 #1 got 150-Using transfer connection
goftp: 0.144 error in ReadDir: failed parsing MLST entry:

The server response was:
Type=dir;Size=0;Modify=20191124122657; subdir1<CRLF>
Type=dir;Size=0;Modify=20190808091946; subdir2<CRLF>
<CRLF>

Note the last empty line on which the parsing fails.
As to me, to fix this we could ignore empty lines in MLSD response. What do you think?

I'm having the same problem. I'm assuming that because it's been ignored for 1yr, there's little point using this library.

I'm having the same problem. I'm assuming that because it's been ignored for 1yr, there's little point using this library.

Fix: https://github.com/secsy/goftp/commit/abc51308bc247cf16604fb2248e146cfb241a180

Fix: https://github.com/secsy/goftp/commit/abc51308bc247cf16604fb2248e146cfb241a180


Fix package validation bug

Integration with the Package Validation module (son-validate) has a bug:
E, [2017-06-12T08:37:57.791166 #6] ERROR -- GtkApi::Validator#valid_package?: Error during processing: no implicit conversion of Tempfile into String
E, [2017-06-12T08:37:57.791279 #6] ERROR -- GtkApi::Validator#valid_package?: Backtrace:
	/app/models/validator.rb:62:in `http_post'
	/app/models/validator.rb:62:in `valid_package?'

Closed by PR #731


Read md file

Task Done:

Integrate Markdone converter to HTML
Move challenge folder to inside /ui/sr so it is readable by the project
Setup appropirate pages for each of a challenge
Challenge Selection is also now functional

Future task:

Adjust the schema from API back end
API Get request to get data (not from file as it is right now)
Use map function on challenge selection page

I removed proxy (either to port 5000 or to ctf.gorence.io) in package.json in this version, so it does go to another host or port with I fetch for files input. This is something that you might need to reconsider