-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
LGTM alerts . #19077
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
Comments
hey, can i have this issue? |
Posting for reference the LGTM alerts: https://lgtm.com/projects/g/numpy/numpy/alerts/?mode=list I can take a look at the errors in arithmetic.h, which were added during our SIMD division change. |
@ganesh-k13 so i just need to fix the errors/warnings shown in the lgtm page ? |
Welcome. Please read the developer's workflow guide, especially around commit messages. Some of those errors/warnings will be difficult to fix since LGTM's ideas may not agree with ours. Try to group the fixes in some logical way: for instance, all the unused imports in one PR and in another PR all the integer overflow warnings. |
@mattip thanks. I've removed all of the unused imports only to find out it breaks the code fsr(hoping you'll tell why), but reading the exceptions and restoring the removed imports solved the issue. I can now build and run tests. The test results are same after removing unused imports as linked below. Do you want me to go ahead and do a pr ? |
@mattip do you want me to go ahead and do a pr man? or is there I should be doing first ? Thanks |
A cleanup PR would be welcome. Please be sure it only changes the lines you intend to change: sometimes coding tools can "clean up" formatting which makes PRs harder to review. |
@charris I've raised a new PR for unused variables. Can anyone check and give a suitable review? |
Usually review requires a few days. If after a week no-one has reviewed, feel free to ping (without names) in the PR with a "please review" comment. |
thanks, noted. |
Relates to ticket numpy#19077
Keeping this open for a while. |
Hello, can I contribute to this particular issue? |
https://lgtm.com/projects/g/numpy/numpy/alerts/?mode=list |
What would you fix? I am not seeing any LGTM alerts for |
It is listed under error |
That file is a generated file. The correct fix will be to tell lgtm (and probably gitattributes) to ignore that file. You could fix it upstream in versioneer too if you wanted. |
Hello, I am new to open source contribution, Can I fix the "Suspicious unused loop iteration variable" issue from [https://lgtm.com/projects/g/numpy/numpy/alerts/?mode=list] ??? |
We do not assign work. Anyone can submit a PR. Please mark that as |
Can I work on this? I'm new so can someone guide me? |
@charris can I contribute in this? I am a starter in open source contributions and therefore may require guidance |
Is the issue fixed? Otherwise I would take up the issue. |
I would want to take this issue up if it is still open |
@priorigratia Go ahead, but keep in mind that some of the remaining issues are subtle and harder than they look. |
Let Me Do this issue |
We do not assign work. Anyone can submit a PR. Please mark that as related to #19077 so others will see that you are working on it. |
Hi, I would like to work on the following issue. regexp miss-match. line 227. But I'm confused about what we're trying to match? Can you please provide test cases so that I can work on it. This is my first project so kindly help me. |
This code path is exercised by https://github.com/numpy/numpy/blob/main/numpy/linalg/lapack_lite/README.rst |
I've gone through it.. and now I'm a bit confused. will you please guide me through it? There are two types of subroutines in f2c_*.c, extern subroutines and local subroutines, and I am a bit confused whether we're trying to match both or only local subroutines.
|
Hi everyone, I'd like to contribute to this issue. I am a beginner in contributing to open source projects. Could someone help and guide me on how to start a contribution? |
@acse-srm3018 If you're still interested in working on this issue (or others), here's a summary for first-time contributors to numpy! |
Hello I have read the first-time contributors docs and would like to contribute. What exactly do I do with the issues, I am having a little trouble following. |
The above link has LGTM errors and alerts, this issue is all about fixing them. Visit the link, you will understand it. |
I'm going to close this as we are disabling LGTM. Continuing work to fix the already found problems is of course welcome. |
I notice that there are still a fair number LGTM alerts, many of which look pretty simple. I wonder if they would be a good source of issues for the next NumPy sprint?
The text was updated successfully, but these errors were encountered: