Subj : Commit f9ad15e8 might need more work :)
To   : Digital Man
From : deon
Date : Mon Dec 23 2024 23:53:16

  Re: Commit f9ad15e8 might need more work :)
  By: Digital Man to deon on Mon Dec 23 2024 01:03 am

Howdy,

 > How are you posting that message? When I post messages using the terminal
 > server or using smbutil to import a message, I'm seeing the bit-encoded date
 > values in hex (with the '0' initial nibble).

I answered this in another message - I'm using save_msg() with hdr.date = rfc822 date (it works, even with the timezone). That must not be using your new format for when_written_time yet.

I figured out why the strftime was messing up (when I first started using hdr.date to save messages that triggered this timezone discussion) - I had logging on and noticed it changed after 1pm - I was using %I instead of %H (which is what I always use, dont know where %I came from or why I used it).

 > I'm confused about your time zone settings and systems, so I'm not really
 > following.

OK, I'm sorry for messing you around, and thanks for looking at it. Looks like I sent you on a red herring.

I run sbbs in docker, and I have 2 containers running sharing the same config and dirs (one sees a different login.js/logon.js that launches my ansitex shell on connection).

While I thought I had shutdown one container while posting these messages about the date/times - I just discovered I hadnt - and it's OS was still configured with UTC+11:00 (which explains where the aus date strings must have coming from). Probably would have discovered it quicker if I had change scfg -> System -> Local Time Zone to Auto after updating ;)

My other container (which is likely I wasnt connected to) was configured to PST, and I was logging the console, so I saw the terminal server recycle when playing with scfg (setting PST) and the logs when binkit was triggered sending messages.

So, I killed everything, and started just the PST container, posted messages and they are infact the correct time string - for both the when*time values. When using save_msg() with hdr.date, it doesnt use your new when_written_time encoding though.

When I changed the OS back to AEDT (and I'm now using the Auto Time zone - winner :), the rendering of the message showed the wall clock time that you were after, and rendered the correct "minutes ago" age message.

Sorry for the run around - On the upside, I understand sync's internals better ;)


....лоеп

---
 ю Synchronet ю AnsiTEX bringing back videotex but with ANSI
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.