Hi Sabine,
I proposed a solution, and included an example implementation and asked for review here in February of 2016. Re: Time millisecondClockValue (was: The Trunk: Morphic-mt.1080.mcz) http://forum.world.st/Time-millisecondClockValue-was-The-Trunk-Morphic-mt-1080-mcz-tp4877661p4877918.html But I received no feedback whatsoever. I'm not particularly excited by doing all the heavy lifting while the unethical pass off my work as theirs, and contribute nothing back. But that's where we are.
On Wed, Aug 28, 2019 at 11:55 PM Sabine notifications@github.com wrote:
I want to bring this up again. A summary of the history of this thread is that on windows, the time of the Image (Time now) gets a gap to NTP Time which grows by several seconds each day.
This has already be discussed here
http://forum.world.st/Time-millisecondClockValue-was-The-Trunk-Morphic-mt-10... and here http://forum.world.st/Windows-image-has-system-time-delay-td5096643.html#a50...
I start my production server images new each week since 6 months now because of this issue.
And after a discussion at ESUG yesterday in the evening here again: yes, I could find ways for workarounds. But I think this is a serious issue which should be fixed because if you can not rely on the time in the image you can get various problems.
I have put a link to this issue here pharo-project/opensmalltalk-vm#12 https://github.com/pharo-project/opensmalltalk-vm/issues/12 (did not know that it is a vm issue when reporting it 6 months ago).
I really would appreciate having a good solution for this.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pharo-project/pharo/issues/2792?email_source=notifications&email_token=ADY5VUCTTRFHRX2ZHD5K7NTQG5XHTA5CNFSM4G5CDDJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5NOTNQ#issuecomment-526051766, or mute the thread https://github.com/notifications/unsubscribe-auth/ADY5VUGI4LUMPBSNSN62NGTQG5XHTANCNFSM4G5CDDJQ .