Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9096

Closed
Open
Created Apr 07, 2015 by Administrator@rootOwner

Can not handle future commit date

Created by: waterscar

When a repo contains future commit date, activity log will stop updating, and compare page always returns a 502.

2015-04-07_07:21:37.23853 2015-04-07T07:21:37.238Z 8948 TID-68rq8 WARN: Failed to parse commit f814fc50107b236295ccdaf100f29043bc0e340a - cannot parse commit time

2015-04-07_07:21:37.23870 2015-04-07T07:21:37.238Z 8948 TID-68rq8 WARN: /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/gitlab_git-7.0.1/lib/gitlab_git/repository.rb:261:in `each'

Gitlab shouldn't fail to handle future (not invalid) dates.

Here's how the commit look like:

commit f814fc50107b236295ccdaf100f29043bc0e340a
Merge: ff9de7d 62df227
Author: Some one <[email protected]>
Date:   Sat Jun 23 11:36:01 2040 +0800
Assignee
Assign to
Time tracking