Closed PedroCaldeira closed 1 year ago
Hi @PedroCaldeira,
I'd like to point out that we don't support proxy at the moment, and this option will be removed in the next release.
Regarding the issue, the proxy
option should be an object rather than a string. For example:
const browser = chromium.launch({
args:['ignore-certificate-errors'],
headless: false,
proxy: {
server: "someproxy",
bypass: "",
username: "",
password: "",
},
}); // Replace with a real proxy
Other than this, we need to tackle an inherent issue here. Instead of an error message, we get a panic stack trace. I'll be looking into this. Update: I've looked into this and the problem introduced in commit 2b1a852: Here, it panics with a nil context
that it gets from init()
. After recent updates, this problem has been fixed by returning errors to the mapping layer.
Brief summary
When trying out the
BrowserType.launch([options])
api with the proxy field, an error is popping up:ERRO[0000] a panic occurred during JS execution: runtime error: invalid memory address or nil pointer dereference
Not having the proxy field runs okay.
k6 version
k6 v0.44.1 ((devel), go1.20.4, darwin/amd64)
OS
MacOS 13.4 Intel
Docker version and image (if applicable)
No response
Steps to reproduce the problem
Run the given code sample via cli:
Expected behaviour
Expected the test to run normally, using the proxy given on the browser.
Actual behaviour
Get the given stack trace: