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

Recursive analysis not working on Windows 10 #2

Closed
2 tasks done
ericcornelissen opened this issue Nov 3, 2020 · 2 comments · Fixed by #3
Closed
2 tasks done

Recursive analysis not working on Windows 10 #2

ericcornelissen opened this issue Nov 3, 2020 · 2 comments · Fixed by #3
Labels
bug Something isn't working

Comments

@ericcornelissen
Copy link
Owner

Bug Report

This is a bug report for:

  • goparamcount
  • goreturncount

More specifically:

  • Tool version: v1.0.1 (for both)
  • Operating system: Windows 10

Description

The "./..." notation does not seem to work on Windows 10 (and likely other Windows versions)

Actual Behaviour

When using the "./..." notation to recursively inspect a directory on Windows 10 (and possibly other versions) the directory will be inspected non-recursively.

Expected Behaviour

When using the "./..." notation to recursively inspect a directory it should ALWAYS inspect the directory recursively.

Working Example

In gofunchecks tools it can be reproduced on a Windows 10 machine by simply running [TOOL] -max 0 ./... in the gofunchecks directory and you will observe that no errors are reported.

Log Output

n/a

@ericcornelissen ericcornelissen added the bug Something isn't working label Nov 3, 2020
@ericcornelissen
Copy link
Owner Author

This seems to be related to an upstream issue in the core Go packages that causes the filepath.Abs() call to remove it from the provided path (on Windows but not on Unix). I filed a report in the official Go repository for this: golang/go#42362. In the meantime I will try to get a temporary fix out for this as soon as possible.

@ericcornelissen
Copy link
Owner Author

In the meantime I will try to get a temporary fix out for this as soon as possible.

I was able to find a solution that isn't necessarily temporary, the fix in #3 can stay even if golang/go#42362 is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant