Petar Maymounkov

@dworthen I released the structured result output in https://github.com/gov4git/gov4git/releases/tag/v2.0.4

@dworthen as I look at the code, I see that the code already produces an error amounting to "user X is not a member of community Y", specifically this one...

OK. I would scrap the "submit an issue with logs attached" feature. Instead we just want to make sure the users know how to find the logs to send it...

@Stebalien: > I find out who has what. This is a mapping of CID -> PID. This is how things work today. We'd like to generalize this significantly. A source...

> Is this a general IPLD Schema problem (then it should really be fixed) or an Go Schema implementation detail? @vmx I've updated the description. Maybe it was a bit...

If this is the case, this suggests a design bug in the IPLD data model: if the IPLD data model allows arbitrary bytes in a string (which I believe it...

Please upgrade the version of gov4git in your cron to the latest v2.2.6. The crons are sometimes failing because the earlier version was taking too much time due to an...

Hi @AshBC. Yes, let's upgrade your Gov4Git deployment to v2.2.6 and then if the issue persists we'll look further. To upgrade: - Go to your project's governance repo: https://github.com/cubeca/cube-gov.public/ -...

The authentication error suggests that the GitHub access token you used to deploy governance is either expired or has insufficient privileges to clone the governance repository. Could you verify it...

Yes, correct! I am glad it worked out. Note that you will occasionally/infrequently get a failed cron job run due to GitHub scheduling capacity. This is expected behavior. Of course,...