Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Triple discount modules refactor and maturity levels
    Hello community

    A few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:

    Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.

    We actually have migration PRs for triple discount modules in 17.0:

    My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?

    Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?

    Please let me know what do you guys think about it.

    Best regards.

    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Akim Juillerat
    Business solutions
    Software architect
    +41 62 544 03 78

    Camptocamp SA
    Leberngasse 21
    4600 Olten
    Switzerland
    +41 21 619 10 10
    by Akim Juillerat - 07:06 - 10 Sep 2024

    1 replies 1 replies

    • Re: Triple discount modules refactor and maturity levels
      Hi Akim,

      Thank you for your hard work on the triple discount module. IMO we should merge the 16.0 branch. By bumping the version to the next major level, the signal is clear that this new version contains breaking changes. I'm often reluctant to introduce such deep changes in a ‘stable’ version. In this case, I feel it's justified by the need to introduce a cleaner/simpler approach and remove hacks made necessary by the complexity of the previous one. This cleaner architecture also provides a better basis for all the modules based on this module.  Regarding the maturity level, the default one is beta, I would find it logical to prohibit such changes on a ‘stable’/‘mature’ version, but not on a ‘beta’ version.

      Regards,

      lmi



      On Tue, Sep 10, 2024 at 7:08 PM Akim Juillerat <notifications@odoo-community.org> wrote:
      Hello community

      A few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:

      Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.

      We actually have migration PRs for triple discount modules in 17.0:

      My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?

      Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?

      Please let me know what do you guys think about it.

      Best regards.

      camptocamp
      INNOVATIVE SOLUTIONS
      BY OPEN SOURCE EXPERTS

      Akim Juillerat
      Business solutions
      Software architect
      +41 62 544 03 78

      Camptocamp SA
      Leberngasse 21
      4600 Olten
      Switzerland
      +41 21 619 10 10

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe



      --
      Laurent Mignon
      Technical lead / Management Team
      T: +32 2 8883148


      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

      by Laurent Mignon - 08:56 - 11 Sep 2024
  • Management System Odoo 17
    Hello, I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?
    Thanks..



    PT Laris Chandra
    Sole Distributor of :
    STP - PENRAY - TURTLE WAX - SIP - PRESTONE (Radiator Products) - ARMOR ALL - CHW - AUTOGARD
    Jl. Pluit Utara Raya Blok B-VIII No. 47 RT 05/04 Penjaringan Jak-Ut 14450 – Indonesia
    Phone: +62 21 667 6699 | Fax: +62 21 667 6789
    Visit PT Laris Chandra at : larischandra.com
    This email and any attachments are confidential. If you are not the addressee or have received this message in error, please delete all copies from your system and notify the sender immediately. The sender does not accept liability for any problems that may arise from this email transmission.
    by Lingga Pratama - 11:17 - 4 Sep 2024

    2 replies 2 replies

  • Re: Contributors
    Hello,  I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?

    Thank You..


    PT Laris Chandra
    Sole Distributor of :
    STP - PENRAY - TURTLE WAX - SIP - PRESTONE (Radiator Products) - ARMOR ALL - CHW - AUTOGARD
    Jl. Pluit Utara Raya Blok B-VIII No. 47 RT 05/04 Penjaringan Jak-Ut 14450 – Indonesia
    Phone: +62 21 667 6699 | Fax: +62 21 667 6789
    Visit PT Laris Chandra at : larischandra.com
    This email and any attachments are confidential. If you are not the addressee or have received this message in error, please delete all copies from your system and notify the sender immediately. The sender does not accept liability for any problems that may arise from this email transmission.
    by Lingga Pratama - 11:11 - 4 Sep 2024
  • Odoo Experience Exhibition 2024: Comprehensive Attendee Directory

    Hi,

    Hope all is well with you!

     

    We're offering a special deal: discounted cost and extra information.

    We're following up to see if you're interested in getting the Visitors/Attendees List.

     

    Event name: Odoo Experience Exhibition 2024

    Date: 02 - 04 Oct 2024

    Location :  Brussels Expo - Exhibition Center, Brussels, Belgium  

    Attendees/Visitors Count: 7500

     

     

     

    Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

    Could you let us know if you're interested? We'll then send you the discounted cost and more details.

     

    Waiting for your positive response.


    Thanks and Regards
    Aria Wells
    by Aria.Wells@leadboostershq.com - 08:41 - 4 Sep 2024

    2 replies 2 replies

    • Re: Fwd: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory

      Unfortunately Virginie, anyone who knows the email address, contributors@odoo-community.org, can write to this list.

      Questions is, who is it? Most likely not ... Aria Wells!!

      Let's do some Sherlack Homes activities and investigate the original email headers.
      Received: from mail-wm1-x361.google.com (mail-wm1-x361.google.com [IPv6:2a00:1450:4864:20::361])

      Looks like Aria Wells, or whatever his/her/it name is, is using a Google mail server located in Ireland, see attached screenshot.


      Has anyone else other info about this "person"?



      Best regards,

      Michel Stroom
      Office Everywhere


      On 2024-09-04 09:02, Virginie Dewulf wrote:

      Hello,
       
      This is the kind of email I'd like to not receive anymore on the Contributors mailing list, but the person who sent it is not in the mailing list.
      How is this possible?
      Can anyone write to the contributors mailing list?
       
      I'll dig into this later ^^
      Virginie Dewulf
      Executive Director
      +32 477 64 17 20


      ---------- Forwarded message ---------
      De : Aria.Wells <notifications@odoo-community.org>
      Date: mer. 4 sept. 2024 à 08:42
      Subject: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
      To: Contributors <contributors@odoo-community.org>


      Hi,



      Hope all is well with you!






      We're offering a special deal: discounted cost and extra information.



      We're following up to see if you're interested in getting the Visitors/Attendees List.






      Event name: Odoo Experience Exhibition 2024



      Date: 02 - 04 Oct 2024



      Location :  Brussels Expo - Exhibition Center, Brussels, Belgium  



      Attendees/Visitors Count: 7500












      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.



      Could you let us know if you're interested? We'll then send you the discounted cost and more details.






      Waiting for your positive response.




      Thanks and Regards
      Aria Wells

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      by Michel Stroom - 11:41 - 4 Sep 2024

      1 attachments 1 attachments

      Screenshot 2024-09-04 at 11.31.55.png
    • Fwd: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
      Hello,

      This is the kind of email I'd like to not receive anymore on the Contributors mailing list, but the person who sent it is not in the mailing list.
      How is this possible?
      Can anyone write to the contributors mailing list?

      I'll dig into this later ^^
      Virginie Dewulf
      Executive Director
      +32 477 64 17 20


      ---------- Forwarded message ---------
      De : Aria.Wells <notifications@odoo-community.org>
      Date: mer. 4 sept. 2024 à 08:42
      Subject: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
      To: Contributors <contributors@odoo-community.org>


      Hi,

      Hope all is well with you!

       

      We're offering a special deal: discounted cost and extra information.

      We're following up to see if you're interested in getting the Visitors/Attendees List.

       

      Event name: Odoo Experience Exhibition 2024

      Date: 02 - 04 Oct 2024

      Location :  Brussels Expo - Exhibition Center, Brussels, Belgium  

      Attendees/Visitors Count: 7500

       

       

       

      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

      Could you let us know if you're interested? We'll then send you the discounted cost and more details.

       

      Waiting for your positive response.


      Thanks and Regards
      Aria Wells

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Virginie Dewulf (OCA) - 09:01 - 4 Sep 2024
  • OCA Technical Training: 20h online from 16th Sept to 22nd Oct
    Hello Contributors,

    I hope everything is doing great!

    Did you hear that the OCA launched an Odoo Technical Training?

    It starts on 16th September for a 5-week journey (2 hours/session, 10 sessions).

    The full schedule and information are here:

    To register:

    In summary, it is aimed at
    • new developers hired by Odoo integrator companies, as a complementary technical onboarding
    • freelance developers wanting to start a career within the Odoo world
    • any developer who has been around for a time but would like to go back to the foundation of Odoo development

    The trainers are experienced Odoo developers:
    • Daniel Reis (Open Source Integrators), author of Odoo Development Essentials book
    • Radovan Školník (Data Dance)
    • Carmen Bianca Bakker (Coop IT Easy)
    • Tom Blauwendraat (Therp)
    • Ronald Portier (Therp)
    And below is the full schedule of the 10 Sessions.

    We still have seats available!
    If you are interested but not available on the dates, let me know (virginie@odoo-community.org)

    Have a good week,
    Virginie

    ------

    Session 1:
    * Odoo product overview: versions, licenses, architecture, components
    * OCA organization, contribution processes, tooling, coding standards
    * You and the OCA: how to use or integrate OCA code in your projects


    Sessions 2, 3 and 4:

    * Odoo architecture - client / server / database
    * Database nature of Odoo
    * Basic building blocks - models, fields, views, ...

    * Installing local Odoo development environment
    * Database configuration
    * git repositories
    * Documentation / Resources

    * First module
    * Basic building blocks - models and views
    * Extension mechanisms


    Sessions 5, 6 and 7:
    * How the Odoo Object-Relational Mapping (ORM) works

    * Available data types in the Odoo ORM

    * Querying your database using the Odoo ORM
    * Debugging Odoo
    * Writing tests for your Odoo modules
    * How to adjust Odoo views to make them useful and beautiful


    Sessions 8, 9 and 10:

    Contributing to the OCA:

    * The OCA review process
    *The importance of unit tests
    * The important of pre-commit
    * OCA runboat and CI
    * Translations in OCA
    * Stale / not stale
    * How to contact a PSC member or apply to be one yourself
    * Before you submit your PR: checking if similar work already exists, and deciding on which repository to put it
    * Python dependencies, dependencies between PR's
    * "Rebel modules"


    Modules Migration:
    *how migrations are part of the OCA model
    * data migration and openupgrade
    * code migration:
    -- The need to keep history
    -- Technical method
    -- Following all the steps
    -- Maintain and increase code quality
    -- Improving and adding tests

    ------




    OCA Training Session-3.png


    Virginie Dewulf
    Executive Director
    +32 477 64 17 20

    by Virginie Dewulf (OCA) - 12:51 - 2 Sep 2024

    1 attachments 1 attachments

    OCA Training Session-3.png
  • Seeking References for HR Implementations with Large Companies

    Hello Community,

     

    we have a customer based in California and he is looking for a References of large companies using HR Modules, Please share any references that we can use for this customer.

     

     

      

    Best Regards,

     

    Manish Mannan

    Director - Sales

    Sales | O2B Technologies

    mobilePhone

    +13106018359

    emailAddress

    manish@o2b.co.in

    website

    www.o2btechnologies.com

    facebook

    linkedin

     

    by Manish Mannan - 09:51 - 2 Sep 2024

    5 attachments 5 attachments

    image005.png
    image004.png
    image003.png
    image002.png
    image001.png
  • RFQ for OCA Days 2024 Video Post Production
    Hello OCA Contributors,

    I hope this finds you all well.

    We are getting the final details ready for OCA Days 2024.
    If you haven't registered yet,  there is still time, you can do so here.

    I'm sharing the RFQ for Video Post Production of the recorded talks - have you got a digital superstar in your company who could help? Please share it around.

    Deadline for submission for the RFQ is 18th September 2024.
    You can find out more on our RFQ process page.

    If you have any questions please get in touch.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly (OCA) - 01:16 - 28 Aug 2024

    1 attachments 1 attachments

    2024 OCA Days Video Post Production RFQ.pdf

    1 replies 1 replies

    • Re: RFQ for OCA Days 2024 Video Post Production
      Hello OCA Contributors,

      Just a reminder this RFQ closes today.

      If you have the skills within your company to help us out after the OCA Days, we would love to hear from you.

      Warm regards,
      Rebecca

      On Wed, 28 Aug 2024 at 23:11, Rebecca Gellatly <rebecca@odoo-community.org> wrote:
      Hello OCA Contributors,

      I hope this finds you all well.

      We are getting the final details ready for OCA Days 2024.
      If you haven't registered yet,  there is still time, you can do so here.

      I'm sharing the RFQ for Video Post Production of the recorded talks - have you got a digital superstar in your company who could help? Please share it around.

      Deadline for submission for the RFQ is 18th September 2024.
      You can find out more on our RFQ process page.

      If you have any questions please get in touch.
      Rebecca

      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association


      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association
      by Rebecca Gellatly (OCA) - 12:21 - 18 Sep 2024
  • odoo-community.org has a new home
    Hi everyone,

    https://odoo-community.org has found a new home on a more powerful server.

    Everything should work as before, just faster. Let me know if you notice anything is off.

    Best regards,

    -Stéphane

    --
    Stéphane Bidoul
    http://acsone.eu/
    by Stéphane Bidoul - 12:06 - 22 Aug 2024

    10 replies 10 replies

  • Test
    This is a test message, preparing for the migration of the OCA Odoo instance to a new server.

    -sbi

    by Stéphane Bidoul - 10:41 - 20 Aug 2024

    3 replies 3 replies

  • Large Data Files
    Hello,

    I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

    It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

    I suppose the ORM might be an issue here. Potential workaround:

    1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
    2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
    3. Increase the CPU/RAM/Worker nodes
    4. Some better ideas?

    What would be the best way to go?

    A piece of my current test (df is a pandas dataframe containing the new events): 

    @api.model
        def create_events_from_df(self, df):
            Event = self.env['event.event']
            events_data = []
            for _, row in df.iterrows():
                event_data = {
                    'location': row['location'],
                    'name': row['name'],
                    'date_begin': row['date_begin'],
                    'date_end': row['date_end'],
                }
                events_data.append(event_data)
           
            # Create all events in a single batch
            Event.create(events_data)

    Thanks in advance if you read this, and thanks again if you replied :)

    Jérôme
    by "Jerôme Dewandre" <jerome.dewandre.mail@gmail.com> - 05:31 - 20 Aug 2024

    10 replies 10 replies

    • Re: Large Data Files

      Le mer. 7 mai 2025 à 10:16, David Beal <david.beal@akretion.com> a écrit :
      Hi Jérome,

      Additionally you may reach more performance with https://github.com/yanyanren123hotmailcom/connectorx

      Here is the explanation

      I experimented successfully connectorx with polars (but not benchmark it myself with other solutions)

      Regards

      David BEAL
      Consultant ERP Odoo


      Le ven. 2 mai 2025 à 23:57, Jerôme Dewandre <notifications@odoo-community.org> a écrit :

      Hello everyone,

      Thanks to your valuable feedback and suggestions, I’ve developed a dedicated ETL module for Odoo designed to handle large-scale data synchronization efficiently.

      The solution bypasses ORM bottlenecks using optimized SQL and batch processing, and integrates Polars and SQLAlchemy for fast data transformation.

      It supports millions of records and is ideal for daily sync with legacy systems (from SQLITE for now).

      The module is available here: https://github.com/cyberwave-odoo/odoo-etl

      I truly appreciate the community insights that shaped this project — thank you!

      Best regards,


      Jérôme



      On Wed, Aug 21, 2024 at 9:17 AM David Beal <notifications@odoo-community.org> wrote:
      Nice to see pandas run fast.

      For those for those that want run very very ... very fast consider to use polars


      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 21 août 2024 à 01:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.

      There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.

      On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:
      Hello,

      Thank you very much for your quick responses :) 

      Tom Blauwendraat: I am running on v16

      Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4

      Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action


      Daniel Reis: This is indeed the problem I encountered.


      Thank you all for your replies, it helps a lot :)

      Jérôme


      On Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:
      I would expect this code to just abort for a non trivial quantity of records.
      The reason why is that this is a single worker doing a single database transaction.
      So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
      And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.

      Going direct to the database can work if the data is pretty simple.
      It can work but it can also be a can of worms.

      One approach is to have an incremental approach to the data loading.
      In the past I have used external ETL tools or scripts to do this.
      Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
      https://github.com/OCA/queue/tree/16.0/base_import_async

      Thanks

      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]



      On 20/08/2024 16:32, Jerôme Dewandre wrote:
      Hello,

      I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

      It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

      I suppose the ORM might be an issue here. Potential workaround:

      1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
      2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
      3. Increase the CPU/RAM/Worker nodes
      4. Some better ideas?

      What would be the best way to go?

      A piece of my current test (df is a pandas dataframe containing the new events): 

      @api.model
          def create_events_from_df(self, df):
              Event = self.env['event.event']
              events_data = []
              for _, row in df.iterrows():
                  event_data = {
                      'location': row['location'],
                      'name': row['name'],
                      'date_begin': row['date_begin'],
                      'date_end': row['date_end'],
                  }
                  events_data.append(event_data)
             
              # Create all events in a single batch
              Event.create(events_data)

      Thanks in advance if you read this, and thanks again if you replied :)

      Jérôme

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by David BEAL - 10:26 - 7 May 2025
    • Re: Large Data Files
      Hi Jérome,

      Additionally you may reach more performance with https://github.com/yanyanren123hotmailcom/connectorx

      Here is the explanation

      I experimented successfully connectorx with polars (but not benchmark it myself with other solutions)

      Regards

      David BEAL
      Consultant ERP Odoo


      Le ven. 2 mai 2025 à 23:57, Jerôme Dewandre <notifications@odoo-community.org> a écrit :

      Hello everyone,

      Thanks to your valuable feedback and suggestions, I’ve developed a dedicated ETL module for Odoo designed to handle large-scale data synchronization efficiently.

      The solution bypasses ORM bottlenecks using optimized SQL and batch processing, and integrates Polars and SQLAlchemy for fast data transformation.

      It supports millions of records and is ideal for daily sync with legacy systems (from SQLITE for now).

      The module is available here: https://github.com/cyberwave-odoo/odoo-etl

      I truly appreciate the community insights that shaped this project — thank you!

      Best regards,


      Jérôme



      On Wed, Aug 21, 2024 at 9:17 AM David Beal <notifications@odoo-community.org> wrote:
      Nice to see pandas run fast.

      For those for those that want run very very ... very fast consider to use polars


      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 21 août 2024 à 01:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.

      There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.

      On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:
      Hello,

      Thank you very much for your quick responses :) 

      Tom Blauwendraat: I am running on v16

      Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4

      Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action


      Daniel Reis: This is indeed the problem I encountered.


      Thank you all for your replies, it helps a lot :)

      Jérôme


      On Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:
      I would expect this code to just abort for a non trivial quantity of records.
      The reason why is that this is a single worker doing a single database transaction.
      So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
      And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.

      Going direct to the database can work if the data is pretty simple.
      It can work but it can also be a can of worms.

      One approach is to have an incremental approach to the data loading.
      In the past I have used external ETL tools or scripts to do this.
      Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
      https://github.com/OCA/queue/tree/16.0/base_import_async

      Thanks

      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]



      On 20/08/2024 16:32, Jerôme Dewandre wrote:
      Hello,

      I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

      It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

      I suppose the ORM might be an issue here. Potential workaround:

      1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
      2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
      3. Increase the CPU/RAM/Worker nodes
      4. Some better ideas?

      What would be the best way to go?

      A piece of my current test (df is a pandas dataframe containing the new events): 

      @api.model
          def create_events_from_df(self, df):
              Event = self.env['event.event']
              events_data = []
              for _, row in df.iterrows():
                  event_data = {
                      'location': row['location'],
                      'name': row['name'],
                      'date_begin': row['date_begin'],
                      'date_end': row['date_end'],
                  }
                  events_data.append(event_data)
             
              # Create all events in a single batch
              Event.create(events_data)

      Thanks in advance if you read this, and thanks again if you replied :)

      Jérôme

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by David BEAL - 10:21 - 7 May 2025
    • Re: Large Data Files

      Hello everyone,

      Thanks to your valuable feedback and suggestions, I’ve developed a dedicated ETL module for Odoo designed to handle large-scale data synchronization efficiently.

      The solution bypasses ORM bottlenecks using optimized SQL and batch processing, and integrates Polars and SQLAlchemy for fast data transformation.

      It supports millions of records and is ideal for daily sync with legacy systems (from SQLITE for now).

      The module is available here: https://github.com/cyberwave-odoo/odoo-etl

      I truly appreciate the community insights that shaped this project — thank you!

      Best regards,


      Jérôme



      On Wed, Aug 21, 2024 at 9:17 AM David Beal <notifications@odoo-community.org> wrote:
      Nice to see pandas run fast.

      For those for those that want run very very ... very fast consider to use polars


      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 21 août 2024 à 01:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.

      There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.

      On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:
      Hello,

      Thank you very much for your quick responses :) 

      Tom Blauwendraat: I am running on v16

      Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4

      Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action


      Daniel Reis: This is indeed the problem I encountered.


      Thank you all for your replies, it helps a lot :)

      Jérôme


      On Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:
      I would expect this code to just abort for a non trivial quantity of records.
      The reason why is that this is a single worker doing a single database transaction.
      So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
      And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.

      Going direct to the database can work if the data is pretty simple.
      It can work but it can also be a can of worms.

      One approach is to have an incremental approach to the data loading.
      In the past I have used external ETL tools or scripts to do this.
      Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
      https://github.com/OCA/queue/tree/16.0/base_import_async

      Thanks

      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]



      On 20/08/2024 16:32, Jerôme Dewandre wrote:
      Hello,

      I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

      It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

      I suppose the ORM might be an issue here. Potential workaround:

      1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
      2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
      3. Increase the CPU/RAM/Worker nodes
      4. Some better ideas?

      What would be the best way to go?

      A piece of my current test (df is a pandas dataframe containing the new events): 

      @api.model
          def create_events_from_df(self, df):
              Event = self.env['event.event']
              events_data = []
              for _, row in df.iterrows():
                  event_data = {
                      'location': row['location'],
                      'name': row['name'],
                      'date_begin': row['date_begin'],
                      'date_end': row['date_end'],
                  }
                  events_data.append(event_data)
             
              # Create all events in a single batch
              Event.create(events_data)

      Thanks in advance if you read this, and thanks again if you replied :)

      Jérôme

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by "Jerôme Dewandre" <jerome.dewandre.mail@gmail.com> - 11:56 - 2 May 2025
    • Re: Large Data Files
      Nice to see pandas run fast.

      For those for those that want run very very ... very fast consider to use polars


      Regards

      David BEAL
      Consultant ERP Odoo


      Le mer. 21 août 2024 à 01:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.

      There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.

      On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:
      Hello,

      Thank you very much for your quick responses :) 

      Tom Blauwendraat: I am running on v16

      Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4

      Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action


      Daniel Reis: This is indeed the problem I encountered.


      Thank you all for your replies, it helps a lot :)

      Jérôme


      On Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:
      I would expect this code to just abort for a non trivial quantity of records.
      The reason why is that this is a single worker doing a single database transaction.
      So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
      And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.

      Going direct to the database can work if the data is pretty simple.
      It can work but it can also be a can of worms.

      One approach is to have an incremental approach to the data loading.
      In the past I have used external ETL tools or scripts to do this.
      Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
      https://github.com/OCA/queue/tree/16.0/base_import_async

      Thanks

      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]



      On 20/08/2024 16:32, Jerôme Dewandre wrote:
      Hello,

      I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

      It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

      I suppose the ORM might be an issue here. Potential workaround:

      1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
      2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
      3. Increase the CPU/RAM/Worker nodes
      4. Some better ideas?

      What would be the best way to go?

      A piece of my current test (df is a pandas dataframe containing the new events): 

      @api.model
          def create_events_from_df(self, df):
              Event = self.env['event.event']
              events_data = []
              for _, row in df.iterrows():
                  event_data = {
                      'location': row['location'],
                      'name': row['name'],
                      'date_begin': row['date_begin'],
                      'date_end': row['date_end'],
                  }
                  events_data.append(event_data)
             
              # Create all events in a single batch
              Event.create(events_data)

      Thanks in advance if you read this, and thanks again if you replied :)

      Jérôme

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by David BEAL - 09:16 - 21 Aug 2024
    • Re: Large Data Files
      Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.

      There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.

      On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:
      Hello,

      Thank you very much for your quick responses :) 

      Tom Blauwendraat: I am running on v16

      Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4

      Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action


      Daniel Reis: This is indeed the problem I encountered.


      Thank you all for your replies, it helps a lot :)

      Jérôme


      On Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:
      I would expect this code to just abort for a non trivial quantity of records.
      The reason why is that this is a single worker doing a single database transaction.
      So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
      And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.

      Going direct to the database can work if the data is pretty simple.
      It can work but it can also be a can of worms.

      One approach is to have an incremental approach to the data loading.
      In the past I have used external ETL tools or scripts to do this.
      Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
      https://github.com/OCA/queue/tree/16.0/base_import_async

      Thanks

      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]



      On 20/08/2024 16:32, Jerôme Dewandre wrote:
      Hello,

      I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).

      It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.

      I suppose the ORM might be an issue here. Potential workaround:

      1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)
      2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)
      3. Increase the CPU/RAM/Worker nodes
      4. Some better ideas?

      What would be the best way to go?

      A piece of my current test (df is a pandas dataframe containing the new events): 

      @api.model
          def create_events_from_df(self, df):
              Event = self.env['event.event']
              events_data = []
              for _, row in df.iterrows():
                  event_data = {
                      'location': row['location'],
                      'name': row['name'],
                      'date_begin': row['date_begin'],
                      'date_end': row['date_end'],
                  }
                  events_data.append(event_data)
             
              # Create all events in a single batch
              Event.create(events_data)

      Thanks in advance if you read this, and thanks again if you replied :)

      Jérôme

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by "Graeme Gellatly" <graeme@moahub.nz> - 01:56 - 21 Aug 2024

  • Visitors Database of Odoo Website Day 2024

    Hi,

    Hope all is well with you!

     

    We're offering a special deal: discounted cost and extra information.

    We're following up to see if you're interested in getting the Visitors/Attendees List.

     

    Event Details:

    Event Name: Odoo Website Day 2024

    Date:03 Oct 2024

    Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium

    Visitors/Attendees:5,000

                                         

    Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

     

    Could you let us know if you're interested? We'll then send you the discounted cost and more details.

     

    Waiting for your positive response.


    Thanks and Regards
    Ivy Rodriguez
    by Ivy.Rodriguez@galaxileadshq.com - 03:01 - 15 Aug 2024

    4 replies 4 replies

    • Re: Visitors Database of Odoo Website Day 2024
      Hello everyone,

      We are trying to find a way to stop receiving this kind of spam on the OCA Contributors Mailing List.

      Please, don't answer to this person by answering to its first email, this spams everyone in the mailing list.

      Thanks!
      Virginie Dewulf
      Executive Director
      +32 477 64 17 20


      Le ven. 16 août 2024 à 13:57, DIALLO Innah <notifications@odoo-community.org> a écrit :

      Hello,

      Thank you so much, but actually i am not interested, thank you very much.

      Have a nice day.

      Le jeu. 15 août 2024 à 13:02, Ivy.Rodriguez <notifications@odoo-community.org> a écrit :

      Hi,

      Hope all is well with you!

       

      We're offering a special deal: discounted cost and extra information.

      We're following up to see if you're interested in getting the Visitors/Attendees List.

       

      Event Details:

      Event Name: Odoo Website Day 2024

      Date:03 Oct 2024

      Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium

      Visitors/Attendees:5,000

                                           

      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Could you let us know if you're interested? We'll then send you the discounted cost and more details.

       

      Waiting for your positive response.


      Thanks and Regards
      Ivy Rodriguez

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Virginie Dewulf (OCA) - 02:30 - 16 Aug 2024
    • Re: Visitors Database of Odoo Website Day 2024

      Hello,

      Thank you so much, but actually i am not interested, thank you very much.

      Have a nice day.

      Le jeu. 15 août 2024 à 13:02, Ivy.Rodriguez <notifications@odoo-community.org> a écrit :

      Hi,

      Hope all is well with you!

       

      We're offering a special deal: discounted cost and extra information.

      We're following up to see if you're interested in getting the Visitors/Attendees List.

       

      Event Details:

      Event Name: Odoo Website Day 2024

      Date:03 Oct 2024

      Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium

      Visitors/Attendees:5,000

                                           

      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Could you let us know if you're interested? We'll then send you the discounted cost and more details.

       

      Waiting for your positive response.


      Thanks and Regards
      Ivy Rodriguez

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by hawa1 - 01:54 - 16 Aug 2024
    • Re: Visitors Database of Odoo Website Day 2024
      Hello,

      No, I am not interested, thank you very much.

      Have a nice day.


      El 15/08/2024 a las 15:02, Ivy.Rodriguez escribió:

      Hi,

      Hope all is well with you!

       

      We're offering a special deal: discounted cost and extra information.

      We're following up to see if you're interested in getting the Visitors/Attendees List.

       

      Event Details:

      Event Name: Odoo Website Day 2024

      Date:03 Oct 2024

      Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium

      Visitors/Attendees:5,000

                                           

      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Could you let us know if you're interested? We'll then send you the discounted cost and more details.

       

      Waiting for your positive response.


      Thanks and Regards
      Ivy Rodriguez

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      by Fernando - 01:00 - 16 Aug 2024
    • Re: Visitors Database of Odoo Website Day 2024

      How much ?


      On Thu, 15 Aug 2024, 20:02 Ivy.Rodriguez, <notifications@odoo-community.org> wrote:

      Hi,

      Hope all is well with you!

       

      We're offering a special deal: discounted cost and extra information.

      We're following up to see if you're interested in getting the Visitors/Attendees List.

       

      Event Details:

      Event Name: Odoo Website Day 2024

      Date:03 Oct 2024

      Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium

      Visitors/Attendees:5,000

                                           

      Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Could you let us know if you're interested? We'll then send you the discounted cost and more details.

       

      Waiting for your positive response.


      Thanks and Regards
      Ivy Rodriguez

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by milori2006 - 04:45 - 15 Aug 2024
  • pre-commit help
    I'm having trouble with pre-commit. Can someone give me a few tips?

    I tried to follow the instructions in the README for maintainer-tools:


    I installed maintainer-tools and activated the venv, then ran the following

    .../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always

    Still failing the pre-commit test on pull request.

    Maybe there is more documentation that I am missing?

    Matt

    by Matt - 11:00 - 14 Aug 2024

    3 replies 3 replies

    • Re: pre-commit help
      Not all the errors that precommit gives are automatically solved, some you have to solve them manually.

      Usually the precommit log as displayed on the PR is pretty clear about what the problem is.

      14 aug. 2024 23:01:57 Matt Taylor <notifications@odoo-community.org>:

      I'm having trouble with pre-commit. Can someone give me a few tips?

      I tried to follow the instructions in the README for maintainer-tools:


      I installed maintainer-tools and activated the venv, then ran the following

      .../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always

      Still failing the pre-commit test on pull request.

      Maybe there is more documentation that I am missing?

      Matt

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Tom Blauwendraat - 08:31 - 15 Aug 2024
    • Re: pre-commit help
      by Pedro M. Baeza - 11:45 - 14 Aug 2024
    • Re: pre-commit help
      To run pre-commit, you first need to install it:
      $ pip install pre-commit

      And then in (each) cloned repo, install the pre-commit hooks with:
      $ pre-commit install

      Now you can run :
      $ pre-commit run -a

      At least that's what works for me.

      --Daniel
       

      On 14/08/2024 22:01, Matt Taylor wrote:
      I'm having trouble with pre-commit. Can someone give me a few tips?

      I tried to follow the instructions in the README for maintainer-tools:


      I installed maintainer-tools and activated the venv, then ran the following

      .../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always

      Still failing the pre-commit test on pull request.

      Maybe there is more documentation that I am missing?

      Matt

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe


      --
      DANIEL REIS
      MANAGING PARTNER

      Meet with me.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]

      by Daniel Reis - 11:22 - 14 Aug 2024
  • Highlights on my contributions to Odoo Community Association
    Here is my experience with my first contribution to OCA:

    I hope it will be useful to the new contributors.

    Thanks all,
    by Mohamed Alkobrosly - 04:16 - 13 Aug 2024

    2 replies 2 replies

    • Re: Highlights on my contributions to Odoo Community Association
      Ok, it is really good and useful to refer to all the points that I still miss.

      Some of this information is very new to me like mentioning the PR in a comment of the "Migration to version 17.0 #1446" PR.

      In addition to this, I am not aware of what still missing to merge the PR, I only know that there should be two reviews, only!

      But if there is still something that I do not know please help me to get it and fill the gap.

      As all of that will be mentioned on the same blog post, and we all will benefit and the rest of the world.

      Thanks.

      On Tue, Aug 13, 2024 at 5:51 PM Radovan Skolnik <notifications@odoo-community.org> wrote:

      Hi,


      first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.


      I did quick review of your blog post. Few suggestions:

      *) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:


      *) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.

      *) "(7)    After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.

      *) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.

      *) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0"  - in your case https://github.com/OCA/product-attribute/issues/1446


      One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.


      So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.


      Best luck and regards


          Radovan Skolnik


      On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:

      > Here is my experience with my first contribution to OCA:

      > https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo

      > .html [1] I hope it will be useful to the new contributors.

      > Thanks all,

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [2]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]

      >

      >

      >

      > [1]

      > https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo

      > .html [2] https://odoo-community.org/groups/contributors-15

      > [3] https://odoo-community.org/groups?unsubscribe



      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Mohamed Alkobrosly - 05:11 - 13 Aug 2024
    • Re: Highlights on my contributions to Odoo Community Association

      Hi,


      first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.


      I did quick review of your blog post. Few suggestions:

      *) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:


      *) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.

      *) "(7)    After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.

      *) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.

      *) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0"  - in your case https://github.com/OCA/product-attribute/issues/1446


      One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.


      So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.


      Best luck and regards


          Radovan Skolnik


      On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:

      > Here is my experience with my first contribution to OCA:

      > https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo

      > .html [1] I hope it will be useful to the new contributors.

      > Thanks all,

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [2]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]

      >

      >

      >

      > [1]

      > https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo

      > .html [2] https://odoo-community.org/groups/contributors-15

      > [3] https://odoo-community.org/groups?unsubscribe



      by Radovan Skolnik - 04:50 - 13 Aug 2024

      1 attachments 1 attachments

      image
  • Odoo Experience Exhibition 2024, Visitors Data

    Hi, 

    Hope you are doing well !!

    To help you, we are offering detailed visitor data collected for  the exhibition

     

    We are following up to confirm if you are interested in acquiring the Visitors/Attendees List. 

    Event Name   :   Odoo Experience Exhibition 2024

    Date                    :  02 - 04 Oct 2024

    Location           :    Brussels Expo - Exhibition Center, Brussels, Belgium

    Counts              :  4,300

     

    If you are interested in acquiring the Exact list, we can Send you the Discounted cost and real additional details.

     

    Each record of the list contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

     

    Exhibitors who utilized our visitor data in previous events have seen a significant increase in lead conversion rates and tailored their follow-up strategies effectively. By analyzing this data, you can better understand your audience, refine your marketing approach, and follow up with highly qualified leads.

     

    We are looking forward to hearing from you.

     If you interested to take visitors list, please reply to me has ” YES  INTRESTED “

     

    Thanks & Regards,

    Eliza

    Market Analyst.

    by "Amelia" <amelia.dataprovider@gmail.com> - 04:56 - 12 Aug 2024

    3 replies 3 replies

    • Re: Odoo Experience Exhibition 2024, Visitors Data
      YES  INTRESTED

      Best regards,
      linkedin

      Morgane Goujon

      Développeuse Logiciel

      Scalizer


      emailAddress
      		morgane@scalizer.fr
      website
      		www.scalizer.fr
      address
      		13 rue Crucy, 44000 Nantes



      Le jeu. 22 août 2024 à 10:27, Michel Stroom <notifications@odoo-community.org> a écrit :
      YES  INTERESTED

      Thanks for sharing Eliza


      Best regards,

      Michel Stroom

      -- 

      Office Everywhere
      t      : +31 6 53360677
      e: mstroom@office-everywhere.com
      w: Office-Everywhere.com

      Office
      Ramstraat 31-33
      3581 HD Utrecht

      Netherlands 

      On 12 Aug 2024, at 16:57, Amelia <notifications@odoo-community.org> wrote:


      Hi, 

      Hope you are doing well !!

      To help you, we are offering detailed visitor data collected for  the exhibition

       

      We are following up to confirm if you are interested in acquiring the Visitors/Attendees List. 

      Event Name   :   Odoo Experience Exhibition 2024

      Date                    :  02 - 04 Oct 2024

      Location           :    Brussels Expo - Exhibition Center, Brussels, Belgium

      Counts              :  4,300

       

      If you are interested in acquiring the Exact list, we can Send you the Discounted cost and real additional details.

       

      Each record of the list contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Exhibitors who utilized our visitor data in previous events have seen a significant increase in lead conversion rates and tailored their follow-up strategies effectively. By analyzing this data, you can better understand your audience, refine your marketing approach, and follow up with highly qualified leads.

       

      We are looking forward to hearing from you.

       If you interested to take visitors list, please reply to me has ” YES  INTRESTED “

       

      Thanks & Regards,

      Eliza

      Market Analyst.


      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by morgane - 12:31 - 22 Aug 2024
    • Re: Odoo Experience Exhibition 2024, Visitors Data
      YES  INTERESTED

      Thanks for sharing Eliza


      Best regards,

      Michel Stroom

      -- 

      Office Everywhere
      t      : +31 6 53360677
      e: mstroom@office-everywhere.com
      w: Office-Everywhere.com

      Office
      Ramstraat 31-33
      3581 HD Utrecht

      Netherlands 

      On 12 Aug 2024, at 16:57, Amelia <notifications@odoo-community.org> wrote:


      Hi, 

      Hope you are doing well !!

      To help you, we are offering detailed visitor data collected for  the exhibition

       

      We are following up to confirm if you are interested in acquiring the Visitors/Attendees List. 

      Event Name   :   Odoo Experience Exhibition 2024

      Date                    :  02 - 04 Oct 2024

      Location           :    Brussels Expo - Exhibition Center, Brussels, Belgium

      Counts              :  4,300

       

      If you are interested in acquiring the Exact list, we can Send you the Discounted cost and real additional details.

       

      Each record of the list contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Exhibitors who utilized our visitor data in previous events have seen a significant increase in lead conversion rates and tailored their follow-up strategies effectively. By analyzing this data, you can better understand your audience, refine your marketing approach, and follow up with highly qualified leads.

       

      We are looking forward to hearing from you.

       If you interested to take visitors list, please reply to me has ” YES  INTRESTED “

       

      Thanks & Regards,

      Eliza

      Market Analyst.


      by Michel Stroom - 10:26 - 22 Aug 2024
    • Re: Odoo Experience Exhibition 2024, Visitors Data
      YES INTERESTED

      Cordialement, Best regards,




      Karim DINMAMODE

      — Associé

                

      Tél :   +33 (0)7 81 51 75 24

                 +261 (0)34 20 780 30

      Mail :  karim@nexources.com

      Map :  22 Rue Andrianary Ratianarivo

                  Immeuble ex-Teillet Labrousse

                  Antananarivo Madagascar


      www.nexources.com 

                                                                                                                                                                                                               



      Le lun. 12 août 2024 à 17:57, Amelia <notifications@odoo-community.org> a écrit :

      Hi, 

      Hope you are doing well !!

      To help you, we are offering detailed visitor data collected for  the exhibition

       

      We are following up to confirm if you are interested in acquiring the Visitors/Attendees List. 

      Event Name   :   Odoo Experience Exhibition 2024

      Date                    :  02 - 04 Oct 2024

      Location           :    Brussels Expo - Exhibition Center, Brussels, Belgium

      Counts              :  4,300

       

      If you are interested in acquiring the Exact list, we can Send you the Discounted cost and real additional details.

       

      Each record of the list contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.

       

      Exhibitors who utilized our visitor data in previous events have seen a significant increase in lead conversion rates and tailored their follow-up strategies effectively. By analyzing this data, you can better understand your audience, refine your marketing approach, and follow up with highly qualified leads.

       

      We are looking forward to hearing from you.

       If you interested to take visitors list, please reply to me has ” YES  INTRESTED “

       

      Thanks & Regards,

      Eliza

      Market Analyst.

      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe

      by Karim Dinmamode - 05:08 - 12 Aug 2024
  • Odoo-Community

    Hi Odoo-Community ,

    Just wanted to confirm if there's any update on your interest in acquiring the Registrants/Attendees list..

    ·           Odoo Experience Exhibition 2024 (Brussels, Belgium, 02 - 04 Oct 2024)

    ·          5000+ Contacts

     

    I’m waiting for your response so i can let you know the price & additional more information.

     

    Hoping to receive your reply soon.

     

    Regards,

    Isla – Business Executive

     

    by "Isla Ruth" <isla.ruth@digimarket.services> - 06:21 - 9 Aug 2024

    1 replies 1 replies

  • upgrade "product_pricelist_fixed_currency_rate" from 16.0 to 17.0
    Dear all OCA members, I am delighted to say that I have just committed my first contribution to your organization.

    I succeeded after a huge effort, I was tracking the errors that prohibited me from doing the commit successfully.

    I found that there is a syntax error in the code written in the documentation for upgrading from v16 to v17.

    There was a dependency that I had to install manually.

    But I will write about my experience in my blog hoping that it helps me in the future and anybody who needs to contribute.

    Here is my successful pull request:
    https://github.com/OCA/product-attribute/pull/1706

    Thanks to everybody who answered my questions and thanks to you all.
    by Mohamed Alkobrosly - 12:56 - 9 Aug 2024

    3 replies 3 replies

  • OCA Volunteers Needed - Odoo Community Days India - 23-24 August.
    Hello OCA Contributors.

    I hope this finds you well.

    We have a booth at the upcoming India Odoo Community Days.
    We've had some awesome support from the Serpent and BizzApp teams who have volunteered to help on the stand - we are hoping we could get a few more volunteers from our community to put in an hour or two over the two days.

    If you are available to help out - please add your details to this spreadsheet.

    The task at hand is to help promote the OCA within India and answer any questions people may have about the OCA.

    Alternatively, if you are new to the OCA and/or want to find out more about the OCA, come and visit our stand to have a chat in person - we are at     E1S33.

    The great news is the event is free and open to the public! The Basic Pass gives access to Conferences, Exhibition & Talks during event days (August 23-24, 2024). 

    Our OCA community looks forward to seeing you.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    odooindia.png
    by Rebecca Gellatly (OCA) - 12:10 - 9 Aug 2024

    1 attachments 1 attachments

    odooindia.png
  • Readme file genetating fails
    while running this command:
    pre-commit run -a

    to upgrade a module from v16 to v17 I got that error:

    Generate addons README files from fragments..............................Failed
    - hook id: oca-gen-addon-readme
    - files were modified by this hook

    and my name as a contributor is not added
    by Mohamed Alkobrosly - 11:51 - 8 Aug 2024
  • pre-commit run -a failed
    I wonder why this error arises up, and how can it be solved:

    Generate addons README files from fragments..............................Failed
    - hook id: oca-gen-addon-readme
    - exit code: 1


    File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['ar', 'x', '/home/kobros/Documents/odoo/product-attribute/pandoc-3.3-1-amd64.deb']' returned non-zero exit status 1.

    I hope someone help me to solve the issue to upgrade from v16 to v17
    by Mohamed Alkobrosly - 08:50 - 8 Aug 2024

    1 replies 1 replies

  • migration from 16.0 to 17.0
    Hi there!

    I followed the instructions to migrate from v16.0 to v17.0.

    I want to make sure I did it correctly.

    Here is the link to compare v16.0 to v17.0

    But I couldn't make a pull request, is it because I already pushed the branch to your repository?

    Here is also the link to my branch:
    https://github.com/kobros-tech/product-attribute/tree/17.0-mig-product_pricelist_fixed_currency_rate

    Thanks for your help.
    by Mohamed Alkobrosly - 03:01 - 6 Aug 2024