Bot has "trouble processing the request"

[KirstieJane]

Describe the bug

All contributors bot has trouble processing the request to add a new contributor.

See, for example: the-turing-way/the-turing-way#822 (comment)

To Reproduce

I typed the following in a pull request comment.

Hey @allcontributors bot - please add @ACFaul for event organizing.

The bot replied saying:

We had trouble processing your request. Please try again later.

We've had this problem for a few months unfortunately 😢

Expected behavior
I was expecting the bot to open a new pull request 😬

Screenshots

Additional context

This used to work, and I'm not sure what happened. It might be because I sometimes move the order around in the json file...but I don't think that's the case.

Thank you so much for your help!

[Berkmann18]

That's surely because it expects something like "@allcontributors Please add @ACFaul for event".
Basically it expects a Please add at_username for type message.

[allcontributors]

@Berkmann18

I could not determine your intention.

Basic usage: @all-contributors please add @Someone for code, doc and infra

For other usages see the documentation

[KirstieJane]

Hi @Berkmann18 - I tried that and got the same error: the-turing-way/the-turing-way#822 (comment)

[Berkmann18]

I can't tell if there's a configuration/setting problem or if it's due to the version.
Have you tried using the CLI?

[smoia]

I had the same problem in a repo I'm working on. I checked the configuration and the settings, all seemed ok. I thought it was due to the fact that I was already using a cotrnibution type that is not implemented yet in the bot, but I see now that it might be independent?

[Berkmann18]

@smoia Does that still happen with the latest version of the bot?

[smoia]

@Berkmann18 I never had any occasion to test it again until today. It's still giving troubles:
physiopy/phys2bids#233 (comment)
It already fired twice, if it enters a loop like in old times, I'm going to delete the comment.

[rachelcarmena]

Hi! 🙌 Just an idea. If it worked with other users, it could be an issue related to certain GitHub user profiles. I found issues when managing GitHub user profiles with the GitHub API because some data are missing for some users.

[mloning]

A similar issue here: sktime/sktime#335

CLI works without any issues, here's the commit: sktime/sktime@70b82aa

[malvikasharan]

For all-contribution troubleshoot, see this PR: the-turing-way/the-turing-way#843

[mloning]

Seems like the .all-contributorsrc file is different for the bot and CLI, does that mean that we cannot use both with the same config file?

[mloning]

I still can't get it to work ...

I've removed our .allcontributorsrc and create an empty README.md. The initial PR worked and added the .allcontributorsrc and updated the README.md with the table and badge. However, when I asked the bot to make another addition, instead of updating the files, it wanted to recreate them leading to a merge conflict as these files already existed.

I've tried a number of other things, but still can't get it to work. Any ideas on how to go about debugging this?

CLI works without any problems.

[meteoritt]

I have some trouble: meteoritt/topalias#4
will try without .allcontributorsrc and with .allcontributorsrc

[meteoritt]

With cli all work fine, but bot not work: meteoritt/topalias#5

[outofambit]

We're seeing this issue over in processing/p5.js#5268, has anyone found a workaround that isn't using the CLI?

EDIT: debugged with CLI to get the error message, fixed with processing/p5.js@7bfb8b3 and we're back in business :))

[gr2m]

@outofambit glad it’s back to normal! It seems that GitHub API is experiencing some trouble, I see lots of time outs right now myself. Feel free to ping me directly next time :) Cool to see p5.js using @all-contributors

[brandonlenz]

This hasn't worked the last few times of infrequent attempts over the course of a month or so, e.g. trussworks/react-uswds#2618 (comment)

Any way to debug the actual issue? If there were a problem with the repo config or a user, I would want the bot to indicate that. As of now, it just sounds like that underlying API is failing. Any way to check the status of things separately from github status?

[gr2m]

Any way to check the status of things separately from github status?

Unfortunately no, I can share access to the logs as they might include non-public data

[gr2m]

I do love the idea of having a view to self-debug problems, but it would require quite some work. We would need an OAuth flow to verify you have access to a given repository, and then show the logs in a custom UI. I'd be happy to provide guidance if anyone wants to build this, but cannot work on it myself