AsyncCursor.callproc() fails due to NewRelic AsyncCursorWrapper

[lotfiGipsyKing]

Description

In our FastAPI application using oracledb library in async mode, calls to AsyncCursor.callproc() fails only when using the newrelic-admin run-program to run my app:

The line that raise the error:

await cursor.callproc(name=sql, parameters=params)

And the error i'am getting:

callproc() got an unexpected keyword argument 'name'

After investigation the root cause is :

• NewRelic wraps the async Oracle cursor with AsyncCursorWrapper to instrument DB calls.

• The wrapper changes the signature, replacing name with procname and altering expected arguments:

  • Link to oracle-db doc
  • Link to the newrelic wrapper

• This causes keyword argument errors when calling callproc as usual.

Expected Behavior

The newrelic wrapper should keep the same function signature as oracledb.AsyncCursor.

Environment

python = "~3.13"
fastapi = "~0.125"
oracledb = "^3.4.1"
newrelic = "~11.2"

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-518045

[TimPansino]

Thank you for the report, this will be fixed in the next release of the agent.

Couple additional notes here:

This issue was a direct result of python-oracledb not conforming to the DBAPI 2.0 specification for callproc(). They've not only changed the name of the first parameter, but added a 3rd parameter to the function signature as well. I've added custom wrappers for callproc() here to fix the issue.

As a result of various libraries not conforming to the same argument names as the DBAPI 2.0 specification, it's generally recommended to pass arguments as positional arguments rather than keyword arguments for DBAPI 2.0 Connection and Cursor classes. That might be worthwhile to do in the future to avoid conflicts if they (or other database driver libraries) decide to rename any arguments.

Regardless, if you find another issue like this in the future feel free to report it and we'll continue to adjust argument names as needed to match library signatures.