fc::time_point_sec::to_iso_string is broken

[pmconrad]

time_point_sec internally uses an unsigned int to count seconds from epoch, like unix time. That means it is impossible to represent dates before 1970-01-01. Still, we sometime see dates before that in JSON output.

Probably a bug in boost::posix_time, have received a report that it's fixed in Boost-1.64. This ticket is for tracking and testing.

CORE TEAM TASK LIST

• Evaluate / Prioritize Feature Request
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
  • Assigned: @cogutvalera
  • Estimated: 1 hour (paid: Core Team Weeks 30-31)
• Perform QA/Testing
• Update Documentation

[cifer76]

so this issue it to be resolved by upgrading to boost-1.64?

[jmjatlanta]

Out with one problem, in with another. Boost 1.64 fixes the issue, but Bitshares is not compatible with Boost 1.64 yet.

A stop-gap fix may be to patch a 1.63 or earlier version of Boost. I haven't looked into the issue too deeply.

[abitmore]

Perhaps back-port something from boost 1.64. Or fix it another way.

Note: when querying different API nodes running with or without this issue fixed, will get different results. Some client applications may be broken due to this.

[abitmore]

Or just document it.

Update: created issue #881 for documentation.