Azure / Azure/azure-functions-host

[BUG] ServiceBus body containing ExpiresAtUtc field is not parsed properly

Open
#7,119 7 comments 0 reactions 0 assignees View on GitHub
Needs: Attention :wave:
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

### Investigative information
###### Please provide the following:

- Related CRI: 219200398
- Timestamp: 2020-12-22 22:58:33
- Function App name: prod-azureing-governor
- Function name(s) (as appropriate):
- Core Tools version:

### Repro steps
###### Provide the steps required to reproduce the problem:
1. Create a function app with service bus trigger.
2. Send a message to the ServiceBus namespace, with ExpiresAtUtc in the body which contains an invalid format.
3. The function's metadata ExpiresAtUtc field will be overwritten by ServiceBus body ['ExpiresAtUtc'].

### Expected behavior
###### Provide a description of the expected behavior.
The function app should not fail since we should not parse of the ServiceBus message.body

### Actual behavior
###### Provide a description of the actual behavior observed.
ValueError: time data '12/18/2020 20:57:23' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'

### Known workarounds
###### Provide a description of any known workarounds.

### 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

* Links to source
* Bindings used

cc: @gzuber @vrdmr @anirudhgarg @stefanushinardi

Contributor guide

Open the contributing guide

Research direction

Start with the Service Bus trigger behavior described in the reproduction steps and trace how message bodies are handled alongside function metadata. Reproduce the invalid ExpiresAtUtc format, then verify that the body cannot overwrite the metadata value or cause the reported ValueError.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.