github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 04:25:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

API: RFC 3339 time format weirdness #6314

New Issue
Closed
opened 2025-11-02 06:52:20 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 06:52:20 -06:00
Owner
Copy Link

Originally created by @DuckDuckWhale on GitHub (Nov 15, 2020).

  • 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.

Originally created by @DuckDuckWhale on GitHub (Nov 15, 2020). - Gitea version (or commit ref): 1.12.5 - Git version: N/A - Operating system: Ubuntu Server 20.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] 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.
GiteaMirror commented 2025-11-02 06:52:21 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Nov 15, 2020):

its a bug and its fixed

@6543 commented on GitHub (Nov 15, 2020): its a bug and its fixed
GiteaMirror commented 2025-11-02 06:52:21 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Nov 15, 2020):

Backport #13560 will fix it for 1.12.6 too

@6543 commented on GitHub (Nov 15, 2020): Backport #13560 will fix it for 1.12.6 too
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6314
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?