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.

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

Proxy Support broken on Slack App approach (Slack Bot Token approach) #217

Open
4 of 10 tasks
frednntelia opened this issue Jun 22, 2023 · 6 comments
Open
4 of 10 tasks
Labels
bug Something isn't working

Comments

@frednntelia
Copy link

Description

When using the slack-github-action in GitHub App mode, the Action fails to utilize environment variables HTTPS_PROXY and https_proxy correctly.

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • example code related
  • testing related
  • discussion

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version: slackapi/slack-github-action@v1.24.0

node version:

OS version(s): Ubuntu 20.04 LTS

Steps to reproduce:

  1. run slack-github-action behind a proxy
  2. make sure you set HTTPS_PROXY and https_proxy env vars
  3. use slack webhook method
  4. observe success
  5. use slack app method (slack bot token)
  6. observe failure

Expected result:

HTTPS_PROXY var is respected and slack api call goes through properly, resulting in the display of a message on the respective channel.

Actual result:

Slack message never arrives in channel. Likely because HTTPS_PROXY env var is not being respected

Attachments:

[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 3.***.***.153:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 18.***.***.***:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 3.***.***.98:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 3.***.***.98:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 18.***.***.225:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 3.***.***.98:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 18.***.***.***:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 3.***.***.153:443
[WARN]  web-api:WebClient:0 http request failed connect ETIMEDOUT 18.***.***.225:443
Error: The operation was canceled.
@WilliamBergamin
Copy link
Contributor

Hello @frednntelia thanks for writing in 💯

This is a curious behavior, would be able to tell me if the proxy you are using is http or https?

Based on this test suite seems like webhook method should use default axios config when proxy uses HTTPS

@frednntelia
Copy link
Author

Hi @WilliamBergamin, thanks for your swift response! 👍🏾
This proxy in my assembly is http afaik.

@frednntelia
Copy link
Author

@WilliamBergamin is there a way to enable debug level logs from this Action, so that we can get some more context?

@WilliamBergamin
Copy link
Contributor

Based on what I can see in the code there seems to be a bug where HTTP proxies are not properly set but HTTPS proxies are, I am not sure if there is a reason behind this

@WilliamBergamin WilliamBergamin added the bug Something isn't working label Jul 6, 2023
@minjunk
Copy link

minjunk commented Aug 1, 2023

The Slack Bot Token Proxy was updated in June (#205), but the release was last in May (v1.24.0).
Do you happen to know when there will be a release plan for this update?

@joshsnelling
Copy link

Is there a plan to release this fix? If not, is there a workaround that can be used in the meantime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants