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

[18.0][MIG] delivery_carrier_label_batch #982

Closed
wants to merge 60 commits into from

Conversation

imlopes
Copy link

@imlopes imlopes commented Feb 13, 2025

No description provided.

yvaucher and others added 30 commits February 13, 2025 16:00
- change name to batch to match with change of `picking_dispatch` name to
`stock_batch_picking`
- mode description in README.rst
- move files in models and views directories
- change headers to small license header
- use api 8.0
- fix and improve tests
the field has been renamed in the base module
Probably due to usage of multiple environment and cache. datas can't be
read from shipping.label but it can be read from ir.attachment
When there is more than 1 pack in a picking, 2 or more thread worker
might be in concurrence on the same picking, which makes one of the
transaction fails, resulting in the abort of the whole label generation.

The solution implemented is to change the way of passing the tasks to
the thread workers. Instead of passing a label at a time, we pass a
group of label. A group of label actually contains all the labels to
generate for one picking.
Co-Authored-By: Alexandre Fayolle <alexandre.fayolle@camptocamp.com>
The support of picking without packages has been dropped following the RFC OCA#192

Since ffaab97 commit `base_delivery_carrier_label` force the usage of
packages.
OCA-git-bot and others added 27 commits February 13, 2025 16:00
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: delivery-carrier-12.0/delivery-carrier-12.0-delivery_carrier_label_batch
Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-12-0/delivery-carrier-12-0-delivery_carrier_label_batch/
The threading option doesn't work in test mode but was not tested
because labels were already generated in the test.
Using a condition to use different threads only when test mode
is not activated allows to test label generation.
Co-authored-by: Hai Lang <hailn@trobz.com>
Sometimes, when regenerating labels from third party API, we could not get the
new tracking references. And then as we do not purge tracking references
correctly, previous ones are kept and lead to incoherences (batch picking
tracking references emptied but labels still existing). For this we need to
manually purge references when asking for full regeneration.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: delivery-carrier-14.0/delivery-carrier-14.0-delivery_carrier_label_batch
Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-14-0/delivery-carrier-14-0-delivery_carrier_label_batch/
Currently translated at 2.8% (1 of 35 strings)

Translation: delivery-carrier-14.0/delivery-carrier-14.0-delivery_carrier_label_batch
Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-14-0/delivery-carrier-14-0-delivery_carrier_label_batch/es/
Currently translated at 100.0% (35 of 35 strings)

Translation: delivery-carrier-14.0/delivery-carrier-14.0-delivery_carrier_label_batch
Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-14-0/delivery-carrier-14-0-delivery_carrier_label_batch/es/
@imlopes imlopes force-pushed the 18.0-mig-delivery_carrier_label_batch branch from c214bce to d7c92de Compare February 13, 2025 21:16
@imlopes
Copy link
Author

imlopes commented Feb 16, 2025

Closing :
#984

@imlopes imlopes closed this Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.