{"push_id":2533345310,"size":68,"distinct_size":3,"ref":"refs/heads/saas-11.2-fixes-aku","head":"36e42cf20b6e8bd298ee23a2bf2bc04aed2b0dbf","before":"f47fb170db507c53712acf686045947b04de147a","commits":[{"sha":"6c97aeee8de0ba495d48e659c9e50a5b4ca33d40","author":{"name":"Géry Debongnie","email":"767e387ec22b285e8a981c348a6e0620992d4a93@odoo.com"},"message":"[FIX] web: use FieldText as fallback for html fields\n\nCurrently, the default field widget of type html is not defined in the\nweb addon, but in the web_editor addon.  It uses the summernote library\nand different assets.\n\nThe web_editor addon is defined with auto_install=true, so it is usually\nnot an issue.  However, it could happen that there is some issue with\nthe web_editor asset bundles.  In that case, any form view with a field\nof type html will crash.\n\nWith this commit, we define a default widget of type html in the web\naddon.  This will render as text (so, not exactly what one might\nexpect), but it is still better than making the web client unusable.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/6c97aeee8de0ba495d48e659c9e50a5b4ca33d40"},{"sha":"b8bf945335f2e52dbd07f2560108f2ee4637598d","author":{"name":"Géry Debongnie","email":"767e387ec22b285e8a981c348a6e0620992d4a93@odoo.com"},"message":"[FIX] web: do not change pager when discarding changes\n\nHere is a scenario that could happen before this commit:\n1. go to a list view with more than one record, say 3\n2. click on the 3rd record to open the form view\n3. the pager says 3/3\n4. click on edit button\n5. click on discard button\n6. the pager says 1/3 (but the record displayed is still the same)\n\nIt is often necessary to restore the offset for the sub records, because\nthe number of pages in a one2many could have changed.  However, it is\nnot a good idea to do that for the main record, since it interferes with\nthe usual flow of operations.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/b8bf945335f2e52dbd07f2560108f2ee4637598d"},{"sha":"dea07fc29116c36c8a3773eec0fce526a972ba08","author":{"name":"XavierDo","email":"a1a56fd5af677733fcc9fce69c49c5e66d550efa@odoo.com"},"message":"[IMP] project, portal: group tasks by project on portal.\n\nThe portal view for tasks previously listed all task of all projects\nwithout grouping them. It was a problem, mainly when we want to make\nthe distinction on project label_tasks, to make the difference\nbetween tasks, issues, ... Grouping task by project by default allows\nto show the label_tasks before each project.\n\nGrouping the tasks removes the possibility to define a primary\nordering. We want to be able to ungroup the tasks in some cases.\nThe implentation was done in the portalsearch bar adding\na group by option. The portal proposes two grouping options,\nproject (by default) and none (to keep strict ordering).\n\nTask: #1827950\nPR #23769","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/dea07fc29116c36c8a3773eec0fce526a972ba08"},{"sha":"b61aad2f6b7a0b1fa5c4a2dad941a350f2c03236","author":{"name":"Olivier Dony","email":"d670d44c3ca8bd4cd53a3b09f8bf8fc35e4843cc@openerp.com"},"message":"[FIX] hr*: restrict personal employee fields at model level\n\nFixes #12077\nCloses #12160","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/b61aad2f6b7a0b1fa5c4a2dad941a350f2c03236"},{"sha":"0dd08bd148d6b2f74e8800ffe1b72b939876e214","author":{"name":"Nicolas Martinelli","email":"771435c469f83f6aa9c405ac5e1ed06314a94f2d@odoo.com"},"message":"[FIX] mrp: change BOM\n\n- Create a MO for Product A with quantity to produce of 2\n- Produce 1\n- Open the associated BOM, and add a line to the bom\n- Go back to the MO and try to update the qty to produce to 1\n\nTraceback: division by 0\n\nopw-1838006","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/0dd08bd148d6b2f74e8800ffe1b72b939876e214"},{"sha":"9daf3f85a8a3b012a79226fe13d3cde2293fcce0","author":{"name":"Nicolas Martinelli","email":"771435c469f83f6aa9c405ac5e1ed06314a94f2d@odoo.com"},"message":"[FIX] stock: search on quantity\n\n- Create a stockable Product A\n- Get create an incoming picking at date D for A\n- Go to Inventory > Report > Inventory, and search for the the inventory\n  at date D-1.\n- A should appear with a quantity on hand of 0.\n- Filter on 'Available Products'\n\nThe product still appear in the list with a quantity on hand of zero.\n\nThe optimized method `_search_qty_available_new` is used, although it\ndoesn't take into account dates.\n\nThe original use case for this optimized method was to quickly get\nproducts with stock on hand, i.e. products with quants without needed\ninformation of stock moves.\n\nopw-1833510","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/9daf3f85a8a3b012a79226fe13d3cde2293fcce0"},{"sha":"96ce375c610d2ddcaf801340603afc139069ace5","author":{"name":"Nicolas Lempereur","email":"2907e499a003d1c3ab7944c0a40c6df46e3e3c2f@odoo.com"},"message":"[FIX] models: more than one prefetch in onchange\n\nWhen a record fields are prefetched, the currently accessed record is\nprefetched as well as PREFETCH_MAX (=1000) minus currenly accessed\nrecords.\n\nSince 439fa826 the id field was thought as \"prefetched\" but was not,\nwhich caused that in an onchange, we would have a prefetching as follow\nfor 1200 records:\n\n- get records 1-1000\n- get record 1001 (1001-1200 INTERSECTION 1-999 (id) + 1001 (current))\n- get record 1002 (1002-1200 INTERSECTION 1-999 (id) + 1002 (current))\n- get record 1003 (1003-1200 INTERSECTION 1-999 (id) + 1003 (current))\n- ...\n- get record 1200 (1200 INTERSECTION 1-999 (id) + 1200 (current))\n\nSo we would do 201 queries instead of 2 when prefetching the records.\n\nThe added test without this change failed the query count with:\n\n \"AssertionError: 284 not less than or equal to 5 : admin\"\n\nopw-1837548\nopw-1837552\ncloses #24326","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/96ce375c610d2ddcaf801340603afc139069ace5"},{"sha":"b41c4396dd103b01d9f265a9f5fa3858fea10bf1","author":{"name":"Xavier Morel","email":"0f311f41b2be8e2b5de98776566d712cdc154ca4@odoo.com"},"message":"[FIX] handling of empty/absent modules in xids\n\nRestore behaviour of not adding the separating dot if the module field\nof an ir.model.data record is empty. This is useful/important for\ninterop with external systems.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/b41c4396dd103b01d9f265a9f5fa3858fea10bf1"},{"sha":"6ff8eeea36743cfe47f042a50125d3fa29ece968","author":{"name":"Odoo Translation Bot","email":"e7f5472e9a159f4d404f1091c7e345bf7ac1ddb0@odoo.com"},"message":"[I18N] Update translation terms from Transifex","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/6ff8eeea36743cfe47f042a50125d3fa29ece968"},{"sha":"383947646f5652804bd6bbc764380a890e6f4a8d","author":{"name":"Simon Lejeune","email":"1969d8dff896674c2d819e813f5e88ca826229ab@openerp.com"},"message":"[REF] stock: rounding issues\n\nThere's a certain configuration of UOM that is not correctly handled in\nthe v11 stock:\n- create a move with an UOM having an higher factor than the product's\n  UOM\n- this higher UOM has a rounding of 1.0, meaning it doesn't allow\n  partial reservation\n- use the product's uom in this move and enter quantities that aren't\n  expressible in the move's uom\n\nA practical example is to set the rounding of dozen at 1.0, set the uom\nof a product to units, create a move for a dozen and create a new move\nline with 8 units.\n\nThe first issue is the `quantity_done` field, that uses an half-up\nrounding on the `qty_done` field of each move line and sum them. When\napplying this logic to the previous example, `quantity_done` field would\nbe 1.0, meaning we won't make a backorder for the missing 4 units. We\nfix these issue by summing a non rounded qty_done and afterwards\nrounding this value to the general products'UOM. This mean\n`quantity_done` is technically not be expressible in the move's uom, but\nkeeping this value close to the reality will allow to handle the\nbackorders and extra moves correctly.\n\nThe second issue is that the backorder is always expressed in the move's\nuom. In the previous example, this would mean creating a backorder of 0\ndozen. In v10, an error was throwed, saying this operation is\nimpossible.\n\nThe `_prepare_move_split_vals` previously always received the quantity\nof the backordered move in the uom of the original move. This is a\nremnant of the v10 implementation where, if the quantity to backorder is\nnot expressible in the original move's UOM, an error was throwed. We now\npass the used uom via a context key to not update the method signature,\nas it is probably legitimately overidden by custom modules. This way, in\nthe previous example, a backorder of 4 units is created.\n\nThe last issue is in `_action_assign`. Let's say you have 8 units in\nstock and you want to reserve a dozen, the system will reserve 8 units\nand then convert back 8 units in dozen, meaning a dozen was reserved.\nThis resulted in awkward situation where more items than available were\nreserved, and the famous \"cannot unreserve more than what's available in\nstock\" was throwed at almost each operation. To solve this, we convert\nthe not-yet reserved quantities back and forth in both uom. This\nprevents partial reservation when not allowed, which is good. We had to\nadapt some lines of `_action_assgn` that expected\n`_update_reserved_quantity` always at least partially reserved the move.\nIt is now possible that it doesn't reserve anything.\n\nWe also normalize the quantity with a greater decimal precision when\ndeciding if we open the immediate transfer wizard or not (in the\noriginal exemple, if you enter a single unit the immediate transfer\nwizard would be openned because 0 was done in the UOM of the dozen). We\nalso prevent to enter `qty_done` on the move line if the value doesn't\nhonour the rounding of the UOM.\n\nWe introduce two tests, a simple  `_action_assign` in MTS and a more\ncomplete MTO scenario with backorders, extra moves and invalid qty_done.\n\nopw-1835186\nopw-1835946","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/383947646f5652804bd6bbc764380a890e6f4a8d"},{"sha":"df58ead943225fdf4848c1fd7ee90589625069a5","author":{"name":"Alexandre Kühn","email":"22220c18caede9806cb42c8e2b41136d711673bf@odoo.com"},"message":"[FIX] mail: fix composer css style\n\nRevision of https://github.com/odoo/odoo/commit/c778de44c7cd9b7ef5a9a91738164ab0ebd0ca06\n\nThe commit above changed the composer in order to add colored text for mentions\n(instead of textarea, it uses a div with contenteditable).\n\nSome tweaks were made in order to preserve the css style of the composer, but\nthere were some leftovers:\n\n    - placeholder \"Write Something\" should be more transparent\n    - cursor hover on placeholder should be of type text\n    - text is not vertically centered with the input container\n    - there should be no focus border when the composer has the focus\n    - \"Send\" button is vertically misaligned by 1 pixel off in discuss\n\nThis commit solves all of the above problems.\n\nAs a result, the css style of the composer should look almost similarly to the\none in v11.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/df58ead943225fdf4848c1fd7ee90589625069a5"},{"sha":"f2ba1cc843016c1f431a7335995df9bc86d500d4","author":{"name":"Alexandre Kühn","email":"22220c18caede9806cb42c8e2b41136d711673bf@odoo.com"},"message":"[FIX] mail: no crash when clicking on systray inbox notification not linked to a document\n\nBefore this commit, when we have a notification in the messaging menu (systray)\nthat comes from a message in inbox which isn't linked to a document\n(e.g. a task), clicking on it result in a crash.\n\nThis issue comes from a typo of a recent js mail refactoring [1]\n\nAlthough this is only a 1-line fix, there are no tests on the messaging menu\nwidget in the systray. Therefore, this commit also introduces some basic tests\nof this widget, in addition to the test related to the fixed issue.\n\n[1] https://github.com/odoo/odoo/commit/02ec09cb1c3e2d7bc7968f40c18f2208d7f3f498","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/f2ba1cc843016c1f431a7335995df9bc86d500d4"},{"sha":"794e1cbb29429503aab0771d230ca8fd7f388222","author":{"name":"Martin Trigaux","email":"cc7c5be316e48d137cbb549833b85d91034d799d@odoo.com"},"message":"[I18N] crm: update source terms\n\nTo reflect the (unstable) changes made at 002bf77df3","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/794e1cbb29429503aab0771d230ca8fd7f388222"},{"sha":"4d88e8e8223d04cff05e7f5b4fae2cef081707d9","author":{"name":"Akim Juillerat","email":"a19d074d602e53eef4d197dcb0fcf9523314b216@camptocamp.com"},"message":"[FIX] hr_holidays: update _check_holidays constrains\n\nIt was possible to edit a leave request in order to use a leave type\nwhich had no more days left. This was due to a missing field in the\nconstrains call.\n\nCloses #24320","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/4d88e8e8223d04cff05e7f5b4fae2cef081707d9"},{"sha":"47cf31b539ade1e71450184300a338acb0cab9fa","author":{"name":"Géry Debongnie","email":"767e387ec22b285e8a981c348a6e0620992d4a93@odoo.com"},"message":"[FIX] web: prevent web client from blocking some view\n\nIn some situations, it could happen that the action manager had a\nrejected deferred representing the creation of a view, and was blocked\nfrom doing any other interaction with that view.\n\nFor example, imagine that a read operation crashes for record 1 on the\nmodel res.partner.  If the user is on the kanban view and click on\nrecord 1, there will be an error dialog informing him of the error.\nHowever, if the user clicks then on another record, nothing will happen\nbecause the action manager is blocked (only the form view in this case).\n\nWith this commit, whenever the view creation process failed, we also\nremove the rejected deferred so the action manager will be allowed to\ntry again.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/47cf31b539ade1e71450184300a338acb0cab9fa"},{"sha":"dab5a83132097ca5ed1759aa2bc98250813fa287","author":{"name":"RomainLibert","email":"d3a53ea3f0d6ebbbf1eb8431093f132bc4577d93@odoo.com"},"message":"[DOC] views: add documentation for gantt view attributes\n\nCloses #24341","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/dab5a83132097ca5ed1759aa2bc98250813fa287"},{"sha":"82de88b066842040ee7d0246f58d2281ab48b333","author":{"name":"Martin Trigaux","email":"cc7c5be316e48d137cbb549833b85d91034d799d@odoo.com"},"message":"[FIX] mail: cover more cases for URLs\n\nTransifex URLs have an original scheme using #lang, followed by the module or\n'$' (for any module) and the searched text can be quoted\n\nBefore this commit the link was cut after\nhttps://www.transifex.com/odoo/odoo-11/translate/#fr/, making the link not\nclicable\n\nCloses #24346","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/82de88b066842040ee7d0246f58d2281ab48b333"},{"sha":"b16c4f50d43590f6eeef7b3812fe6ed16607974d","author":{"name":"Jeremy Kersten","email":"56923a0c9ca793c07ff1df1013de5694062a27a6@odoo.com"},"message":"[FIX] website_sale: avoid traceback when category don't exists\n\nIn case the category is given in GET, ?category_id=xx, we cannot guarantee that\nthe category exists\n\nThis commit closes #24235","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/b16c4f50d43590f6eeef7b3812fe6ed16607974d"},{"sha":"d8221eab30159f03caf5c17144b9ca4e69fce950","author":{"name":"William Henrotin","email":"27622d0d92573d88f123cba4968250797d9e766b@odoo.com"},"message":"[FIX] stock: update qty_done in move wizard\n\nScenario : Create a transfer on a product tracking by lot. Update the\noperation type \"Receipt\" by unchecking the \"show reserved\" option.\nOpen the Register lots, pack, location wizard and set some lots with a\nquantity done. The quantity done field is not updated in real time.\n\nIssue :\nThe depends function on quantity_done is triggered only on move_line_ids\nbut \"show reserverd\" option replace move_line_ids by\nmove_line_nosuggest_ids in the wizard.","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/d8221eab30159f03caf5c17144b9ca4e69fce950"},{"sha":"3fd24cba2afea6985593896229d8ffca3a5770d6","author":{"name":"pka-odoo","email":"57fc907697cb584c8710b34b8d3db437451647b3@odoo.com"},"message":"[FIX] web: calendar: show Undefined label if sidebar filter has no value\n\n and keep all those filters at last. (PR#20463)\r\n\r\ne.g. If field used in color attribute of calendar view does not have value then such sidebar filters will not have string besides filter checkbox\r\nin such cases we should set Undefined string and put all those filters at last in filter list\r\nCurrently we can see issue in calendar of manufacturing orders in db with demo data\r\n\r\nRelated to Issue #1778360\r\n\r\nCo-authored-by: Mohammed Shekha <msh@openerp.com>","distinct":false,"url":"https://api.github.com/repos/odoo-dev/odoo/commits/3fd24cba2afea6985593896229d8ffca3a5770d6"}]}
{"actor":{"display_login":"alexkuhn"}}