]jPtdZddlZddlmZddlmZddlmZddlm Z m Z eje Z dZdZy) z FSM utility functions for backfilling and managing state transitions. This module contains reusable functions for FSM state management that are used across different parts of the codebase. NCurrentContext)iterate_queryset)get_or_infer_state)get_or_initialize_stateis_fsm_enabledcd|dkrytsy ddlm}t|jj |j dd|jdd}|sytjd t|d tj}|jj | }t|D]}t|}t||| tjd t|d y#t $r$} tj#d| dYd} ~ yd} ~ wwxYw)a| Backfill initial FSM states for tasks created during storage sync. This function creates initial CREATED state records for all tasks that were created during a storage sync operation. It's designed to be called after tasks have been successfully created and linked to storage. Args: storage_id: The ID of the storage that created the tasks tasks_created: Number of tasks that were created link_class: The link model class (e.g., S3ImportStorageLink) to query tasks Note: - CurrentContext must be available before calling this function - This function is safe to call in both LSO and LSE environments - Failures are logged but don't propagate to prevent breaking storage sync - FSM feature flag is checked before processing - Tasks are processed in chunks via iterate_queryset to avoid OOM issues rN)Task)storagez -created_attask_idT)flatz.Storage sync: creating initial FSM states for z tasks)id__in)userinferred_statez%Storage sync: FSM states created for z$FSM sync after storage sync failed: )exc_info)r tasks.modelsr listobjectsfilterorder_by values_listloggerinfolenrget_userrrr Exceptionerror) storage_id tasks_created link_classr task_idsrtasks_qstaskres D/root/env/lib/python3.12/site-packages/label_studio/fsm/functions.pybackfill_fsm_states_for_tasksr&s&(  P%    % %j % 9 Xm $^m 5 [[ .    DS]OSYZ[&&(<<&&h&7$X. TD/5N #DtN S T  ;CM?&QR P ;A3?$ OOPsAD$BD D/ D**D/cddlm}ddlm}ddlm}ddlm}ddlm }|j}||sy |}|j|} |jr |jn |j} | @|jr|j|d | n|j|d | |||y| | k7rC| |jk(r|j|d | n|j|d | |||yy#t $rD} t"j%d t'| |j(|j(d Yd} ~ yd} ~ wwxYw)a+ Update task FSM state after an annotation has been deleted. This function ensures that the task's FSM state reflects its current labeled status after an annotation has been deleted. It will: 1. Check if FSM is enabled 2. Get the current task state 3. Determine the expected state based on task.is_labeled 4. Execute appropriate transition if state doesn't match 5. Update project state if task state was changed Args: task: The Task instance whose annotation was deleted project: The Project instance containing the task Note: - Requires CurrentContext to be set with a valid user - Failures are logged but don't propagate to prevent breaking annotation deletion - Will initialize state if task has no FSM state record yet rr)&update_project_state_after_task_change)TaskStateChoices)get_state_manager)r)rNtask_completed)entitytransition_namertask_in_progressz4FSM state update failed during annotation deletion: )r project_id)extra)core.current_requestrfsm.project_transitionsr(fsm.state_choicesr)fsm.state_managerr* fsm.utilsrrget_current_state_value is_labeled COMPLETED IN_PROGRESSexecute_transitionrrwarningstrid) r#projectrr(r)r*rr StateManagercurrent_task_stateexpected_stater$s r%+update_task_state_after_annotation_deletionrBJsN*4N23( #> " " $D t $  (* *AA$G8<)33L\LhLh  %//tM]dh/i//tM_fj/k 27 F > 1!1!=!==//tM_fj/k//tM]dh/i 27 F 2  B3q6( K"ggWZZ@    sA=D9AD E :E  E)__doc__loggingr1rcore.utils.iteratorsrfsm.state_inferencerr5rr getLogger__name__rr&rBr%rKs:/12=   8 $5PpA rJ