[Bug][pulsar-function]Pulsar Function processing time doesn't get properly recorded for asynchronous functions

[walkinggo]

Main Issue: #23705

Motivation

In the code, the asynchronous function is not handled properly. stats.processTimeEnd() is called immediately when the result is returned, but we should wait for the asynchronous task to complete before processing.

Modifications

Passed stats as a parameter into the function, and called stats.processTimeEnd() after the function call completes. Also, updated the corresponding test cases.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[lhotari]

This needs a different approach since there could be multiple messages in flight. The current duration calculation expects one-by-one messages handling.

[walkinggo]

This needs a different approach since there could be multiple messages in flight. The current duration calculation expects one-by-one messages handling.

Sorry, I'm not quite sure I understand your point. Are you referring to the potential issue when multiple messages are being processed, where they might share the same stats variable, leading to the modification of the same processTimeStart variable after calling processTimeStart in ComponentStatsManager?