Open Manestricker opened 1 month ago
The goal here is to connect to an already running instance of chrome by creating a ChromeRemote browser object, creating a new Chromote object with this browser, then creating a ChromoteSession with the parent as this Chromote object.
a <- ChromeRemote$new(host="localhost", port=9111) #creates a remote browser
bWindow <- Chromote$new(browser = a) #doesn't work because process is null
rider <- ChromoteSession$new(parent = set_default_chromote_object(bWindow))
I'm encountering the same issue when I use a custom container powered by Apptainer to launch a chrome process via the {processx}
package and trying to get the ChromeRemote
session to connect to that existing process. There was no issues with this workflow in version 0.1.2
(I am running version 0.3.1
currently).
Can you share any kind of reprex @rpodcast?
A browser object created using
a <- ChromeRemote$new(host="localhost", port=9222)
is unable to calla$is_alive()
. From what I understand, this is because the process is never set which results inError in a$is_alive() : attempt to apply non-function
as there is now process to call on.