Oleg Pudeyev
Oleg Pudeyev
I can certainly leave this PR until the redesign, but I am having trouble understanding the following: > I think the key consideration is that ulimit values are already set...
@skerschb Could you please elaborate on why 128000 was insufficient and 135000 is? https://jira.mongodb.org/browse/DOCS-11161 does not appear to provide any help with this.
Suggest closing per https://github.com/mongodb/docs/pull/3168.
I am working on implementing OCSP stapling.
> but we can't fix it What is preventing adding new methods that raise exceptions?
I am happy to contribute an implementation. I don't understand what the conclusion/decision is in this ticket, if that is clarified I can look into typing the code up.
Resources used to implement: - https://www.openssl.org/docs/man1.1.0/man3/SSL_set_tlsext_status_type.html - https://stackoverflow.com/questions/9607516/openssl-certificate-revocation-check-in-client-program-using-ocsp-stapling - https://unmitigatedrisk.com/?p=100 I requested improved diagnostics from openssl in https://github.com/openssl/openssl/issues/12735.
Fixes https://github.com/ruby/openssl/issues/295.
FYI I have a project that uses Mongoid 7.1.2 and mongoid-history 0.8.2, I don't think I *read* history in any capacity but at least everything loads and I assume writes.
#21 implements manual grouping of examples.