Ticket #3849 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

bin/issues_audit makes changes to (some?) eprints on every run

Reported by: tmb Owned by:
Priority: Priority Fix Milestone: 3.2.4
Component: - Version: 3.2
Severity: major Keywords:
Cc:

Description (last modified by tmb) (diff)

Seeing some eprint records with revision numbers into high 500s - investigation shows bin/issues_audit causing new revision.

Examples seen:

  • item with autoresolved issue, issues_audit updates autoresolved timestamp (=> new revision) on every subsequent run
  • item with no issues in lifetime, issues_audit causes lastmod update on every run(!)

May be local aberration

Change History

Changed 4 years ago by tmb

  • description modified (diff)

Changed 4 years ago by tmb

  • priority changed from unset to Priority Fix
  • version changed from 3.1 to 3.2
  • severity changed from normal to major
  • milestone changed from EPrints 3.2.x (general bugs/features for 3.2) to 3.2.4

Changed 4 years ago by tdb01r

Use r5736 to work out what's going wrong.

On ECS "fileinfo" was being set twice on commit: once by automatic_fields.pl and back to the original value by commit(). This caused ghost revisions.

With r5736 the fields that were changed (hence trigger a revision) will be stored in the history "details" field. Ideally we would show the list of fields changed with workflow links on the History tab ...

This may be resolved by r5730 that modifies EPrints to only call fileinfo() and automatic_fields() if an existing field has changed, rather than on every commit.

Changed 4 years ago by tdb01r

  • status changed from new to closed
  • resolution set to fixed

Closing this as it seems to be a bug in repository configurations. The bigger change (3.3) will reduce the vector for this mistake.

Note: See TracTickets for help on using tickets.