Ryo Kajiwara

:+1: 本の表記のままではエラーを得ました。 再現コードは以下です: ```cpp #include "../all.h" int main(){ std::allocator a; using traits = std::allocator_traits; std::string * p = traits::allocate(a, 1); std::string * s = traits::construct(a, p, "hello"); // traits::construct(a, p,...

I do recognize that there are issues for newer versions of mongodb, but its fix is not trivial, and I cannot work on fixing it right away. As such, please...

Fourthed. From reading #167, this issue seems to stem from conflicting understanding where: * the user of the gem assumes that metadata persister / metadata getter is some kind of...

I have checked with our team that we can figure out a workaround to our project's specific problem, so we can wait for the cowboy update. Meanwhile, we found out...

Looks like it's being worked on @ https://github.com/ruby/openssl/pull/555 . As for now, workarounds can be found here: - https://github.com/ruby/openssl/issues/498 - https://github.com/ruby/openssl/pull/555#issuecomment-1440079803

@ryosk7 Sorry for the late response... Yes, I think writing `lwipopts.h` options separately for each gem is the better way to go. It seems that `picoruby-mqtt` does not depend on...

（https://github.com/picoruby/picoruby/pull/190#issuecomment-3187824561 のコメントの意図がlost in translation気味な気がしてきたので日本語で意図を説明します。(EN: This comment is a disambiguation of the linked comment in Japanese)） 本pull requestとしては動作はokという理解をしており、まず機能のリリースをしてMQTTをユーザーに使ってもらい、それとは別に `picoruby-net` から `lwipopts.h` のMQTTに必要な部分だけ分離するというのは別pull requestでやってもよいのでは、というのが該当コメントの主張です。よって本pull requestの範囲としては完了しておりmergeしてもよいのでは、と考えていますが、いかがでしょう？ > @hasumikin