The Wayback Machine - https://web.archive.org/web/20210607222416/https://github.com/numpy/numpy/issues/19077
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

LGTM alerts . #19077

Open
charris opened this issue May 23, 2021 · 10 comments · May be fixed by #19102
Open

LGTM alerts . #19077

charris opened this issue May 23, 2021 · 10 comments · May be fixed by #19102

Comments

@charris
Copy link
Member

@charris charris commented May 23, 2021

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?

@default-303
Copy link
Contributor

@default-303 default-303 commented May 24, 2021

hey, can i have this issue?
I'm quite new to this so I might need some guidance

@ganesh-k13
Copy link
Contributor

@ganesh-k13 ganesh-k13 commented May 24, 2021

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.

@default-303
Copy link
Contributor

@default-303 default-303 commented May 24, 2021

@ganesh-k13 so i just need to fix the errors/warnings shown in the lgtm page ?

@mattip
Copy link
Member

@mattip mattip commented May 24, 2021

I'm quite new to this so I might need some guidance

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.

@default-303
Copy link
Contributor

@default-303 default-303 commented May 24, 2021

@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've restored the following imports -

I can now build and run tests. The test results are same after removing unused imports as linked below.

Before fixing imports -
before_fixing_unused_imports

After fixing imports -
after_fixing_unused_imports

Do you want me to go ahead and do a pr ?

@default-303
Copy link
Contributor

@default-303 default-303 commented May 25, 2021

@mattip do you want me to go ahead and do a pr man? or is there I should be doing first ?

Thanks

@mattip
Copy link
Member

@mattip mattip commented May 25, 2021

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.

@default-303
Copy link
Contributor

@default-303 default-303 commented May 26, 2021

@charris I've raised a new PR for unused variables. Can anyone check and give a suitable review?

@mattip
Copy link
Member

@mattip mattip commented May 26, 2021

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.

@default-303
Copy link
Contributor

@default-303 default-303 commented May 26, 2021

thanks, noted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants