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

feat: Improve SSL error logging. #1557

Closed

Conversation

megabus-tobin
Copy link
Contributor

Log more information about why an SSL error occured as this can be very difficult to diagnose. This is logged in the same way as other probably fatal issues are, e.g. HTTP 404s.

Copy link
Contributor

github-actions bot commented Mar 7, 2024

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale label Mar 7, 2024
Log more information about why an SSL error occured as this can be very difficult to diagnose. This is logged in the same way as other probably fatal issues are, e.g. HTTP 404s.
Copy link
Contributor

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale label Apr 12, 2024
@github-actions github-actions bot closed this May 12, 2024
@megabus-tobin
Copy link
Contributor Author

I missed that this had been closed automatically. It wold still be good to get this in if possible to make debugging SSL related errors easier.

@kaylareopelle
Copy link
Contributor

Hi @megabus-tobin , I missed that too. Thanks for bringing this to our attention.

I'm not able to reopen the PR, the button is null with the message: The ssl-error-logging branch was force pushed or recreated. Are you able to reopen in a new PR?

@megabus-tobin
Copy link
Contributor Author

@kaylareopelle ah, I didn't realise Github couldn't handle that happening. I've been using the branch locally and rebasing it periodically using the official repo's main branch.

New MR: #1644

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

Successfully merging this pull request may close these issues.

None yet

4 participants