| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Add some initial #syz invalid support to syz-cluster. For now, mark all
findings as invalid and don't display that such series have findings on
the web dashboard.
|
| |
|
|
| |
Cc syzkaller-bugs@googlegroups.com in all upstreamed syzbot ci findings.
|
| |
|
|
| |
This allows the dashapi-based sender include them in the email address.
|
| | |
|
| |
|
|
|
| |
We use the archive list to track replies, so it must be included in all
our original emails as well.
|
| |
|
|
|
| |
Add [moderation/CI] prefix for moderation emails.
Add a prefix with the service name for reports.
|
| |
|
|
| |
This will facilitate code reuse.
|
| |
|
|
|
| |
For the emails sent via GAE, we don't immediately know the MessageID.
Rely on addr context for their identification.
|
| |
|
|
|
| |
Refactor the configuration to support both SMTP and dashapi-based email
sending functionality.
|
| |
|
|
|
|
|
|
|
|
| |
Add the functionality to poll the specified LKML git archive for the new
user replies under the bot's messages.
Check out the repository and pull it once in the specified time period.
Keep track of the latest processed commit hash.
Track the original report ID via In-Reply-To references.
|
| |
|
|
|
|
|
|
| |
Since email-reporter is anyway tied to a specific reporting channel,
let's keep reporter names less generic.
Using "lkml" instead of just "email" will also let us generate proper
links to the email discussions based only on Reporter+MessageID.
|
|
|
Add the high-level logic for the email-reporter component that will
be responsible for sending bug reports and reacting to incoming emails.
|
