Use yarl instead of grpcio in tests to avoid dependabot warnings #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background is that there is quite often known vulnerabilities for grpcio. We do not want to disable dependabot for this repository but on the other hand we do not want to spend time updating testcases, and dependabot has as of today no good mechanism to exclude directories. So then the question comes - could we use some other (more stable) package in the test cases to avoid future dependabot issues.
Also fixing some NOTICE file regressions on main