sanitize=undefined

$ make tests CC=clang
clang -std=c11 -O2 -g -Wall -Wextra -Werror -D_POSIX_C_SOURCE=200809L -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wno-unknown-warning-option  -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wold-style-definition -Wsuggest-attribute=noreturn -Wjump-misses-init -Wduplicated-cond -Wmisleading-indentation -Wnull-dereference -Wduplicated-branches -Wrestrict -Og -DDEBUG -fno-omit-frame-pointer -fsanitize=undefined   -c -o thmap.o thmap.c
clang -std=c11 -O2 -g -Wall -Wextra -Werror -D_POSIX_C_SOURCE=200809L -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wno-unknown-warning-option  -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wold-style-definition -Wsuggest-attribute=noreturn -Wjump-misses-init -Wduplicated-cond -Wmisleading-indentation -Wnull-dereference -Wduplicated-branches -Wrestrict -Og -DDEBUG -fno-omit-frame-pointer -fsanitize=undefined   -c -o murmurhash.o murmurhash.c
clang -std=c11 -O2 -g -Wall -Wextra -Werror -D_POSIX_C_SOURCE=200809L -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wno-unknown-warning-option  -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wold-style-definition -Wsuggest-attribute=noreturn -Wjump-misses-init -Wduplicated-cond -Wmisleading-indentation -Wnull-dereference -Wduplicated-branches -Wrestrict -Og -DDEBUG -fno-omit-frame-pointer -fsanitize=undefined   -c -o t_thmap.o t_thmap.c
clang -std=c11 -O2 -g -Wall -Wextra -Werror -D_POSIX_C_SOURCE=200809L -D_GNU_SOURCE -D_DEFAULT_SOURCE -Wno-unknown-warning-option  -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -Wold-style-definition -Wsuggest-attribute=noreturn -Wjump-misses-init -Wduplicated-cond -Wmisleading-indentation -Wnull-dereference -Wduplicated-branches -Wrestrict -Og -DDEBUG -fno-omit-frame-pointer -fsanitize=undefined thmap.o murmurhash.o t_thmap.o -o t_thmap
MALLOC_CHECK_=3 ./t_thmap
thmap.c:204:16: runtime error: member access within misaligned address 0x55eb709da19c for type 'const thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:204:16 in
thmap.c:204:16: runtime error: load of misaligned address 0x55eb709da19c for type 'const uint32_t' (aka 'const unsigned int'), which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:204:16 in
thmap.c:334:2: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:334:2 in
thmap.c:334:2: runtime error: load of misaligned address 0x55eb709da1a4 for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da1a4: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:334:2 in
thmap.c:335:2: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:335:2 in
thmap.c:335:2: runtime error: load of misaligned address 0x55eb709da19c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:335:2 in
thmap.c:336:2: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:336:2 in
thmap.c:336:2: runtime error: load of misaligned address 0x55eb709da21c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da21c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:336:2 in
thmap.c:338:2: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:338:2 in
thmap.c:338:2: runtime error: load of misaligned address 0x55eb709da19c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:338:2 in
thmap.c:340:8: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:340:8 in
thmap.c:340:2: runtime error: store to misaligned address 0x55eb709da21c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da21c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:340:2 in
thmap.c:341:8: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:341:8 in
thmap.c:385:9: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:385:9 in
thmap.c:385:9: runtime error: store to misaligned address 0x55eb709da22c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:385:9 in
thmap.c:390:8: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:390:8 in
thmap.c:390:8: runtime error: store to misaligned address 0x55eb709da234 for type 'size_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da234: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:390:8 in
thmap.c:391:8: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:391:8 in
thmap.c:391:8: runtime error: store to misaligned address 0x55eb709da23c for type 'void *', which requires 8 byte alignment
0x55eb709da23c: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:391:8 in
thmap.c:482:39: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:482:39 in
thmap.c:493:36: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:493:36 in
thmap.c:214:34: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:214:34 in
thmap.c:225:7: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:225:7 in
thmap.c:527:6: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:527:6 in
thmap.c:527:6: runtime error: load of misaligned address 0x55eb709da19c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:527:6 in
thmap.c:536:39: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:536:39 in
thmap.c:616:41: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 01 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:616:41 in
thmap.c:235:21: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 02 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:235:21 in
thmap.c:235:21: runtime error: load of misaligned address 0x55eb709da19c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 02 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:235:21 in
thmap.c:239:31: runtime error: member access within misaligned address 0x55eb709da19c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da19c: note: pointer points here
  00 00 00 00 02 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:239:31 in
thmap.c:302:24: runtime error: member access within misaligned address 0x55eb709dac5c for type 'const thmap_leaf_t', which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:302:24 in
thmap.c:302:24: runtime error: load of misaligned address 0x55eb709dac5c for type 'const thmap_ptr_t' (aka 'const unsigned long'), which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:302:24 in
thmap.c:303:22: runtime error: member access within misaligned address 0x55eb709dac5c for type 'const thmap_leaf_t', which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:303:22 in
thmap.c:303:22: runtime error: load of misaligned address 0x55eb709dac64 for type 'const size_t' (aka 'const unsigned long'), which requires 8 byte alignment
0x55eb709dac64: note: pointer points here
  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00  01 00 00 80 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:303:22 in
thmap.c:325:9: runtime error: member access within misaligned address 0x55eb709dbfac for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709dbfac: note: pointer points here
  40 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:325:9 in
thmap.c:325:9: runtime error: store to misaligned address 0x55eb709dbfac for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709dbfac: note: pointer points here
  40 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:325:9 in
thmap.c:326:9: runtime error: member access within misaligned address 0x55eb709dbfac for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709dbfac: note: pointer points here
  40 00 00 00 00 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:326:9 in
thmap.c:326:9: runtime error: store to misaligned address 0x55eb709dbfb4 for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709dbfb4: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:326:9 in
thmap.c:280:20: runtime error: member access within misaligned address 0x55eb709dac5c for type 'const thmap_leaf_t', which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:280:20 in
thmap.c:280:20: runtime error: load of misaligned address 0x55eb709dac5c for type 'const thmap_ptr_t' (aka 'const unsigned long'), which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:280:20 in
thmap.c:285:33: runtime error: member access within misaligned address 0x55eb709dac5c for type 'const thmap_leaf_t', which requires 8 byte alignment
0x55eb709dac5c: note: pointer points here
  00 00 00 00 f4 0c 00 00  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:285:33 in
thmap.c:285:33: runtime error: load of misaligned address 0x55eb709dac64 for type 'const size_t' (aka 'const unsigned long'), which requires 8 byte alignment
0x55eb709dac64: note: pointer points here
  00 00 00 00 04 00 00 00  00 00 00 00 11 00 00 00  00 00 00 00 11 00 00 00  01 00 00 80 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:285:33 in
thmap.c:670:33: runtime error: member access within misaligned address 0x55eb709da5a4 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da5a4: note: pointer points here
  06 00 00 00 02 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:670:33 in
thmap.c:409:39: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 00  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:409:39 in
thmap.c:573:15: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:573:15 in
thmap.c:573:15: runtime error: load of misaligned address 0x55eb709da23c for type 'void *', which requires 8 byte alignment
0x55eb709da23c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00  0a 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:573:15 in
thmap.c:721:2: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:721:2 in
thmap.c:348:2: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:348:2 in
thmap.c:348:2: runtime error: load of misaligned address 0x55eb709df994 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:348:2 in
thmap.c:349:2: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:349:2 in
thmap.c:349:2: runtime error: load of misaligned address 0x55eb709dfa0c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709dfa0c: note: pointer points here
  00 00 00 00 01 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 bc 5a 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:349:2 in
thmap.c:351:2: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:351:2 in
thmap.c:351:2: runtime error: load of misaligned address 0x55eb709df994 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:351:2 in
thmap.c:352:2: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:352:2 in
thmap.c:352:2: runtime error: load of misaligned address 0x55eb709df994 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:352:2 in
thmap.c:354:8: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:354:8 in
thmap.c:354:2: runtime error: store to misaligned address 0x55eb709dfa0c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709dfa0c: note: pointer points here
  00 00 00 00 01 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 bc 5a 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:354:2 in
thmap.c:355:8: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 02 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:355:8 in
thmap.c:728:24: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 01 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:728:24 in
thmap.c:728:24: runtime error: load of misaligned address 0x55eb709df994 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 01 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:728:24 in
thmap.c:765:6: runtime error: member access within misaligned address 0x55eb709df994 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 01 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:765:6 in
thmap.c:765:6: runtime error: load of misaligned address 0x55eb709df994 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709df994: note: pointer points here
  22 01 00 00 01 00 00 80  00 00 00 00 1c 02 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:765:6 in
thmap.c:787:14: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:787:14 in
thmap.c:787:14: runtime error: load of misaligned address 0x55eb709da23c for type 'void *', which requires 8 byte alignment
0x55eb709da23c: note: pointer points here
  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00  09 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:787:14 in
thmap.c:789:29: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:789:29 in
thmap.c:789:29: runtime error: load of misaligned address 0x55eb709da22c for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:789:29 in
thmap.c:789:40: runtime error: member access within misaligned address 0x55eb709da22c for type 'thmap_leaf_t', which requires 8 byte alignment
0x55eb709da22c: note: pointer points here
  00 00 00 00 c4 02 00 00  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:789:40 in
thmap.c:789:40: runtime error: load of misaligned address 0x55eb709da234 for type 'size_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709da234: note: pointer points here
  00 00 00 00 04 00 00 00  00 00 00 00 01 00 00 00  00 00 00 00 01 00 00 00  09 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:789:40 in
thmap.c:744:3: runtime error: member access within misaligned address 0x55eb709da5a4 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da5a4: note: pointer points here
  06 00 00 00 07 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 51 27 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:744:3 in
thmap.c:744:3: runtime error: load of misaligned address 0x55eb709da5a4 for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709da5a4: note: pointer points here
  06 00 00 00 07 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 51 27 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:744:3 in
thmap.c:749:3: runtime error: member access within misaligned address 0x55eb709da5a4 for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709da5a4: note: pointer points here
  06 00 00 00 07 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 51 27 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:749:3 in
thmap.c:731:3: runtime error: member access within misaligned address 0x55eb709dc55c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709dc55c: note: pointer points here
  50 00 00 00 00 00 00 80  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:731:3 in
thmap.c:731:3: runtime error: load of misaligned address 0x55eb709dc55c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709dc55c: note: pointer points here
  50 00 00 00 00 00 00 80  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:731:3 in
thmap.c:740:12: runtime error: member access within misaligned address 0x55eb709dc55c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709dc55c: note: pointer points here
  50 00 00 00 00 00 00 80  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:740:12 in
thmap.c:740:12: runtime error: load of misaligned address 0x55eb709dc564 for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709dc564: note: pointer points here
  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:740:12 in
thmap.c:746:9: runtime error: member access within misaligned address 0x55eb709dc55c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709dc55c: note: pointer points here
  50 00 00 00 00 00 00 80  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:746:9 in
thmap.c:746:9: runtime error: store to misaligned address 0x55eb709dc55c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709dc55c: note: pointer points here
  50 00 00 00 00 00 00 80  00 00 00 00 e8 15 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:746:9 in
thmap.c:771:3: runtime error: member access within misaligned address 0x55eb709db29c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709db29c: note: pointer points here
  20 00 00 00 00 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:771:3 in
thmap.c:771:3: runtime error: load of misaligned address 0x55eb709db2a4 for type 'thmap_ptr_t' (aka 'unsigned long'), which requires 8 byte alignment
0x55eb709db2a4: note: pointer points here
  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:771:3 in
thmap.c:775:11: runtime error: member access within misaligned address 0x55eb709db29c for type 'thmap_inode_t', which requires 8 byte alignment
0x55eb709db29c: note: pointer points here
  20 00 00 00 00 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:775:11 in
thmap.c:775:11: runtime error: store to misaligned address 0x55eb709db29c for type 'uint32_t' (aka 'unsigned int'), which requires 8 byte alignment
0x55eb709db29c: note: pointer points here
  20 00 00 00 00 00 00 80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior thmap.c:775:11 in
ok

The problem is with the test_mem() test in t_thmap, rather than the actual implementation. This has been already fixed in #5 which I just merged.
I have also enabled UBSan by default as part of #9.


feat: export custom date range

Summary
https://app.clickup.com/t/862k258az

Checklist

[ ] I checked my UI changes against the design and there are no notable differences
[ ] I checked my UI changes for any responsiveness issues
[ ] I checked my UI changes in light AND dark mode
[ ] I checked my (code) changes for obvious issues, debug statements and commented code
[ ] I opened a corresponding card on Clickup for any remaining TODOs in my code
[ ] I added a short description on how to test this PR (if necessary)
[ ] Documentation (if necessary)
[ ] Tests (if necessary)
[ ] Ready to be merged

Yes I forgot :sadmici:
https://github.com/ArkEcosystem/laravel-foundation/pull/585


Out-of-date content in "Settings not copied from RS" article

Issue in help/admin/c-manage-report-suites/c-new-report-suite/settings-not-copied-from-rs.md
This article appears to have some out-of-date info; for example, it claims that Success Event "Unique Recording" settings are not copied, which seems to be incorrect.

@inselaffe  - following up on this now...

Thanks @inselaffe - this has now been fixed.


Librairies -> Libraries (fixed spelling error)

Make sure to also copy this to the docs at http://pewpew.live/documentation/main.html

Thanks!

Make sure to also copy this to the docs at http://pewpew.live/documentation/main.html
I'm going to deprecate the old doc website and make it point to https://jyaif.github.io/ppl-utils/ instead.

Rebased the commit. Thanks!

Alright, I'm removing my fork of the repo.


better handling for projects with multiple go mod paths

Issue #, if available:
Description of changes:
/hold
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/lgtm


Get Rid of Plotly/Redis Dependency

Plotly and Redis should not be a requirements of Pynecone.

Closing this in favor of #2901


Service CT entries leaking

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Visiting clusterIP in a POD leads to a service CT entry generated in CT map with a long timeout. Because the service CT entry does not see close in INGRESS direction, I think this is a critical bug.
$ cilium bpf ct list global |grep <IP_ADDRESS>
TCP OUT <IP_ADDRESS>:80 -> <IP_ADDRESS>:60462 service expires=113956 RxPackets=0 RxBytes=4209 RxFlagsSeen=0x00 LastRxReport=0 TxPackets=0 TxBytes=0 TxFlagsSeen=0x1b LastTxReport=92356 Flags=0x0012 [ TxClosing SeenNonSyn ] RevNAT=116 SourceSecurityID=0 IfIndex=0

If the visiting is very frequently, such as a high load application. The count of service CT entries will has a significant growth.
$ cilium bpf ct list global |grep <IP_ADDRESS> |grep service |wc -l
14116

As time goes on, the CT map will be full. Then the new connection will be reset like https://github.com/cilium/cilium/issues/17457
I am going to fix it with the following logic:

After deNAT, we have the clusterIP, then lookup the CT map again with the new tuple, if the entry is existed, set entry->rx_closing with 1.

Cilium Version
Client: 1.9.0 go version go1.15.4 linux/amd64
Daemon: 1.9.0 go version go1.15.4 linux/amd64
Kernel Version
Linux 4.14.105-19-0019 SMP Fri Jan 15 11:39:34 CST 2021 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.18", GitCommit:"6b913dbde30aa95b247be30a5318fb912f8fe29e", GitTreeState:"clean", BuildDate:"2021-08-11T10:20:21Z", GoVersion:"go1.15.11", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.18-57+776098ae2e7bf3-dirty", GitCommit:"776098ae2e7bf358cce0af0b0faf139fe66c6c48", GitTreeState:"dirty", BuildDate:"2021-09-01T07:38:52Z", GoVersion:"go1.15.11", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@tgraf

Visiting clusterIP in a POD leads to a service CT entry generated in CT map with a long timeout. Because the service CT entry does not see close in INGRESS direction, I think this is a critical bug.

Why is the TCP FIN exchange not seen here? Under what Cilium configuration did you reproduce this?
cc @brb

It'll also be useful to check conntrack-gc-interval. Could you also attach the sysdump while the issue is happening? Please highlight the service traffic tuple that you suspect is leaking.

It'll also be useful to check conntrack-gc-interval. Could you also attach the sysdump while the issue is happening? Please highlight the service traffic tuple that you suspect is leaking.

Reduce the value of conntrack-gc-interval could not solve the problem in depth.  Just transmit a lot requests via accessing service clusterIP to reproduce the problem.

It's very easy to reproduce the leak:

Create a deployment to generate Server pod, and create a service relate to the Server pod which has ClusterIP <IP_ADDRESS>
Use any pod as Client, exec in the Client pod, run curl <IP_ADDRESS>
Exec in the cilium-agent pod which on the same node of the Client pod, run cilium bpf ct list global|grep <IP_ADDRESS> will see the leak entry looks like:

TCP OUT <IP_ADDRESS>:80 -> <IP_ADDRESS>:57438 service expires=17135534 RxPackets=0 RxBytes=3 RxFlagsSeen=0x00 LastRxReport=0 TxPackets=0 TxBytes=0 TxFlagsSeen=0x1b LastTxReport=17114441 Flags=0x0012 [ TxClosing SeenNonSyn ] RevNAT=6 SourceSecurityID=0 IfIndex=0

The leaked entry will not be GC until 6h later.

Think about many pods visit many service ClusterIPs, it's very easy to touch the max TCP CT entry, and then the new connections will receive the unexpected rest, as eBPF lru map drop the item randomly.

Besides, as I know, CT entry will also leak when receive rst.

Why is the TCP FIN exchange not seen here?
@pchaigno https://github.com/cilium/cilium/blob/master/bpf/lib/conntrack.h#L266

As time goes on, the CT map will be full.

This should not be a problem if you use the LRU maps for the CT entries.

@BSWANG https://github.com/cilium/cilium/pull/19451 and https://github.com/cilium/cilium/pull/19800 should help you with this problem.


[Localization] Setting.json file usage text (comments) didn't change when user changing the locale.

VSCode Version:
OS Version:0.10.12-alpha

Steps to Reproduce:

Launch app with any targeted locale from command prompt > code-alpha --locale=ko
Navigate to File->Preference->Workspace settings.
It will launch both default setting and settings.json file.
Verify commented text under both the files and should match with target locale.
Close app and re-launch with different local or with default locale (EN) from cmd prompt > code-alpha
Repeat action from 2-4

Actual: Setting.json file usage text didn't change when user changed the locale.

Expected: When application re-launch with targeted local then usage text (comments) should be localized.

As designed, the file is being created and saved once.


Git version parsing doesn't get updated during the first cmake run

Currently, we store the short github hash into a cmake variable:
https://github.com/XapaJIaMnu/translateLocally/blob/44a1148ee826abf2d7de453817a6d0eef55fad71/cmake/GetVersionFromFile.cmake#L26
However this doesn't seem to be updated during the first cmake run. IE if you run cmake .. on a clean directory you would see.
...
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Building translateLocally-v0.0.1+
-- Found LibArchive: /usr/lib/x86_64-linux-gnu/libarchive.so (found version "3.2.2")
-- Looking for C++ include pthread.h
...

Whereas a second cmake .. run would display
Building translateLocally-v0.0.1+44a1148
-- Submodule update

I am not sure why this is not working.

GIT_EXECUTABLE is empty the first time cmake is executed.
I added COMMAND_ECHO STDERR to the execute_process(COMMAND ${GIT_EXECUTABLE} rev-parse --short HEAD ...) line and the first time it shows 'rev-parse' '--short' 'HEAD'. Re-running cmake it shows '/usr/bin/git' 'rev-parse' '--short' 'HEAD'.
It might be set as a CACHE variable by one of the subprojects? Related: all subprojects take on the git hash from the translatelocally project into their version string, not their own hashes:
Building translateLocally-v0.0.1+d681ab4
-- Submodule update
CMake Warning at 3rd_party/bergamot-translator/CMakeLists.txt:20 (message):
  CMAKE_BUILD_TYPE not set; setting to Release

-- Submodule update
-- Project name: bergamot_translator
-- Project version: v0.3.1+d681ab4
-- Project name: marian
-- Project version: v1.9.56+d681ab4
...

Yeah, i see. This is used by marian. That would be the issue.

This is probably either intentional in marian, or a bug over there, for choosing to use CMAKE_SOURCE_DIR instead of CMAKE_CURRENT_SOURCE_DIR in their GetVersionFromFile.cmake script.

We should do PRs on the submodules to fix that. I assume this bug is safe to close in the meantime?


HeaderTooLarge error

Hi, was trying to run llama 2 70b, ran into this err:
  File "/home/anton/personal/transformer-experiments/exllama/model.py", line 697, in __init__
    with safe_open(self.config.model_path, framework = "pt", device = "cpu") as f:
safetensors_rust.SafetensorError: Error while deserializing header: HeaderTooLarge

python3 test_benchmark_inference.py -d ./Llama-2-70B-GPTQ

Model file: https://huggingface.co/TheBloke/Llama-2-70B-GPTQ

Fixed with:
pip install git+https://github.com/huggingface/transformers

Now getting another err:
  File "/home/anton/personal/transformer-experiments/exllama/env/lib/python3.10/site-packages/sentencepiece/__init__.py", line 310, in LoadFromFile
    return _sentencepiece.SentencePieceProcessor_LoadFromFile(self, arg)
RuntimeError: Internal: src/sentencepiece_processor.cc(1101) [model_proto->ParseFromArray(serialized.data(), serialized.size())]

Fixed, seems like for some reason the tokenizer.model wasn't downloaded properly when I pulled the 70b hf repo.


Adding batch processing support , Adding new Python interface

@Reza-Najafi can you look into these warnings - https://lgtm.com/projects/g/GPUOpen-ProfessionalCompute-Libraries/MIVisionX/rev/pr-e3cfa416a3aab80f305c110c3c78ef8939cc892e

Tested utilities/rali_basic_test and the validation app. It works. Can be merged


[Snyk] Fix for 2 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

Gemfile
Gemfile.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

556/1000  Why? Recently disclosed, Has a fix available, CVSS 5.4
Open Redirect SNYK-RUBY-RAILS-1071902
Yes
No Known Exploit

671/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS) SNYK-RUBY-RAILS-1071903
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Can't apply without extensive refactoring


I prefers long options in documentation

IMO short options are more common but let's wait what others say.

With long options, there's better chances that user that does not know (or forgot) will make a good guess what the option means, instead of having to look it up.

I prefer short options because they're shorter :P
But I think it's a good idea to have the long options for intuition. Perhaps we can have both?

Since this is documentation, one could simply copy-paste (and perhaps modify) stuff, so no extra typing needed.

True, but it's also a teaching aid, and it's useful to know the shortcuts. I think it's ok to just mention both...

Descending order of what I prefer...

go for --long-options
go for -s options
go for -s | --long-options

The last one means I lose copy-paste convenience, unless you mean duplicating instructions?

I'm not convinced but I may agree with changing -i with --incremental because this is a rustc guide. About git, I'm less convinced because it's more common to use -m than --message, the same for -u and this is even not a git guide.

BTW about -i and --incremental somewhere in the guide it should be clear that -i is a shortcut for --incremental unsure if that's explained somewhere but it should. After we explain all the flags and their shortcuts, I think it's fine to just use shortcuts everywhere.

There's lots of CLI tools out there, and seeing yet-another -o to remember in another such tool adds to cognitive load. To the regular user of said tool who is tired of typing --option, let it be on them to look for --help so as to see if there is a short option they can use. I rather we optimize for the new user... I want them to have a good guess as to what the --option means, instead of them having to reach out to --help to find out.

I was thinking more of having a note after the command that says something like "-i is the short version of --incremental"


Enable multi-staged builds

Fixes #92: Multi-staged builds
To allow multi-staged builds, Docker 17.05 is required or higher is required on the daemon and the client. Documentation for Docker can be found here.

That's very odd - it was working when a few days ago and downloading the .tgz file. I'm going to look into this now!

@tirumaraiselvan Something odd is up - even the old link for https://get.docker.com/builds/Linux/x86_64/docker-1.12.6.tgz is returning a 403.
I'm going to see why the download link has changed!

@tirumaraiselvan I've updated the docker image to 17.06.0-ce from ttps://download.docker.com/linux/static/stable/x86_64 and make build-all is successful on my local machine.
If you could pull down the latest commit and test it locally, that would be great!

Good idea @tirumaraiselvan! I've made the changes and rebuilt it locally with no errors:

If we can make this any better, please let me know! 😁

Docker cli has been upgraded but will be ineffective if the underlying host docker is not > 17.06


SLSA v1 should be wrapped into intoto v1 statement

