Dont put #no_uv in requirements.in

Instead postfix hash for requirements.in with `-no_uv`

Author: pyranota

backend/windmill-worker/src/python_executor.rs

@@ -114,7 +114,7 @@ pub async fn uv_pip_compile(
     let mut logs = String::new();
     logs.push_str(&format!("\nresolving dependencies..."));
     logs.push_str(&format!("\ncontent of requirements:\n{}\n", requirements));
-    let mut requirements = if let Some(pip_local_dependencies) =
+    let requirements = if let Some(pip_local_dependencies) =
         WORKER_CONFIG.read().await.pip_local_dependencies.as_ref()
     {
         let deps = pip_local_dependencies.clone();
@@ -144,17 +144,20 @@ pub async fn uv_pip_compile(
     };
 
     #[cfg(feature = "enterprise")]
-    {
-        requirements = replace_pip_secret(db, w_id, &requirements, worker_name, job_id).await?;
-    }
+    let requirements = replace_pip_secret(db, w_id, &requirements, worker_name, job_id).await?;
+
+    let mut req_hash = format!("py-{}", calculate_hash(&requirements));
 
     if no_uv || *USE_PIP_COMPILE {
+        // Set no_uv if not setted
         no_uv = true;
-        // We want to make sure that when we specify `no_uv` lockfile will be resolved again
-        requirements.push_str("\n#no_uv");
+        // Make sure that if we put #no_uv (switch to pip-compile) to python code or used `USE_PIP_COMPILE=true` variable.
+        // Windmill will recalculate lockfile using pip-compile and dont take potentially broken lockfile (generated by uv) from cache (our db).
+        // It will recalculate lockfile even if inputs have not been changed.
+        req_hash.push_str("-no_uv");
+        // Will be in format:
+        //     py-000..000-no_uv
     }
-
-    let req_hash = format!("py-{}", calculate_hash(&requirements));
     if !no_cache {
         if let Some(cached) = sqlx::query_scalar!(
             "SELECT lockfile FROM pip_resolution_cache WHERE hash = $1",