Bag manifest-md5.txt file contains duplicate entries for each file after bag update

@horsburgh brought this to my attention that for this resource https://www.hydroshare.org/resource/4de42db6485f47b290bd9e17b017bb51/ his student just published, all of the content files are listed twice in the manifest-md5.txt file. After some investigation, I found this problem occurs for all resources. The bag looks correct the first time when the bag is created, but after the resource is updated and the bag needs to be recreated, this problem with duplicate entries for each content file occurs. This problem is a regression, but I am not sure from which release on this problem started to crop up. There has been no change to the irods bagit rule file that generates the manifest file in the bag for a long time and I can confirm this problem had already occurred on June 2nd this year evidenced from this resource: https://www.hydroshare.org/resource/84152dd636c445d69b5bada34bc2ca95/, but did not occur on April 17 as evidenced by this resource: https://www.hydroshare.org/resource/b0abfd43ba1949ef8b69bead62785788/. So I believe this problem cropped up sometime between 4/17 and 6/2 of this year. @sblack-usu @cbcunc Let me know if any changes that occurred during that period ring a bell to you that could potentially have caused this regression issue.

We ran into a similar issue with duplicate entries for content files in manifest bag file a couple of years ago as detailed in this issue: https://github.com/hydroshare/hydroshare/issues/2404, but the cause of that issue was not related to code and was only isolated to that single resource. This time this issue appears to be wide-spread and happens to all resources after the bag is updated according to my testing.

fixed. Closing.


more pythonic

Hi.
I think a better solution would be:
print range(2, 100, 2)

@AkashSharma93 Awesome! But I think it may be more pythonic to use List Comprehensions , rather than just a method of Range to output some numbers.

Thank you for you contribution to the repo and the community
On 4 Jun 2017, at 16:10, Shagbark the Plush<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/geekcomputers/Python/pull/176
Commit Summary
more pythonic
File Changes
M Print_List_of_Even_Numbers.py (2)
Patch Links:
https://github.com/geekcomputers/Python/pull/176.patch
https://github.com/geekcomputers/Python/pull/176.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Link to existing native SQLite library

First of all, congrats and thank you for this work!
Would it be hard to support compiling the wrapper to use the existing native SQLite library?
Like libsqlite3.so, libsqlite3.dylib and sqlite3.dll
Instead of informing the path to the amalgamation we would inform the path to the library, and maybe its name.
Then gyp would pass to the linker the path to the library (-L) and the library name to be linked to (-l)

I saw that node-sqlite3 does it
I also found this implementation on better-sqlite3


gollvm: stack splitting support is not detected,on Aarch64 (GCC, Clang). False negatives during mmap detection

This is the first issue, which was tacked on Aarch64 servers, provided by Equinix .
CC'ing to @vielmetti , since he is helping with servers, on behalf of gollvm project/Aarch64 port.
Edward, this issue is related to
https://llvm.org/docs/SegmentedStacks.html#:~:text=Segmented stack allows stack space,into a doubly linked list.
https://gcc.gnu.org/wiki/SplitStacks
. So it is missing critical/being a significant blocker.
Actually I was surprised about it - I thought building on 64bit ARM hardware was possible.
Here is my setup, for now:

$ lscpu
Architecture:                    aarch64
CPU op-mode(s):                  64-bit
Byte Order:                      Little Endian
CPU(s):                          96
On-line CPU(s) list:             0-95
Thread(s) per core:              1
Core(s) per socket:              48
Socket(s):                       2
NUMA node(s):                    2
Vendor ID:                       Cavium
Model:                           1
Model name:                      ThunderX 88XX
Stepping:                        0x1
BogoMIPS:                        200.00
NUMA node0 CPU(s):               0-47
NUMA node1 CPU(s):               48-95
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Vulnerable
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Vulnerable
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid

Checking the linker:

$ gold --version
GNU gold (GNU Binutils for Ubuntu 2.34) 1.16
; and another one:
$ ld --version
GNU ld (GNU Binutils for Ubuntu) 2.34
.

Checking the OS:

$ uname -a
Linux ams1-c1.large.arm-01 5.4.0-40-generic #44-Ubuntu SMP Mon Jun 22 23:59:48 UTC 2020 aarch64 aarch64 aarch64
. In detail:

$ cat /etc/release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
.
Checking compilers:

$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

$ clang-11 --version
Ubuntu clang version 11.0.0-2~ubuntu20.04.1
Target: aarch64-unknown-linux-gnu

$ llc-11 --version
LLVM (http://llvm.org/):
LLVM version 11.0.0
Optimized build.
Default target: aarch64-unknown-linux-gnu
Host CPU: thunderxt88

The full list of installed package could be checked here
.
Here is how I am able to track the issue:

$ cmake -DLLVM_TARGETS_TO_BUILD=Aarch64 -DLLVM_USE_LINKER=gold -G Ninja ../llvm-project/llvm
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type selected, default to Debug
-- Looking for dlfcn.h
-- Looking for dlfcn.h - found
-- Looking for errno.h
-- Looking for errno.h - found
-- Looking for fcntl.h
-- Looking for fcntl.h - found
-- Looking for link.h
-- Looking for link.h - found
-- Looking for malloc/malloc.h
-- Looking for malloc/malloc.h - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for signal.h
-- Looking for signal.h - found
-- Looking for sys/ioctl.h
-- Looking for sys/ioctl.h - found
-- Looking for sys/mman.h
-- Looking for sys/mman.h - found
-- Looking for sys/param.h
-- Looking for sys/param.h - found
-- Looking for sys/resource.h
-- Looking for sys/resource.h - found
-- Looking for sys/stat.h
-- Looking for sys/stat.h - found
-- Looking for sys/time.h
-- Looking for sys/time.h - found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for sysexits.h
-- Looking for sysexits.h - found
-- Looking for termios.h
-- Looking for termios.h - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for valgrind/valgrind.h
-- Looking for valgrind/valgrind.h - not found
-- Looking for fenv.h
-- Looking for fenv.h - found
-- Looking for FE_ALL_EXCEPT
-- Looking for FE_ALL_EXCEPT - found
-- Looking for FE_INEXACT
-- Looking for FE_INEXACT - found
-- Looking for mach/mach.h
-- Looking for mach/mach.h - not found
-- Looking for histedit.h
-- Looking for histedit.h - not found
-- Looking for CrashReporterClient.h
-- Looking for CrashReporterClient.h - not found
-- Looking for linux/magic.h
-- Looking for linux/magic.h - found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Looking for pthread_getspecific in pthread
-- Looking for pthread_getspecific in pthread - found
-- Looking for pthread_rwlock_init in pthread
-- Looking for pthread_rwlock_init in pthread - found
-- Looking for pthread_mutex_lock in pthread
-- Looking for pthread_mutex_lock in pthread - found
-- Looking for dlopen in dl
-- Looking for dlopen in dl - found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for pfm_initialize in pfm
-- Looking for pfm_initialize in pfm - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found ZLIB: /usr/lib/aarch64-linux-gnu/libz.so (found version "1.2.11")
-- Looking for compress2
-- Looking for compress2 - found
-- Could NOT find LibXml2 (missing: LIBXML2_LIBRARY LIBXML2_INCLUDE_DIR)
-- Looking for xar_open in xar
-- Looking for xar_open in xar - not found
-- Looking for arc4random
-- Looking for arc4random - not found
-- Looking for backtrace
-- Looking for backtrace - found
-- backtrace facility detected in default set of libraries
-- Found Backtrace: /usr/include
-- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
-- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed
-- Looking for __register_frame
-- Looking for __register_frame - found
-- Looking for __deregister_frame
-- Looking for __deregister_frame - found
-- Looking for _Unwind_Backtrace
-- Looking for _Unwind_Backtrace - found
-- Looking for getpagesize
-- Looking for getpagesize - found
-- Looking for sysconf
-- Looking for sysconf - found
-- Looking for getrusage
-- Looking for getrusage - found
-- Looking for setrlimit
-- Looking for setrlimit - found
-- Looking for isatty
-- Looking for isatty - found
-- Looking for futimens
-- Looking for futimens - found
-- Looking for futimes
-- Looking for futimes - found
-- Looking for posix_fallocate
-- Looking for posix_fallocate - found
-- Looking for sigaltstack
-- Looking for sigaltstack - found
-- Looking for lseek64
-- Looking for lseek64 - found
-- Looking for mallctl
-- Looking for mallctl - not found
-- Looking for mallinfo
-- Looking for mallinfo - found
-- Looking for malloc_zone_statistics
-- Looking for malloc_zone_statistics - not found
-- Looking for getrlimit
-- Looking for getrlimit - found
-- Looking for posix_spawn
-- Looking for posix_spawn - found
-- Looking for pread
-- Looking for pread - found
-- Looking for sbrk
-- Looking for sbrk - found
-- Looking for strerror
-- Looking for strerror - found
-- Looking for strerror_r
-- Looking for strerror_r - found
-- Looking for strerror_s
-- Looking for strerror_s - not found
-- Looking for setenv
-- Looking for setenv - found
-- Looking for dlopen
-- Looking for dlopen - found
-- Looking for dladdr
-- Looking for dladdr - not found
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC - Failed
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC - Success
-- Looking for GLIBC
-- Looking for GLIBC - found
-- Looking for pthread_getname_np
-- Looking for pthread_getname_np - found
-- Looking for pthread_setname_np
-- Looking for pthread_setname_np - found
-- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE
-- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE - Success
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Success
-- Performing Test LLVM_HAS_ATOMICS
-- Performing Test LLVM_HAS_ATOMICS - Success
-- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG
-- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG - Success
-- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG
-- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG - Failed
-- Performing Test HAS_MAYBE_UNINITIALIZED
-- Performing Test HAS_MAYBE_UNINITIALIZED - Success
-- Native target AArch64 is not selected; lli will not JIT code
-- Threads enabled.
-- Doxygen disabled.
-- Go bindings disabled.
-- Ninja version: 1.10.0.git.kitware.jobserver-1
-- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
-- OCaml bindings disabled.
-- Could NOT find Python module pygments
-- Could NOT find Python module pygments.lexers.c_cpp
-- Could NOT find Python module yaml
-- LLVM host triple: aarch64-unknown-linux-gnu
-- LLVM default target triple: aarch64-unknown-linux-gnu
-- Performing Test CXX_SUPPORTS_CUSTOM_LINKER
-- Performing Test CXX_SUPPORTS_CUSTOM_LINKER - Success
-- Performing Test C_SUPPORTS_FPIC
-- Performing Test C_SUPPORTS_FPIC - Success
-- Performing Test CXX_SUPPORTS_FPIC
-- Performing Test CXX_SUPPORTS_FPIC - Success
-- Building with -fPIC
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success
-- Performing Test C_SUPPORTS_WERROR_DATE_TIME
-- Performing Test C_SUPPORTS_WERROR_DATE_TIME - Success
-- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME
-- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME - Success
-- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
-- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG - Success
-- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
-- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
-- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
-- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
-- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG
-- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG - Success
-- Performing Test CXX_SUPPORTS_REDUNDANT_MOVE_FLAG
-- Performing Test CXX_SUPPORTS_REDUNDANT_MOVE_FLAG - Success
-- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG
-- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG - Success
-- Performing Test C_SUPPORTS_DELETE_NON_VIRTUAL_DTOR_FLAG
-- Performing Test C_SUPPORTS_DELETE_NON_VIRTUAL_DTOR_FLAG - Failed
-- Performing Test CXX_SUPPORTS_DELETE_NON_VIRTUAL_DTOR_FLAG
-- Performing Test CXX_SUPPORTS_DELETE_NON_VIRTUAL_DTOR_FLAG - Success
-- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG
-- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG - Success
-- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL
-- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL - Success
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP - Failed
-- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG
-- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG - Failed
-- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG
-- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG - Failed
-- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS
-- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS - Failed
-- Looking for os_signpost_interval_begin
-- Looking for os_signpost_interval_begin - not found
-- Found Python3: /usr/bin/python3.8 (found version "3.8.5") found components: Interpreter
CMake Error at CMakeLists.txt:731 (message):
The target `Aarch64' is experimental and must be passed via
LLVM_EXPERIMENTAL_TARGETS_TO_BUILD.
-- Configuring incomplete, errors occurred!
See also "/home/oceanfish81/workarea/release/CMakeFiles/CMakeOutput.log".
See also "/home/oceanfish81/workarea/release/CMakeFiles/CMakeError.log".

gollvm_aarch64_gcc.zip
Here is the compressed build folder.
Super detailed CMake's log is available here https://gist.github.com/advancedwebdeveloper/29ed56eb49ba30af9c4c61bc59449d2b

gollvm_aarch64_gcc.zip
Here is the compressed build folder.
Super detailed CMake's log is available here https://gist.github.com/advancedwebdeveloper/29ed56eb49ba30af9c4c61bc59449d2b

Your log includes:
CMake Error at CMakeLists.txt:731 (message):
The target `Aarch64' is experimental and must be passed via
LLVM_EXPERIMENTAL_TARGETS_TO_BUILD.

I don't think this has anything to do with gollvm.
FYI, LLVM back end does not currently support -fsplit-stack for aarch64. Clang accepts the option but does not actually insert stack-check sequences in function prologs, to the best of my knowledge. For aarch64 builds I would recommend using -DGOLLVM_USE_SPLIT_STACK=OFF.

Your log includes:
CMake Error at CMakeLists.txt:731 (message):
The target `Aarch64' is experimental and must be passed via
LLVM_EXPERIMENTAL_TARGETS_TO_BUILD.

I don't think this has anything to do with gollvm.
FYI, LLVM back end does not currently support -fsplit-stack for aarch64. Clang accepts the option but does not actually insert stack-check sequences in function prologs, to the best of my knowledge. For aarch64 builds I would recommend using -DGOLLVM_USE_SPLIT_STACK=OFF.

Well,
must say that I didn't new that.

Well,
must say that I didn't new that.

@thanm, what about mmap ?

@thanm, what about mmap ?

OK, I got some progress.

[  3%] Linking CXX executable ../../../bin/llvm-goc
/usr/bin/ld: ../../../lib/libLLVMCppGoFrontEnd.a(go.cc.o): in function go_create_gogo(go_create_gogo_args const*)': /home/oceanfish81/workarea/llvm-project/llvm/tools/gollvm/gofrontend/go/go.cc:44: undefined reference to Gogo::read_embedcfg(char const*)'
/usr/bin/ld: ../../../lib/libLLVMCppGoFrontEnd.a(parse.cc.o): in function Parse::declaration()': /home/oceanfish81/workarea/llvm-project/llvm/tools/gollvm/gofrontend/go/parse.cc:1324: undefined reference to Gogo::is_embed_imported() const'
collect2: error: ld returned 1 exit status
make[3]: *** [tools/gollvm/driver-main/CMakeFiles/llvm-goc.dir/build.make:240: bin/llvm-goc] Error 1
make[2]: *** [CMakeFiles/Makefile2:30478: tools/gollvm/driver-main/CMakeFiles/llvm-goc.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:29975: tools/gollvm/CMakeFiles/gollvm.dir/rule] Error 2
make: *** [Makefile:7622: gollvm] Error 2
.
That's on

$ lscpu
Architecture:                    aarch64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
CPU(s):                          64
On-line CPU(s) list:             0-63
Thread(s) per core:              1
Core(s) per socket:              32
Socket(s):                       2
NUMA node(s):                    4
Vendor ID:                       ARM
Model:                           2
Model name:                      Cortex-A72
Stepping:                        r0p2
BogoMIPS:                        100.00
L1d cache:                       2 MiB
L1i cache:                       3 MiB
L2 cache:                        16 MiB
L3 cache:                        64 MiB
NUMA node0 CPU(s):               0-15
NUMA node1 CPU(s):               16-31
NUMA node2 CPU(s):               32-47
NUMA node3 CPU(s):               48-63
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Vulnerable
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
.

$ llc-11 --version
LLVM (http://llvm.org/):
LLVM version 11.0.0
Optimized build.
Default target: aarch64-unknown-linux-gnu
Host CPU: cortex-a72

Any suggestions?

OK, I got some progress.

[  3%] Linking CXX executable ../../../bin/llvm-goc
/usr/bin/ld: ../../../lib/libLLVMCppGoFrontEnd.a(go.cc.o): in function go_create_gogo(go_create_gogo_args const*)': /home/oceanfish81/workarea/llvm-project/llvm/tools/gollvm/gofrontend/go/go.cc:44: undefined reference to Gogo::read_embedcfg(char const*)'
/usr/bin/ld: ../../../lib/libLLVMCppGoFrontEnd.a(parse.cc.o): in function Parse::declaration()': /home/oceanfish81/workarea/llvm-project/llvm/tools/gollvm/gofrontend/go/parse.cc:1324: undefined reference to Gogo::is_embed_imported() const'
collect2: error: ld returned 1 exit status
make[3]: *** [tools/gollvm/driver-main/CMakeFiles/llvm-goc.dir/build.make:240: bin/llvm-goc] Error 1
make[2]: *** [CMakeFiles/Makefile2:30478: tools/gollvm/driver-main/CMakeFiles/llvm-goc.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:29975: tools/gollvm/CMakeFiles/gollvm.dir/rule] Error 2
make: *** [Makefile:7622: gollvm] Error 2
.
That's on

$ lscpu
Architecture:                    aarch64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
CPU(s):                          64
On-line CPU(s) list:             0-63
Thread(s) per core:              1
Core(s) per socket:              32
Socket(s):                       2
NUMA node(s):                    4
Vendor ID:                       ARM
Model:                           2
Model name:                      Cortex-A72
Stepping:                        r0p2
BogoMIPS:                        100.00
L1d cache:                       2 MiB
L1i cache:                       3 MiB
L2 cache:                        16 MiB
L3 cache:                        64 MiB
NUMA node0 CPU(s):               0-15
NUMA node1 CPU(s):               16-31
NUMA node2 CPU(s):               32-47
NUMA node3 CPU(s):               48-63
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Vulnerable
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
.

$ llc-11 --version
LLVM (http://llvm.org/):
LLVM version 11.0.0
Optimized build.
Default target: aarch64-unknown-linux-gnu
Host CPU: cortex-a72

Any suggestions?

Thanks, I'll send a CL. This is due to a frontend change just recently submitted.

Thanks, I'll send a CL. This is due to a frontend change just recently submitted.

https://drive.google.com/file/d/11VZO_2zHe_gO77Jj19eetNVuKf4PP_Cx/view?usp=sharing - this my build folder

https://drive.google.com/file/d/11VZO_2zHe_gO77Jj19eetNVuKf4PP_Cx/view?usp=sharing - this my build folder

https://golang.org/cl/284581 is now submitted. Thanks.

https://golang.org/cl/284581 is now submitted. Thanks.

Confirming: I was able to build gollvm and run GoBackendCoreTests suite.
So I assume that we have to initiate a discussion elsewhere, regarding GOLLVM_USE_SPLIT_STACK - and this issue could be closed.

Confirming: I was able to build gollvm and run GoBackendCoreTests suite.
So I assume that we have to initiate a discussion elsewhere, regarding GOLLVM_USE_SPLIT_STACK - and this issue could be closed.

@thanm , please extract those from https://drive.google.com/file/d/1QnF73JBcHmfdDBP8RSF8ccpgYP6XHDxP/view?usp=sharing


List "For You" page?

Hi,
Is it possible to get a list of "For You" videos similar to what we get in the .listPosts ?
I am assuming that .listPosts only lists videos of the current user_id. Would be good to list all videos for all users, as they appear in the "For You" page screen.
For example:
.listForYouPosts(params)
Lists posts for the user's For You page.
api.listForYouPosts({
user_id: '<user_id>',
max_cursor: 0,
})
.then(res => console.log(res.data.aweme_list))
.catch(console.log);
// Outputs:
// [{ author: {...}, aweme_id: '999', desc: 'description', music: {...}, statistics: {...}, video: {...} },

Yep, I'll get this done.


Error with Google Font (Noto Sans TC)

I've tried converting the new Google font Noto Sans TC font (found here) on versions 1.2.2 and 1.3.1. In both cases, it doesn't seem to convert (the source font is about 5.7mb, whereas the output fonts are 6.4kb and 3.1kb for the ttf and woff2 fonts, respectively).
I don't believe any errors are occurring (which is even more confusing).
If you want the font to download via wget for testing, I have it hosted here:
https://s3-us-west-2.amazonaws.com/app.local.getstencil.com/upldghcnz0k4

Here's the verbose output when running the conversion against 1.3.1:

Following up on this to see if you were able to investigate.

Trying to debug this a bit further. I get the following messages when I open the font using the FontForge GUI, although I don't think they're relevant:

However, I get this message when converting the .otf file to .ttf, which is the crux of the issue:

So CID fonts have multiple sub-fonts, but when converting an .otf with multiple sub-fonts to a .ttf, the converter is arbitrarily choosing only one. After some Googling I found that FontForge offers a way to flatten the sub-fonts:
https://fontforge.github.io/cidmenu.html
Sure enough, flattening the file before generating the .ttf results in a .ttf file that includes the CJK characters. The size of the file is also 5.7M.
The solution seems to be to add the "flatten" step to the converter.

It can be done beforehand using the FontForge API, but there's no reason it can't be integrated into the generator.
Here's the relevant FontForge function:
https://fontforge.github.io/scripting-alpha.html#CIDFlatten

I've implemented this in a new release, and the font converts correctly now.

Okay great I'll try that over the weekend. I appreciate your help on this.

I actually just tested and it's working great. Thanks a lot!


Fix for using the correct shipping/payment method if the current sele…

1. Why is this change necessary?
It's necessary that the correct shipping/payment method is selected if the context changed.
2. What does this change do, exactly?
It applies the context changes on runtime.
3. Describe each step to reproduce the issue or behaviour.

Go to checkout page (storefront) and select a payment (or shipping) method.
Head over to the backend/administration  area of the shop and deactivate the selected payment (shipping) method.
Back again to the checkout page (storefront) and refresh it.
The default payment (shipping) method is not selected correctly (see attached video)

4. Please link to the relevant issues (if any).
SW-26623
5. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

https://user-images.githubusercontent.com/4333324/159887731-e4863752-f9f6-4eec-a4e8-61f16a6acf1c.mp4

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Unfortunately, this solution won't work. We can't just assign the other payment method and shipping method to the original SalesChannelContext, since other parameters, such as active rules, may change with that as well.
We only use the $updatedContext here for a quick cart calculation to check, if a method switch solves the situation or leads to new errors. In case it does, we call the ContextSwitchRoute, which then persists the new shipping and/or payment method. Afterwards, the page needs to be reloaded with the new SalesChannelContext, which is done with the Cart Page and the Offcanvas Cart (in the Shopware\Storefront\Controller\CheckoutController.
Unfortunately, it was overlooked to do this with the Checkout Confirm Page as well. We have an open ticket for that but feel free to open a new pull request for a reload on the confirm page.


speed up performance by smart loop unroll?

idea to improve performance with no loss of precission.
Use the fact that integer multiply is faster than float math.
The integer multiplications do not overflow. (170 * 169 * 168 * 167 just fits in a uint32_t)
double dfactorial(uint8_t n)
{
  double f = 1;
  while (n > 4)
  {
    uint32_t val = n * (n-1);
    val *= (n-2) * (n-3);
    f *= val;
    n -= 4;
  }
  while (n > 1) f *= (n--);
  return f;
}

even faster could be using tables, optionally start with the max from the table.

Works, confirmed to stay within precision of both float and double. (UNO / ESP32)

Works, confirmed to stay within precision of both float and double. (UNO / ESP32)


detailed contact or group information is broken

The contact or group information can't be displayed. A empty screen appears. But in WhatsApp Web it works fine. Can you fix this?
Best Regards,
Tom

When will the app be updated?
The error is in the inject.js file...

i will take a look at this

Fixed with last commit https://github.com/Neo11/ChitChat/commit/951823f0e40d2e48286b3f5c2060332ddbeb9b6d

fixed too much hahaha ... will recheck

done


src/axis.js:666, select(this).selectAll('text') should be selectAll('text'), right?

C3 version: 0.4.18
D3 version: 3.5.17
Browser: chrome, edge
OS: windows

https://jsfiddle.net/te5xz643/1/
Hello,
I think
$$.d3.select(this).selectAll('text').each(function () {

in src/axis.js, line 666 should be changed to
$$.d3.selectAll('text').each(function () {

Otherwise it is only measuring the first x-axis' tick-value for size in the process of getMaxTickWidth-ing (for example, to setting left padding on a rotated accordingly).
I found out while working on a project that uses a very large font-size on potentially very long category tick value labels.
Am I forgetting something?

Hi,
$$.d3.select(this).selectAll('text').each(...)

Is the same as:
const axisElement = $$.d3.select(this);
const axisTexts = axisElement.selectAll('text');

Which means, for a given axis, we find the tick with the biggest text.
What you suggest would select all the <text> from the whole chart (actually from the whole document..)` since this is not scoped by anything, which is not what we want.


Make compactRange() non-blocking

Owner:
Is your feature request related to a problem? Please describe.
In Kafka Streams up to 2.6, to speed up restoration of RocksDB-backed state stores, we used to apply bulk loading when restoring. We used Options::prepareForBulkLoad() for that. So all data was first written to L0 during restoration without any compactions. When restoration ended and before normal processing started, we switched the state store back to non-bulk-loading mode. Now compactions started on all the restored data on L0. During a compaction writes to the state store stall. These meant, we sometimes experienced write stalls when normal processing started. The duration of these write stalls exceeded a timeout that we have in Kafka Streams (max.poll.interval.ms for the interested reader) which hindered progress in processing. Due to this issue, we removed bulk loading during restoration.
Now we did some improvements in restoration that would maybe allow to re-add bulk loading during restoration. However, we would need to make a manual compaction with compactRange() before we switch to normal processing for a specific store. Since we have multiple state stores to restore, we do not want to be blocked by the manual compaction of each state store after restoration. We would rather want to start manual compaction for one state store that finished restoration and then continue to restore the other state stores. Once the compaction on the state store has finished we want to switch it to normal processing. For that we need some ways to verify if the compaction has ended like a future.
Describe the solution you'd like
A non-blocking compactRange() and a way to verify that the compaction started with compactRange() finished.

🎉


Fix 'getline' warning with #define _GNU_SOURCE

The compilation process was generating a warning regarding the implicit declaration of the 'getline' function, which is not part of the C language standard but is defined by POSIX. To address this issue and eliminate the warning, the patch introduces the inclusion of '#define _GNU_SOURCE' in the code.

The getline() function conforms to IEEE Std 1003.1-2008 ("POSIX.1").
Defining _GNU_SOURCE affects the definitions set by including headers, whether they are included before or after it. To ensure stability and avoid dependency on the order of includes, it is more secure to define _GNU_SOURCE with preprocessor guard. This way, it is consistently defined irrespective of the sequence of includes.


[HOLD for payment 2024-07-10] [$250] Track expense - "Delete expense" option appears for paid tracked expense

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.82-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to workspace chat
Submit an expense
Track an expense
Pay elsewhere the expense report
Go to transaction thread of tracked expense
Click 3-dot menu

Expected Result:
"Delete expense" option will not appear for paid tracked expense
Actual Result:
"Delete expense" option appears for paid tracked expense
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/8b2f5e72-80ba-45dc-a5b4-20aed1d77172
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bb7f209695580cf5
Upwork Job ID:<PHONE_NUMBER>068548628
Last Price Increase: 2024-06-17
Automatic offers:

eh2077 | Reviewer | 102806652
bernhardoj | Contributor | 102806654

Issue OwnerCurrent Issue Owner: @kevinksullivan

@kevinksullivan  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Delete expense option is shown for paid track expense.
What is the root cause of that problem?
The delete option is always shown for track expense report.
https://github.com/Expensify/App/blob/a451de460c45611f64bcd06961afb78b4e2f3c9b/src/components/MoneyRequestHeader.tsx#L103
This is useful for self DM track expense report because the moneyRequestReport is the parent report which is self DM,
https://github.com/Expensify/App/blob/a451de460c45611f64bcd06961afb78b4e2f3c9b/src/components/MoneyRequestHeader.tsx#L63
so canAddOrDeleteTransactions returns false for selfDM track expense. In a normal money request or workspace track expense, we have IOU/expense report and then the transaction thread.
chat report -> money request report -> transaction thread
But in self DM track expense, we only have the track expense report/transaction thread
self DM -> track expense report
What changes do you think we should make in order to solve the problem?

We need to also check whether the track expense is a self DM track or not.
const isSelfDMTrack = ReportUtils.isTrackExpenseReport(report) && ReportUtils.isSelfDM(parentReport);
const moneyRequestReport = !isSelfDMTrack ? parentReport : undefined; <- optional, just so it's more predictable
const canDeleteRequest = ... && (ReportUtils.canAddOrDeleteTransactions(moneyRequestReport) || isSelfDMTrack) && ...

We also have the same condition in MoneyReportHeader that is shown in the money request report, but self DM track doesn't have money request report, so we can remove it (remove ReportUtils.isTrackExpenseReport(report))
https://github.com/Expensify/App/blob/a451de460c45611f64bcd06961afb78b4e2f3c9b/src/components/MoneyReportHeader.tsx#L81-L82
What alternative solutions did you explore? (Optional)
In canAddOrDeleteTransactions, returns true if it's a self DM.
https://github.com/Expensify/App/blob/a451de460c45611f64bcd06961afb78b4e2f3c9b/src/libs/ReportUtils.ts#L1506-L1509
if (isSelfDM(moneyRequestReport)) return true

But I don't like this one because canAddOrDeleteTransactions is expected to work with a money request report.
Instead, we can add a new optional param to canAddOrDeleteTransactions called transactionReport and if transactionReport is a self DM track, then returns true.

Moving to vip-vsb and making external. @eh2077 can you review the proposals above when you get a chance? Thanks!

Agreed @bernhardoj's proposal looks good 👍

PR is ready
cc: @eh2077

Checklist

[x] [@eh2077] The PR that introduced the bug has been identified. Link to the PR: I can't find the specific PR that is responsible for this bug. We missed this case when adding the track expense feature to workspace.
[x] [@eh2077] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x] [@eh2077] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] [@eh2077] Determine if we should create a regression test for this bug. Yes

Regression test

Open workspace chat
Submit 1 expense and track 1 expense
Open the expense report
Pay the expense
Open the track transaction thread
Press the 3-dot button
Verify there is no Delete expense option
Open a self DM
Track an expense
Open the track report
Press the 3-dot button
Verify there is a Delete expense option

Do we agree 👍 or 👎

I requested the payment in ND.

Payment summary:

@bernhardoj $250 (ND)
@eh2077 $250

All set paying @eh2077

$250 approved for @bernhardoj


HIVE-26049: Inconsistent TBL_NAME lengths in HMS schema

What changes were proposed in this pull request?
Make the TBL_NAME references consistent in length

Why are the changes needed?
TBLS allows tables defined with name up to 256 character long but transaction specific tables allow only names up to 128 characters. This makes transaction related processing - like locking such a table - broken. The changes fixes this issue. The option to extend the shorter definitions instead of shortening the others was chosen to maintain backward compatibility. That way if someone already has long table names will be able to keep using them.

Does this PR introduce any user-facing change?
No.

How was this patch tested?
Was tested on a live system with the migration of metadata.
Schema upgrade changes (with the 4th mod) were tested via integration test as shown below:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hive.metastore.dbinstall.ITestPostgres
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26 s - in org.apache.hadoop.hive.metastore.dbinstall.ITestPostgres
[INFO] Running org.apache.hadoop.hive.metastore.dbinstall.ITestMssql
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 76.309 s - in org.apache.hadoop.hive.metastore.dbinstall.ITestMssql
[INFO] Running org.apache.hadoop.hive.metastore.dbinstall.ITestMysql
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 43.313 s - in org.apache.hadoop.hive.metastore.dbinstall.ITestMysql
[INFO] Running org.apache.hadoop.hive.metastore.dbinstall.ITestDerby
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.509 s - in org.apache.hadoop.hive.metastore.dbinstall.ITestDerby
[INFO] Running org.apache.hadoop.hive.metastore.dbinstall.ITestOracle
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 72.62 s - in org.apache.hadoop.hive.metastore.dbinstall.ITestOracle
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0

Just found an issue in the MSSQL upgrade code: compared to others it has an extra PK referencing the _TABLE column which makes the ALTER to fail.
I'll fix it in the next commit...

The upgrade script was adjusted for MSSQL and MYSQL as these engines lost the NOT NULL constraint on ALTER. The others - Derby, Postgres and Oracle - don't need this, actually this would be invalid ALTER statement for those engines.


Multiplayer

Description
Other players on the Same force are saying they can not see tasks created by other players.
Reproduction
No response

Duplicate of #37


Year dropdown looks funky

I installed the gem and implemented it on a text field, the rails dropdown does not look the same as the example on the site. Here is what I am seeing.

Looks like you just have some conflicting styles in your app, or there's a bug in pickadate itself. This gem just wraps pickadate in order to make it easier to include in Rails. If you have issues or questions, try the pickadate repository.


Give priority to task owner instead of TR owner

Consider using the task owner instead of the TR owner. Sometimes, especially when the TRs are managed by Solution Manager, only the tasks (not the TR) are owned by the developer. In these cases the results will be misleading as the changes will be attributed to some functional person who was not the actual developer.
This is complex since nothing prevents a TR from having multiple tasks with different developers with overlapping objects. Some decisions will have to be made on how to address this.

Implemented in 232e988d31ef8a29e0826524f749fc0ed525d3d6.


Update tables to store user credentials

Added column to store user credentials
Commit# 2b5e8bbb6c673244560738eebd6e31e3ef0a9e50

Table structure updated, and looks fine. Good to close this.


[Event Request] - Table 37 "Sales Line" - OnValidate "Work Type Code" - "OnBeforeValidateWorkTypeCode"

We need an additional event raiser at the beginning of OnValidate-Trigger of field "Work Type Code" to handle our own logic.
OLD CODE
field(52; "Work Type Code"; Code[10])
{
	Caption = 'Work Type Code';
	TableRelation = "Work Type";

	trigger OnValidate()
	var
		WorkType: Record "Work Type";
	begin
		if Type = Type::Resource then begin
			TestStatusOpen();
			if WorkType.Get("Work Type Code") then
				Validate("Unit of Measure Code", WorkType."Unit of Measure Code");

NEW CODE:
field(52; "Work Type Code"; Code[10])
{
	Caption = 'Work Type Code';
	TableRelation = "Work Type";

	trigger OnValidate()
	var
		WorkType: Record "Work Type";
		// start kvspsa - Variables added
		IsHandled: Boolean;
		// stop kvspsa
	begin
		// start kvspsa - Event Raiser
		IsHandled := false;
		OnBeforeValidateWorkTypeCode(Rec, xRec, IsHandled);
		if IsHandled then
			exit;
		// stop kvspsa
		if Type = Type::Resource then begin
			TestStatusOpen();
			if WorkType.Get("Work Type Code") then
				Validate("Unit of Measure Code", WorkType."Unit of Measure Code");

NEW EVENT PUBLISHER:
[IntegrationEvent(false, false)]
local procedure OnBeforeValidateWorkTypeCode(var SalesLine: Record "Sales Line"; xSalesLine: Record "Sales Line"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Narrow type to access content in VerilogSourceFile.

No need to provide access to a full MemBlock, just the string-view is needed.
(This is to prevent accessing the MemBlock at the wrong level).

Codecov Report
Base: 92.82% // Head: 92.81% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (ba2fbdf) compared to base (18c178f).
Patch coverage: 86.66% of modified lines in pull request are covered.

:exclamation: Current head ba2fbdf differs from pull request most recent head 8121495. Consider uploading reports for the commit 8121495 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1517      +/-   ##
==========================================
- Coverage   92.82%   92.81%   -0.01%
==========================================
  Files         345      345
  Lines       24417    24424       +7
==========================================
+ Hits        22664    22669       +5
- Misses       1753     1755       +2

Impacted Files
Coverage Δ

verilog/analysis/verilog_project.h
94.73% <71.42%> (-5.27%)
:arrow_down:

verilog/analysis/verilog_project.cc
86.45% <100.00%> (+0.08%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


New version: GeoRegions v2.2.1

Registering package: GeoRegions
Repository: https://github.com/JuliaClimate/GeoRegions.jl
Created by: @natgeo-wong
Version: v2.2.1
Commit: a6c3ae3fee4b26a90c82bedd56dbdd3d1eaa7348
Reviewed by: @natgeo-wong
Reference: https://github.com/JuliaClimate/GeoRegions.jl/commit/a6c3ae3fee4b26a90c82bedd56dbdd3d1eaa7348#commitcomment-79416615
Description: Extraction of gridded geoscience/climate data
Release notes:

Allow user to choose to overwrite pre-existing GeoRegions from files
coordGeoRegion() now returns a vector to allow for plotting on projections
Read a vector of GeoRegions from a given file
Allow user to choose to NOT save a temporary GeoRegion (i.e. a test GeoRegion only for that specific script)

[noblock]
I would prefer to restrict this version of GeoRegions.jl to the LTS support version.


chore(PR-41): improve-ci-standards-check

use central ci-standards-check template for https://www.notion.so/typeform/Github-Actions-Runners-revamp-d67c03f3dfb949d1a22a7abfe8c249d2
Created by Sourcegraph batch change engineering-intelligence/PR-41-improve-ci-standards-check.

[BOT] Preview available with hash a5af6ca53ea52c7bffcb0839714a7cc580637e43 here.

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add autoselect option

Fixed merge conflicts for #54

@jcrben Squashed. Is this acceptable as is? Should I also commit the built/minified sources (dist)? Bump the version number?

Don't think a version bump is necessary - we can bump the version when a new package is distributed.
Are you interested in becoming a maintainer? Honestly I'm not going to maintain this and it doesn't look like any of the other committers are interested either.

Sorry, but i've got my hands full atm. Good luck with the hunt! It's a pretty useful project.

@jcrben I'm still around, have just been busy lately. Thanks for reviewing and merging a few of these PRs!


DesignerSerializationVisibility - Behaviour Changes

Type of issue
Missing information
Description
Starting from .Net 9.0 RC1 (9.0.100-rc.1.24380.1)the "missing DesignerSerializationVisibility" is treated as an error: WFO1000 for Properties where a default value is not provided.
To suppress all the WFO1000 errors in the project, add a  property to your project file:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
   ...
   <NoWarn>$(NoWarn);WFO1000</NoWarn>
  </PropertyGroup>
</Project>

Regards,
Angelo
Page URL
https://learn.microsoft.com/en-us/dotnet/core/compatibility/windows-forms/9.0/componentdesigner-initialize
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/compatibility/windows-forms/9.0/componentdesigner-initialize.md
Document Version Independent Id
f5762761-6cf1-56e1-60b5-6e641fbabe30
Article author
@gewarren
Metadata

ID: e5fcbbb2-0764-836f-a430-f7d81bd96554
Service: dotnet-fundamentals

This is making a HUGE problem when using Forms that are called from other Forms as child ones.  When using "Forms" that error should be excluded.

A workarround:
[System.Diagnostics.CodeAnalysis.SuppressMessage("WinForms Security", "WFO1000", Justification = "No Error on forms")]
public partial class Form1 : Form
{
public IBankIcon? CurrentBank { get; private set; }
public Form1()


Sycamore-v0.9.0's PointerEvent error in Chrome (Windows)

Describe the bug
PointerEvent is not fired in Chomium browsers (Chrome, Edge, Brave) when building it with Sycamore version 0.9.0-beta2's view! syntax.
For example, below code successfully builds a div element, however, the pointerdown event does not get fired in Chromium browsers (checked Chrome, Edge, and Brave at Windows). Tricky thing is that the pointerdown event listener is indeed attached to the element when looking up the browsers' devtools panel. It just not get fired. Other events like mousedown works very well (didn't check all the event types though.);
view! {
  div(on:pointerdown = move |_| { /*do something*/ }) { "pointerdown" }
}

For the comparison, these cases work well:

Browser-side:

using Firefox

Code-side:

Explicitly add an event handler inside of on_mount scope
using Builder syntax, not view! syntax
using Sycamore version 0.8.2

To Reproduce
Check crates under this repository:

v090b2-on:

using view! syntax, Sycamore=v0.9.0.beta-2;
❎The pointerdown event not gets fired in Chromium browsers.

v090b2-add:

Sycamore=v0.9.0.beta-2; added event handlers inside of on_mount scope
✅ works well

v090b2-builder:

Sycamore=v0.9.0.beta-2, using builder syntax instead of view! syntax
✅ works well

v082-on:

Sycamore=v0.8.2, view! syntax
✅ works well

Expected behavior
PointerEvent's handlers get fired as expected

Environment

Sycamore: 0.9.2-beta.2
Browser:

Chrome: 126.0.6478.183 (latest at the moment)
Firefox: 128.0 (latest at the moment)

OS: Windows

Additional context

Hey sorry for taking so long to get to this. I can't seem to reproduce this in v0.9.0-beta.3. I have a hard time seeing how this could happen in v0.9.0-beta.2 though (since we basically just call the JS api without doing anything else)...
I'm going to close this now but if this issue still occurs for you, please feel free to reopen.

I just checked it again with latest version of Chrome and it works well... It seems to have been a minor bug occurred between developments of versions in the Chromium browsers. I should have made it clear that it seems to be a browser side problem. Thanx for digging in to the issue. And I'm excited to see the great progress of new beta.3 version!


Cant compile the game

Describe your problem here.
LINK : fatal error LNK1104: cannot open file 'libcpmt.lib'

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

Your source is damaged or a critical error

Your source is corrupted or there is a critical error in the game code


Stack Overflow in Circle Drawing

The drawCircles method causes a stack overflow. The structure of the trees also appears to be incorrect, though this might be an issue with the function I wrote to print them rather than the trees themselves. More investigation is needed to pin down what the exact problem is.

This was fixed temporarily by making a set which keeps track of which nodes have been drawn and not printing nodes that were already drawn. That method of fixing is obviously a kluge, and we should continue to investigate; however, the code does work now.

We finally fixed it by rewriting buildTree.


DOES IT WORK ?

Does This app still work ? I have riot open and its not loading

This should still work? I'm unable to replicate this bug on my machine. Would be great if you could post some logs from %APPDATA%/valorant-chat-client/logs but remember to redact out sensitive info such as tokens.

what is tokens ?
it still doesnt open
[image: image.png]
[image: b39ded0f-0582-4bd1-9716-3946ba4137b1.png]
בתאריך יום ד׳, 18 בספט׳ 2024 ב-6:59 מאת Jonathan Loh <
@.***>:

This should still work? I'm unable to replicate this bug on my machine.
Would be great if you could post some logs from
%APPDATA%/valorant-chat-client/logs but remember to redact out sensitive
info such as tokens.
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2357444614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILIDQFVA4ARNLBNSZEDZXD3CBAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJXGQ2DINRRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

its still like this . please help meee i would loveeee to use this chat thing . its so annoying to open every second the game

Hi please navigate to %APPDATA%/valorant-chat-client/logs on your Windows file explorer and send it here. Redact lines containing the word "token"

בתאריך יום ו׳, 20 בספט׳ 2024 ב-7:31 מאת Jonathan Loh <
@.***>:

Hi please navigate to %APPDATA%/valorant-chat-client/logs on your Windows
file explorer and send it here. Redact lines containing the word "token"
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2362791302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILJRP4TDZPKOFZM7L4LZXOQKXAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSG44TCMZQGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

[2024-09-18 21:52:12.697] [info]  [Background] Lock Retrieved and log initialized
[2024-09-18 21:52:12.774] [info]  [Preferences] Path to Preferences: C:\Users\brach\AppData\Roaming\valorant-chat-client/preferences.json
[2024-09-18 21:52:12.781] [info]  [Preferences] Found preferences: {"minimizeToTray":true,"notifications":true,"winWidth":1200,"winHeight":800,"winX":360,"winY":120}
[2024-09-18 21:52:12.832] [info]  [Background] Main window created
[2024-09-18 21:52:12.889] [info]  [Background] Tray created
[2024-09-18 21:52:12.890] [info]  [Background] VALORANT API initialized
[2024-09-18 21:52:13.159] [info]  [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live
[2024-09-18 21:52:13.291] [info]  Checking for update
[2024-09-18 21:52:13.294] [info]  [VALORANT] Lockfile data: Riot Client:17052:62993:XsUDXJgBl28nwOp_RLVF4Q:https
[2024-09-18 21:52:13.295] [info]  [VALORANT] Region: eu
[2024-09-18 21:52:13.296] [info]  [VALORANT] Shard: eu
[2024-09-18 21:52:14.690] [info]  [WINDOWS] Uninstall Path: "C:\Riot Games\Riot Client\RiotClientServices.exe" --uninstall-product=valorant --uninstall-patchline=live
[2024-09-18 21:52:15.204] [info]  Update for version 1.0.8 is not available (latest version: 1.0.8, downgrade is disallowed).
[2024-09-18 21:52:18.361] [info]  [VALORANT] Lockfile data: Riot Client:17052:63028:tNdQk68l4VRkLhzMtosxcw:https
[2024-09-18 21:52:18.362] [info]  [VALORANT] Region: eu
[2024-09-18 21:52:18.362] [info]  [VALORANT] Shard: eu
[2024-09-18 21:52:18.381] [info]  [VALORANT] Entitlement:
[2024-09-18 21:52:18.450] [info]  [VALORANT] Auth User Info: {"country":"isr","sub":"90ea0bac-bee9-5d60-91ad-a9300b13f6da","lol_account":{"summoner_id":3585294410458400,"profile_icon":29,"summoner_level":1,"summoner_name":""},"email_verified":true,"player_plocale":null,"country_at":1591879749000,"pw":{"cng_at":1591879750000,"reset":false,"must_reset":false},"lol":{"cuid":3585294410458400,"cpid":"EUW1","uid":3585294410458400,"pid":"EUW1","apid":null,"ploc":"en","lp":false,"active":true},"original_platform_id":"EUW1","original_account_id":3585294410458400,"phone_number_verified":false,"photo":"https://avatar.leagueoflegends.com/euw/.png","preferred_username":"foxy2007b","ban":{"restrictions":[]},"ppid":null,"lol_region":[{"cuid":3585294410458400,"cpid":"EUW1","uid":3585294410458400,"pid":"EUW1","lp":false,"active":true}],"player_locale":"en","pvpnet_account_id":3585294410458400,"region":{"locales":["de_DE","en_GB","es_ES","fr_FR","it_IT"],"id":"EUW1","tag":"euw"},"acct":{"type":0,"state":"ENABLED","adm":false,"game_name":"Serious Fox","tag_line":"Crazy","created_at":1591879749000},"jti":"_DHKJyW-emk","username":"foxy2007b"}

thx for the help btw :D i realllllly want this chat without opening app cuz omg it will be so useful

have u found a fix yet ?
בתאריך שבת, 21 בספט׳ 2024 ב-22:10 מאת Brachya Gaziel <
@.***>:

בתאריך יום ו׳, 20 בספט׳ 2024 ב-7:31 מאת Jonathan Loh <
@.***>:

Hi please navigate to %APPDATA%/valorant-chat-client/logs on your
Windows file explorer and send it here. Redact lines containing the word
"token"
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2362791302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILJRP4TDZPKOFZM7L4LZXOQKXAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSG44TCMZQGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

jonathan have u found an answer yet ?
בתאריך יום ב׳, 23 בספט׳ 2024 ב-18:27 מאת Brachya Gaziel <
@.***>:

have u found a fix yet ?
בתאריך שבת, 21 בספט׳ 2024 ב-22:10 מאת Brachya Gaziel <
@.***>:

בתאריך יום ו׳, 20 בספט׳ 2024 ב-7:31 מאת Jonathan Loh <
@.***>:

Hi please navigate to %APPDATA%/valorant-chat-client/logs on your
Windows file explorer and send it here. Redact lines containing the word
"token"
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2362791302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILJRP4TDZPKOFZM7L4LZXOQKXAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSG44TCMZQGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sorry I've been pretty busy with other work lately. There seems to be an issue with getting entitlement token in which the relevant code is here. If I have time I will check this but I cannot reproduce this on my end
https://github.com/jloh02/valorant-chat-client/blob/57426167c7437f1aa44c0c1d27dc2032fa3afff6/packages/main/valorant.ts#L180C1-L189C4

thanks for responding , is there anybody you can refer me to ? that might
be able to help understand the issue and find a solution ? i dont really
understand anything with coding and programming so it would be really great
if you or anybody you know can help . i tried to find more info online but
nothing including Ai chat boxes can help find the issue
בתאריך יום א׳, 13 באוק׳ 2024 ב-9:15 מאת Jonathan Loh <
@.***>:

Sorry I've been pretty busy with other work lately. There seems to be an
issue with getting entitlement token in which the relevant code is here. If
I have time I will check this but I cannot reproduce this on my end
https://github.com/jloh02/valorant-chat-client/blob/57426167c7437f1aa44c0c1d27dc2032fa3afff6/packages/main/valorant.ts#L180C1-L189C4
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2408841270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILNHLS7NSXVO5PDVOR3Z3IFYXAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYHA2DCMRXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Unfortunately i am currently the only developer working on this. if anyone else is interested in OSS development, feel free to pick this up and create a PR!

omg im sorry to hear that . This program is sounding like a huge life saver
tho. like i talk to friends so much on val but i dont like having to open
the app on my phone and opening full games just to see what they playing is
annoying . please please if u can find time for the solution it would be
great and  i would forever be appreciative of you
בתאריך יום א׳, 13 באוק׳ 2024 ב-17:49 מאת Jonathan Loh <
@.***>:

Unfortunately i am currently the only developer working on this. if anyone
else is interested in OSS development, feel free to pick this up and create
a PR!
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2409008360,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILI3M7KCVVQ4MCVJD43Z3KB73AVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGAYDQMZWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

is there anything you need me to send to you ? any files ? logs ? anything
?  please let me know . i really want to get this working
בתאריך יום א׳, 13 באוק׳ 2024 ב-21:13 מאת Brachya Gaziel <
@.***>:

omg im sorry to hear that . This program is sounding like a huge life
saver tho. like i talk to friends so much on val but i dont like having to
open the app on my phone and opening full games just to see what they
playing is annoying . please please if u can find time for the solution it
would be great and  i would forever be appreciative of you
בתאריך יום א׳, 13 באוק׳ 2024 ב-17:49 מאת Jonathan Loh <
@.***>:

Unfortunately i am currently the only developer working on this. if
anyone else is interested in OSS development, feel free to pick this up and
create a PR!
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2409008360,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILI3M7KCVVQ4MCVJD43Z3KB73AVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGAYDQMZWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Unless there's someone who has the same issue in the EU, I can't really replicated this issue. Can I check for the Entitlement line, was it removed by you, or was it empty to begin with?

Also noticed your logs stopped at a specific step, can you try seeing if this returns anything for you
https://valorant-api.com/v1/version

[image: image.png]when i open the link
and these are the logs fully
בתאריך יום ג׳, 15 באוק׳ 2024 ב-18:16 מאת Jonathan Loh <
@.***>:

Also noticed your logs stopped at a specific step, can you try seeing if
this returns anything for you
https://valorant-api.com/v1/version
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2414253218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILKHZM3CI7RKWOQB4JDZ3UWUVAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGI2TGMRRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

i play on EU servers like thats where my account is . is it possible that
the services dont work for me because i tried to install it late ? like it
works for everyone because its already on pc ?
בתאריך יום ג׳, 15 באוק׳ 2024 ב-20:11 מאת Brachya Gaziel <
@.***>:

[image: image.png]when i open the link
and these are the logs fully
בתאריך יום ג׳, 15 באוק׳ 2024 ב-18:16 מאת Jonathan Loh <
@.***>:

Also noticed your logs stopped at a specific step, can you try seeing if
this returns anything for you
https://valorant-api.com/v1/version
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2414253218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILKHZM3CI7RKWOQB4JDZ3UWUVAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGI2TGMRRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

vcc-20241013-185235.log
vcc-20241014-181034.log
These are the full logs  ,Maby something got broken .
I play on EU servers thats also where my account is located and about the link you sent

this is what i see

Ok that helps. But please remember not to post your entitlement token as someone can use it to login and hack your account. For now, please change your passwords for your Riot account for security.
Thanks for the full log though, for some reason I think the web query to https://valorant-api.com/v1/version is not working and I have no idea why. Specifically it's this line of code
https://github.com/jloh02/valorant-chat-client/blob/57426167c7437f1aa44c0c1d27dc2032fa3afff6/packages/main/valorant.ts#L208

i changed my password .
How can i fix that line then ? i have no idea in coding . do i copy that somewhere ?

@jloh02 any news ?

Have you found some time? If you have the files it should be fast no? Like
seems like you found the issue already
On Wed, Oct 16, 2024, 5:19 AM Jonathan Loh @.***> wrote:

Ok that helps. But please remember not to post your entitlement token as
someone can use it to login and hack your account. For now, please change
your passwords for your Riot account for security.
Thanks for the full log though, for some reason I think the web query to
https://valorant-api.com/v1/version is not working and I have no idea
why. Specifically it's this line of code
https://github.com/jloh02/valorant-chat-client/blob/57426167c7437f1aa44c0c1d27dc2032fa3afff6/packages/main/valorant.ts#L208
—
Reply to this email directly, view it on GitHub
https://github.com/jloh02/valorant-chat-client/issues/11#issuecomment-2415588666,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6VILI2RKCWWOS5TLDML7TZ3XELLAVCNFSM6AAAAABOMDOGQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJVGU4DQNRWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Unfortunately, as much as I am able to find the request that fails, I am unable to replicate this on my system. Will require more debugging, preferably with someone who is able to replicate this issue reliably or debug why this issue occurs on a public API endpoint.


Linux: Copy and Paste

Describe the bug
Copy and paste via hotkeys only works "within" MegaMol. Copying or pasting text from or to other applications is not working.
To Reproduce
Steps to reproduce the behavior:

Start MegaMol.
Add text to any input text filed of ImGui (e.g. search field of parameter window).
Mark text and copy it via 'Ctrl + c'
Try to paste text from clipboard in any other application.
Copy text to clipboard in any other application.
Try to paste text via hotkey in any text field of the MegaMol GUI.

Expected behavior
1-4: It is expected that text copied inside the MegaMol application to the clipboard, is inserted into other applications using the common hotkey.
5-6: It is expected that text copied outside the MegaMol application to the clipboard, is inserted into text fields using the common hotkey.
Screenshots
...
Log file
...
Environment

Ubuntu 20.04

Additional context
...

This is not a bug. Clipboard is only fully supported for Windows. Otherwise only a ImGui internal clipboard is used. Will be fixed using GLFW in PR #679.


Can't running IDE debugger. Database connection issue when modifying autoapp.py

This is more of a question rather than an issue. I would like to use the PyCharm debugger, but in order to do this, I should run autoapp.py through the IDE interface, not call flask run from the command line. However, upon adding the line app.run() to autoapp.py, when attempting to login, I receive the following error.
OperationalError: (psycopg2.OperationalError) could not connect to server: Connection refused Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432?
This seems to be common (not just to this project). Do I need to adjust my database in order to run the application directly from autoapp.py?
Thanks!

I use PyCharm to debug my Flask applications. It should not be necessary to introduce any config or code changes to do this.
All you need to do is create a debug configuration, and then set the necessary Environment variables to replicate what you have on the command line.
You can, and should, then still make use of flask run to launch your app by specifying the path to your Flask binary in Script and simply setting Script parameters to 'run'.

Fantastic. I think I understand how this works better now. This seemed to work. Another quick followup question, how are the commands within the command file different from running flask with an argument after it? I see that these are click commands (and probably not flask commands).
Thanks


"default" option is not being applied on validation

What version of Elysia.JS is running?
1.0.22
What platform is your computer?
Linux 6.9.2-arch1-1 x86_64 unknown
What steps can reproduce the bug?
export const apiUsersRoutes = new Elysia({prefix:'/users'})
  .post(
    '/',
    async ({body}) => {
      const result = await users.addOne(body);
      return result;
    },
    {
      body: t.Object({
        username: t.String(),
        password: t.String(),
        email: t.Optional(t.String({format: 'email'})),
        isSuperuser: t.Boolean({default: false}),
      })
    }
  )

then try to send a POST request with this body:
{
"username": "admin",
"password": "123456789",
"email"<EMAIL_ADDRESS>}
What is the expected behavior?
body is accepted with default value applied to "isSuperuser" property
What do you see instead?

If I send this body:
{
"username": "admin",
"password": "123456789",
"email"<EMAIL_ADDRESS>"isSuperuser": false
}
then it is accepted and processed.
Additional information
No response

Workaround: Wrap it into optional and pass false as a second parameter

@david-plugge it doesn't work, isSuperuser is ignored and never is assigned the default value.

7d0e29b published on 1.0.23 including test case. Let me know if it works on your end.

it is working as expected, thanks.

Oh I think I'm relying on this bug for my app to work as intended. I'm not experienced with Typebox so when I saw that default values would get translated to examples in Swagger, I started using them everywhere. But if they can actually permeate to the DB, I should go and update everything at once lol


Including support for bitmap serialization

Summary
I have a table structure which has a few aggregate function columns (groupBitmap) and I was unable to directly insert into it as the ClickhouseBitmapColumn was throwing an unsupported data type when serializing.
Checking the code I saw there was a writeBitmap function implemented in the BinaryStreamUtils but it was not being used in the SerializerUtils. Not sure if there was any reason behind it or if there are any other considerations to not use it that I am not aware of.
I tested the change and I was able to successfully import in a column with such data type.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @javiercj93 thanks for submitting this! Would you mind adding a test to cover this data as well?

Thanks for reviewing @Paultagoras! appreciate it! Please let me know if this change in an existing test would be enough or we need something more specific.

@javiercj93 would you please resolve conflicts in the merge?
I would do it with web editor but I need a permission to commit merge to your fork.
Thanks in advance!

@javiercj93 appreciate it! Thank you!


Bugfix/clue item price

Fixed a bug where clue item prices aren't correct. Build on https://github.com/MidgetJake/UniversalDiscordNotifier/pull/14

Looks like quite some refactoring and changes, thanks! I'm away due to work so I can't really get a good chance to check through/test it easily. But will get to it asap

I am so so sorry, I completely forgot about this :S


HTML attribute of form's submit button is misspelled

In Request.php file, the method renderForm() has a form with one "submit" button with misspelled attribute, it should be type="submit" instead of  type="submut".

Thanks for reporting @budiony.
It's already fixed in 0c73e481e033b7b1dfe79ad4a66f56c8adf8560.

Thanks for reporting @budiony.
It's already fixed in 0c73e481e033b7b1dfe79ad4a66f56c8adf8560.


fan network creates IPv6 local link address

Required information

Distribution: ubuntu
Distribution version: faocal / 20.04
The output of "lxc info" :

$ lxc info
config:
  cluster.https_address: <IP_ADDRESS>:8443
  core.https_address: <IP_ADDRESS>:8443
  core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
- usedby_consistency
- custom_block_volumes
- clustering_failure_domains
- resources_gpu_mdev
- console_vga_type
- projects_limits_disk
- network_type_macvlan
- network_type_sriov
- container_syscall_intercept_bpf_devices
- network_type_ovn
- projects_networks
- projects_networks_restricted_uplinks
- custom_volume_backup
- backup_override_name
- storage_rsync_compression
- network_type_physical
- network_ovn_external_subnets
- network_ovn_nat
- network_ovn_external_routes_remove
- tpm_device_type
- storage_zfs_clone_copy_rebase
- gpu_mdev
- resources_pci_iommu
- resources_network_usb
- resources_disk_address
- network_physical_ovn_ingress_mode
- network_ovn_dhcp
- network_physical_routes_anycast
- projects_limits_instances
- network_state_vlan
- instance_nic_bridged_port_isolation
- instance_bulk_state_change
- network_gvrp
- instance_pool_move
- gpu_sriov
- pci_device_type
- storage_volume_state
- network_acl
- migration_stateful
- disk_state_quota
- storage_ceph_features
- projects_compression
- projects_images_remote_cache_expiry
- certificate_project
- network_ovn_acl
- projects_images_auto_update
- projects_restricted_cluster_target
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    << some stuff >>
    -----END CERTIFICATE-----
  certificate_fingerprint: b3e3e62bcd2d0f21aebcd44f344fe4c09861b1ab2311e589ce647f88056cbafb
  driver: lxc | qemu
  driver_version: 4.0.6 | 5.2.0
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.4.0-70-generic
  lxc_features:
    cgroup2: "true"
    devpts_fd: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Ubuntu
  os_version: "20.04"
  project: default
  server: lxd
  server_clustered: true
  server_name: albans
  server_pid: 2124
  server_version: "4.12"
  storage: zfs
  storage_version: 0.8.3-1ubuntu12.6

Issue description
A brief description of the problem. Should include what you were
attempting to do, what you did, what happened and what you expected to
see happen.
Steps to reproduce

create fan network.

$ lxc network show lxdfan0
config:
  bridge.mode: fan
  dns.domain: lxd
  dns.mode: managed
  fan.overlay_subnet: <IP_ADDRESS>/8
  fan.underlay_subnet: <IP_ADDRESS>/16
  ipv4.firewall: "false"
  ipv4.nat: "true"
description: Default LXC cluster network
name: lxdfan0
type: bridge
managed: true
status: Created

$ lxc profile show lxdfan0
config: {}
description: Use LXC fan network
devices:
  eth0:
    name: eth0
    network: lxdfan0
    type: nic
name: lxdfan0

launch container with fan network

$ lxc launch images:ubuntu/bionic test -p default -p lxdfan0 --ephemeral
Creating test
Starting test

check interface addresses

$ lxc exec test -- ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
20: eth0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
    link/ether 00:16:3e:52:14:5d brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/8 brd <IP_ADDRESS> scope global dynamic eth0
       valid_lft 3245sec preferred_lft 3245sec
    inet6 fe80::216:3eff:fe52:145d/64 scope link
       valid_lft forever preferred_lft forever

expected:

no ipv6 address on eth0 in container

I don't see the problem with having a link local address, that's what happens on regular networks without IPv6 connectivity too.
It's also not something LXD has much control over as the interface in the container is set up by the distro's networking tools.
If you really don't want that link local address, you can configure netplan/networkd in the container to not setup the link local.
But it's harmless and usually expected to be there on all modern systems regardless of whether the network supports IPv6 or not so I don't see us making any change to LXD about this behavior.

My apologies.  I hadn't checked against other bridged networks - this behaviour is the same for all.
I'll drop all IPv6 traffic in the firewall.


Fud support for the interactive debugger

A small hack to enable fud to work with the interactive debugger. This was complicated slightly by the need to use standard input & output directly which is a bit different from fud's normal behavior.
The end result is that now you can use --to debugger to get the interactive debugger and use -s interpreter.debugger.flags to pass flags directly to the debugger. It is an alternate stage of the interpreter and so plugs into the same places that the interpreter does.
Given that this is more than a bit hacky, I'd appreciate some eyes on it.

LGTM


at netbeans 12.6, code formating has some errors

erre1.  Format of html was running away, bringing more and more spacing.
ex1:
not format yet :
 logout

format once:
 logout

format twice:
 logout

....
ex2:
not format yet :
<?= $content->date_create ?>>

format once:
<?= $content->date_create ?>     >

format twice:
<?= $content->date_create ?>              >

error2. netbeans display syntax error
ex1: @section({{ $content }})

HI,
Thank you for the notices.
The formatting had been a blocking issue so far, but I think I've started to overcome some of them.
I think the formatting should be more stable now with the latest commit
https://github.com/haidubogdan/netbeans-php-blade-plugin/releases
I will address the error2 issue soon.

Trying to render a blade template with @section({{ $content }}) will throw an exception on older version of blade templating :
"Parse error: syntax error, unexpected '<'"
So I think I can keep the display syntax error until a blade versioning is implemented.

Maybe an old issue but with the latest update but with the latest update starting from 2.0.3 the formatting for custom components is also broken.
Not formatted:

After formatting:

It is possible that it is a html embedding issue also.


set_index does not preserve partitioning

When doing a set_index for groupby(Series) we incorrectly indicate it preserves partitioning by index
Post-Commit Tests Status (on master branch)

Lang
SDK
Dataflow
Flink
Samza
Spark
Twister2

Go

---

---

---

Java

Python

---

---

XLang

---

---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @robertwb

Windows failures are BEAM-10921


add sleep middleware

新增“睡眠”中间件

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.chaofeng.yanchaofe seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Release 2.6 - Repository explorer findEntities issue

Testing 2.6 release, inmem repo, latest repository explorer...

Selected cocoMDS1 and tried a search for '*'

This error seems to occur regardless of which repo is selected, and with both local and enterprise options.

This error seems to occur regardless of which repo is selected, and with both local and enterprise options.

segment1 servers
deserializeUser called with id 6
findByUserId
passport.deserializeUser user is [object Object],err isnull
/servers/* post called /servers/coco/rex/users/pollytasker/instances/entities/by-property-value
Got body: {
  serverName: 'cocoMDS2',
  platformName: 'Core',
  enterpriseOption: true,
  searchText: '*',
  typeName: null,
  classificationNames: []
}
 getServerInfoFromEnv() 1
 getServerInfoFromEnv() 2
Found server name coco
downstream url https://lab-datalake:9443/servers/cocoView1/open-metadata/view-services/rex/users/pollytasker/instances/entities/by-property-value
response.data
{
  class: 'RexSearchResponse',
  relatedHTTPCode: 400,
  exceptionClassName: 'org.odpi.openmetadata.viewservices.rex.api.ffdc.RexViewServiceException',
  actionDescription: 'findEntities',
  exceptionErrorMessage: 'The repository explorer view service operation findEntities encountered a problem connecting to the repository, the message is OMRS-REPOSITORY-400-040 An invalid property has been found in a metadata instance stored in repository cocoMDS1 during the findEntitiesByPropertyValue operation',
  exceptionErrorMessageId: 'OMVS-REPOSITORY-EXPLORER-400-007',
  exceptionErrorMessageParameters: [
    'findEntities',
    'OMRS-REPOSITORY-400-040 An invalid property has been found in a metadata instance stored in repository cocoMDS1 during the findEntitiesByPropertyValue operation'
  ],
  exceptionSystemAction: 'The system could not complete a repository operation due to the error indicated.',
  exceptionUserAction: 'Look at the error message and check the configuration and state of the repository server.'
}

segment1 servers
deserializeUser called with id 6
findByUserId
passport.deserializeUser user is [object Object],err isnull
/servers/* post called /servers/coco/rex/users/pollytasker/instances/entities/by-property-value
Got body: {
  serverName: 'cocoMDS2',
  platformName: 'Core',
  enterpriseOption: true,
  searchText: '*',
  typeName: null,
  classificationNames: []
}
 getServerInfoFromEnv() 1
 getServerInfoFromEnv() 2
Found server name coco
downstream url https://lab-datalake:9443/servers/cocoView1/open-metadata/view-services/rex/users/pollytasker/instances/entities/by-property-value
response.data
{
  class: 'RexSearchResponse',
  relatedHTTPCode: 400,
  exceptionClassName: 'org.odpi.openmetadata.viewservices.rex.api.ffdc.RexViewServiceException',
  actionDescription: 'findEntities',
  exceptionErrorMessage: 'The repository explorer view service operation findEntities encountered a problem connecting to the repository, the message is OMRS-REPOSITORY-400-040 An invalid property has been found in a metadata instance stored in repository cocoMDS1 during the findEntitiesByPropertyValue operation',
  exceptionErrorMessageId: 'OMVS-REPOSITORY-EXPLORER-400-007',
  exceptionErrorMessageParameters: [
    'findEntities',
    'OMRS-REPOSITORY-400-040 An invalid property has been found in a metadata instance stored in repository cocoMDS1 during the findEntitiesByPropertyValue operation'
  ],
  exceptionSystemAction: 'The system could not complete a repository operation due to the error indicated.',
  exceptionUserAction: 'Look at the error message and check the configuration and state of the repository server.'
}

Note I don't rememeber logging on as polly tasker - however I re-logged on and get the same result with garygeeke
Another issue is that cocoMDS5 is failing to work with REX. It is defined as a repository proxy, with an inmem setup, is this valid? If so it should work, if not we should remove from the rex configuration list?

Note I don't rememeber logging on as polly tasker - however I re-logged on and get the same result with garygeeke
Another issue is that cocoMDS5 is failing to work with REX. It is defined as a repository proxy, with an inmem setup, is this valid? If so it should work, if not we should remove from the rex configuration list?

cc: @grahamwallis

cc: @grahamwallis

One comment about the first test - "*" is not a valid regex so I think the RepositoryContentValidator is probably catching an exception from the matches() method. Most probably it is catching:
java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
However, this test does show the difficulty of pinning down the exact cause of the problem - i.e. the exception being reported by Rex indicates an invalid property - which (if I am right about the cause above) is a bit misleading in itself. Digging through the code I would guess that cocoMDS2 is running an in-memory repository and contains an entity that is being inspected as part of findEntitiesByPropertyValue. The matching of properties against the searchCriteria is done by verifyInstancePropertiesMatchSearchCriteria and if this gets any exception from any of the underlying switch cases it will throw a '400-040'. Beyond that it is impossible to precisely pin down the cause of the problem - the try catch is fairly generic and doesn't have access to the propertyName or entity typeName. The RepositoryContentValidator method could be refactored to enable the property category and propertyName to be included in the exception and to record more precisely the nature of the problem. The exception could also be caught in the calling method, InMemoryOMRSMetadataCollection::findEntitiesByPropertyValue, and augmented with the type name and re-thrown.

One comment about the first test - "*" is not a valid regex so I think the RepositoryContentValidator is probably catching an exception from the matches() method. Most probably it is catching:
java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
However, this test does show the difficulty of pinning down the exact cause of the problem - i.e. the exception being reported by Rex indicates an invalid property - which (if I am right about the cause above) is a bit misleading in itself. Digging through the code I would guess that cocoMDS2 is running an in-memory repository and contains an entity that is being inspected as part of findEntitiesByPropertyValue. The matching of properties against the searchCriteria is done by verifyInstancePropertiesMatchSearchCriteria and if this gets any exception from any of the underlying switch cases it will throw a '400-040'. Beyond that it is impossible to precisely pin down the cause of the problem - the try catch is fairly generic and doesn't have access to the propertyName or entity typeName. The RepositoryContentValidator method could be refactored to enable the property category and propertyName to be included in the exception and to record more precisely the nature of the problem. The exception could also be caught in the calling method, InMemoryOMRSMetadataCollection::findEntitiesByPropertyValue, and augmented with the type name and re-thrown.

Regarding the second point (RepositoryProxy) - is this related to the problem I worked on yesterday about the type system not being complete and well-formed? If so I think the changes I put into Tex in PR #4519 would help - they at least would help to isolate the cause of the problem.
I only included those changes in Tex and it occurred to me last night that Rex and Dino will need similar FFDC so I will add them today.

Regarding the second point (RepositoryProxy) - is this related to the problem I worked on yesterday about the type system not being complete and well-formed? If so I think the changes I put into Tex in PR #4519 would help - they at least would help to isolate the cause of the problem.
I only included those changes in Tex and it occurred to me last night that Rex and Dino will need similar FFDC so I will add them today.

I'll test with some other searches.
I'd not noticed either issue in previous releases, but I would need to go back and retest to be sure. I may have not noticed.

If the search string isn't a valid regex we probably should sanitize in the backend API call. Otherwise we may be exposed to injection attacks if other invalid syntax is passed?
Agree on error handling
The repository proxy angle is overlapping -- though here this was just with coco pharma, as opposed to another developer's experiments with the atlas connector. However I not noticed this issue before

I'll test with some other searches.
I'd not noticed either issue in previous releases, but I would need to go back and retest to be sure. I may have not noticed.

If the search string isn't a valid regex we probably should sanitize in the backend API call. Otherwise we may be exposed to injection attacks if other invalid syntax is passed?
Agree on error handling
The repository proxy angle is overlapping -- though here this was just with coco pharma, as opposed to another developer's experiments with the atlas connector. However I not noticed this issue before

It's probably much harder than it sounds to validate or sanitize the regex. About the most that could be done I guess would be to perform a 'matches()' against a dummy string and see whether the parser blows its top.

It's probably much harder than it sounds to validate or sanitize the regex. About the most that could be done I guess would be to perform a 'matches()' against a dummy string and see whether the parser blows its top.

The NPE issue is addressed by #4544

The NPE issue is addressed by #4544

Retesting with the latest 4.6 code (which includes your commit on sparse exceptions) and now seeing the original issue..
This of course is repeating the invalid search term

Leaving this open. will test some more & check again with master .

To me it looks like the regex exception is being mapped into something too generic - that message appears to suggest an invalid property in an instance whereas the real problem is an invalid parameter and we should at least indicate which parameter (which needs a view-service level mapping to what the user actually sees on the screen, rather than the API parameter name which would be meaningless to the user) and ideally it would be nice to see (at least some of) the original exception message about the regex.

I suggest we don't need to fix this error for 2.6 - I'll add a note to the readme about regex, but it would be a useful usability improvement

I repeated this test, albeit on a simpler environment, searching for '*' when I have instances loaded, and get:
Could not find entities (status : 400). The repository explorer view service operation findEntities encountered a problem connecting to the repository, the message is OMRS-REPOSITORY-400-055 An unexpected java.util.regex.PatternSyntaxException exception was received from a repository connector during the findEntitiesByPropertyValue operation which had message: Dangling meta character '*' near index 0
*
^

System detail: The system could not complete a repository operation due to the error indicated.

Recommended user action: Look at the error message and check the configuration and state of the repository server.

Searching for .* as a valid regex pattern works ok
As such I will close for now


feature: Add Support for AWS Ingress Annotation

Checklist:

[x] I've searched for similar issues and couldn't find anything matching
[ ] I've discussed this feature in the #k8sgpt slack channel

Is this feature request related to a problem?

[x] Yes
[ ] No

Currently, AWS K8S annotations are not supported and are reported as errors
https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/ingress/annotations/
Describe the solution you'd like

Benefits for the project and its users
By adding support for annotation resources, k8sgpt will become more versatile and valuable for its users.

Thanks for raising the issue, are you thinking we should have manifests/ingress.yaml available with these annotations?

Perhaps making this a consideration of #307 would be an idea


Support more bbtags

Perhaps add bbcode-support for font-size?
http://www.bbcode.org/examples/?id=5

I'll add it to the repo where I intend to further develop ctextfilter:
https://github.com/mosbth/ctextfilter/issues/5


Support rbac control for the data access

Feature Request
Is your feature request related to a problem? Please describe:

Currently, the user who have the pd address will have the ability to do every action in pd and tikv (read/write/delete). However, in real world users might need to have the different rights to access the data. (like mysql rbac control)
Describe the feature you'd like:

Adding rbac control for the TiKV and PD so that each request for access data to TiKV and PD will be checked by authorization and authentication.
The whole task would be split into following steps:

[ ] design authorization and authentication for PD to control the whole rbac process.
[ ] support authorization and authentication in PD for the PD API by rbac control
[ ] support rbac ability for pdclient in TiKV
[ ] support authorization and authentication in TiKV (metadata would be saved in PD)
[ ] support rbac ability for tikv-client.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:
The detailed design document would be released recently by @Yisaer

Mentee candidates who want to participate in CommunityBridge with the TiKV project are expected to join Slack Channel to have self-introductions.