Auto-creqing: Difference between revisions

Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 62: Line 62:
These states are reserved for the AVMF server/service. The only exception is the state ''new'': Dumps will stay even when files are deleted from the database. The state of those dumps will however be reset to ''new''. This is done by the site code.
These states are reserved for the AVMF server/service. The only exception is the state ''new'': Dumps will stay even when files are deleted from the database. The state of those dumps will however be reset to ''new''. This is done by the site code.


{| class="wikitable"
{| class="wikitable sortable"
|-
|-
! State !! ID !! Description
! State !! ID !! class="unsortable"|Description
|-
|-
| new || 0 || The dump has not been handled by the AVMF service yet; it's either too new or not supported (file format). It's also possible that the dump has been ''reset'' by a moderator.
| new || 0 || The dump has not been handled by the AVMF service yet; it's either too new or not supported (file format). It's also possible that the dump has been ''reset'' by a moderator.
Line 87: Line 87:
|-
|-
| failed-xml || 41 ||  
| failed-xml || 41 ||  
|-
| failed-db || 43 ||
|}
|}


===Manual states===
===Manual states===
These states can only be set by moderators. They should be avoided as far as possible; keeping the dump ''used'' is preferred.
These states can only be set by moderators. They should be avoided as far as possible; keeping the dump ''used'' is preferred.
{| class="wikitable"
{| class="wikitable sortable"
|-
|-
! State !! ID !! Description
! State !! ID !! class="unsortable"|Description
|-
|-
| reset || 83 || A moderator wants the dump to be re-handled by the AVMF service, usually because he/she wants to unlock the related file temporarily. Lifecycle: new -> used -> reset -> new -> used. It would be better to improve/change the interface (regarding locks) instead of using this state.
| reset || 83 || A moderator wants the dump to be re-handled by the AVMF service, usually because he/she wants to unlock the related file temporarily. Lifecycle: new -> used -> reset -> new -> used. It would be better to improve/change the interface (regarding locks) instead of using this state.

Navigation menu

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.