Re: Trouble with hoptoad
On Sun, Apr 12, 2009 at 8:44 PM, shenry stuarthe...@gmail.com wrote:
I have this same problem, Hoptoad will correctly send a message after
heroku rake hoptoad:test but if I create an exception manually I get
nothing
Hoptoad Success: Net::HTTPOK
Rendering /disk1/home/slugs/2185_8e050c1_3bb1/mnt/public/500.html (500
Internal Server Error)
Any ideas?
There's an open bug in the hoptoad plugin. Full detail below but the
quick workaround is to add async. to the environment_filters in
config/initializers/hoptoad.rb as follows:
HoptoadNotifier.configure do |config|
config.api_key = 'YOUR KEY'
config.environment_filters 'async.'
end
This causes the notifier to remove any matching keys before building
the YAML payload to send to hoptoad.
Here's my original write up on the issue. I'm under the impression
that the thoughtbot folks are aware of this. Maybe someone on the list
can bring it to the right person's attention:
This issue occurs when there are complex objects in the request
environment. The hoptoad plugin builds a POST body to send to the
hoptoad server by converting the session, environment, request,
backtrace, and error_message into YAML. Heroku loads a special version
of Thin that places two special variables in the environment:
async.callback and async.close. These are both Proc/Method objects
but could theoretically be any object not directly serializeable to
YAML. When these objects are converted to YAML, they look like this:
async.callback: !ruby/object:Method {}
I assume some kind of deserialization exception is occurring on the
hoptoad server when an attempt is made to parse the YAML. The right
fix is probably to adjust the following code in the hoptoad plugin:
def clean_non_serializable_data(notice) #:nodoc:
notice.select{|k,v| serializable?(v) }.inject({}) do |h, pair|
h[pair.first] = pair.last.is_a?(Hash) ?
clean_non_serializable_data(pair.last) : pair.last
h
end
end
def serializable?(value) #:nodoc:
!(value.is_a?(Module) || value.kind_of?(IO))
end
The serializable? check should probably be a whitelist of allowed
value types instead of a blacklist of disallowed value types. Adding
Method/Proc to the current list of disallowed types would also solve
this issue but it will happen again with some other object. It's
becoming a very common pattern in Rack to add various types of objects
to the environment.
Thanks,
Ryan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en
-~--~~~~--~~--~--~---
Re: Trouble with hoptoad
There's an open bug in the hoptoad plugin. Full detail below but the quick workaround is to add async. to the environment_filters in config/initializers/hoptoad.rb as follows: HoptoadNotifier.configure do |config| config.api_key = 'YOUR KEY' config.environment_filters 'async.' end Thanks for the detailed response, Ryan! I already have the 'async.' workaround in hoptoad.rb, so I assume this is a separate issue with Hoptoad? I'll post a ticket and see if they have a fix for this. Thanks, Stu --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
.gems and curb gem
The curb gem won't take when I add it to the .gems file. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Trouble with hoptoad
This is the response I got from hoptoad when I posted the same problem there -- Forwarded message -- From: Hoptoad Support no-re...@help.hoptoadapp.com Date: Wed, Mar 18, 2009 at 5:18 PM Subject: Re: errors not reported, seeing standard rails error page [Problems] To: yuric...@gmail.com // Add your reply above here == From: tammersaleh Subject: errors not reported, seeing standard rails error page Can you try installing the latest version of the notifier from github? There was an issue with rack sending non-serializeable attributes that the heroku guys caught for us. This should fix the issue. If it does, then feel free to resolve this thread for us. Thanks, Tammer View this Discussion online: http://help.hoptoadapp.com/discussions/problems/65-errors-not-reported-seeing-standard-rails-error-page --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Database layer autoscaling?
Hello, I am intrigued by the heroku value proposition. From the online information regarding heroku and it's capabilities, it is a little unclear if heroku solves the problem of auto scaling the database layer. I notice there is an option for providing database replication. I assume this would be in a master slave type setup? What is to be done if there needs to be more than one slave? Or is this totally handled by heroku's infrastructure wherein heroku can scale the database layer infinitely without the developer ever having to worry about setup and optimizing the databases themselves. If there is anyone who can shed light into the topic about how heroku handles db scaling and if this is left to the developer to handle or if heroku is capable of handling 100% of this process, I would really appreciate it. Best, Marc --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: db:push internal server error
Ricardo, thanks! Upgrading to taps 0.2.14 fixed the following error: Taps Server Error: PGError ERROR: value 20090410004412 is out of range for type integer On Apr 12, 6:36 pm, Michael Keenan michael.kee...@gmail.com wrote: Thanks, that worked! I'm writing an application that includes Chinese characters. When I push my database from my local computer to Heroku, all the Chinese characters come out as question marks. Is there anything I can do about that? On Sat, Apr 11, 2009 at 7:15 AM, Ricardo Chimal, Jr. rica...@heroku.comwrote: taps 0.2.14 should fix your schema_migrations issue. also, you can wipe out (reset) your database by doing heroku db:reset --app app name On Apr 9, 9:44 pm, Bill Burcham bill.burc...@gmail.com wrote: The reason it worked for me was that: precondition: fully migrated schema existed on heroku 1. tried to push from local db to heroku–this failed because of schema_migrations primary key conflict (I surmise) 2. deleted all schema_migrations records from my local db 3. successfully pushed from local db to heroku See my heroku db already had good schema_migrations to start with. Better solution would have been to drop all my data from heroku before the push. But I don't think heroku provides any such canned capability. I did find a rake task that purported to do it though. Haven't tested it yet. -- Michael Keenan michael.kee...@gmail.com (+886) 0981447531 michaelkeenan.blogspot.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
phpMyAdmin equivalent?
Is there some sort of equivalent to phpMyAdmin where we can tinker with the database in production? For better or worse, I tend to use phpMyAdmin as my admin interface in the early stages of a website to fix problems for various users, etc. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Caveats for root-level domain?
Interesting, I was able to set it up as a root level domain with GoDaddy.com buyersvote.com pointing to heroku.com @Keenan, what did you have to do with the MX records? I am using Google Apps to handle the email and I assume I should setup something like this? http://articles.slicehost.com/2007/10/25/creating-mx-records-for-google-apps It looks like Heroku already has these MX records setup for Google Apps: Macintosh:BuyersVote barmstrong$ host buyersvote.com buyersvote.com is an alias for heroku.com. heroku.com has address 75.101.163.44 heroku.com has address 75.101.145.87 heroku.com mail is handled by 5 alt2.aspmx.l.google.com. heroku.com mail is handled by 10 aspmx2.googlemail.com. heroku.com mail is handled by 10 aspmx3.googlemail.com. heroku.com mail is handled by 10 aspmx4.googlemail.com. heroku.com mail is handled by 10 aspmx5.googlemail.com. heroku.com mail is handled by 1 aspmx.l.google.com. heroku.com mail is handled by 5 alt1.aspmx.l.google.com. But I'm guessing I should set it up with my own domain on GoDaddy to avoid potential spam issues? (where the email from address says buyersvote.com but the reverse dns says heroku?) I don't quite understand how this works, just guessing...if someone has more info please let me know. Thanks! Brian On Apr 12, 7:20 pm, Matthew Winter winte...@teratools.com wrote: Hi, I read an blog post recently on the subject of comparing hosted DNS providers: http://dns.learnhub.com/lesson/11620-how-to-compare-hosted-dns-provid... The article got me thinking about the current use of cname at Heroku, and how you would need to incur double name resolution costs. Take your domain sonic.net. A user enters www.sonic.net into their browser, the browser then makes a requests from your DNS to be passed back the name heroku.com, a second request would then need to be made to the Heroku DNS, to obtain the IP address. So using the figures given in that website, the average response for the DNS request was 113ms, meaning for accessing an application deployed on Heroku, you would need on average 226ms, with the worst time being 760ms. So the user would have to wait up to 3/4 of a second before the browser even makes the request for the webpage. Maybe Heroku could offer DNS services, as a paid for option. So removing the need for 2 requests, and therefore cutting the response times even further. As long as we have some way of modifying the MX records I am sure most people would be happy to pay for the service, once there sites take off. Regards Matthew Winter On 13/04/2009, at 2:24 AM, shenry wrote: I wasn't able to get Sonic.net to allow the root-level domain to point to either the www subdomain or heroku.com (in both cases it said it was an invalid IP.) I had to make an .htaccess file that redirects root-level domain requests to the www subdomain, which then goes to heroku.com I'm sure this is hurting performance but I'm not sure if there is another way to get sonic.net to play nice. Any ideas? Stu On Apr 12, 7:27 am, Keenan Brock kee...@thebrocks.net wrote: Having a primary domain as a cname sometimes messes with mail mx records. Sometimes the DNS host can't figure it out. Godaddy gave me all sorts of issues setting up the cname. But all in all, it works in the end. Other DNS hosts are easier. Best of luck --Keenan On Apr 11, 2009, at 9:06 PM, Brian Armstrong barmstr...@gmail.com wrote: http://docs.heroku.com/custom-domains In the docs it says or it could be the root-level domain, mydomain.com, though this last one has some caveats described below. I didn't see anything describing below, what should we watch out for? Thanks! Brian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Caveats for root-level domain?
Yes, those MX records are our corporate ones for Heroku. They do no have anything to do with your apps. Best, MOrten On Apr 13, 2009, at 4:11 PM, Brian Armstrong wrote: Interesting, I was able to set it up as a root level domain with GoDaddy.com buyersvote.com pointing to heroku.com @Keenan, what did you have to do with the MX records? I am using Google Apps to handle the email and I assume I should setup something like this? http://articles.slicehost.com/2007/10/25/creating-mx-records-for-google-apps It looks like Heroku already has these MX records setup for Google Apps: Macintosh:BuyersVote barmstrong$ host buyersvote.com buyersvote.com is an alias for heroku.com. heroku.com has address 75.101.163.44 heroku.com has address 75.101.145.87 heroku.com mail is handled by 5 alt2.aspmx.l.google.com. heroku.com mail is handled by 10 aspmx2.googlemail.com. heroku.com mail is handled by 10 aspmx3.googlemail.com. heroku.com mail is handled by 10 aspmx4.googlemail.com. heroku.com mail is handled by 10 aspmx5.googlemail.com. heroku.com mail is handled by 1 aspmx.l.google.com. heroku.com mail is handled by 5 alt1.aspmx.l.google.com. But I'm guessing I should set it up with my own domain on GoDaddy to avoid potential spam issues? (where the email from address says buyersvote.com but the reverse dns says heroku?) I don't quite understand how this works, just guessing...if someone has more info please let me know. Thanks! Brian On Apr 12, 7:20 pm, Matthew Winter winte...@teratools.com wrote: Hi, I read an blog post recently on the subject of comparing hosted DNS providers: http://dns.learnhub.com/lesson/11620-how-to-compare-hosted-dns-provid ... The article got me thinking about the current use of cname at Heroku, and how you would need to incur double name resolution costs. Take your domain sonic.net. A user enters www.sonic.net into their browser, the browser then makes a requests from your DNS to be passed back the name heroku.com, a second request would then need to be made to the Heroku DNS, to obtain the IP address. So using the figures given in that website, the average response for the DNS request was 113ms, meaning for accessing an application deployed on Heroku, you would need on average 226ms, with the worst time being 760ms. So the user would have to wait up to 3/4 of a second before the browser even makes the request for the webpage. Maybe Heroku could offer DNS services, as a paid for option. So removing the need for 2 requests, and therefore cutting the response times even further. As long as we have some way of modifying the MX records I am sure most people would be happy to pay for the service, once there sites take off. Regards Matthew Winter On 13/04/2009, at 2:24 AM, shenry wrote: I wasn't able to get Sonic.net to allow the root-level domain to point to either the www subdomain or heroku.com (in both cases it said it was an invalid IP.) I had to make an .htaccess file that redirects root-level domain requests to the www subdomain, which then goes to heroku.com I'm sure this is hurting performance but I'm not sure if there is another way to get sonic.net to play nice. Any ideas? Stu On Apr 12, 7:27 am, Keenan Brock kee...@thebrocks.net wrote: Having a primary domain as a cname sometimes messes with mail mx records. Sometimes the DNS host can't figure it out. Godaddy gave me all sorts of issues setting up the cname. But all in all, it works in the end. Other DNS hosts are easier. Best of luck --Keenan On Apr 11, 2009, at 9:06 PM, Brian Armstrong barmstr...@gmail.com wrote: http://docs.heroku.com/custom-domains In the docs it says or it could be the root-level domain, mydomain.com, though this last one has some caveats described below. I didn't see anything describing below, what should we watch out for? Thanks! Brian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Internal server error when trying to execute anything in the console
Should be fixed now. Adam --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: File uploads timeout?
Dang, I've got this sort of problem now too. Users reporting timeouts on uploads to S3 via heroku of files larger than 10M 9M : OK 10M: not OK. Where did you get the error message: I haven't even got as far as finding anything telling me what's behind this. Martin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
