Arian Joyandeh

I had the same problem: Changing `` to `` fixed it for me.

@marabesi you linked the testing example that is part of the tests for ChocolateBars from the [paragraph 2.6 property based testing](https://sttp.site/chapters/testing-techniques/property-based-testing.html), not of the boundary testing I was looking for....

Another option, is to use use [next-intl without i18n-routing](https://next-intl.dev/docs/getting-started/app-router/without-i18n-routing). By using cookie/database-based locales you can keep your middleware clean and avoid clashes between next-intl middleware and multi-tenant middleware.

> > Another option, is to use use [next-intl without i18n-routing](https://next-intl.dev/docs/getting-started/app-router/without-i18n-routing). By using cookie/database-based locales you can keep your middleware clean and avoid clashes between next-intl middleware and multi-tenant middleware....

Any update on this bug?

Thanks Gustavo for the code! I updated it so that the first page does not have the top padding. ```ts import type ReactPDF from "@react-pdf/renderer"; import { View } from...

It seems that the column visibility is being persisted, but it's tied to an evalId. https://github.com/promptfoo/promptfoo/blob/0534451f99e9c324ff3105ee9bd62e6e0c931e19/src/app/src/pages/eval/components/store.ts#L99

+1