Thread::Pool::Task leaks

#!/usr/bin/env ruby

require 'sigdump/setup'
require 'thread/pool'

puts "process started with pid: #{Process.pid}"

sum = 0

pool = Thread.pool(4) { |i| sum += i }

loop do
  1000.times { |i| pool.process(i) }

  GC.start
  sleep 30
end

kill the process with kill -CONT pid, we have sigdump result as following:
Sigdump at 2015-07-08 23:34:16 +0800 process 4530 (./leak.rb)
  Thread #<Thread:0x007f8e5a0c03b0> status=run priority=0
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `backtrace'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `dump_backtrace'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:25:in `block in dump_all_thread_backtrace'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `each'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `dump_all_thread_backtrace'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:16:in `block in dump'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `open'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `_open_dump_path'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:14:in `dump'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:7:in `block in setup'
      ./leak.rb:16:in `call'
      ./leak.rb:16:in `sleep'
      ./leak.rb:16:in `block in <main>'
      ./leak.rb:12:in `loop'
      ./leak.rb:12:in `<main>'
  Thread #<Thread:0x007f8e5a082ee8> status=sleep priority=0
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x007f8e5a082d08> status=sleep priority=0
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x007f8e5a082b28> status=sleep priority=0
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x007f8e5a082970> status=sleep priority=0
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /Users/forresty/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  GC stat:
      count: 9
      heap_allocated_pages: 74
      heap_sorted_length: 75
      heap_allocatable_pages: 0
      heap_available_slots: 30161
      heap_live_slots: 18598
      heap_free_slots: 11563
      heap_final_slots: 0
      heap_marked_slots: 17398
      heap_swept_slots: 12762
      heap_eden_pages: 74
      heap_tomb_pages: 0
      total_allocated_pages: 74
      total_freed_pages: 0
      total_allocated_objects: 103524
      total_freed_objects: 84926
      malloc_increase_bytes: 109520
      malloc_increase_bytes_limit: 16777216
      minor_gc_count: 5
      major_gc_count: 4
      remembered_wb_unprotected_objects: 190
      remembered_wb_unprotected_objects_limit: 380
      old_objects: 15195
      old_objects_limit: 30390
      oldmalloc_increase_bytes: 109904
      oldmalloc_increase_bytes_limit: 16777216
  Built-in objects:
    30,161: TOTAL
    11,457: FREE
    10,276: T_STRING
     3,146: T_ARRAY
     1,970: T_OBJECT
     1,877: T_DATA
       530: T_CLASS
       506: T_NODE
       267: T_HASH
        68: T_REGEXP
        27: T_ICLASS
        23: T_MODULE
         4: T_FILE
         4: T_FLOAT
         3: T_STRUCT
         2: T_BIGNUM
         1: T_COMPLEX
  All objects:
    10,446: String
     2,813: Array
     1,006: Time
       968: Thread::Pool::Task
       708: RubyVM::InstructionSequence
       264: Hash
       249: Class
       211: Gem::Version
       208: Gem::StubSpecification
       205: Gem::StubSpecification::StubLine
       204: Gem::Requirement
       124: Gem::Dependency
       100: Encoding
        68: Regexp
        39: Gem::Specification
        23: Module
        17: Proc
        12: RubyVM::Env
        12: MatchData
         7: Mutex
         5: Thread::Backtrace
         5: Thread
         4: Float
         3: IO
         3: Object
         2: Thread::ConditionVariable
         2: Bignum
         1: Thread::Pool
         1: IOError
         1: Binding
         1: RubyVM
         1: NoMemoryError
         1: SystemStackError
         1: Random
         1: ARGF.class
         1: Complex
         1: Data
         1: ThreadGroup
         1: File
         1: fatal
         1: Gem::Platform
         1: Monitor
         1: Gem::PathSupport
         1: Range
  String 281,685 bytes
   Array 2 elements
    Hash 2 pairs

We now have  968 Thread::Pool::Task
Ruby version:
$ ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin13]

Found on some other Ruby versions as well. Read the source code of thread gem, no idea why yet

and following was found on a long running process in one of our services:
Mutex:21825
Thread::Pool::Task:21732
Thread::Future:21710
RubyVM::InstructionSequence:8440

Looking into it.
Were the Thread::Future used withing a Thread::Pool or just by themselves?

@meh within a Thread::Pool
RDKit is a small toolkit I wrote, and we've built some long running processes on top of it
the problematic code is here:
https://github.com/forresty/rdkit/blob/master/lib/rdkit/client.rb#L38

I've been testing the example code you provided in the opening comment, and the leak is actually not a leak, at least in that code.
If you keep getting sigdumps and reduce the wait time, you'll see the number of tasks stays constant, that's because they're pushed onto the todo list and kept there until they're executed.
To avoid that leak you'd have to wait for the pool to be idle, and you can do that with pool.wait.process(i) in that small example.
#!/usr/bin/env ruby

require 'sigdump/setup'
require 'thread/pool'

puts "process started with pid: #{Process.pid}"

sum = 0

pool = Thread.pool(4) { |i| sum += i }

loop do
  1000.times { |i| pool.wait.process(i) }

  GC.start
  sleep 5
end

Sigdump at 2015-07-08 18:34:29 +0200 process 30127 (/tmp/lol.rb)
  Thread #<Thread:0x000000024172e0> status=run priority=0
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `dump_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:25:in `block in dump_all_thread_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `each'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `dump_all_thread_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:16:in `block in dump'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `open'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `_open_dump_path'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:14:in `dump'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:7:in `block in setup'
      /tmp/lol.rb:16:in `call'
      /tmp/lol.rb:16:in `sleep'
      /tmp/lol.rb:16:in `block in <main>'
      /tmp/lol.rb:12:in `loop'
      /tmp/lol.rb:12:in `<main>'
  Thread #<Thread:0x000000026d9500> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d92a8> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d8fb0> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d8a38> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  GC stat:
      count: 8
      heap_allocated_pages: 74
      heap_sorted_length: 75
      heap_allocatable_pages: 0
      heap_available_slots: 30160
      heap_live_slots: 12047
      heap_free_slots: 18113
      heap_final_slots: 0
      heap_marked_slots: 11812
      heap_swept_slots: 18347
      heap_eden_pages: 74
      heap_tomb_pages: 0
      total_allocated_pages: 74
      total_freed_pages: 0
      total_allocated_objects: 75555
      total_freed_objects: 63508
      malloc_increase_bytes: 29992
      malloc_increase_bytes_limit: 16777216
      minor_gc_count: 4
      major_gc_count: 4
      remembered_wb_unprotected_objects: 171
      remembered_wb_unprotected_objects_limit: 342
      old_objects: 11540
      old_objects_limit: 23080
      oldmalloc_increase_bytes: 30440
      oldmalloc_increase_bytes_limit: 16777216
  Built-in objects:
    30,160: TOTAL
    18,007: FREE
     7,996: T_STRING
     1,346: T_ARRAY
       896: T_DATA
       596: T_CLASS
       525: T_OBJECT
       506: T_NODE
       156: T_HASH
        68: T_REGEXP
        27: T_ICLASS
        23: T_MODULE
         4: T_FLOAT
         4: T_FILE
         3: T_STRUCT
         2: T_BIGNUM
         1: T_COMPLEX
  All objects:
     8,158: String
     1,014: Array
       708: RubyVM::InstructionSequence
       282: Class
       153: Hash
       133: Gem::Version
       115: Gem::StubSpecification
       112: Gem::StubSpecification::StubLine
       100: Encoding
        85: Gem::Requirement
        68: Regexp
        43: Gem::Dependency
        25: Time
        23: Module
        20: Gem::Specification
        17: Proc
        12: RubyVM::Env
         8: MatchData
         7: Mutex
         6: Thread::Pool::Task
         5: Thread::Backtrace
         5: Thread
         4: Float
         3: IO
         3: Object
         2: Bignum
         2: Thread::ConditionVariable
         1: File
         1: Complex
         1: ThreadGroup
         1: IOError
         1: Binding
         1: RubyVM
         1: NoMemoryError
         1: SystemStackError
         1: Random
         1: ARGF.class
         1: Data
         1: fatal
         1: Thread::Pool
         1: Range
         1: Gem::Platform
         1: Monitor
         1: Gem::PathSupport
  String 158,032 bytes
   Array 4 elements
    Hash 1 pairs
Sigdump at 2015-07-08 18:34:45 +0200 process 30127 (/tmp/lol.rb)
  Thread #<Thread:0x000000024172e0> status=run priority=0
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:39:in `dump_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:25:in `block in dump_all_thread_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `each'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:24:in `dump_all_thread_backtrace'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:16:in `block in dump'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `open'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:119:in `_open_dump_path'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:14:in `dump'
      /home/meh/.gem/ruby/2.2.0/gems/sigdump-0.2.3/lib/sigdump.rb:7:in `block in setup'
      /tmp/lol.rb:16:in `call'
      /tmp/lol.rb:16:in `sleep'
      /tmp/lol.rb:16:in `block in <main>'
      /tmp/lol.rb:12:in `loop'
      /tmp/lol.rb:12:in `<main>'
  Thread #<Thread:0x000000026d9500> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d92a8> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d8fb0> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  Thread #<Thread:0x000000026d8a38> status=sleep priority=0
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `sleep'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `wait'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:393:in `block (3 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `synchronize'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:373:in `block (2 levels) in spawn_thread'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `loop'
      /home/meh/.gem/ruby/2.2.0/gems/thread-0.2.0/lib/thread/pool.rb:372:in `block in spawn_thread'
  GC stat:
      count: 12
      heap_allocated_pages: 74
      heap_sorted_length: 75
      heap_allocatable_pages: 0
      heap_available_slots: 30160
      heap_live_slots: 12088
      heap_free_slots: 18072
      heap_final_slots: 0
      heap_marked_slots: 11894
      heap_swept_slots: 18265
      heap_eden_pages: 74
      heap_tomb_pages: 0
      total_allocated_pages: 74
      total_freed_pages: 0
      total_allocated_objects: 100602
      total_freed_objects: 88514
      malloc_increase_bytes: 24160
      malloc_increase_bytes_limit: 16777216
      minor_gc_count: 4
      major_gc_count: 8
      remembered_wb_unprotected_objects: 180
      remembered_wb_unprotected_objects_limit: 360
      old_objects: 11667
      old_objects_limit: 23334
      oldmalloc_increase_bytes: 24608
      oldmalloc_increase_bytes_limit: 16777216
  Built-in objects:
    30,160: TOTAL
    17,966: FREE
     8,024: T_STRING
     1,351: T_ARRAY
       900: T_DATA
       596: T_CLASS
       528: T_OBJECT
       506: T_NODE
       157: T_HASH
        68: T_REGEXP
        27: T_ICLASS
        23: T_MODULE
         4: T_FLOAT
         4: T_FILE
         3: T_STRUCT
         2: T_BIGNUM
         1: T_COMPLEX
  All objects:
     8,159: String
     1,019: Array
       708: RubyVM::InstructionSequence
       282: Class
       153: Hash
       133: Gem::Version
       115: Gem::StubSpecification
       112: Gem::StubSpecification::StubLine
       100: Encoding
        85: Gem::Requirement
        68: Regexp
        43: Gem::Dependency
        29: Time
        23: Module
        20: Gem::Specification
        17: Proc
        12: RubyVM::Env
         9: Thread::Pool::Task
         8: MatchData
         7: Mutex
         5: Thread::Backtrace
         5: Thread
         4: Float
         3: IO
         3: Object
         2: Bignum
         2: Thread::ConditionVariable
         1: File
         1: Complex
         1: ThreadGroup
         1: IOError
         1: Binding
         1: RubyVM
         1: NoMemoryError
         1: SystemStackError
         1: Random
         1: ARGF.class
         1: Data
         1: fatal
         1: Thread::Pool
         1: Range
         1: Gem::Platform
         1: Monitor
         1: Gem::PathSupport
  String 158,055 bytes
   Array 4 elements
    Hash 1 pairs

hmm
I've rerun the test with pool.wait, and more aggressive mode:
loop do
  1000.times { |i| pool.wait.process(i) }

  GC.start
end

the output seems good
 205: Gem::StubSpecification::StubLine
 204: Gem::Requirement
 169: Thread::Pool::Task
 124: Gem::Dependency

without pool.wait
13,508: Array
11,261: Thread::Pool::Task
10,420: String
 5,329: Time

Therefore I think the problem is very likely to be within my code, I will check it out, closing this now.
Thanks so much for the quick response! :smile:

Yeah, you'll have to block somewhere along the line, or you're just going to starve the pool with unprocessed tasks, even with futures.
For instance, tasks aren't that heavy memory wise, but I'd be worried about the truckload of Mutex instances, but a Future needs a Mutex each.

But it is does not seem like that our tasks are unprocessed, otherwise there will be very noticeable problems
From the live dump the Proc:109429 is suspicious though:
<IP_ADDRESS>:5444> gc
OK
<IP_ADDRESS>:5444> info objspace
# Objspace
TOTAL:761795
FREE:194052
T_OBJECT:143445
T_CLASS:2485
T_MODULE:271
T_FLOAT:11
T_STRING:37242
T_REGEXP:1153
T_ARRAY:93067
T_HASH:4516
T_STRUCT:57
T_BIGNUM:260
T_FILE:652
T_DATA:277363
T_MATCH:5
T_COMPLEX:1
T_RATIONAL:1
T_SYMBOL:129
T_NODE:6813
T_ICLASS:272

# Allobjects
Proc:109429
RubyVM::Env:98131
Hector::Channel:84566
Array:64515
String:37242
Time:29029
Mutex:24362
Thread::Pool::Task:24276
Thread::Future:24247
RubyVM::InstructionSequence:8440
Hash:4455
Thread::Backtrace:3821
Hector::User:3512

OK I will dig into the problem and report back if I've found something interesting. Thanks for the time! @meh

Yeah, that number does definitely seem way too big, it may be a problem with the interaction between Pool and Future.
I'll dig more on my side as well.

Ok, I confirm the problem is with Future, made a small test and it shows.

hmm
in https://github.com/meh/ruby-thread/blob/master/lib/thread/future.rb#L35
When there is a pool, the @thread is a Thread::Pool::Task not a Thread. Is this the problem?

Yes, the problem is task calls self.deliver, and @thread is a Task which is kept alive in the finalizer.
Just trying to figure out what to do.

I've tested with
if pool
  pool.process(&task)
else
  @thread = Thread.new(&task)

  ObjectSpace.define_finalizer self, self.class.finalizer(@thread)
end

and fixed this. Maybe I can provide a pull request?

hmm not quite right, cancel depends on the @thread ivar.
I'd wait for your fix then

Yeah, working on it.

Can you test master please? The small testcase seems to be fixed.

@meh deployed to our production server, seems like the correct fix
will report back later, thanks!

After ~10 hour the objects inside one of our processes looks like:
...
Regexp:666
Time:657
Gem::Requirement:423
Hector::User:347
Gem::Dependency:279
Module:271
Bignum:243
AVLTree::Node:241
Mutex:194
Gem::Version:148
Symbol:129
WeakRef:126
Encoding:100
Thread::Pool::Task:93
TCPSocket:89
Redis::Connection::Ruby:80
Redis::Client::Connector:80
Redis::Client:80
...

I believe that this bug is fixed. Thanks very much.

Cool, I'll release the gem then.


Fix start/stop/restart command tooltips

Description
Tooltips had stopped working on start/stop/restart buttons. This PR fixes and improves them:

Fix falling back from description to name if description is an empty string.
Add the resource type to display name. Tooltip (or name in action menu) displays "Start container", "Stop container", etc.

Do people like showing the resource type? Is "Restart container" better than "Restart"?

Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Do people like showing the resource type? Is "Restart container" better than "Restart"?

Nah, save the space.

/azp run

The test is being skipped https://github.com/dotnet/aspire/pull/5974. This won't pass until then.


Jcaccamo/add category move samples

@ldanzinger @JamesMBallard Ready for review. Moving these samples to a new category and folder, Utility Network.

@ldanzinger Merge conflicts resolved and Display utility association has been moved to the new folder and all files should reference the correct category.


Fix typo in command history button label

Keybinding shorthand for Control key is "ctrl".
I noticed this is spelled incorrectly when loading Waveterm for the first time.

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


Do not use ExecutionType.IDE when not debugging

When running tests from Visual Studio IntPreview (a build from last week), I observe that we are telling DCP to execute projects & executables via the IDE even when we are not debugging the tests. This fails because the IDE does not have a debug session when not debugging. This fix works around the issue by only enabling IDE execution when the debugger is attached.
The specific error I see is:
  | [2024-04-02T22:04:08] Aspire.Hosting.Dcp.dcpctrl.ExecutableReconciler Error: failed to start Executable	{"Executable": {"name":"servicea_3e8589f4-ej16bj0"}, "Reconciliation": 97, "error": "run session could not be started: failed to connect to IDE run session notification endpoint: websocket: bad handshake"}

EDIT: I cannot seem to reproduce this on the current build, so perhaps it's been fixed in VS?
cc @BillHiebert @karolz-ms
Microsoft Reviewers: Open in CodeFlow

This should work and we do NOT want this change. The execution type should only be driven by the presence of IDE debug session var. Having debugger detached is equivalent to running in Ctrl+F5 mode, still via IDE, but without debugging.

This should just work w/o doing anything. We need to investiage

Agreed that we don't want this change. I cannot reproduce this anymore. It was reproducing consistently on Tuesday, but I've updated VS since then. Maybe there was an issue which was already fixed somewhere.


Unlock poison dep

Poison lib is now 3.x (https://github.com/devinus/poison).
Is it possible to unlock the dep ?
currently {:poison, "~> 1.5 or ~> 2.0", optional: true}

What's the status on this? I just tried it out with poison 3.0, the tests work.

Opened simple PR that unlocks it. All tests passed :)

👍

Published: https://hex.pm/packages/joken/1.3.2


Unable to filter on entityStream properly

Hello,
I encountered the issue of not able to filter on a field from my Object. The object looks like this:
one abstract class that is extended by multiple objects that I am saving in Redis

