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
Describe the bug
RuntimeError: "unreachable" when rendering PDF with floating-point scale in WASM build
To Reproduce
Steps to reproduce the behavior:
update the scale value into a floating number in the released wasm package
start a HTTP server
load the PDF file and check the error
Expected behavior
render the PDF with the correct scale
Screenshots
System (please complete the following information):
OS: Mac
Version 15.1
Target WASM
Additional context
First of all, thank you for creating such an amazing project for PDF processing!
I encountered an issue and wanted to check if it might be specific to the WASM build. Here's the scenario:
I downloaded the release example and tried rendering a PDF with different scale values. However, when I use a floating-point number for the scale, I receive the following error:
(index):489 RuntimeError: unreachable
I’m not entirely sure if this issue is limited to the WASM build, but I tagged it as "WASM" for now as a starting point.
Thank you for your help!
The text was updated successfully, but these errors were encountered:
Describe the bug
RuntimeError: "unreachable" when rendering PDF with floating-point scale in WASM build
To Reproduce
Steps to reproduce the behavior:
Expected behavior
render the PDF with the correct scale
Screenshots
System (please complete the following information):
Additional context
First of all, thank you for creating such an amazing project for PDF processing!
I encountered an issue and wanted to check if it might be specific to the WASM build. Here's the scenario:
I downloaded the release example and tried rendering a PDF with different scale values. However, when I use a floating-point number for the scale, I receive the following error:
I’m not entirely sure if this issue is limited to the WASM build, but I tagged it as "WASM" for now as a starting point.
Thank you for your help!
The text was updated successfully, but these errors were encountered: