-
Notifications
You must be signed in to change notification settings - Fork 100
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
SQS :SendMessage results in a :cognitect.anomalies/fault #110
Comments
Ah. This seems related to #86. For the record, I'm running this on Lambda with the java-1.8.0-openjdk runtime. |
Actually, after digging around for a few hours, I suspect this has something to do with how our uberjar packager is handling transitive dependencies. Closing for now. |
It makes sense that it's a transitive dep issue. Please do report back here if you find a workaround so other ppl can take advantage of it. Thanks! |
Turns out this is a known bug in luchiniatwork/cambada: luchiniatwork/cambada#16 I've created a fork that meets our needs for the moment: https://github.com/jdhollis/cambada That said, I'll be keeping an eye on (and possibly contributing to) @luchiniatwork's master version. |
Thanks for the sleuthing and follow up @jdhollis. |
So I'm running even more up to date versions of everything but I'm still getting this issue
|
@gozes Are you running via an uberjar? If so, how are you packaging it up? |
@jdhollis so I am building an uberjar just by running lein uberjar in my CI pipeline. on my project.clj I have
so nothing special |
I would check Lein's issues then. I haven't used Lein in a while, but the issue I was running into was related to transitive dependencies. |
Running into a strange issue with the SQS library—
The messages are being successfully sent, but I’m getting a
:cognitect.anomalies/fault
(which is throwing off my error handling):My invocation is pretty basic (and more or less the same as I’m using everywhere). And since the messages are getting sent to the proper queue, I'm guessing that's not the issue.
I'm also running the latest version of everything:
Any ideas?
The text was updated successfully, but these errors were encountered: