hallvictoria

Hey @uberger thanks for your patience. I looked into this issue and here are some things that I found: - This error only occurs for Queue messages with content in...

Transferring to the Queue extension repo to see if they can look into this -- adding / setting a `time_to_live` property in the Queue Message object. In the meantime, using...

This can be addressed by using SDK type bindings for blob. The BlobTrigger can define a client type, and the client type can be used to access the blob name...

Hi @syberen, thanks for the catch. `start_from_beginning` should be `bool`, and `start_from_time` should be `str`. I've linked a PR with these changes. However, since we're currently in a release freeze...

Hi @ajstewart, this is expected behavior. With the blob input binding, the entire file is passed from the host to the worker through grpc messaging and is loaded into memory....

Yes, unfortunately that's a known limitation for blob bindings as of right now. The main difference between using a blob input binding and the SDK is how the file is...

I don't think this is new, but yes it's known. We'll be introducing a feature that addresses this soon! Stay tuned :)

Moved from https://github.com/Azure/azure-functions-python-worker/issues/1614: I would like to do the following: Azure Functions + fastAPI + v2 Python model + Azure Static Web App For static webapp to deploy along with...

Hi @io-canopy, thanks for raising this. With our current architecture, when an exception is raised, we catch it and propagate forward the exception name and exception content. The top level...

Sure thing. Majority of the formatting is done in the [`_serialize_exception`](https://github.com/Azure/azure-functions-python-worker/blob/dc8d56434b569bd78766a0a7dd8f5a09c5619308/azure_functions_worker/dispatcher.py#L273) and [`marshall_exception_trace`](https://github.com/Azure/azure-functions-python-worker/blob/dc8d56434b569bd78766a0a7dd8f5a09c5619308/azure_functions_worker/utils/tracing.py#L19) methods -- specifically, we use `traceback.extract_tb`. The execution flow looks like this: [invocation request](https://github.com/Azure/azure-functions-python-worker/blob/dc8d56434b569bd78766a0a7dd8f5a09c5619308/azure_functions_worker/dispatcher.py#L590) -> [exception occurs](https://github.com/Azure/azure-functions-python-worker/blob/dc8d56434b569bd78766a0a7dd8f5a09c5619308/azure_functions_worker/dispatcher.py#L726)...