See also this thread:
https://groups.google.com/d/topic/rubyonrails-core/kqKoJHcQu9U/discussion
...wherein is discussed (without any official response from core
contributors) many of the warts and limitations of RAILS_ENV in a modern,
cloud-native-y, 12-factor-y world.
-- Chad
On Mon, Feb 27, 2
Couple of data points:
We are moving to Elm for all our client code, so Karma or Mocha wouldn't
help us much, as we use elm-test.
Also, we have multiple bundles for different SPAs living within the same
Rails app, so I also wouldn't want to see the hardcoded assumption that all
tests have to be r
24, 2016 at 7:46 PM, Chad Woolley
wrote:
> I usually keep my fixtures in `spec/fixtures`.
>
> In order for `rake db:fixtures:load` to work, I've always had to symlink
> `test/fixtures` to point to `spec/fixtures`.
>
> I was trying to avoid this in a new Rails 5 project
I usually keep my fixtures in `spec/fixtures`.
In order for `rake db:fixtures:load` to work, I've always had to symlink
`test/fixtures` to point to `spec/fixtures`.
I was trying to avoid this in a new Rails 5 project, but I could see any
way to (even monkey patching `ActiveSupport::TestCase#fixtu
I agree. I've been doing Rails for 10 years (and databases for going on
25)), and "belongs_to" has always been a cognitive blocker for me.
I wouldn't do away with "belongs_to", but making "has_key_for" aliases
sounds like a great idea, for people who want to write their code that way.
But, most
Hi,
As you can see here:
https://github.com/rails/rails/blob/5-0-0/activerecord/lib/active_record/transactions.rb#L214
...there's no docs, and it's not mentioned in any of the guides.
Is this intentional, or an oversight?
Thanks,
-- Chad
--
You received this message because you are subscribe
That was one thought I had. That would be the easiest first pass at a gem
that made the generators "compliant" - just make it add a rubocop config
that allowed the default generated rails code to pass.
On Mon, Jul 18, 2016 at 6:16 AM, Greg Navis wrote:
> We can invert the problem and make ruboc
Yes, I now see the points against including it are valid, but it would be
good to see a gem that overrides the generators to generate compliant apps.
On Sat, Jul 16, 2016 at 5:49 AM, Andrew Kaspick wrote:
> Why can't a gem be created that contains rubocop compliant generators and
> that is used
Re: "I don't use RuboCop in personal projects. In my consultant work some
clients do, some don't. Those that do have different configuration files
because no two Ruby teams have the same preferences"
This is a red herring. Most of the Rubocop failures against the standard
Rubocop config are due t
2016, Rafael Mendonça França <
rafaelmfra...@gmail.com> escribió:
> Automatic test schema maintainance is a feature of Rails since 4.1
> http://guides.rubyonrails.org/4_1_release_notes.html#railties-notable-changes
>
> On Tue, Jun 28, 2016 at 5:32 PM Chad Woolley > wrote:
>
+1, this is one of a few things that doesn't "work out of the box" for
databases in real-world usage. I always end up having some version of a
custom "db:prepare" which does extra necessary things for my apps.
FYI, this thread is somewhat related, in that it's also about confusion
about the behav
+1 on at least discussing what can be done about this.
The dev-env-switching-to-test thing has caused me lots of headaches over
the years, including in areas other than the db handling mentioned here -
the most recent coincidentally being today.
Another way to think of the problem is that on loca
And apparently google groups no longer provides the 'reject with comment'
moderation option, which is why I handled like this. If any other group
mods know how to you can still do that, please let me know...
-- Chad
On Sun, Jan 3, 2016 at 10:19 PM, Chad Woolley
wrote:
> Hi Duta
Hi Duta,
I think this ship sailed about four years ago, and in general it's not good
mailing list etiquette to reply to very old threads.
But you were nice and well intentioned, so I moderated this through. Have
a nice year too.
-- Chad
On Sun, Jan 3, 2016 at 8:16 PM, Duta Ksp wrote:
> Hello
Sorry too quick on the moderate button :(
On Monday, August 17, 2015, Nhung Hoang wrote:
> Bên mình đang cần tuyển 3 vị trí Ruby, Perl, Python
> Quyền lợi :
> - Mức lương: Từ 400$ trở lên. Thỏa thuận theo trình độ.
> - Cơ hội tiếp xúc, làm việc trực tiếp với khách hàng người Anh và Mỹ.
> - Cơ hộ
+1 on allowing control over formatting, there's been many times over the
years on various projects when schema.rb has flapped for spurious reasons,
it would have been good to have had control over it.
-- Chad
On Tue, May 19, 2015 at 6:46 AM, Randy Parker
wrote:
> +1 on a DIY format. And I woul
Thanks for sharing.
Not directly related to rails core, but kind of interesting so I moderated
it through...
-- Chad
On Sun, Apr 5, 2015 at 5:50 AM, Darren Daly wrote:
> Hi all,
>
> For my final year project I have been comparing web frameworks to get
> performance benchmarks that others can t
This list is for discussion of internal development of Rails itself, not
for general questions on Rails development - see the "rubyonrails-talk"
list for that.
Having said that, see http://12factor.net/ for more info on your question.
Good luck,
-- Chad
On Mon, Mar 16, 2015 at 10:58 PM, Pradeep
Sorry, there were some messages awaiting moderation from 2/24, but I didn't
see any group admin notifications until today. Maybe something fell
through the Google-cracks... I'll try to check manually for a while in
case it happens again.
--Chad
--
You received this message because you are subs
Hi Nicole,
Also, you can check a group's "About" to find out the rules for posting, if
the group admins have specified any. E.g.:
https://groups.google.com/forum/#!aboutgroup/rubyonrails-core
Good luck!
-- Chad
On Fri, Oct 24, 2014 at 9:19 AM, Nicolas Cavigneaux wrote:
>
> Le 24 oct. 2014
Sounds like a great idea, just make sure it doesn't break the build locally.
For bonus points make the number of parallel builds configurable.
For extra bonus points, make the parallelization work locally as well as
Travis.
-- Chad
On Wed, Oct 22, 2014 at 9:22 AM, Tu Hoang wrote:
> I raised th
This list is for rails core discussion, so this question is probably better
suited for rubyonrails-talk.
But I'll answer anyway (it would be great to get something like
fixture_builder into Rails someday, none of the alternatives are good IMO):
I use factories + fixtures via https://github.com/rd
+1, I was just wishing for this last week :)
On Wed, Nov 6, 2013 at 10:45 AM, Xavier Noria wrote:
> Sounds good to me.
>
> The documentation would say "if +capitalize+ is true", with "true" in
> regular font. Please update the AS guide as well if you are so kind.
>
> --
> You received this mes
#squelch ???
On Mon, May 6, 2013 at 10:55 PM, laise wrote:
> Issue:
>
> It breaks compatibility with old good Log4r and default ::Logger. I found
> that issue today while trying to setup custom logger. The cause is the new
> ActiveSupport::Logger#silence method, which is called by ActiveRecord
Can you give an example of how you would implement this?
On Fri, Apr 5, 2013 at 11:19 PM, Bakhtiyor Homidov wrote:
> Why doesn't Rails use aspect-oriented programming? e.g. for loggers
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" grou
Removed from group...
-- Chad
On Fri, Dec 14, 2012 at 5:01 AM, Peta Ward wrote:
> 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 a
"M" is the mute thread shortcut in gmail:
http://support.google.com/mail/bin/answer.py?hl=en&answer=47787
Don't feed the trolls.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googl
+1 on considering git-notes. Seems to solve the root problems cleanly.
On Thursday, November 17, 2011, Josh Susser wrote:
> I suggest using git-notes to mark commits for the CHANGELOG. Metadata FTW!
> Not all changes are worth mentioning in the CHANGELOG. But with
git-notes, you can annotate com
On Thu, Sep 1, 2011 at 7:46 AM, Everton Moreth wrote:
> I agree with Rodrigo, it should be optional, but when the Rails Community
> takes its choice in supporting anything, it gets attention, people start to
> use it, and even the framework itself gets better.
>
> Also, we really should ease the n
On Thu, Sep 1, 2011 at 6:40 AM, Michael Breen wrote:
> Rails doesn't really ship with any testing framework. It defaults to what's
> in Ruby core, which is Test/Unit in 1.8 and MiniTest in 1.9.
* Rails ships with Ruby test generators (because testing is good)
* Rails ships with Javascript/Coffee
OK, another spammer who joined May 27th, and have their posting
allowed flag turned on without ever having a first post moderated.
Unless some other list admin is going and flipping this bit in the
groups management console (anyone???), this looks like spammers have
found some exploit in google gr
No idea how this spammer got their moderate-first-post bit turned off.
I didn't do it, and doubt any other group admin did. They only
joined on May 24th. Google Groups fail or exploit?
Anyway, banned now...
On Fri, Jun 3, 2011 at 11:21 PM, Steve Schwartz wrote:
> That's not rails core... it's
Dunno who let her through first post moderation (not I), but she's
banned now. Sorry for the inconvenience.
On Tue, Jan 18, 2011 at 3:38 PM, Ryan Bigg wrote:
> Lori, whilst we appreciate the offer of jobs greatly, this is not the
> correct thread or even message board to post it into. Please do
On Sun, Nov 21, 2010 at 3:49 AM, www.watchcs.com wrote:
> replica watch fake|http://groups.google.com/group/rubyonrails-core?hl=en.
Of course I meant google groups. It's all teh googlez...
On Thu, Sep 23, 2010 at 3:52 PM, Chad Woolley wrote:
> UGH, what a google docs fail. I moderated this to ignore but it posted
> anyway.
>
> Anyway, Tyler Jennings is unsubscribed now, he can join again and get
>
UGH, what a google docs fail. I moderated this to ignore but it posted anyway.
Anyway, Tyler Jennings is unsubscribed now, he can join again and get
past the first post moderation again if he gets his hacked account
sorted...
On Thu, Sep 23, 2010 at 2:37 PM, Jamie Rumbelow wrote:
> Thank you fo
On Sat, Sep 11, 2010 at 6:03 PM, Ryan Bigg wrote:
> I don't see what lighthouse offers that github issues doesn't.
Search that actually works?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonra
On Saturday, April 24, 2010, Brian Durand wrote:
>> This I'm not so sold on, expires in is a memcached implementation
>> specific feature and adding it to all the other cache stores simply
>> seems to add overhead for very little gain. No one is seriously going
>> to be using MemoryStore or File
On Thu, Apr 22, 2010 at 4:23 PM, Federico Builes
wrote:
> Below you'll find my proposal, please contact me if you have any
This all sounds great.
> questions or suggestions:
> I currently don't know how far Chad plans to take his project, but
> from what I understand his idea
> is to setup sever
On Tue, Apr 20, 2010 at 2:56 PM, Jeremy Kemper wrote:
> Hey Federico,
>
> Have you tried the performance test suite built in to Rails apps?
>
> You write performance tests in the style of integration tests then
> `rake test:benchmark` or `rake test:profile`.
>
> The benchmark task benches each per
On Tue, Apr 20, 2010 at 10:33 AM, Federico Builes
wrote:
> Hi,
>
> As part of my Ruby SOC proposals I'm thinking of working in the CI
> idea posted in http://wiki.rubyonrails.org/rubysoc/2010/ideas
>
> Ideally, I'd like to do a two step proposal: first one would be
> writing custom CI tool tailore
On Mon, Apr 19, 2010 at 3:30 PM, Matt Jones wrote:
> On Apr 19, 2010, at 6:24 PM, Kristian Mandrup wrote:
>
>> If I have a gem locally that I change without updating the version
>> number the bundler never seems to notice.
>
> Don't do this. Seriously. Long-term, it's a one-way ticket to dependenc
On Mon, Mar 15, 2010 at 8:41 AM, Patrick Peak wrote:
> A. Copy the static files from the gems into the public directory of
> the project, which can allow the web server to handle serving them.
> (BrowserCMS does this).
I dislike the copying files approach, it seems confusing and error-prone.
> B
On Sun, Mar 7, 2010 at 6:49 PM, Jeremy Kemper wrote:
> I have a plugin with migrations for its own database. I want those to
> run and be managed in their own universe. This works well today using
> our existing tools: just override the connection class method on the
> migration.
Even if a plugin
On Sun, Mar 7, 2010 at 4:54 PM, Josh Susser wrote:
> I have a semi-grand plan for some changes to migrations.
+1 on all points.
I reviewed rails.lighthouseapp.com/projects/8994/tickets/2058, and
your solutions seem to cover all bases (someone speak up if it
doesn't). I especially like the part
On Sun, Dec 13, 2009 at 4:40 PM, Yehuda Katz wrote:
> Long-term, we want to try to get away from using global state like
> this as much as possible, but fixing it can sometimes open a thorny
> can of worms. Koz's solution, paired with a mutex or thread-local (for
> threadsafe scenarios) is a good
On Sun, Feb 21, 2010 at 8:27 AM, Prem Sichanugrist wrote:
> However, on the CI site, http://ci.rubyonrails.org , there's no testing
> environment for 1.9.2 there. So I would like to kindly ask the owner of those
> CI servers to add an environment for 1.9.2 too.
I'd be glad to do that, if Rails
On Mon, Feb 15, 2010 at 7:48 PM, Yehuda Katz wrote:
> The catch-all route let to a series of faulty patterns such a
> hide_action and verification. At it's core, the router is the
> appropriate place to limit request that go onto the controllers.
Agreed. Many a 2.x production app spews exception
On Sun, Feb 7, 2010 at 9:43 PM, Anuj Dutta wrote:
> Check this out as well, by Jose Valim:
>
> https://gist.github.com/9fcf658fc4f559b97c2c
>
> It gives a good introduction and a brief insight into how Railtie, Engine,
> Application fits together in Rails3.
That's a great writeup with lots of exa
If I have an action which can render multiple formats (e.g. html, js,
rss), is it possible to page-cache all of these formats?
I can't see how to do it with 'caches_page'. It looks like you can
only override 'page_cache_extension' at the class level:
http://github.com/rails/rails/blob/master/act
On Wed, Jan 13, 2010 at 1:44 PM, Anuj Dutta wrote:
> No problem. Yeah, it should be easily repeatable and extensible. I will keep
> an eye on the repository.
To be more clear, here's all you need to do with my current setup:
http://github.com/thewoolleyman/rails/blob/ci/ci/README.markdown
All y
On Wed, Jan 13, 2010 at 1:34 PM, Anuj Dutta wrote:
> Thanks for the correct. Well, I have started looking into Chef and really
> got no where with it :o( but I will keep trying.
No, I apologize - I didn't read your email closely enough - you had it right.
Anyway, the point is, it should all be r
Rails 3 is
> in the town.
>
> I had a word with Chad Woolley (thewoolleyman) who did the initial cinabox
> scripts to install the cruisecontrol.rb on your own server but since the
> different versions of Linux require different scripts, he has decided to
> rewrite the entire proces
On Wed, Dec 30, 2009 at 7:37 PM, Mike Gunderloy wrote:
> And indeed, if you check http://ci.rubyonrails.org/ you can see that Rails
> builds are pretty hit-or-miss on master right now.
>
> Mike
Yeah. The Core team has been bugging me to send campfire
notifications so they are more aware of brea
This list is for discussion of Rails internal development, not general
ruby questions.
Having said that, check out the 'cat' (catchpoint) functionality in
ruby-debug...
On Wed, Dec 2, 2009 at 10:44 AM, RubyNewbie wrote:
> Question:
> I was wondering if there was a way to instruct the ruby debug
On Sun, Dec 13, 2009 at 4:40 PM, Yehuda Katz wrote:
> Long-term, we want to try to get away from using global state like
> this as much as possible, but fixing it can sometimes open a thorny
> can of worms. Koz's solution, paired with a mutex or thread-local (for
> threadsafe scenarios) is a good
This causes problems in the following scenario:
1. You use ActiveResource to post data to an external site using
subdomains for individual accounts (e.g. Lighthouse)
2. You want your app to allow multiple users to do this (register
their Lighthouse account/URI to automatically push their data from
On Mon, Nov 23, 2009 at 4:29 PM, Mikel Lindsaar wrote:
> So I just updated the mail gem to 1.3.0 and against my fork of actionmailer
> at github/mikel/rails, ActionMailer now passes all tests in MRI 1.8.6, 1.8.7
> and 1.9.1
Now how about JRuby? ;)
--
You received this message because you are su
On Sun, Nov 22, 2009 at 5:48 AM, Mikel Lindsaar wrote:
> So, I have integrated edge ActionMailer with the Mail gem, removing TMail in
> the process.
> Currently, ActionMailer is running with 131 tests, 309 assertions, 0
> failures, 0 errors
> This is using ActionMailer from http://github.com/mikel
On Tue, Oct 13, 2009 at 9:53 AM, Mislav Marohnić
wrote:
> The default value for RAILS_ENV is set to "development" in initializer.rb,
> which is loaded right after boot.rb has determined the boot strategy.
> I created a "config/preinitializer.rb" which was supposed to provide another
> default val
On Fri, Oct 9, 2009 at 7:57 PM, Liping Huang wrote:
> sqlite3 can't run on ruby1.9.
It is running on 1.9 on the CI box, for the 2.3 branch:
http://mri19.ci.rubyonrails.org:/builds/rails-2-3-stable-ruby-1-9-1
...and master:
http://mri19.ci.rubyonrails.org:/builds/rails-master-ruby-1-9-
Running geminstaller against ci/geminstaller.yml should install
correct versions. Bundler is a great way to manage this, but not in
use on 2-3 branch and not fully in use on master, so geminstaller is
what the rails ci boxes still use.
Sorry for top post, on iPhone
On Thursday, October 8, 2009,
On Wed, Oct 7, 2009 at 1:55 AM, James Mead wrote:
> This is likely to be due to using Mocha >= 0.9.6 when Mocha is being
> loaded *before* Test::Unit.
>
> You need to make sure you are loading Mocha *after* Test::Unit. There
> are a number of ways of achieving this depending on how you are using
On Tue, Oct 6, 2009 at 4:00 PM, Philippe Creux wrote:
> I have few patches for active resource I would like to publish but I
> can't get the test suite passing.
>
> In: rails/activeresource (2-3-stable)
> Running: rake test
> Got the following:
> 1) Error:
> test_exists_without_http_mock(BaseTes
Hi Rodrigo, I can provide some info...
On Sun, Sep 20, 2009 at 8:37 AM, Rodrigo Rosenfeld Rosas
wrote:
> 1 - actionmailer: There are 6 errors of this kind: "NoMethodError:
> undefined method `find_template' for AutoLayoutMailer:Class"
These have been failing for quite a while - see the CI build
On Wed, Sep 9, 2009 at 4:02 PM, Rick DeNatale wrote:
> My normal practice when writing migrations which depend on model code
> is to put a migration specific model clase in the migration file
> itself, scoped inside the migration. The model mimics a subset of the
> one in app/models including on
On Wed, Sep 9, 2009 at 5:03 AM, Chris wrote:
>
> I see sublime elegance in having the DB store the DDL to revert
> migrations. I haven't worked with large teams in years, but I see the
> dilemma Steven is addressing:
>
> The common DB is at Rev N
> User (or branch) A migrates common DB up to Rev
On Tue, Sep 8, 2009 at 2:01 PM, Michael Koziarski wrote:
> That'd work only for cases where your down migrations *only* change
> the schema, they don't touch models or any other ruby code. Otherwise
> there's no guarantee that those models are available when the system
> tries to downgrade.
Doe
On Sat, Sep 5, 2009 at 6:15 AM, Eloy Duran wrote:
> I liked the idea of sending the email to the commit author, as Hudson
> apparently does as described by Joris. And as I do share concerns
> about the robustness of the Rails code, I wrote a patch for
> CruiseControl to be able to do the same:
>
On Fri, Sep 4, 2009 at 11:27 AM, Czarek wrote:
> Perhaps a timeout within which the build should be fixed? I mean it
> doesn't take hours for CI to detect the problem. And then mail if fix
> doesn't come in time.
That's a good idea. How about this:
1. The first three red builds notify only the
On Fri, Sep 4, 2009 at 7:11 AM, Eloy Duran wrote:
> I wouldn't be bothered by these CI emails if we'd see one every now
> and then. But nowadays, it seems like every other build is broken.
> That's the real problem here.
Thanks for the feedback, everyone. FWIW, this is not new, build
failures u
On Thu, Sep 3, 2009 at 12:13 PM, John Pignata wrote:
> It looks like this last test failure just won't pass on CI as it is
> running 1.8.6, from the code:
>
> # This is broken in 1.8.6 (not supported in Rails 3.0) because the
> cache uses a Hash
> # key. Since Ruby 1.8.6 implements Hash#hash usi
On Thu, Sep 3, 2009 at 10:02 AM, Czarek wrote:
> Am I overreacting or is anyone else a tiny bit annoyed by the size of
> these emails? If you're mobile with a GSM card out of UTMS range , you
> have around 4-8kB/s, and 70kB per mail is a noticeable wait.
>
> The summary at the top is fine, but I
On Mon, Aug 31, 2009 at 10:06 PM, wrote:
>
> The build failed.
>
> CHANGES
> ---
> Build was manually requested.
>
The "Build Now" button is tempting, but there's no need to click it. It
will build automatically on the next commit :)
--~--~-~--~~~---~--~~
Y
On Mon, Aug 31, 2009 at 9:19 PM, Ryan Bigg (Radar)
wrote:
> PUBLIC HUMILIATION!!!
>
>
Hehe, this one is because the gem didn't propogate yet. But now we know it
works Beware!
-- Chad
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
On Fri, May 22, 2009 at 4:37 PM, Jason King wrote:
> So now I'm confused, because my test fails with the same versions of
> SQLite2 and same sqlite-ruby gem as the CI machine. I can reproduce
> the bug in last_insert_rowid() directly in SQLite2 (by using those
> large ids) so I have to conclude
On Fri, May 22, 2009 at 4:24 PM, Jason King wrote:
>
> Can someone tell me which version of sqlite is used on the CI
> machine? (Or, even better, how to find out?)
>
> I'm seeing what looks like a bug in my 2.8.17 for the
> last_insert_rowid() function with the high PKey IDs that the test
> fixt
I believe this:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2686-fix-ci-build-patch-fix-eager-association-test-related-to-different-ordering-on-sqlite
fixes the only (current) build failure for master branch:
http://ci.rubyonrails.org/builds/rails
-- Chad
--~--~---
Yay :)
-- Forwarded message --
From:
Date: Sun, May 17, 2009 at 1:06 PM
Subject: [CruiseControl] rails build 01d7acd fixed
To: thewoolley...@gmail.com
The build has been fixed.
CHANGES
---
Revision ...01d7acd committed by Joshua Peek on
2009-05-17 19:42:36
Fix reset
On Tue, Apr 28, 2009 at 2:51 AM, Michael Koziarski
wrote:
>> Some of us are having problems running vendored edge Rails.
>
> Edge rails is likely to be a rough ride for a while until the
> refactoring for 3.0 slows down. You should probably track 2-3-stable
> instead.
The CI build for edge is g
On Wed, Apr 22, 2009 at 10:51 AM, Pratik wrote:
>
> Which problem is it solving for you ? Do you see any performance gains
> that I'm missing ? Do you believe if this is making any code easier to
> understand ? Could you please provide failing tests which are to be
> fixed by the refactoring in q
On Fri, Apr 17, 2009 at 1:09 AM, Chad Woolley wrote:
> I'd like to see the CI build kept green through these efforts:
>
> http://ci.rubyonrails.org/builds/rails
Ah, it is green again. Nice :)
-- Chad
--~--~-~--~~~---~--~~
You received this messa
On Thu, Apr 16, 2009 at 9:03 AM, Yehuda Katz wrote:
> 2.3 application. We're obviously not done yet (by any stretch), but if
> you go through the new_base specs, I think you'll be pleased with our
> thoroughness.
>
> I'd be happy to answer any other questions you might have.
I'd like to see the
On Sun, Mar 29, 2009 at 12:13 PM, kaluza_klein wrote:
> One of the ideas implemented to a certain extent and suggested
> is by brynary to parallelize testing and using bonjour for auto
> discovery of test servers.
Shared test server farms are a lot of work and effort to get right. I
was
On Thu, Mar 12, 2009 at 9:10 AM, Tekin Suleyman wrote:
> This looks good to me, much neater than having separate tables or extra
> columns to maintain migrations from plugins.I think it's perfectly
> reasonable to expect a user of a plugin to copy the migrations that creates
> the models to their
On Wed, Feb 25, 2009 at 4:25 AM, Manfred Stienstra wrote:
>
> Ok, I spent some time digging through commits and writing tests. The
> tests I wrote actually don't have anything to do with reloading
> because I couldn't find a recent commit that required any forking or
> spawning to test.
>
> http
On Tue, Feb 24, 2009 at 12:41 PM, Manfred Stienstra wrote:
> My first intuition is to spawn new Rails process from a test and see
> if it behaves the way it should. I'll try to free up some time
> tomorrow to give it a try.
The tricky part of this would be to ensure that the spawned
environment
On Tue, Feb 10, 2009 at 4:46 PM, Nick Hoffman wrote:
>
> Are the Railties tests current and passing at the moment? I ask
> because I found an old thread saying that they're neglected [1], but I
> can't find any recent discussions.
> -Nick
>
> [1] http://tinyurl.com/acuhkr
Well, SOME of them are
On Thu, Jan 29, 2009 at 5:09 AM, Mike Gunderloy wrote:
> One possible resolution would be for us to have both gems available on
> the CI server, and to increase the sophistication of the build script
> to run the AR tests using each one in isolation - I know Chad Woolley
> was looki
On Sun, Jan 25, 2009 at 8:36 PM, Michael Koziarski
wrote:
> Send us a patch with test for this one, nice find!
Yeah, great catch. This totally bit me on some daemons in the past
when the mysql connection died after several days...
-- Chad
--~--~-~--~~~---~--~~
On Sun, Jan 25, 2009 at 9:08 AM, Josh Susser wrote:
>
> This is a good improvement, but I dislike that building gems loads the
> environment at all. If something in your environment file uses a
> class defined in a gem, you get a circular dependency where you need
> the gem you're trying to buil
On Wed, Jan 14, 2009 at 12:13 PM, Chad Woolley wrote:
> 2009/1/14 Mike Gaffney :
>> On a separate note, I think it would be beneficial to have an easy, built in
>> way to run YOUR app against edge or latest of a given branch (like
>> 2.2-stable).
>
> As I mentioned bef
2009/1/14 Mike Gaffney :
> We've been looking at switching to integrity as well. One of the major
> benefits I see at the moment is that integrity would likely be more willing
> to accept features.
We are running the ci.rubyonrails.org off my ccrb GitHub branch, and
it's possible that ThoughtWork
On Tue, Jan 13, 2009 at 9:05 PM, Jeremy McAnally
wrote:
>
> Hey guys and gals,
> I suggested that perhaps we should use Integrity
> (http://github.com/foca/integrity) for the CI for Rails rather than
> CC.rb. DHH said he was all for it, but I should bring it before you
> all before he made a dec
On Tue, Nov 18, 2008 at 8:57 AM, Geoff B <[EMAIL PROTECTED]> wrote:
>
> Adam and Chad -- curious to know if this setup would work for you:
>
I was just bikeshedding about the dubiousness of bundling a hacked version
of a dependency gem in another gem, and adding code manage the resulting
problems
On Thu, Nov 13, 2008 at 12:25 PM, Adam Greene <[EMAIL PROTECTED]> wrote:
> If I'm the only one who was bit by this issue, then so be it. But if
> it keeps coming up, putting the full gem (with the extra 2.6 megs and
> hundreds of files; yes it is a beast!) into vendor/ doesn't seem to be
> all th
On Tue, Nov 11, 2008 at 4:57 PM, Geoff B <[EMAIL PROTECTED]> wrote:
>
> On Nov 11, 2:02 pm, "Chad Woolley" <[EMAIL PROTECTED]> wrote:
> > Why does it need to be bundled rather than be a normal gem dependency?
>
> By bundling tzinfo, everything works out
On Tue, Nov 11, 2008 at 7:27 AM, Geoff B <[EMAIL PROTECTED]> wrote:
>
> Adam,
>
> The bundled tzinfo is a slimmed-down version that only includes the
> classes and zone definitions necessary to support
> ActiveSupport::TimeZone. This chops ~2.8MB from the size of tzinfo,
> and hundreds of files, s
On Thu, Oct 23, 2008 at 4:53 AM, Michael Koziarski <[EMAIL PROTECTED]>wrote:
> * 2.2.0 for RC1
> * 2.2.0.N for RCN
> * 2.2.1 for Final 2.2 release
>
+1
It might be more consistent to make RC1 be 2.2.0.1, but this is fine.
The basic idea is that 2.1 is not 2.2. If people want to stay on 2.1, or
On Fri, Oct 17, 2008 at 7:58 AM, Damian Janowski
<[EMAIL PROTECTED]>wrote:
>
> Hey all,
>
> So currently there's no way to automatically get Rake tasks from your
> config.gems.
>
> Issue and discussion here:
> http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/59
>
> If we do this,
1 - 100 of 172 matches
Mail list logo
