-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Fixed Improper Method Call: Replaced mktemp
#33874
base: master
Are you sure you want to change the base?
Fixed Improper Method Call: Replaced mktemp
#33874
Conversation
Thanks for the pull request, @fazledyn-or! This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.
|
Hi @fazledyn-or, thank you for this contribution! Please let me know if you have any questions regarding completing a CLA form. Thanks! |
Yeah, thanks for asking. Actually, I do need some help. What do I put in these two fields? |
@fazledyn-or I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard? @fazledyn-or in contributions field you can just put "N/A." Are you contributing on bahalf of OpenRefactory-Inc or on your own behalf? |
0d4f25d
to
cf64849
Compare
Signed-off-by: fazledyn-or <[email protected]>
cf64849
to
560dc44
Compare
I've updated my commit message. Please have a look |
Hi @fazledyn-or! Just checking to see if you plan to pursue this pull request? If so, it looks like you'll need to re-run the checks. Thanks! |
Yes, I do. My first commit message had a lint failure, so I updated the commit message and pushed. Looks like the workflows need to be re-run by one of the maintainers. Without re-running them, I can't say whether I need to update something or not. |
@fazledyn-or great! I'll mark this for our team to re-run the checks. |
Your branch is behind the base. I've pulled in changes from master as a merge commit which will update your branch and cause the tests to be re-run. |
Your branch is behind the base. I've pulled in changes from master as a merge commit which will update your branch and cause the tests to be re-run. |
Hi @fazledyn-or! Is this still in-progress? |
Yes. I don't think I have anything more to add. I've already made changes
that were required, filled and submitted the form.
If you need me to do anything to get it merged to the source code,
please let me know.
I'll be glad to do so.
…On Wed, Jul 31, 2024, 1:28 AM Michelle Philbrick ***@***.***> wrote:
Your branch is behind the base. I've pulled in changes from master as a
merge commit which will update your branch and cause the tests to be re-run.
Hi @fazledyn-or <https://github.com/fazledyn-or>! Is this still
in-progress?
—
Reply to this email directly, view it on GitHub
<#33874 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBB3LA5F2YJPXDBVOXK6AYLZO7SMLAVCNFSM6AAAAABAFZZQQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJZGA2TMOBSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@fazledyn-or - It looks like a few more tests need to be run. Please let me know if you have any questions! |
Yes, you're correct.
One of the maintainers should run the tests. I don't have the permissions
to do so. I've already mentioned it in one of my old comments.
…On Thu, Aug 1, 2024, 2:21 AM Michelle Philbrick ***@***.***> wrote:
Yes. I don't think I have anything more to add. I've already made changes
that were required, filled and submitted the form. If you need me to do
anything to get it merged to the source code, please let me know. I'll be
glad to do so.
… <#m_7199204017778239836_>
@fazledyn-or <https://github.com/fazledyn-or> - It looks like a few more
tests need to be run. Please let me know if you have any questions!
—
Reply to this email directly, view it on GitHub
<#33874 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBB3LA2THRKAOXSCJNVDWKDZPFBLBAVCNFSM6AAAAABAFZZQQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRGM4DENBVGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have requested a change since mkstemp
has a bug with file descriptors.
@@ -55,7 +55,8 @@ def handle(self, *args, **options): | |||
pipe_results = False | |||
|
|||
if filename is None: | |||
filename = mktemp() | |||
fd, filename = mkstemp() | |||
os.close(fd) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fazledyn-or in addition to this we need to add os.unlink(filename), this is one of the bugs pointed out in python/cpython#86996.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
Description
While triaging your project, our bug fixing tool generated the following message(s)-
Resources Related to
mktemp
Changes
mktemp()
method withmkstemp()
Previously Found & Fixed
CLA Requirements
This section is only relevant if your project requires contributors to sign a Contributor License Agreement (CLA) for external contributions.
All contributed commits are already automatically signed off.
Sponsorship and Support
This work is done by the security researchers from OpenRefactory and is supported by the Open Source Security Foundation (OpenSSF): Project Alpha-Omega. Alpha-Omega is a project partnering with open source software project maintainers to systematically find new, as-yet-undiscovered vulnerabilities in open source code - and get them fixed – to improve global software supply chain security.
The bug is found by running the Intelligent Code Repair (iCR) tool by OpenRefactory and then manually triaging the results.