Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pike pike
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 119
    • Issues 119
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pikelang
  • pikepike
  • Issues
  • #3516

Closed
Open
Created Oct 01, 2003 by Peter Bortas@zinoOwner

New Calendar.parse specifier for seconds since Epoch

Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3516

Reported by Dan Nelson dnelson_1901@yahoo.com

To make a logfile searcher I am writing easier to process, I need to be able to parse squid logfile timestamps which use time_t.fraction format:

1065019763.300 796 199.67.51.207 TCP_MISS/200 9401 GET http://community.roxen.com/crunch/ - DIRECT/194.52.182.5 text/html

The current %s format doesn't work because that allows only 0-59, and also is relative from now().

The attached patch lets you do:
> Calendar.parse("%S.%f","1065019763.300");
(8) Result: Fraction(Wed 1 Oct 2003 9:49:23.300000 CDT)
Assignee
Assign to
Time tracking