Note that the timestamps should update the start end dates as follows:
Start: Wednesday, December 8, 2021 2:00:00 PM
End: Wednesday, December 8, 2021 2:29:00 PM
When the post request completes. the following information is returned from the API:
Note the inconsistency between the epoch times listed in the request and listed in the body. It is off by 15 minutes.
When running /events view euhq9soh41 I get this:
It looks like the API might be updating the database with a null value. As a side note, the API documentation indicate that the epoch start/end times are to be long values, but in the code, these are string that are converted to long value body.getString("epoch_start").toLong(). Posting this as a long results in an error.
Who is the bug affecting?
Administrators
What is affected by this bug?
API
When does this occur?
When updating an event
I am editing an event to adjust the start and end times (by one hour) This is the request body:
Note that the timestamps should update the start end dates as follows: Start: Wednesday, December 8, 2021 2:00:00 PM End: Wednesday, December 8, 2021 2:29:00 PM
When the post request completes. the following information is returned from the API:
Note the inconsistency between the epoch times listed in the request and listed in the body. It is off by 15 minutes.
When running
/events view euhq9soh41
I get this:It looks like the API might be updating the database with a null value. As a side note, the API documentation indicate that the epoch start/end times are to be long values, but in the code, these are string that are converted to long value
body.getString("epoch_start").toLong()
. Posting this as a long results in an error.