Expected Behavior
SLSA v1 predicate should be wrapped into intoto v1 statement
Actual Behavior
It's wrapped into intoto v0.1 statement
https://github.com/tektoncd/chains/blob/70c8c7de563ba3d6c1e65a1e4e21c83335fa432a/pkg/chains/formats/slsa/v2alpha2/internal/pipelinerun/pipelinerun.go#L47
Related
https://github.com/in-toto/in-toto-golang/issues/265
It would be ideal if intoto defines the v1.0 statement type in intoto project and chains uses it for _type field.

cc @chitrangpatel @wlynch @lcarva


[Feature Request] Mark dates in the calendar component

Is your feature request related to a problem? Please describe.
Wanted to use the calendar to show availability. BUT ... still be able to select any date to see what's going on on that day.
Describe the solution you'd like
An additionnal prop something like "isSpecialDate" => then we could add some custom formating to the date in the calendar, either strikethrough like unavailable ... or maybe with a faded background or somthing (already more generic feature than strikethroug) ...
OR even better and most generic : a "dateFormater" prop to which we could pass a callback (just like isUnavailable) but which callback should return some specific formatting like
{
    strikethrough?: boolean,
    color?: DateProps["color"], // or similar
    faded?: boolean, // or whatever other appearance is easy and makes sense to offer
    // ... other ???
}

... or actually just returning an array or string of classNames would be great already
Would be most generic and even allow the callback to differentiate occupency let's say :

"normal" => available whole day => {}
"completely unavailable" => {strikethrough: true, faded: true}
"partially unavailable" => {faded: true}
"special" => {color: "warning"}
....

Describe alternatives you've considered
Already described as first part above ... Still believe the last and most generic solution would be best ! (my use-case actually involves partial unavailability and complete unavailability)
Screenshots or Videos

Here I just edited the example from the docs manually with the developper tools of the browser, adding text-warning class ... works pretty well ...
And huh ... I'll gladly answer questions if anything is unclear ... but right now I don't see anything else ...

I would also like to do something like this:

With a custom component behind the number
it seems these two problems might be separate but solved in the same manner. i.e. a callback that is passed down from the user to  add a class name or component based on the specific day (d?:Date) => style or (d:Date) => html


[Function] convert_interval (#33893)

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[x] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

a function description doc need to be added, you can refer to the docs under this directory: https://github.com/StarRocks/starrocks/tree/main/docs/en/sql-reference/sql-functions

hi, I have added a doc

@silverbullet233 hi

UT failed

UT failed

@silverbullet233 @packy92 Hi, I solved BE UT failed, but it seems to need review again. There are also 3 failed, which seems to be related to my doc location, but this folder is not there when I pull this branch

UT failed

@silverbullet233 @packy92 Hi, I solved BE UT failed, but it seems to need review again. There are also 3 failed, which seems to be related to my doc location, but this folder is not there when I pull this branch

@XinzhuangL could you rebase the latest main branch code and try again ?

UT failed

@silverbullet233 @packy92 Hi, I solved BE UT failed, but it seems to need review again. There are also 3 failed, which seems to be related to my doc location, but this folder is not there when I pull this branch

@XinzhuangL could you rebase the latest main branch code and try again ?

Thank you very much for your help. I'm sorry. I'm not very familiar with this, so it might seem confusing. But it seems to have worked. What else do I need to do?


Missing stock history of sellers in offers in returned JSON from Query

Hi Keepa Team,
I see there are stock history of each sellers in addon. However, I cannot find these information in returned JSON from Query API. Are those information available?
Thanks in advance!

We are facing same issue. Does anyone have update on this?


Update Chart.JS to 2.4 / use a different chart library

Once the New UI is done, would love if someone could PR this.

https://d3js.org/ Would be my pick, but it is low level.

yeah im looking at charts specifically, data binding to dom is handled by React.

based on latest research at work, the latest version of Chart.js rocks and solved everyone's problems with 1.
We chose to go with it at work out of all the options, so should stick to it just use latest.


[2.6.3] Can´t pull traefik docker image for amd64

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
docker pull traefik:2.6.3
2.6.3: Pulling from library/traefik
no matching manifest for linux/amd64 in the manifest list entries

What did you see instead?
I could not pull the image but it seems that there is an image in the release tag for amd64.
What version of Traefik are you using?
2.6.3
What is your environment & configuration?
nothing
If applicable, please paste the log output in DEBUG level
No response

Hello,
The official Docker images are built by Docker itself, it's the process for official images: https://github.com/docker-library/official-images
The official Docker images of Traefik are currently under construction in the Docker build system.
The process takes time, you have to wait for a bit (a few hours).

The related PR in the Official Image repository: https://github.com/docker-library/official-images/pull/12145
The Traefik page in the Jenkins of the Official Images: https://doi-janky.infosiftr.net/job/multiarch/view/images/view/traefik/

duplicate of #8213n #7023, #7265, #5992, #5512, #4265,  #2467, #5348, and many other issues like every time we create a new version.

Hi!  It's been over 24 hours and I am still not seeing it
➜  traefik docker pull traefik:2.6.3
2.6.3: Pulling from library/traefik
no matching manifest for linux/amd64 in the manifest list entries

https://hub.docker.com/layers/traefik/library/traefik/v2.6.3/images/sha256-2a6e91644420e884a47301e5719349eb6a1c6c36d044c7fcfac6789aeb4b0475?context=explore

@timothystewart6 same here :(
PS: Loving your videos. They often helped me out :+1:

it works now
docker pull traefik:v2.6.3
v2.6.3: Pulling from library/traefik
cfab2db72209: Already exists
491249faa733: Already exists
0e7660e64df1: Pull complete
080a3ffe94e5: Pull complete
Digest: sha256:4ff6ffde832702965c3602dfd3023b164f10f75b5d748889b190ca72bfff8f2a
Status: Downloaded newer image for traefik:v2.6.3
docker.io/library/traefik:v2.6.3

FYI I provided an explanation here: https://github.com/traefik/traefik/issues/8885#issuecomment-1083458134

Thank you!


add dummy change to test prowjobs

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test imagebuilder-presubmit
/test cloud-provider-vsphere-tooling-presubmit

/test imagebuilder-presubmit


Getting started with side projects

skills/projects
Michael wehar (past PTI at pitt and gave talks to the club a few times sent us an email also linking this -
http://michaelwehar.com/documents/SideProjects.pdf which has good info and said we could link

Thanks so much for adding this as an issue!
I really enjoy working on coding projects with students and gave this talk for Pitt CSC.  Please feel welcome to share it.  :)
Also, another PTI named Muneeb Alvi wrote a CS job search guide: https://onedrive.live.com/view.aspx?resid=2203166754AF485B!486&ithint=file%2Cpptx&authkey=!AOxaiO5tEkV6RkY
PittCSWiki is really cool!  Keep up the great work.  :)


Unable to resolve service by invoking protoc

Hi,
I am getting the below error with this sampler. Can you please help in troubleshooting this issue?
2021-04-25 00:17:38,015 INFO v.z.j.g.c.GrpcClientSampler: Created GrpcClientSampler
2021-04-25 00:17:38,019 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2021-04-25 00:17:38,020 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2021-04-25 00:17:38,022 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2021-04-25 00:17:38,284 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2021-04-25 00:17:38,285 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2021-04-25 00:17:38,285 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2021-04-25 00:17:38,286 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2021-04-25 00:17:38,287 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2021-04-25 00:17:38,287 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2021-04-25 00:17:38,290 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2021-04-25 00:17:38,291 INFO v.z.b.GRPCSampler: Thread Group 1-1@3895635e-GRPC Request	testStarted
2021-04-25 00:17:39,208 WARN v.z.b.c.p.ProtocInvoker: Protoc invocation failed with status: 1
2021-04-25 00:17:39,209 WARN v.z.b.c.p.ProtocInvoker: [Protoc log] protoc-jar: protoc version: 3.10.1, detected platform: osx-x86_64 (mac os x/x86_64)
2021-04-25 00:17:39,209 WARN v.z.b.c.p.ProtocInvoker: [Protoc log] protoc-jar: embedded: bin/3.10.1/protoc-3.10.1-osx-x86_64.exe
2021-04-25 00:17:39,209 WARN v.z.b.c.p.ProtocInvoker: [Protoc log] protoc-jar: executing: [/var/folders/4v/ht8prz9n0wl7wv6dvjp2s968lf392v/T/protocjar10133609867773508138/bin/protoc.exe, /opt/GitHub/pay-integrator-api/src/main/proto/com/expedia/payment/integrator/service/v1/integrator_payment_api.proto, -I/opt/GitHub/googleapis-master, -I/var/folders/4v/ht8prz9n0wl7wv6dvjp2s968lf392v/T/polyglot-well-known-types2172559459053989569, -I/opt/GitHub/pay-integrator-api/src/main/proto/com/expedia/payment/integrator/service/v1, --descriptor_set_out=/var/folders/4v/ht8prz9n0wl7wv6dvjp2s968lf392v/T/descriptor40288201410774047.pb.bin, --include_imports]
2021-04-25 00:17:39,209 ERROR o.a.j.t.JMeterThread: Error calling threadStarted
java.lang.RuntimeException: Unable to resolve service by invoking protoc
	at vn.zalopay.benchmark.core.ClientCaller.init(ClientCaller.java:54) ~[jmeter-grpc-request-1.1.2.jar:?]
	at vn.zalopay.benchmark.core.ClientCaller.<init>(ClientCaller.java:32) ~[jmeter-grpc-request-1.1.2.jar:?]
	at vn.zalopay.benchmark.GRPCSampler.init(GRPCSampler.java:62) ~[jmeter-grpc-request-1.1.2.jar:?]
	at vn.zalopay.benchmark.GRPCSampler.threadStarted(GRPCSampler.java:105) ~[jmeter-grpc-request-1.1.2.jar:?]
	at org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:769) [ApacheJMeter_core.jar:5.3]
	at org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:993) [jorphan.jar:5.3]
	at org.apache.jorphan.collections.HashTree.traverse(HashTree.java:976) [jorphan.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.threadStarted(JMeterThread.java:737) [ApacheJMeter_core.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.initRun(JMeterThread.java:725) [ApacheJMeter_core.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:252) [ApacheJMeter_core.jar:5.3]
	at java.lang.Thread.run(Thread.java:832) [?:?]
Caused by: vn.zalopay.benchmark.core.protobuf.ProtocInvoker$ProtocInvocationException: Got exit code [1] from protoc with args [[/opt/GitHub/pay-integrator-api/src/main/proto/com/expedia/payment/integrator/service/v1/integrator_payment_api.proto, -I/opt/GitHub/googleapis-master, -I/var/folders/4v/ht8prz9n0wl7wv6dvjp2s968lf392v/T/polyglot-well-known-types2172559459053989569, -I/opt/GitHub/pay-integrator-api/src/main/proto/com/expedia/payment/integrator/service/v1, --descriptor_set_out=/var/folders/4v/ht8prz9n0wl7wv6dvjp2s968lf392v/T/descriptor40288201410774047.pb.bin, --include_imports]]
	at vn.zalopay.benchmark.core.protobuf.ProtocInvoker.invokeBinary(ProtocInvoker.java:159) ~[jmeter-grpc-request-1.1.2.jar:?]
	at vn.zalopay.benchmark.core.protobuf.ProtocInvoker.invoke(ProtocInvoker.java:104) ~[jmeter-grpc-request-1.1.2.jar:?]
	at vn.zalopay.benchmark.core.ClientCaller.init(ClientCaller.java:52) ~[jmeter-grpc-request-1.1.2.jar:?]
	... 10 more
2021-04-25 00:17:39,210 ERROR o.a.j.t.JMeterThread: Error while processing sampler: 'GRPC Request'.
java.lang.NullPointerException: null
	at vn.zalopay.benchmark.GRPCSampler.sample(GRPCSampler.java:70) ~[jmeter-grpc-request-1.1.2.jar:?]
	at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:630) ~[ApacheJMeter_core.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:558) ~[ApacheJMeter_core.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:489) [ApacheJMeter_core.jar:5.3]
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:256) [ApacheJMeter_core.jar:5.3]
	at java.lang.Thread.run(Thread.java:832) [?:?]
2021-04-25 00:17:39,211 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2021-04-25 00:17:39,211 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2021-04-25 00:17:39,212 INFO v.z.b.GRPCSampler: Thread Group 1-1@3895635e-GRPC Request	testEnded
2021-04-25 00:17:39,212 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2021-04-25 00:17:39,212 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)

Regards
Debayan

Hi @debayandesarkar,
The protoc compiling was failed. Please recheck your input as Proto Root Directory, Library Directory (if you use externally lib as googleapis, ...) then clicking the Listing button in order to get existed methods.
Or, you can start with an example here.
Welcome and Thank you.

Hi @huynhminhtan ,
Thanks for your prompt response. The proto root directory seems to be correct as it found the /opt/GitHub/pay-integrator-api/src/main/proto/com/expedia/payment/integrator/service/v1/integrator_payment_api.proto file. We are not using external library like googleapis. Hence, clicking on the "Listening" button is not rendering any methods. The proto file integrator_payment_api.proto

I am using doesn't have a service name and method name like the example below. Is that the reason the compilation is failing?
service Bookstore {
// Returns a list of all shelves in the bookstore.
rpc ListShelves (google.protobuf.Empty) returns (ListShelvesResponse) {
// Define HTTP mapping.
// Client example (Assuming your service is hosted at the given 'DOMAIN_NAME'):
//   curl http://DOMAIN_NAME/v1/shelves
option (google.api.http) = { get: "/v1/shelves" };
}
Regards
Debayan

Hi @debayandesarkar,
Do you import other internal proto files? please check file path when importing. The integrator_payment_api.proto doesn't have a service name and method name, so I wonder how do you make many requests to your gRPC server?
Can you upload portable/simple version of the proto file?
Regards

@huynhminhtan  Did you get a chance to look at my response above? Does these implementation require the service and method names declaration in the .proto file?
Regards
Debayan

@huynhminhtan Thanks for your response.I added the service name and method name in the service .proto file as shown below and the compilation seems to be successful. However, I am getting the below error now.
option java_outer_classname = "BraintreeClientImplGrpc";
/* Added to test with JMeter GRPC Request Sampler */
service BraintreeClientImpl {
rpc authorize (AuthorizeRequest) returns (AuthorizeResponse) {}
}

Thread Name:Thread Group 1-1
Sample Start:2021-04-28 00:33:07 PDT
Load time:59
Connect Time:0
Latency:0
Size in bytes:38
Sent bytes:0
Headers size in bytes:0
Body size in bytes:38
Sample Count:1
Error Count:1
Data type ("text"|"bin"|""):text
Response code:500
Response message:Exception: UNAVAILABLE: Network closed for unknown reason
SampleResult fields:
ContentType:
DataEncoding: null
Response Data: Caught exception while waiting for rpc

@huynhminhtan Hi, did you get a chance to look at my latest response?
Regards
Debayan

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 14 days since being marked as stale.


Provide a way to include license files in AppImage

When running for example python3 -m nuitka --standalone --onefile diag.py it builds a AppImage that contains the compiled python packages and some necessary .so files from the system, for example libpython3.10.so.1.0 and libssl.so.1.1.
Many python packages and system libraries are released under a Open Source license that requires binary distributions of the code to contain the full license text.
For example the python license contains (shortened by me):
[...] provided, however, that PSF's License Agreement and PSF's notice of copyright,
[...] are retained

and the openssl license contains:
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.

and the Apache license nuitka itself comes with:
a. You must give any other recipients of the Work or Derivative Works a copy of this License; and

So while I'm not a lawyer and don't know if any of these clauses have been tested in court, I read them all like the license texts should be included in the AppImage itself or distributed together with it.
Nuitka should provide a way to comply with these licenses without too much hassle for the developer.
It could work like this:

nuitka outputs the source filenames with full path of all python modules it compiles
nuitka outputs the .so libraries with full path of all shared libs it includes
the package manager is queried for these files and the related packages are found out
in most current Linux distributions each package comes with a license file in for example /usr/share/licenses/
the license files are included in a subdir within the AppImage
the developer adds a short code snippet that allows to browse the included licenses when a special commandline option is given

Unfortunately I don't know of an easy and distribution-independent way to find a license file to some source file.
So I think to get this at least going, nuitka should as first step get an option to output a list of all source files (points 1. and 2. above).
When using the --show-modules-output option you already get parts of it. But this output seems to be more directed at human readers debugging dependency problems and is not suitable to pipe into a script that does the distribution dependent license file lookup.
So maybe the code for --show-modules-output could be adapted to create a new option, for example called --show-source-files
The file written out by it could then look like this:
/usr/lib/python3.10/abc.py
/usr/lib/python3.10/ast.py
/usr/lib/python3.10/codecs.py
/usr/lib/python3.10/collections/__init__.py
[...]
/usr/lib/libpython3.10.so.1.0
/usr/lib/libssl.so.1.1

You could then use this and a distribution dependent script to get the necessary license files.

  > python -m nuitka --version
0.8.4
Commercial: None
Python: 3.10.5 (main, Aug  1 2022, 07:53:20) [GCC 12.1.0]
Flavor: Unknown
Executable: /usr/bin/python
OS: Linux
Arch: x86_64
Distribution: Sysrescue (based on arch) 9.04

How did you install Nuitka and Python
Arch Linux package nuitka 0.8.4-1 installed via pacman

does --include-data-files not do what you want?

My main problem right now is figuring out for which source files I have to add the licenses.
Finding all used source files should be done fully automatic and not by hand, because new dependencies with new licenses could be added without the developer doing anything, just because a package you actively import now requires some other package in a new version.
As far as I understand, --include-data-files would include the files, but I have to know in advance which files. So it could for example be used in a second run of nuitka, when I figured out all necessary license files in a first run.

Nuitka is not using AppImage anymore. I am not a lawyer either, but if the PyPI packages do not contain a license file, then your binary probably doesn't have to do it either.
Data files can be added to the Yaml configuration, where this an issue. I am pretty sure the PSF copyright notice is only for source code and not binaries, but I could be wrong there too.

I am putting this as invalid, as data files can be easily added to the Yaml configuration already, so there is no problem with that.

Nuitka has a compilation report with --report which contains what is included, and I think with the original source. If a file must be included, I welcome PRs that do that. In some instances, Nuitka already does it.

Thanks for the pointer to --report.
It contains the source files for included shared libraries like this:
<included_dll name="libssl.so.1.1" dest_path="libssl.so.1.1" source_path="/usr/lib/libssl.so.1.1" package="/usr/lib/libssl.so.1.1" ignored="no" />
<included_extension name="_lzma.so" dest_path="_lzma.so" source_path="/usr/lib/python3.10/lib-dynload/_lzma.cpython-310-x86_64-linux-gnu.so" package="/usr/lib/python3.10/lib-dynload/_lzma.cpytho
n-310-x86_64-linux-gnu.so" ignored="no" />

But it is missing source information for python modules (UncompiledPythonModule and CompiledPythonModule) used:
  <module name="http.client" kind="UncompiledPythonModule" reason="Instructed by user to follow all modules, including non-automatic standard library modules." />
<module name="dialog" kind="CompiledPythonModule" reason="Instructed by user to follow to all non-standard library modules." />

I would appreciate it if you could add the source files for these to the report file. Thanks.

I might do it if the request was related to this: https://nuitka.net/doc/commercial.html
Currently the report is a feature that is not complete, and I spotted a bug in your output, but I don't think I have the time right now to do this. You can write a Nuitka plugin, they also get this information. I don't see this as a priority right now.

Without a comprehensive list of sources it is very hard to find out which source files and licenses are actually used and have to be dealt with. Without complying with all the license conditions of all used modules and shared libraries, you are not allowed to distribute the resulting binary.
For me using Nuitka becomes moot when I am not allowed to distribute the resulting binary. So I rate this as something like a showstopper.


Slotify list section

Added Slots to the ListSection. The renderItem prop was replaced by a scopedSlot called item. The filter buttons can now also be rendered using a scoped slot. This is optional though.

looks good to me (I just left one comment on preposition use in a code comment, which could be improved)

looks good to me (I just left one comment on preposition use in a code comment, which could be improved)


fix capitalization

There were two unnecessary capitalizations.

/retest

Hi! Can this PR get an approval label? Thanks!

@tengqm Hi, could you help? Thanks!

/lgtm
/approve


What is missing for the State Management Query API to move to the beta stage?

In what area(s)?
/area runtime
/area test-and-release
What is missing for the State Management Query API to move to the beta stage?
The State Management Query API is currently in the alpha stage, I am interested by using it in business critical use cases.
When can we expect to have it moved at least to the beta stage ? Are we missing conformance tests for the Query API?
What contribution would help to move this forward?

It is mentioned on other issues somewhere but the consensus was it was not going to be developed any further and instead we anticipate a document store component that will have a general query mechanism. This is where the effort is being invested and i believe its not too far away..

@theperm thank you for your reply.


reflect: reflect.flag.mustBeAssignable using value obtained using  unexported field

https://github.com/matryer/goblueprints/blob/aae50b4b30fa6dfd73e3c411b3bfe1972294be61/chapter7/meander/query.go#L115
https://github.com/matryer/goblueprints/blob/aae50b4b30fa6dfd73e3c411b3bfe1972294be61/chapter7/meander/query.go#L20
This line cause me: reflect: reflect.flag.mustBeAssignable using value obtained using  unexported field
But, if I specify field names here, It works

I have the same problem. Can u tell me how works for you?

Try GoogleGeometry - this should make it exported (and not "unexported")


chore(typings): improve zip typings

Add signature to the lettable zipProto so it's consistent with the
non-lettable zipProto.

Description:
This PR is closely related to #2787. In between that PR being submitted and its being merged there were WIP commits made re: lettable operators. Consequently, the overload signature that the PR added to the non-lettable zipProto was not included in the lettable zipProto.
This PR adds the relevant overload to the lettable zipProto.
Related issue (if exists): #2784

Unfortunately, this PR falls victim to TypeScript matching arbitrary functions with ArrayLike<any> and, consequently, with ObservableInput<any>. That means that if T is any there is no sensible order for:
export function zip<T>(...observables: Array<ObservableInput<T>>): OperatorFunction<T, T[]>;

and:
export function zip<T, R>(...observables: Array<ObservableInput<T> | ((...values: Array<T>) => R)>): OperatorFunction<T, R>;

When T is any the whichever is first will be matched regardless of whether or not a projection function is specified.
This is a pity, as when T is not any it works fine. Such is life.
This also means that the signature added in PR #2787 is also unsafe when T is any and should probably be removed.


Process Death discussion

Does the library support Process Death 💀? If the App process gets killed by the system and the App is relaunched, does the state recover automatically to the same value it had before the process was killed?
Or persisting relevant process death recovery data is left to the developer according to the App business logic.

This library has no opinions on how to handle process death:
My take: Handle it in any way you prefer: Store the relevant data and restore ist at the correct lifecycle methods!

Got it


fix(radio): [ie11] dont collapse margin on label

Fixes: #458
Could not get to the bottom of why only IE did this.  It has something
to do with the Halo positioning.  Think it's related to IE's treatment
of splitting up the flex space.  Instead of flexing, just
display-inlined the circle and label.

@danethurber , I adjusted again in order to get better label wrapping.  Added extra div to help layout.  IE seems to be doing ok with it.


kup list PKG to show which versions we already have local caches of

Is it possible to have kup list PKG display which versions I already haev in local cache? Maybe as another column, or as a color code (with a legend).

I know I've installed one of these in the past, and removed it (for testing something), but I have no idea which one. I'd like to reinstall it, doesn't matter which version, just want the one that's already cached.

So kup clean and kup gc would basically just be pre-filled Nix commands as well, but targeting our packages? I like that idea.
Is there any way we could just have a generic way to call any nix command with the arguments prefilled to filter for our needs?

This has been implemented for the binary cache now:


URL link to MVP Plasma has an extra '.' at the end

The extra '.' makes it resolve to a 404, removing it fixes the problem.

Fixed in #12


Add pagination and sorting to transactions table

This commit adds pagination and sorting to the transaction table to
avoid showing a very long table.
Changes:

Add pagination component.
Use pagination component on transaction table.
Add sorting to transaction table headers.
Adjust text overflow for columns in transaction table.

Also updates Bootstrap to 4.1.1.
Closes #20

Codecov Report

Merging #25 into master will increase coverage by 2.64%.
The diff coverage is 83.63%.

@@            Coverage Diff            @@
##           master     #25      +/-   ##
=========================================
+ Coverage   54.65%   57.3%   +2.64%
=========================================
  Files          35      37       +2
  Lines         569     616      +47
=========================================
+ Hits          311     353      +42
- Misses        258     263       +5

Impacted Files
Coverage Δ

src/components/transactions/TransactionRow.js
72.72% <ø> (ø)
:arrow_up:

src/index.js
0% <0%> (ø)
:arrow_up:

src/components/Transactions.js
56.52% <100%> (ø)
:arrow_up:

src/components/shared/Pagination.js
78.94% <78.94%> (ø)

src/components/transactions/SortHeader.js
87.5% <87.5%> (ø)

src/components/transactions/TransactionTable.js
96% <95.83%> (+8.5%)
:arrow_up:

src/components/transactions/CategorySelect.js
75% <0%> (+37.5%)
:arrow_up:

Continue to review full report at Codecov.

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


Canary Deployment for config

Description:
Hi there
I'd like to inquire about the process for adding or updating a new route or similar configurations. Is there an approach available that allows us to implement a canary release for these configurations?

Do you mean you want to apply the new config for just part of the incoming requests?
If that's the case, EG doesn't have a "Canary Deployment for config" feature, but you can try to use weighted routing to achieve something similar.

I think this can be achieved by deploying two Envoy Gateway instances side by side, one for serving the production traffic, and one for canary/testing traffic. Once the testing is done, we can change the DNS to point to the canary one.

@zhaohuabing  do you have example?

@zhaohuabing  do you have any example?

I didn't try it myself. You're free to try this approach and report back any findings in this issue.
You can set a different controller name in the values.yaml when installing the canary eg instance, then you can have two sets of configurations, one for production, and one for canary testing.
For example:
controller name: gateway.envoyproxy.io/gatewayclass-controller-1 -> gateway calss: eg1 -> gateway1 -> xRoute1
controller name: gateway.envoyproxy.io/gatewayclass-controller-2 -> gateway calss: eg2 -> gateway2 -> xRoute2

Got it thanks

@sonnydinhgc PTAL https://gateway.envoyproxy.io/latest/user/deployment-mode/

closing this one since the solution has been shared


Cannot read property 'normalModuleFactory' of undefined

I configured the WorkerPlugin plugin in my vue project, and the result project could not be started. The error message is: "Cannot read property normalModuleFactory of undefined"

Hi @873550602 - can you tell me what version of Webpack this would be using? WorkerPlugin requires Webpack 4+.

Closing as this is almost certainly just unsupported usage with Webpack 3.x.


Record video explanations

explain test providers; why/how
explain how teams can setup reusable test scenarios
explain test shorthand

I will suggest to start the video , telling the viewers they have to follow the steps from the ReadMe page under **Usage **. Because the steps work fine , are so easy to follow , take some time to complete and the viewer must have done his/her homework.
then , in my opinion
-how to add a custom page
-maybe talk to some time of http endpoint
-make an allusion that is the pro version of https://github.com/mgechev/angular2-seed
-show the results of creating and removing a new framework for your application in src/client/app/frameworks
-explain the awesome power of the nativerScript engine ,
-briefly talk about how Electron helps the seed and how to always keep the app fine to build with Eelectron.
IMHO.
regards

Really really appreciate this suggestion @OscarAgreda, part of the reason I have procrastinated recording the video is I keep going back/forth on what should be highlighted in a help video.
This helps a ton and totally agree.

Thank you :100:
Also, the first thing a user wanting to use the template will need nativeScript PLUGINS to talk to the camera and location via GPS, etc.
in the past, when all we have was the apache cordova + ionic. that was such a painful experience , so thank you for this seed, once again.
and, regarding Electron , is it possible to use the autoUpdater  so when the developer changes the app and re-deploy, the user running the desktop version of it, receives an alert to update. In this way always keep just one Codebase but several platforms (desktop. mobile and web).

Hello @nathanwalker
Any news on the video.

Hi @OscarAgreda due to some refactorings this was placed in long delay. There is one more refactor that will take place over the next week and after that, it should clear the way to record some videos. Thanks for the ping.

@OscarAgreda so sorry for delay in these videos. They take time to do well and have not had ample time this summer to produce them. If you have any specific questions, feel free to ask though.

Just want to add that I'm looking forward to the videos. I saw your nativescript-ng2-magic one and you did a great job. Now that Angular 2 is final... let's do it ;)

I plan to cover this seed in depth in a future egghead.io course.


03/25/2018 17:10 : Create Pull Request for branch master -> prTesting1_2018032517

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fixed missing $ for to get correct JDK version

Thank you for submitting this pull request

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

closed because it is the same as #908

closed because it is the same as #908


Use a different coloring for component slots (i.e. renderfragment parameters)

in this image, Menu is a [Parameter] of type RenderFragment - thus creating a Slot to put things into.
I suggest that those slots should be drawn in a different color to differentiate their declarations from actual component instanciations.

This is mostly tooling, but I assume if we wanted to do this, we'd need the compiler to classify them differently?

I don't know for sure, but I suspect there is enough metadata in a tag helper descriptor that this can probably be done entirely on the tooling side.


KAFKA-9976: Reuse repartition node in all cases

If a KGroupedStream or KGroupedTable requires a repartition, reusing the same instance results in creating a new repartition topic.   Unless the user provides a name via Grouped.  However, we should have consistent behavior regardless if the user provides a name or Kafka Streams generates it.
This PR changes the behavior to create one repartition topic (if required) per instance.
I've updated the test cases.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

ping @mjsax and @vvcephei for review

Java 11 passed.
Java 8 failed with org.apache.kafka.streams.integration/EosBetaUpgradeIntegrationTest/shouldUpgradeFromEosAlphaToEosBeta_true
Java 14 failed with org.apache.kafka.streams.integration/EosBetaUpgradeIntegrationTest/shouldUpgradeFromEosAlphaToEosBeta_false_
retest this please.

