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

Fix "panic: runtime error: invalid memory address or nil pointer dereference" #261

Closed
wants to merge 2 commits into from

Conversation

bartoszpop
Copy link
Contributor

@bartoszpop bartoszpop commented May 1, 2024

Fix bazel run gazelle failing on Windows with

panic: runtime error: invalid memory address or nil pointer dereference

because of the incorrect path separator when accessing the Configs map (#260).

@bartoszpop bartoszpop changed the title Fix "panic: runtime error: invalid memory address or nil pointer dereference Fix "panic: runtime error: invalid memory address or nil pointer dereference" May 1, 2024
illicitonion added a commit to illicitonion/rules_jvm that referenced this pull request May 2, 2024
We're using this to find the parent of a package, not a filesystem path,
and packages always use `/`.

Fixes bazel-contrib#260
Closes bazel-contrib#261
@illicitonion
Copy link
Collaborator

Thanks for your fix! (And all your fixes - I've been working today on getting our CI running on Windows so we can catch this kind of problem in the future and make sure things work and keep working).

I think #264 is a slightly more targeted fix - does that look good to you?

@bartoszpop
Copy link
Contributor Author

Thanks for your fix! (And all your fixes - I've been working today on getting our CI running on Windows so we can catch this kind of problem in the future and make sure things work and keep working).

I think #264 is a slightly more targeted fix - does that look good to you?

@illicitonion LGTM, I checked on my local and your fix also works.

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

Successfully merging this pull request may close these issues.

2 participants