mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Zack TannerandGitHub
94bda4995e
When we acquire a lock on a fetch, and the fetch errors, we weren't resolving the lock. This meant a subsequent request would stall waiting to acquire a lock and prevent the page from rendering. An example of this is a fetch with force-cache in `generateMetadata` and another in the RSC where both requests encounter a fetch error. Fixes #74613
14 lines
383 B
TypeScript
14 lines
383 B
TypeScript
import { nextTestSetup } from 'e2e-utils'
|
|
|
|
describe('app-fetch-errors', () => {
|
|
const { next } = nextTestSetup({
|
|
files: __dirname,
|
|
})
|
|
|
|
it('should still successfully render when a fetch request that acquires a cache lock errors', async () => {
|
|
const browser = await next.browser('/1')
|
|
|
|
expect(await browser.elementByCss('body').text()).toBe('Hello World 1')
|
|
})
|
|
})
|