[16.0][FIX] stock_release_channel: do not write records in _compute_picking_count
#969
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…unt' This is triggering concurrency updates on release channel records while reading them in the dashboard (updating `write_date` + `write_uid` fields).
|
Hi @mt-software-de, @jbaudoux, |
gurneyalex
approved these changes
Jan 9, 2025
mt-software-de
approved these changes
Jan 9, 2025
santostelmo
approved these changes
Jan 9, 2025
|
/ocabot merge patch |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
jbaudoux
approved these changes
Jan 9, 2025
There was a problem hiding this comment.
Need to backport this fix on v14
@mt-software-de Fix on #699
@rousseldenis You'll want this also
|
Congratulations, your PR was merged at c963cbd. Thanks a lot for contributing to OCA. ❤️ |
|
@jbaudoux @mt-software-de backported in 14.0 here: #970 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is triggering concurrency updates on release channel records while reading them in the dashboard (updating
write_date+write_uidfields).