Solved No notifications from Release Bell

[A Former User]

I no longer seem to get email notifications from Release Bell. They worked fine for over a year at least and now I haven't gotten them in several weeks. I've deleted and readded my personal access token from Github, but no change.

Here are some errors from the logs:

Jun 01 22:34:33 releasebell/tasks syncGithubStarredByUser: mygithubusername +2ms
Jun 01 22:35:14 releasebell/tasks syncGithubStarredByUser: found 1556 starred repos +40s
Jun 01 22:35:14 releasebell/tasks syncGithubStarredByUser: new projects: 1 outdated projects: 0 +386ms
Jun 01 22:35:14 releasebell/tasks syncGithubStarredByUser: [jasondrawdy/Forerunner] is new for user mygithubusername +1ms
Jun 01 22:35:14 releasebell/tasks syncReleasesByProject: [jasondrawdy/Forerunner] type github start sync releases. Last successful sync was at 1970-01-01T00:00:00.000Z +4ms
Jun 01 22:35:14 releasebell/tasks syncReleasesByProject: [jasondrawdy/Forerunner] found 0 new releases +175ms
Jun 01 22:35:14 releasebell/tasks syncReleasesByProject: [jasondrawdy/Forerunner] successfully synced +0ms
Jun 01 22:35:14 releasebell/tasks syncReleasesByProject: [noLogicXD/xssizer] type github start sync releases. Last successful sync was at 1970-01-01T00:00:00.000Z +348ms
Jun 01 22:35:15 ERROR Repository access blocked [ /app/code/backend/tasks.js:198:32 ]
Jun 01 22:35:15 Repository access blocked HttpError: Repository access blocked
Jun 01 22:35:15 at /app/code/node_modules/@octokit/request/dist-node/index.js:66:23
Jun 01 22:35:15 at runMicrotasks (<anonymous>)
Jun 01 22:35:15 at processTicksAndRejections (internal/process/task_queues.js:97:5)
Jun 01 22:35:15 releasebell/tasks run: done +203ms

I see similar logs for at least 10 repos before the logs stop from a recent update.

[nebulon]

Looks like it fails due to an unhandled error condition. That repo in question was apparently taken down https://github.com/noLogicXD/xssizer
I will see how we can just log that and continue regardless.

[nebulon]

I think I have fixed this issue now and published a new app package as well. Please let me know if the updated version fixes it for you.

[A Former User]

That did it! Thanks!