Aaron Duce comments

Results 6 comments of


                                            Aaron Duce

unstable_parseMultipartFormData nulls all non-file formdata fields

facing this issue after writing a multi handler uploadHandler. ```ts const uploadRamsHandler = unstable_composeUploadHandlers( unstable_createFileUploadHandler({ maxPartSize: 25_000_000, directory: './private/rams/' }), unstable_createMemoryUploadHandler() ); const uploadAssociationsHandler = unstable_composeUploadHandlers( unstable_createFileUploadHandler({ maxPartSize: 25_000_000, directory:...

InnoDB is not using the custom configuration file at initialisation, so initialises files with 16k page size instead of 64k page size configured then won't start.

Can I nudge this? Obviously can't restore a copy of this 64k instance without this working?

InnoDB is not using the custom configuration file at initialisation, so initialises files with 16k page size instead of 64k page size configured then won't start.

Even creating brand new db with this custom configuration file -> 16k page size not 64k as set. ![Screenshot 2023-03-07 at 08 15 57](https://user-images.githubusercontent.com/20649108/223363683-b04ffaa9-72ee-4f5a-bf4e-f8df609fe481.png)

Aaron Duce

unstable_parseMultipartFormData nulls all non-file formdata fields

InnoDB is not using the custom configuration file at initialisation, so initialises files with 16k page size instead of 64k page size configured then won't start.

InnoDB is not using the custom configuration file at initialisation, so initialises files with 16k page size instead of 64k page size configured then won't start.

Unable to issue instanceof Prisma.PrismaClientValidationError on known caught PrismaClientValidationError

Assertion Failure after reboot.

Assertion Failure after reboot.