Closed ChrisLane closed 2 years ago
I can't reproduce this. Can you please post the complete classpath? lein classpath
if it's a lein project, or clj -Spath
for a tools.deps project.
I'm closing this since I can't reproduce it an haven't heard back. @ChrisLane, I'll reopen this if you can help me reproduce the behavior. Thanks!
Hi again! I can't be 100% sure without the classpath you see, but what the error suggests is that you have two incompatible versions of jetty on your classpath. This likelihood is reinforced by that fact that specifying [org.eclipse.jetty/jetty-io "9.4.46.v20220331"]
resolves the issue.
A lot of the time, build tools like maven, leiningen, and tools.deps make choices for you in the face of transitive dependency conflicts and they end up working out, but sometimes they don't, at which point it becomes your responsibility to resolve it with explicit requires and/or exclusions. I'll add something to the README about this.
I just ran into this and it absolutely drove me up the wall, as I have two projects, one a web app and the other an ingest script, that both have 100% the same AWS setup. The ingest script works, the web app doesn't. It took me an hour to figure out that it was a dependency issue, the whole of which I thought I must be hallucinating, because if I just jack in to the data ingest project, the same call succeeds, and when I try it on the web app, it fails with a cryptic error.
Thank you for your interest in helping to improve Cognitect's aws-api!
Dependencies
Description with failing test case
I'm trying to encrypt a string with a particular KMS key using the following code. I expect to get a success response with the encrypted value but instead I get an exception.
The problem goes away if I add
[org.eclipse.jetty/jetty-io "9.4.46.v20220331"]
to my dependencies, however, this is not a step that I was expecting to need to take.Stack traces