Skip to content

librariesindex: Fix nil pointer. Refs #1176 #1177

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

Closed
wants to merge 3 commits into from
Closed

Conversation

r10r
Copy link
Contributor

@r10r r10r commented Feb 7, 2021

Let the library index return the latest known version,
if a library without a version is updated.

Signed-off-by: Ruben Jenster [email protected]

@CLAassistant
Copy link

CLAassistant commented Feb 7, 2021

CLA assistant check
All committers have signed the CLA.

Let the library index return the latest known version,
if a library without a version is found.

Signed-off-by: Ruben Jenster <[email protected]>
Copy link
Contributor

@silvanocerza silvanocerza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A small change requested. Would be great if you could add an integration test to reproduce the issue so we won't have regressions in the future.

@r10r
Copy link
Contributor Author

r10r commented Feb 17, 2021

A small change requested. Would be great if you could add an integration test to reproduce the issue so we won't have regressions in the future.

Sure I can - but it may take some time.
Where should the integration test go to? (Btw. have you seen the test I've added to index_test.go ?)

@silvanocerza
Copy link
Contributor

Sure I can - but it may take some time.
Where should the integration test go to?

Integration tests go in the test folder in the project root, they're written in Python and call the CLI directly. There's more information in the official docs. I'd probably add tests for any command that is affected by this change, lib install and lib list for sure, I'd have to verify if there are others.
If you want I can take care of it, let me know.

(Btw. have you seen the test I've added to index_test.go ?)

Yep, that's fine for unit tests.

@r10r
Copy link
Contributor Author

r10r commented Feb 17, 2021

If you want I can take care of it, let me know.

Sorry, but I'm not used to Python, It'll take more time for you to review my code than to write it yourself.
Anyway it's good to know for the future. Thanks!

@silvanocerza
Copy link
Contributor

silvanocerza commented Feb 17, 2021

Sorry, but I'm not used to Python, It'll take more time for you to review my code than to write it yourself.
Anyway it's good to know for the future. Thanks!

No worries, I'll take care of it as soon as I can, I'll notify you when closing the issue.
Anyway thanks for reporting it and providing a fix. Really appreciated. :)

@silvanocerza
Copy link
Contributor

@r10r I had to cherry pick your commits to a separate branch and create a new PR #1189. It would have been problematic to merge this since it points to your fork's master branch and didn't want to put you through the hassle of creating a new PR.

You'll result as contributor anyway so don't worry about that.

The new PR is #1189, I'll close this one as soon as that is merged in.

@silvanocerza
Copy link
Contributor

Closed since #1189 has been merged.

@r10r
Copy link
Contributor Author

r10r commented Feb 18, 2021

I'm really happy to see this merged. Thanks for your support!

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.

3 participants