-
-
Notifications
You must be signed in to change notification settings - Fork 385
[18.0][MIG] delivery_carrier_label_batch: Migration to 18.0 #984
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
base: 18.0
Are you sure you want to change the base?
[18.0][MIG] delivery_carrier_label_batch: Migration to 18.0 #984
Conversation
The tests are failing because of the issue I've mentioned in this PR ( |
/ocabot migration delivery_carrier_label_batch |
a17288a
to
dd119da
Compare
ca31b7c
to
e3888d0
Compare
e3888d0
to
823ed3d
Compare
|
@StephaneMangin if the field |
af1f057
to
3a334de
Compare
NOTE for reviewers |
45402db
to
f9dd62d
Compare
f9dd62d
to
41e34c7
Compare
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/
a7620be
to
b73431c
Compare
b73431c
to
adba048
Compare
Hello @StephaneMangin , I'm fine, thanks, hope you're too 😄 |
Yes that's it. Thanks |
[EDIT] Re-added here Hello, the commit mentioned in my previous message disappeared, probably during a force-push 🤔 Please try to keep it during next force-push 😉 |
Sorry about it. It’s definitely accidentally. I’ll be more attentive. Sorry
again
пт, 13 черв. 2025 р. о 17:43 Camille Morand ***@***.***> пише:
… *Camille0907* left a comment (OCA/delivery-carrier#984)
<#984 (comment)>
FTR the force-push made today adds this commit
<2cf903e>
to fix an assignation to a field that doesn't exist (anymore ?)
Hello, the commit mentioned in my previous message disappeared, probably
during a force-push 🤔
I'm about to re-add it
Please try to keep it during next force-push 😉
—
Reply to this email directly, view it on GitHub
<#984 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG6ZRRXGU2EG4ECZDPP5QXT3DLPQJAVCNFSM6AAAAABXEHNPBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZQGYZDKNJXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…er_code` This line has been added by OCA@3b0232d but it looks like the field carrier_code has never been added to the model (or at least it has never been merged in the OCA repo?), thus we get following error when updating the ``carrier_id``: ``` [...] File "/odoo/src/addons/web/models/models.py", line 1005, in onchange record._apply_onchange_methods(field_name, result) File "/odoo/src/odoo/models.py", line 7364, in _apply_onchange_methods res = method(self) ^^^^^^^^^^^^ File "/odoo/external-src/delivery-carrier/delivery_carrier_label_batch/models/stock_batch_picking.py", line 61, in onchange_carrier_id self.carrier_code = self.carrier_id.code ^^^^^^^^^^^^^^^^^ AttributeError: 'stock.picking.batch' object has no attribute 'carrier_code' The above server error caused the following client error: RPC_ERROR: Odoo Server Error RPC_ERROR at makeErrorFromResponse (http://localhost:8069/web/assets/e5ed061/web.assets_web.min.js:3144:163) at XMLHttpRequest.<anonymous> (http://localhost:8069/web/assets/e5ed061/web.assets_web.min.js:3149:13) ```
c2868d9
to
f358f74
Compare
… by ``UserError.args[0]`` In the label generation, when getting an error, we were using its ``name``, however, this is deprecated since a while and as been removed in odoo/odoo@d200dcf. We should use ``args[0]`` instead.
f358f74
to
99c171c
Compare
Hello, my new force-push is to add another commit: f0f852e It fixes a traceback appearing when we manage errors happening during label generation We might want to squash it with the migration commit ? |
… return ``stock.move.line`` records instead of an Iterator All calls to this method expect ``stock.move.line`` records.
Regenerating the carrier labels would crash with a Concurent Update error. We use a new cursor for tracking reference purge and avoid concurrent update when the labels regeneration also updates that field in a separate cursor afterwards: this ensures that the purge is committed before the transactions created by the threads also update and commit their own changes.
Don't spawn more threads than needed: if there are fewer groups to process than the configured max number of threads, only start the specified number of threads.
@yankinmax @Camille0907 I just pushed 2 new commits on this PR |
Thanks @gurneyalex |
) | ||
raise exceptions.UserError(msg) | ||
|
||
def action_generate_labels(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason, the labels generated aren't ordered as expected.
Does anyone using this module have the same issue?
Depends on: