I ended up using
headers['Set-Cookie'] = 'cookiename=key=value@key2=value2;
domain=.domain.com; path=/'
--
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
hi,
I'm trying to get a cookie to store in the format key=value@key2=value2 (
compatibility reasons over which I have no control ).
However, when the cookie get's set, it is stored as
key%3Avalue%40key2%3Avalue2 which is what the CGI.escaped version
of key=value@key2=value2 looks like.
How
So I solved it by doing a RACK_ENV=test before running my task. I
suspect a bug since this probably shouldn't have been required and
luckily all my related tasks here were to do with test, but they may
not have been.
Anyway, FYI
On Feb 9, 9:28 am, anywho wrote:
> this is happening in pr
So I solved it by doing a RACK_ENV=test before running my task. I
suspect a bug since this probably shouldn't have been required and
luckily all my related tasks here were to do with test, but they may
not have been.
Anyway, FYI
On Feb 9, 9:28 am, anywho wrote:
> this is happening in pr
this is happening in production only it would seem. Running 1.9.2 with
an isolated gem env via rvm
Fedora release 8 (Werewolf)
Gems included by the bundle:
* ZenTest (4.4.0)
* abstract (1.0.0)
* actionmailer (3.0.4)
* actionpack (3.0.4)
* activemerchant (1.5.1)
* activemodel (3.0.4)
t;schema_migrations"."version" FROM "schema_migrations"
Anyone?
On Jan 27, 11:28 pm, anywho wrote:
> Why would, in an upgrade from 3.0.1 to 3.0.3, a rake db:migrate run
> this:
>
> SELECT "schema_migrations"."version" FROM "schema_migrations"
Why would, in an upgrade from 3.0.1 to 3.0.3, a rake db:migrate run
this:
SELECT "schema_migrations"."version" FROM "schema_migrations"
vs this ?
SELECT `schema_migrations`.`version` FROM `schema_migrations`
__ rake db:migrate output __
rake aborted!
Mysql::Error: You have an error in your SQL
On Nov 19, 12:30 pm, Colin Law wrote:
> On 19 November 2010 17:43, anywho wrote:
>
> Could you not top post please, it is easier to follow the thread if
> replies are interleaved into previous message as appropriate. Thanks.
>
> > Hi Colin and thanks for your reply.
&
isit_CoercibleString error remaining.
The call stack is offering no clues.
On Nov 18, 8:50 am, Colin Law wrote:
> On 16 November 2010 19:18, anywho wrote:
>
> > From having no errors with 3.0.2 I now see lots of these errors when
> > running my tests.
>
> &g
anyone?
On Nov 16, 11:18 am, anywho wrote:
> From having no errors with 3.0.2 I now see lots of these errors when
> running my tests.
>
> undefined method `visit_CoercibleString' for # 0x01074f4298>
>
> Anyone know what this is?
--
You received this message bec
>From having no errors with 3.0.2 I now see lots of these errors when
running my tests.
undefined method `visit_CoercibleString' for #
Anyone know what this is?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send
Suddenly exceptional is sending emails about Mysql having gone away in
production. This had not been an issue until, well, today. No changes
have even been made. We see this with an internal product as well.
Does anyone know how to prevent this from happening? Why isn't rails
handling this more gra
On Aug 10, 12:29 am, Colin Law wrote:
> On 10 August 2010 01:29, Sandy wrote:
>
> Please don't top post, it makes it difficult to follow the thread.
> Insert your reply at appropriate points in the previous mail. Thanks.
>
> > Daniel,
>
> > While I'm sure that you had good intentions, the tuto
here we go... I filed this ticket:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5246
On Jul 29, 8:31 pm, anywho wrote:
> I should probably mention that this is with rails3 and the file you
> refer to doesn't exist in rails3
>
> On Jul 29, 8:27
I should probably mention that this is with rails3 and the file you
refer to doesn't exist in rails3
On Jul 29, 8:27 pm, anywho wrote:
> Thanks but that didn't help. I've followed the documentation here:
>
> http://api.rails.info/classes/ActionController/HttpAuthentic
> Cheers,
> Bala
> RoR Developer Now Available for Hire
>
>
>
>
>
> On Thu, Jul 8, 2010 at 9:21 AM, anywho wrote:
> > hi, I've got an api which is using
> > authenticate_or_request_with_http_basic
>
> > What are you guys using to test this? I'm us
hi, I've got an api which is using
authenticate_or_request_with_http_basic
What are you guys using to test this? I'm using rspec, and before I
was using rspec-rails, I was using authorize from Rack::Test to do the
authentication. However, authorize clearly doesn't work when using
rspec-rails, so I
Marnen Laibow-Koser
> > wrote:
> >> anywho wrote:
> >>> does rails always need to update the development database before
> >>> running the
> >>> tests? It seems to insisit on running db:migrate before.
>
> >> Your production DB is
does rails always need to update the development database before
running the
tests? It seems to insisit on running db:migrate before. Why can't it
just update
the test database? This can be annoying if I'm in a production
environment and I
don't want a migration to happen until I know the tests pas
anyone?
On May 27, 10:29 am, anywho wrote:
> I've been looking at rescue_from and rescue_action_in_public however,
> none of them have worked without making a catch-all route.
>
> So currently, my solution is to use the catch-all route: match
> '*path' =>
I've been looking at rescue_from and rescue_action_in_public however,
none of them have worked without making a catch-all route.
So currently, my solution is to use the catch-all route: match
'*path' => "controller#action" # custom 404 which then renders a 404
with the appropriate layout whethe
Why is rails3 so slow to initialize?
I am running 1.9.1 which I know is known to give some rails3 issues.
Can that be the reason? Here's a very very basic test.
$ rvm 1@rails2
$ rails new_rails2
$ cd new_rails2
$ time ./script/runner ''
real0m1.583s
$ rvm 1@rails3
$ rails new_rails3
hi,
During the migration to a new server, I started running into some
issues. I'd been running production on passenger which does not seem
to have any problems, but the idea was to now use unicorn or thin or
some other server to spawn the instances.
When starting unicorn, thin or webrick in produ
23 matches
Mail list logo