the EntityStream code that I try to filter with:
entityStream.of(ConcreteObjectDTO.class)             .filter(ConcreteObjectDTO$.CLIENT_CODE.eq("0001QA"))             .collect(Collectors.toSet());
In RedisInsight I see the fallowing query:
  "FT.SEARCH" "com.path.to.my.dto.ConcreteObjectDTOIdx" "( @clientCode:0001QA)" "LIMIT" "0" "10000" "DIALECT" "1"
This query returns 0 entries.
If I try filtering by id, it works as expected:
entityStream.of(ConcreteObjectDTO.class)             .filter(ConcreteObjectDTO$.ID.eq("0001QA:some:specific:id"))             .collect(Collectors.toSet());
the query:
"FT.SEARCH" "com.path.to.my.dto.ConcreteObjectDTOIdx" "( @id:{0001QA\\:some\\:specific\\:id})" "LIMIT" "0" "10000" "DIALECT" "1"
I tried to edit the original query in redis CLI by adding curly braces to the client code value like this :
  "FT.SEARCH" "com.path.to.my.dto.ConcreteObjectDTOIdx" "( @clientCode:{0001QA})" "LIMIT" "0" "10000" "DIALECT" "1" and it works, but I am unable to figure out how to translate it to an entityStream code to behave the same...
We use redis-om-spring version: 0.9.1 and java version: 21

Either use @Indexed or @Searchable but not both on the same field. Also @Id is by default indexed as TAG so no need to add the @Indexed on @Id. Use @Searchble only if you need full-text search capabilities, for field like clientCode you are probably searching by exact value, right?
To troubleshoot it, also provide the FT.INFO "com.path.to.my.dto.ConcreteObjectDTOIdx"

It worked as expected. Thanks !


Resolve syncing conflicts from FromPrivateRepo to live

Pull request opened by OPS to resolve syncing conflicts from FromPrivateRepo to live.

@huypub : Thanks for your contribution! The author, @minewiskan, has been notified to review your proposed change.

@huypub @PRMerger14 - Why am I being notified of this?

@huypub : Thanks for your contribution! The author, @minewiskan, has been notified to review your proposed change.

DO NOT ATTEMPT TO FIX MERGE CONFLICT OR PROCESS THIS PR. PLEASE LEAVE THIS PR AS IS FOR NOW.
Contact @stevestein and @MightyPen if clarification is needed.
Thank you

@Minewiskan - Owen, go ahead and ignore this one!

@huypub : Thanks for your contribution! The author, @minewiskan, has been notified to review your proposed change.


Update new-eapconfiguration.md

#729
I cannot verify if the "WinLogonCredential with MSCAPv2, can use NON Window credential username + password" , I cannot find any article with regard to this.
Article: https://docs.microsoft.com/en-us/windows/security/identity-protection/vpn/vpn-authentication
Although according to the above article: "EAP-Microsoft Challenge Handshake Authentication Protocol version 2 (EAP-MSCHAPv2) supports User name and password authentication", Could you please help me to verify if this mean it accept a Non-windows credentials username + password.
Additionally in this article, it said that "UWP VPN plug-in can use the authentication method "User name and password" and supports custom credential type.
Can we recommend this to the user instead?
Technet Forum: https://social.technet.microsoft.com/Forums/en-US/4d677476-0440-4276-ab07-c142f07a7bc8/really-confused-about-peap-and-mschap-v2-why-sometimes-they-are-separated-and-sometimes-one-is-the?forum=winserverNIS
It said in this forum the " Passwords from the clients are send using hashes to the authentication server. To protect these password hashes being send over the network, you can use PEAP which act as a TLS/SSL tunnel to protect the authentication traffic." - so does this mean it is just accepts a Windows login credential?
=====================================================
References:
https://github.com/MicrosoftDocs/windows-powershell-docs/blob/master/docset/windows/vpnclient/add-vpnconnection.md
https://docs.microsoft.com/en-us/windows/security/identity-protection/vpn/vpn-authentication
https://docs.microsoft.com/windows/configuration/wcd/wcd-connectivityprofiles#vpn-1
AuthenticationUserMethod When you set NativeProtocolType to IKEv2, choose between EAP and MSChapv2.
https://docs.microsoft.com/en-us/windows/configuration/wcd/wcd-connectivityprofiles
https://docs.microsoft.com/en-us/windows/client-management/mdm/eap-configuration
https://support.microsoft.com/en-us/help/2744850/implementing-peap-ms-chap-v2-authentication-for-microsoft-pptp-vpns
https://social.technet.microsoft.com/Forums/en-US/4d677476-0440-4276-ab07-c142f07a7bc8/really-confused-about-peap-and-mschap-v2-why-sometimes-they-are-separated-and-sometimes-one-is-the?forum=winserverNIS

@nenonix Minor copy editing is needed for this PR. Thanks.

@dariomws306 @get-itips @tseward
Would you able to assist Jerry in moving forward with this PR?
Peer review is also needed for this PR. Thanks.

about VPN authentication method.

Should be methods.
I'm otherwise OK with the change.

Agree with Trevor.

I am ok with @tseward and @dariomws306

@AndreaBarr This PR can be merged. Thanks.


Do LiveQuery subscriptions support queries derived from relations?

This isn't an issue so much as a question: I've got live queries working fine with queries on parse objects, as in the example below.
    var testQuery = new Parse.Query('Test');
    var subscription = testQuery.subscribe();

But if I try to subscribe to a query derived from a relation, my event callbacks don't ever fire:
    var relation = user.relation('tests');

    // generate a query based on that relation
    var query = relation.query();
    var subscription = query.subscribe();

    subscription.on('enter', function(test){
      console.log('Info=\'Got subscription enter\' name=' + test.get('name'));
    });

Before I spend any more time on this, I thought I should ask - can I subscribe to queries derived from relations?

I think It's not cause I'm trying to subscribe to my relation's query. But It's giving me error.

+1

Apologize for closing this, but we want to make sure we stick to discussing actionable issues here in GitHub.
--
We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it.
You may also use Server Fault for questions about managing your own servers.


content goes under footer-bar if footer-bar specifies controller

<ion-content> goes under <ion-footer-bar> if <ion-footer-bar> contains a ng-controller
codepen example: (to visualize: on line 48 remove the ng-controller and the list item "Java" is not under the footer anymore)
http://codepen.io/anon/pen/KVBZrz

Adding an inline controller breaks the parent scope that should be there between ion-content and ion-footer-bar.  Logging out the parent scope when there is an inline-controller on ion-footer returns
Scope {$id: 1, $$childTail: ChildScope, $$childHead: ChildScope, $$prevSibling: null, $$nextSibling: null…}
$$ChildScope: ChildScope()
$$applyAsyncQueue: Array[0]
$$asyncQueue: Array[0]
$$childHead: ChildScope
$$childTail: ChildScope
$$destroyed: false
$$isolateBindings: null
$$listenerCount: Object
$$listeners: Object
$$nextSibling: null
$$phase: null
$$postDigestQueue: Array[0]
$$prevSibling: null
$$watchers: Array[2]
$$watchersCount: 5
$hasHeader: true
$hasSubheader: false
$id: 1
$ionicGoBack: (backCount)
$parent: null
$root: Scope
__proto__: Scope

With out the controller
Scope {$id: 1, $$childTail: ChildScope, $$childHead: ChildScope, $$prevSibling: null, $$nextSibling: null…}
$$ChildScope: ChildScope()
$$applyAsyncQueue: Array[0]
$$asyncQueue: Array[0]
$$childHead: ChildScope
$$childTail: ChildScope
$$destroyed: false
$$isolateBindings: null
$$listenerCount: Object
$$listeners: Object
$$nextSibling: null
$$phase: null
$$postDigestQueue: Array[0]
$$prevSibling: null
$$watchers: Array[4]
$$watchersCount: 5
$hasFooter: true
$hasHeader: true
$hasSubfooter: false
$hasSubheader: false
$id: 1
$ionicGoBack: (backCount)
$parent: null
$root: Scope
__proto__: Scope

Short term fix: Don't add a controller to the ion-footer-bar as it creates an isolated scope

Will note this also happens with ion-header-bar as well.

This issue was moved to driftyco/ionic-v1#190


[Web] how to add worker.js, worker.js.deps, worker.js.map in your project's root ?

how to add worker.js, worker.js.deps, worker.js.map in your project's root ?

Hello
you only have to add the worker.js file into the root directory, worker.js  is in the root of the package.
hope this helps

thanks ,


PySpark worker pool crash resilience

What changes were proposed in this pull request?
PySpark worker processes may die while they are idling. Here we aim to provide some resilience, by validating process and selectionkey aliveness prior to returning the process from idle pool.
Why are the changes needed?
To not fail queries when a python process crashed while idling.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added appropriate testcase.
Was this patch authored or co-authored using generative AI tooling?
No

@ueshin @HyukjinKwon can you take a look here?

Let's file a JIRA, see https://spark.apache.org/contributing.html

Apache Spark uses the GitHub Actions in your forked repository so the builds have to be found in https://github.com/sebastianhillig-db/spark/actions . The GitHub Actions would have to be enabled at https://github.com/sebastianhillig-db/spark/settings/actions , and rebase this PR

Merged to master.


When to release code

Interesting work
Is there any plan to release the source code?

Bump!

@zj-dong great work! Can you please advise if you are planning to release the code?


Variable may be used uninitialized

Variable entry in insertEntry may be used uninitialized:
https://github.com/munificent/wren/blob/744147fd94febd7dae0c14f132f2dec363252a6f/src/vm/wren_value.c#L522-L531
https://github.com/munificent/wren/blob/744147fd94febd7dae0c14f132f2dec363252a6f/src/vm/wren_value.c#L455-L459
Neither entry is initialized, nor findEntry sets it to NULL if capacity is not ensured, so when this assert should be triggered the variable is not actually set.

Trivial, initialize entry to NULL on line 522.
I think I have pull request for this somewhere, but can't find it. For some reasons, gcc only find it when not using WREN_NAN_TAGGING.


Edit

👷 Deploy Preview for adoring-leavitt-e31a11 processing.

Name
Link

🔨 Latest commit
bf9ae64327354481b294857c6595adf0e3f423ad

🔍 Latest deploy log
https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/62a89a39c045e20008aaf88c


add e2e test for service entry with inlined workload entry

What type of PR is this?
/kind enhancement
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #1037
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/lgtm


Add russian localozation

I'd be happy to merge this if you'd like!
Reopen the pull request if you want it merged.

i made new pull request, but i don´t see it. there was mistake (forgot space). i will create new pull request


The "@serverless-stack/aws-lambda-ric" dependency is not resolved reliably

While testing the tutorial project in https://github.com/microsoft/rushstack/pull/3282,  we encountered an issue where @serverless-stack/aws-lambda-ric is not being resolved correctly. The error looks like this:
Debug session started. Listening for requests...
a65a98b3-5b98-41d6-80b2-2e8f50daaa26 REQUEST repro-serverless-stack-tu-ApiLambdaGETB1714EF3-MjSo5wKL9F0a [src/lambda.handler] invoked by API GET /
2022-03-29T10:20:13.693Z    undefined   INFO    Executing '/Users/nobody/repro/rushstack/build-tests-samples/heft-serverless-stack-tutorial/.sst/artifacts/repro-serverless-stack-tutorial-my-stack-Api-Lambda_GET_-/src/lambda.handler' in function directory '/Users/nobody/repro/rushstack/build-tests-samples/heft-serverless-stack-tutorial'
- /Users/nobody/.npm/_npx/51045/lib/node_modules/aws-lambda-ric/bin/index.jslient/index.jslient.jse-client.node'

@frekje-wm was able to fix the issue by adding "@serverless-stack/aws-lambda-ric": "^2.0.12" as a direct dependency of the project. The solution may be similar to PR https://github.com/serverless-stack/serverless-stack/pull/1582

I was able to repro this problem on Windows. The error looks like this:
Debug session started. Listening for requests...
90d608d2-47aa-4408-9964-c8916bec7502 REQUEST prod-heft-serverless-stack-tu-ApiLambdaGETB1714EF3-Q2WJdPoQrWor [src/lambda.handler] invoked by API GET /
'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR!
code ELIFECYCLE
npm ERR! errno 1
npm
ERR<EMAIL_ADDRESS>preinstall: `./scripts/preinstall.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.

The workaround of adding @serverless-stack/aws-lambda-ric as a direct dependency also works on Windows.

PR: https://github.com/serverless-stack/serverless-stack/pull/1588

Fixed in v0.69.6 and v1.0.0-beta.20
@octogonz @fkjellberg Sorry about the delay in merging the fix. We were in the middle of restructuring the repo for v1 launch. :crossed_fingers:


remove non-metabolic isolated genes

Description of the issue:

Non-metabolic genes are discovered in the Subsystems of Isolated as below:

gene
Reasons
Subsystems
RxnIDs

ENSG00000082014
Involved in transcriptional activation and repression of select genes by chromatin remodeling
Isolated
MAR00024

ENSG00000115641
May function as a molecular transmitter linking various signaling pathways to transcriptional regulation
Isolated
MAR00024

ENSG00000120158
Does not have cyclase activity
Isolated
MAR09546

ENSG00000121486
Not methyltransferase. May play a role in motor coordination and exploratory behavior.
Isolated
MAR09519

ENSG00000124006
Core component of the 3M complex, a complex required to regulate microtubule dynamics and genome integrity.
Isolated
MAR09493

ENSG00000125686
Not lipid associated. Component of the Mediator complex, a coactivator involved in the regulated transcription of nearly all RNA polymerase II-dependent genes.
Isolated
MAR00024

ENSG00000127511
Not lipid associated. Acts as a transcriptional repressor.
Isolated
MAR00024

ENSG00000130589
Helicase that acts as a transcriptional coactivator.
Isolated
MAR00024

ENSG00000134317
Transcription factor involved in epithelial development
Isolated
MAR00024

ENSG00000135473
not annotated for this rxn in KEGG
Isolated
MAR09490

ENSG00000136715
Acts as a transcriptional repressor.
Isolated
MAR09464

ENSG00000148677
May play an important role in endothelial cell activation.
Isolated
MAR00024

ENSG00000162571
Inactive polyglycylase.
Isolated
MAR09505

ENSG00000167371
not sugar related, may be involved in synaptic transmission in the central nervous system.
Isolated
MAR09464

ENSG00000169375
Acts as a transcriptional repressor.
Isolated
MAR00024

ENSG00000177565
recruitment of the ubiquitin/19S proteasome complex.
Isolated
MAR00024

ENSG00000185250
Probable inactive PPIase with no peptidyl-prolyl cis-trans isomerase activity.
Isolated
MAR09492

ENSG00000185615
remove from rxn MAR00030, is not a transport gene.
Isolated;Transport reactions
MAR00030;MAR09806

ENSG00000177200
Acts as a transcriptional coactivator for PPARA and possibly other nuclear receptors.
Isolated
MAR00024

Current feature/value/output:

The association of these genes is lack of evidence according to the provided reasons

Expected feature/value/output:

Remove above genes from Human-GEM

I hereby confirm that I have:

[X] Done this analysis in the main branch of the repository
[X] Checked that a similar issue does not exist already

The gene ENSG00000185615 is currently associated with two reactions MAR00030 and MAR09806. It catalyzes the rearrangement of -S-S- bonds in the pancreas and may act as a chaperone that inhibits aggregation of misfolded proteins, this seems match well with MAR09806.

Yes. It is kind of match this rxn. I was thinking even this rxn should be removed, as the protein disulfide bond formation should be protein post-translational modification process rather a metabolic rxn, but we can keep this rxn for now and the gene association.

I was thinking even this rxn should be removed, as the protein disulfide bond formation should be protein post-translational modification process rather a metabolic rxn,

yes indeed, it belongs to PTM process and presented as a dead-end reaction in Human-GEM

Since ENSG00000177565 and ENSG00000169375 are complex subunits, it ould be safe to keep them for now.


Web App rewrite

WebApp Rewrite for the OpenTargets Platform

All further work associated with this Front End Development team project has been planned out by the team using React rewrite lime green labels to "tag" activities under particular OT pages to track plans and progress towards target milestones for completion.

@d0choa are y'all targeting a specific release for the full rewrite?

We haven't committed to a date for the full rewrite.
We'll release a public beta mid-June with the FE for all entity pages, the new search functionalities and the new GraphQL API. You might have seen that we had new recruitments (@javfg) and The Hyve (@Sjoerd-van-Hagen et al.) are contributing to the front-end these days.
Before the mid-June deadline, @mkarmona and @cmalangone will start the ETL work on evidence and associations, following up on the code from @eric-czech. It took more time than we anticipated, but we are getting there. We'll keep you posted.

Thanks @d0choa! We will keep an eye out for the public beta. We have been using the alpha site quite a bit because of the dynamic associations view and look forward to having the evidence strings available in that view.


⚠ Bofrost.es has degraded performance

In 2e9a80c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1623 ms

Resolved: Bofrost.es performance has improved in bdcd3eb after 6 minutes.


getUser always runs null

I'm using typescript version with 'asycn/await'.
public getLoggedUser(): Promise<Oidc.User> {
        return this.userManager.getUser();
 }

  private async onComponentDidMount() {
        let user = await this.userService.getLoggedUser();
        this.onUserChanged(user);
    }

private onUserChanged = (user: Oidc.User): void => {
        if (user === null) {
            this.setState({ rightElement: this.getLoginBnt() });
        } else {
            this.setState({ rightElement: this.getUserControls() });
        }
    }

and the config:
        const config = {
            client_id: 'js',
            redirect_uri: `${window.location.protocol}//${window.location.hostname}:${window.location.port}`,
            response_type: 'id_token token',
            scope: 'openid profile',
            authority: 'http://localhost:5000',
            post_logout_redirect_uri: `${window.location.protocol}//${window.location.hostname}:${window.location.port}/login`,
            silent_redirect_uri: od`${window.location.protocol}//${window.location.hostname}:${window.location.port}/silent_renew.html`,
            automaticSilentRenew: true,
            filterProtocolClaims: true,
            loadUserInfo: true
        };

seeing many related issue, but can find the good fix.
Thanks,

This is not enough info for me to help. You will have to debug.

I closed this issue.
This is my missing understanding work-flow.
Thank you
On Thu, Dec 1, 2016 at 10:08 AM, Brock Allen<EMAIL_ADDRESS>wrote:

Closed #203 https://github.com/IdentityModel/oidc-client-js/issues/203.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IdentityModel/oidc-client-js/issues/203#event-877884289,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFXNMVVWcRyfT9xPew0Xij88niJbApV7ks5rDjoigaJpZM4K3RIa
.


Variable of type VOID (void) with pointer.

A VOID type variable with pointer (single or double) will be declared "VOID _variable_name[100];" in test driver.
This will be error when compiled.
Update this trouble.

Update the application
to generate test driver codes


Kafka Admin security schemes allow only service accounts and not token

We have that
 securitySchemes:
   Bearer:
     type: oauth2
     description: Access token used with OAuth 2.0
     flows:
       clientCredentials:
         tokenUrl: /token
         scopes: {}

In openapi file:
https://github.com/bf2fc6cc711aee1a0c2a/kafka-admin-api/blob/96c5e76b8867a763eb542a25fd74c08b6267f26a/kafka-admin/src/main/resources/META-INF/openapi.yaml#L407-L414
That would render service account authentication:
but we should also supply token based authentication which is also supported and in most cases more desired:
  securitySchemes:
    Bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

Ping @MikeEdgar WDYT?

I agree - any issue with renaming the existing Bearer to OAuth2? This will need to be dynamically added (in the OASFilter) only when OAuth2 is enabled.

To make sure that I understand do you mind putting full snippet of what will be pushed to the repository? As for dynamically added - that is no problem - we only use version in the repository right now for both SDK and API portal

@wtrocki - it would end up like this:
security:
- OAuth2: []
- Bearer: []
.
.
.
  securitySchemes:
   OAuth2:
     type: oauth2
     description: Access token used with OAuth 2.0
     flows:
       clientCredentials:
         tokenUrl: "/token"
         scopes: {}
    Bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

Perfect! That works well with swagger UI


url fix for unisolated domain

MD5: 3449c9e5e332f1dbb81505cd739fbf3f
NSP - Security Report
This is an automated security audit of this project. Please do not modify its contents
Vulnerabilities found: 15
Affected Modules: superagent, superagent, superagent, superagent, mime, mime, mime, mime, mime, superagent, superagent, uglify-js, uglify-js, debug, fresh
Summary:

Large gzip Denial of Service
Large gzip Denial of Service
Large gzip Denial of Service
Large gzip Denial of Service
Regular Expression Denial of Service
Regular Expression Denial of Service
Regular Expression Denial of Service
Regular Expression Denial of Service
Regular Expression Denial of Service
Large gzip Denial of Service
Large gzip Denial of Service
Regular Expression Denial of Service
Incorrect Handling of Non-Boolean Comparisons During Minification
Regular Expression Denial of Service
Regular Expression Denial of Service

Detailed report
Large gzip Denial of Service
Affected Module: superagent
Installed version: 1.8.5
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Large gzip Denial of Service
Affected Module: superagent
Installed version: 1.8.5
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Large gzip Denial of Service
Affected Module: superagent
Installed version: 1.8.5
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Large gzip Denial of Service
Affected Module: superagent
Installed version: 1.8.5
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: mime
Installed version: 1.3.4
Patched versions: >= 1.4.1 < 2.0.0 || >= 2.0.3
Advisory: https://nodesecurity.io/advisories/535
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: mime
Installed version: 1.3.4
Patched versions: >= 1.4.1 < 2.0.0 || >= 2.0.3
Advisory: https://nodesecurity.io/advisories/535
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: mime
Installed version: 1.3.4
Patched versions: >= 1.4.1 < 2.0.0 || >= 2.0.3
Advisory: https://nodesecurity.io/advisories/535
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: mime
Installed version: 1.3.4
Patched versions: >= 1.4.1 < 2.0.0 || >= 2.0.3
Advisory: https://nodesecurity.io/advisories/535
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: mime
Installed version: 1.3.4
Patched versions: >= 1.4.1 < 2.0.0 || >= 2.0.3
Advisory: https://nodesecurity.io/advisories/535
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Large gzip Denial of Service
Affected Module: superagent
Installed version: 2.3.0
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Large gzip Denial of Service
Affected Module: superagent
Installed version: 2.3.0
Patched versions: >=3.7.0
Advisory: https://nodesecurity.io/advisories/479
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: uglify-js
Installed version: 2.2.5
Patched versions: >=2.6.0
Advisory: https://nodesecurity.io/advisories/48
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Incorrect Handling of Non-Boolean Comparisons During Minification
Affected Module: uglify-js
Installed version: 2.2.5
Patched versions: >= 2.4.24
Advisory: https://nodesecurity.io/advisories/39
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: debug
Installed version: 2.2.0
Patched versions: >= 2.6.9 < 3.0.0 || >= 3.1.0
Advisory: https://nodesecurity.io/advisories/534
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
Regular Expression Denial of Service
Affected Module: fresh
Installed version: 0.3.0
Patched versions: >= 0.5.2
Advisory: https://nodesecurity.io/advisories/526
Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>


[3.x] No get_as_bulk_array method on multimesh

Godot version:

3.2.3 stable
OS/device including version:

Windows 10 64bit, Ryzen 3600, RTX 2070s, GLES3/GLES2
Issue description:

Not sure if it is a feature proposal or a bug, but seems closer to a bug: There is a set_as_bulk_array method, but no get_as_bulk_array.
Steps to reproduce:
Try to use get_as_bulk_array(), which does not exist.
Minimal reproduction project:

Not necessary? It's a missing function.

Could you explain why you want the method/what the use case would be? The existence of a setter doesn't necessarily mean that there should be a getter if the data is only meant as input and not output.

Fair enough, I probably should have explained originally!
Personally, I discovered this when trying to sort multimesh instances by closest to the player camera (so if I limited the number of visible instances, only the closest ones are left), but accessing get_instance_transform alone (not to mention set_instance_transform) seems to be too slow when handling large amounts of multimeshes (for some reason, it is much slower on a thread, as well... maybe sync issues?), especially when you're doing something with many accesses like an in-place sort. I didn't want to build a new sorted array either because of the large number of objects, and the accesses to build it initially would still be too slow. But if I can fetch all of them at once, do my processing in a thread, then instantly bring them back, it would make it much faster.
I can see other uses for this, too. The documentation talks about set being useful for loading data and processing it, but in the same way it could be useful for saving data or mutating already existing multimesh data. Saving could be useful for custom levels, for example. You may also want to assign many new properties to the multimesh that require you to know the original values. For example, you have many rocks instanced as multimeshes, and it begins to rain, and you want to mark some rocks as not having objects above them using their transform so they can become wet.

accessing get_instance_transform alone (not to mention set_instance_transform) seems to be too slow when handling large amounts of multimeshes

I stumbled across the same need in my voxel engine. I have a system that spawns instances on top of terrain using multimeshes (grass and small rocks) and these instances must be detached when the user digs holes in the ground where they stand. So I need to iterate them to find which ones must be removed. I would probably not need get_as_bulk_array since it would still need decoding, but I've seen transforms are cached in VisualServer so it would be useful to just have access to that, instead of doubling my own cache or having to do an invididual call for each.

I think this could be a harmless addition. So I am not opposed to adding it. That being said, I am not certain it is necessary or advisable to use.
set_as_bulk_array was added in order to support CPU Particles. We needed a fast way to update all the particle data at once. The use-case is similar to the above, except CPU Particles don't need to request data from the visual server.  CPU Particles maintains its own particle array and then just pushes to the Visual Server when it needs to. This works well with Godot's design which is to try to never return data from the server (see the Servers Doc).
If performance is your main concern, then you should keep a copy of the array yourself. get_as_bulk_array is going to cause threading stalls and will decrease overall performance. Off the top of my head the only time get_as_bulk_array would be advisable is in a single-threaded environment where memory is extremely constrained.

If performance is your main concern, then you should keep a copy of the array yourself.

That sounds sensible, however why is VisualServer keeping a duplicated cache as well?

That sounds sensible, however why is VisualServer keeping a duplicated cache as well?

The typical API for Multimesh is for users to allocate a certain number of instances in advance (this allocates space on the GPU), and then set each instance one at a time using commands (set_instance_transform for example). set_as_bulk_array was introduced to allow users to set all transforms, color data, and custom data in a single API call to reduce overhead. This API requires an array to be stored in the renderer. Further, users can still request instance data from the API using, for example, get_instance_transform

Hmm... having two copies of the same data CPU-side in such case sounds wasteful, but that's probbaly unavoidable to support use cases Godot wants to provide I suppose

If performance is your main concern, then you should keep a copy of the array yourself. get_as_bulk_array is going to cause threading stalls and will decrease overall performance.

Yeah I was considering only using it in the beginning to get the initial values then mutating and setting it when needed. The threading stalls actually explain why the iteration performance was so much worse than in the main thread.

Transforms are cached in the same format as *bulk_array in VisualServer so it would be useful to just have access to that

That does sound good, but I'm not sure if that's possible to do with GDScript?
I do have a branch with a get_as_bulk_array implementation that makes a PoolArray copy it sends out. I can make a PR for that.

Hmm... having two copies of the same data CPU-side in such case sounds wasteful, but that's probably unavoidable to support use cases Godot wants to provide I suppose

I guess, realistically how large is your instance array? We are talking about data in the range of kilobytes for an array of thousands of instances. But yeah, thats why I mentioned above that get_as_bulk_array may be useful for extremely memory constrained situations.

Transforms are cached in the same format as *bulk_array in VisualServer so it would be useful to just have access to that

From a usability standpoint it would be great to just write directly to or read directly from the transform array, but then multithreading is just not possible at all. The architecture of the Visual Server is designed to allow for maximum speed and multithreading opportunities. Sometimes this results in a slightly more verbose API, but the performance benefits are certainly worth it.

it would be great to just write directly to or read directly from the transform array, but then multithreading is just not possible at all.

Isn't it when CoW actually comes in handy?


Github extension sign-in issues

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.25393.1
Other software
OS Build Version: 10.0.25393.1.amd64fre.zn_release.230608-1158
.NET Version: .NET 6.0.16
Steps to reproduce the bug
When I click on Sign-in with the GH Extension, nothing happens.
Expected result
I expect something to open up either enter/choose my credentials/keys for GH
Actual result
nothing happens
Included System Information
Physical Memory: 7.84GB (0.98GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Duplicate of #472


Test with Ruby 3.0

Description
Detail your changes here.
A few sentences describing the overall goals of the pull request's commits will suffice.
Some questions you might answer:

Why was this change required?
Did you have any tough decisions to make? Which one(s) did you go with and why?
Are there any deployment impacts to this change?
Is there something you aren't happy with or that needs extra attention?

Testing
Outline steps to test your changes.

Go here.
Click this.
See that.

To-Dos

[ ] tests
[ ] documentation

References

GitHub Issue ####
GitHub Pull Request ####

How do we want to go about this? Do we want to merge this in first, and then merge the kwargs PR into draper master afterward?

How do we want to go about this? Do we want to merge this in first, and then merge the kwargs PR into draper master afterward?

How do we want to go about this? Do we want to merge this in first, and then merge the kwargs PR into draper master afterward?

Sounds good 👍

How do we want to go about this? Do we want to merge this in first, and then merge the kwargs PR into draper master afterward?

Sounds good 👍

@oieioi Do you want to approve this and merge it into your branch when you get a chance?

@oieioi Do you want to approve this and merge it into your branch when you get a chance?


where is the changelog?

I am still using 0.13.3 but now 1.0.0 is available (along with apollo-client@2?). There have been lots of changes in the docs, and I would like to know about breaking changes before updating, but I can't find any changelog.

Inside of each package /packages/apollo-angular/CHANGELOG.md


Cannot read property 'column' of undefined

Issue Id: 5ef8005d-2f0e-147b-4511-4c5a6058112eVersions - 1.47.0-  59c7cbcf15745e4a8adb4fc59b63aa93f14d3cc3-  376d9d9d785ccca128fdbb16f001446d0ad64d32Stack TypeError: Cannot read property 'column' of undefined/vs/editor/contrib/suggest/suggestModel.ts#463:69

Did occur again


Use JSON files as input for the CLI instead of only CLI input parameters

The CLI for calling the RPC methods now has all structures built from command line parameters. This makes the command line very long and quite cumbersome to call. @brenzi suggested to use an input JSON file instead, that holds all the information, e.g. order.
This issue was orignally discussed in this PR: https://github.com/Polkadex-Substrate/polkadexTEE-worker/pull/30 -> https://github.com/Polkadex-Substrate/polkadexTEE-worker/pull/30#discussion_r638814353

Do we really need to do this? since CLI is only for PoC, is there any reason to include the CLI-based interaction for production? If not, we don't really need to do this.

agreed: we don't need it ATM

@Gauthamastro can we close this or should we move it to the main net?

Let's close this


Semicolon in F# member declaration is not recognized as end of expression

Code is below, but due to indentation issues it will probably be easier to understand the problem by referring to attached screenshots.
type Name = Name of string
    with override x.ToString() = let value (Name s) = s
                                 value x

(here the 'value x' line is indented to begin directly below the 'let')
is acceptable but the equivalent code
type Name = Name of string
    with override x.ToString() = let value (Name s) = s; value x

results in a compiler error.
Problem observed on VS Community 15.6.4
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/227841/semicolon-in-f-member-declaration-is-not-recognize.html
VSTS ticketId: 594506
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)

This is by design - ; has never been end-of-expression, you have to use in


[Fix] export/TypeScript: properly detect export specifiers as children of a TS module block

Fixes #1773

Coverage decreased (-2.09%) to 95.819% when pulling 2b5705b205333609da4848421cd4ccee9771515d on andreubotella:fix/export-specifiers-in-ts-module into 5fe14e391f8c74c23f1d78fd547791f79ad30146 on benmosher:master.


Update title of Overflow with Icon section of Breadcrumb demo (#5652)

closes #5652

@nabinbhatt Thanks for your contribution 😊


Typo and style

Few fixes staging on my repo
Checklist

[X] documentation is added or updated
[ ] tests are added or updated

Should I split out ssl.h corrections into his standalone PR to ease the Approval ?

Rebased to latest master

Comments fixed, and PR rebased to last master.

reconfirm +1
I'll merge.

Merged to master; closing


Tiles not updating

Hi, I haven't seen changes on map since two days ago.
Here are some changes:
https://www.openhistoricalmap.org/changeset/20962
https://www.openhistoricalmap.org/changeset/21021

hi @nik994 , thank you for reporting this issue, we have been updating the platform and there were an issue there, but it was already fixed.
Hope these are the changes that you expected :

Hi @Rub21, there are new changes:

UPDATE: While I was writing this post, changes have shown. :)

Nice , Go to know that is working fine , so I will close this ticket!!


Render newlines in profile bio

Added white-space: pre-line; to .about so that it renders newlines in my bio. pre-line removes the extra whitespaces but keeps the \n s

@basantagoswami sorry I forgot to notify you that the problem has been fixed, thanks for the report.


Mwpw 129255

Codecov Report
Patch coverage has no change and project coverage change: +23.18 :tada:

Comparison is base (b871d4f) 39.16% compared to head (4d43119) 62.34%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##            stage       #5       +/-   ##
===========================================
+ Coverage   39.16%   62.34%   +23.18%
===========================================
  Files           2       26       +24
  Lines         286     2114     +1828
===========================================
+ Hits          112     1318     +1206
- Misses        174      796      +622

see 24 files with indirect coverage changes

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


[Question] Insert partially NULL binary string

It can be useful to insert binary data that is partially NULL. E.g. 0x12 00 13 00 00 13 14 16
I am unsure if this feature is present. As far as I can tell it is only possible to insert either an all NULL value, or insert a c-like string(where NULL is the string terminator).
It appears to me that I must have missed something here?

On 29 Sep 2016 08:56, "Aart Stuurman"<EMAIL_ADDRESS>wrote:

It can be useful to insert binary data that is partially NULL. E.g. 0x12
00 13 00 00 13 14 16

I think you need to provide an example of SQL, details of table/column
schema to illustrate what you aim to achieve. Perhaps you have sample of
C++ code to show how you call nanodbc and what is not working.

Sorry for being unclear. Lets see if I can make it more clear.
The C++ code below describes what I'm trying to achieve. The database column 'raw_data' is a Mysql BINARY(300) field(just for testing purposes).
The problem I have is that I cannot find out how to insert this binary data. I cannot convert this to a c-string because that is terminated by a zero byte.
// create my binary string
std::vector<unsigned char> rawdata;
rawdata.push_back(14);
rawdata.push_back(0);
rawdata.push_back(99);
rawdata.push_back(0);
rawdata.push_back(0);
rawdata.push_back(3);

// display string
for (unsigned char& c : rawdata)
    std::cout << (unsigned int)c << " ";
std::cout << std::endl;

// insert everything in database
nanodbc::statement statement(nanodbcInstance);
nanodbc::prepare(statement, "INSERT INTO mydb.mytable (raw_data, unpack_successful) VALUES (?, FALSE)");
// Bind raw data. (this does not compile because I do not use a supported type)
statement.bind(0, rawdata);
nanodbc::just_execute(statement);

I figured out a way to bind this type of data. statement.bind can also be called by providing an array and the number of objects in the array.
// create my binary string
std::vector<unsigned char> rawdata;
rawdata.push_back(14);
rawdata.push_back(0);
rawdata.push_back(99);
rawdata.push_back(0);
rawdata.push_back(0);
rawdata.push_back(3);

// display string
for (unsigned char& c : rawdata)
    std::cout << (unsigned int)c << " ";
std::cout << std::endl;

// insert everything in database
nanodbc::statement statement(nanodbcInstance);
nanodbc::prepare(statement, "INSERT INTO mydb.mytable (raw_data, unpack_successful) VALUES (?, FALSE)");

