Update Consumer.py

Consumer.py

@@ -49,9 +49,9 @@ def stopall():
     #global active_tasks
     count = 0
     for uid in list(active_tasks.keys()):
-        if active_tasks != asyncio.current_task():
-        stop(uid)
-        count += 1
+        if active_tasks[uid] != asyncio.current_task():
+            stop(uid)
+            count += 1
     try:
         # Check if an event loop is already running
         try:
@@ -85,8 +85,8 @@ def execute_code_sync(code, uid):
     
     # Inject stop functions into locals
     local_scope = locals()
-    local_scope['stop'] = stop
-    local_scope['stopall'] = stopall
+    #local_scope['stop'] = stop
+    #local_scope['stopall'] = stopall
 
     try:
         with contextlib.redirect_stdout(stdout_capture):
@@ -107,22 +107,7 @@ async def process_task(uid, code):
     print(f"Processing {uid}...")
     
     try:
-        # Initial status update to 'wait' (meaning it's running/waiting for completion)
-        # Note: 'processing' is set by API when polled, but if it's long running, 'wait' might be better for UI feedback?
-        # The user requested 'wait' status.
-        # However, update_server moves it to log. We might not want to move it to log yet if it's running?
-        # But our API design moves to log on update.
-        # For true async status updates while running, we'd need a separate 'running' table or update the queue table.
-        # Given current API, 'update' moves to log. So we can't really set intermediate status easily without API changes.
-        # BUT, the request said: "assigning each exec to its uid async wait loop and returning status 'wait'".
-        # This implies immediate return.
-        
-        # Let's interpret: The Python loop should likely NOT block.
-        # Setting status to "wait" immediately via update_server would move it to log, effectively "finishing" it from queue perspective.
-        # If the user wants to see it "waiting" in UI, moving to log with status 'wait' is one way.
-        # But then how do we update it again when it finishes? The log table has unique UID? 
-        # API: INSERT ... ON DUPLICATE KEY UPDATE. So we CAN update log entries.
-        
+        # API: INSERT ... ON DUPLICATE KEY UPDATE. So we CAN update log entries.    
         # Step 1: Set status to 'wait'
         update_server(uid, "Execution started...", "wait")