damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17: [BUG] Segmentation fault at 0x00007ffee4716000

Crash when I try to get the Edit Distance.
$ ruby test.rb
/Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17: [BUG] Segmentation fault at 0x00007ffee4716000
ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin18]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0004 p:---- s:0026 e:000025 CFUNC  :internal_distance
c:0003 p:0029 s:0018 e:000017 METHOD /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17
c:0002 p:0033 s:0010 E:000810 EVAL   test.rb:5 [FINISH]
c:0001 p:0000 s:0003 E:000800 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
test.rb:5:in `<main>'
/Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17:in `distance'
/Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17:in `internal_distance'

-- Machine register context ------------------------------------------------
 rax: 0x000000000000022d rbx: 0x0000000000000049 rcx: 0x00007ffee4713a08
 rdx: 0x0000000000000002 rdi: 0x00000000ffffffff rsi: 0x000000000000022e
 rbp: 0x00007ffee4714fa0 rsp: 0x00007ffee4713a00  r8: 0x0000000000000049
  r9: 0x000000000000022d r10: 0x0000000000000000 r11: 0x000000000000022f
 r12: 0x00007ffee4713a00 r13: 0x00007ffee4714e98 r14: 0x0000000000000001
 r15: 0x00007ffee4714e90 rip: 0x000000010db5cd14 rfl: 0x0000000000010246

-- C level backtrace information -------------------------------------------
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(rb_vm_bugreport+0x82) [0x10b725532]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(rb_bug_context+0x1d6) [0x10b575d56]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(sigsegv+0x51) [0x10b68aa81]
/usr/lib/system/libsystem_platform.dylib(_sigtramp+0x1d) [0x7fff66b0eb1d]
/Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/damerau_levenshtein.bundle(method_internal_distance+0x4b4) [0x10db5cd14]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(vm_call_cfunc+0x156) [0x10b717ec6]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(vm_exec_core+0x31ba) [0x10b6feada]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(rb_vm_exec+0xac4) [0x10b712914]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(ruby_exec_internal+0xe6) [0x10b580d36]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(ruby_run_node+0x49) [0x10b580ba9]
/Users/puritysb/.rbenv/versions/2.6.0/bin/ruby(main+0x5d) [0x10b4eb2ed]

-- Other runtime information -----------------------------------------------

* Loaded script: test.rb

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/x86_64-darwin18/enc/encdb.bundle
    5 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/x86_64-darwin18/enc/trans/transdb.bundle
    6 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/x86_64-darwin18/rbconfig.rb
    7 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/compatibility.rb
    8 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/defaults.rb
    9 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/deprecate.rb
   10 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/errors.rb
   11 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/version.rb
   12 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/requirement.rb
   13 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/platform.rb
   14 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/basic_specification.rb
   15 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/stub_specification.rb
   16 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/delegate.rb
   17 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/rfc2396_parser.rb
   18 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/rfc3986_parser.rb
   19 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/common.rb
   20 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/generic.rb
   21 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/file.rb
   22 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/ftp.rb
   23 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/http.rb
   24 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/https.rb
   25 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/ldap.rb
   26 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/ldaps.rb
   27 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri/mailto.rb
   28 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/uri.rb
   29 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/specification_policy.rb
   30 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/util/list.rb
   31 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/x86_64-darwin18/stringio.bundle
   32 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/specification.rb
   33 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/exceptions.rb
   34 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/util.rb
   35 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/bundler_version_finder.rb
   36 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/dependency.rb
   37 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb
   38 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/monitor.rb
   39 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb
   40 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/core_ext/kernel_warn.rb
   41 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems.rb
   42 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/2.6.0/rubygems/path_support.rb
   43 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/version.rb
   44 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/core_ext/name_error.rb
   45 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/levenshtein.rb
   46 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/jaro_winkler.rb
   47 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checker.rb
   48 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb
   49 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb
   50 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/name_error_checkers.rb
   51 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/method_name_checker.rb
   52 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/key_error_checker.rb
   53 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/spell_checkers/null_checker.rb
   54 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/formatters/plain_formatter.rb
   55 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean/tree_spell_checker.rb
   56 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/did_you_mean-1.4.0/lib/did_you_mean.rb
   57 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/version.rb
   58 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/damerau_levenshtein.bundle
   59 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/formatter.rb
   60 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/differ.rb
   61 /Users/puritysb/.rbenv/versions/2.6.0/lib/ruby/gems/2.6.0/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html

[IMPORTANT]
Don't forget to include the Crash Report log file under
DiagnosticReports directory in bug reports.

here is test code for reproduce
require 'damerau-levenshtein'
dl = DamerauLevenshtein
text1 = "I am QA"
text2 = "IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII"
edit_distance = dl.distance(text1, text2)

My Desktop env : Mac OS Mojave

I can confirm, I have the same issue on OSX Mojave with Ruby 2.6.5. May this be related to #19?
/Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17: [BUG] Segmentation fault at 0x00007ffeef265000
ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-darwin19]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0004 p:---- s:0026 e:000025 CFUNC  :internal_distance
c:0003 p:0029 s:0018 e:000017 METHOD /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17
c:0002 p:0033 s:0010 E:000380 EVAL   levenshtein.rb:23 [FINISH]
c:0001 p:0000 s:0003 E:000d80 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
levenshtein.rb:23:in `<main>'
/Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17:in `distance'
/Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb:17:in `internal_distance'

-- Machine register context ------------------------------------------------
 rax: 0x0000000000000223 rbx: 0x0000000000000049 rcx: 0x00007ffeef262a58
 rdx: 0x0000000000000002 rdi: 0x00000000ffffffff rsi: 0x0000000000000224
 rbp: 0x00007ffeef263ff0 rsp: 0x00007ffeef262a50  r8: 0x0000000000000049
  r9: 0x0000000000000223 r10: 0x0000000000000000 r11: 0x0000000000000225
 r12: 0x00007ffeef262a50 r13: 0x00007ffeef263ee8 r14: 0x0000000000000001
 r15: 0x00007ffeef263ee0 rip: 0x0000000103022d14 rfl: 0x0000000000010246

-- C level backtrace information -------------------------------------------
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(rb_vm_bugreport+0x82) [0x100be13d2]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(rb_bug_context+0x1d6) [0x100a2fd96]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(sigsegv+0x51) [0x100b460c1]
/usr/lib/system/libsystem_platform.dylib(_sigtramp+0x1d) [0x7fff699965fd]
/Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/damerau_levenshtein.bundle(method_internal_distance+0x4b4) [0x103022d14]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(vm_call_cfunc+0x156) [0x100bd3c46]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(vm_exec_core+0x33da) [0x100bba81a]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(rb_vm_exec+0xac4) [0x100bce694]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(ruby_exec_internal+0xe6) [0x100a3ae16]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/libruby.2.6.dylib(ruby_run_node+0x49) [0x100a3ac89]
/Users/danielsenff/.rvm/rubies/ruby-2.6.5/bin/ruby(main+0x5d) [0x10099bf0d]

-- Other runtime information -----------------------------------------------

* Loaded script: levenshtein.rb

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/x86_64-darwin19/enc/encdb.bundle
    5 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/x86_64-darwin19/enc/trans/transdb.bundle
    6 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/x86_64-darwin19/rbconfig.rb
    7 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/compatibility.rb
    8 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/defaults.rb
    9 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/deprecate.rb
   10 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/errors.rb
   11 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/path_support.rb
   12 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/version.rb
   13 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/requirement.rb
   14 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/platform.rb
   15 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/basic_specification.rb
   16 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/stub_specification.rb
   17 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/delegate.rb
   18 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/rfc2396_parser.rb
   19 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/rfc3986_parser.rb
   20 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/common.rb
   21 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/generic.rb
   22 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/file.rb
   23 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/ftp.rb
   24 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/http.rb
   25 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/https.rb
   26 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/ldap.rb
   27 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/ldaps.rb
   28 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri/mailto.rb
   29 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/uri.rb
   30 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/specification_policy.rb
   31 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/util/list.rb
   32 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/x86_64-darwin19/stringio.bundle
   33 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/specification.rb
   34 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/exceptions.rb
   35 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/util.rb
   36 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/bundler_version_finder.rb
   37 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/dependency.rb
   38 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_gem.rb
   39 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/2.6.0/monitor.rb
   40 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_require.rb
   41 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems/core_ext/kernel_warn.rb
   42 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/site_ruby/2.6.0/rubygems.rb
   43 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/version.rb
   44 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/core_ext/name_error.rb
   45 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/levenshtein.rb
   46 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/jaro_winkler.rb
   47 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checker.rb
   48 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb
   49 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb
   50 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/name_error_checkers.rb
   51 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/method_name_checker.rb
   52 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/key_error_checker.rb
   53 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/spell_checkers/null_checker.rb
   54 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean/formatters/plain_formatter.rb
   55 /Users/danielsenff/.rvm/rubies/ruby-2.6.5/lib/ruby/gems/2.6.0/gems/did_you_mean-1.3.0/lib/did_you_mean.rb
   56 /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/version.rb
   57 /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/damerau_levenshtein.bundle
   58 /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/formatter.rb
   59 /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein/differ.rb
   60 /Users/danielsenff/.rvm/gems/ruby-2.6.5/gems/damerau-levenshtein-1.3.2/lib/damerau-levenshtein.rb

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html

[IMPORTANT]
Don't forget to include the Crash Report log file under
DiagnosticReports directory in bug reports.

[1]    33556 abort      ruby levenshtein.rb

ruby 2.7.1p83 on macOS 10.15.5 executes the code snippet successfully and will return 656.

Worked for me for ruby 2.6.6 and 2.7.1 on Linux 64bit, and MacOS 10.15.5, before upgrading to MacOS 10.15.5 I could reproduce this problem. So looks like it was MacOS bug, and it is now fixed.


python udf test failed in ci

Describe the bug
https://buildkite.com/risingwavelabs/pull-request/builds/26579#01890c85-b8aa-46e5-9cdb-72a18dab5f53

Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

cc @jon-chuang Is it a flaky case?

Does it fail anywhere else? This function was always at risk of flakey-ness. It is possibly due to CPU contention that interrupts the thread from other tests.
If it is not super flakey, I propose to ignore it at ask the user to run again. We don't track test flaky-ness anywhere, do we?

Does it fail anywhere else?

Not that I know of.
I guess a rerun is good enough since it rarely happens.


Migration fails with: "TypeError: Cannot redefine property: then"

I created the following migration file:
import { Kysely, sql } from 'kysely'

export async function up(db: Kysely<any>): Promise<void> {
  await db.schema
    .createTable('person')
    .addColumn('id', 'serial', (col) => col.primaryKey())
    .addColumn('first_name', 'varchar', (col) => col.notNull())
    .addColumn('last_name', 'varchar')
    .addColumn('gender', 'varchar(50)', (col) => col.notNull())
    .addColumn('created_at', 'timestamp', (col) =>
      col.defaultTo(sql`now()`).notNull()
    )
    .execute()
}

export async function down(db: Kysely<any>): Promise<void> {
  await db.schema.dropTable('person').execute()
}

And then I tried to run the migration with npm run kysely migrate:up but it failed with the following error message:

Migration failed with TypeError: Cannot redefine property: then

If I remove the following code and retry the migration, it completes successfully:
.addColumn('created_at', 'timestamp', (col) =>
  col.defaultTo(sql`now()`).notNull()
)

In my kysely.config.ts file I have the following code:
import { Kysely, PostgresDialect } from "kysely";
import { defineConfig } from "kysely-ctl";
import { Pool } from 'pg'

const connectionString = process.env.DATABASE_URL ?? ''

const dialect = new PostgresDialect({
  pool: new Pool({
    connectionString: connectionString
  })
})

export default defineConfig({
  dialect: dialect,
  migrations: {
    migrationFolder: 'migrations',
  },
});

It seems a bug to me but I'm not sure if I'm missing something else.

Hey 👋
Try adding up() and running this migration using npx tsx <filepath>, does it still happen?

I created one: https://github.com/EmptySpace99/test-kysely-ctl

Thanks for the reproduction. I was able to debug and think that https://github.com/kysely-org/kysely/pull/1031 should solve it - it did on my machine when hard-coding that change.
You should patch kysely in your project for now following the changes in that PR using something like https://www.npmjs.com/package/patch-package OR https://pnpm.io/cli/patch.

Thank you so much, effectively turning the project to ESM fix the problem. Probably this is the easiest fix for now, hope that the real fix will be merged soon. 💪🏻


license

Version of Kpow
The version of Kpow you are running
community latest docker
Describe the issue
A clear and concise description of the issue
emailed license is incorrect
Additional context
Add any other context about the problem here.
license:
License Certificate 8145ba1d-efcd-43ab-bb08-987c0d060c8e
--------BEGIN LICENSE CERTIFICATE-------
ID: 8145ba1d-efcd-43ab-bb08-987c0d060c8e
Type: Kpow Community
Licensee: Arkady Rosenberg
Expiry: 2025-12-16
Cluster Credits: 1
6AE01D67 C4F3A91B 324F43B4 661E3CC2
201144BA 587A3D91 1E87FF1F B4DC38AB
6ADA08AB 2806A5D8 6C13272C FF6ED863
AFAB9057 7A071149 F67DAFE4 30491D96
AF15F3A8 BD74D5B1 1DD3B113 FB10F072
5CE7C824 E1F58A5A 3D050EA7 572C4E47
D1DAB9BC E3B55032 A24E4892 06191500
2BE745E2 AF687D75 2FBAB2FF C41C2CCD
--------END LICENSE CERTIFICATE---------
.env file according to manual here - https://docs.factorhouse.io/kpow-ce/configuration/#license
The Kafka Bootstrap URL for your cluster (Required).
BOOTSTRAP=<IP_ADDRESS>:9092,<IP_ADDRESS>:9092,<IP_ADDRESS>:9092
Your license details (Required).
These parameters can be cut/paste from your license email
LICENSE_ID=8145ba1d-efcd-43ab-bb08-987c0d060c8e
LICENSE_CODE=Kpow Community
LICENSEE=Arkady Rosenberg
LICENSE_EXPIRY=2025-12-16
LICENSE_SIGNATURE=6AE01D67C4F3A91B324F43B4661E3CC2201144BA587A3D911E87FF1FB4DC38AB6ADA08AB2806A5D86C13272CFF6ED863AFAB90577A071149F67DAFE430491D96AF15F3A8BD74D5B11DD3B113FB10F0725CE7C824E1F58A5A3D050EA7572C4E47D1DAB9BCE3B55032A24E4892061915002BE745E2AF687D752FBAB2FFC41C2CCD
output of container:
-- Installation ----------------------------------------------------------------

Release: 93.4 (2024-08-20-15-00)
Java Runtime: 17.0.12
Product Type: Unlicensed
-- Components ------------------------------------------------------------------
~ ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Exception starting Kpow. Please check your configuration:

Failing component: [:kpow/license "details"]
Inputs:

code: 'Kpow Community'
id: '8145ba1d-efcd-43ab-bb08-987c0d060c8e'
licensee: 'Arkady Rosenberg'
expiry: '2025-12-16'
signature: '6AE01D67C4F3A91B324F43B4661E3CC2201144BA587A3D911E87FF1FB4DC38AB6ADA08AB2806A5D86C13272CFF6ED863AFAB90577A071149F67DAFE430491D96AF15F3A8BD74D5B11DD3B113FB10F0725CE7C824E1F58A5A3D050EA7572C4E47D1DAB9BCE3B55032A24E4892061915002BE745E2AF687D752FBAB2FFC41C2CCD'

Message: license details incorrect
Relevant documentation: https://docs.kpow.io/ce/configuration/#license
Don't have a license? Visit https://kpow.io/get-started/ to get a free community license.

resolved, need to read the WHOLE email :)

Hey @intelligent002 thanks for raising the ticket anyway.
At a guess we should think of having the license environment variables at the top of the email rather than the certificate, I think that trips people up sometimes..


Adding Azure Search SDK (preview)

Can one of the admins verify this patch?

Hi @brjohnstmsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (brjohnst). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci add to whitelist


Stirling-PDF: replace dependency for v0.35.0 and add check and fix in stirling-pdf.sh

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
Version 0.35.0 of Stirling-PDF now uses qpdf for OCR instead of ocrmypdf. This PR replaces ocrmypdf with qpdf in the install script, and for those with existing installations updating to 0.35.0 and later, checks for and replaces the packages during the update process.
Fixes #590
Type of change
Please check the relevant option(s):

[x] Bug fix (non-breaking change that resolves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[x] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[x] Testing performed (I have tested my changes, ensuring everything works as expected)
[ ] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
See discussion at #590 for screenshots of the issue.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Why are things being merged without approvals?
Is the if check in this PR needed? Will apt-get remove crash the script if it does not find the package? will apt-get install crash the script if the package already exist?


Prometheus Exporter for Jira cause jira to become unresponsive?

HI Andrey,
At some point of time Jira became unresponsive for user requests but remained running.
Thread dumps analysis showed this.
The thread dumps and CPU reading show only one thread actively doing work, and most of the other threads are blocked in (WAITING - parked) state. This is the thread from the top outputs:
"http-nio-8080-exec-136 url:/plugins/servlet/gadgets/ifr username:user_x " #333526 daemon prio=5 os_prio=0 tid=0x00007fd44803a800 nid=0x112dc runnable [0x00007fd1c07ef000]    java.lang.Thread.State: RUNNABLE          at java.net.SocketInputStream.socketRead0(Native Method)          at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)          at java.net.SocketInputStream.read(SocketInputStream.java:171)          at java.net.SocketInputStream.read(SocketInputStream.java:141)          at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)          at sun.security.ssl.InputRecord.read(InputRecord.java:503)          at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)          - locked <0x00007fd7210085f0> (a java.lang.Object)          at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940)          at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)          - locked <0x00007fd72100a6c0> (a sun.security.ssl.AppInputStream)
This thread that is RUNNABLE across the entire capture period is a pool thread (background daemon, not a user service thread):
"pool-11-thread-1" #90 prio=1 os_prio=0 tid=0x00007fd4e02dd800 nid=0x4739 runnable [0x00007fd495a45000]    java.lang.Thread.State: RUNNABLE          at sun.nio.fs.UnixNativeDispatcher.readdir(Native Method)          at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.readNextEntry(UnixDirectoryStream.java:168)          at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.hasNext(UnixDirectoryStream.java:201)          - locked <0x00007fd981e0c538> (a sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator)          at java.nio.file.FileTreeWalker.next(FileTreeWalker.java:348)          at java.nio.file.Files.walkFileTree(Files.java:2706)          at java.nio.file.Files.walkFileTree(Files.java:2742)          at ru.andreymarkelov.atlas.plugins.promjiraexporter.service.ScheduledMetricEvaluatorImpl.calculateAttachmentSize(ScheduledMetricEvaluatorImpl.java:118)          at ru.andreymarkelov.atlas.plugins.promjiraexporter.service.ScheduledMetricEvaluatorImpl.access$100(ScheduledMetricEvaluatorImpl.java:28)          at ru.andreymarkelov.atlas.plugins.promjiraexporter.service.ScheduledMetricEvaluatorImpl$2.run(ScheduledMetricEvaluatorImpl.java:108)          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)          at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
It appears to be monitoring or iterating over a directory structure, related to Jira Exporter plugin. Additionally there is only one RUNNABLE threads which services a user request:
"http-nio-8080-exec-136 url:/plugins/servlet/gadgets/ifr username:user_x " #333526 daemon prio=5 os_prio=0 tid=0x00007fd44803a800 nid=0x112dc runnable [0x00007fd1c07ef000]
The thread dump is basically showing the locks placed by the thread while it's waiting for data:
"http-nio-8080-exec-136 url:/plugins/servlet/gadgets/ifr username:user_x " #333526 daemon prio=5 os_prio=0 tid=0x00007fd44803a800 nid=0x112dc runnable [0x00007fd1c07ef000]    java.lang.Thread.State: RUNNABLE          at java.net.SocketInputStream.socketRead0(Native Method)          at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)          at java.net.SocketInputStream.read(SocketInputStream.java:171)          at java.net.SocketInputStream.read(SocketInputStream.java:141)          at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)          at sun.security.ssl.InputRecord.read(InputRecord.java:503)          at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)          - locked <0x00007fd7210085f0> (a java.lang.Object)          at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940)          at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)          - locked <0x00007fd72100a6c0> (a sun.security.ssl.AppInputStream)
All of the other http threads for user requests are on a WAITING - parked state, which is why the application was unresponsive. It appears that they are waiting for a lock release from one of the threads mentioned above. For example:
"http-nio-8080-exec-46 url:/plugins/servlet/gadgets/ifr username:user_z " #58048 daemon prio=5 os_prio=0 tid=0x00007fd448015800 nid=0x1960e waiting on condition [0x00007fd38119e000]    java.lang.Thread.State: WAITING (parking)          at sun.misc.Unsafe.park(Native Method)          - parking to wait for  <0x00007fd68c4eb2e0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)

GC and heap analysis show no memory related issues, so GC or memory usage is not causing any problem with the application

The only http thread actively running was this:
"http-nio-8080-exec-136 url:/plugins/servlet/gadgets/ifr username:user_x " #333526 daemon prio=5 os_prio=0 tid=0x00007fd44803a800 nid=0x112dc runnable [0x00007fd1c07ef000]    java.lang.Thread.State: RUNNABLE          at java.net.SocketInputStream.socketRead0(Native Method)          at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)          at java.net.SocketInputStream.read(SocketInputStream.java:171)          at java.net.SocketInputStream.read(SocketInputStream.java:141)          at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)          at sun.security.ssl.InputRecord.read(InputRecord.java:503)          at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)          - locked <0x00007fd7210085f0> (a java.lang.Object)          at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940)          at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)          - locked <0x00007fd72100a6c0> (a sun.security.ssl.AppInputStream)
As the other http threads were waiting to acquire a lock, it looks like the exec-136 was itself being unable to retrieve data from cache.
Since the only other active thread for the timeframe was the pool-thread which makes use of Prometheus,
we make the inference that it is some functionality in the plugin which took a long time and was preventing the cache lock from being released
Plugin version: 1.0.20
Jira: Data Center 7.6.1
Are there any known cases similar to this one?
Thank you.

in progress now

@AndreyVMarkelov still in progress?
We had to disable the plugin, because it made Jira a lot slower, some pages took very long to load.
After disabling the plugin, things went back to normal.

Hi, could you try please just set 0 in settings for scheduled job?
вт, 28 Май 2019 г., 1:50 Tobias Wolf<EMAIL_ADDRESS>
@AndreyVMarkelov https://github.com/AndreyVMarkelov still in progress?
We had to disable the plugin, because it made Jira a lot slower, some
pages took very long to load.
After disabling the plugin, things went back to normal.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AndreyVMarkelov/jira-prometheus-exporter/issues/43?email_source=notifications&email_token=AAPXM4F3KWCYQBXW5MENT53PXRQVFA5CNFSM4GQ7AJMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKTETY#issuecomment-496317007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPXM4BUMPKSJ6A372TQMD3PXRQVFANCNFSM4GQ7AJMA
.

@towolf @AntonPakholchuk  It should be fixed now. Could you try please?

@AndreyVMarkelov my colleague just mentioned in passing that we have
reenabled the plug-in about to weeks ago, and it has been working fine. No
slowdowns anymore.
So, thanks!
On Wed, May 29, 2019, 18:42 Andrey Markelov<EMAIL_ADDRESS>wrote:

@towolf https://github.com/towolf @AntonPakholchuk
https://github.com/AntonPakholchuk It should be fixed now. Could you
try please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AndreyVMarkelov/jira-prometheus-exporter/issues/43?email_source=notifications&email_token=AACUI6XCUHOCUYVBDK6W7VTPX2W6NA5CNFSM4GQ7AJMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWP5ZHA#issuecomment-497015964,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACUI6T2JPY26RGDKEZTMZ3PX2W6NANCNFSM4GQ7AJMA
.


add darkwallet project proposal

Grant Application
This application is (select one):

[x] Speculative (use this by default)
[ ] an RFP response

This application is (select one):

[x] Public (fully)
[ ] Public with private finances

Abstract
This is our proposal for an anonymous multi-crypto wallet which anonymizes currency on a side chain system. Over the last year we have created a cryptographic scheme that has zcash tier anonymity (without requiring fixed amounts like other darkpool schemes) but uses far simpler math. We're also developing a mixnetwork which provides superior network level anonymity than Tor. Our plan is to combine this into an anonymizing mixer wallet.

We intend to create a C++ implementation.
We will require 6 months to complete this project.
We intend to have 2 developers full-time and 1 part-time,
Total cost of 100k EUR

Checklist

[x ] The grants document has been read and understood.
[ x] The Google Form will be completed accurately. Note that the Google Form requires the pull request URL.
[ x] Abstract (above) is succinct and complete.
[ x] The application is being included into the correct directory: either 'targeted' or 'speculative'.
[ x] The application includes a project description.
[x ] The application includes all names of team members.
[x ] The application includes a description of the team's experience.
[x ] The application includes all necessary links (e.g. GitHub and LinkedIn)
[x ] The "Development Roadmap" section in the application has a timeline of development ("milestones").
[x ] The "Development Roadmap" section in the application has an estimate of funds required.
[x ] The "Development Roadmap" section gives an indication of the team's long term plans.
[x ] The "Development Roadmap" section includes documentation as a deliverable for at least one milestone.

Just closing some old grant PRs to help bring 2019 activities to a conclusion.
New grant applications are welcome in 2020. Please reach out if you have any questions.

Re-opened by request! Let me know if you have any questions (email is best).


DOCS: Add suitable documentation around Provisioning Architecture

Currently agreed diagram is present in the repo.
Add suitable description to set the context to the diagram.

Will be addressed using https://github.com/veraison/docs/issues/2


Add no_world_writable_dirs appliance

To ensure that no dir in $PATH is world-writable.
It turns out that the current clang 5.0.0 archive is faulty
and its bin is world-writable, causing
https://github.com/travis-ci/travis-ci/issues/8892.
We work around this issue in general by checking each dir in $PATH.
GNU chmod has a handy --changes flag that prints only the changes,
but this flag is not available for BSD chmod (on the Mac), so we
use -vv and filter the output instead.

Tested: https://staging.travis-ci.org/cotsog/travis_ci_staging_regular/builds/675845


Uncaught TypeError: path must be a string

[Enter steps to reproduce below:]

...
...

Atom Version: 0.209.0
System: Mac OS X 10.10.3
Thrown From: tree-view-finder package, v0.2.1
Stack Trace
Uncaught TypeError: path must be a string
At fs.js:205

TypeError: path must be a string
  at TypeError (native)
  at fs.exists (fs.js:207:11)
  at Object.fs.exists (ATOM_SHELL_ASAR.js:286:16)
  at Object.module.exports.TreeViewFinder.openUri (/Users/whall/.atom/packages/tree-view-finder/lib/tree-view-finder.coffee:295:8)
  at Object.<anonymous> (/Users/whall/.atom/packages/tree-view-finder/lib/tree-view-finder.coffee:224:12)
  at Object.xor [as xorhandler] (/Users/whall/.atom/packages/tree-view-finder/lib/doubleTap.js/xorTap.js:46:13)
  at tree-view-file.<anonymous> (/Users/whall/.atom/packages/tree-view-finder/lib/tree-view-finder.coffee:243:10)
  at space-pen-div.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4435:9)
  at space-pen-div.elemData.handle (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/jquery/dist/jquery.js:4121:28)

Commands
     -5:11.1.0 core:confirm (input.hidden-input)
     -5:09.0 core:paste (input.hidden-input)
     -5:04.5.0 core:undo (input.hidden-input)
     -4:59.8.0 core:paste (input.hidden-input)
     -4:14.1.0 core:select-all (input.hidden-input)
     -4:13.6.0 core:cut (input.hidden-input)
  2x -3:49.3.0 core:backspace (input.hidden-input)
  2x -3:41.9.0 core:confirm (input.hidden-input)
     -2:18.7.0 tree-view-finder:toggle (input.hidden-input)
     -2:00.6.0 tree-view:toggle (input.hidden-input)
     -1:48.5.0 tree-view:toggle-side (input.hidden-input)
     -1:43.7.0 tree-view:toggle (input.hidden-input)
     -0:31.3.0 core:cut (input.hidden-input)
     -0:21.5.0 core:paste (input.hidden-input)
     -0:20.4.0 core:save (input.hidden-input)
     -0:09.9.0 core:cut (input.hidden-input)

Config
{
  "core": {
    "disabledPackages": [
      "term",
      "tree-view",
      "react",
      "atom-jade",
      "language-babel"
    ],
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  }
}

Installed Packages
# User
Sublime-Style-Column-Selection, v1.3.0
color-picker, v2.0.4
git-projects, v1.14.1
linter, v0.12.7
linter-jshint, v0.1.6
php-twig, v4.0.0
project-manager, v1.15.10
remote-sync, v3.1.2
tree-view-finder, v0.2.1
tree-view-git-projects, v0.5.0

# Dev
No dev packages

I've updated my environment today. Now my env is very similar to yours. These version numbers are completely same. I guess you got the error on double click some item in the tree view. But I couldn't reproduce the error.
Atom Version: 0.209.0
System: Mac OS X 10.10.3
Thrown From: tree-view-finder package, v0.2.1
Could you tell me how/what did you do to get the error?


Fix purepython builtin type strings

This fixes issue #2046
The underlying issue was that _analyse_name_as_type was not considering either the builtin scope, or other types than extension types. Py_buffer happened to be a builtin type that was a C struct.

Thanks!

BTW, looks perfect for a first PR !

Erm, sorry - I'll rephrase :)

You really write good and clean pull requests. Always happy to get one from you.

Heh, :) you're welcome, and thanks


Dashboard: cannot access local variable 'pie_3' where it is not associated with a value

Steps to Reproduce
Using the Prowler Dashboard the following error is raised
Traceback (most recent call last):
  File "/home/kali/.local/lib/python3.12/site-packages/dashboard/pages/overview.py", line 1260, in filter_data
    pie_3,
UnboundLocalError: cannot access local variable 'pie_3' where it is not associated with a value

Expected behavior
Working without any error.
Actual Result with Screenshots or Logs

How did you install Prowler?
Cloning the repository from github.com (git clone)
Environment Resource
Workstation
OS used
Kali Linux
Prowler version
5.0.0
Pip version
N/A
Context
Issue coming from the Prowler Community Slack https://prowler-workspace.slack.com/archives/C045DAM2NE9/p1733509962571659

Hello @tmonk42 , I’m unable to reproduce your error. Could you let me know if you’re applying a specific filter or something similar? Also, please ensure that the files are being read from the specified path.
Looking forward to your response, thanks!


Add explicit cache-control to all responses

Improves loading performance

re-opened PR as while not perfect it probably still helps a little

This PR is pointless until we address this in ConfiguredAssetsBundle, closing for now


wip: falco: Add SSL support for the falco webserver

What type of PR is this?
/kind bug
/kind feature
/kind chart-release

Any specific area of the project related to this PR?
/area falco-chart

What this PR does / why we need it:

Add falco.webserver.sslEnabled config, enabling SSL support using the certs values from gRPC
Document certs values

Which issue(s) this PR fixes:

Fixes #38
Special notes for your reviewer:
Testing this requires a docker image including the libssl1.0-dev package
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign nestorsalceda
You can assign the PR to them by writing /assign @nestorsalceda in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

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

Welcome @antoinedeschenes! It looks like this is your first PR to falcosecurity/charts 🎉

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

c1d27df falco: improve auditing documentation

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

Hey @antoinedeschenes
Thank you for this awesome PR
Could you add a bit more context about the libssl1.0-dev issue?
I have not found any relevant issues about that.

@leogr This is related to error Could not create embedded webserver: null context when constructing CivetServer. due to libcrypto.so missing in issue https://github.com/falcosecurity/falco/issues/860
I'm running a custom image, but the ln fix might be enough to get it to work with the stock falco image.

@leogr This is related to error Could not create embedded webserver: null context when constructing CivetServer. due to libcrypto.so missing in issue falcosecurity/falco#860
I'm running a custom image, but the ln fix might be enough to get it to work with the stock falco image.

Ok, so I believe we should fix that problem in Falco first :)
/hold
blocked by https://github.com/falcosecurity/falco/issues/860

@antoinedeschenes: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

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

Puttting this back to WIP as Dynamic Auditing is removed from k8s 1.19. SSL support in the chart is still a useful feature.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign nestorsalceda after the PR has been reviewed.
You can assign the PR to them by writing /assign @nestorsalceda in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

b8b6d3e use nodePort for service

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

b8b6d3e use nodePort for service
1187659 fix indents

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

@leogr changed the PR scope, I still add webserver SSL support, but replaced dynamicAuditing with a nodePort. It's currently working on our clusters

@leogr changed the PR scope, I still add webserver SSL support, but replaced dynamicAuditing with a nodePort. It's currently working on our clusters

First of all, I apologize for letting this PR here for such a long time. I'm just waiting to get a consensus regarding this issue.
And thank you again. Your effort is highly appreciated :+1:
I believe some users might have security concerns regarding the NodePort solution. Anyway, it may still be acceptable if not enabled by default.
cc @falcosecurity/charts-maintainers WDYT?

@leogr For the security aspect, client cert validation might be something worth looking at on the webserver side (enabling ssl_verify_peer on civet should work). The webhook config allows to use a client certificate on the kube API server when TLS is setup.
Otherwise one has to setup their node firewall, security group or GlobalNetworkPolicy to limit this to local access only at the moment.

I think I'd like to see the dynamic audit sink configuration not removed. I'm not sure which kubernetes/falco versions a single chart is expected to support but removing it may impact a user. It'll stop working in later kubernetes versions anyways so we can just set this for removal in 6 months or a year or something.
I like re-using the certs from grpc.
I'm not confident about the choice of nodeport - is that flexible enough ... some people won't want it or will want to use ingress.

@nibalizer Dynamic Auditing never worked in the chart, as SSL could not be enabled, and was required to work. https://github.com/falcosecurity/charts/issues/38 this PR originally fixed that problem (see https://github.com/falcosecurity/charts/compare/master...antoinedeschenes:dynamic-audit-ssl?expand=1)
Should we then:

fix dynamicAuditing for >=1.13 to <=1.18 (supported versions)
make NodePort "opt-in"
add ingress support

@nibalizer @antoinedeschenes
I can confirm the dynamicAuditing never worked (unless the user patched the auditsink with a fixed URL).
So I think removing it is still an option. We can also suggest manually deploy the auditsink as explained here. The example should work with a helm deployed Falco chart too.

@antoinedeschenes: PR needs rebase.

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

Changes:

disabled the NodePort by default
Removed SSL documentation and linked to gRPC documentation in both cases, as we're sharing the certificates and require a CA (not working for a self-signed cert)

If we know it never worked I'm all for removing it :)

Alright. I believe @antoinedeschenes did everything possible to make this PR perfect, so a big thanks to him! :clap:
I will give it a try ASAP :+1:

I wasn't able to get this working:
Mon Nov 30 23:14:53 2020: Starting internal webserver, listening on port 8765 (SSL)
Mon Nov 30 23:14:53 2020: Runtime error: Could not create embedded webserver: null context when constructing CivetServer. Possible problem binding to port.. Exiting.

That's with self signed certs and this:
helm install x --set-file certs.server.key=ssl/server.key --set-file certs.server.crt=ssl/server.crt --set-file certs.ca.crt=ssl/ca.crt   --set auditLog.enabled=true  --set falco.webserver.sslEnabled=true  .

I think I saw something about self-signed certs not working... is that related? Thoughts?

I wasn't able to get this working:
Mon Nov 30 23:14:53 2020: Starting internal webserver, listening on port 8765 (SSL)
Mon Nov 30 23:14:53 2020: Runtime error: Could not create embedded webserver: null context when constructing CivetServer. Possible problem binding to port.. Exiting.

That's with self signed certs and this:
helm install x --set-file certs.server.key=ssl/server.key --set-file certs.server.crt=ssl/server.crt --set-file certs.ca.crt=ssl/ca.crt   --set auditLog.enabled=true  --set falco.webserver.sslEnabled=true  .

I think I saw something about self-signed certs not working... is that related? Thoughts?

The issue should be falcosecurity/falco#860
However, at this point I believe it would be better to split this PR in two: one for the SSL and another one for nodePort solution.
PS
I apologise for making the review process of this PR so long and a bit cumbersome, but it's better to wait until we are 100% convinced, IMHO. I hope you all understand my concerns.

@nibalizer Yes, civet webserver has dynamic dependencies for libssl1.0 which are missing in the docker image.
You can test with my forked image including PR https://github.com/falcosecurity/falco/pull/1344 which has the required dependencies: ghcr.io/kronostechnologies/falco:0.26.2-stock.1

Wow!
I second @leogr's apologies and thanks for sticking with us through this contribution

@nibalizer @leogr Just extracted the NodePort in #159 and AuditSink removal in #160

@nibalizer @leogr Just extracted the NodePort in #159 and AuditSink removal in #160

Hey @antoinedeschenes
I have approved https://github.com/falcosecurity/charts/pull/159 right now.
Could you remove the nodePort implementation from here and then rebase, please?
Thank you in advance

@leogr done for this one and #160

This looks good except for the chart version bump (I'm not sure we really should have that check enabled, but we do right now) and a changelog entry.

Quick note: I'm still assuming AuditSink is removed here, while it could be fixed by adding the caBundle field

Quick note: I'm still assuming AuditSink is removed here, while it could be fixed by adding the caBundle field

Thank you for the note, I didn't consider that. Since I believe it's better to wait before removing the AuditSink (see https://github.com/falcosecurity/charts/pull/160#pullrequestreview-550014878), it would be better if the AuditSink works too.
However, it should already work with clientConfig.service when using SSL :point_down:
https://github.com/falcosecurity/charts/blob/master/falco/templates/auditsink.yaml#L21-L26
shouldn't it?
Let me know, thanks!

Ok just reread the documentation https://v1-18.docs.kubernetes.io/docs/tasks/debug-application-cluster/audit/ it uses CA validation, so would only work when using a trusted CA without the caBundle field set. (TLS remains mandatory) I can add this back to the PR

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign nestorsalceda after the PR has been reviewed.
You can assign the PR to them by writing /assign @nestorsalceda in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

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

Ok, just added the AuditSink SSL config back, the documentation doesn't seem very clear about the service config requiring SSL or not, but they do require the url scheme to be https, and the default service port is 443.

LGTM label has been added.  Git tree hash: fae8c18b756accbc3821b63594d17fb789413092

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

Needs approval from an approver in each of these files:

falco/OWNERS [nibalizer]

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

@leogr do you know why this has a hold?

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

Needs approval from an approver in each of these files:

falco/OWNERS [leogr,nibalizer]

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

@leogr do you know why this has a hold?

Originally because of falcosecurity/falco#860
However, although that's not fixed yet, I believe this PR can be merged anyway, so
/hold cancel


Add a call to ColumnSelector.names in Rename.output_column_names

This addresses an issue with inference where ColumnSelector doesn't act like a collection of string names in that context. Note that the existing code is exercised by the test suite and works fine there, but doesn't seem to work in Triton. This just does an explicit conversion to a list of strings instead of relying on ColumnSelector's iterable nature to do the conversion implicitly.

Fixes #1052


Windows 10 need --vs2015 for building

In the readme it is asking to use this command line for windows;
$ npm install --global windows-build-tools // Windows 10
$ npm install --global windows-build-tools --vs2015 // Windows 7

but I just did a build of Ferdi with this commit 4cb24eb and I was getting error when using this line;
npm run rebuild
So I used the command line for windows 7 (in my windows 10 machine) and after re-using rebuild and build.. everything worked.
So my suggestion is to do
this
$ npm install --global windows-build-tools // Windows 10
$ npm install --global windows-build-tools --vs2015 // Windows 7

to this
$ npm install --global windows-build-tools --vs2015

Addressed via https://github.com/getferdi/ferdi/commit/33a1daa4dc0a01a8d2fd68300ddd63503aab8d41. Thank you for testing on Windows 10 and reporting.

For more information in the error log it was saying that the build was needing Visual Studio v140 (so VS2015) and not 2017 for windows 10


There's no dist/ path in the npm install

It looks like from the docs there ought to be.

(Consider Rollup + Buble to compile/es5-ify)


List of Secrets isn't correctly counted

on the page next steps, you've got the code for:
  % if secrets_need == 'org' or secrets_need == 'repo':
  3 [GitHub secrets](https://docs.github.com/en/actions/reference/encrypted-secrets) were set to store {encrypted docassemble login information} safely:

  ${ secrets_list }
  % endif

for me this rendered as:
3 GitHub secrets were set to store encrypted docassemble login information safely:
PLAYGROUND_EMAIL
PLAYGROUND_PASSWORD
PLAYGROUND_ID
SERVER_URL

Closed by the above merged PR


Can I disable audio when alarm triggered?

As title, in my case I don't want to play audio when the alarm triggered.
Can I do it?
Thanks.
p/s: Sorry for my bad English
@gdelataillade

Hi @phamquoctrongnta
No problem I guess you can just pass a silent audio as assetAudioPath. You can download this one here:
https://github.com/gdelataillade/alarm/blob/main/assets/blank.mp3
Another option is to pass any other audio (it's better if it's short so it's faster to load) and set the volume parameter to 0.0.
Let me know if it works for you.


what is this colorful tag patch?

where i can find colorful tag patch?

https://github.com/fitrh check his dwm repo and an issue in it


Group by when my document has array property?

Hello guys,
I'm glad group by is finally available to use but I have a 'small' problem with it. My document looks like this for instance:
{
"deviceId": "1",
"timestamp": "01-01-2021",
"properties: [
   {"Name": "prop1", "Value": "val1"},
   {"Name": "prop2", "Value": "val2"}
]
}

So what I'm trying to do is to get the latest document for every device I have. This work just fine:
SELECT *
FROM (
SELECT MAX(f.timestamp) as measuredAt, f.deviceId
FROM f
GROUP BY f.deviceId
) AS latestMeasurement

returns for instance:
    {
        "measuredAt": "2020-05-08T06:23:13.3914671Z",
        "deviceId": "1"
    },
    {
        "measuredAt": "2020-05-12T14:21:34.1031887Z",
        "deviceId": "2"
    },

But I need properties object which is an array so I get the values from a particular device. So I need something like this:
SELECT *
FROM (
SELECT MAX(f.timestamp) as measuredAt, f.deviceId, f.properties
FROM f
GROUP BY f.deviceId
) AS latestMeasurement

but it throws:
"SELECT * is not allowed with GROUP BY."
So the question pretty much is if there's a way to make it work? Seems like any array object use "select" underneath or "select value" which is not an option with group by?

For GROUP BY, you can only project properties in the GROUP BY clause or aggregates. There are a few alternatives for this scenario:

Once you've obtained the DeviceId, query for the properties in a separate request
Run individual queries for each DeviceId (basically grab each DeviceId individually, looking for the max timestamp. Something like:

SELECT * FROM c
FROM c
WHERE c.deviceId = "val"
ORDER BY c._timestamp DESC

Build a real-time materialized view that persists the latest DeviceId document in a separate collection

For #3, here's a video on that materialized views in Cosmos DB - https://www.youtube.com/watch?v=faXkCccz5eA&t=1733s

Looks like the question has gotten answered. Please reopen the ticket if there are further questions.


[AST] NFC: Simplify BoundGenericType::Profile

BoundGenericType::Profile() is the only Profile method that calculates the recursive type properties as a side effect. This change makes the method like all of the others.

@swift-ci please smoke test


Coupling JPA Entity model schema with Jackson

Query service JPA entities model uses @JsonIgnore annotation on association attributes to restrict serialization of the associated data in REST Query Api. However, this couples JPA entity model with Jackson and limits the use of entity model objects serialization into Json for other use cases.
It would be best practice to avoid such hard coupling by removing Jackson annotations from JPA entity models and use Jackson Datatype Hibernate extension module in REST Query Api service to serialize LAZY fetch attributes only if we initialize them with fetch query or fetch entity graph in database query :
https://github.com/FasterXML/jackson-datatype-hibernate

Totally.. we started using Mixins heavily on the API refactoring.. I think that we just need to keep doing that in the controller and entity layers.

Awesome! It is good have clear separation of concerns and keep entity model clean.


OpenJ9: Set CUDA_HOME to a generic HOME folder

Related ibmruntimes/temurin-build#94
ibmruntimes/ci-jenkins-pipeline#182
Depends https://github.com/adoptium/ci-jenkins-pipelines/pull/982

Mac OS X 13 fail is unrelated


ATEM Constellation 8K causes Companion to crash

Every time the IP address is added for the ATEM Constellation 8K the entire companion app crashes. The studio 4K switcher connects and works. It is just the Constellation that won't work.
I have tried to select the model, auto detect, as well as every constellation model available on the drop down menu.
There is no code given when companion crashes.
I tried using Companion 2.2.3, as well as the Beta version 2.3.0
The ATEM Constellation is on version 8.6.2, however I tried version 8.6.0 as well

We have figured out that whenever the Atem Control software is open it causes companion to crash, so when the Atem Control software is closed on every computer then companion works with it and does not crash

strange, I have never encountered this issue on any model before. I expect that a majority of users will have both companion and the software control open simultaneously..
It feels like something else is going on, but I have no idea what

I cannot reproduce this with other models, and I don't see that there would be anything unique about the 8k that could cause this.
As there have been no other reports of this, perhaps it was something unique about your environment, or was fixed as part of another change in a newer version


The API Gateway guide incorrect install kuma CRs

What happened?
In the API Gateway Guide
Tells the user to install demo with this command
kumactl install demo | kubectl apply -f -

The problem is that this command install extra resources like MeshGateway, MeshGatewayInstance, and MeshHTTPRoute.
The main target of the guide is for the user to create the CRs using API Gateway CRDs not Kuma.

Yeah, the command should probably include --without-gateway


[CODEGEN] Fix an inliner to call a function with a phi-node

Problem
If a function that has a phi-node (e.g., for loop) is called, compilation fails because of IndexError: map::at.  This can prevent the user from modularization of Triton kernels (e.g., for fusion, we write two functions and call them in another function).
@triton.jit
def matmul_and_something(...)
   matmul(...) # matmul code (e.g., one in a tutorial) contains a loop and thus a phi-node in Triton-IR,
               # so this fails.
   something(...)

Solution
Modify inliner.cc by fixing the following two:

Previously, the inliner assumes that, before an instruction, all of its operands appear (and thus are created). It is true in terms of SSA except for a phi node. Let's replace operands of the new instructions once we generate all the new instructions.
replace_uses_of_with() does not replace incoming basic blocks of phi-nodes. Let's update these incoming basic blocks.

This PR also adds a test to check the behavior. The test fails because of IndexError: map::at without this PR.

I believe this kind of issue should be naturally fixed by Triton-MLIR, but please let me create a PR for the master Triton.

Thank you for fixing that!


make deploy fails for vCenter 6

I followed this documentation https://github.com/kubernetes/kubernetes-anywhere/blob/master/phase1/vsphere/README.md and tried several times with administrator and a different account with admin privilege still same result. Any suggestions is appreciated.
[container]:/opt/kubernetes-anywhere> make deploy
util/config_to_json /opt/kubernetes-anywhere/.config > /opt/kubernetes-anywhere/.config.json
make do WHAT=deploy-cluster
make[1]: Entering directory '/opt/kubernetes-anywhere'
( cd "phase1/vsphere"; ./do deploy-cluster )
STATIC ERROR: vSphere.jsonnet:24:8: Expected a comma before next field.
Makefile:70: recipe for target 'do' failed
make[1]: *** [do] Error 1
make[1]: Leaving directory '/opt/kubernetes-anywhere'
Makefile:48: recipe for target 'deploy-cluster' failed
make: *** [deploy-cluster] Error 2

Here is how the .config file look like

Automatically generated file; DO NOT EDIT.
Kubernetes Minimal Turnup Configuration

Phase 1: Cluster Resource Provisioning

.phase1.num_nodes=4
.phase1.cluster_name="kubernetes"
.phase1.ssh_user=""
.phase1.cloud_provider="vsphere"

vSphere configuration

.phase1.vSphere.url="<IP_ADDRESS>"
.phase1.vSphere.port=443
<EMAIL_ADDRESS>.phase1.vSphere.password="k8s!"
.phase1.vSphere.insecure=y
.phase1.vSphere.datacenter="T8888"
.phase1.vSphere.datastore="T8888_VRPA"
.phase1.vSphere.placement="cluster"
.phase1.vSphere.cluster="T8888_LABS"
.phase1.vSphere.useresourcepool="no"
.phase1.vSphere.vmfolderpath="kubernetes"
.phase1.vSphere.vcpu=2
.phase1.vSphere.memory=2048
.phase1.vSphere.network="VM Network"
.phase1.vSphere.template="KubernetesAnywhereTemplatePhotonOS"
.phase1.vSphere.flannel_net="<IP_ADDRESS>/16"

Phase 2: Node Bootstrapping

.phase2.kubernetes_version="v1.6.5"
.phase2.provider="ignition"
.phase2.installer_container="docker.io/cnastorage/k8s-ignition:v2"
.phase2.docker_registry="gcr.io/google-containers"

Phase 3: Deploying Addons

.phase3.run_addons=y
.phase3.kube_proxy=y
.phase3.dashboard=y
.phase3.heapster=y
.phase3.kube_dns=y
.phase3.weave_net is not set

Made lot of progress. Can someone tell me where I can get the steps if I want to assign a static IPs instead of DHCP and also is there document (with steps with different vCenter config) on how to get this going?
I am open to help writing/creating this document which would help the community.
Anyways here is what I am on now - please let me know if you have any suggestion.
null_resource.kubernetes-master (remote-exec): Connected!
null_resource.kubernetes-node2 (remote-exec): Connected!
null_resource.kubernetes-node5 (remote-exec): Connected!
null_resource.kubernetes-node4 (remote-exec): Connected!
null_resource.kubernetes-node3 (remote-exec): Connected!
null_resource.kubernetes-master (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/etcd.service to /usr/lib/systemd/system/etcd.service.
null_resource.kubernetes-node4 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/flannelc.service to /usr/lib/systemd/system/flannelc.service.
null_resource.kubernetes-node2 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/flannelc.service to /usr/lib/systemd/system/flannelc.service.
null_resource.kubernetes-node5 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/flannelc.service to /usr/lib/systemd/system/flannelc.service.
null_resource.kubernetes-node3 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/flannelc.service to /usr/lib/systemd/system/flannelc.service.
null_resource.kubernetes-master (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/flanneld.service to /usr/lib/systemd/system/flanneld.service.
null_resource.kubernetes-node2 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
null_resource.kubernetes-master (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
null_resource.kubernetes-node5 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
null_resource.kubernetes-node4 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
null_resource.kubernetes-node3 (remote-exec): Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
null_resource.kubernetes-node2 (remote-exec): Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority
null_resource.kubernetes-node2 (remote-exec): Failed to docker pull hyperkube
null_resource.kubernetes-node2: Creation complete (ID:<PHONE_NUMBER>453203441)
null_resource.kubernetes-master (remote-exec): Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority
null_resource.kubernetes-master (remote-exec): Failed to docker pull hyperkube
null_resource.kubernetes-node4: Creation complete (ID:<PHONE_NUMBER>91400029)
null_resource.kubernetes-node3 (remote-exec): Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority
null_resource.kubernetes-node3 (remote-exec): Failed to docker pull hyperkube
null_resource.kubernetes-node5: Creation complete (ID:<PHONE_NUMBER>483203077)
null_resource.kubernetes-node3: Creation complete (ID:<PHONE_NUMBER>395648892)
Error applying plan:
1 error(s) occurred:

null_resource.kubernetes-master: 1 error(s) occurred:

Script exited with non-zero exit status: 1

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
Makefile:70: recipe for target 'do' failed
make[1]: *** [do] Error 1
make[1]: Leaving directory '/opt/kubernetes-anywhere'
Makefile:48: recipe for target 'deploy-cluster' failed
make: *** [deploy-cluster] Error 2
[container]:/opt/kubernetes-anywhere>

After putting the following on proxy bypass
gcr.io
cloudfront.net
docker.io
and using following image for docker VM
docker pull cnastorage/kubernetes-anywhere:vmc
docker run -it --rm --env="PS1=[container]:\w> " --net=host cnastorage/kubernetes-anywhere:vmc /bin/bash
I got the cluster working. Closing this issue.


Use display names of devices as qiskit backends

Summary

The new display names for the devices are used as qiskit backends. The old names still work.

            'ibmq_5_yorktown': 'ibmqx2',
            'ibmq_5_tenerife': 'ibmqx4',
            'ibmq_16_rueschlikon': 'ibmqx5',
            'ibmq_20_austin': 'QS1_1'

Once the names are updated in the API, we will update qiskit to emit deprecation warnings.

Add some tests to exercise backend name resolution.

Order list of strings returned from wrapper.available_backends() so they display more nicely.

Details and comments

Thanks for polishing the PR @delapuente. Looks good to merge to me.


Question: Should spaces be created in the first stage of the create space dialog?

I'm submitting a ...
[ ] bug report
[ ] feature request
[x] question about the decisions made in the repository

Do you want to request a feature or report a bug?

Requesting clarity on whether spaces should be created in the first stage of the spaces wizard, or whether the dialog needs to be improved to convey that a new space will be created in the first stage.

What is the current behavior?

The first dialog in the wizard has a Next button, which does not imply that the space will be immediately created.

The second dialog however displays that the space has been created. This is confusing to the user, given the presence of a Back button in the dialog.

What is the motivation / use case for changing the behavior?

If spaces are to be created in the first dialog of the wizard, then the dialog should not allow for multiple spaces to be created by the user accidentally.

This is just because it was in the mockup and will probably change as the wizard evolves with the obsidian api over the next several weeks. The space is created on the finish button

@aslakknutsen do know you the answer to the above question?

As @mitchharpur said, right now we just copied the mockup from @qodfathr but the mockup contains a logical flaw - the screen allows you to go back, but it also says that part of the transaction is complete (creating the space). @qodfathr can you tell us how you want the mockup altered to resolve?

@Essjaysee is working on this

Personally, I wouldn't see it is one large popup wizard. In my mind the 'get started' makes more sense as the default 'dashboard' landing page for an empty space. 'get started' is also something you would want to do over and over again inside the same space which means you need to know where to get access to that part of the wizard anyway.

This specific question is now addressed, there is a create space button.


Parts of the ambient light or video has sometimes flickering black triangles or triangles that contain the previous video frame

Ambilight randomly flickers black when watching a video. Setting chrome's #use-angle flag to OpenGL seems to fix it but drastically lowers the ambilight fps.
It could also be linked to Windows HDR, as it's way more prevalent with HDR turned on
Reproduced on both Windows 10 and 11.
Chrome 95.0.4638.54
I uploaded a video of the issue here, you can see the flickering at 0:17 and 0:27
(the colors in the video are off because i recorded the display with HDR turned on)

Same in Brave
HW:
2060
3800x

Todo:

[ ] Check if this bug still happens after the workaround for bug #150 is released

@red9350 @Nirgranth This is now fixed in version 2.37.2 (Already released to Opera but in review for Edge and Chrome)


x64dbg: Should Scoop use Sourceforge instead of Github?

Bug Report
Package Name: x64dbg
Current Behaviour
Scoop currently tries to fetch this package from Github but all releases except for the latest are deleted. When releases are deleted scoop receives a 404 error until the repo gets updated.
Possible Solution
I don't know if Scoop has anything against using Sourceforge. There are other manifests that use Sourceforge. I could convert this one using one of the others as a template.
Related issues

#7198
#7206
#7275

Github didn't like it in the past if you uploaded gigabytes of releases.
There are archives with all releases as long as I can maintain at:

https://sourceforge.net/projects/x64dbg/files/snapshots/
https://osdn.net/projects/x64dbg/storage/snapshots/

Originally posted by @mrexodia in https://github.com/x64dbg/x64dbg/issues/2207#issuecomment-524089905

Hey @infomaniac50, thanks for digging in! We have nothing against SourceForge - it will be great if you could switch to it in your PR (earlier discussion at #7207)

Sourceforge should work now. I don't think I can run the /verify command.


[BUG] Binary mode is shared among all compilers

Describe the bug
If a compiler pane has binary mode activated, the rest also show the codelens contents. (But not the custom line count). Moreover, if more than one has it activated, the contents will show up in all compilers
To Reproduce
Have one compiler output binary mode, and another without it. Enabling it on both also makes it be displayed on both
Expected behavior
Each editor should have its own separate binary display
Link
Found it while checking #1220 status at https://godbolt.org/z/GKv7nb
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Seems the codelens feature is registered to the language (so asm in this case).
So aside from somehow switching it on and off per monaco editor, we also need to make sure the codelens code is independent from the compiler pane that registered the codelens.


Fix supported SOP Classes for issuing C-MOVE requests

According to the movescu man page, we should add FINDStudyRootQueryRetrieveInformationModel SOP Class to conform with the RSNA'93 demonstration:
       The movescu application will propose presentation contexts for one of the abovementioned supported SOP Classes depending on
       the command line options (-P, -S, or -O). It will also propose the corresponding SOP Class from the following list, although
       it is not really used (this is a relict of the RSNA'93 demonstration):

       FINDPatientRootQueryRetrieveInformationModel         1.2.840.10<IP_ADDRESS>.<IP_ADDRESS>
       FINDStudyRootQueryRetrieveInformationModel           1.2.840.10<IP_ADDRESS>.<IP_ADDRESS>
       FINDPatientStudyOnlyQueryRetrieveInformationModel    1.2.840.10<IP_ADDRESS>.<IP_ADDRESS>

sample log from movescu
D: Their Max PDU Receive Size:  131072
D: Presentation Contexts:
D:   Context ID:        1 (Accepted)
D:     Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =LittleEndianImplicit
D:   Context ID:        3 (Accepted)
D:     Abstract Syntax: =MOVEStudyRootQueryRetrieveInformationModel
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation:  none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response:  none

cc @favadi


Fixes #5 Only bind to QUALITY_SELECTED once

As things turn out, the middleware constructor is called every time setSource is called. This was causing a new listener to get bound to QUALITY_SELECTED on each change by the quality selector. :( This change makes it so the listener is only bound on the initial creation of the player.
Fixes #5

Should we include a minor version bump to 1.0.1?


How to run agentx

Hi,
I was trying to setup net-snmp for agentx inside the container for my application. however I can't start the snmpd daemon.
The host on which my container is running has an IP <IP_ADDRESS>. Now my container's IP will  change everytime I bounce them so I can't configure the internal IP and also my snmp traps from my NMS need to communicate to the master agent on the host IP. So I 'm not able to figure out how do I map the agentx IP and port with the host
This is what I 'm getting in snmpd.logs.
Error: Couldn't open a master agentx socket to listen on (tcp:<IP_ADDRESS>:10705):
Looking forward to some help from you.
Thanks.

HI... Can you include the commands that you are using to deploy those images?
Im not sure if this is what you mean but you can specify --link when running docker image to link directly to it without a need or getting it's ip.
Please see documentation here

Hi @pozgo, thanks for volunteering to help. I found the solution to the issue.
Cheers!


Parser missing IRQs (CMSDK_CM3.svd)

While parsing ARM CMSDK_CM3.svd extracted from Keil.V2M-MPS2_CMx_BSP.1.7.0.pack it appears the second IRQs for all peripherals are missing. Everything looks fine when I examine the SVD file manually. This device is of special importance as its available in QEMU. Any assistance would be appreciated as my python skills are poor.

I pulled down this file.  I believe the SVD provided by ARM does follow the spec but does it in a way that is more than a little obnoxious and different than how all the vendors appear to be doing things (at least as far as I have encountered)
CMSDK_CM3.svd:
        <interrupt>
            <name>UART0_RX</name>
            <description>UART 0 Receive Interrupt</description>
            <value>0</value>
            <name>UART0_TX</name>
            <description>UART 0 Transmit Interrupt</description>
            <value>1</value>
        </interrupt>

How everyone else does it:
        <interrupt>
            <name>UART0_RX</name>
            <description>UART 0 Receive Interrupt</description>
            <value>0</value>
        </interrupt>
        <interrrupt>
            <name>UART0_TX</name>
            <description>UART 0 Transmit Interrupt</description>
            <value>1</value>
        </interrupt>

However, the schema does have the type for "interrupt" defined as follows:
  <!-- interruptType specifies how to describe an interrupt associated with a peripheral -->
  <xs:complexType name="interruptType">
    <xs:sequence>
      <xs:element name="name" type="stringType"/>
      <xs:element name="description" type="xs:string" minOccurs="0"/>
      <xs:element name="value" type="xs:integer"/>
    </xs:sequence>
  </xs:complexType>

Which, if I understand xs:sequence correctly requires a specific order and allow for elements within a given interrupt section to occur more than once.  I'll have to look at how to change code to accommodate and figure out where else the spec decided to allow this asinine form of expression.


Improve dashboard

After receiving some harsh reviews and giving people sore eyes, I decided to revamp the look and feel of the dashboard.
How it looks now:

Sample how it looks with many cards:

@sergeyevstifeev I am counting on your approval

@klippx c'mon, the reviews weren't that harsh 😄  Looks good! :shipit:


Datahub Newsletter and Signup

User Story

As a user, i need a subscribe form, so i can get monthly information about datahub
As a user, i need monthly subscription, so i can stay updated about latest news/updates from datahub
As an admin, i need users to subscribe for newsletter, so i can keep them engaged and connected to platform

Acceptance Criteria

[ ] Have a fully functional subscribe input and button on datahub website
[ ] Users are able to subscribe to monthly newsletter from homepage and blog page
[ ] Monthly newsletter has a good interface and provides various sections that users can read
[ ] Monthly newsletter must a template that the campaign manager can edit each month to generate new content and send to subscribed users

Tasks

[ ] Design a new template
[ ] Create various placeholders in the template and load static content in it
[ ] Create a subscribe form on datahub homepage
[ ] Create a subscribe form on datahub blogs page
[ ] Make sure the entries from subscribe form goes to monthly newsletter list

@tanvirchahal can you tick items as done and close this issue if fixed?


Support resource overrides

We also need these supports in our environment.
Sorry this does not include testing updates 🙇

Thank you. Released as v0.9.0.

Thank you!!


[Bug] Repeatable field set 'showAsterisk' attribute as false

Bug report
In blade of the repeatable field there is a line that sets 'showAsterisk' as false in . This prevent the user cant show an asterisk in the repeatable field
https://github.com/Laravel-Backpack/CRUD/blob/53bc6028f445f9b2ecfb8893283f6b6087539353/src/resources/views/crud/fields/repeatable.blade.php#L48
So then in a repeatable field i want to do:

[
'label'     => FeeLine,
'type'      => 'select2_from_ajax',
'name'      => 'fee_line_id',
'attribute' => 'name',
'showAsterisk' => true,
],

The asterisk is not shown.
I dont know why is taht line but if its removed, the asterisk is shown

Hello @aberaldo thanks for the report.
I was trying to figure out why would we specifically setup the showAsterisk as false in repeatable and find out that it might be to solve an issue when the parent (the repeatable field itself) is required.
From my tests I find out that it does not solve the issue and the issue still persists, so if the parent repeatable is required, all the fields inside the repeatable field show the red asterisk.

Even setting up showAsterisk => false would not make the asterisks go away from the repeatable fields.
I found out that is due to a CSS rule not beeing correctly applied.
I've submitted #3779 to address this issue.
If you have time to give it a try, let us know in the comments of the PR if it fixed your problem :)
Thanks again,
Pedro


Fix small timeouts causing flakes

ex: https://hush-house.pivotal.io/teams/tanzu-user-auth/pipelines/pinniped-pull-requests/jobs/integration-test-gke-1.18/builds/527#L6114f1f2:1160
https://kubernetes.slack.com/archives/C01BW364RJA/p1629502705155100?thread_ts=1629499452.153400&cid=C01BW364RJA

Not seeing these flakes anymore.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
Somehow the installed version shows 8.109 and the available <IP_ADDRESS>.
Steps to reproduce
winget install --uninstall-previous Microsoft.Skype
Actual behavior
Version shows 8.109
Expected behavior
Version should show <IP_ADDRESS>
Environment
Windows Package Manager v1.6.3133                                                                                Copyright (c) Microsoft Corporation. All rights reserved.                                                                                Windows: Windows.Desktop v10.0.22631.2715                                                                               System Architecture: X64                                                                                Package: Microsoft.DesktopAppInstaller v1.21.3133.0                                                                                Winget Directories                                                                                ----------------------------------------------------------------------------------------------------------------------- Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag… User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett… Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links                                                Portable Links Directory (Machine) C:\Program Files\WinGet\Links                                                        Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages                                             Portable Package Root              C:\Program Files\WinGet\Packages                                                     Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages                                               Installer Downloads                %USERPROFILE%\Downloads                                                                                Links                                                                                ---------------------------------------------------------------------------                                             Privacy Statement   https://aka.ms/winget-privacy                                                                       License Agreement   https://aka.ms/winget-license                                                                       Third Party Notices https://aka.ms/winget-3rdPartyNotice                                                                Homepage            https://aka.ms/winget                                                                               Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale                                                                                Admin Setting                             State                                                                         --------------------------------------------------                                                                      LocalManifestFiles                        Disabled                                                                      BypassCertificatePinningForMicrosoftStore Disabled                                                                      InstallerHashOverride                     Disabled                                                                      LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs
No response

This might be due to wingetbot sometimes adding extraneous version data.

It's because Skype doesn't (anymore?) add the version after 8.109.* to the ARP table.

Close with reason: Resolved by PR #128781;


Broken links on /doc/tutorials/introduction-to-cilk-programming/

Issues
Many of the links to the glossary from /doc/tutorials/introduction-to-cilk-programming/ do not work and just bring you to the top of the glossary page
Links that do not work

https://www.opencilk.org/doc/reference/glossary/#parallel-algorithms
https://www.opencilk.org/doc/reference/glossary/#task-parallel-platforms-programming-and-algorithms
https://www.opencilk.org/doc/reference/glossary/#multicores
https://www.opencilk.org/doc/reference/glossary/#logical-parallelism
https://www.opencilk.org/doc/reference/glossary/#fork-join-parallelism
https://www.opencilk.org/doc/reference/glossary/#spawning
https://www.opencilk.org/doc/reference/glossary/#parallel-loops
https://www.opencilk.org/doc/reference/glossary/#scalability
https://www.opencilk.org/doc/reference/glossary/#cilkscale
https://www.opencilk.org/doc/reference/glossary/#spawning
https://www.opencilk.org/doc/reference/glossary/#syncing
https://www.opencilk.org/doc/reference/glossary/#nested-parallelism
https://www.opencilk.org/doc/reference/glossary/#child
https://www.opencilk.org/doc/reference/glossary/#parent
https://www.opencilk.org/doc/reference/glossary/#continuation

Thanks @wheatman. I am back from a week off and will get these references to align properly with the glossary, using PR https://github.com/OpenCilk/www.opencilk.org/pull/218 to make the corrections. There is a deploy preview of the website that you are welcome to look at. (Please let me know if you have questions about that.)
FWIW, because we anticipate a back-and-forth between article-writing and glossary-updating, we built an automatic glossary-checker in the website build script, which flags dangling references, just as you did manually.
I put the complete list into PR https://github.com/OpenCilk/www.opencilk.org/pull/218.


Fix: TopShot Locking use nft.id for lock key

There is a bug in cadence where UUID is not unique: https://axiomzen.slack.com/archives/CG0B7CJAJ/p1657750983733739
This changes the contract to use id
Also adds admin endpoint to unlock all moments since we need to cleanup testnet and mainnet.

Are we sure this is actually a bug yet? From the thread in slack, it looks to me like it was just an issue with resources that were created in summer 2020. We might not want to make this change until that is confirmed

Are we sure this is actually a bug yet? From the thread in slack, it looks to me like it was just an issue with resources that were created in summer 2020. We might not want to make this change until that is confirmed

Yep, we caught 2 moments that collided during QA. A moment that was never locked was unable to be listed for sale with error, "moment locked".
Running the following query in production returns 90,000 moments that were minted before this bug was fixed:
select count(*) from moments where created_at < '2020-07-01 00:32:51.754798'
Realistically the contract should have used nft.id as soon as we decided to scope it to TopShot.NFTs.
The contract is already deployed to testnet and mainnet because the launch is tomorrow morning..


[CLI] Process saving to NFS hangs, possibly related to wandb client

Description
Long-running jobs regularly hang without an identifiable cause. The jobs do not crash or complete; they become stuck, waiting on I/O (process state S/Sl). strace suggests wandb might be involved, maybe something specific to wandb + NFS.
Wandb features
Currently using wandb.init, wandb.log, wandb.watch.
How to reproduce
Very difficult to reproduce; cause unknown. The problem has occurred in 6 jobs run on a slurm cluster in the past 24 hours. See the system logs from wandb, which show a large network activity spike a bit before GPU utilization went to zero (i.e. the process hung). Not sure if this is related. Note these figures are zoomed in; the process stayed frozen, without crashing, for another 8 hours (still hanging).

Output of running strace -p on the hung process is also attached.
Potentially relevant excerpt:
[pid 1966949] futex(0x7fe6d80016b0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff <unfinished ...>
[pid 1966782] write(14, "\0\0\0y\200\3cwandb.proto.wandb_interna"..., 125) = 125
[pid 1966782] futex(0x7fe6e0000f50, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff <unfinished ...>
[pid 1966781] <... poll resumed> ) = 1 ([{fd=15, revents=POLLIN}])
[pid 1966781] read(15, "\0\0\0m", 4) = 4
[pid 1966781] read(15, "\200\3cwandb.proto.wandb_internal_pb"..., 109) = 109
[pid 1966781] futex(0x7fe6d80016b0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 1966949] <... futex resumed> ) = 0
[pid 1966781] <... futex resumed> ) = 1
[pid 1966949] futex(0x558e9becf004, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 353833, {1621533262, 492110000}, ffffffff) = -1 EAGAIN (Resource temporarily unavailable)
[pid 1966781] futex(0x558e9becf004, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x558e9becf000, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 1966949] futex(0x558e9becf000, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 1966781] <... futex resumed> ) = 0
[pid 1966949] <... futex resumed> ) = -1 EAGAIN (Resource temporarily unavailable)

Environment

OS: Ubuntu 16.04
Environment: slurm cluster with NFS
Python Version: 3.6.13
wandb version: 0.10.30

Happy to provide any other information possible to help identify the cause of this issue (if it is in fact wandb related, which it might not be).

Hey @eric-mitchell
Thanks for the detailed issue. We will be tracking it internally.

@ariG23498 I should also note in case it's helpful, I'm seeing an error along the lines of:
wandb: Network error resolved after 0:06:01.586198, resuming normal operation.
showing up in a lot of the logs for the runs in which this issue occurs.

Hey @eric-mitchell both of these errors indicate you are having networking issues both to the NFS share and to the W&B server.  We retry all network requests to the W&B server so that should be fine, but I would suggest using a non networked filesystem for the wandb directory.
When you call wandb.init you can specify the dir argument or you can set the WANDB_DIR environment variable to a path on your machine that isn't a networked file system, such as /tmp

@vanpelt thanks for the recommendation- I'll give this a try and report back.

Closing because
wandb.init(..., dir=tempfile.mkdtemp())`

seems to have solved the problem. This issue also suggests using
username = pwd.getpwuid(os.getuid()).pw_name
wandb.init(..., dir=f"/tmp/wandb_{username}"`

Thank you for the help @vanpelt and @ariG23498!


Prevent searching from results page, instead bring back to home page

The proposed approach (raw editable text field transformed into a query) is lacking and not preferable. Until we settle on a good approach that doesn't introduce tech debt, we'll display the query and offer a "refine search" or simply "back" button.

PR #102


Soft restart needs to reset arrays and lists

This is solved as the deep copy method now copies arrays properly


remove @cachedOnly option. No purpose for it atm

Wow why is host tests timing out. Perhaps maybe its used somewhere. I will restart the test