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

[14.0] stock_barcodes: regression on inventory #565

Closed
alexis-via opened this issue Dec 14, 2023 · 6 comments
Closed

[14.0] stock_barcodes: regression on inventory #565

alexis-via opened this issue Dec 14, 2023 · 6 comments
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@alexis-via
Copy link
Contributor

alexis-via commented Dec 14, 2023

The PR #560 by @dalonsod has introduced a regression: it uses the fields "user_id", "inventory_quantity_set" and "inventory_date" and on stock.quant, which exists on odoo v15 but NOT on odoo v14 !

There is the code which uses the non-existing user_id + inventory_quantity_set + fields inventory_date on stock.quant: https://github.com/OCA/stock-logistics-barcode/blob/14.0/stock_barcodes/wizard/stock_barcodes_read_inventory.py#L28

@alexis-via alexis-via added the bug label Dec 14, 2023
@alexis-via
Copy link
Contributor Author

Traceback (most recent call last):
  File "/home/alexis/new_boite/dev/14/odoo/odoo/http.py", line 652, in _handle_exception
    return super(JsonRequest, self)._handle_exception(exception)
  File "/home/alexis/new_boite/dev/14/odoo/odoo/http.py", line 317, in _handle_exception
    raise exception.with_traceback(None) from new_cause
ValueError: Invalid field stock.quant.inventory_date in leaf ('inventory_date', '<=', datetime.date(2023, 12, 14))

@dalonsod
Copy link

Ouch. It's clear we missed reviewing that option, and tests were passed anyway.

We'll take a look and solve it ASAP.

cc @ChristianSantamaria @sergio-teruel

@alexis-via
Copy link
Contributor Author

Any news ? Can I help on this regression ? I'm not very familiar with this code, but I'm ready to help !

@dalonsod
Copy link

We'll started with it, but not working yet 😞, so no PR is created yet. We'll continue with it...

@dalonsod
Copy link

@alexis-via #569

Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 30, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants