Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

API: RFC 3339 time format weirdness #13573

Closed
2 of 7 tasks
DuckDuckWhale opened this issue Nov 15, 2020 · 2 comments
Closed
2 of 7 tasks

API: RFC 3339 time format weirdness #13573

DuckDuckWhale opened this issue Nov 15, 2020 · 2 comments

Comments

@DuckDuckWhale
Copy link
Contributor

DuckDuckWhale commented Nov 15, 2020 •
edited
Loading

  • Gitea version (or commit ref): 1.12.5
  • Git version: N/A
  • Operating system: Ubuntu Server 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Haven't tried
  • Log gist: N/A

Description

I was making a request using the API to /user/times and parameter since using RFC 3339. When I use 2002-10-02T10:00:00-00:00 and 2002-10-02T10:00:00Z it works fine, but when I use 2002-10-02T10:00:00+00:00 (with a plus) the API returns an empty message with a error code of 500.
@6543
Copy link
Member

6543 commented Nov 15, 2020

its a bug and its fixed

@6543
Copy link
Member

6543 commented Nov 15, 2020

Backport #13560 will fix it for 1.12.6 too

@6543 6543 closed this as completed Nov 15, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Jan 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@6543 @DuckDuckWhale