Ensure that PDFDocument.documentInfo doesn't fail during document load, when the entire XRef table hasn't been fetched yet (issue 8180)

[Snuffleupagus]

Similar to other try-catch statements in /core code, we must re-throw MissingDataException to prevent issues with missing data during document loading.
Note that I'm not sure if/how we can test this, which is why the patch doesn't include any test(s).

Fixes #8180.

@Rob--W Thank you for helping with debugging this in #8180 (comment); do you have time to review the patch?

[Rob--W]

That was quick, thanks for the patch!

To create a unit test for it, you could try to mock the network component and deliberately send partial data. Do you want to add the test, or should I merge the PR after manual verification?

[Snuffleupagus]

To create a unit test for it, you could try to mock the network component and deliberately send partial data. Do you want to add the test, or should I merge the PR after manual verification?

Unfortunately I won't have time to try and write a unit-test for this right now, so in the interest of getting this long-standing issue resolved it's probably better to just test manually for now (and we should at least run the unit-tests as well).

/botio unittest

[pdfjsbot]

From: Bot.io (Linux)

---

Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://107.21.233.14:8877/89517c8637d8cf8/output.txt

[pdfjsbot]

From: Bot.io (Windows)

---

Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.215.176.217:8877/553f11a4354657c/output.txt

[pdfjsbot]

From: Bot.io (Linux)

---

Success

Full output at http://107.21.233.14:8877/89517c8637d8cf8/output.txt

Total script time: 2.40 mins

• Unit Tests: Passed

[pdfjsbot]

From: Bot.io (Windows)

---

Success

Full output at http://54.215.176.217:8877/553f11a4354657c/output.txt

Total script time: 5.78 mins

• Unit Tests: Passed

[Rob--W]

Verified by applying this patch to the project from #8180 and confirming that the printed information is complete.

[Rob--W]

To create a unit test for it, you could try to mock the network component and deliberately send partial data. Do you want to add the test, or should I merge the PR after manual verification?

Unfortunately I won't have time to try and write a unit-test for this right now, so in the interest of getting this long-standing issue resolved it's probably better to just test manually for now (and we should at least run the unit-tests as well).

Fair enough, thanks for taking your time to write the patch in the first place.