[
https://issues.apache.org/jira/browse/PROTON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718312#comment-16718312
]
Alan Conway edited comment on PROTON-1981 at 12/12/18 1:08 AM:
---------------------------------------------------------------
C++ timestamp::now() implementation is definitely faulty. Annoying portability
dance required, see
https://github.com/alanconway/qpid-proton/blob/master/c/src/platform/platform.c#L55
In C\+\+11 we could use std::chrono but as long as we have to handle C\+\+03 I
think we should do it the smelly old way.
was (Author: aconway):
C++ timestamp::now() implementation is definitely faulty. Annoying portability
dance required, see
https://github.com/alanconway/qpid-proton/blob/master/c/src/platform/platform.c#L55
In C++11 we could use std::chrono but as long as we have to handle C++03 I
think we should do it the smelly old way.
> Wrong posix time for pn_proactor_now()
> --------------------------------------
>
> Key: PROTON-1981
> URL: https://issues.apache.org/jira/browse/PROTON-1981
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
> Affects Versions: proton-c-0.26.0
> Reporter: Cliff Jansen
> Assignee: Cliff Jansen
> Priority: Major
>
> Uses MONOTONIC instead of REALTIME, hence not anchored to UNIX epoch as per
> AMQP standard.
>
> Used by proton::timestamp::now()
>
> Can take you back to 1970 on Centos7. Other time travel destinations
> possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
