distance matrix departure time unit change from miliseconds to seconds

[monajafi]

departure time changed from miliseconds to seconds

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
• In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

[monajafi]

I signed CLA

[googlebot]

CLAs look good, thanks!

[stephenmcd]

is this still one hour ahead?

[monajafi]

oh sorry you are right I've corrected it

[monajafi]

Every time in this library is in milliseconds while google documentations says following about departure_time and arriavel_time:
departure_time — Specifies the desired time of departure. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC. Alternatively, you can specify a value of now, which sets the departure time to the current time (correct to the nearest second).
As you see it says time in seconds since january 1 ,1970 not milliseconds . you set milliseconds everywhere in tests not seconds. not just distanceMatrix I see in directions Api too