Avoid using inspect.getfullargspec that doesn't work properly for a wrapped function

[harupy]

Signed-off-by: harupy hkawamura0130@gmail.com

What changes are proposed in this pull request?

In dmlc/xgboost#6751, xgboost.train is wrapped by _deprecate_positional_args to deprecate the positional arguments. This change broke xgboost autologging because inspect.getfullargspec doesn't work properly for a wrapped function:

https://github.com/mlflow/mlflow/runs/4033126360?check_suite_focus=true#step:11:8877

        all_arg_names = inspect.getfullargspec(original)[0]  # `original` is `xgboost.train`
                              # ^^^^^^^^^^^^^^
                              # doesn't work for a wrapped function
        num_pos_args = len(args)
    
        # adding a callback that records evaluation results.
        eval_results = []
>       callbacks_index = all_arg_names.index("callbacks")
E       ValueError: 'callbacks' is not in list

This PR fixes the issue by using inspect.signature.

How is this patch tested?

Existing tests

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

Interface

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

Language

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

Integrations

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

[harupy]

_get_arg_names here isn't used at all.

[harupy]

pylint doesn't seem to check import statements in a function.

[harupy]

@dbczumar Does the module name (arguments_utils) sound fine?

[dbczumar]

Yep!

[dbczumar]

LGTM! Thanks @harupy !