Re: db:pull = Internal server error
Give this another shot on Ruby 1.9, it should be fixed now. Thanks, David On Nov 30, 2010, at 1:10 AM, Emanuele Tozzato wrote: problem solved using ruby 1.8.7, but I am sure I successfully used more recent versions.. Did I miss any update? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
Different size fonts and images between localhost and heroku
Hi folks, I'm not sure if this is specific to Heroku or not, but it's still driving me nuts. My site looks different when viewed running on localhost compared to when it's deployed to heroku, even when viewed in the same browser. By different, I mean my fonts and images are a lot smaller in production (maybe 25% smaller) compared to localhost. It's throwing all my styling out and makes it a pain to layout the page properly. Anybody seen this before? Chris -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: HTML5 manifest caching on Heroku
I have HTML5 offline-capable apps running off Heroku and have had no issues so far; we've had them used across a fairly wide range of devices, too. FWIW, I didn't have any problems with the links below in either desktop or mobile Safari; loading the page once, turning on airplane mode, closing the tab and visiting the same URL worked fine. (iPhone 4 on iOS 4.1.) Rufo On Tue, Nov 30, 2010 at 1:13 AM, railsnerd rails.n...@gmail.com wrote: Adam Wiggins kindly put up a cache manifest example: http://cachemanifest.heroku.com/clock.html I notice that this does work when I reload the page that is already open in iPhone Safari However if I load the clock url on a fresh safari page, the cache does not kick in. Is this a heroku issue? The manifests seem to be set up ok from what I can see? The reason I am wondering is that other manifest examples, outside of heroku, do work eg: http://www.thecssninja.com/demo/offline_webapp/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: patron gem install issues
According to https://github.com/toland/patron/issues#issue/25 instaling older patron gem will work fine with curl 7.18: $ gem install patron -v0.4.9 and it works indeed. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: App Timeouts
On Nov 30, 2:55 am, mattsly matt...@gmail.com wrote: So I've been trying to get rack-timeout installed, but it's causing consistent, though non-deterministic, application crashes from which my app won't recover. I've had to rollback. Can you tell me more about the nature of these crashes? What do you see, what do you mean by won't recover? How were you getting your app back on track? By restarting it? Mostly, I'd love to see a stack trace if that's possible. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: HTML5 manifest caching on Heroku
I can't test the example right now, but I would like to remind you that appcache or manifest cache is still in at a experimental stage. If you think it works inconsistently with Safari, better not even try with Firefox (yet). It all depends on the version though. On Tue, Nov 30, 2010 at 6:35 PM, Rufo Sanchez r...@rufosanchez.com wrote: I have HTML5 offline-capable apps running off Heroku and have had no issues so far; we've had them used across a fairly wide range of devices, too. FWIW, I didn't have any problems with the links below in either desktop or mobile Safari; loading the page once, turning on airplane mode, closing the tab and visiting the same URL worked fine. (iPhone 4 on iOS 4.1.) Rufo On Tue, Nov 30, 2010 at 1:13 AM, railsnerd rails.n...@gmail.com wrote: Adam Wiggins kindly put up a cache manifest example: http://cachemanifest.heroku.com/clock.html I notice that this does work when I reload the page that is already open in iPhone Safari However if I load the clock url on a fresh safari page, the cache does not kick in. Is this a heroku issue? The manifests seem to be set up ok from what I can see? The reason I am wondering is that other manifest examples, outside of heroku, do work eg: http://www.thecssninja.com/demo/offline_webapp/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Different size fonts and images between localhost and heroku
Some ideas... Check the style assets loaded on local host versus production. There is probably a difference. Force your browser to to a hard reload. Make sure your browser wasn't put into a zoom mode for your production URL. Sent from my iPhone On Nov 25, 2010, at 12:44 PM, Chris Walsh chriswa...@ireland.com wrote: Hi folks, I'm not sure if this is specific to Heroku or not, but it's still driving me nuts. My site looks different when viewed running on localhost compared to when it's deployed to heroku, even when viewed in the same browser. By different, I mean my fonts and images are a lot smaller in production (maybe 25% smaller) compared to localhost. It's throwing all my styling out and makes it a pain to layout the page properly. Anybody seen this before? Chris -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Different size fonts and images between localhost and heroku
More diagnostics - For every browser? For other users pointed at heroku, which version do they get? Does Firebug tell you what you expect? On Tue, Nov 30, 2010 at 12:38 PM, Brandon Casci brandon.ca...@gmail.comwrote: Some ideas... Check the style assets loaded on local host versus production. There is probably a difference. Force your browser to to a hard reload. Make sure your browser wasn't put into a zoom mode for your production URL. Sent from my iPhone On Nov 25, 2010, at 12:44 PM, Chris Walsh chriswa...@ireland.com wrote: Hi folks, I'm not sure if this is specific to Heroku or not, but it's still driving me nuts. My site looks different when viewed running on localhost compared to when it's deployed to heroku, even when viewed in the same browser. By different, I mean my fonts and images are a lot smaller in production (maybe 25% smaller) compared to localhost. It's throwing all my styling out and makes it a pain to layout the page properly. Anybody seen this before? Chris -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: HTML5 manifest caching on Heroku
Adam Wiggins kindly put up a cache manifest example: http://cachemanifest.heroku.com/clock.html I notice that this does work when I reload the page that is already open in iPhone Safari However if I load the clock url on a fresh safari page, the cache does not kick in. Is this a heroku issue? The manifests seem to be set up ok from what I can see? It works on Chrome 8.0.552/ubuntu. It must be a safari issue. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: App Timeouts
Yeah unfortunately I missed the log entries where the crash first occurred, and I didn't have a tail -f going (dumb) so I don't know the request that caused it. And nothing was logged to exceptional so I don't have a stacktrace - maybe the Heroku guys can dig one up? (I also have a thread open w/ support about the issue) In terms of being unrecoverable, once the original crash happened, every subsequent resulted in an App Crashed response from the dyno - here's a sample from the logs (just after the first crash event - really just missed by seconds, sadly...) 2010-11-29T20:14:15-08:00 heroku[nginx]: GET /letters/recently_written? offset=48 HTTP/1.1 | [ip address] | 3310 | http | 500 2010-11-29T20:14:20-08:00 heroku[router]: Error H10 (App crashed) - GET www.futureme.org/letters/recently_written dyno=none queue=0 wait=0ms service=0ms bytes=0 2010-11-29T20:14:20-08:00 heroku[nginx]: GET /letters/recently_written? offset=48 HTTP/1.1 | [ip address] | 3310 | http | 500 2010-11-29T20:14:25-08:00 heroku[router]: Error H10 (App crashed) - GET www.futureme.org/letter/218665-no-subject dyno=none queue=0 wait=0ms service=0ms bytes=0 2010-11-29T20:14:31-08:00 heroku[router]: Error H10 (App crashed) - GET www.futureme.org/letter/218665-no-subject dyno=none queue=0 wait=0ms service=0ms bytes=0 2010-11-29T20:14:31-08:00 heroku[router]: Error H10 (App crashed) - GET www.futureme.org/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2010-11-29T20:14:31-08:00 heroku[nginx]: GET / HTTP/1.1 | [ip address] | 3310 | http | 500 2010-11-29T20:14:36-08:00 heroku[router]: Error H10 (App crashed) - GET futureme.org/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2010-11-29T20:14:36-08:00 heroku[nginx]: GET / HTTP/1.1 | [ip address] | 3310 | http | 500 2010-11-29T20:14:37-08:00 heroku[nginx]: GET /letters/our_favs? offset=483 HTTP/1.1 | [ip address] | 6194 | http | 200 2010-11-29T20:14:37-08:00 heroku[router]: Error H10 (App crashed) - GET www.futureme.org/ dyno=none queue=0 wait=0ms service=0ms bytes=0 I got back on track by commenting out the two gems (system-timer and rack-timeout) and then redeploying. But until I did that, every request was hitting the Application crashed page. Feel free to ping me offline to discuss more. I tried to repro in my staging environment for a while last night but couldn't but can keep giving it a shot. Matt On Nov 30, 1:07 pm, Caio Chassot caio.chas...@gmail.com wrote: On Nov 30, 2:55 am, mattsly matt...@gmail.com wrote: So I've been trying to get rack-timeout installed, but it's causing consistent, though non-deterministic, application crashes from which my app won't recover. I've had to rollback. Can you tell me more about the nature of these crashes? What do you see, what do you mean by won't recover? How were you getting your app back on track? By restarting it? Mostly, I'd love to see a stack trace if that's possible. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
