Closed Bug 944881 Opened 11 years ago Closed 11 years ago

Gaia should interpret timestamps as long-long numbers

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(blocking-b2g:1.3+, b2g-v1.3 fixed)

RESOLVED FIXED
blocking-b2g 1.3+
Tracking Status
b2g-v1.3 --- fixed

People

(Reporter: airpingu, Assigned: steveck)

References

Details

Attachments

(1 file, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #939302 +++

Bug 939302 is going to change all the timestamps to be long-long numbers. Gaia needs to have corresponding changes to avoid breaking the backward compatibility.

This one should be marked as V1.3 because it blocks Bug 939302 which is a blocker of V1.3.
Attached patch Patch (WIP) (obsolete) — Splinter Review
Hi Steve,

As title, we are going to change all the timestamps to be long-long numbers due to bug 939302, including {sms,mms}timestamp, {sms,mms}deliveryTimestamp, {sms,mms}readTimestamp and thread.timestamp.

This is just a quick WIP patch to address what we're going to do. I'd appreciate if you could take over the Gaia part.

One strange thing is, what I can only see in the current Gaia master is thread.timestamp. How about others like deliveryTimestamp you're working on?
Attachment #8340633 - Flags: feedback?(schung)
Why is security sensitive?
Group: core-security
deliveryTimestamp is still in WIP bug 933131, I will also apply the changes in the patch. This changes will also need for desktop mock and unit test. If you have any question about the test or have no cycle to finish all these stuff, please let me know, thanks.
Per off-line discussion, Steve can help take over this.
Assignee: gene.lian → schung
Can I have access to Bug #939302 please?
Done.
Hi Steve, please see bug 939302, comment #41 which might be a better approach to keep the backward compatibility.
(In reply to Boris Zbarsky [:bz] from comment #6)
> Done.

Can you grant me access as well? Thanks
Done. :)
I think that we always convert the Date to a timestamp (using getTime()) and really use a timestamp in the sms code, so let's just use "+timestamp" instead of calling getTime() :)
Comment on attachment 8340633 [details] [diff] [review]
Patch (WIP)

Clear feedback and thanks for the tip!
Attachment #8340633 - Flags: feedback?(schung)
Hi Joe, we need to mark this as V1.3+ because this bug blocks Bug 939302 which is a V1.3+ blocker.
Flags: needinfo?(jcheng)
Attached file Link to github
Hi Julien, this patch force all timestamp related properties to long int(and also changed unit test/mock and desktop test). I'll also fix delivery timestamp in bug 933131 once this patch landed, thanks.
Attachment #8340633 - Attachment is obsolete: true
Attachment #8345340 - Flags: review?(felash)
Comment on attachment 8345340 [details] [review]
Link to github

Looks good, mostly nits, and one oversight.

I'd like to wait for another pass before giving r+ but I think it will be fine at the next review!
Attachment #8345340 - Flags: review?(felash)
Comment on attachment 8345340 [details] [review]
Link to github

Hi Julien, another commit for your suggestions, thanks for the feedback!
Attachment #8345340 - Flags: review?(felash)
Flags: needinfo?(jcheng)
Flags: needinfo?(jcheng)
blocks a blocker. 1.3+
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(jcheng)
Comment on attachment 8345340 [details] [review]
Link to github

r=me

thanks! easy patch, but so boring ;)
Attachment #8345340 - Flags: review?(felash) → review+
Landed in master: 87345e3947da71386552561d5f15109955d4fe15
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Need someone's help to land this to V1.3 branch for Gaia and then we can then bug 939302.
Keywords: checkin-needed
v1.3: 8d21e3cbea1cc8515c460e1d2427e1a161812ddb
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: