Bureaucrats, staff, Administrators
938
edits
Auto-creqing: Difference between revisions
Jump to navigation
Jump to search
→Automatic states
mNo edit summary |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
===New system=== | ===New system=== | ||
The "new" system, which is used by | The "new" system, which is used by Avdump, is not part of any API and not documented anywhere. (The server side part is however related the UDP API server). Instead of checking against AniDB data and issue creqs directly when necessary, Avdump just sends the information (per file) to the server without any regard. It is entirely up to the server to decide what to do with the raw data that is received. This new approach was implemented to shift the control from the clients to the server. | ||
The different parts of the system is; | The different parts of the system is; Avdump, AVMF server, AVMF service, auto-granter and the {{AniDBLink|avmf|avmf page}}. | ||
====Avdump==== | ====Avdump==== | ||
| Line 26: | Line 26: | ||
# Decrypt, decompress the package. If it should fail the package will just be disregarded. | # Decrypt, decompress the package. If it should fail the package will just be disregarded. | ||
# Validate the dump (XML validation). | # Validate the dump (XML validation). | ||
#: Invalid dumps will only be stored for | #: Invalid dumps will only be stored for Avdump debugging purposes. | ||
# Map the dump to a AniDB file and store the dump in database. | # Map the dump to a AniDB file and store the dump in database. | ||
#: If no file is found, the dump is marked unknown. It will be mapped to a file when/if the file is added (by the site code). The AVMF Service does also do some maintenance in this regard. | #: If no file is found, the dump is marked unknown. It will be mapped to a file when/if the file is added (by the site code). The AVMF Service does also do some maintenance in this regard. | ||
| Line 46: | Line 46: | ||
A page that lists all dumps, with tons of filters. The main use of this page is to (some are mod only): | A page that lists all dumps, with tons of filters. The main use of this page is to (some are mod only): | ||
* check if a file has been dumped. | * check if a file has been dumped. | ||
* who dumped it? when? how many has confirmed it? version of | * who dumped it? when? how many has confirmed it? version of Avdump? | ||
* check why a file has not been verified | * check why a file has not been verified | ||
* unlock a file | * unlock a file | ||
| 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 !! Description | ! State !! ID !! class="unsortable"|Description | ||
|- | |- | ||
| new || 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. | ||
|- | |- | ||
| used || A file is considered ''verified'' if it has one ''used'' dump. There can only be one dump with this state for each file at once. In the process of changing the state of a dump to ''used'', automatic change requests will be generated if needed. | | used || 11 || A file is considered ''verified'' if it has one ''used'' dump. There can only be one dump with this state for each file at once. In the process of changing the state of a dump to ''used'', automatic change requests will be generated if needed. | ||
|- | |- | ||
| deprecated || The dump was in use at some point, but has been automatically replaced by an other. Dumps of newer versions (produced by newer versions of | | deprecated || 13 || The dump was in use at some point, but has been automatically replaced by an other. Dumps of newer versions (produced by newer versions of Avdump) will automatically replace dumps of older versions ''unless it requires new creqs''. Dumps with this state might be purged regularly at some point, but that is not enabled ATM. | ||
|- | |- | ||
| candidate || The dump is not used because the related file is already verified by another dump of an older version of | | candidate || 23 || The dump is not used because the related file is already verified by another dump of an older version of Avdump. The service will never issue creqs for files that has already been verified. A moderator can however delete the ''used'' dump (or smite it) and then ''reset'' the candidate if needed. | ||
|- | |- | ||
| unseen || The dump is not used because the related file is already verified by another dump of the same version of | | unseen || 21 || The dump is not used because the related file is already verified by another dump of the same version of Avdump. It basically means that two copies of the same Avdump version has generated two different dumps (usually encoding issues due locale). It is the ''most seen'' dump that was supposed to be used in cases like these, however, ''first come, first served'' is currently implemented. | ||
|- | |- | ||
| stalled || The dump is stalled due a pending change request of the related file. Stalled dumps will be reset to ''new'' automatically after some time. | | stalled || 33 || The dump is stalled due a pending change request of the related file. Stalled dumps will be reset to ''new'' automatically after some time. | ||
|- | |- | ||
| incoherent || The dump is not trusted, and thus not used, because the track bitrates does not match up to the file size. Too much overhead in other words. The threshold is 6% ATM. | | incoherent || 47 || The dump is not trusted, and thus not used, because the track bitrates does not match up to the file size. Too much overhead in other words. The threshold is 6% ATM. | ||
|- | |- | ||
| exception || The AVMF server threw an exception when handling an incoming dump. | | exception || -11 || The AVMF server threw an exception when handling an incoming dump. | ||
|- | |- | ||
| failed || The AVMF service failed to process the dump. | | failed || 45 || The AVMF service failed to process the dump. | ||
|- | |- | ||
| codec || Unknown codec. The AVMF service has to be updated. | | codec || 31 || Unknown codec. The AVMF service has to be updated. | ||
|- | |||
| 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 !! Description | ! State !! ID !! class="unsortable"|Description | ||
|- | |- | ||
| reset || 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. | ||
|- | |- | ||
| smitten || The dump is considered invalid by a moderator. This state can be used by developers to pick up and handle issues with | | smitten || || The dump is considered invalid by a moderator. This state can be used by developers to pick up and handle issues with Avdump. It is better to use [[Avdump issues]] to keep track of these dumps, though. | ||
|- | |- | ||
| forgotten || When a | | forgotten || || When a Avdump issue has been resolved the related ''smitten'' dumps should be deleted. Dumps related to issues that's never resolved should be marked ''forgotten''. (It is in other words just a second state of ''smitten''). This state is not really used. | ||
|- | |- | ||
| deleted || Not a state. Moderators are allowed to delete dumps completely if needed. Usually only done when cleaning up after old | | deleted || || Not a state. Moderators are allowed to delete dumps completely if needed. Usually only done when cleaning up after old Avdump versions. | ||
|} | |} | ||
[[Category:Avdump]][[Category:Development]] | [[Category:Avdump]] | ||
[[Category:Development]] | |||