Update app.py

xplanation of Gradio's Event Handling:

Gradio uses a declarative approach to define UI elements and their interactions. When you create a component (like a Button) inside a with gr.Column(...) or with gr.Row(...) block, you're essentially adding it to that container's hierarchy. Event handlers (like .click) need to be associated with components within that same hierarchy.

By moving the convert_button.click(...) call inside the with gr.Column(...) block, we ensure that the click event is correctly bound to the convert_button within the Gradio UI structure. This resolves the issue, and the button should now appear and function as expected. This was an issue related to how gradio handles the events, and not related to any of the model conversion, hf hub, or caching.

app.py

@@ -343,18 +343,18 @@ with gr.Blocks(css=css) as demo:
         convert_button = gr.Button("Convert and Upload", elem_id="convert-button")
         output = gr.Markdown()
 
-    convert_button.click(
-        fn=main,
-        inputs=[
-            model_to_load,
-            reference_model,
-            output_path,
-            hf_token,
-            orgs_name,
-            model_name,
-            make_private,
-        ],
-        outputs=output,
-    )
+        convert_button.click( #NOW IT IS INSIDE
+            fn=main,
+            inputs=[
+                model_to_load,
+                reference_model,
+                output_path,
+                hf_token,
+                orgs_name,
+                model_name,
+                make_private,
+            ],
+            outputs=output,
+        )
 
 demo.launch()