Friday, July 10, 2020
14 changes · master
Resolved issues and error corrections
This update removes leftover debugging output and fixes small code quality issues from a previous smooth scrolling change. It helps keep the editor and web interface stable and maintainable without changing how users work day to day.
This change updates several modules to use safer, approved database query construction required by stricter internal checks. It helps prevent fragile query patterns and keeps the codebase aligned with improved quality controls, without introducing expected user-facing changes.
Original PR description
Changes necessary due to fixed / stricter sql linter in odoo/odoo#53938: dsql cases which were previously missed / ignored are now properly inspected, injecting self._table is whitelisted but other injections of local variables require using the psycopg2.sql API.
Miscellaneous changes
When building the package list of the APT repository, dpkg-scanpackages reports the following and only output the latest package information in the Packages file: ``` dpkg-scanpackages: warning: Packages with multiple instances but no --multiversion specified: dpkg-scanpackages: warning: ./odoo_13.0.20191002_all.deb dpkg-scanpackages: warning: ./odoo_13.0.20191003_all.deb [...] dpkg-scanpackages: warning: ./odoo_13.0.20200630_all.deb ``` Having only the latest version listed in the P
Original PR description
When building the package list of the APT repository, dpkg-scanpackages reports the following and only output the latest package information in the Packages file: ``` dpkg-scanpackages: warning: Packages with multiple instances but no --multiversion specified: dpkg-scanpackages: warning: ./odoo_13.0.20191002_all.deb dpkg-scanpackages: warning: ./odoo_13.0.20191003_all.deb [...] dpkg-scanpackages: warning: ./odoo_13.0.20200630_all.deb ``` Having only the latest version listed in the Packages file makes it impossible to tell apt to use a specific version through apt-pinning. It also makes it impossible to revert to a previous version if a regression is caused by an update. For these reasons, tell dpkg-scanpackages to include all versions of the odoo package in the Packages file it generates. Forward-Port-Of: odoo/odoo#53888
### Issue - Accounting > General ledger - Have 2-3 lines in the table I added filters to have them - Toggle optional columns: (...) on the right There is an y scroll but you can't scroll more than half of the scrollbar. ### Cause The cause is that the dropdown height is greater than the table height. ### Solution Compute the table height depending on the dropdown and table header height. **OPW-2291531** -- I confirm I have signed the CLA and read the PR
Original PR description
### Issue - Accounting > General ledger - Have 2-3 lines in the table I added filters to have them - Toggle optional columns: (...) on the right There is an y scroll but you can't scroll more than half of the scrollbar. ### Cause The cause is that the dropdown height is greater than the table height. ### Solution Compute the table height depending on the dropdown and table header height. **OPW-2291531** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54256
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53874
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53874
…nt Link wizard In Sales, in Payment Link generation wizard, when entering manually the total of the quotation as Amount, it can happen that the Validation Error asking to set an Amount smaller than the total is triggered. opw-2287794 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54278
Original PR description
…nt Link wizard In Sales, in Payment Link generation wizard, when entering manually the total of the quotation as Amount, it can happen that the Validation Error asking to set an Amount smaller than the total is triggered. opw-2287794 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54278
The label of some buttons is updated on-the-fly, and the code which does that was actually altering the structure of the button widgets instead of just the labels' text. This code should be made more robust in master. Forward-Port-Of: odoo/odoo#54319
Original PR description
The label of some buttons is updated on-the-fly, and the code which does that was actually altering the structure of the button widgets instead of just the labels' text. This code should be made more robust in master. Forward-Port-Of: odoo/odoo#54319
Search the xsd files from in the database. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54130
Original PR description
Search the xsd files from in the database. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54130
When we group by date with DST change within a range, we could get a reocrd inside two date range grouping, or inside no grouping. This is because we computed range just with [+ 1 month], so we possibly had these ranges (in UTC): - October 2019 : [('datetime', '>=', '2019-10-01 02:00:00') ('datetime', '<', '2019-11-01 02:00:00')] - November 2019 : [('datetime', '>=', '2019-11-01 01:00:00') ('datetime', '<', '2019-12-01 01:00:00')] So a record on 2019-11-0
Original PR description
When we group by date with DST change within a range, we could get a reocrd inside two date range grouping, or inside no grouping. This is because we computed range just with [+ 1 month], so we…
When we group by date with DST change within a range, we could get a
reocrd inside two date range grouping, or inside no grouping.
This is because we computed range just with [+ 1 month], so we possibly
had these ranges (in UTC):
- October 2019 : [('datetime', '>=', '2019-10-01 02:00:00')
('datetime', '<', '2019-11-01 02:00:00')]
- November 2019 : [('datetime', '>=', '2019-11-01 01:00:00')
('datetime', '<', '2019-12-01 01:00:00')]
So a record on 2019-11-01 01:30:00 would be both inside October and
November.
This happen because the DST is removed on happen on 27 October 2019 and
this was not taken into account when computing the end of the range.
With this changeset, for the given example aboth, we will have:
- October 2019 : [('datetime', '>=', '2019-10-01 02:00:00')
('datetime', '<', '2019-11-01 01:00:00')]
Added test without the change fails with "AssertionError: Lists differ"
because:
- "Q1 2019" finished on 17:00:00 instead of 16:00:00
- "Q3 2019" finished on 16:00:00 instead of 17:00:00
opw-2278829
Forward-Port-Of: odoo/odoo#54189
Forward-Port-Of: odoo/odoo#54056The fact that led_status.sh was still running when performing the `git reset --hard` made it impossible to remount the filesystem in RO mode, due to a `mount point is busy` error. Instead of starting the led_status_sh script from rc.local, we make it a service so it can be easily restarted when an update is performed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54339
Original PR description
The fact that led_status.sh was still running when performing the `git reset --hard` made it impossible to remount the filesystem in RO mode, due to a `mount point is busy` error. Instead of starting the led_status_sh script from rc.local, we make it a service so it can be easily restarted when an update is performed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54339
opw-[2294930](https://www.odoo.com/web#id=2294930&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The tax amount not included in price should be computed in the remaining balance, even if not included in price. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54325
Original PR description
opw-[2294930](https://www.odoo.com/web#id=2294930&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) The tax amount not included in price should be computed in the remaining balance, even if not included in price. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54325
Update the description of the module to better match the workflow. Closes #11777 Forward-Port-Of: odoo/enterprise#11782
Original PR description
Update the description of the module to better match the workflow. Closes #11777 Forward-Port-Of: odoo/enterprise#11782
Forward-Port-Of: odoo/enterprise#11553
Original PR description
Forward-Port-Of: odoo/enterprise#11553
Account > Account > General Ledger Expand one account entries When journal entries are collected if on a move line a currency_id is defined in the record but the amount_currency is None an error will raise from format_value. opw-2288912 Forward-Port-Of: odoo/enterprise#11775 Forward-Port-Of: odoo/enterprise#11679
Original PR description
Account > Account > General Ledger Expand one account entries When journal entries are collected if on a move line a currency_id is defined in the record but the amount_currency is None an error will raise from format_value. opw-2288912 Forward-Port-Of: odoo/enterprise#11775 Forward-Port-Of: odoo/enterprise#11679