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.

Sign up for GitHub

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

Jump to bottom

Add retry logic for Slack http requests #94

Open
phoenix090 opened this issue Aug 31, 2022 · 1 comment · May be fixed by #135
Open

Add retry logic for Slack http requests #94

phoenix090 opened this issue Aug 31, 2022 · 1 comment · May be fixed by #135
Labels
help wanted Extra attention is needed

Comments

@phoenix090
Copy link

Hi

We are getting this error quite frequently when sending notifications to slack:

wait for process completion: connection: decode failed: read tcp 127.0.0.1:49532->127.0.0.1:45955: read: connection reset by peer

I understand connection reset by peer occurs when when a peer (the other end) unexpectedly closes the underlying connection. But i'm simply wondering if there is a way to configure retries when this occurs. Thanks in advance.
@arbourd
Copy link
Owner

arbourd commented Sep 20, 2022

Happy to accept a PR for this! I haven't used Concourse in years so I'm a bit out of the loop

@arbourd arbourd changed the title connection reset by peer Add retry logic for Slack http requests Apr 17, 2023
@arbourd arbourd added the help wanted Extra attention is needed label Mar 5, 2024
@arbourd arbourd linked a pull request Apr 4, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add exponential backoff for Slack requests arbourd/concourse-slack-alert-resource
2 participants
@arbourd @phoenix090