rfcs | RFCs for Cloud Native Buildpacks

I have created code with iText 7 that is able to digitally sign a given PDF with a X509 certificate that uses an ECDSA key pair. When I open this signed PDF in Acrobat Reader DC, it correctly reads it, and verifies it to be valid (meaing doc is unmodified since signing, etc etc).

However, when I try to validate this same document with iText 7, the integrity and authenticity check returns false.

Here is a sample code:

I have three types of this 414 error:
1.

I am using the experimental script setup to create a learn enviroment. I got a selfmade navigation bar with open a single component.

I am having trouble using the method. This method is described in the docs under component basics -> dynamic-components

In the Vue 3 Composition API, it works as expected:

I have a function which receives a Box and needs to convert that into an Rc to share read-only ownership within the thread.

With a Box of some T: Sized, we can do Rc::new(*my_box), but unfortunately that doesn't work for unsized trait objects.

Here's an oversimplified example which hopefully clarifies the problem:

I'm wondering how I can observe child properties from the parent component in Vue 3 using the composition api (I'm working with the experimental script setup).

I haven't wandered the path of advanced traits much, but I'm wondering if it's possible to save re-writing / copying and pasting nine functions by creating a trait which overrides just one or three functions of a more complex trait.

This was some experimenting I did this evening with serde_json's PrettyFormatter where I'd like to create a version of the PrettyFormatter that just changes how a Vec is printed.

I should note that the idea came from this answer which differs in that I'm consuming serde_json and interested in removing code duplication but likely the answer is still "not possible, check the RFC". It seems wasteful to not be able to re-use code already available.

Here's my minimum case that seems to fail:

I'm trying to implement several workflows along with Oauth2 standard. I've seen that in different RFCs the request format suggested (and the only one mentioned) is application/x-www-form-urlencoded. Since my whole application relies on application/json request formats I was wondering if the application/x-www-form-urlencoded format for Oauth2 standard is mandatory or simply a suggestion.

Since PHP7 it seems to be possible to directly call anonymous functions like this:

In Rust, you can use if let instead of match when it comes to unwrapping and directly using just a simple value.

So instead of