-
Notifications
You must be signed in to change notification settings - Fork 1
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 response emails are sent #309
Comments
cannot reproduce, I just received an email. |
logs were disabled, so I can't check those (they're now enabled). |
@njahn82 can you post the DOIs that lead to the missed message? |
fill in example DOIs
…On Fri, 24 Sept 2021 at 11:00, Max Held ***@***.***> wrote:
@njahn82 <https://github.com/njahn82> can you post the DOIs that lead to
the missed message?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#309 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM7YRTBK26NAONR2VBN4LTUDQ43BANCNFSM5EVO5BQQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
to reproduce, send several reports from the same shiny session in quick sucession |
RAM was reported at 96% so this might have something to do with it, though I am not certain. |
confirmed that this is ram, problem is now away, closing in favor of #315 |
there seems to be a bug again, reported by @njahn82:
The text was updated successfully, but these errors were encountered: