Skip to content

views' timestamp loses tz info when run in HTTP or cli.py #312

Closed

Description

@keighrim

Bug Description

When a view is generated via the regular annotate() wrapper (used in cli.py and HTTP ) , the "run ID" (#269 ) re-write the timestamp but without timezone information as fixed in clamsproject/mmif-python#368

Reproduction steps

Run any app uses (e.g., SWT v9) clams-python 1.4.0 (2025 Nov) -- 1.8.0 , and check the timestamp value in the view's metadata.

  "timestamp": "2026-09-06T16:38:28.203289",

Expected behavior

the value should be Z part . The mmif-python side added this in 2026 Feb, but clams-python side somehow have implemented its own timestamping code and wasn't updates along with clamsproject/mmif-python#368.

Log output

Screenshots

No response

Additional context

Proper fix should be, instead of maintaining its own timestamping code in clams-python, capturing the timestamp from the first view of the current run and rewrite other following views (if any) with the first view's timestamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🐛BSomething isn't working

    Type

    No type

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions