Bug report: Start and stop timestamp in db not properly set

Describe the bug

The stop and start timestamps in the database are identical:

To Reproduce

• Register a strava account against staging.bikedataproject.org.
• Check the timestamp data in the database.

Expected behavior

The timestamps to be properly set. Start timestamp the first timestamp from the track, the stop timestamp the last.

Bug report: A user without activities generates an error in ther logs.

Describe the bug

After redeploying the service this message appears in the log:

"time="2020-09-21T12:36:38Z" level=error msg="Could not store new user activities: Could not fetch user activities: ""

Update: It seems this happens when a user has no activities.

To Reproduce

Change the IsHistoryFetched boolean of the last user in the database to 'false'.

Expected behavior

• User Activities are fetched.
• The boolean is not set until activities are fetched without errors.
• No error messages are reported.

Bug report: Not all relevant activities are fetched.

Describe the bug

When registering my strava account with staging.bikedataproject.org it fetches most of my activities but not all of them.

To Reproduce

• Register strava account.
• Check the database to see if all contributions are there.

Expected behavior

All relevant activities to be fetched.

Attachments

Activties in the db:

Activities on profile:

https://www.strava.com/athletes/15977988

Missing activity:

https://www.strava.com/activities/3945539474

The primary keys are generated by the database. Could it be that in this service they are generated by the service itself?