Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #29633 Meilisearch: 0.29.2 -> 0.30.0
    Actions
    Infos
    #29633
    Thomas Gerbet (tgerbet)
    2022-12-01 10:53
    2022-11-29 11:22
    31230
    Details
    Meilisearch: 0.29.2 -> 0.30.0

    Release notes:
    https://github.com/meilisearch/meilisearch/releases/tag/v0.30.0

    Full text search
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2022-12-01
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #29213 Tuleap Releases 14.3 Delivered 2022-12-08 10:41 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #29633

    Git commit

    tuleap/tuleap/stable

    Closes request #29633 Meilisearch: 0.29.2 -> 0.30.0 10129b7124
    User avatar Thomas Gerbet (tgerbet) , 2022-11-29 11:22
    Merge commit 'refs/changes/23/27323/1' of ssh://gerrit.tuleap.net:29418/tuleap 8eb86dd015
    User avatar Manuel Vacelet (vaceletm) , 2022-12-01 10:52
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2022-11-29 18:34

    To follow up with the discussion in the PR updating the doc: https://github.com/Enalean/tuleap-documentation-en/pull/1077#discussion_r1034991571

    I would suggest to better catch this situation in Tuleap to limit the amount of surprise and give a clear situation in the interface like "Search not available, re-index needed".

    Not really sure how to do that in a clean way. From Tuleap PoV we cannot really tell the server is down because it was not able to start due to outdated or because of something else.