Skip to content

When connect fails, Grizzly provider doesn't notify with the proper exception (1.9 only) #1166

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

Closed
slandelle opened this issue May 23, 2016 · 7 comments
Assignees
Milestone

Comments

@slandelle
Copy link
Contributor

See discussion and possible fix #1134.
Waiting for fix to be validated by @oleksiys.

@gsfernandes
Copy link

Hi @oleksiys, did you have a chance to look at this issue?
I would need this fixed along with #1152 in the new 1.9.x release of AHC. Let me know if I could help you somehow, I have tested the fix provided in #1134 and it does the fix for it.
Thank you!

@elrodro83
Copy link

Is there any ETA for this issue? @oleksiys

@afelisatti
Copy link

Any update on this, @oleksiys ? The 1.9.39 release seems to be blocked by this issue but there's a proposed fix available.
Thanks

@afelisatti
Copy link

Anyone else from the Grizzly team that could take a look at this? @rlubke

@rlubke rlubke self-assigned this Jul 11, 2016
@rlubke
Copy link
Contributor

rlubke commented Jul 11, 2016

Yep, will take a look.

rlubke added a commit that referenced this issue Jul 12, 2016
@rlubke rlubke closed this as completed Jul 12, 2016
@slandelle slandelle added this to the 1.9.39 milestone Jul 27, 2016
@slandelle
Copy link
Contributor Author

@rlubke Welcome back!

@rlubke
Copy link
Contributor

rlubke commented Jul 27, 2016

@slandelle Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants