-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Implement Celery task for Discord notifications of reports #3517
Comments
Hi @olliestanley , I'm happy to give this a try. I've managed to get the dev server running locally and spotted where that button lives and what are the methods called. I have a couple of questions:
Chances are this issue might have a steep learning curve, so if anyone more knowledgeable is keen to pick this up, feel free, I'm happy with the learning experience anyways. |
I think the previous approach was fine in principle, but there was a bug causing the report function to be broken entirely, and we wanted to fix prod ASAP so just reverted the change. We don't have a sandbox, you might have to set something up for that unfortunately. Hopefully this should be a fairly small change so would be great if you could take a look! |
Cool, thanks for the answers, I will work through this these days and will let you know if I get stuck 🤞 |
It should fix: #3517 In debeb35 we reverted the original implementation of the task as it broke the production environment. The problem was that celery tasks need objects that could be JSON serializable and we were passing a `Message` instance, so just passing the details fixed the issue. ![Screenshot from 2023-07-13 08-04-49](https://github.com/LAION-AI/Open-Assistant/assets/33068707/1e76d71f-7182-49ec-8e94-38ef2fce56a2) A few things that I noticed: - There's no `pre-commit` version pinned in the requirements.txt so I just used the latest one (3.3.3). In the past I had experienced issues with this so it might be a good idea to pin it. - There are a few automated tests, I was about to write them but found no installation of `pytest` or similar, if you consider so, I'm happy to write them and install the necessary libraries as eventually that will make the codebase more robust.
The previous implementation caused a bug and so is reverted by #3516
The text was updated successfully, but these errors were encountered: