Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FOTT bug report - UI error with some text-based PDF #990

Open
AndreaLeonangeli opened this issue Sep 1, 2021 · 0 comments
Open

FOTT bug report - UI error with some text-based PDF #990

AndreaLeonangeli opened this issue Sep 1, 2021 · 0 comments

Comments

@AndreaLeonangeli
Copy link

Describe the bug
The system does not handle properly a specific type of text-based PDF documents. Unfortunately I cannot share the document.

In the Tags Editor of the UI, the document is not loaded from an Azure Blob Storage. The thumbnail is black and keeps spinning.

In the analyze with custom model section, the UI keeps loading the file and nothing happens.

To Reproduce
Steps to reproduce the behavior:

  1. Open the analyze with custom model section.
  2. Click on 'Browse for a file' and select the PDF document.
  3. The UI keeps fetching with the spinning icon. The console shows this message
    "Warning: getOperatorList - ignoring errors during "GetOperatorList: page 0" task: "DataCloneError: Failed to execute 'postMessage' on 'DedicatedWorkerGlobalScope': function at() { [native code] } could not be cloned."

Expected behavior
The UI loads the text-based PDF document both in the tagging section and in the analyze page.

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 10 Pro, Version 21H1, Build 19043
  • Docker version
  • Browser: Microsoft Edge
  • Version: 92.0.902.84

Additional context
I tried with a different PDF of the same type and structure (created in the same way I suppose) and the problem still happens. With a completely different text-based PDF the UI works properly.
Note that the PDF that does not work with FOTT, is analyzed properly when using the Form Recognizer REST API directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant