Inconsistency in date/times

[paulsaxe]

When I add a job from outside the Dashboard I use simple datetimes in UTC:

            with seamm_datastore.session_scope(db.Session) as session:
                job = db.Job.create(
                    job_id,
                    flowchart_path,
                    project_names=data["projects"],
                    path=wdir,
                    title=data["title"],
                    description="Run from the command-line",
                    submitted=current_time,
                    started=current_time,
                    parameters={"cmdline": []},
                    status="started",
                )
                session.add(job)

However, when I update the job after completion, the time to pass is ... different! This wonderful construct works:

                # current_time = datetime.datetime.now(datetime.timezone.utc)                                                                                                     

                # At the moment update takes weird numbers!                                                                                                                       
                now = datetime.datetime.now().astimezone()
                dt = now.utcoffset().total_seconds()
                current_time = (time.time() - dt) * 1000

                # Add to the database                                                                                                                                             
                ...
                with seamm_datastore.session_scope(db.Session) as session:
                    job = db.Job.update(
                        job_id, finished=current_time, status=data["state"]
                    )

This appears to be because the code in Job (models.py) is this

        for k, v in update_dict.items():
            if k == "submitted" or k == "finished" or k == "started":
                if v:
                    update_dict[k] = datetime.fromtimestamp(v / 1000)
                else:
                    update_dict[k] = None

Which seems to be 1000 times a timestamp. I presume this has something to do with the Web side of things, but it is certainly awkward for the job side. Would it be possible to check the type of the value v and use as-is if it is a datetime? Would a UTC datetime then give a reasonable time in the Web page?

[paulsaxe]

Hmmm. current_time got lost in the first code snippet. It is the same as the commented out line just below, in the 2nd snippet.