Skip to content

Fixes #17323: Associate job with script object when executed using runscript command #17343

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 3, 2024
Merged

Fixes #17323: Associate job with script object when executed using runscript command #17343

merged 1 commit into from
Sep 3, 2024

Conversation

jeremystretch
Copy link
Member

Fixes: #17323

  • Ensure the Job is associated with the Script object rather than the ScriptModule
  • Pass the script instance to _run_script() as an argument

@jeremystretch jeremystretch merged commit 814b699 into develop Sep 3, 2024
6 checks passed
@jeremystretch jeremystretch deleted the 17323-runscript-jobs branch September 3, 2024 13:20
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@bctiemann bctiemann bctiemann approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Scripts ran using manage.py runscript don't show up in the script's history
2 participants
@jeremystretch @bctiemann