Skip to content

Sometimes deposits are not marked as validated even when document is created #925

@PascalRepond

Description

@PascalRepond

Bug description:

In some instances (to be specified), the validation of a deposit creates a document but does not mark the corresponding deposit as validated. This can lead to a double validation and a document created twice.

Expected behavior:

When validating a deposit and creating a document, the deposit should always be marked as validated.

Example:
Document https://folia.unifr.ch/manage/records/documents/detail/324501 has been created
But the corresponding deposit is still "to be validated" : https://folia.unifr.ch/manage/deposit/324490/create

Steps to Reproduce:

Could not reproduce as it is a puncutal problem:

Verify https://github.com/rero/sonar/blob/staging/sonar/modules/deposits/rest.py#L201-L235

Context

This could be caused by an error during deposit reindexing, see SONAR-N0 (Sentry).
On validation, the system dumps all document resolved index fields. If there are more than 1000 fields, there is an ES error. The document is created, but the deposit is not validated!

Server:

  • production (folia)

v1.8.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugBreaks something but is not blockingclient request

    Type

    No type

    Projects

    Status

    Product Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions