You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed instructions in documentation written for my React-PDF version
I have checked if this bug is not already reported
I have checked if an issue is not listed in Known issues
If I have a problem with PDF rendering, I checked if my PDF renders properly in PDF.js demo
Description
I'm currently generating large documents on the server and I'm embedding images from a blob storage (Vercel blob).
When lots of images are present, I can see some of the images on the later part of the document being dropped (appearing as empty) and several of the following errors in the log request to https://....png failed, reason: (with the reason being actually empty).
I've tried to filter out the input to generate only a subset of the document and all the images (including the one that are dropped when creating the full document) are properly included.
I wonder if this may be down to to the number of asset requests that are triggered at the same time, assuming these all happen in parallel, but I'm just guessing.
To clarify further I'm using renderToStream to generate my output and subsequently store this on a file.
Steps to reproduce
I don't have a replicable example I'm afraid as I cannot just publish the same code and data I'm using, and recreating a similar one from scratch is going to be non-trivial. I can share code snippets and other info if needed.
Expected behavior
I expect all assets to be retrieved correctly.
Or to be able to configure the fetching process to avoid the receiver being overwhelmed.
Alternatively a way to split the document generation in chuncks would also work.
Actual behavior
Fetching of some of the assets fails during the rending process.
Additional information
No response
Environment
Browser (if applicable):
React-PDF version:
React version:
Bundler name and version (if applicable):
The text was updated successfully, but these errors were encountered:
Mirthis
changed the title
Asset fetching fail for some assets, when many assets are present
Asset fetching fails for some assets, when many assets are present
Oct 3, 2024
Before you start - checklist
Description
I'm currently generating large documents on the server and I'm embedding images from a blob storage (Vercel blob).
When lots of images are present, I can see some of the images on the later part of the document being dropped (appearing as empty) and several of the following errors in the log
request to https://....png failed, reason:
(with the reason being actually empty).I've tried to filter out the input to generate only a subset of the document and all the images (including the one that are dropped when creating the full document) are properly included.
I wonder if this may be down to to the number of asset requests that are triggered at the same time, assuming these all happen in parallel, but I'm just guessing.
To clarify further I'm using
renderToStream
to generate my output and subsequently store this on a file.Steps to reproduce
I don't have a replicable example I'm afraid as I cannot just publish the same code and data I'm using, and recreating a similar one from scratch is going to be non-trivial. I can share code snippets and other info if needed.
Expected behavior
I expect all assets to be retrieved correctly.
Or to be able to configure the fetching process to avoid the receiver being overwhelmed.
Alternatively a way to split the document generation in chuncks would also work.
Actual behavior
Fetching of some of the assets fails during the rending process.
Additional information
No response
Environment
The text was updated successfully, but these errors were encountered: