profile
viewpoint
George Pickett grp06 San Francisco https://hirightnow.co Co-founder @ Hi Right Now

grp06/meteorBoilerplate 2

A basic Meteor boilerplate project which includes packages I use on most projects. Set up with Semantic-UI CSS framework

grp06/snippetShare 2

A Chome Extension + A Meteor App

grp06/productivityTracker 1

A Meteor app that prompts you to fill out a questionnaire every 30 minutes as you're working

grp06/spotify-imgur 1

using spotify and imgur api's

grp06/alexa-app 0

A framework for Alexa (Amazon Echo) apps using Node.js

grp06/better-boilerplate 0

an improved version of my previous meteor boilerplate app

grp06/Browser-Stream 0

A Google Chrome extension that pushes multiple users' browser history to Firebase

grp06/Countdown-Chaos 0

you'll see

issue openedkelektiv/node-cron

Stopping a cron after one-time execution

If I set a job to run once, do I need to do any cleanup? Like, do I need to call job.stop() at any point?

Here's my job:


  const date = new Date()

  date.setMinutes(date.getMinutes() + 5)

  const job = new CronJob(date, function () {
      // do stuff here
  })

  job.start()```

The job will run 5 minutes from now, which is what I want. Just curious if I NEED to call `job.stop()` at some point in the future

created time in 2 months

issue commenthasura/graphql-engine

Scheduled event triggers are broken

Ok, I got it. Huge bummer for me then. I was architecting my app around precisely timed event triggers. Which, if that were possible, would allow me to avoid long set timeouts and really simplify the architecture.

Thanks for your clarification.

grp06

comment created time in 2 months

issue commenthasura/graphql-engine

Scheduled event triggers are broken

From the docs it seems like you can specify an exact time, like 6:34 pm and 35 seconds and the trigger should fire at that time. But it seems like if this interval fires every one minute and the interval is going 34 seconds past the top of the minute, this event trigger would be fired 59 seconds late?

grp06

comment created time in 2 months

issue commenthasura/graphql-engine

Scheduled event triggers are broken

Ok, maybe I am misunderstanding something, so I'm not sure if I can answer your question yet. With this "1-minute sleep interval" - does this mean that I cannot guarantee that an event trigger that I specify will fire at a specific second? Like, it might not fire until the next interval "check"?

If that's the case, it seems like it's only a time display issue

grp06

comment created time in 2 months

issue openedhasura/graphql-engine

Scheduled event triggers are broken

I don't quite understand how nobody has reported this yet, but scheduled event triggers do not work. (Or I am somehow missing something major here)

Step 1: I create a scheduled event trigger in the Hasura UI at 17:35:04 to be fired at 17:36:25 Step 2 I create a scheduled event trigger from my server at 17:35:27 to be fired at 17:36:27

Here's a screen shot of what I see in "pending triggers" Screen Shot 2020-09-03 at 5 35 54 PM

The first thing to notice: look at the created_at and the "scheduled_time" ... something is off already.

Then, at 17:37:01, my webhook endpoint is hit, first with the UI-created trigger: Screen Shot 2020-09-03 at 5 37 49 PM

And immediately after, with the programmatically-created trigger: Screen Shot 2020-09-03 at 5 38 20 PM

Notice how the created_at times are incorrect.

Further confirmation of the created_at times being incorrect on the "processed events" tab: Screen Shot 2020-09-03 at 5 53 27 PM

At first I thought it might have been something I'm doing wrong with Javascript dates, which are often tricky... So here, I set the schedule_at time to be 4 hours ahead. In this case, I set it to be: schedule_at 2020-09-04T01:56:34.530Z

And here's what the pending trigger looks like in the UI: Screen Shot 2020-09-03 at 5 59 00 PM

I hope this is enough to help you sort this out. I replicated this on v1.3.0 and 1.3.1

created time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha bd28fd57aa1b7b36e4be0faa5791370c074d1a83

take off redirect that didnt work

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha e60320dd44a9ba95acafb5eb73ac14fabeb242d4

trying out another redirect

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha e9156a1c5ff6109c40568b63b0105fe5bc687103

more redirect bs

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha 50f5ee5627137ca8de29462474904b29313e6a27

remove catch all on main redirect

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha c2e262da76b25932a189df8a020e21d38a1bdf5e

more testign with redirects

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha ab90383be85891bded42608707874afda966598a

add another redirect for upcoming -events

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha fda607d524559d2c22294a26370617d12c1ed54d

add netlify redirect for say.hrn

view details

push time in 2 months

push eventgrp06/hirightnow-entrepreneurs

George Pickett

commit sha 76e9b435928dc6df9dfcd43a5be63bd5438503bd

add netlify redirect

view details

push time in 2 months

more