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

Issue when null email returned from GitHub #2083

Open
kreynen opened this issue Dec 6, 2022 · 5 comments
Open

Issue when null email returned from GitHub #2083

kreynen opened this issue Dec 6, 2022 · 5 comments

Comments

@kreynen
Copy link

kreynen commented Dec 6, 2022

This may be related to the Keep my email addresses private option at https://github.com/settings/emails

Screen Shot 2022-12-06 at 10 50 03 AM

@davidmreed
Copy link
Contributor

@kreynen I would expect this not to work, but can you provide reproduction steps and the actual behavior shown from Metecho? We would like to provide clear instruction to the user.

@kreynen
Copy link
Author

kreynen commented Dec 6, 2022

This happened when we were trying to get additional users to test https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits. I've stripped out the user-specific information, but this is what Metecho is returning when synch the GitHub Collaborators.

Uh oh. There was an error re-syncing GitHub Collaborators for this Project: “Membership Schema and Benefits.”
null value in column "name" violates not-null constraint DETAIL: Failing row contains ([ID], [Username], null, https://avatars.githubusercontent.com/u/[ID]?v=4).

Hopefully this error is logged somewhere on your end with more information.

@davidmreed
Copy link
Contributor

Tracking this issue as W-12175666. Thank you!

@prescod
Copy link
Contributor

prescod commented Feb 9, 2023

@kreynen Is this a private instance of Metecho that you were using, or one hosted by Salesforce?

A related bug was fixed in November and deployed on our instances recently, so the problem might be fixed.

Something slightly confusing about the bug report is that the column it is complaining about is name, not email. Maybe there is a different setting that controls name visibility. Or maybe the setting controls both.

@kreynen
Copy link
Author

kreynen commented Feb 9, 2023

The instance is https://metecho.herokuapp.com/. I am using it for https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits, but this instance is used for all the Commons Sprint projects. I believe this was resolved by removing the user from the MembershipSchemaAndBenefits project, but I wanted to flag this in case it comes up again in the next Commons sprint in March.

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

3 participants