Ruby on Rails Thursday, October 30, 2014

Johann Vazquez wrote in post #1161364:
> I have the same problema on Windows7, with the following code:
> This generates EMFILE Error (BINARY Mode):
>, "wb") do |f|
> f.puts(version)
> f.puts(sha)
> f.write(contents)
> end
> This one, NOT!! (TEXT Mode):
>, "w") do |f|
> f.puts(version)
> f.puts(sha)
> f.write(contents)
> end
> Everything was right and doing very well until 4 days ago... Looks like
> some Windows 7 system stuff changed or something but I'm not able to
> figure out what it is!
> What could it be??? HELP!!

It seems that some kind of malware stuff was interferring with my
application. I tested it on Windows "Secure Mode" and everything was
right (No EMFILE Error)... So I downloaded several antiviruses,
antimalwares, etc.... with no luck.

But, finally, "ADW Cleaner" did the job (running it under Windows
"Secure Mode"). Happuly, after that, no more EMFILE Error. End of the
story? I hope so...

Posted via

You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
To view this discussion on the web visit
For more options, visit

Ruby on Rails

Hello everyone!!! It's that time again.

I would like to announce that Rails 3.2.20, 4.0.11, 4.1.7, and 4.2.0.beta3 have been released. These releases contain a security fix where the existence of arbitrary files on the file system can be leaked, but the contents of the file **will not** be leaked. The issue generally only impacts people who are using Rails to serve static assets, and will generally not impact people who use a proxy to serve static assets. You can read more about the issue [here (CVE-2014-7818)](!topic/rubyonrails-security/dCp7duBiQgo). A release of sprockets has also been made to help with this issue. You can read about it [here (CVE-2014-7819)](!topic/rubyonrails-security/wQBeGXqGs3E).

For ease of upgrading, the only changes in these releases are the security fixes.

Here are the checksums for the gems:

[aaron@TC release]$ shasum *3.2.20*
b14ca1ad923e035ab2a7785e657c5653447c3149 actionmailer-3.2.20.gem
d6fea767996a954e4bc95fd0ca101ec912fcb093 actionpack-3.2.20.gem
97f5bb424aee73fbbd319baab3fd35c3f5eeb5f4 activemodel-3.2.20.gem
32d76836675a4c88685c3904271b16d9d2338ce9 activerecord-3.2.20.gem
640d83a96accc24e6afcae3cc5b253e5d355983f activeresource-3.2.20.gem
d1d0a19a589c62278e7d9ac4275d5f8d75df20b3 activesupport-3.2.20.gem
f8b4d3c56d89760c02b37d4c67efd31dedd4df80 rails-3.2.20.gem
41c272d53dd748407210a2270ad17bc7c9f30594 railties-3.2.20.gem
[aaron@TC release]$ shasum *4.0.11*
9718b62f4428a7e4bbf66df4ac57dd82d197905a actionmailer-4.0.11.gem
f1aec3d29e781e3beb685852db00ecf495150077 actionpack-4.0.11.gem
2ba4ceeff0a76df850d6294e2e1da703f3f6e7cb activemodel-4.0.11.gem
714dca99a452adfec76b507241896ffd7978a254 activerecord-4.0.11.gem
2791791c5c1eeefb3eee76712656bf674a20867d activesupport-4.0.11.gem
56bb306d4f0309dcf3a804a97104a3ee26b64b94 rails-4.0.11.gem
243e265c879db8876cce8688374cb7f9bb752d7d railties-4.0.11.gem
[aaron@TC release]$ shasum *4.1.7*
4e4ce2530ff8773af784340e17e925b3b2c8cb20 actionmailer-4.1.7.gem
81628e433ca4335409677a33cfe9b56627f6ae1a actionpack-4.1.7.gem
7dc2626f5bc85379c55e49a712f5c0e060340ca8 actionview-4.1.7.gem
83c8be73d22973c843d43a988b27a449d2ca8a9d activemodel-4.1.7.gem
001156373c248a20c69bcf1451d6f7166dac3ddb activerecord-4.1.7.gem
217f25a911f8e89cd2834849232555cbc47ca850 activesupport-4.1.7.gem
a1d9bb181d718e7f6cf380136425444e627c2345 rails-4.1.7.gem
1b9c8d08afc8fa77786fef13c54d4e6985cdc6d6 railties-4.1.7.gem
[aaron@TC release]$ shasum *4.2.0*
e5d608e8ce32abdd73c73c91fd34cb8f7075a251 actionmailer-4.2.0.beta3.gem
2e2034c285943777ad325c35292e202a46b937c2 actionpack-4.2.0.beta3.gem
a008833cd1045c926fb6f36ee03e3d34499a0aa9 actionview-4.2.0.beta3.gem
02f4438363419c59b33d85b2dda4d4cf741a6098 activejob-4.2.0.beta3.gem
c8a7dc2134c885ad3b23d4c36be95abc1ec1b769 activemodel-4.2.0.beta3.gem
192e33ab3b9d54954ff834ce6ee7f67a9197cb36 activerecord-4.2.0.beta3.gem
00437ab52df0ed0dd9afe571d083c92c3cdbe361 activesupport-4.2.0.beta3.gem
ca81d6ac9fdd658775d32a6dbfe248ee13f5c87b rails-4.2.0.beta3.gem
cc302e363248e4bc2d245201f922c576f9fe6f15 railties-4.2.0.beta3.gem

Have a great day!!! <3

Aaron Patterson

Ruby on Rails

Colin Law wrote:
> That tells you it is rails 4.0.0 as activemodel is one of the
> components. However, rather than seeing what versions are installed
> (there could be more than one version of the gems installed) look in
> the file Gemfile.lock in the applications root folder and you will see
> what versions it /requires/.

I have several GIT entries in the Gemfile.lock file and a list of gems
after the following lines, but this list looks much more extensive than
'gem list' shows ...

<list of gems>

Then under DEPENDENCIES, I see ...

rails (= 3.2.13)

Does that explain my rails version? I don't see any references to 4.0.0.

> I suggest you work right through a good tutorial such as
> (which is free to use online) which will show you
> the basics of rails. A few days spend doing that will save you time
> in the long run.

Yes, I've already found that and been reading, thanks.

> If you want this for development work then I suggest you install rails
> using rvm [1]
> That will give you a complete working setup in a few minutes.

I used rvm to install same ruby-1.9.3-p392 as the VPS, following a doc

After all setup in Apache, I am getting this Passenger application error
in the browser....

cannot load such file -- bundler/setup (LoadError)



`block in run_load_path_setup_code'







Perhaps I need to get some more gems installed? I did a 'gem install
bundle' and still get the error. My gem list is this so far on the dev
server I am trying to setup, not sure if this error is affecting things
as well...

root@media:/etc/apache2# gem list
`<top (required)>':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.

*** LOCAL GEMS ***

bundle (0.0.1)
bundler (1.7.4)
daemon_controller (1.2.0)
passenger (4.0.53)
rack (1.5.2)
rake (10.3.2)

On the production server, I have...

*** LOCAL GEMS ***

activemodel (4.0.0)
activerecord (4.0.0)
activerecord-deprecated_finders (1.0.3)
activerecord-mysql-adapter (0.0.1)
activesupport (4.0.0)
arel (4.0.0)
atomic (1.1.13)
bigdecimal (1.1.0)
builder (3.1.4)
bundler (1.3.5)
i18n (0.6.5)
io-console (0.3)
json (1.5.5)
minitest (4.7.5, 2.5.1)
multi_json (1.7.9)
mysql (2.9.1)
rake (
rdoc (3.9.5)
thread_safe (0.1.2)
tzinfo (0.3.37)

But again the list in the Gemfile.lock file lists many more. Just trying
to get a grasp of where to go from here, what is need to get this copy
to run, appreciate any help!


You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
To view this discussion on the web visit
For more options, visit