Auto-creqing: Difference between revisions

! State !! 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.

| 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.

| 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 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 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 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.

| 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.

| exception || The AVMF server threw an exception when handling an incoming dump.

| failed || The AVMF service failed to process the dump.

| codec || Unknown codec. The AVMF service has to be updated.

! State !! 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.

| 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 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 Avdump versions.