Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Failed to set special attribute [kueche_esszimmer.color_s] #281

Open
euberdeveloper opened this issue Mar 22, 2024 · 10 comments
Open
Labels
bug Something isn't working

Comments

@euberdeveloper
Copy link

✔️ Expected Behaviour

It whould work

🐞 Actual Behaviour

It gives the following error: TimeoutError: Failed to set special attribute [kueche_esszimmer.color_s]

📋 Steps to Reproduce

active: true
type: OFFER
title: XXX
description: XXX
category: 80l16387/86l16387
special_attributes:
  kueche_esszimmer.color_s: sonstige
  kueche_esszimmer.art_s: geschirr
  kueche_esszimmer.condition_s: ok
price: 7
price_type: NEGOTIABLE
shipping_type: NOT_APPLICABLE
shipping_costs:
shipping_options:
sell_directly:
images:
  - ad_yyy__img1.jpg
contact:
  zipcode: 'XXX'
  name: XXX
  street:
  phone:
republication_interval: 3
id: XXX
created_on: '2024-02-16T00:00:00'
updated_on:

📺 What browsers are you seeing the problem on? (if applicable)

No response

💻 What operating systems are you seeing the problem on? (if applicable)

No response

📃 Relevant log output (if applicable)

[INFO] Deleting ad 'YYY' if already present...
[INFO]  ... pausing for 1954 ms ...
[INFO] Publishing ad 'YYY'...
[INFO]  ... pausing for 2225 ms ...
[INFO]  ... pausing for 1690 ms ...
[INFO]  ... pausing for 1796 ms ...
[INFO]  ... pausing for 2484 ms ...
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
args ({'code': -32000, 'message': 'Invalid search result range'},) kwargs {}
args ({'code': -32000, 'message': "DOM agent hasn't been enabled"},) kwargs {}
[ERROR] TimeoutError: Failed to set special attribute [kueche_esszimmer.color_s]
[73099] Failed to execute script '__main__' due to unhandled exception!
successfully removed temp profile /home/XXX/.config/google-chrome

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct
@euberdeveloper euberdeveloper added the bug Something isn't working label Mar 22, 2024
@euberdeveloper
Copy link
Author

It actually does not work with all my adds, another example: TimeoutError: Failed to set special attribute [kleidung_damen.brand_s]

@euberdeveloper
Copy link
Author

euberdeveloper commented Mar 22, 2024

It is also very nerving, because it removes the ad without publishing it

@euberdeveloper euberdeveloper changed the title [BUG] TimeoutError: Failed to set special attribute [kueche_esszimmer.color_s] [BUG] Failed to set special attribute [kueche_esszimmer.color_s] Mar 22, 2024
@PlanetDyna
Copy link

I get a similar error when publishing a vehicle.

2024-03-23 16:46:19,952 [ERROR] TimeoutError: Failed to set special attribute [autos.ez_i]

@euberdeveloper
Copy link
Author

Hallo, gibt est Neuigkeiten? Der Bot ist nicht mehr benutzbar

@TylonHH
Copy link

TylonHH commented Apr 21, 2024

Also with [ERROR] TimeoutError: Failed to set special attribute [spielzeug.condition_s]

What I recognized: while publishining, the category is not choosen. This causes this ERROR.
The Bot click on category and then clicks on "continue/weiter" without selecting a category.

@TylonHH
Copy link

TylonHH commented Apr 21, 2024

What I found out:
In my yaml of ad there was the category set to: 17l21871/23l21871
When I check online the link to the category it says: 17/23/gesellschaftsspiele
So I replaced this in my yaml and this worked.

Seems the links to the categories have to be updated

@Airwave1981
Copy link
Contributor

Hi all,

facing the same issue.
Seems that this only occurs on number fields?

Eg. have it on:
autos.km_i: '30000'
autos.ezm_i: '6'
autos.ez_i: '2022'
autos.power_i: '136'

Lists are working.

@TylonHH
Copy link

TylonHH commented May 24, 2024

What I found out: In my yaml of ad there was the category set to: 17l21871/23l21871 When I check online the link to the category it says: 17/23/gesellschaftsspiele So I replaced this in my yaml and this worked.

Seems the links to the categories have to be updated

conclusion:
while downloading an ad the category is red to 161l463/225l463. When I wanna (re)publish this ad I need this 161/225/festplatten_laufwerke.
So do we need a mapping table? Or the logic to read the category while saving have to be changed. When I look into the sourcecode I also found this

dimensions: {"dimension1":"sVIP","dimension2":"161","dimension3":"225","dimension4":"festplatten_laufwerke","dimension6":"408","dimension7":"463", [...]

@Airwave1981
Copy link
Contributor

So I have the same issue with correct current category:

e.g.: category: 210/216/opel/corsa/

and issue on

autos.km_i: '30000'
autos.ezm_i: '6'
autos.ez_i: '2022'
autos.power_i: '136'

@provinzio
Copy link
Contributor

Does this PR solves your problem? #308

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

5 participants