食品サンプルの試食会に行ってはしゃいでいたら元同僚からたしなめられちゃう夢を見てました。味はおいしかったので、二度寝しよう。
食品サンプルの試食会に行ってはしゃいでいたら元同僚からたしなめられちゃう夢を見てました。味はおいしかったので、二度寝しよう。
仕事しろ←
8c44b723b (upstream/main) Change confirmations controller to redirect to / for approved users (#16151)
09bb92875 Bump mini-css-extract-plugin from 1.5.0 to 1.6.0 (#16150)
8a33b7ac4 Bump @babel/preset-env from 7.13.15 to 7.14.0 (#16145)
c35a6b9e0 fix component name (#16138)
b75ecb083 Bump @babel/runtime from 7.13.17 to 7.14.0 (#16148)
970ffd8d1 Bump aws-sdk-s3 from 1.93.1 to 1.94.0 (#16143)
c35befb3e Bump @babel/core from 7.13.16 to 7.14.0 (#16141)
bcf63e6e2 Bump sass from 1.32.11 to 1.32.12 (#16142)
a2b3a5f42 Bump marky from 1.2.1 to 1.2.2 (#16147)
60446ddd4 Bump sidekiq-unique-jobs from 7.0.8 to 7.0.9 (#16139)
\Master?/ \ますたー/
Merged tootsuite/mastodon at 8c44b723bb7505eb5923019b454ce9abd7ea59c0.
Bug #17781: Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang - Ruby master - Ruby Issue Tracking System
https://bugs.ruby-lang.org/issues/17781
Sidekiqを長時間走らせておくと処理が止まる原因はこれかもわね…
@Gargron I've just noticed this Ruby's bug in a PR to a work related code, while I personally haven't been able to reproduce Sidekiq hanging after a while as Heroku restarts processes every 24 hours.
not reproducible on:
- ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux-musl] (ruby:2.7.2-alpine docker image)
- ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux]
reproducible on:
- ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux-musl] (ruby:2.7.3-alpine docker image)
- ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]
- ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
- ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]
オイゲンさんからお返事いただいてスロットルがかかった(左上の赤)んだけどRedisのメモリ(左下)を眺めるとまだ緩められそうねと思ったけど今回は応答時間(右上)がダメだったね
WARN: Redis::CommandError: ERR max number of clients reached
ナンデナンデ
WARN: Redis::CommandError: ERR max number of clients reached
ナンデナンデ
Puma+Sidekiq側で取りすぎてるかー
20:52:07: WARN Starting streaming API server master with 3 workers
20:52:07: WARN Starting worker 1
20:52:07: WARN Worker 1 now listening on 0.0.0.0:15885
20:52:07: WARN Starting worker 2
20:52:07: WARN Starting worker 3
20:52:07: WARN Worker 2 now listening on 0.0.0.0:15885
20:52:07: WARN Worker 3 now listening on 0.0.0.0:15885
20:52:07: ERR! ReplyError: ERR max number of clients reached
20:52:07: WARN Worker 3 exiting
20:52:07: WARN Starting worker 4
20:52:07: WARN Worker 4 now listening on 0.0.0.0:15885
キレの良さ
PPAP *INDIAN VERSION* (Pen Pineapple Apple Pen) - Live Banned | Awez Darbar Choreography
https://youtu.be/TPFJGIXXeq0
@Gargron @spla Yep. Reproduced locally on Ubuntu 20.04 and ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]
$ ruby /tmp/test.rb
Ran 65536 times
and top shows 99-100 %CPU for the ruby.
Also on a Hobby dyno on Heroku (waiting for a few minutes):
$ heroku run bash
~ $ which ruby
/app/bin/ruby
~ $ ruby --version
ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]
~ $ cat <<_END > test.rb
> require 'resolv'
> 65536.times { Resolv::DNS.new.getresource('www.example.net', Resolv::DNS::Resource::IN::A) }
> puts "Ran 65536 times"
> Resolv::DNS.new.getresource('www.example.net', Resolv::DNS::Resource::IN::A)
> puts "Ran 65537 times"
> _END
~ $ ruby test.rb
Ran 65536 times
^Z
[1]+ Stopped ruby test.rb
~ $ bg
[1]+ ruby test.rb &
~ $ top
:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11 u6876 20 0 93216 34284 6100 R 99.7 0.1 1:59.79 ruby
:
https://bugs.ruby-lang.org/issues/17781 の件、Gemfileに
gem "resolv", "< 0.2"
みたいにしておくとなおるっぽいんだけどなぜなんだぜ。あー、Rubyに添付されてるライブラリよりもBundlerの入れたやつを先に見に行くんだ
$ bundle exec ruby -rpp -e 'pp $:'
["/home/zunda/.rbenv/versions/2.7.3/lib/ruby/gems/2.7.0/gems/bundler-2.2.15/lib",
"/home/zunda/src/local/ruby-resolv/vendor/bundle/ruby/2.7.0/gems/resolv-0.2.0/lib",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/gems/2.7.0/gems/bundler-2.2.15/lib/gems/bundler-2.2.15/lib",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/site_ruby/2.7.0",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/site_ruby/2.7.0/x86_64-linux",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/site_ruby",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/vendor_ruby/2.7.0",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/vendor_ruby/2.7.0/x86_64-linux",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/vendor_ruby",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/2.7.0",
"/home/zunda/.rbenv/versions/2.7.3/lib/ruby/2.7.0/x86_64-linux"]
2週間に1度tootctl media removeするようにしたら弊ぼっちのメディアファイルのS3代むっちゃ安くなったよ!!やっぱり容量が効くんだねえ。