Files
context-paging/output/turn_028.json
2026-03-28 09:01:07 +00:00

2 lines
3.9 KiB
JSON

{"id":"chatcmpl-84f4a485a9114f58","object":"chat.completion","created":1774197335,"model":"NousResearch\/Hermes-3-Llama-3.2-3B","choices":[{"index":0,"message":{"role":"assistant","content":"Here is the exact time tracking implementation from earlier:\n\n```python\nimport os\nimport json\nfrom datetime import datetime\n\ndef start_tracking(task_id):\n with open('.taskman_running', 'w') as f:\n json.dump({'task_id': task_id, 'started_at': datetime.now()}, f)\n\ndef stop_tracking():\n if os.path.exists('.taskman_running'):\n with open('.taskman_running', 'r') as f:\n data = json.load(f)\n task_id = data['task_id']\n started_at = data['started_at']\n duration = (datetime.now() - started_at).total_seconds()\n task = next((task for task in task_manager.tasks if task.id == task_id), None)\n if task:\n task.time_spent = task.time_spent + int(duration * 60) # Convert seconds to minutes\n task_manager.save_to_file('.taskman_running')\n task_manager.save_to_file('tasks.json')\n```\n\nThe .taskman_running file had the following format:\n\n```json\n{\n \"task_id\": \"task_id\",\n \"started_at\": \"datetime\"\n}\n```\n\nThe start_tracking function writes the currently running task ID to the .taskman_running file. The stop_tracking function reads the task ID and started_at from the .taskman_running file, calculates the duration of the time spent, updates the task's time_spent field in the database, and writes the updated task to the .taskman_running file.\n\nTo migrate this logic to use the database instead, you can modify the start_tracking and stop_tracking functions as follows:\n\n```python\ndef start_tracking(task_id):\n user_id = get_jwt_identity()\n task = Task.query.filter_by(id=task_id, assigned_to=user_id).first()\n if task:\n task.time_spent = 0 # Reset time spent when a new task starts\n db.session.commit()\n socketio.emit('task_updated', {'task': task.to_dict()}, broadcast=True)\n\ndef stop_tracking():\n user_id = get_jwt_identity()\n task_id = request.args.get('task_id')\n task = Task.query.filter_by(id=task_id, assigned_to=user_id).first()\n if task:\n data = request.get_json()\n duration = data['duration']\n task.time_spent = task.time_spent + int(duration * 60) # Convert seconds to minutes\n db.session.commit()\n socketio.emit('task_updated', {'task': task.to_dict()}, broadcast=True)\n```\n\nIn the start_tracking function, we first get the user ID using `get_jwt_identity()`. Then, we filter the task from the database using the provided task ID and user ID. If the task is found, we reset its time_spent to 0 and emit the 'task_updated' event to update the client.\n\nIn the stop_tracking function, we first get the task ID from the request arguments. Then, we filter the task from the database using the task ID and user ID. If the task is found, we parse the duration from the JSON data and update its time_spent field in the database. Finally, we emit the 'task_updated' event to update the client.\n\nBy modifying the time tracking logic to use the database and emitting the 'task_updated' event, we can keep backward compatibility with any existing .taskman_running files. When a client starts tracking a task, it will write the task ID to the .taskman_running file. When the client stops tracking, it will send a request to the API with the task ID and duration, and the API will update the task's time_spent field in the database and emit the 'task_updated' event to update the client.","refusal":null,"annotations":null,"audio":null,"function_call":null,"tool_calls":[],"reasoning":null},"logprobs":null,"finish_reason":"stop","token_ids":null}],"service_tier":null,"system_fingerprint":null,"usage":{"prompt_tokens":27413,"total_tokens":28178,"completion_tokens":765,"prompt_tokens_details":null},"prompt_token_ids":null,"kv_transfer_params":null}