Running image export bug fixed

[WhiteBlackGoose]

The issue is that when rendering an image it fails to start chromium browser on Linux

[WhiteBlackGoose]

Why 😢 . It produces the same image, but different string, varying in character 1002. The CI is on ubuntu 22.04, just like my machine...

[kMutagene]

Why 😢 . It produces the same image, but different string, varying in character 1002. The CI is on ubuntu 22.04, just like my machine...

Yeah that's the exact reason why i gave up on those tests and just started to skip them, the exact string does not seem to be deterministic (although it's kinda strange)

[kMutagene]

Regarding the --no-sandbox thing - There is already a mutable variable exposed where you should be able to set this:

Plotly.NET/src/Plotly.NET.ImageExport/PuppeteerSharpRenderer.fs

Line 14 in 9e9b31c

let mutable launchOptions = LaunchOptions()

so you should be able to just set the flag for your environment

[WhiteBlackGoose]

Should it be linux-only?

[kMutagene]

i do not think we need to hard-code this at all. I have used this lib on linux without setting this. as we expose the launch settings, this can be set by the user if needed.

[WhiteBlackGoose]

That's imo too obscure. I spent some time investigating it, and we leave it as it, not working for some linux users?

[kMutagene]

is this on the contrary guaranteed to work everywhere else where it wasn't needed before? if so, i guess theres no harm

[WhiteBlackGoose]

Can't say for sure. Windows and Linux tests pass though. Is there some reason why we don't have those for MacOS btw?

(also I can set this option only for Linux platform, this is no problem)