INTERNAL ERROR: missing context with id

[christophe-ledu]

Since the version 3 ( YellowLabTools/YellowLabTools-server#6 ), I get this kind of errors :

I don't get this problem on every machines, it seems to be related to the machine performance, but I'm not sure

On the screenshot, the official image is used, to nothing more is used

[macbre]

Pinging @gmetais.

@christophe-ledu - can you share what version of phantomas you're running? I'm also not sure how the YellowLabTools-server is significant here? Are you running the phantomas container inside the "server"?

[christophe-ledu]

In this screen, I'm only running phantomas withtout YellowLabTools, and for what I know, it's the latest image from docker ( https://hub.docker.com/r/macbre/phantomas ) I didn't have the image before, so it should be the latest

This problem happen on the http://yellowlab.tools:8282 instance too (not all the times, but often)

[Fred-artwai]

Hi,
I work with Christophe: to clarify, this happens very often with certain sites, in particular https://www.lepoint.fr

[gmetais]

Hi there, sorry for the lack of response on your previous ticket Christophe.

I am experiencing the same random issue, especially when ran on an AWS Lambda. For this reason, I didn't deploy YLT3 in production (https://yellowlab.tools) yet. I have no clue for the moment and unfortunately not much time to investigate.

You're mentioning the lack of performance of the machine. That's a good start. Could it be also related to the complexity of the tested website too?

[christophe-ledu]

That's possible, that's not the only one we are testing having this issue.

For what I can tell test the same site given earlier, there is no issue with phantomas 2.6, it seems to start with 2.7.

Could it be related to the new headless mode ?

[macbre]

Could it be related to the new headless mode ?

Worth checking. I'll introduce a command line option to disable the new headless mode and fall back to the old one.

[christophe-ledu]

On our side, just commenting that headless: new line seems to fix the problem, so it's probably related