Skip to content
Snippets Groups Projects
  1. Sep 04, 2024
  2. Aug 30, 2024
  3. Aug 29, 2024
  4. Aug 28, 2024
  5. Aug 27, 2024
  6. Aug 22, 2024
  7. Aug 21, 2024
  8. Aug 20, 2024
  9. Aug 13, 2024
    • David Douard's avatar
      Add a sync_masking_mailmaps admin command · 0f8cf67a
      David Douard authored
      This command will copy all the active mailmaps in the masking proxy DB
      which dsn is given as argument.
      
      It is similar to the (now deprecated) sync_mailmaps command, but since
      it does not modify the Person table of the storage any more, it does not
      need the timestamp-based detection to determine which entries are to be
      enabled or disabled; it simply rewrite the whole displayname table
      every time it's called, if need be.
      
      A '--force' option allows to enforce rewrite the whole table even if no
      update has been detected in the displayname database.
      0f8cf67a
    • David Douard's avatar
      Split test_mailmap in 2 parts · 1aaaef12
      David Douard authored
      Extract tests for (soon to be legacy) sync_mailmap related fatures in a
      dedicated test file.
      1aaaef12
    • David Douard's avatar
      a136fdfb
  10. Aug 05, 2024
  11. Jul 22, 2024
  12. Jul 16, 2024
  13. Jul 12, 2024
  14. Jul 08, 2024
  15. Jul 04, 2024
    • Antoine Lambert's avatar
      save_bulk: Add new endpoints to manage bulk archival of origins · 8ac56399
      Antoine Lambert authored
      Add a new django application to manage bulk archival of origins.
      
      As a first step, add a new Web API endpoint to submit a list of origins
      to archive and a new endpoint enabling to retrieve that list of origins
      in a paginated way.
      
      The Web API endpoint enables an user with specific permission to submit
      a list of origin URLs and their visit types through a POST request.
      The endpoint performs some basic checks on the received origins data to
      verify origin URLs are well formed but also if provided visit types are
      supported.
      
      If provided origins data are valid, the request is accepted and a oneshot
      scheduler task is created to execute the bulk-save lister. That lister will
      consume that list of origins, perform some extra but more costly checks on
      them and those validated by it will then be scheduled for loading into the
      archive.
      
      If some origins data are not valid, the request is rejected and a list of
      bogus origins along the reasons of their rejections is returned to the user
      in the Web API response.
      
      The other endpoint is dedicated to be consumed by the bulk-save lister to
      retrieve the submitted origins list in a paginated way. It is better to
      store submitted origins data on the webapp side to avoid bloating the
      scheduler database with large JSON documents in case a big list of origins
      is submitted by an user.
      
      Related to #4802.
      8ac56399
    • Antoine Lambert's avatar
    • Antoine Lambert's avatar
      48c6fd33
  16. Jul 02, 2024
Loading