Naotoshi Seo

Results 43 issues of Naotoshi Seo

``` ThreadError Attempt to unlock a mutex which is not locked lib/vertica/connection.rb:298:in `unlock' lib/vertica/connection.rb:298:in `process_message' lib/vertica/connection.rb:398:in `startup_connection' lib/vertica/connection.rb:446:in `boot_connection' lib/vertica/connection.rb:329:in `run_in_mutex' lib/vertica/connection.rb:146:in `query' ``` https://github.com/wvanbergen/vertica/blob/200d317e64130ce333c7c44c6362618858ccd3cc/lib/vertica/connection.rb#L298 `@mutex.unlock if @mutex.locked?` correctly or...

The sigdump often (about 50%?) does not show `all objects` section. The output of sigdump stops at `Built-in objects:` section as below: ``` /xxxxxx/shared/bundle/ruby/2.2.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in `block in initialize' /xxxxxx/shared/bundle/ruby/2.2.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `block in...

I got an error like ``` /Users/naotoshi.seo/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/parallel-rspec-c95d59273b0f/lib/rspec/parallel/worker.rb:74:in `load': no implicit conversion of nil into String (TypeError) from /Users/naotoshi.seo/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/parallel-rspec-c95d59273b0f/lib/rspec/parallel/worker.rb:74:in `block in each' from /Users/naotoshi.seo/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/parallel-rspec-c95d59273b0f/lib/rspec/parallel/worker.rb:60:in `loop' from /Users/naotoshi.seo/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/parallel-rspec-c95d59273b0f/lib/rspec/parallel/worker.rb:60:in `each' ```

https://bugs.ruby-lang.org/issues/13849

which allows us to directly read data from bigquery storage, results in less expensive (about 1/5 compared with select * from table)

Some of our workflows require additional parameters. For such workflows, we can not use the `RUN` button on Web UI, currently. It would be nice to pop-up and require some...

feature_request

From https://github.com/treasure-data/digdag/pull/1048#issuecomment-476484645 With #1048, I introduced `digdag server --disable-scheduler` which does not start any schedules registered. But, it is somewhat misleading because it allows registering schedules dig files with ```...

feature_request