Project

General

Profile

Actions
Copy link

Bug #14595

closed

[API] logs.event_at has wrong timestamp

Added by Tom Clegg over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Peter Amstutz
Category:
API
Target version:
2018-12-21 Sprint
Story points:
-
Release:
Arvados v1.4 - Q1/Q2 2019
Release relationship:
Auto

Description

Some updates generate rows in the logs table with event_at set to the time of a previous update, not the one being logged:
  • logs.event_at is populated from object_being_updated.modified_at (not db_current_time like you might guess)
  • object_being_updated.modified_at is not updated when the updates are saved inside a leave_modified_user_alone block
Either one of these should fix it:
  • Use db_current_time for the log entry
  • Revert the part of #13168 that avoids updating modified_at. (The original premise of #13168 was to stop changing modified_by_user_uuid. I don't see anything in the commit messages or on the ticket explaining why we stopped changing modified_at as well -- perhaps we didn't need to?)

Subtasks 1 (0 open — 1 closed)

Task #14609: Review 14595-leave-modified-atResolvedPeter Amstutz12/13/2018Actions

Related issues

Related to Arvados - Bug #13168: [API] state/priority-change triggers should not change container request modified_by_user_uuid to rootResolvedLucas Di Pentima03/29/2018Actions
Actions
Copy link

Also available in: Atom PDF