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

Synchronization between Github and Bountysource is broken #1556

Open
kerel-fs opened this issue Nov 22, 2021 · 1 comment
Open

Synchronization between Github and Bountysource is broken #1556

kerel-fs opened this issue Nov 22, 2021 · 1 comment

Comments

@kerel-fs
Copy link

🐞 Problem

The existing bounty for kerel-fs/spectranalysis#1 posted in bs: 102888571-load-satnogs-artifacts can't be claimed because bountysource is showing this issue as "open" while in fact it was already fixed&closed in github.

This is a synchronisation issue which happend multiple (#1401) times (#1474) in the past (#1536).

I contacted support@ several weeks ago, but it is still not solved nor did I got a date when this will be fixed!

💡 Possible solution

  • Add a working process to trigger the usage of the existing admin tools to force close in the event of sync issues.
  • Investigate the root cause for these synchronization issues
@kerel-fs
Copy link
Author

Update:
After contacting support multiple times over several weeks, the (force-?)sync was performed today (the issue in Bounty Source is correctly shown as "closed" now). It appears to have happened a few hours after I sent yet another message to support, stating an ultimatum to inform bakers to open a dispute for their money.

Despite this, the Synchronization Issue described here still exists. The sync should have been performed automatically. And apparently this does not work reliably!

@kerel-fs kerel-fs changed the title Fix Synchronization Issues between Github and Bountysource Synchronization between Github and Bountysource is broken Nov 25, 2021
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

1 participant