HTML5 manifest caching on Heroku

[railsnerd]

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.

Re: db:pull => Internal server error

[Emanuele Tozzato]

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.

db:pull => Internal server error

[Emanuele Tozzato]

Hello All!

Did I miss any update? I am not able to pull or push my databases
anymore! Last successful operation around Nov, Sun the 21st!

E/

Gems:

taps (0.3.14)
sqlite3-ruby (1.3.2)
mysql (2.8.1)
sequel (3.17.0)
heroku (1.14.5, 1.14.3)

Ruby: ruby 1.9.2p0 (2010-08-18 revision 29036) [i386-darwin9.8.0]

https://gist.github.com/721215

-- 
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

[mattsly]

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.

I'm on Rails 3.0.1 on Bamboo (Ruby 1.8.7)

Basically, per README here:
https://github.com/kch/rack-timeout

...I add two lines to my Gemfile
gem "system_timer" if RUBY_VERSION < "1.9"
gem "rack-timeout"

...and that causes the crash (after running peachy keen for a few
minutes, even up to an hour or so...) Comment them out, and we're all
good.

Have others had success using rack-timeout?



On Nov 7, 9:34 pm, Subramanya Sastry  wrote:
> Aha!  Thanks for the explanation.  That is very helpful.  So, it could
> just be a single bad request that pretty much times out all additional
> requests down the pipe.  We've added rack-timeout already, and next
> time we hit one such bad request, we'll know with an exceptional
> report!
>
> Subbu.
>
>
>
>
>
>
>
> On Sun, Nov 7, 2010 at 8:27 PM, daniel hoey  wrote:
> > Just to follow up on my original post: We had one action that we knew
> > had a timeout problem but we hadn't prioritized fixing it. We
> > eventually discovered that this action caused other requests to
> > timeout. The understanding that I got from talking to Heroku support
> > is when a request comes in it gets assigned to a dyno immediately. For
> > the purposes of herokutimeoutsthe request 'start time' is now. But
> > if that dyno is currently processing some other request then the new
> > request will just wait. If 30 seconds passes and the first request has
> > not finished processing, then both requests timeout. Note also that if
> > the first request takes 29s and the second request takes 2s then the
> > second request will timeout.
>
> > We ended up putting SystemTimer (http://systemtimer.rubyforge.org/)
> >timeoutsaround some of our actions and filters so an exception gets
> > raised when something times out, rack-timeout looks like a better way
> > of doing this. We also used New Relic Silver to find the actions that
> > where the root cause of the problem.
>
> > Basically the moral of the story is that you have to make sure that
> > none of your actions ever timeout.
>
> > On Nov 6, 4:31 am, Oren Teich  wrote:
> >> I've seen a few people with weirdtimeoutswhere theappowner was
> >> able to find out that it was a bug in their code.  Anything from a
> >> weird SQL query locking a table that was hanging their process to API
> >> requests to other hard to track stuff.
>
> >> This gem (http://github.com/kch/rack-timeout) will timeout your
> >> requests after a period you specify.  The advantage of this is you can
> >> set it to a short time, and exceptional/hoptoad should catch the
> >> timeout giving you some indication in the backtrace of what's going
> >> on.
>
> >> Oren
>
> >> On Fri, Nov 5, 2010 at 9:06 AM, Subbu Sastry  wrote:
> >> > Has anyone found a reasonable solution to this problem yet?  On our
> >> >appas well, we notice totally random timeout errors that couldn't
> >> > possibly be associated with db lookup -- sometimes request time out on
> >> > pages that lookup a row by primary key on a table with 15 records.
> >> > Favicon.ico timed out as well.  Thetimeoutsseem arbitrary, and
> >> > *always* get fixed on server restart (heroku restart).  This has
> >> > happened to us a few times over the last week.  And yes, as several of
> >> > you have noted, there is no exceptions raised (neither exceptional nor
> >> > NewRelic).
>
> >> > I think given that we experienced timeout with favicon.ico and an
> >> > about page with a single db lookup and newrelic doesn't see this at
> >> > all, I suspect this is something higher up the heroku stack that is
> >> > timing out .. It almost smells like a memory leak somewhere which is
> >> > howapprestart seems to fix the problem.  Now, the question is
> >> > whether the memory leak is in ourappor somewhere else (plugins,
> >> > gems, interaction with heroku stack) ... I will debug this, but wanted
> >> > to see if someone else has found a reasonable solution to this.
>
> >> > Subbu.
>
> >> > On Oct 6, 9:37 pm, mattsly  wrote:
> >> >> In just manual testing myapp, I've seen a fair number oftimeouts
> >> >> (maybe a dozen) but have not received any communication.  I am pretty
> >> >> sure I'd have no idea they occurred had I not personally witnessed the
> >> >> error page.  I find this a borderline "ship blocker" for a migration
> >> >> to Heroku as I consider migrating a ~500K monthly page viewappto
> >> >> Heroku, and get very anxious thinking about lots of users seeing funky
> >> >> error page and having no way of being alerted or knowing how prevalent
> >> >> the issue is.
>
> >> >> WRT to thetimeouts, it's maybe 1% of requests thattimeout...and I
> >> >> still can't pin down why they're happening.  I'm on a single dyno,
> >> >> with Koi, and < 5 alpha testers on it "concurrently" (andtimeout
> >> >> errors are related to response...not concurrency...) and these are
> >>

Re: HTTP deployhook erroring?

[Pedro Belo]

Hi Jason,

I just checked, we are passing all available variables to the POST
payload. Can you read from it instead?

Thanks,
Pedro

On Fri, Nov 19, 2010 at 2:10 PM, Pedro Belo  wrote:
> Hi Jason,
>
> Ah, we don't support variables on the POST url at this moment.
> I'll add support for it and get back to you once it's deployed.
>
> Thanks,
> Pedro
>
> On Fri, Nov 19, 2010 at 1:41 PM, Jason Morrison
>  wrote:
>> Hi Pedro,
>> Thanks - I pasted the whole response.  All I get is (from the gist above):
>>
>> -> Running HTTP POST to
>> https://hoptoadapp.com/deploys.txt?deploy[local_username]={{user}}&deploy[scm_revision]={{head_long}}&deploy[rails_env]=production&api_key=REDACTED...
>> FAILED
>>  !     Internal error
>>
>>
>>    http://evening-frost-43.heroku.com deployed to Heroku
>>
>> Thanks,
>> Jason
>> n Fri, Nov 19, 2010 at 3:06 PM, Pedro Belo  wrote:
>>>
>>> Does it show you the status code? When we get a bad response like 404
>>> or 500 we do display the code.
>>>
>>> On Wed, Nov 17, 2010 at 2:47 PM, Jason Morrison
>>>  wrote:
>>> > Hi all,
>>> >
>>> > I'm trying to configure an HTTP deploy hook, but receiving an error
>>> > upon deploy - see https://gist.github.com/736c1053562e4cf069ed
>>> >
>>> > I'm not seeing the HTTP request actually make it to the server
>>> > (working on integrating deploy notification into the Heroku addons -
>>> > let me know if I should move this discussion to the addon providers
>>> > list).
>>> >
>>> > Any insights?  Does the "! Internal Error" signify a non-2xx HTTP
>>> > response from the endpoint, or that something went wrong inside the
>>> > Heroku deploy hook addon?
>>> >
>>> > Thanks,
>>> > Jason
>>> >
>>> > --
>>> > 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.
>>>
>>
>>
>>
>> --
>> Jason Morrison
>> thoughtbot.com
>> 585-216-5657
>> @jayunit
>>
>> --
>> 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: Automating pgbackups

[Peter van Hardenberg]

ENV["DATABASE_URL"] will be the URL that the database written to
database.yml lives on.

On Mon, Nov 29, 2010 at 3:05 AM, Neil  wrote:

> We've many apps on Heroku (read about 30) of which roughly ten are
> production apps.
>
> Therefore I've been looking at creating a little management app to
> backup all the production apps on an hourly cron (and thus only pay
> for cron once).  Question is, using the above rake tasks, what URL
> should be used for a specific db?  Currently I'm using
> ENV["SHARED_DATABASE_URL"] but I keep getting back that it's a bad
> URI.
>
> Does anyone have any pointers on this?  Hopefully if I get it working
> I can open it up to folks
>
> N
>
> On Nov 19, 12:22 am, "Andrew C."  wrote:
> > I've got a lot on my plate right now, but I'm not opposed to getting
> > it into a usable state for other people once I get some spare time.
> >
> > On Nov 17, 2:10 am, Trevor Turk  wrote:
> >
> >
> >
> >
> >
> >
> >
> > > On Nov 16, 6:44 pm, "Andrew C."  wrote:
> >
> > > > I spin up an EC2 instance from my cron job.  The EC2 instance
> captures
> > > > and downloads the backup to S3, then shuts itself down.  Works well
> so
> > > > far.  Obviously, it's not free, but it's freaking cheap.
> >
> > > Any chance of open-sourcing some of that code? It's an interesting
> > > idea. I'm still hoping there's an easier way, but this is certainly an
> > > idea!
> >
> > > - Trevor
>
> --
> 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: Bogus bundle not complete messages

[Wes Gamble]

Yes I do, and I'm currently using "development test".  I'll give 
"development:test" a shot.  Thanks!


Also, if this does happen again, is there any way to tell Heroku to 
rebuild the bundle without presenting a changed Gemfile.lock file?  It's 
really annoying to have to do 2 bogus deploys to get bundler synced up.


W

On 11/29/10 11:57 AM, Steve Smith wrote:
Wes, do you have bundle without set? I had this error and the Heroku 
guys determined I should have used "development:test" and not 
"development test" could be the same issue?


Steve

On 29 Nov 2010, at 17:43, Wes Gamble > wrote:


Occasionally in the last week, I keep getting messages about bundler 
not finding some gems for my app., even though on these deploys, I 
haven't changed my Gemfile or Gemfile.lock files.


The only way I seem to be able to fix it is to deploy a changed 
Gemfile/Gemfile.lock (commenting out some random gem), deploying 
that, and then undoing that change and redeploying with the 
"corrected" Gemfile/Gemfile.lock.


Has anyone else seen this behavior?

Thanks,
Wes
--
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.

--
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: Bogus bundle not complete messages

[Steve Smith]

Wes, do you have bundle without set? I had this error and the Heroku guys 
determined I should have used "development:test" and not "development test" 
could be the same issue?

Steve

On 29 Nov 2010, at 17:43, Wes Gamble  wrote:

> Occasionally in the last week, I keep getting messages about bundler not 
> finding some gems for my app., even though on these deploys, I haven't 
> changed my Gemfile or Gemfile.lock files.
> 
> The only way I seem to be able to fix it is to deploy a changed 
> Gemfile/Gemfile.lock (commenting out some random gem), deploying that, and 
> then undoing that change and redeploying with the "corrected" 
> Gemfile/Gemfile.lock.
> 
> Has anyone else seen this behavior?
> 
> Thanks,
> Wes
> -- 
> 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.

Bogus bundle not complete messages

[Wes Gamble]

Occasionally in the last week, I keep getting messages about bundler not 
finding some gems for my app., even though on these deploys, I haven't 
changed my Gemfile or Gemfile.lock files.


The only way I seem to be able to fix it is to deploy a changed 
Gemfile/Gemfile.lock (commenting out some random gem), deploying that, 
and then undoing that change and redeploying with the "corrected" 
Gemfile/Gemfile.lock.


Has anyone else seen this behavior?

Thanks,
Wes

--
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: Automating pgbackups

[Neil]

We've many apps on Heroku (read about 30) of which roughly ten are
production apps.

Therefore I've been looking at creating a little management app to
backup all the production apps on an hourly cron (and thus only pay
for cron once).  Question is, using the above rake tasks, what URL
should be used for a specific db?  Currently I'm using
ENV["SHARED_DATABASE_URL"] but I keep getting back that it's a bad
URI.

Does anyone have any pointers on this?  Hopefully if I get it working
I can open it up to folks

N

On Nov 19, 12:22 am, "Andrew C."  wrote:
> I've got a lot on my plate right now, but I'm not opposed to getting
> it into a usable state for other people once I get some spare time.
>
> On Nov 17, 2:10 am, Trevor Turk  wrote:
>
>
>
>
>
>
>
> > On Nov 16, 6:44 pm, "Andrew C."  wrote:
>
> > > I spin up an EC2 instance from my cron job.  The EC2 instance captures
> > > and downloads the backup to S3, then shuts itself down.  Works well so
> > > far.  Obviously, it's not free, but it's freaking cheap.
>
> > Any chance of open-sourcing some of that code? It's an interesting
> > idea. I'm still hoping there's an easier way, but this is certainly an
> > idea!
>
> > - Trevor

-- 
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.