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
Handle new emails correctly #28
Labels
Comments
So, clearly we can't rely on their email being complete. Another feature was added that should correctly pull their real email from FAS when they are created, but we still have a DB now full of these unusable email addresses. We should add some code that catches this error, and:
|
ralphbean
added a commit
to fedora-infra/fmn.consumer
that referenced
this issue
Mar 23, 2015
Currently it just emails us. This tries to: 1) get a good email from fas 2) failing that, disable the account. Fixes fedora-infra/fmn#28.
jeremycline
pushed a commit
to jeremycline/fmn
that referenced
this issue
Dec 7, 2016
…pref-update Throw a lock around cached preference refresh.
jeremycline
pushed a commit
to jeremycline/fmn
that referenced
this issue
Dec 7, 2016
Include rules for the-new-hotness.
jeremycline
pushed a commit
to jeremycline/fmn
that referenced
this issue
Dec 7, 2016
These were forgotten in fedora-infra#28 -- whoops!
jeremycline
pushed a commit
to jeremycline/fmn
that referenced
this issue
Dec 7, 2016
…oration-fix Fix hint decoration.
jeremycline
pushed a commit
that referenced
this issue
Apr 26, 2017
…ization Context page reorganization
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think this comes from when we create new accounts automatically for new packagers.. their email forwarding is not necessarily hooked up yet. Can we rely on their
@fedoraproject.org
address being usable?The text was updated successfully, but these errors were encountered: