# Chronic parse problem?

**URL:** <https://www.ruby-forum.com/t/chronic-parse-problem/129698>\
**Category:** Rails\
**Created:** [February 20, 2008, 8:33pm UTC](https://www.ruby-forum.com/t/chronic-parse-problem/129698 "2008-02-20T20:33:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f1d935/32.png) [@cal](https://www.ruby-forum.com/u/cal)\
**Post date:** [February 20, 2008, 8:33pm UTC](https://www.ruby-forum.com/t/chronic-parse-problem/129698/1 "2008-02-20T20:33:24Z")

</div>

Hi all,

Using the Chronic.parse method, I see some weird behavior. Perhaps  
someone can set me straight or confirm that it is indeed weird. Note  
that the date changes to one day earlier in the last example below.  
Since the date and time are uniquely specified using the hh:mm:ss  
notation – though in the future – I would expect the same result as  
when I specify the time as in ‘4pm’. Thanks in advance for any  
thoughts on this.

-cal

> > Chronic.parse(“now”, :context =\> :past)  
> > =\> Wed Feb 20 11:17:36 -0500 2008
> 
> > Chronic.parse(“2008-02-20”, :context =\> :past)  
> > =\> Wed Feb 20 12:00:00 -0500 2008
> 
> > Chronic.parse(“2008-02-20 10am”, :context =\> :past)  
> > =\> Wed Feb 20 10:00:00 -0500 2008
> 
> > Chronic.parse(“2008-02-20 10:00:00”, :context =\> :past)  
> > =\> Wed Feb 20 10:00:00 -0500 2008
> 
> > Chronic.parse(“2008-02-20 4pm”, :context =\> :past)  
> > =\> Wed Feb 20 16:00:00 -0500 2008
> 
> > Chronic.parse(“2008-02-20 16:00:00”, :context =\> :past)  
> > =\> Tue Feb 19 16:00:00 -0500 2008

---

<div class="post-metadata">

**Author:** ![cal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f1d935/32.png) [@cal](https://www.ruby-forum.com/u/cal)\
**Post date:** [March 5, 2008, 2:56am UTC](https://www.ruby-forum.com/t/chronic-parse-problem/129698/2 "2008-03-05T02:56:38Z")

</div>

Ahem. Anyone home?