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

Network Login Failure error reporting is QUITE unhelpful #2142

Closed
derek-adair opened this issue Nov 1, 2018 · 8 comments
Closed

Network Login Failure error reporting is QUITE unhelpful #2142

derek-adair opened this issue Nov 1, 2018 · 8 comments

Comments

@derek-adair
Copy link

Currently if my social account integration is not set up properly, I'm left having to dig into the code to debug. It'd be a fantastic improvement for debugging if we could make this generic fail more helpful.

  • {{ auth_error }} returned in debug mode
  • Exact errors reported via the error console/logs (even w/o debug=True)

I'm sure there are other improvements that can be made in this regard.

I'd be glad to dive in and get this done if no one else had the bandwidth.

@derek-adair derek-adair changed the title Social Network Login Failure is QUITE unhelpful Social Network Login Failure error reporting is QUITE unhelpful Nov 1, 2018
@derek-adair
Copy link
Author

Probably a duplicate of #1120

@derek-adair
Copy link
Author

Specifically using twitter. Which seems to NOT be related to #1120? unsure tho.

@derek-adair derek-adair changed the title Social Network Login Failure error reporting is QUITE unhelpful [Twitter] Social Network Login Failure error reporting is QUITE unhelpful Nov 1, 2018
@derek-adair derek-adair changed the title [Twitter] Social Network Login Failure error reporting is QUITE unhelpful Network Login Failure error reporting is QUITE unhelpful Nov 1, 2018
@ykdojo
Copy link

ykdojo commented Dec 28, 2018

I had the same issue with Twitter. Currently working on a fix that's going to put out a log.

@kov
Copy link

kov commented May 12, 2021

This is very frustrating and it is a bit surprising that it has been an issue for so long (the first issue I hit on my search was from 2014). I am working on a dockerized application so it's not very easy to debug things or make changes. Why not simply provide at least some detail in the logs at least so that you don't risk exposing something you shouldn't to users. It really shouldn't be that hard to do, right?

@pennersr
Copy link
Owner

pennersr commented Jul 6, 2023

Dupe of #1120

@pennersr pennersr closed this as completed Jul 6, 2023
@derek-adair
Copy link
Author

my bad dude. Thanks for your work.

Would you be open to someone help you triage issues?

@pennersr
Copy link
Owner

pennersr commented Jul 6, 2023

Sure, there is nothing preventing anyone from hopping onto an issue and doing the research.

@derek-adair
Copy link
Author

Sure, I'll try to comment where I can. I meant in a more official capacity -- e.g. closing issues for you or escalating valid ones -- which would require us being on the same page with your ambitions and approach to open source.

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

No branches or pull requests

4 participants