Statping: Date not parsed in browser

[bash-stack]

graphs not showing up in detail page ,

browser console says:

TypeError: e.forEach is not a function
Starting with v2.0.0-beta.1 date-fns doesn't accept strings as arguments. Please useparseISOto parse strings. See: https://git.io/fjule

[KaulSe]

same here. have you found a solution?

[KaulSe]

In my case the error was on the PostgreSQL side: error: "pq: timestamp with time zone units "1h0m0s" not recognized". After switching back to SQLlite, everything worked again properly.

[hunterlong]

Detail page has some major issues right now, let me work on that a bit...

[peimanja]

Same issue here

WARN[0271] sending error response for /api/core: json: cannot unmarshal string into Go struct field Core.timezone of type float32  type=handlers
WARN[0333] sending error response for /api/services/22/hits_data?start=1585926337&end=1586531137&group=6h&fill=false: pq: timestamp with time zone units "6h0m0s" not recognized  type=handlers
WARN[0333] sending error response for /api/services/3/hits_data?start=1585926337&end=1586531137&group=6h&fill=false: pq: timestamp with time zone units "6h0m0s" not recognized  type=handlers
WARN[0333] sending error response for /api/services/6/hits_data?start=1585926337&end=1586531137&group=6h&fill=false: pq: timestamp with time zone units "6h0m0s" not recognized  type=handlers

[github-actions[bot]]

This issue hasn't had any updates in a while. If this is still a problem, please create a new issue.

[hunterlong]

@peimanja, Statping no longer uses time zones, so you might need to upgrade your Statping instance to the latest version. All time is recorded in UTC, and browser will convert to your local time zone.

[hunterlong]

@KaulSe , I haven’t seen this issue in a while. I believe I might have fixed this a while ago. Try the latest version.