Open GrandfatherJ opened 2 years ago
Yes - the error is "merely" that there is a timing/understanding issue between the tests and Chrome and sometimes the id of a node cannot be retrieved as it is zero.
I don't know what causes this, but it is a known issue and usually temporary.
if it's timing, could a wait and retry fix it?
On Mon, 16 May 2022 at 04:24, Max Maischein @.***> wrote:
Yes - the error is "merely" that there is a timing/understanding issue between the tests and Chrome and sometimes the id of a node cannot be retrieved as it is zero.
I don't know what causes this, but it is a known issue and usually temporary.
— Reply to this email directly, view it on GitHub https://github.com/Corion/WWW-Mechanize-Chrome/issues/65#issuecomment-1126973535, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJJGZ6ZMGXN5RHP6TROOZDVKEQLXANCNFSM5V7JOQQQ . You are receiving this because you authored the thread.Message ID: @.***>
cpanm --force gets the job done. Haven't tested the result yet, but will update this if I find issues over the next few days. build.log