[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*
From: |
Juan Pablo Carbajal |
Subject: |
[Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:* |
Date: |
Thu, 29 Jun 2017 16:32:46 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 |
Follow-up Comment #12, bug #51340 (project octave):
Hi Mike,
Thanks for the effort. I still dot not understand how the current behavior is
acceptable. It just misbehaves for the period of 1 hour and for that day.
1. In the first assert indeed the "_" should be erased.
2. The element-wise comparisson was intentional to show that it fails in the
span of an hour
3. What do you mean by invalid time string/specification? '29/03/2009
02:00:00' is a valid time string.
4. I do not get any error with my system's strptime, it always works as
expected (I would expect Octave to do the same, but maybe it is a
compatibility issue). I gave the example program in comment #1
5. I get empty when getting TZ
>> getenv TZ
ans =
6. The example in comment #9 works fine here.
>> getenv TZ
ans =
>> fmt = "yyyy-mm-dd HH:MM:SS";
>> datevec ("2017-03-12 02:00:01", fmt)
ans =
2017 3 12 2 0 1
>> datevec ("2017-03-12 03:00:01", fmt)
ans =
2017 3 12 3 0 1
I understand that in the octave wrapper of strptime we are adding some TZ
awareness. I also assume this is an inherited bug from Matlab compatibility.
Right?
7. Setting TZ to UTC solves the original issue. I just wonder whether it will
be triggered somewhen else.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51340>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, (continued)
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Dmitri A. Sergatskov, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Juan Pablo Carbajal, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Nicholas Jankowski, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Dmitri A. Sergatskov, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Philip Nienhuis, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Juan Pablo Carbajal, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Nicholas Jankowski, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*,
Juan Pablo Carbajal <=
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Juan Pablo Carbajal, 2017/06/29
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Philip Nienhuis, 2017/06/30
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/30
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Mike Miller, 2017/06/30
- [Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*, Juan Pablo Carbajal, 2017/06/30