WeblateOrg / weblate

Web based localization tool with tight version control integration.
https://weblate.org/
GNU General Public License v3.0
4.49k stars 993 forks source link

Non-existing progress view for project #12413

Closed nijel closed 1 week ago

nijel commented 1 week ago

Describe the issue

11717 introduced redirecting to progress page on repository operations. It uses the same redirect for project/category/component/translation scopes, but the view only supports only component and translation scopes:

https://github.com/WeblateOrg/weblate/blob/bf2a2c46649785703f6e816b6c948df1fc3b5831/weblate/trans/views/settings.py#L348

Thus, when a user performs an operation on project or category scope, it ends up on HTTP 404 Not Found.

I already tried

Steps to reproduce the behavior

  1. Go to project repository maintenance
  2. Click on rescan
  3. See HTTP 404

Expected behavior

The actual progress should be shown

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

mont29 commented 1 week ago

Uuuuh indeed...

Not sure what are Groups here?

For Projects, how would you suggest fixing this? Adding a Progress view for projects as well? Not sure what it would mean/represent though. Or redirect to /projects/my-project/ instead?

nijel commented 1 week ago

Sorry, it should have been category, I was writing this rushing.

There can be multiple components in progress for both project and category. I'm not sure whether it's a good idea to include logs for all of them on a single page. But it could probably show a progress bar for each of them, there is existing support for this in the client code using data-task attribute.

github-actions[bot] commented 1 week ago

Thank you for your report; the issue you have reported has just been fixed.

github-actions[bot] commented 1 week ago

Thank you for your report; the issue you have reported has just been fixed.