Stefan Zabka
Stefan Zabka
I don't think this is related to this issue, or if it is then it's related via a common root cause. This log message only says that processing the request...
Could you try just disabling the callstack Instrument and see if that also resolves the problem? The callstack Instrument messes with Firefox internals, so I'd think it's more likely to...
Thank you for doing this investigation!
@gunesacar I'm sorry, I don't quite understand which side you are arguing for at the moment? Do you think types make it easier to work with the code base or...
Coming back to this I have a couple of thoughts: Our target audience aren't developers/software engineers but researchers, this means the barriers both to modifying existing code and adding new...
Looking back at this from a simplifying lense for long-term maintainability: - merge the two extension folders - keep TS around - write documentation for implementing custom instrumentation - maybe...
https://github.com/mozilla/OpenWPM/blob/master/automation/DeployBrowsers/configure_firefox.py#L150 The fix is deployed but we need tests for it.
Would you mind us copying that page into our test pages, since we have set the explicit goal of being able to run the tests without an internet connection?
When exploring the issue in previous crawls we didn't observe any container being shut down in such a manner.
To save time during shutdown the following steps should be followed: - No save_record task should be awaited - All currently not finalized visit_ids should be marked as unfinished -...