similar to: Rails 4.0.1.rc4 has been released!

Hi everyone, I am happy to announce that Rails 4.0.1.rc1 has been released. This is a bug fix release and includes more than 450 commits. This release comes up with an important change on how Active Record handles subsequent `order` calls. In Rails 4.0.0 when you do something like this: ```ruby User.order("name asc").order("created_at desc") ``` The later called `order`

This is a delivery failure notification message indicating that an email you sent could not be delivered. The problem appears to be : -- Recipient email server rejected the message This condition occurred after 1 attempt(s) to deliver over a period of 0 hour(s). If you sent the email to multiple recipients, you will receive one of these messages for each one which failed delivery, otherwise

Hi everyone, I am happy to announce that Rails 4.0.4.rc1 has been released. This is a bug fix release and includes more than 290 commits. If no regressions are found we will release 4.0.4 final this Friday, on March 14, 2014. If you find one, please open an Issue on GitHub and mention me (@rafaelfranca) on it, so that we can fix it before the final release. ## CHANGES since 4.0.3 To view the

There''s a small inconsistency in ActiveRecord''s callback syntax that has tripped me up before. It wouldn''t be a big deal, but it can lead to a silent failure. I''d like to suggest that it either be made consistent or be made to fail loudly. The issue is that to do something before validating, but only when creating, you use `before_validation on: :create`,

Last night a friend of mine started ranting about validates_presence_of :boolean_field returning not valid when the boolean field is false. I checked the rails issues and this seems to be a pretty common concern about the naming of ''presence'' . Instead of changing the behaviour of the presence validator, I was wondering if maybe the answer to avoid such misconceptions could be

Hi, Thanks, yes, not very familiar with Centos and hence googling took a while to find a 4.0 version at, https://wiki.centos.org/SpecialInterestGroup/Storage On 28 March 2018 at 14:37, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > Go to [1], click on CentOS, the README.txt has links to the CentOS > Storage SIG where you can find information on installing RPMs from the

Go to [1], click on CentOS, the README.txt has links to the CentOS Storage SIG where you can find information on installing RPMs from the CentOS Storage SIG. On 03/27/2018 08:53 PM, Thing wrote: > Hi, > > Thanks, any howtos/docs/notes for installing gluster4.0.x on Centos 7 > please? > > On 27 March 2018 at 01:28, Shyam Ranganathan <srangana at redhat.com >

Just putting this out there before I make a pull request. Is there any interest in an asset_url method as a view helper? It would work by using the config.action_controller.asset_host if it exists and prepending this to the results of asset_path. I have found this necessary when writing html emails and needing a full url path for assets. Since my CDN in the asset_host mirrors my assets in my

(I posted this as a bug in GitHub (https://github.com/rails/rails/issues/7018), but then someone there told me I should post it here, so here it is.) If you set attr_accessible on some properties in an ActiveRecord-descended class, and then attr_protected on others - the class becomes ''default-open'' - if any properties are missed or added later, they will be accessible by

I think we are missing 3.12.7 in CentOS releases. On Wed, Mar 28, 2018 at 4:47 AM, Niels de Vos <ndevos at redhat.com> wrote: > On Wed, Mar 28, 2018 at 02:57:55PM +1300, Thing wrote: >> Hi, >> >> Thanks, yes, not very familiar with Centos and hence googling took a while >> to find a 4.0 version at, >> >>

The Gluster community is pleased to announce the release of Gluster 4.0.1 (packages available at [1]). Release notes for the release can be found at [2]. Thanks, Gluster community [1] Packages: https://download.gluster.org/pub/gluster/glusterfs/4.0/4.0.1/ [2] Release notes: https://github.com/gluster/glusterfs/blob/v4.0.1/doc/release-notes/4.0.1.md

I suggest that if you don''t pass any args to ActiveRecord#pluck, it would use the select values. This follows along well with the way other AR::Calculations work. As an extra benefit we would be able to pluck virtual columns. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit

Hi, Thanks, any howtos/docs/notes for installing gluster4.0.x on Centos 7 please? On 27 March 2018 at 01:28, Shyam Ranganathan <srangana at redhat.com> wrote: > The Gluster community is pleased to announce the release of Gluster > 4.0.1 (packages available at [1]). > > Release notes for the release can be found at [2]. > > Thanks, > Gluster community > > [1]

On Wed, Mar 28, 2018 at 02:57:55PM +1300, Thing wrote: > Hi, > > Thanks, yes, not very familiar with Centos and hence googling took a while > to find a 4.0 version at, > > https://wiki.centos.org/SpecialInterestGroup/Storage The announcement for Gluster 4.0 in CentOS should contain all the details that you need as well:

Just that: class Date > def remaining_to(date) > if date.acts_like? :date > date - self > end > end > alias :days_to end and then be able to do this: Date.today.remaining_to(Date.parse ''2014-04-02'').days.seconds -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To

Hey everyone, first of all, thank you for the tremendous work and effort on making Rails more awesome every day. I''ve brought up this "issue" on Github last Friday. [1] Steve Klabnik told me to bring the discussion here, as it''s more appropriate. The thing is, there is some amount of logic scattered around Rails (and its tests) that depends upon error/exception

1. Attempt to load Nexenta under 2.6.32.16-1.2.108.xendom0.fc13.x86_64 Xen 4.0.1-rc6-pre & 2.6.32.16-1.2.108.xendom0.fc13.x86_64 on top F13 [root@fedora13 NexentaStor-Community-3.0.2]# uname -a Linux fedora13 2.6.32.16-1.2.108.xendom0.fc13.x86_64 #1 SMP Fri Jul 23 17:09:30 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux [root@fedora13 NexentaStor-Community-3.0.2]# xm create -c

Hello! Are the plans of splitting ActionPack for several gems (AbstractController, ActionView, etc)? Like https://github.com/rails/rails/pull/7356 ... I.e. I know gems that are needed AbstractController only... And they are forced to require the whole ActionPack... Thanx. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To

I''m probably going to help backport some code from master onto 3.2, and the suggested process in the Contributing guide doesn''t actually look like the best approach to me. Wouldn''t it make more sense to just check out the branch you want to patch, cherry-pick the change(s) from master, make any additional commits necessary to get it working? Not only is that simpler

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I