Brett Sutton

@ohemorange thanks for the feedback. I am aware and use certbot certificates. When my code is working correctly it uses certbot certificates to parse the certificates and identify staging/production certificates....

Having production as the default is fine but staging should always be require. On Thu, 18 Feb 2021, 12:25 pm ohemorange, wrote: > Ah, I see. I don't think we...

I'm not familiar with the structural limitations of certificates but can the certificate contain a property staging=true. Then if there is a mismatch between the certbot flag and the certificate...

@osirisinferi > (…) the current method of including a string 'invalid' with the date also feels like a hack. >> 'Not sure what you mean by this, do you mean...

> Well, I'm not sure if we've even established what the "correct" solution actually is to be honest 🙂 Maybe not but my point was that what we have now...

So how does it determined that the certificate is a test certificate. On Tue, 23 Mar 2021, 4:34 am osirisinferi, ***@***.***> wrote: > Yes. I assumed it was some hack...

I've just tested using vite with chrome and chrome doesn't have the same problem. So this looks like its a vite/firefox bug.

I'm seeing the same issue with jdk 17: ```java { public List _rangesFor(VersionConstraint constraint) throws ArgumentException { if (constraint.isEmpty()) return new ArrayList(); if (constraint instanceof VersionUnion union) // this line...

I think we need to go back to conventions and what developers expect of build tools. * make * mvn * gradle * dart pub * docker build All of...

I haven't just proclaimed it, I've given concrete examples of other build tools that all conform to the convention, including Dockers own build tool. Let me repeat that: including Dockers...