Synchronization between Github and Bountysource is broken

[kerel-fs]

:lady_beetle: Problem

The existing bounty for https://github.com/kerel-fs/spectranalysis/issues/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!

:bulb: 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]

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!