dashboard: export full bug info #4342
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a-nogikh
force-pushed
the
features/share-bug-info-archive
branch
6 times, most recently
from
e776553
to
df52bb3
Compare
|
It would be good to have a test that ensures that export respects access rules within namespace and don't export bugs from other namespaces. |
a-nogikh
force-pushed
the
features/share-bug-info-archive
branch
from
df52bb3
to
47f952b
Compare
a-nogikh
force-pushed
the
features/share-bug-info-archive
branch
from
47f952b
to
3cf7a2c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please do not review it yet
We get requests from the researchers community to make our data more accessible. This is a dirty and hacky version of the code that exports all published syzbot bugs as a big
.tar.gzarchive. It should already give some initial useful version to iterate on later.In the final solution, this will not be an HTTP endpoint, but rather a cron command that would upload the archive to GCS.OK, AppEngine does not let us dynamically generate responses bigger than 32 MB, so I added a simple code that saves the file to a bucket.There are a lot of TODOs before we can upstream it.