Uname:Linux antigravity-cli 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64

Base Dir : /var/www/moonbloom

User : wp-moonbloom


403WebShell
403Webshell
Server IP : 85.155.190.233  /  Your IP : 216.73.216.103
Web Server : nginx/1.24.0
System : Linux antigravity-cli 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64
User : wp-moonbloom ( 1001)
PHP Version : 8.3.6
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : OFF
Directory :  /opt/Gemini_Swarm_Core/specs/diagnostics/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /opt/Gemini_Swarm_Core/specs/diagnostics/fix_scheduler_reset_spec.md
# Specification: Fix Scheduler Reset on Startup

## Context
During service restart (e.g. during deployment), the database initialization logic in `scripts/tg_bridge.py` resets the `active` status of the `wordpress_blog_writer` task to `0`. This causes the blog writer scheduler to skip execution on subsequent nights. We need to preserve the user-configured `active` status across service restarts.

## Proposed Changes

### `scripts/tg_bridge.py`
Remove the hardcoded update query that resets `active = 0` for `wordpress_blog_writer`.
Specifically:
```python
        await db.execute("""
            UPDATE swarm_tasks 
            SET active = 0 
            WHERE task_name = 'wordpress_blog_writer'
        """)
```
This block should be completely removed, allowing the `INSERT OR IGNORE` to set the initial value (or the user-configured value to persist).

## Verification
- Run tests (or check parsing).
- Ensure DB initialization does not run `UPDATE swarm_tasks SET active = 0 WHERE task_name = 'wordpress_blog_writer'`.

Youez - 2016 - github.com/yon3zu
LinuXploit