No longer getting price updates

[flyize]

Is anyone else having this issue? Seems to exist for current entries as well as new ones.

[samyun]

What version is deployed? See #4

[flyize]

The version was current as of a couple hours ago. I see a new commit. Any chance that would help?

[samyun]

No, I created a new release 3.1.1 with the semaphores, but that shouldn’t affect this. Mind posting some of the logs? Look for sections that say “error” or “warning”

On May 7, 2018, 8:38 AM -0700, flyize notifications@github.com, wrote:

The version was current as of a couple hours ago. I see a new commit. Any chance that would help? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[flyize]

I assume its this then (using Heroku if it matters):

May 07 08:51:32 fly app/scheduler.2320: Error: Failed to launch chrome! May 07 08:51:32 fly app/scheduler.2320: /app/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory May 07 08:51:32 fly app/scheduler.2320: (node:20) UnhandledPromiseRejectionWarning: ReferenceError: browser is not defined May 07 08:51:32 fly app/scheduler.2320: (node:20) ReferenceError: browser is not defined

[samyun]

That would be it.

Is this a fresh deployment, or did you do the redeploy through Heroku?

On May 7, 2018, 9:06 AM -0700, flyize notifications@github.com, wrote:

I assume its this then (using Heroku if it matters): May 07 08:51:32 fly app/scheduler.2320: Error: Failed to launch chrome! May 07 08:51:32 fly app/scheduler.2320: /app/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory May 07 08:51:32 fly app/scheduler.2320: (node:20) UnhandledPromiseRejectionWarning: ReferenceError: browser is not defined May 07 08:51:32 fly app/scheduler.2320: (node:20) ReferenceError: browser is not defined — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[flyize]

Redeploy

[samyun]

Read through the readme. There’s a buildpack you need to add. One of the issues discussed this.

On May 7, 2018, 9:10 AM -0700, flyize notifications@github.com, wrote:

Redeploy — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[samyun]

4 actually.

On May 7, 2018, 9:10 AM -0700, flyize notifications@github.com, wrote:

Redeploy — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[flyize]

Okay, I've added the buildpack, that error is gone, and it seems to be pulling prices for new alerts. However, it still doesn't seem to be updating existing alerts. Do they have to be removed and readded?

[samyun]

Anything in the logs?

On May 7, 2018, 10:05 AM -0700, flyize notifications@github.com, wrote:

Okay, I've added the buildpack, that error is gone, and it seems to be pulling prices for new alerts. However, it still doesn't seem to be updating existing alerts. Do they have to be removed and readded? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[flyize]

Actually, no. According to the Heroku scheduler, the task should have run at :50. But this is the only thing I have in the logs around that time.

May 07 09:50:42 flysw app/heroku-redis: source=REDIS sample#active-connections=3 sample#load-avg-1m=0.11 sample#load-avg-5m=0.09 sample#load-avg-15m=0.04 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664184kB sample#memory-free=12564788kB sample#memory-cached=1633840kB sample#memory-redis=321056bytes sample#hit-rate=1 sample#evicted-keys=0

[samyun]

Looks like it didn’t run for some reason. It should check them the next round.

On May 7, 2018, 10:08 AM -0700, flyize notifications@github.com, wrote:

Actually, no. According to the Heroku scheduler, the task should have run at :50. But this is the only thing I have in the logs around that time. May 07 09:50:42 flysw app/heroku-redis: source=REDIS sample#active-connections=3 sample#load-avg-1m=0.11 sample#load-avg-5m=0.09 sample#load-avg-15m=0.04 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15664184kB sample#memory-free=12564788kB sample#memory-cached=1633840kB sample#memory-redis=321056bytes sample#hit-rate=1 sample#evicted-keys=0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[flyize]

As expected, you are correct. Thanks!