Uh oh!
There was an error while loading. Please reload this page.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
To my knowledge, this is NOT needed when the field is imported directly instead of using the patched
odoo.fields.Serialized(like in queue_job).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.
But I have shown you the capture with the error in our CI when we run the server without this:
Uh oh!
There was an error while loading. Please reload this page.
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.
This problem might come from the fact that
base_sparse_fieldis not available in your env (for whatever reason) or you are using an outdated version of queue_job... I don't know, can't judge from a screenshot 🤷♂️We never had this problem on any of our instances or dev setup or CI setup. Even when we use
--load=queue_job.FTR this was fixed a looong time ago here 547538b and if you look at the change we removed the need for the server wide module. Hence it looks weird, at least 😉
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.
The code of
queue_jobis updated to latest one. Don't you think that not depending in the manifest onbase_sparse_fieldis an error?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.
And what's the problem with having such server wide module loaded?
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.
I'm arguing only about the
server_wide_moduleschange here. The dependency change IS correct.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.
But one is attached to the other: if you don't add it to the server wide modules, then it's not loaded at all. And I insist: is there any problem adding to the server wide modules that I'm not aware of?
Uh oh!
There was an error while loading. Please reload this page.
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.
AFAIK This is not true. It was required WHEN we were using the patch.
AFAIK The server wide module IS NOT needed. If you want to recommend it for certain cases, fine, but if you want to state in the docs that is required, to me is wrong. Unless proven otherwise. This is my point.
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.
Tested and indeed the server wide is not needed. @victoralmau please do a PR in 14.0 for removing such change in the documentation.