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

"No to!" in the logs #311

Closed
Crocmagnon opened this issue May 15, 2020 · 5 comments · Fixed by #312
Closed

"No to!" in the logs #311

Crocmagnon opened this issue May 15, 2020 · 5 comments · Fixed by #312
Labels

Comments

@Crocmagnon
Copy link

Crocmagnon commented May 15, 2020

Describe the bug

I noticed some errors in the logs (No to! <nil>), see: https://gist.github.com/Crocmagnon/b54664133aed86127f2133bdb5f099d3

Steps to reproduce (if necessary)

Let the app run, with federation enabled?

Expected behavior

I shouldn't get this message in the logs? Or it should be more explicit.

Application configuration

  • Single mode or Multi-user mode? single
  • Database? sqlilte
  • Open registration? no
  • Federation enabled? yes

Version or last commit: 037fc40 but happened also with v0.12.0

@thebaer
Copy link
Member

thebaer commented May 15, 2020

Thanks @Crocmagnon. This would have more useful information with the --debug flag enabled, so I've changed it to only log this message when that's turned on in #312.

@Crocmagnon
Copy link
Author

👍 and what's that error message supposed to mean?

@Crocmagnon
Copy link
Author

I mean, should I do something about it? Is there something not working on my instance?

@thebaer
Copy link
Member

thebaer commented May 15, 2020

It refers to the to attribute on ActivityPub requests -- it's only needed for development / debugging, so nothing for you to worry about. Whatever activity is triggering the message is simply going ignored.

@Crocmagnon
Copy link
Author

Thanks for your answer, patience and speed! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

2 participants