Page MenuHomeSoftware Heritage

api/server: Fix remote search server when using memory backend
ClosedPublic

Authored by anlambert on Thu, Sep 15, 2:31 PM.

Details

Summary

It can be useful to use a remote search server using the memory backend,
for instance in the docker environment to avoid spawning a costly
elasticsearch instance.

As this was never tested, there was an issue when trying to start
such remote search server so fix it and add tests.

Diff Detail

Repository
rDSEA Archive search
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Build is green

Patch application report for D8485 (id=30563)

Rebasing onto 445f62d0ee...

Current branch diff-target is up to date.
Changes applied before test
commit 977938aa114e037ec5c00f5767e98f0587c1eca4
Author: Antoine Lambert <anlambert@softwareheritage.org>
Date:   Thu Sep 15 14:27:44 2022 +0200

    api/server: Fix remote search server when using memory backend
    
    It can be useful to use a remote search server using the memory backend,
    for instance in the docker environment to avoid spawning a costly
    elasticsearch instance.
    
    As this was never tested, there was an issue when trying to start
    such remote search server so fix it and add tests.

See https://jenkins.softwareheritage.org/job/DSEA/job/tests-on-diff/339/ for more details.

This revision is now accepted and ready to land.Thu, Sep 15, 3:33 PM