Object store mtime is alsways '0001-01-01T00:00:00Z'

[fsievers]

Observed behavior

When doing a watch or requesting info about an object from the object store, the mtime is always set to '0001-01-01T00:00:00Z'.

Example (typescript):

import { connect } from "@nats-io/transport-node";

import { jetstream } from "@nats-io/jetstream";
import { Objm } from "@nats-io/obj";

async function main() {
    try {
        const nc = await connect({ servers: "localhost" });
        const js = jetstream(nc, { timeout: 10000 });
        const objm = new Objm(js);
        const os = await objm.open("sample");

        const watcher = await os.watch({ includeHistory: true });

        for await (const entry of watcher) {
            console.log(entry);
        }

        await nc.close();
    } catch (err) {
        console.log(`Some error: ${err}`);
    }
}

await main();

The output is:

{
  name: 'something-one',
  options: { max_chunk_size: 131072 },
  bucket: 'sample',
  nuid: 'oWRfe1FNB5IykFUFvvpFTy',
  size: 542850,
  mtime: '0001-01-01T00:00:00Z',
  chunks: 5,
  digest: 'SHA-256=mT0zapKIRNt6BNC1i3KDVjzgvhm3clbgG-GcQbxyjUQ=',
  isUpdate: false
}
{
  name: 'something-twp',
  options: { max_chunk_size: 131072 },
  bucket: 'sample',
  nuid: '7OaaaiDsfg9sFjlOAobPWK',
  size: 5971143,
  mtime: '0001-01-01T00:00:00Z',
  chunks: 46,
  digest: 'SHA-256=GdBhynQjYs48FVOghB7BvpwfDYbWo5eZVpv_ONoXZL4=',
  isUpdate: true
}

Expected behavior

I expect to get a proper modification time in the result.

Server and client version

Server: 2.12.4
@nats-io/nats-core: 3.3.1
@nats-io/obj: 3.3.1
@nats-io/transport-node: 3.3.1

Host environment

No response

Steps to reproduce

No response

[fsievers]

Ok, I took some time to find the problem in the code. But in the end it's the nats cli command. If you do a nats object put … the modification time does not get set. Which leads to the undefined mtime. That seems to be converted to '0001-01-01…' by the nats server when the info for an item gets requested.

If I use the JS or Rust library to put some data, the mtime will be set and get correctly.

What confuses me is that the nats cli tool always shows the time column with the modification time that is also somewhere in the datastream and the JS and Rust library rely exclusively on the metadata mtime.

[derekcollison]

Looping in @ripienaar since you mention the cli..

[ripienaar]

I looked at this yesterday I think its a nats.go thing :)