bugGNU Octave - Bugs: bug #55650, Time Zone is not stable with...

 
 

bug #55650: Time Zone is not stable with function NOW (at least)

Submitter:  Dave Schaack <dschaack>
Submitted:  Tue 05 Feb 2019 11:32:17 PM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 4.4.1 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 06 Feb 2019 04:23:20 PM UTC, comment #3: 

4.4.1 is about to be deprecated.  If you can replicate with the soon-to-be-released 5.1 then file another bug report against that version.  For the time being, I'll assume that the fix in bug #53922 also resolves this report.

Marking as fixed and closing report.

Rik <rik5>
Group administrator
Wed 06 Feb 2019 12:25:48 AM UTC, comment #2: 

Wow, quick response, thanks!
I may try the new version at some point, but for now, since I am new to Octave, and can work around this problem, I will avoid that.  It was a very confusing way to get started!

Dave Schaack <dschaack>
Tue 05 Feb 2019 11:46:10 PM UTC, comment #1: 

You might try the Octave 5 release candidate, version 5.0.91 (https://lists.gnu.org/archive/html/octave-maintainers/2019-02/msg00037.html). I think this may have been fixed, see bug #53922. The reason for this behavior on your system is that the 'unsetenv' function doesn't do what it's supposed to do.

Mike Miller <mtmiller>
Group Member
Tue 05 Feb 2019 11:32:17 PM UTC, original submission:  

I'm a new user of Octave, but a long time user of Matlab.  For the first time ever, I have need of time handling capabilities.  I immediately ran into this very apparent problem.  Start Octave, and type in the following:


now
now  %Do it again, just to see that the result is consistent
days = datenum(datestr(now))
now  % Result changes to a different time zone!

Here is what I got:

>> now
ans =  737461.66489
>> now
ans =  737461.66493
>> days = datenum(datestr(now))
days =  737461.66510
>> now
ans =  737461.95683


What happened there at the end is that the local time used by Octave changed from my correct local time to GMT time!

Dave Schaack <dschaack>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by dschaack (Submitted the item)
  • -email is unavailable- added by dschaack
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-02-06 rik5 StatusNeed Info Fixed
        Open/ClosedOpen Closed
    2019-02-05 mtmiller CategoryNone Octave Function
        StatusNone Need Info
    2019-02-05 dschaack Carbon-Copy- Added dschaack

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code