cation run correctly.
>
> But If I uninstall this new gem to leave the old. The error become
> again. I don't know what I have this error. I have test on another PC
> and no problem.
>
> Have you an idea ?
>
>
> [1] : http://weblog.rubyonrails.org/2007/9/30/rai
a death
sentence, just a matter of feedback change your opinion of 'closed'?
Do the 'untested', 'undocumented' resolutions hurt less?
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are sub
gt; like this or any material
> plz give some pointers
> badly needed
>
> thanks
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Co
I love the fact that all of the continuous integration reports go to
the core list. It means we have to pay attention. At the same time, it
sort of floods the rest of my core threads. Could we prefix CI reports
with [CI] or [CONTINT] or something similar so I can write a filter?
--
Kevin Clark
ed. This in itself would be a huge step,
> > > > and I don't see a lot of downside. Localizing dates and countries
> > > > could also be done much the same way.
> > >
> > > I don't quite follow how adding a String#t no-op helps the
> > >
: "Ticket #2322".
> > Here is the actual ticket:
> http://dev.rubyonrails.org/ticket/2322
> >
> >
> >
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are
TED]> wrote:
> On 5/22/07, harm <[EMAIL PROTECTED]> wrote:
> >
> > However, Using the form helper methods, it appears they are not using
> > the instance methods:
>
> This issue already has a thread: "Ticket #2322".
> Here is the actual ticket:
> http
k we should just treat that as regular patches. Like
the pagination thing.
13:50 < nextangler> Extraction plugins should live at something like
plugins/legacy on the official rails svn
13:50 < kevinclark> ah, we can just change the "Component" setti
or updates, but the core doesn't
need to deal with them.
How do people feel about that? Should the tickets be closed, as well
as tagged? I'm not sure the best way to keep those tickets out of the
patch count but still indicate that it hasn't been dealt with.
--
Kevin
plenty of
> > details, but if you think about it this guy is yanking our chain.
> >
> > * "after some months" - After several months it would be impossible to
> > be this clueless.
>
> On the contrary, I thin
p.new("|#{source}").match('').captures.length
> end
>
>
> Does this method not always return 0? It's always going to match ''
> with the blank spot before the | and therefore will have no captures.
>
>
> >
>
--
Kevin Clar
> >
> > In fact I've reconcidered and I also give a +1 now
> > CI is awareness and IMO the fact that errors clog the main list
> > prompts to fix them faster
>
> +1 from here as well.
>
> --
> Jarkko Laine
> http://jlaine.net
> http://
core. If anything, dynamic scaffolding
> would serve better as a plugin.
>
> Anyone agree?
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "R
addressing the warnings. Rails spits out tons of warnings and this is
> > definitively a pain for doing proper ruby development.
>
> Patches go to http://dev.rubyonrails.org. Knock yourself out!
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~-
er NOT NULL,
> num_disks smallint NOT NULL DEFAULT 1,
> CONSTRAINT licensed_pkey PRIMARY KEY (name, version, publisher)
> )
> WITHOUT OIDS;
>
> I have no trouble with the scaffolding for sites, computers, and
> technicians but it throws up on the others.
>
> Pleas
g offenders get at least
> a hand slapping.
>
> --
> Josh Susser
> http://blog.hasmanythrough.com
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
old and its author should remake the
> diff against latest trunk?
>
> When the patch is good but ignored anyway, maybe it's title or description
> are bad. Posting on this ML also helps raise awareness about those.
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~
Do note that the patch in 7110 needs Mocha 0.3.3 (released yesterday).
There was a bug that caused other problems, but it has been fixed.
On 1/18/07, Kevin Clark <[EMAIL PROTECTED]> wrote:
I've got four patches improving test coverage in various parts of the
framework that could us
/7122
http://dev.rubyonrails.org/ticket/7117
http://dev.rubyonrails.org/ticket/7110
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post
eally high? Can something be done?
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
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@google
16/07, Kevin Clark <[EMAIL PROTECTED]> wrote:
Hi guys,
I'm adding some test coverage to Rails-Core (yay heckle!), and noticed
some odd things in the routing code.
Using the latest trunk, if I do something like this:
map.resource :assertions, :name_prefix => 'bada
And that brings up another point actually.. Why when using name_prefix
does edit_assertion become edit_assertionS? The tests say that it
_should_ be the controller name (plural) instead of the singular name,
but this seems wrong.
Ideas? Is this a bug?
--
Kevin Clark
h
ng and erroring.
So the question is, am I running these right? I feel like I'm missing
something. Or perhaps the trunk of rails edge does not always pass all
its tests?
Thanks,
Eric
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You recei
re it - what I meant is should
it gracefully require it?
Dan Manges
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post t
hy this shouldn't be posssible or why it isn't
already done?
Greetings,
Esad
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core"
e in integration.rb.
> Normalising http headers is reasonably common, I believe the servlet
> API does it too (enterprise!).
>
> If changing that line back to location fixes it, then we can just commit
> that.
>
> --
> Cheers
>
> Koz
>
> >
>
--
Kev
rather than 'Location' is set
in the response header. So, now 'Location' is nil and I get URI parse
errors.
I PDId, how should we fix this?
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscrib
omatically?
>
> If there isn't, am I ok to submit a patch that fixes it?
>
> (P.S. the generator test code seems a bit thin on the ground. Have I
> missed something, or is it unloved?)
>
> Regards
>
> NeilW
>
>
> >
>
--
Kevin Clark
http://glu.
a ticket here: http://dev.rubyonrails.org/ticket/6392
Whadya think?
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
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 rub
sable in Ubuntu (Linux kernel 2.6)? (I will switch
> from WinXP SP2 to Ubuntu within the next week), is it:
> - Apache2 + FastCGI
> - WEBrick?
> - Lighttpd + FastCGI
> - Mongrel (?) -- I'm not familiar at all with mongrel or even how it
> works.
> Anyway
As of 1.1.6 this is the case. Is there a reason for this? It runs in
dev mode. In ARTS I don't want to polute Rails internals in dev or
production mode. Unfortunately I can't have passing tests _and_ keep a
handle on my objects currently.
--
Kevin Clark
http://gl
jax')
>
> => My text containing class="highlight">ajax
>
> What I want to get :
> highlight (@page.content, 'ajax')
>
> => src='ajax-image.gif' alt='Ajax Image'/>My text containing class="highlight">ajax
>
>
wonderous. Either way, easy to write find!
On 8/29/06, Jarkko Laine <[EMAIL PROTECTED]> wrote:
> On 30.8.2006, at 9.24, Kevin Clark wrote:
> >
> > Does .blank? handle [] as well as "" and nil? I was going to use
> > .empty? but then I'd have to check
Does .blank? handle [] as well as "" and nil? I was going to use
.empty? but then I'd have to check that the method existed.
On 8/29/06, Jarkko Laine <[EMAIL PROTECTED]> wrote:
>
> On 30.8.2006, at 8.43, Kevin Clark wrote:
>
> >
> >> You'd then
sn't tested.
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
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@googlegroups.com
To u
row_when_not_found => true
> :throw_when_nil => true
> :throw_on_not_found => true
> :throw_on_nil => true
> :not_found => :throw
>
> Thoughts?
>
> -- tim lucas
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~---
v/code/rails/actionpack/test/controller/cgi_test.rb:223]:
<{:user=>{:login=>"my_username", :password=>"apassword"}}> expected but was
<{"user[login]"=>"my_username", "user[password]"=>"apassword"}>.
--
Kevin Cl
ize #=> "sheep"
> "words".pluralize #=> "words"
> "the blue mailman".pluralize #=> "the blue mailmen"
>
> Although that behavior should probably also be specified in the rdoc
> in addition to exampl
) should -never- return something other than
Account objects.
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send
dig into this,
> but if you've interesting in testing it out send me a message and i'll
> send you the patch.
>
>
> >
>
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
rks find when using the site: '/projects/edit/1'
>
> However, when this code is hit froim a functinoal test, it produces:
> "/projects/edit/#"
>
> has anyone else run into this?
>
> mark
>
> --
> Mark Van Hols
> and stopped.
> >
> > Changing it to check for nil and return an empty string instead if it
> > is alleviated some of the breakage, but I had no idea *why* I was
> > making that change, only that it helped my test passing efforts.
>
>
> Set EN
All the breakage appears to be because of changes to the cgi
extensions in action controller. raw_post_data_fix.rb specifically.
Can someone more familiar with that take a look?
On 8/21/06, Kevin Clark <[EMAIL PROTECTED]> wrote:
> Yeah, I'm getting massive breakage too. I&#
Yeah, I'm getting massive breakage too. I'll PDI.
Kev
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscrib
ng so.
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe
gt; breaking backwards compatibility for people who rely on find_by_sql
> and STI? If you're using find_by_sql there are a few areas where you
> have to be careful, I'm tempted to say that this is one of them...
> --
> Cheers
>
> Koz
>
> >
>
--
Kevin C
I've got a workaround Rick. My query actually gets more complex,
that's just the important bits. It's still a bug ;)
--
Kevin Clark
http://glu.ttono.us
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google G
_id"=>"1"}>
> # #"agile", "tag_id"=>"2",
> "type"=>"TopicTag", "id"=>"2", "taggable_type"=>"Book",
> "taggable_id"=>"
Tagging belongs_to Tag which is an STI model.
Tagging.find_by_sql("SELECT * FROM taggings INNER JOIN tags ON tags.id
= taggings.tag_id").each {|t|
puts t.inspect
}
# #"ruby", "tag_id"=>"1",
"type"=>"TopicTag", "id"=>"1", "taggable_type"=>"Book",
"taggable_id"=>"1"}>
# #"agile", "tag_id"=>"2",
49 matches
Mail list logo
