0007122: clarify Timestamp precision

ID	Project	Category	View Status	Date Submitted	Last Update
0007122	Taler	documentation	public	2021-12-09 11:52	2022-11-04 19:53

Reporter	Antoine A	Assigned To	Christian Grothoff	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	git (master)
Target Version	0.9	Fixed in Version	0.9

Summary	0007122: clarify Timestamp precision
Description	Based on the current documentation (https://docs.taler.net/core/api-common.html#tsref-type-Timestamp), timestamp consists of milliseconds since epoch or the special value 'never'. In practice, taler-exchange-wire-gateway-client refuse timestamps that are not rounded to second as a protocol violation, this behavior needs to be clarified.
Tags	No tags attached.

Date Modified	Username	Field	Change
2021-12-09 11:52	Antoine A	New Issue
2021-12-09 11:52	Antoine A	Status	new => assigned
2021-12-09 11:52	Antoine A	Assigned To	=> Stefan
2021-12-11 18:50	Christian Grothoff	Assigned To	Stefan => Christian Grothoff
2021-12-15 07:54	Christian Grothoff	Status	assigned => informing
2021-12-15 07:54	Christian Grothoff	Resolution	open => fixed
2021-12-15 07:54	Christian Grothoff	Fixed in Version	=> 0.9
2021-12-15 07:54	Christian Grothoff	Note Added: 0018572
2021-12-15 07:54	Christian Grothoff	Product Version	=> git (master)
2021-12-15 07:54	Christian Grothoff	Target Version	=> 0.9
2022-11-04 19:53	Christian Grothoff	Status	informing => closed

Christian Grothoff 2021-12-15 07:54 manager ~0018572	Latest code moves all the JSON absolute time objects to timestamps with t_s instead of t_ms. Also modifies relative time (in the very few places where it exists) to microseconds.