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

Heroku "App Crashed" #176

Open
SimonLab opened this issue Feb 13, 2018 · 3 comments
Open

Heroku "App Crashed" #176

SimonLab opened this issue Feb 13, 2018 · 3 comments

Comments

@SimonLab
Copy link
Member

image

dwylbot is crashing on Heroku when a new event is received.

  • reproduce the error on localhost to get more information about the issue
@SimonLab
Copy link
Member Author

SimonLab commented Feb 13, 2018

error:
image

Function call error:
The error is due to the call of the function Enum.any?/2 with the first parameter being nil when dwylbot check for breaking rules:

Rules.any_error?(check_errors, error)

Github payload error, bad credentials
image

The payload isn't received properly due to a "bad credentials" so Enum.any? isn't able to run on a wrong payload

Installation token is nil:

token = @github_api.get_installation_token(payload["installation"]["id"])

Installation not found:
image

@SimonLab
Copy link
Member Author

The error on my localhost was due to a conflicts between multiple dwylbot Github app tests. After updating the environment variables everything works fine. The next step is to see if the error is similar on the server. I'll try to get more logs info directly from the server instead of using a localhost app.

@SimonLab SimonLab added this to the doc & update milestone Feb 14, 2018
@SimonLab SimonLab added the T1d label Feb 14, 2018
@SimonLab
Copy link
Member Author

While looking for logs #180, I spotted some other issues/logging infomraiton that could also be resolved:

However I couldn't find more information about the current error on the production at this stage with heroku logs. The next step is to understand how to logo more info in a production information, otherwise another thought is to make sure that all the environmnent variables are properly loaded, I think Phoenix 1.3 might do this differently.

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

1 participant