Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using with undetected Chromedriver

See original GitHub issue

it works, but I get thousends of DEBUG loggings if I import the v2 over selenium-wire package Direct from uc, where I used before, there are no debug loggs How can I disable this please? I couldn`t find any information about…

Issue Analytics

State:
Created 2 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

petzi75commented, Jul 20, 2021

I`ve added this command now: logging.getLogger(‘seleniumwire’).level = logging.INFO reduces the amount a little bit - so no DEBUGS with 127.0… are listening anymore.

but also hundreds per each second like this: 2021-07-19 21:44:55 DEBUG: Resizing header table to 65536 from 4096 2021-07-19 21:44:55 DEBUG: Decoded 2, consumed 1 bytes 2021-07-19 21:44:55 DEBUG: Decoded (b’:method’, b’POST’), consumed 1 2021-07-19 21:44:55 DEBUG: Decoded 2, consumed 1 bytes 2021-07-19 21:44:55 DEBUG: Decoded (b’:method’, b’GET’), consumed 1 2021-07-19 21:44:55 DEBUG: Decoded 1, consumed 1 bytes 2021-07-19 21:44:55 DEBUG: Decoded (b’:method’, b’GET’), consumed 1 2021-07-19 21:44:55 DEBUG: Adding (b’origin’, b’https://www.google.com’) to the header table, sensitive:False, huffman:True 2021-07-19 21:44:55 DEBUG: Encoding 5 with 7 bits 2021-07-19 21:44:55 DEBUG: Encoding 16 with 7 bits 2021-07-19 21:44:55 DEBUG: Adding (b’content-type’, b’application/x-www-form-urlencoded’) to the header table, sensitive:False, huffman:True 2021-07-19 21:44:55 DEBUG: Encoding 31 with 6 bits 2021-07-19 21:44:55 DEBUG: Encoding 24 with 7 bits 2021-07-19 21:44:55 DEBUG: Adding (b’sec-fetch-site’, b’none’) to the header table, sensitive:False, huffman:True 2021-07-19 21:44:55 DEBUG: Encoding 10 with 7 bits 2021-07-19 21:44:55 DEBUG: Encoding 3 with 7 bits

0reactions

wkeelingcommented, Aug 13, 2021

The log messages are coming out of the hpack library which is used in the background for encoding and decoding HTTP/2 data. The messages are debug level, so something in the script/application must have initialised logging at DEBUG level for these to show up. The messages can be silenced by lowering the log level to INFO or lower for just ‘hpack’ or the whole script/application (as @HMaker suggests). Alternatively, you can disable HTTP/2 by passing mitm_http2: False in your seleniumwire_options, but reducing the log level would be the better approach.

Top Results From Across the Web

GitHub - ultrafunkamsterdam/undetected-chromedriver

Optimized Selenium Chromedriver patch which does not trigger anti-bot services like Distill Network / Imperva / DataDome / Botprotect.io Automatically downloads ...

undetected_chromedriver - undetected-chromedriver · PyPI

selenium.webdriver.Chrome replacement with focus on stealth. not triggered by Distil / CloudFlare / Imperva / DataDome / hCaptcha and such.

Undetected ChromeDriver: Stay Below the Radar

undetected -chromedriver ) Python package is a patched version of ChromeDriver which avoids triggering a selection of anti-bot services, allowing ...

Undetected Chromedriver not loading correctly - Stack Overflow

You can use the following solution: Code Block: import undetected_chromedriver as uc from selenium import webdriver options = webdriver.

How to Bypass Selenium Detection using Python - CodeSpeedy

The above-discussed problems can be bypassed using another web-driver library which is the undetected chrome module. Installation of undetected-chromedriver.