You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The remote, hosted instance of the function app on Azure has already triggered this function for a specific uploaded blob. When I then start the local, dev server, it then again gets triggered as though it has never seen it when it was already processed by the live function app.
The expected function is that it does not get triggered since it was already processed by the live function app.
Actual behavior
Provide a description of the actual behavior observed.
Triggers a function for each blob that was uploaded and processed by the live function, that the local server did not process. This is also true of when the live server and local server are both running: the trigger will run twice (which is to be expected, but not the first part of ones that are already processed when the dev server is not running).
Known workarounds
Provide a description of any known workarounds.
@bp.blob_trigger(arg_name='audio',path='{x}.wav',connection='AzureWebJobsStorage',)deftrigger(audio: func.InputStream):
# for starting in dev mode, skip if already while dev server was offlineifcheck_if_processed_dev(audio.name):
returnprint(audio.name)
check_if_processed_dev will check the database to see if that file had already been processed in the functionality of my backend.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Uh oh!
There was an error while loading. Please reload this page.
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
func start
Expected behavior
Provide a description of the expected behavior.
The remote, hosted instance of the function app on Azure has already triggered this function for a specific uploaded blob. When I then start the local, dev server, it then again gets triggered as though it has never seen it when it was already processed by the live function app.
The expected function is that it does not get triggered since it was already processed by the live function app.
Actual behavior
Provide a description of the actual behavior observed.
Triggers a function for each blob that was uploaded and processed by the live function, that the local server did not process. This is also true of when the live server and local server are both running: the trigger will run twice (which is to be expected, but not the first part of ones that are already processed when the dev server is not running).
Known workarounds
Provide a description of any known workarounds.
check_if_processed_dev will check the database to see if that file had already been processed in the functionality of my backend.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Related information
Provide any related information
n/a
The text was updated successfully, but these errors were encountered: