PG screenshot rendering black in the docs

Questions
1

Hello @RaananW !
This has happened. All the other PG sreenshots are OK except this one. Can I do something about it?

image

2

Now I can see why:

screenshot created for #H1LRZ3#9 --- no it's not 
Warning: data for page "/[...id]" (path "/features/featuresDeepDive/mesh/creation/param/greased_line") is 136 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
main getStaticPages
error pg #H1LRZ3#113
screenshot created for #H1LRZ3#115 --- no it's not
Warning: data for page "/[...id]" (path "/features/featuresDeepDive/mesh/creation/param/greased_line") is 140 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.

Can we do something without the need to divide the page to multiple pages? The docs are reffering in multiple location as ‘the PG below’ and it’s quite a monolith and I am out of steam to check and rewrite the whole thing now… :frowning:

EDIT: We can, question is whether you are willing to… :face_with_monocle:
I found this: large-page-data | Next.js

3

i am taking care of that now. the screenshots are being done using the stable version, and it wasn’t deployed until now.

a few minutes and the screenshots will be there :slight_smile:

4

I don’t mean this:

image
image271×785 17 KB

but this:

image
image307×1229 96.8 KB

5

taking care of that as well :slight_smile:

6

Fine :slight_smile: Just be aware that I’ve just added docs for the GetPointsFromText function and it started to happen afterwards :see_no_evil:

7

Am I overworried? :smiley:

8

yes! and it’s perfectly fine :slight_smile:

1 Like
9

should be fine now, by the way

1 Like
10

Sorry:
image

image
image309×508 6.18 KB

11

ready in 7 minutes :slight_smile:

12

LOL…

1 Like
13

Can I ask is the PG screenshots creation an automatic process upon merging or you have to trigger it manually? There are two new PGs without screenshots again in the docs.

Thanks!

14

When you test locally a test that doesn’t have an image, it normally creates it automatically. At least that’s what happens for me.

1 Like
15

Just my two-cents here but may be is because the PG was not working at the time of merge.
The new drawtext PG is non-working at this moment (and the other is working, at least now but may be wasn’t at the time or takes a bit too long to load?). Though, I suppose the thumbnail cannot be generated from a non-working PG, can it?

16

It absolutely make sense and I was thinking like this too, but working PG, no thumb:

image

17

I know. But it takes sometime after loading before the mesh is displayed (understandable, from the quality of what I can see here :smiling_face_with_three_hearts:). Yet, may be (and then just, may be) may be the screenshot function kicks in before it’s ready?

18

I think there is a delay set, because the sphere demo is starting quite slower than the other PGs and the thumb is there :wink:

19

As I said, just my two cents. I hope it will not worry you all too much. Isn’t it time for you to prepare your luggage and make ready for your holidays? :beach_umbrella: :sun_with_face: :sunglasses:

1 Like
20

My mistake, I’m talking about generating the image for a visualization test, not for a PG inside a documentation page!

What I do when a PG I link to a doc page relies on features that are only available on my local computer, is to update the base url used by the code that generates the image. This is located in the lib/frontendUtils/frontendTools.ts file, line 8: replace https://playground.babylonjs.com/ with http://localhost:1338/.