search

SFDO-Tooling / Metecho

Web-based tool for collaborating on Salesforce projects
BSD 3-Clause "New" or "Revised" License
44 stars 34 forks source link

Issue when null email returned from GitHub #2083

Open kreynen opened 1 year ago

kreynen commented 1 year ago

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 commented 1 year ago

@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 commented 1 year ago

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 commented 1 year ago

Tracking this issue as W-12175666. Thank you!

prescod commented 1 year ago

@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 commented 1 year ago

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.