[FR] Support for scheduled functions in emulator

[Elyx0]

[REQUIRED] Environment info

firebase-tools: 7.15.0 & 7.15.1

Platform: macOS 18.7.0 Darwin Kernel Version 18.7.0:

[REQUIRED] Test case

export const pubsubScheduled = functions.pubsub
  .schedule('every 1 minutes')
  .onRun(context => {
    console.log('Resource', JSON.stringify(context.resource));
    return true;
  });

[REQUIRED] Steps to reproduce

firebase emulators firebase emulators:start
✔ functions[pubsubScheduled]: pubsub function initialized.

[REQUIRED] Expected behavior

Logging every 1 minute in the console

[REQUIRED] Actual behavior

No output

Links:
b6fa88a

4dc64da

#1543 (comment)

[samtstern]

@Elyx0 I think we maybe misled with how we represented #2011

It lets those functions be loaded into the emulator but doesn't actually trigger them on a schedule. Instead you'd have to manually trigger them using a Pub/Sub message.

This was mostly meant for use within functions:shell but I can definitely see how this is confusing and we need to clarify it.

[Elyx0]

Thanks for clarifying @samtstern I'll wrap them in a setInterval in the global scope if it detects the emulator

[spicemix]

I have the five lines of SetInterval code running fine to get around the absence of this, but it clutters up my index file with redundant .onPublish and .onRun calls to the same code, and the workaround might up the cold start time a bit for the non-PubSub functions, so it would be great if this feature could get built thanks!

[weixifan]

@spicemix Thanks for the suggestion! To keep the issues focussed, could you please file a separate feature request for this? We are unable to promise any timeline for this, but if others also have this request, adding a +1 on that new feature request can help us prioritize adding this to the roadmap.

[weixifan]

For internal reference: the feature request is b/188590642.

[spicemix]

I would just re-open this until it's actually addressed, I only explained some motivation for fixing this issue.

[weixifan]

@spicemix Sure, my thought was that it might be easier for users to discover the FR and +1 on a new FR rather than having to read through this bug report and realize there is a related FR. I'll change the title to make this clear.