vvvvv
// Bind raw data. (this does not compile because I do not use a supported type)
statement.bind(0, rawdata.data(), rawdata.size());
^^^^^

nanodbc::just_execute(statement);

This does however make for some strange results in the database for the parts of data that you don't write to. For example if BINARY(30) is used and you only bind an array of 10 long, the last 20 bytes seem to be gibberish. This seems logical to me, but when I used a TEXT field, I expected 10 bytes to be used in the database, where I instead got my 10 bytes, plus 30-ish extra bytes of gibberish, which I did not expect or add to my bound array.

Comments would be very much appreciated. Meanwhile I am experimenting and trying to figure out what I am doing wrong.

Resolved by #219 solution.


Implement template-string based replacement methods

These alternative replace/replacing methods let you pass a template string with $-prefixed replacement tokens.
let str = "a:b c:d"
let swapped = str.replacing(/(\w+):(\w+)/, withTemplate: "$2:$1")
// swapped = "b:a d:c"

Tokens can be written as:

/\$\d+/: one or more consecutive digits are read into a single number
/\${\d+}/: you can use this if the token is followed by literal numbers
/\${\w+}/: using a capture by name

Here's surely an uncontroversial design decision: Unrecognized tokens are silently omitted from the output. Other approaches are to include them in the output, or to trap.
\$ escapes the dollar sign into the output; needs to be written as \\$ in a regular string literal, where \$ is an invalid escape sequence.

This looks like a pretty good starting point, but I think there's a bunch of open design questions to resolve before we land this on main. Can we spin up a feature branch for templates?

Sounds good! We can iterate on the feature/replace_template branch.


Unable to validate the configuration by running botium in emulator mode

Im trying out this : https://chatbotsmagazine.com/10-minutes-codeless-test-automation-for-ibm-watson-chatbots-d71eac9626d7
But unable to validate the configuration by running Botium in “emulator”mode

botium-cli emulator --config path/to/botium.json
Error: Loading Botium plugin failed
at Validate.Validate.then (C:....\botium-cli\node_modules\botium-core\src\containers\PluginConnectorContainer.js:56:15)

Is there a problem in installing the botium package?

Please only use this issue tracker if you think you found a bug in Botium.

For asking questions please use Stackoverflow - we are monitoring and answering questions there.
The documentation on a very technical level can be found in the Botium Wiki.
For our VIP users, there is also a Slack workspace available (coming soon).


WIP : Refactor as per golint warnings.

golint was giving warnings for not having proper variable names and comments etc. hence added those.
Added small test for checking null as input for Flatten function.

Current coverage is 25.50% (diff: 100%)

Merging #261 into master will not change coverage

@@             master       #261   diff @@
==========================================
  Files            33         33
  Lines          1200       1200
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            306        306
  Misses          839        839
  Partials         55         55

Powered by Codecov. Last update cd593dc...df94dfd

Please ignore this PR for a while, still fixing it.
Went wrong in Rebase, so either I will close this one or fix it whichever seems easy.

I did messed up while rebase.
Hence closing.
New PR created #263


DarkRP Shipments owned by player on spawn

http://i.imgur.com/mCwcl06.png

Disable strict spawn checks

21:29:42 - Server cvar 'dpp_strict_spawn_checks' changed to 0
Shipments still owned by players. Am I doing something wrong here?
http://i.imgur.com/XSttJtu.jpg
http://i.imgur.com/YhUl1bW.jpg


Add (optional) support for watermarks in FIFOs

It's often useful to have a "high watermark/low watermark" signal from a FIFO, particularly when processing any kind of fixed-length frames. This could be implemented as a wrapper around SyncFIFO pretty easily but probably wants to be more deeply integrated with AsyncFIFO since there's already a clock-domain-crossing counter to use (which is not currently exposed to consumers).

I'm not sure how an async FIFO with water marks works, CDC-wise. Do you have any references?

As section 5.6 of http://www.sunburst-design.com/papers/CummingsSNUG2002SJ_FIFO1.pdf says, you compare against (ptr+N) instead of (ptr) as you would for empty/full. That section appears to be discussing FIFO style 1, but the same technique should be adaptable to FIFO style 2 with minor modifications.

That means we have to Gray decode the resynchronized counters, right? Then it seems like we should rather have r_level and w_level for consistency with SyncFIFO, and the consumer of the FIFO interface can then write a comparator with HWM/LWM. We can even make it a part of the general FIFO interface, with the SyncFIFO case aliasing level as both.

That makes sense, then we can always create a HWM/LWM wrapper as a utility module if we want to and it can work with any FIFOInterface instance.

In particular I think having a level is strictly more useful than watermarks (even configurable watermarks), if only for debugging. It's true that comparators are cheaper on architectures which have lookahead carry primitives, but I would say that it's the toolchain's job to simplify subtract-then-compare, since that's a fairly simple local transformation.

I'll be honest, I missed level on SyncFIFO when I was looking at the existing FIFO code 😅

Fixed in https://github.com/nmigen/nmigen/pull/472, https://github.com/nmigen/nmigen/pull/512, https://github.com/nmigen/nmigen/pull/513, https://github.com/nmigen/nmigen/pull/524.


Add files via upload

student license for Kastamonu Üniversitesi
file.zip

@BaranParlak Please fork SWOT repository, copy file.zip in the root folder of your forked SWOT repository. Then unzip file.zip there with no changes to the directory structure. Then make a new pull request. If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message. I have to close this request without merging. Thank you for your understanding.


add missing fi to build-node.sh

The nested ifs introduced in #149 were missing their respective fi tokens.
This is causing node builds to error out with the message:
.kokoro/firebase/build-node.sh: line 30: syntax error near unexpected token `else'

This PR should add the missing fi.

Thanks!
Maybe we should make sure shellcheck is running against these scripts in CI?


Objects - POLAR - Width/Height/Depth vs Size

Dolby Atmos uses the concept of size as a more high level property.
Define mappings between Size and Width / Height / Depth

This is related to immersive-audio-live/ADM-OSC#2
We currently have proposed "polar" width from 0-180 degrees. Dolby's cartesian proposal is normalized?  It would be better not to have to rely on a different message to know how to interpret /width

We could use /width in polar space (and /w in cartesian)? That would just mess with people's heads, though.
maybe/widthDeg vs /w? It's an interesting problem that width in degrees probably should be affected by distance.


ExplicitStringVariableFixer - fixes for backticks and for 2 variables next to each other

The converted string should be "My name is ${james}${bond}!", right @Slamdunk ?

Yup: https://3v4l.org/eGagi

Solved in https://github.com/kubawerlos/PHP-CS-Fixer/pull/1 @kubawerlos please review and merge if it's ok for you

@SpacePossum I can see this case in tests

@kubawerlos thanks man, I over looked it :+1:

this fixes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4006 as well I think?

Yups: see https://github.com/kubawerlos/PHP-CS-Fixer/pull/2 please @kubawerlos merge it to prove the bugfix :)

Closes #4006
Closes #4029
Closes #4036

Thank you @kubawerlos.


this software had met mistake, i had changed the blastn version, diamond version， how can i solve it ?

WARNING: Output folder </home/meta/mdisk/pl/earthworm/megahit/cd-hit/L1HHH0200300/MGE_new> contains <blastout.txt> and/or <.filtered.>, they/it will be overwritten.
[2024-05-09 14:50:21] INFO: Processing </home/meta/mdisk/pl/earthworm/megahit/cd-hit/L1HHH0200300/MGE_new/extracted.fa> ...
[2024-05-09 14:50:21] INFO: Extracting target sequences using BLAST ...
[2024-05-09 14:50:21] INFO: BLAST settings: 1260675 bps, 8355 reads, 10 threads, mt_mode 0.
[2024-05-09 14:50:24] INFO: Merging files ...
Traceback (most recent call last):
File "/home/meta/miniconda3/envs/args_oap/bin/args_oap", line 10, in
sys.exit(main())
^^^^^^
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/args_oap/args_oap.py", line 232, in main
options.func(options)
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/args_oap/stage_two.py", line 213, in run_stage_two
StageTwo(vars(options)).run()
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/args_oap/stage_two.py", line 208, in run
self.merge_files()
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/args_oap/stage_two.py", line 191, in merge_files
out = pd.merge(self.metadata, result, on='sample')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/pandas/core/reshape/merge.py", line 170, in merge
op = _MergeOperation(
^^^^^^^^^^^^^^^^
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/pandas/core/reshape/merge.py", line 794, in init
) = self._get_merge_keys()
^^^^^^^^^^^^^^^^^^^^^^
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/pandas/core/reshape/merge.py", line 1310, in _get_merge_keys
left_keys.append(left._get_label_or_level_values(lk))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/meta/miniconda3/envs/args_oap/lib/python3.12/site-packages/pandas/core/generic.py", line 1911, in _get_label_or_level_values
raise KeyError(key)
KeyError: 'sample'

Did you modified the metadata.txt file?
Can you confirm that the first entry of the file is sample using:
grep sample metadata.txt

i have rerun the stage_one, after, the stage_two had not make mistake and had sucessfully run again


feat(Scalar.AspNetCore): add HideClientButton configuration

This PR adds support for the recently introduced (https://github.com/scalar/scalar/pull/4047) hideClientButton option to the Scalar.AspNetCore integration.

That was fast!


Support svpcom wifibroadcast

Broken out from https://github.com/goodrobots/maverick/issues/437

Main repo: https://github.com/svpcom/wifibroadcast

Referring to the new wifibroadcast as wifibc, to differentiate the projects.  Compile/install implemented, but wifibc works differently to wifibroadcast.  wifibroadcast takes a byte stream pipe whereas wifibc is hardcoded to take a udp rtp stream on port 5600.
So the gstreamer pipeline for wifibc needs to send an rtp encapsulated stream to udpsink, whereas wifibroadcast either pipes raspivid directly or uses fdsink from gstreamer.

So create a separate systemd service manifest for wifibc which can run standalone and listen for packets on port 5600.
Network interface post action for network-if-monitor.sh should remain the same.

this is also supporting mavlink telemetry correct?  so if you have maverick on robot and maverick with gcs this should support video and telemetry via wifibc?

Ideally, yes

Support should be complete, maverick services added: wifibc_tx and wifibc_rx.  Config added in ~/config/network/wifibc, keys go in ~/data/network/wifibc.

Need to document, but to activate, change settings in ~/data/vision/maverick-visiond.conf to:
output = udp
output_dest = <IP_ADDRESS>
output_port = 5600

^^ This tells visiond to output rtp udp stream.
Turn on wifibc in localconf:
"maverick_network::wifibroadcast::tx_active": true,

Then create a wifibroadcast interface in localconf as per network docs (eg. wcast0), and specify the interface in ~/config/network/wifibc/tx.conf
INTERFACE=wcast0

Reboot to activate everything.  At this point visiond should be streaming rtp udp to localhost 5600, and wifibc_tx service should be running which picks up the rtp udp stream and broadcasts it over the specified interface.

Todo: document receiver, but is essentially the above in reverse.  Need to copy the rx key (~/data/network/wifibc/rx.key) from the sender(tx) computer to the receiver.

Got this on an RPi2.  Looks like just keygen and this is for my rx anyway.
Notice: /Stage[main]/Maverick_network::Wifibroadcast/File[/srv/maverick/data/network/wifibc]/ensure: created
Error: Could not find command '/srv/maverick/software/wifibc/bin/keygen'
Error: /Stage[main]/Maverick_network::Wifibroadcast/Exec[wifibc-genkeys]/returns: change from 'notrun' to ['0'] failed: Could not find command '/srv/maverick/software/wifibc/bin/keygen'
Notice: /Stage[main]/Maverick_network::Wifibroadcast/File[/srv/maverick/config/network/wifibc]/ensure: created

Looks like an ordering issue, could you attach the log?

Looks like an ordering issue, could you attach the log?

Ordering fixed

Need to add kernel pcap permissions for wifibc_tx/rx:
May 01 12:27:25 maverick-up wifibc.sh[6861]: /srv/maverick/software/wifibc/bin/tx -K /srv/maverick/data/network/wifibc/tx.key -k 8 -n 12 -u 5600 -p 1 wcast0
May 01 12:27:25 maverick-up wifibc.sh[6861]: Error: pcap_activate failed: socket: Operation not permitted
May 01 12:27:25 maverick-up systemd[1]: maverick-wifibc_tx.service: Main process exited, code=exited, status=1/FAILURE
May 01 12:27:25 maverick-up systemd[1]: maverick-wifibc_tx.service: Unit entered failed state.
May 01 12:27:25 maverick-up systemd[1]: maverick-wifibc_tx.service: Failed with result 'exit-code'.
May 01 12:27:39 maverick-up sudo[6968]:      mav : TTY=pts/2 ; PWD=/srv/maverick/software/maverick ; USER=root ; COMMAND=/bin/journalctl -xe

Latest self-update on rpi0w went well so I assume ordering is fixed.  Not sure how the interface errors from #770 might impact wifibc so I'll wait until you give me the all clear to proceed with testing.

OK, so it looks like #770 is not a critical dependency.  I'll give it another try today and report back.
Also want to note here that documentation of the config setting for wifibc will be important.  Once I get the prototype working I'll drop an issue over in the svpcom wifibc queue which will ask nicely for a well documented conf file.

There is no conf file for wifibc - I've created a wrapper systemctl/config file system within Maverick.  Better documentation of the various settings would be nice to have though.

Got it.  My main concern would be things like how to assign channels/freq.  That's pretty well documented in the  ezwifibroadcst config.  I am assuming since this is using UDP vs byte stream there are not as many tweaks to the other settings?

Right so there is a config file per interface in ~/config/network/interface-.conf.  The settings in there are commented out but if uncommented are supposed to be used by either normal networking or monitor/inject (wifibc) mode.  In practice it's quite difficult to get right and I'm not sure how effective they are yet.  See #606

Also I did some work on netinfo recently, so maverick netinfo should return quite a bit more info about each network interface.

Definitely want to do a complete overhaul of video including wbc for 2.0

hmm.  sorry.  not sure how i modified the milestones???  i blame one of my cats.


Invalid uleb128 decoding, idx_diffs for Encoded*

Some elements are not read correctly, causing *Invalid objects to be created for them. Sounds like a decoding issue, but after doing some digging I couldn't find the cause.
Dexdump has no issues reading that file.
Example APK is hosted on http://tepr.in/~tpr/temp/androguard_broken.apk . Here's an excerpt from androlyze shell for that file.
In [11]:  for i in d.get_classes():
for x in i.get_methods():
print "idx: %i" % x.get_method_idx_diff()
....:
idx: 4
idx: 5
idx: 7
idx:<PHONE_NUMBER>
idx: 1
idx:<PHONE_NUMBER>
idx: 1
idx: 10
idx: 13
idx: 1
idx: 3
idx:<PHONE_NUMBER>
idx:<PHONE_NUMBER>
idx: 18
idx: 19
idx: 20
idx: 21
idx: 22
idx: 23
idx: 24

probably due the the last pull request

Can you tell me the problem exactly ? Is it with the latest git version ?

It's not a new issue, but I have seen it already almost a year ago (iirc). This was tested with the latest git version, as well as one from approx. a year ago.
The problem is, that those indexes are obviously incorrect, although I'm not sure if it's the fault of DEX file here, or whether androguard reads it incorrectly. Nevertheless dexdump reads it correctly. Here's another snippet, printing out the names and descriptors:
In [6]:  for i in d.get_classes():
for x in i.get_methods():
print("%s %s" % (x.get_name(), x.get_descriptor()))
...:
 ()V
 ()V
testReflection ()V
AG:IMI:invalid_name ()AG:IMI:invalid_proto
AG:IMI:invalid_name ()AG:IMI:invalid_proto
AG:IMI:invalid_name ()AG:IMI:invalid_proto
AG:IMI:invalid_name ()AG:IMI:invalid_proto
onCreate (Landroid/os/Bundle;)V
 ()V
bM_getDefault_122817834 ()Ljava/lang/Object;
bM_valueOf_66284459 (I)Ljava/lang/Object;
AG:IMI:invalid_name ()AG:IMI:invalid_proto
AG:IMI:invalid_name ()AG:IMI:invalid_proto
send (Ljava/lang/String;)V
 ()V
 ()V
 ()V
 ()V
 ()V
 ()V

@rytilahti is it possible to reupload the APK? I would like to have a look at it!

If this issue still occurs, please reopen!


Please tag a new version (0.4.2?)

Previous version 0.4.1 is from December 11 2014.  Would you mind tagging a new version?

cc: @ejelly

@ejelly you're alive? Want to cut a release? I'll do it if I don't hear from him ...

@qvicksilver I'd be happy to give you committer/release rights if you're willing to cut us a release and help with the library. Interested? Email me dblock[at]dblock[dot]org.

https://github.com/dblock/jenkins-ansicolor-plugin/issues/57 could be a blocker before release.

Ah, only read this now, which also shows how responsive I currently am. I have to hold off on contributing for a while, because my free time remains limited for now (and in my previous job, I used the plugin as part of it, which gave me the luxury of working on the plugin during my actual day job).

@qvicksilver Want to cut a release now that we have https://github.com/dblock/jenkins-ansicolor-plugin/pull/62?

@dblock sure! All I have to do is follow the instructions?

Right. I think somewhere I have to give you access to something :) you already have commiter access to github.

As far as I can tell 0.4.2 has now been released.

GitHub has the tag:
ansicolor-0.4.2 … 801390b

It appeared in the Jenkins update center.  Well done and thank you @qvicksilver and @dblock !

Sorry closed too fast.  You might want to update the wiki page https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin
Some plugins list the changelog on the wiki page which is very handy :-)

Not sure how to make version updates stick on the wiki, the preview shows version 0.4.2 but nothing seems to happen after saving.

Seems good now. Probably a side effect due to caching.

Awesome, thanks @qvicksilver.


Feat/ts/form for new concept suggestions

Knyttet til: https://github.com/Informasjonsforvaltning/catalog-frontend/issues/173