Hari-Nagarajan / fairgame

Tool to help us buy hard to find items.
GNU General Public License v3.0
2.43k stars 805 forks source link

[Bug] Amazon headless does not do anything #278

Open luigi311 opened 3 years ago

luigi311 commented 3 years ago

Looking at the nvidia-bot.log the --headless flag does not progress passed

POST http://127.0.0.1:42861/session/8e03bdafa0a9d2c7aab6d15713c8169f/url {"url": "https://www.amazon.com/"}

this is tested on a item that is in stock.

luigi311 commented 3 years ago

Here is what the terminal returns

 python app.py amazon --headless --no-image
2020-11-05 15:01:04 LUIS-DESKTOP nvidia-bot[2644] INFO Initializing Apprise handler
2020-11-05 15:01:04 LUIS-DESKTOP nvidia-bot[2644] INFO Initializing other notification handlers
2020-11-05 15:01:04 LUIS-DESKTOP nvidia-bot[2644] INFO Enabled Handlers: ['Audio']

DevTools listening on ws://127.0.0.1:65011/devtools/browser/029b95c0-22f5-4ea7-b3ed-130ee666cef1
[1105/150105.327:ERROR:devtools_http_handler.cc(291)] Error writing DevTools active port to file
[1105/150105.329:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\js
[1105/150105.329:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\wasm
[1105/150105.331:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\js
[1105/150105.331:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\wasm
[1105/150105.332:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: .profile-amz\Default\Code Cache\js
[1105/150105.332:ERROR:disk_cache.cc(184)] Unable to create cache
[1105/150105.332:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: .profile-amz\Default\Code Cache\wasm
[1105/150105.333:ERROR:shader_disk_cache.cc(606)] Shader Cache Creation failed: -2
[1105/150105.336:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\js
[1105/150105.336:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\wasm
[1105/150105.337:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\js
[1105/150105.337:ERROR:simple_backend_impl.cc(81)] Failed to create directory: .profile-amz\Default\Code Cache\wasm
[1105/150105.340:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: .profile-amz\Default\Code Cache\js
[1105/150105.340:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: .profile-amz\Default\Code Cache\wasm
[1105/150105.341:ERROR:disk_cache.cc(184)] Unable to create cache
[1105/150105.342:ERROR:disk_cache.cc(184)] Unable to create cache
[1105/150105.692:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
ghost commented 3 years ago

So this appears to be something with selenium trying to launch chrome with gpu acceleration, but failing to initialize.

Looks related to #267

luigi311 commented 3 years ago

No longer running into this issue on my docker container but instead running into a timeout issue now. Looks like selenium/chromedriver/chromium are having issues talking with each other.

luigi311 commented 3 years ago

@mihaiparvu can you validate that --headless is still working. Im running into issues with chromium 83.0.4103.116 when using --headless.

paigeweber13 commented 3 years ago

I'm also interested in knowing if --headless is still supported: I'd like to run this on a raspberry pi with no display server installed

furzich2015 commented 3 years ago

@luigi311 how did you fix this problem?

luigi311 commented 3 years ago

@furzich2015 i did not solve this issue, i stopped getting that issue but i updated my entire docker image and rebased with master branch so no idea what made it progress passed that issue but i am still getting issues with it not actually opening and loading a page so it never progresses passed the login page.

furzich2015 commented 3 years ago

@luigi311 I have the same error, only on windows. Do you have any suggestions what this might be? I do not have docker