@bbejeck Wondering if there are any backward incompatibility concerns? Can you explain why this change is safe? For #8504 there would be an exception before and thus it was broken and no compatibility concern raises. Not 100% sure about this PR though.

Seems you agree to my last comment: https://github.com/apache/kafka/pull/8504#issuecomment-631757206
I think it's best to close this PR and also the ticker (either as "not a problem" or "won't fix")?

I think it's best to close this PR and also the ticker (either as "not a problem" or "won't fix")?

ack


Jcarrillosrc/decimals_in_populated_entities_are_always_updated_after_select

Add more tests cases for the same issue.
The problem was not fixed when decimal fraction is zero or missing in decimal numbers. Ex: "11.00" or "11"
I suggest to repalce "compareValues" method of DecimalType class by this code:
compareValues(a, b) {
    return String(a).replace(/(\.(0+))$/, '') === String(b).replace(/(\.(0+))$/, '');
}

66e60cb04463fb6163d2f0a386d9fd9be36fe257


Craft CMS guide: add SSG guide community resource

Description (required)

This PR adds a new Community Resource link to the Craft CMS guide. The link is to a guide to building a static Astro site with data fetched dynamically in dev and once during build.
Related issues & labels (optional)

Suggested label: add-new-content

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/cms/craft-cms.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Issue 64 fix

This pull request fixes Issue #64.
The changes here are more substantial than with my previous pull request (for Issue #62) because these changes add guards for cases where user_info or host are initialized but empty.

LGTM, thanks again.


Issue with time of expiration.

Hi,
I'm quite new to ios development.
I'm having a bit of trouble understanding how your isJWTExpired and expireDateOfJWT works.
My token looks like this:
eyJhbGciOiJIUzI1NiIsImV4cCI6MTQyNzQ2OTA4NSwiaWF0IjoxNDI3NDY4Nzg1fQ.eyJ1c2VyX2lkIjo0LCJuYmYiOjE0Mjc0ODY3ODIuMCwiZXhwIjoxNDI3NDg3MDgyLjB9.X1o75sv3-Iq4mk3gmHYysnkOS-CfRi4dOQ97fOq3I10
From what your code is saying, it is taking the exp from the claims section correct? So that should be<PHONE_NUMBER>
var exp2 = NSDate(timeIntervalSince1970:1427487082.doubleValue)
When running the code through swift playground I'm getting "Mar 27, 2015, 3:11 PM" <<< UTC time.., which I believe is correct. But when I use your expiryDate method it returns back 2015-03-27 20:11:22 +0000.
I'm a bit puzzled as to why this is happening. Is it me sending the incorrect time?
Thanks :)

It's not the incorrect time, its a matter of how the data is displayed. Try printing the value of the property timeIntervalSince1970 in exp2 and what the library returns and they should be the same.
The playground prints the value of this line:
var exp2 = NSDate(timeIntervalSince1970:1427487082.doubleValue)

using your Mac's timezone, but if you add this line:
exp2.description

you'll see it displayed in UTC

@hzalaz I'm having trouble with the ".expired" part with after decoding the token. i'm getting a mismatch between what the server is sending out and what swift code is interpreting the "exp" as. Could you please explain how the ".expired" attribute works? Thanks!

It's just a timestamp and that's how it's handled, and how it explained before. The value of exp a numeric value, is the number of seconds since 1970 so we are using NSDate(timeIntervalSince1970: expValue) to get a date object. Not sure what mismatch you are talking about, possibly as I said before, it is a Tz issue and how you print the dates but if you compare them as timestamp they should be the same.


fix(registry): Use proper hostname for dockerhub images

docker-py will return hostname as 'docker.io' if the image is from dockerhub  but the server address is different than that.
fixes #919

ping @jdumars. Mind trying to deploy this patch to your cluster and see if this fixes your issue? you should be able to do the following to test it:
cd controller
git remote add kmala git@github.com:kmala/controller
git fetch kmala bug
git checkout bug
make deploy
deis destroy -a bar --confirm=bar
deis create foo
deis config:set PORT=8080
[...]

@kmala can you explain how this should fix issue in the commit message? Is this because the hostname is docker.io in @jdumars' secret registry config when it should be https://index.docker.io/v1/?

Also is there a way we can add unit tests for this please

Current coverage is 85.70% (diff: 50.00%)

Merging #920 into master will increase coverage by 0.17%

@@             master       #920   diff @@
==========================================
  Files            30         30
  Lines          3014       3016     +2
  Methods           0          0
  Messages          0          0
  Branches        503        504     +1
==========================================
+ Hits           2578       2585     +7
+ Misses          290        287     -3
+ Partials        146        144     -2

Powered by Codecov. Last update bc1ed14...4b0967b

Tested this change on my cluster and it worked.

@bacongobbler i think it is tough to write a unit test but we can write a e2e test

We should test this change thoroughly. I had tried to make a similar change in Deis v1 controller and could never get it working solidly--there is odd behavior in the Docker client around special handling for Docker Hub, although it may have had to do with the routing between the v1 and v2 registry API endpoints.
This looks safe to me, just sayin'.

@kmala you can write a unit test for _set_image_secret here. Try pulling out the secret generation logic into a separate function and write a unit test for that function's expected input and output. For an example, see https://github.com/deis/controller/blob/master/rootfs/scheduler/tests/test_scheduler.py#L22-L55.

Yeah, that should work as a test plan. Would be good to get some test going for just the generated secret content


Refresh token flow doesn't extend access token lifetime

The existing expires_in gets fed into the refreshed token, which causes the token to not be renewable. Ideally a token authorization can be kept alive indefinitely through continually refreshing, but the library is currently forcing a reauthorization due to this issue.
https://github.com/lepture/authlib/blob/master/authlib/oauth2/rfc6749/grants/refresh_token.py#L132

Actually looks like I misinterpreted the implementation of expires_in on the credentials, which is a static value stored, not the current point-in-time expires in value.


Publishing on PECL

I would like to thank you for this fantastic extension. It helped our company easily test time-aware features.
Are there any plans for publishing this extension in PECL or PEAR2? It would simplify the installation procedure.

Agreed this would be a great addition to standard PECL libraries.

It is on pecl now: http://pecl.php.net/package/timecop

Awesome!

Now we publish php-timecop on PECL. Thanks for opening the issue and all the thumbs up!
As unexpected side-effects, we are able to support Windows platform thanks to PECL's DLL build system.


Leave switch as-is but just extract branches to function calls

Just to see if this alone has a perf diff.

@typescript-bot perf test this faster

@DanielRosenwasser good news! The perf improvements aren't from the switch-case change, and I'm not going crazy reading the v8 source code, unable to figure out why the switch was deoptimized! Just extracting the various cases into individual functions looks to be most if not all of the performance improvement. So it looks like it's not the switch that's an issue, but rather the length and polymorphism of the function itself.

@typescript-bot perf test this
For LS numbers for this, too~

I do like the improved safety of this one over #50225.
Would the perf be identical if these functions were instead declared at the bottom of forEachChild? That way, nobody could actually try and call them.
(This is probably very moot post-modules, as this whole thing could be its own file that doesn't export them.)

I wonder if V8 is using a jump table for the switch now that it has no fall-through cases.

Would the perf be identical if these functions were instead declared at the bottom of forEachChild? That way, nobody could actually try and call them.

These functions don't need to be exported from ts either and it might make sense to just move forEachChild et all to its own file anyways.

I ultimately like @DanielRosenwasser 's PR more, simply because it is yet more performant, but it looks like the perf improvement is correlated with the instruction length of the function and not the presence or lack thereof of the switch, which is what I wanted to confirm with this.

I wonder if V8 is using a jump table for the switch now that it has no fall-through cases.

Based on the conditions for switch optimization I read in the v8 sources, both before this PR and with this PR, the switch should be optimized to a jump table. For an interpreted function, you get a jump table so long as you have a minimum number of branches and cover at least 33% of the range of inputs (measured as the difference between the min and max case values). On x64, for a compiled function, there's a somewhat complex space/time tradeoff heuristic where it falls back to a binary search, but it weights the time metric more, and for anything with a somewhat densely filled out list of cases, should prefer the jump table. There's links to the relevant v8 sources in our internal discussions, if you're curious about the exact heuristic. AFAIK, the 128 case limit mentioned in the recently-trended blog post about a perf problem from 2013 no longer seems to exist - on x64, the max case count for a jump table is 2 << 16. (And fall throughs don't seem to affect it in any way - they count as a case same as any other)


Documented information about sleep and wake namespace

Fixes: https://github.com/okteto/docs/issues/364

Hi @pchico83, the changes have been pushed.

This PR is ready to be merged now!

Could we make it optional? that way, okteto namespace sleep sleeps the current namespace in my okteto context

Did you mean to exclude mentioning about okteto sleep? If No, we can add more information about okteto sleep mentioning something like "it sleeps the active namespace...".

Could we make it optional? that way, okteto namespace sleep sleeps the current namespace in my okteto context

Did you mean to exclude mentioning about okteto sleep? If No, we can add more information about okteto sleep mentioning something like "it sleeps the active namespace...".

@NitishKumar06 I mean that okteto namespace sleep and okteto namespace wake should work without specifying the namespace name. In that case, we should sleep|wake the current namespace. We can get the current namespace from the okteto context with okteto.Context().Namespace

@NitishKumar06 I mean that okteto namespace sleep and okteto namespace wake should work without specifying the namespace name. In that case, we should sleep|wake the current namespace. We can get the current namespace from the okteto context with okteto.Context().Namespace

That's correct. However, we've configured sleep and wake in such a way that both of these commands requires at least 1 argument to successfully execute. I think we'll need to raise a new PR at okteto/okteto for this addition as well. WDYT?

@NitishKumar06 I mean that okteto namespace sleep and okteto namespace wake should work without specifying the namespace name. In that case, we should sleep|wake the current namespace. We can get the current namespace from the okteto context with okteto.Context().Namespace

That's correct. However, we've configured sleep and wake in such a way that both of these commands requires at least 1 argument to successfully execute. I think we'll need to raise a new PR at okteto/okteto for this addition as well. WDYT?

@NitishKumar06 yes, I would add that functionality to okteto/okteto before documenting it. It's how most people will use that command, and I think it's better to educate users that way from the beginning.

Hi @pchico83, I've added this functionality via this PR. We're good to go with documenting it now.

After the successful merge of PR, are we ready to proceed with next round of review?

@rberrelleza @omnomagonz could you review this PR?

Thanks @NitishKumar06 for taking care of documenting the feature!

Thanks @NitishKumar06 for taking care of documenting the feature!

My pleasure! I'd like to inform the community about this update. How about sending a message on slack mentioning about the docs we have updated? Or shall we wait if needed?

@NitishKumar06 I would wait until the next official CLI release. I think that's the one including the latest fixes.
After merging the docs, they don't go to the main page until we do the next release.
The go to "latest":
https://www.okteto.com/docs/1.8/reference/cli

@NitishKumar06 I would wait until the next official CLI release. I think that's the one including the latest fixes. After merging the docs, they don't go to the main page until we do the next release. They go to "latest": https://www.okteto.com/docs/1.8/reference/cli

I see. Do we have dates we're targeting for the next okteto CLI release?

@NitishKumar06 I would wait until the next official CLI release. I think that's the one including the latest fixes. After merging the docs, they don't go to the main page until we do the next release. They go to "latest": https://www.okteto.com/docs/1.8/reference/cli

I see. Do we have any dates we're targeting for the next okteto CLI release?

Around 2 weeks from now

Around 2 weeks from now

Awesome! Looking forward to contributing more!