wojciech.kapcia@tigase.net opened 2 years ago
|
|
@wojtek Should we apply the same fix https://projects.tigase.net/issue/muc-130? |
|
Yes |
|
I've fixed this issue but it is getting annoying as we already had "almost" the same issue with MySQL #issue #67 but with a difference of 1ms. I've modified previous fix to hopefully fix this, however, I'm not sure why this 1ms offset appeared nor what caused it. |
|
Fix in separate branch |
|
Looks ok, As for the issue - it was sent by the client, so I would say it's a client "bug" of sorts (the timestamp itself is not inherently wrong, but it seems they were aiming at 1970…). |
|
I'll prepare PRs in the future. |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
Candidate for next minor release
|
Related
Issue Votes (0)
Watchers (0)
IMHO a proper IQ error should be returned to user.