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

propagate KeyNotFound on first server to client #307

Merged
merged 1 commit into from
Jul 16, 2021

Conversation

slawekjaranowski
Copy link
Member

When we have key not found status from first server and next server has connection problem we should propagate to client key not found instead of last exception.

@slawekjaranowski
Copy link
Member Author

workaround for #305

@slawekjaranowski slawekjaranowski added the bug Something isn't working. label Jul 15, 2021
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@slawekjaranowski slawekjaranowski merged commit ab9eb8d into master Jul 16, 2021
@slawekjaranowski slawekjaranowski deleted the key-not-found-fix branch July 16, 2021 06:32
pzygielo pushed a commit to pzygielo/pgpverify-maven-plugin that referenced this pull request May 31, 2024
Several key aspects are broken in provided and trusted checksum feature of resolver:
* trusted checksum post processor: the checksum algorithm is not prefixed (as documented)
* the trusted to provided adapter is defunct without MRM being configured
* the existing ProvidedChecksumsSource interface is broken, needs to be replaced

---

https://issues.apache.org/jira/browse/MRESOLVER-375
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Development

Successfully merging this pull request may close these issues.

2 participants