similar to: Rails 3 timezone error

Displaying 20 results from an estimated 20000 matches similar to: "Rails 3 timezone error"

2017 Oct 16
0
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes: > (I reported the test failure mentioned below to R-help but was advised > that this list is the right one to address the issue; in the meantime I > investigated the matter somewhat more closely, including searching > recent R-devel
2017 Oct 19
0
Another issue with Sys.timezone
On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes: (I also included a reply to part of this response of yours below.) >>>>>> Stephen Berman <stephen.berman at gmx.net>
2017 Oct 20
1
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Thu, 19 Oct 2017 17:12:50 +0200 writes: > On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>>>> on Mon, 16 Oct 2017 19:13:31 +0200
2017 Oct 18
2
Another issue with Sys.timezone
>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes: >>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes: > > (I reported the test failure mentioned below to R-help but was advised > > that this list is
2010 Sep 17
1
using OpenPGP gem and getting "out of range error"
I''ve been handed someone else''s code to debug, but am getting no further than he did... perhaps someone can help. We''re using the OpenPGP gem (http://openpgp.rubyforge.org/) to PGP- encrypt an XML file for submission to a third-party for processing. The prob is that when encrypting, we get errors like the following: RangeError: 1502 out of char range from
2006 Jun 18
2
Hosting timezone differs of clients timezone
Hi, I have a website in production wich uses a lot of date and time calculations to show specific information. The timezone of my hosting service (Dreamhost) is PDT, and the timezone of my potential clients is CEST. There are 9 hours of difference between them. Is there an environment variable that I could adjust in my rails application, so all date/time values be set to CEST timezone? Thanks.
2017 Oct 14
2
Another issue with Sys.timezone
(I reported the test failure mentioned below to R-help but was advised that this list is the right one to address the issue; in the meantime I investigated the matter somewhat more closely, including searching recent R-devel postings, since I haven't been following this list.) Last May there were two reports here of problems with Sys.timezone, one where the zoneinfo directory is in a
2020 Oct 02
0
timezone tests and R-devel
Thank you for the report. In R-devel, all.equal.POSIXt() by default reports inconsistent time zones. Previously, > x <- Sys.time() > all.equal(x, as.POSIXlt(x, tz = "EST5EDT")) would return TRUE. To ignore the time zone attributes in R-devel, the argument 'check.tzone = FALSE' needs to be used. That said, I can reproduce the 'make check' failure in R-devel on
2017 May 17
1
problem running test on a system without /etc/localtime
>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>> on Tue, 16 May 2017 20:49:02 -0700 writes: > On Tue, May 16, 2017 at 5:35 PM, Kirill Maslinsky <kirill at altlinux.org> wrote: >> Hi all, >> >> A problem with tests while building R. >> >> I'm packaging R for Sisyphus repository
2017 May 17
0
problem running test on a system without /etc/localtime
On Tue, May 16, 2017 at 5:35 PM, Kirill Maslinsky <kirill at altlinux.org> wrote: > Hi all, > > A problem with tests while building R. > > I'm packaging R for Sisyphus repository and package build environment, > by design, doesn't have /etc/localtime file present. This causes failure > with Sys.timeone during test run: > > [builder at localhost tests]$
2020 Oct 23
0
timezone tests and R-devel
So let me try to raise this issue once more, and perhaps be more clear about what I think the issue is.. In my opinion there is now a bug in make check in R-development (tested today with r79361). As I see it, I specify a reasonable TZ environment variable and this leads to make check emitting an error. Best, Kasper On Fri, Oct 2, 2020 at 11:28 AM Kasper Daniel Hansen < kasperdanielhansen
2010 Jul 03
0
rspec controller test strange error: undefined method `call' for nil:NilClass
must be doing something dumb.... not sure, but the ''call'' appears to be on the block.call when the respond_to block gets executed. straight forward "channels" resource with a ''create'' action.... only new thing is just assigning the current_user to the model. def create @channel = Channel.new(params[:channel]) @channel.user = @user
2020 Oct 23
1
timezone tests and R-devel
Yes, you are absolutely right and I'm pretty sure this will be fixed in one way or another. IMO, the failing test should simply use all.equal.POSIXt's new argument check.tzone=FALSE. Two simple alternatives modifying all.equal.POSIXt behaviour: - make check.tzone=FALSE the default: this is inconsistent with other arguments of all.equal methods, always defaulting to stricter checks -
2010 Apr 07
2
rails timezone difference in console and production application
Hi all, I''m on a rails 2.3.5 app. I''ve got my timezone set to ''Brussels''; config.time_zone = ''Brussels'' When I use mysql I see that a date is stored in UTC (as expected); e.g. 2010-04-07 15:03:10 When I use console to print out the date it correctly returns; >> job.created_at.strftime(''%d %b %Y, %H:%M'') =>
2005 Apr 19
1
timeSeries Date Warning messages: Set timezone to GMT!
Hello, I must be doing something wrong that's very obvious. But I just don't see it. I changed my Windows Time Zone to GMT and my Financial Center to Montreal. But I still get several warnings. >Sys.timezone() [1] "GMT Daylight Time" >myFinCenter [1] "Montreal" >Sys.timeDate() [1] "Montreal" [1] [2005-04-19 10:55:02] Warning messages: 1: Set
2012 Jun 13
0
Weird (?) ActiveSupport::TimeZone parse behaviour
Hi I must be slipping, but say I have a string that looks like: 3/11/2012 2:50:00 AM If I use the UTC timezone and ask it to parse this time, what would you expect the result to be? Personally, I''d say 3/11/2012 2:50:00 AM UTC Given this is the DST switchover date (for some places) this is an edge case. It''s the "spring forward" rule so 2:50 AM is 3:50... But
2008 Jan 11
2
Syslog timezone issue
We recently upgraded (as in, backup, reinstall, selective restore) a couple of servers from CentOS-3.9 to CentOS-5.1. This generally went smoothly but we've encountered one confusing problem with syslog. Under CentOS-3, syslog entries were always dated in the host local timezone. With CentOS-5.1, they're dated in UTC *most* of the time, but occasionally in the local timezone. This has
2007 Apr 19
1
Time zone mapping from TimeZone to TZInfo::Timezone
Hi. Using this: <%= time_zone_select("account", "time_zone" %> I get a list of time zones options, like eg.: <option value="Athens">(GMT+02:00) Athens</option> But as I''m using TZInfo::Timezone, I need to map ''Athens'' to ''Europe/Athens'' I can see that the mapping I''m looking for is
2020 Oct 02
2
timezone tests and R-devel
Yes, the potential issue I see is that make check fails when I explicitly set TZ. However, I set it to be the same as what the system reports when I login. Details: The system (RHEL) I am working on has $ strings /etc/localtime | tail -n 1 EST5EDT,M3.2.0,M11.1.0 $ date +%Z EDT $ echo $TZ US/Eastern On Fri, Oct 2, 2020 at 9:48 AM Sebastian Meyer <seb.meyer at fau.de> wrote: > Thank
2018 May 06
0
Sys.timezone (timedatectl) unnecessarily warns loudly
Dear R-devels, timedatectl binary used by Sys.timezone does not always work reliably. If it doesn't the warning is raised, unnecessarily because later on Sys.timezone gets timezone successfully from /etc/timezone. This obviously might not be true for different linux OSes, but it solves the issue for simple dockerized Ubuntu 16.04. Current behavior R Under development (unstable) (2018-05-04