{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":76460069,"defaultBranch":"14.0","name":"odoo","ownerLogin":"Niboo","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2016-12-14T13:02:13.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/13940887?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715947589.0","currentOid":""},"activityList":{"items":[{"before":"cf513b0bcb61ca3862ab20c12c26b12efe590ab7","after":"ec5a798166cee25db72954da445e2ee2ed991c77","ref":"refs/heads/16.0","pushedAt":"2024-05-17T12:06:42.000Z","pushType":"push","commitsCount":845,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] core: reduce memory use of BaseModel._flush()\n\nThis is re-targeting https://github.com/odoo/odoo/pull/162442 to 16.0\n\nMotivation: MemoryError exceptions when a large number of records on the same\nmodel have dirty fields. Such often happens during upgrades.\n\nIn the current implementation, the cached data is re-arranged in multiple steps\nusing local data structures. The most problematic is\n`id_vals[record.id][field.name]`, because it creates a dictionary with a\npotentially long field name (think studio fields) as key for each dirty record.\nFor thousands of records, this quickly accumulates to 10s or even 100s of MiB\nin RAM.\n\nThe idea of this patch is:\n1. collect all dirty ids for all dirty fields on the model. This does not cost\n   additional memory, since the ist of ids per field will be pop()'ed from the\n   cache.\n2. Walk over fields and ids collecting all fields and values of each id in the\n   same loop, carefully consuming objects, while directly building the\n   `updates` dictionary, without creating the intermediate data structures.\n\nThis way, the _flush method only consumes a marginal amount of memory compared\nto the memory already consumed by the cache.\n\nCareful profiling (using `memray` for memory profiling, the odoo profiler for\nruntime profiling) of a testcase that flushes 80k records in 8 writes has shown\nthis new version to consume roughly 95% less memory while running slightly\nfaster.\n\ncloses odoo/odoo#165393\n\nSigned-off-by: Raphael Collet <rco@odoo.com>\nCo-authored-by: Raphael Collet <rco@odoo.com>","shortMessageHtmlLink":"[FIX] core: reduce memory use of BaseModel._flush()"}},{"before":"6788f43d6b487ce07f8678cadcd06f90e417dffa","after":"aec62c14d86800bacdeffc8907c6f196884c0ef5","ref":"refs/heads/17.0","pushedAt":"2024-05-14T14:23:43.000Z","pushType":"push","commitsCount":588,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] project: duplicate context for dialog_size\n\n-Remove duplicate dialog_size\n\ncloses odoo/odoo#165353\n\nSigned-off-by: Vincent Larcin (vila) <vila@odoo.com>","shortMessageHtmlLink":"[FIX] project: duplicate context for dialog_size"}},{"before":"8cbf44ff0a90e8b276d7835c3c820a0caab659d8","after":"6788f43d6b487ce07f8678cadcd06f90e417dffa","ref":"refs/heads/17.0","pushedAt":"2024-04-12T13:44:58.000Z","pushType":"push","commitsCount":216,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[IMP] base: avoid infinite loops in _update_category\n\nWhen updating the categories, if by any chance there is a loop in the\ncategory hierarchy, the current code was falling into an infinite loop.\n\nWith this commit, the graph loop is broken by clearing a parent_id, and\nif the resulting module category path is wrong, a clean new one will be\nrecreated anyway.\n\nThis allows unblocking uncomfortable situations where people cannot\nupdate the modules list any more. In 15.0, [a check][1] has been\nintroduced to prevent the existence of recursive categories, but as it\nis a python check it doesn't prevent corrupted data to remain corrupted.\n\nOPW-3704007\n\nRelated to odoo/upgrade#5574\n\n[1]: odoo/odoo@6932714200d158a21bf10b90b2f71fa5cae0b13f\n\ncloses odoo/odoo#161583\n\nX-original-commit: f2765d2cab5671a010404c36842bf1b4c4d6350b\nSigned-off-by: Christophe Simonis (chs) <chs@odoo.com>","shortMessageHtmlLink":"[IMP] base: avoid infinite loops in _update_category"}},{"before":"4177e03c2d68de768296f3d335bb44a43542e799","after":"8cbf44ff0a90e8b276d7835c3c820a0caab659d8","ref":"refs/heads/17.0","pushedAt":"2024-04-02T13:49:46.000Z","pushType":"push","commitsCount":314,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] purchase_stock: 'propagate_cancel' check not visible\n\nActivate \"Reception Report\" feature\nCreate a SO for a storable product, confirm.\nCreate a PO for the same product.\nConfirm the PO and check the delivery, open the \"Allocation\" report\nAssign the Product to the delivery of the SO.\nGo back to the PO and cancel the order, delivery of the SO will be cancelled.\n\nIssue: Currently the user cannot modify this behavior as the\n`propagate_cancel` checkbox is unaccessible\n\nopw-3733512\n\ncloses odoo/odoo#159940\n\nX-original-commit: c2059c8d2f9d8f6648a577f2dd44360d699f03cf\nSigned-off-by: Quentin Wolfs (quwo) <quwo@odoo.com>\nSigned-off-by: Andrea Grazioso (agr) <agr@odoo.com>","shortMessageHtmlLink":"[FIX] purchase_stock: 'propagate_cancel' check not visible"}},{"before":null,"after":"10c579b20b2ef53203d729957a7f693e81eeb6e6","ref":"refs/heads/saas-17.1","pushedAt":"2024-04-02T11:14:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] crm: resolve NewId error on SO-Linked tasks\n\nIssue:\n    - When adding opportunity/lead to a contact using Studio\n     and attempt to add a line, we encounter the following error:\n     \"TypeError: 'NewId' object is not iterable.\"\n\nSteps To Reproduce (in 17.0):\n    - In a contact form open Studio and add a O2M field\n     Customer (Lead/Opportunity)\n    - Try to add a line\n    - Notice Traceback Error \"TypeError: 'NewId' object is not iterable\"\n\nSolution:\n    - The issue arises in the search domain of\n    `return_if_relevant` , exactly in\n    (\"partner_id\", \"child_of\", lead.partner_id.commercial_partner_id.id)\n    where the type of `lead.partner_id.commercial_partner_id.id`\n    is NewId since the partner is being edited to add a task.\n    This action triggers the `parse` and `to_ids` methods with\n    a value type of NewId. thus the error.\n\n    - The operator child_of expects a list of IDs, and the ids\n    property refer to the record's origin ids. to resolve this,\n    replace `commercial_partner_id.id` with `commercial_partner_id.ids`.\n\nopw-3760372\n\ncloses odoo/odoo#159544\n\nX-original-commit: 03743a714f0da3731ae2c9c361bbcab54ac6f4b0\nSigned-off-by: Kawtar Drissi El Bouzaidi (kdeb) <kdeb@odoo.com>","shortMessageHtmlLink":"[FIX] crm: resolve NewId error on SO-Linked tasks"}},{"before":"c996a1a5f48c5c86f9c2b42e07a3a2aaae4dbb80","after":"4177e03c2d68de768296f3d335bb44a43542e799","ref":"refs/heads/17.0","pushedAt":"2024-03-18T09:33:55.000Z","pushType":"push","commitsCount":794,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] tools: make module import order consistent\n\nA long time ago, in a commit far far away: 65a3751613a392ae6a36f6efbcaeade924565d84,\nwe introduced a mechanism to support the \"import emulator\" feature[^1] of\ncPython. It's used by some C native modules to trigger an on-the-spot\nmodule import during a low-level function call.\n\nSome of the modules that do this are `datetime` and `time`:\n- https://github.com/python/cpython/blob/b6535ea7ecf40c51a9a13089d961c29abeaffa5e/Modules/timemodule.c#L892\n- https://github.com/python/cpython/blob/b6535ea7ecf40c51a9a13089d961c29abeaffa5e/Modules/_datetimemodule.c#L1654\n\nThose `PyImport_ImportModuleNoBlock()` calls were initially understood as real\ncalls that needed to return the imported module. But the actual return value is\nnever used by PyImport_Import. As long as the call succeeds, it is\nsufficient that the modules are imported and present in `sys.modules`\nafterwards:\nhttps://github.com/python/cpython/blob/b6535ea7ecf40c51a9a13089d961c29abeaffa5e/Python/import.c#L1825-L1834\n\nIn order to avoid randomizing the order of module imports, which can cause\nunpredictable behavior depending on the timing of those \"emulated imports\",\nit's simpler to provide a \"no-op\" import function, and ensure that all the\nallowed modules are imported in advance, when the server starts.\n\nThis is what this commit does. For good measure, it will raise an error\nif the module being imported is not already imported, which means it was\nnot one of the expected/allowed modules. In that case, it's sufficient\nto pre-import the module.\n\n[^1]: https://github.com/python/cpython/blob/b6535ea7ecf40c51a9a13089d961c29abeaffa5e/Python/import.c#L1756-L1766\n\nopw-3721469","shortMessageHtmlLink":"[FIX] tools: make module import order consistent"}},{"before":"cbb1dbe90abdda122d0fe38733e19b9ad1d349d6","after":"cf513b0bcb61ca3862ab20c12c26b12efe590ab7","ref":"refs/heads/16.0","pushedAt":"2024-02-13T16:12:32.000Z","pushType":"push","commitsCount":932,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] sale_loyalty: delivery shant count toward qty bought\n\nThis commit excludes delivery programs from being counted\ntowards rewards for loyalty programs.\nPrior to this commit, there was an issue steaming from the Standard Delivery\nline being added to the Sales Order during the transition from the\n\"Review Order\" screen to the \"Confirm Order\" screen. This flow illustrated\nthat loyalty programs count delivery line toward rewards for loyalty\nprograms.\n\n[Reproduce]\n- Install Odoo with modules:  sale_loyalty,website_sale,delivery\n- Create a loyalty program:\n    - Enable \"Discounts, Loyalty & Gift Card.\"\n    - Archive all the programs.\n    - Create a program with type \"Promotions.\"\n    - Set program conditions:\n        - Minimum Quantity: 2\n        - Minimum Purchase: 0\n        - Grant 1 point per order\n        - Among Product Domain \"Match all records.\"\n    - Set program Rewards:\n        - Type: Discount\n        - In exchange for 1 promo point.\n- Navigate to the front-end shop:\n    - Select 1 item.\n    - Add it to the cart.\n    - Proceed to Checkout.\n    - Ensure there is one item (you need 2 for the discount).\n    - \"Proceed to Checkout\" (delivery is added to the Sales Order at this point).\n    - Click \"Review Order\" to go back.\n    - BUG: The discount is shown in the \"Review Order\" screen.\nopw-3675387\n\ncloses odoo/odoo#149279\n\nSigned-off-by: Andrzej Pietrusiak (pian) <pian@odoo.com>","shortMessageHtmlLink":"[FIX] sale_loyalty: delivery shant count toward qty bought"}},{"before":"8bbc99d576ab1676af5f8fec1a8866fbe25f16fe","after":"c996a1a5f48c5c86f9c2b42e07a3a2aaae4dbb80","ref":"refs/heads/17.0","pushedAt":"2024-02-05T10:54:28.000Z","pushType":"push","commitsCount":683,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] website: filter out JSON fields from authorized fields in forms\n\nIssue:\n\nPossible to reproduce in 17.0: when adding a new field to the website\nform of the \"Extra Info\" page in the eCommerce, a traceback is raised\n(`OwlError: Missing template: \"website.form_field_json\"`) when the user\nselects \"Delivery Point Address\" (`sale.order.access_point_address`).\n\nExplanation:\n\nJSON fields (which exist since [1]) are not supported as selectable\ntypes in website forms, and they should not be because customers would\nnot be able to properly fill them out.\n\nFix:\n\nFilter out all JSON fields from the list of authorized fields in website\nforms; they will not appear in the list of selectable types anymore.\n\n[1]: https://github.com/odoo/odoo/commit/7eeba9d205d2dace571b5d0895ddba6290a512db\n\nopw-3596713\n\ncloses odoo/odoo#152545\n\nX-original-commit: 28c3eb5878ad6f3d40a096803f3ba4aef5ef7937\nSigned-off-by: Quentin Smetz (qsm) <qsm@odoo.com>\nSigned-off-by: Antoine Vandevenne (anv) <anv@odoo.com>","shortMessageHtmlLink":"[FIX] website: filter out JSON fields from authorized fields in forms"}},{"before":"239ea215dab1f9fbbd0053c65269e56c1ed030e6","after":"8bbc99d576ab1676af5f8fec1a8866fbe25f16fe","ref":"refs/heads/17.0","pushedAt":"2024-01-09T12:24:58.000Z","pushType":"push","commitsCount":1123,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[IMP] point_of_sale: Market Odoo on receipts\n\nIn this commit we add a line on the receipt with the text\n\"Odoo Point of Sale\" or \"Odoo Restaurant\". ( depending on the case)\n\nThis is done for marketing reasons.\n\ncloses odoo/odoo#148094\n\nTask: 3635645\nSigned-off-by: Joseph Caburnay (jcb) <jcb@odoo.com>","shortMessageHtmlLink":"[IMP] point_of_sale: Market Odoo on receipts"}},{"before":"86c23a3978b93b7cd4192dbc70e2615d6ad72ea7","after":"5b62e301b91a3f39857c2c7f18729e10796ef194","ref":"refs/heads/15.0","pushedAt":"2023-11-30T09:53:24.000Z","pushType":"push","commitsCount":555,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] account_edi_ubl_cii: no tax exemption reason for NO customers\n\nPrevent error: \"[BR-S-10]-A VAT breakdown (BG-23) with VAT Category code\n(BT-118) \"Standard rate\" shall not have a VAT exemption reason code\n(BT-121) or VAT exemption reason text (BT-120).\"\n\nWe should not provide a tax exemption reason for standard rates when the\ncustomer is Norvegian. It is not allowed in UBL Peppol Bis 3.\n\nno task/no ticket (noticed the error in the IAP logs).\n\ncloses odoo/odoo#144205\n\nSigned-off-by: Laurent Smet (las) <las@odoo.com>","shortMessageHtmlLink":"[FIX] account_edi_ubl_cii: no tax exemption reason for NO customers"}},{"before":"cf661998cb24ac8c22d39972597002cfb9867574","after":"cbb1dbe90abdda122d0fe38733e19b9ad1d349d6","ref":"refs/heads/16.0","pushedAt":"2023-11-20T12:32:16.000Z","pushType":"push","commitsCount":166,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[IMP] l10n_jp: tax group name update\n\nUpdate the japanese tax group template names to\nbetter fit the needs.\n\nTask id #3315696\n\ncloses odoo/odoo#142650\n\nX-original-commit: 04555ae4a1590378314bfcef34a3ef8f98c649f3\nSigned-off-by: William André (wan) <wan@odoo.com>\nSigned-off-by: Nicolas Viseur (vin) <vin@odoo.com>","shortMessageHtmlLink":"[IMP] l10n_jp: tax group name update"}},{"before":null,"after":"239ea215dab1f9fbbd0053c65269e56c1ed030e6","ref":"refs/heads/17.0","pushedAt":"2023-11-14T08:59:51.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] test_mail: fix activity test failing randomly\n\nEach failing of the test \"activity menu widget: activity menu with 2 models\"\nwas close to midnight. And that was actually the cause of the error.\n\nActually, when executing that test very close to midnight, the test activities\nare set up for a day and the check happens the day after (actually a few second\nafter). As we check in this test \"overdue\", \"planned\" and \"today\" activities,\nthe tested value are not inline anymore with the test setup when switching from\na day to the next (passing midnight). For example, \"today\" activities become\n\"overdue\" activities. To avoid that we patch the date to be far from midnight.\n\nTask-3592798\n\ncloses odoo/odoo#141762\n\nSigned-off-by: Warnon Aurélien (awa) <awa@odoo.com>","shortMessageHtmlLink":"[FIX] test_mail: fix activity test failing randomly"}},{"before":"d344966ab24b5fad90fa851846019392c1d3567d","after":"cf661998cb24ac8c22d39972597002cfb9867574","ref":"refs/heads/16.0","pushedAt":"2023-10-30T12:29:30.000Z","pushType":"push","commitsCount":386,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] point_of_sale: load partners by email and mobile/phone number\n\nBefore this commit, partners that were not already loaded in the PoS\ncouldn't be retrieved using their phone number or email address. This\nfunctionality is essential for customer recognition.\n\nopw-3548843\n\ncloses odoo/odoo#138893\n\nSigned-off-by: Joseph Caburnay (jcb) <jcb@odoo.com>","shortMessageHtmlLink":"[FIX] point_of_sale: load partners by email and mobile/phone number"}},{"before":"2aebfa3c6125720263b8629037b4ab6b3c29e3ac","after":"d344966ab24b5fad90fa851846019392c1d3567d","ref":"refs/heads/16.0","pushedAt":"2023-09-23T13:48:07.000Z","pushType":"push","commitsCount":484,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] hr: employee's avatar not showing againnnn\n\ncloses odoo/odoo#136246\n\nSigned-off-by: Sofie Gvaladze (sgv) <sgv@odoo.com>","shortMessageHtmlLink":"[FIX] hr: employee's avatar not showing againnnn"}},{"before":"68b5ab4f2936a02fe8245b887bf402abd4fd2997","after":"86c23a3978b93b7cd4192dbc70e2615d6ad72ea7","ref":"refs/heads/15.0","pushedAt":"2023-08-10T11:32:54.000Z","pushType":"push","commitsCount":913,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] website_event_track_exhibitor: fix sponsor 'midnight' opening hours\n\nCurrently, configuring opening hours for event sponsors 'at midnight' is not\nhandled properly.\n\nIf you set either the start time or the end time opening hours to \"00:00\",\nthe sponsor will be considered as always open.\n\nWe fix that by correctly taking into account that configuration.\n\n(Note: if the user configures a sponsor to be open 'until midnight', we assume\nit means midnight 'the next day').\n\nTests have been altered to take this into account.\n\nTask-3459777\n\ncloses odoo/odoo#131508\n\nX-original-commit: b7db1dfa05a7a5ad86e44eeb14f347bd8662e3be\nSigned-off-by: Thibault Delavallee (tde) <tde@openerp.com>\nSigned-off-by: Warnon Aurélien (awa) <awa@odoo.com>","shortMessageHtmlLink":"[FIX] website_event_track_exhibitor: fix sponsor 'midnight' opening h…"}},{"before":"8006e7ce618f98bd26a82cf9b64eaa9b6e9c9d2a","after":"2aebfa3c6125720263b8629037b4ab6b3c29e3ac","ref":"refs/heads/16.0","pushedAt":"2023-08-10T11:14:51.000Z","pushType":"push","commitsCount":756,"pusher":{"login":"jvandri","name":"Jérémy Van Driessche","path":"/jvandri","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15775380?s=80&v=4"},"commit":{"message":"[FIX] im_livechat: fix history scrollbar\n\nBefore this PR, scrollbar in livechat session history was horizontal because the\nflex-flow was set to column.\nThis PR remove the flex-flow to fix the issue.\n\ntask-3383919\n\ncloses odoo/odoo#131507\n\nSigned-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>","shortMessageHtmlLink":"[FIX] im_livechat: fix history scrollbar"}},{"before":"a0bde41dfe9c96af6a38ebaf60f053a0718d7679","after":"8006e7ce618f98bd26a82cf9b64eaa9b6e9c9d2a","ref":"refs/heads/16.0","pushedAt":"2023-06-12T14:49:39.770Z","pushType":"push","commitsCount":527,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] l10n_it_edi:  preventing valuerror in 10n_it_edi\n\nWhen we confirm an invoice without adding a product in it and then click on\nprocess now then we will face the above valuerror.\n\nSteps to produce:\n1) Install 'l10n_it_edi'.\n2) Change the company to 'IT Company'.\n3) Now go to 'Invoicing' settings and then under 'Fattura Elettronica mode'\ncheck  'Allow Odoo to process invoices' radio button.\n4) Create an invoice by adding a partner.\n5) While creating it click on 'Add a section' instead of 'Add a line'.\n6) Click on confirm.\n7) Now Click on 'Process now'.\nBy following the above steps you will be able to produce the above error.\n\nApplying this commit will solve the valuerror issue.\n\nSentry- 4170737698\n\ncloses odoo/odoo#121799\n\nSigned-off-by: William André (wan) <wan@odoo.com>","shortMessageHtmlLink":"[FIX] l10n_it_edi: preventing valuerror in 10n_it_edi"}},{"before":"0eccd3973e056b4ac6fcd6754a8b6af2818aac4f","after":"656b787716cda3ea7c7e284238b7bf3b4a7a7af9","ref":"refs/heads/11.0","pushedAt":"2023-05-22T13:17:46.765Z","pushType":"push","commitsCount":5,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] base/ir_model: fix materialized views columns listing\n\nBackport of b208570\n\ncloses odoo/odoo#120402\n\nSigned-off-by: Christophe Simonis <chs@odoo.com>","shortMessageHtmlLink":"[FIX] base/ir_model: fix materialized views columns listing"}},{"before":"14c985af526602a88666714e716283650521e537","after":"a0bde41dfe9c96af6a38ebaf60f053a0718d7679","ref":"refs/heads/16.0","pushedAt":"2023-05-08T13:00:20.000Z","pushType":"push","commitsCount":1512,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] project: make state and priority field non auto save in page\n\nBefore this commit changing priority and state from sub-task\nand block-by task saves the unsaved change or even create new\nrecords even though user discard that changes.\n\nThis commit add 'auto_save' false to prevent auto save for\nsub-task and block-by task page.\n\ntask-3282848\n\ncloses odoo/odoo#119330\n\nSigned-off-by: Aaron Bohy (aab) <aab@odoo.com>","shortMessageHtmlLink":"[FIX] project: make state and priority field non auto save in page"}},{"before":"b469295c884026caea1b7779e7ffb778e7a08ab3","after":"68b5ab4f2936a02fe8245b887bf402abd4fd2997","ref":"refs/heads/15.0","pushedAt":"2023-03-15T15:08:06.905Z","pushType":"push","commitsCount":741,"pusher":{"login":"antoineVerlant","name":"Antoine Verlant","path":"/antoineVerlant","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/25740681?s=80&v=4"},"commit":{"message":"[FIX] survey: pass the blank string if name and email is not set\n\nIn some cases name and email are NULL in survey.user_input so it's\nreturn False and can't change the case of the boolean value.\n\nSo here add the blank string if name and email is not set.\n\nsentry-3951409506\n\ncloses odoo/odoo#113459\n\nSigned-off-by: Warnon Aurélien (awa) <awa@odoo.com>","shortMessageHtmlLink":"[FIX] survey: pass the blank string if name and email is not set"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAETN8w0QA","startCursor":null,"endCursor":null}},"title":"Activity · Niboo/odoo"}