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

Preview on results page #7

Open
bennofs opened this issue Mar 6, 2020 · 2 comments
Open

Preview on results page #7

bennofs opened this issue Mar 6, 2020 · 2 comments

Comments

@bennofs
Copy link
Owner

bennofs commented Mar 6, 2020

On the results page, there should be a way to already see a preview of the dump, to make the decision which dump to choose easier.

@mcswell
Copy link

mcswell commented May 28, 2020

Not sure whether this is the right place to ask, but the wdumper "about" page (https://tools.wmflabs.org/wdumps/about) doesn't appear to have any way to do this, and "Preview results" sounded reasonable, so...

I accidentally started 3 identical dumps at https://tools.wmflabs.org/wdumps/dumps?page=1. The only criterion I put on the dumps was "language='ru'". I didn't see much in the way of output, and it was only later that I realized this was because my jobs were queued.

I'd like to kill two of my dumps in the queue, but I can't see any way to do this. Can it be done?

And apropos of the name of this Issue ("Preview on results page"), it would be nice if the system could provide some estimate (preview) of how big a dump is likely to be. It's quite possible that my request to dump the Russian wikidata is an unreasonable one, i.e. a request that will generate huge amounts of data and/or consume too much computer resources for too long. If that's the case, I'd be happy to put more constraints on my request for results (if I could figure out how).

@bennofs
Copy link
Owner Author

bennofs commented Jun 3, 2020

Thanks for your feedback! I've opened a new issue for estimating dump size before generating a dump (#12).

I'd like to kill two of my dumps in the queue, but I can't see any way to do this. Can it be done?

Unfortunately, this is not possible right now. It requires some kind of authentication, which we don't have at the moment (otherwise, anyone could kill your dumps, which would not be good). A simple fix right now would be to prevent putting the exact same dump into the queue twice (this should be easy to implement, I've created #13 for this). In the future, we might implement some kind of session identification so that the creator of a dump can modify some of its properties (like retention time or killing it).

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

No branches or pull requests

2 participants