-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Strange SSL error #47
Comments
This is another error seen in the same app's logs, also preventing error reporting. Not sure if this is related at all.
|
What's Crystal version you're using? |
That's weird, both stacktraces you've posted seems off by 1 call: ...
/usr/share/crystal/src/http/client.cr:499:5 in 'exec' # => `HTTP::Client#exec_internal_single`
/usr/share/crystal/src/http/client.cr:612:5 in 'send_event' # => `HTTP::Client#exec`
/home/app/myapp/lib/raven/src/raven/instance.cr:107:7 in 'capture' # => `Raven::Instance#send_event`
... |
Haven't been able to reproduce this issue with latest Crystal and Raven. |
I am also getting this issue when running from kemal with up.sh (two consecutive requests are shown, the initial request after a cold start, and a follow-up request):
Code is essentially just this: require "kemal"
ENV["HOME"] ||= `pwd`
ENV["PORT"] ||= "3000"
require "raven"
require "raven/integrations/kemal"
Raven.configure do |config|
config.async = true
config.dsn = "[REDACTED]"
end
add_handler Raven::Kemal::ExceptionHandler.new
get "/" do
raise "an error"
end Note: sometimes it explicitly says the SSL error you guys are having above. I'll see if I can get it to do it again. |
There, got it -- it's when the lambda first runs. Note that I had to set async to false for it to get this far.
|
Additional note: it works if I take the |
I'm using Raven 1.2.0. For some reason, it is failing to record a lot of errors. I found this in the log (after this point, Raven does not even attempt to send any more errors). I am not sure how to troubleshoot further, any advice would be appreciated.
The text was updated successfully, but these errors were encountered: