Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove unused inputs and outputs fields for AppBase #3485

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

arhag23
Copy link
Contributor

@arhag23 arhag23 commented Jun 12, 2024

Description

Testing to see if AppBase needs outputs and inputs fields or the lines changed are necessary.

Changed Behaviour

Removed the last 2 lines of AppBase.__init__ which set AppBase.inputs and AppBase.outputs to default values if they exist.

Type of change

  • Code maintenance/cleanup

@arhag23 arhag23 marked this pull request as draft June 12, 2024 18:30
@benclifford benclifford changed the title remove extra inputs and outputs field for AppBase Remove unused inputs and outputs field for AppBase Jun 12, 2024
@benclifford benclifford changed the title Remove unused inputs and outputs field for AppBase Remove unused inputs and outputs fields for AppBase Jun 12, 2024
@benclifford benclifford marked this pull request as ready for review June 12, 2024 18:59
Copy link
Collaborator

@benclifford benclifford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also looked through the current code, and also git history, and I think these are two fields that were introduced back at the very start of parsl in 2017 when the task and decorator model was still being unexplored - as far as I can tell, they've been unused for a long time, but not causing anyone problems.

@benclifford benclifford merged commit 8b45556 into Parsl:master Jun 12, 2024
7 checks passed
benclifford pushed a commit that referenced this pull request Jul 2, 2024
…ords, and like bash_app (#3489)

In a previous PR (#3485), some fields where the default values of outputs and inputs for AppBase were removed. These fields were not being used in any way. However, like the other parsl reserved parameters, the defaults should have been stored in the AppBase.kwargs dict which is used to ensure that the default values of these special reserved parameters are in invocation_kwargs which is sent to the dataflow kernel and used to resolve the corresponding special behaviors. The correct behavior was only observed in BashApp since it does additional checking to store all default args (even the non-reserved ones) to invocation_kwargs. Now it should be consistent for both types of apps.

Changed Behaviour:
PythonApp will now correctly resolve default arguments for the inputs and outputs special parameters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants