abstract-block-dumper 0.0.1__tar.gz → 0.0.4__tar.gz

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/.gitignore

@@ -14,4 +14,5 @@ media/
 .terraform/
 .nox/
 __pycache__
-src/abstract_block_dumper/_version.py
+src/abstract_block_dumper/_version.py
+.gitdo/

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/CHANGELOG.md

@@ -9,6 +9,21 @@ upcoming release can be found in [changelog.d](changelog.d).
 
 <!-- towncrier release notes start -->
 
+## [0.0.4](https://github.com/bactensor/abstract-block-dumper/releases/tag/v0.0.4) - 2025-11-17
+
+No significant changes.
+
+
+## [0.0.5](https://github.com/bactensor/abstract-block-dumper/releases/tag/v0.0.5) - 2025-11-17
+
+No significant changes.
+
+
+## [0.0.2](https://github.com/bactensor/abstract-block-dumper/releases/tag/v0.0.2) - 2025-10-24
+
+No significant changes.
+
+
 ## [0.0.1](https://github.com/bactensor/abstract-block-dumper/releases/tag/v0.0.1) - 2025-10-21
 
 No significant changes.

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstract-block-dumper
-Version: 0.0.1
+Version: 0.0.4
 Project-URL: Source, https://github.com/bactensor/abstract-block-dumper
 Project-URL: Issue Tracker, https://github.com/bactensor/abstract-block-dumper/issues
 Author-email: Reef Technologies <opensource@reef.pl>
@@ -26,6 +26,22 @@ Description-Content-Type: text/markdown
 This package provides a simplified framework for creating block processing tasks in Django applications.
 Define tasks with lambda conditions using the @block_task decorator and run them asynchronously with Celery.
 
+## Usage
+
+> [!IMPORTANT]
+> This package uses [ApiVer](#versioning), make sure to import `abstract_block_dumper.v1`.
+
+
+## Versioning
+
+This package uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+TL;DR you are safe to use [compatible release version specifier](https://packaging.python.org/en/latest/specifications/version-specifiers/#compatible-release) `~=MAJOR.MINOR` in your `pyproject.toml` or `requirements.txt`.
+
+Additionally, this package uses [ApiVer](https://www.youtube.com/watch?v=FgcoAKchPjk) to further reduce the risk of breaking changes.
+This means, the public API of this package is explicitly versioned, e.g. `abstract_block_dumper.v1`, and will not change in a backwards-incompatible way even when `abstract_block_dumper.v2` is released.
+
+Internal packages, i.e. prefixed by `abstract_block_dumper._` do not share these guarantees and may change in a backwards-incompatible way at any time even in patch releases.
+
 ## Implementation Details
 
 ### General Workflow:
@@ -82,6 +98,28 @@ INSTALLED_APPS = [
 python manage.py migrate
 ```
 
+4. **Configure Celery to discover block tasks:**
+
+In your project's `celery.py` file, add the following to ensure Celery workers can discover your `@block_task` decorated functions:
+
+```python
+from celery import Celery
+from celery.signals import worker_ready
+from django.conf import settings
+
+app = Celery('your_project')
+app.config_from_object('django.conf:settings', namespace='CELERY')
+app.autodiscover_tasks()
+
+@worker_ready.connect
+def on_worker_ready(**kwargs):
+    """Load block tasks when worker starts."""
+    from abstract_block_dumper.v1.celery import setup_celery_tasks
+    setup_celery_tasks()
+```
+
+> **Important:** Without this step, Celery workers will not recognize your `@block_task` decorated functions, and you'll see "Received unregistered task" errors.
+
 ## Usage
 
 ### 1. Define Block Processing Tasks
@@ -93,7 +131,7 @@ Create block processing tasks in `tasks.py` or `block_tasks.py` file inside any
 ### 3. Start the Block Scheduler
 Run the scheduler to start processing blocks:
 ```bash
-$ python manage.py block_tasks
+$ python manage.py block_tasks_v1
 ```
 
 This command will:
@@ -112,7 +150,7 @@ See examples below:
 Use the `@block_task` decorator with lambda conditions to create block processing tasks:
 
 ```python
-from abstract_block_dumper.decorators import block_task
+from abstract_block_dumper.v1.decorators import block_task
 
 
 # Process every block
@@ -144,7 +182,7 @@ def process_multi_netuid_task(block_number: int, netuid: int):
 The framework provides a maintenance task to clean up old task records and maintain database performance:
 
 ```python
-from abstract_block_dumper.tasks import cleanup_old_tasks
+from abstract_block_dumper.v1.tasks import cleanup_old_tasks
 
 # Delete tasks older than 7 days (default)
 cleanup_old_tasks.delay()
@@ -160,13 +198,13 @@ This task deletes all succeeded or unrecoverable failed tasks older than the spe
 **Option 1: Manual Execution**
 ```bash
 # Using Django shell
-python manage.py shell -c "from abstract_block_dumper.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
+python manage.py shell -c "from abstract_block_dumper.v1.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
 ```
 
 **Option 2: Cron Job (Recommended - once per day)**
 ```bash
 # Add to crontab (daily at 2 AM)
-0 2 * * * cd /path/to/your/project && python manage.py shell -c "from abstract_block_dumper.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
+0 2 * * * cd /path/to/your/project && python manage.py shell -c "from abstract_block_dumper.v1.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
 ```
 
 **Option 3: Celery Beat (Automated Scheduling)**
@@ -210,55 +248,92 @@ BLOCK_DUMPER_MAX_ATTEMPTS = 3  # maximum retry attempts
 BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 1440  # maximum retry delay (24 hours)
 ```
 
-### Configuration Options Reference
-
-#### Core Settings
-
-**BITTENSOR_NETWORK** (str, default: `'finney'`) Specifies which [Bittensor network](https://docs.learnbittensor.org/concepts/bittensor-networks) to connect to
-
-**BLOCK_DUMPER_START_FROM_BLOCK** (str|int|None, default: `None`)
-- **Purpose**: Determines the starting block for processing when the scheduler first runs
-- **Valid Values**:
-  - `None`: Resume from the last processed block stored in database
-  - `'current'`: Start from the current blockchain block (skips historical blocks)
-  - `int`: Start from a specific block number (e.g., `1000000`)
-- **Example**: `BLOCK_DUMPER_START_FROM_BLOCK = 'current'`
-- **Performance Impact**: Starting from historical blocks may require significant processing time
-
-#### Scheduler Settings
-
-**BLOCK_DUMPER_POLL_INTERVAL** (int, default: `1`)
-- **Purpose**: Seconds to wait between checking for new blocks
-- **Valid Range**: `1` to `3600` (1 second to 1 hour)
-- **Example**: `BLOCK_DUMPER_POLL_INTERVAL = 5`
-- **Performance Impact**:
-  - Lower values (1-2s): Near real-time processing, higher CPU/network usage
-  - Higher values (10-60s): Reduced load but delayed processing
-  - Very low values (<1s) may cause rate limiting
-
-#### Retry and Error Handling Settings
-
-**BLOCK_DUMPER_MAX_ATTEMPTS** (int, default: `3`)
-- **Purpose**: Maximum number of attempts to retry a failed task before giving up
-- **Valid Range**: `1` to `10`
-- **Example**: `BLOCK_DUMPER_MAX_ATTEMPTS = 5`
-- **Performance Impact**: Higher values increase resilience but may delay failure detection
-
-**BLOCK_TASK_RETRY_BACKOFF** (int, default: `1`)
-- **Purpose**: Base number of minutes for exponential backoff retry delays
-- **Valid Range**: `1` to `60`
-- **Example**: `BLOCK_TASK_RETRY_BACKOFF = 2`
-- **Calculation**: Actual delay = `backoff ** attempt_count` minutes
+## Configuration Options Reference
+
+### `BITTENSOR_NETWORK`
+- **Type:** `str`
+- **Default:** `'finney'`
+- **Description:** Specifies which [Bittensor network](https://docs.learnbittensor.org/concepts/bittensor-networks) to connect to
+
+---
+
+### `BLOCK_DUMPER_START_FROM_BLOCK`
+- **Type:** `str | int | None`
+- **Default:** `None`
+- **Valid Range:** `None`, `'current'`, or any positive integer
+- **Description:** Determines the starting block for processing when the scheduler first runs
+  - `None` → Resume from the last processed block stored in database
+  - `'current'` → Start from the current blockchain block (skips historical blocks)
+  - Integer → Start from a specific block number (e.g., `1000000`)
+
+```python
+BLOCK_DUMPER_START_FROM_BLOCK = 'current'
+```
+
+> **Performance Impact:** Starting from historical blocks may require significant processing time
+
+---
+
+### `BLOCK_DUMPER_POLL_INTERVAL`
+- **Type:** `int`
+- **Default:** `1`
+- **Valid Range:** `1` to `3600` (seconds)
+- **Description:** Seconds to wait between checking for new blocks
+
+```python
+BLOCK_DUMPER_POLL_INTERVAL = 5
+```
+
+> **Performance Impact:**
+> - Lower values (1-2s): Near real-time processing, higher CPU/network usage
+> - Higher values (10-60s): Reduced load but delayed processing
+> - Very low values (<1s): May cause rate limiting
+
+---
+
+### `BLOCK_DUMPER_MAX_ATTEMPTS`
+- **Type:** `int`
+- **Default:** `3`
+- **Valid Range:** `1` to `10`
+- **Description:** Maximum number of attempts to retry a failed task before giving up
+
+```python
+BLOCK_DUMPER_MAX_ATTEMPTS = 5
+```
+
+> **Performance Impact:** Higher values increase resilience but may delay failure detection
+
+---
+
+### `BLOCK_TASK_RETRY_BACKOFF`
+- **Type:** `int`
+- **Default:** `1`
+- **Valid Range:** `1` to `60` (minutes)
+- **Description:** Base number of minutes for exponential backoff retry delays
+- **Calculation:** Actual delay = `backoff ** attempt_count` minutes
   - Attempt 1: 2¹ = 2 minutes
-  - Attempt 2: 2² = 4 minutes  
+  - Attempt 2: 2² = 4 minutes
   - Attempt 3: 2³ = 8 minutes
-- **Performance Impact**: Lower values retry faster but may overwhelm failing services
 
-**BLOCK_TASK_MAX_RETRY_DELAY_MINUTES** (int, default: `1440`)
-- **Purpose**: Maximum delay (in minutes) between retry attempts, caps exponential backoff
-- **Valid Range**: `1` to `10080` (1 minute to 1 week)
-- **Example**: `BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 720`  # 12 hours max
-- **Performance Impact**: Prevents extremely long delays while maintaining backoff benefits
+```python
+BLOCK_TASK_RETRY_BACKOFF = 2
+```
+
+> **Performance Impact:** Lower values retry faster but may overwhelm failing services
+
+---
+
+### `BLOCK_TASK_MAX_RETRY_DELAY_MINUTES`
+- **Type:** `int`
+- **Default:** `1440` (24 hours)
+- **Valid Range:** `1` to `10080` (1 minute to 1 week)
+- **Description:** Maximum delay (in minutes) between retry attempts, caps exponential backoff
+
+```python
+BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 720  # 12 hours max
+```
+
+> **Performance Impact:** Prevents extremely long delays while maintaining backoff benefits
 
 
 ## Example Project

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/README.md

@@ -4,6 +4,22 @@
 This package provides a simplified framework for creating block processing tasks in Django applications.
 Define tasks with lambda conditions using the @block_task decorator and run them asynchronously with Celery.
 
+## Usage
+
+> [!IMPORTANT]
+> This package uses [ApiVer](#versioning), make sure to import `abstract_block_dumper.v1`.
+
+
+## Versioning
+
+This package uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+TL;DR you are safe to use [compatible release version specifier](https://packaging.python.org/en/latest/specifications/version-specifiers/#compatible-release) `~=MAJOR.MINOR` in your `pyproject.toml` or `requirements.txt`.
+
+Additionally, this package uses [ApiVer](https://www.youtube.com/watch?v=FgcoAKchPjk) to further reduce the risk of breaking changes.
+This means, the public API of this package is explicitly versioned, e.g. `abstract_block_dumper.v1`, and will not change in a backwards-incompatible way even when `abstract_block_dumper.v2` is released.
+
+Internal packages, i.e. prefixed by `abstract_block_dumper._` do not share these guarantees and may change in a backwards-incompatible way at any time even in patch releases.
+
 ## Implementation Details
 
 ### General Workflow:
@@ -60,6 +76,28 @@ INSTALLED_APPS = [
 python manage.py migrate
 ```
 
+4. **Configure Celery to discover block tasks:**
+
+In your project's `celery.py` file, add the following to ensure Celery workers can discover your `@block_task` decorated functions:
+
+```python
+from celery import Celery
+from celery.signals import worker_ready
+from django.conf import settings
+
+app = Celery('your_project')
+app.config_from_object('django.conf:settings', namespace='CELERY')
+app.autodiscover_tasks()
+
+@worker_ready.connect
+def on_worker_ready(**kwargs):
+    """Load block tasks when worker starts."""
+    from abstract_block_dumper.v1.celery import setup_celery_tasks
+    setup_celery_tasks()
+```
+
+> **Important:** Without this step, Celery workers will not recognize your `@block_task` decorated functions, and you'll see "Received unregistered task" errors.
+
 ## Usage
 
 ### 1. Define Block Processing Tasks
@@ -71,7 +109,7 @@ Create block processing tasks in `tasks.py` or `block_tasks.py` file inside any
 ### 3. Start the Block Scheduler
 Run the scheduler to start processing blocks:
 ```bash
-$ python manage.py block_tasks
+$ python manage.py block_tasks_v1
 ```
 
 This command will:
@@ -90,7 +128,7 @@ See examples below:
 Use the `@block_task` decorator with lambda conditions to create block processing tasks:
 
 ```python
-from abstract_block_dumper.decorators import block_task
+from abstract_block_dumper.v1.decorators import block_task
 
 
 # Process every block
@@ -122,7 +160,7 @@ def process_multi_netuid_task(block_number: int, netuid: int):
 The framework provides a maintenance task to clean up old task records and maintain database performance:
 
 ```python
-from abstract_block_dumper.tasks import cleanup_old_tasks
+from abstract_block_dumper.v1.tasks import cleanup_old_tasks
 
 # Delete tasks older than 7 days (default)
 cleanup_old_tasks.delay()
@@ -138,13 +176,13 @@ This task deletes all succeeded or unrecoverable failed tasks older than the spe
 **Option 1: Manual Execution**
 ```bash
 # Using Django shell
-python manage.py shell -c "from abstract_block_dumper.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
+python manage.py shell -c "from abstract_block_dumper.v1.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
 ```
 
 **Option 2: Cron Job (Recommended - once per day)**
 ```bash
 # Add to crontab (daily at 2 AM)
-0 2 * * * cd /path/to/your/project && python manage.py shell -c "from abstract_block_dumper.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
+0 2 * * * cd /path/to/your/project && python manage.py shell -c "from abstract_block_dumper.v1.tasks import cleanup_old_tasks; cleanup_old_tasks.delay()"
 ```
 
 **Option 3: Celery Beat (Automated Scheduling)**
@@ -188,55 +226,92 @@ BLOCK_DUMPER_MAX_ATTEMPTS = 3  # maximum retry attempts
 BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 1440  # maximum retry delay (24 hours)
 ```
 
-### Configuration Options Reference
-
-#### Core Settings
-
-**BITTENSOR_NETWORK** (str, default: `'finney'`) Specifies which [Bittensor network](https://docs.learnbittensor.org/concepts/bittensor-networks) to connect to
-
-**BLOCK_DUMPER_START_FROM_BLOCK** (str|int|None, default: `None`)
-- **Purpose**: Determines the starting block for processing when the scheduler first runs
-- **Valid Values**:
-  - `None`: Resume from the last processed block stored in database
-  - `'current'`: Start from the current blockchain block (skips historical blocks)
-  - `int`: Start from a specific block number (e.g., `1000000`)
-- **Example**: `BLOCK_DUMPER_START_FROM_BLOCK = 'current'`
-- **Performance Impact**: Starting from historical blocks may require significant processing time
-
-#### Scheduler Settings
-
-**BLOCK_DUMPER_POLL_INTERVAL** (int, default: `1`)
-- **Purpose**: Seconds to wait between checking for new blocks
-- **Valid Range**: `1` to `3600` (1 second to 1 hour)
-- **Example**: `BLOCK_DUMPER_POLL_INTERVAL = 5`
-- **Performance Impact**:
-  - Lower values (1-2s): Near real-time processing, higher CPU/network usage
-  - Higher values (10-60s): Reduced load but delayed processing
-  - Very low values (<1s) may cause rate limiting
-
-#### Retry and Error Handling Settings
-
-**BLOCK_DUMPER_MAX_ATTEMPTS** (int, default: `3`)
-- **Purpose**: Maximum number of attempts to retry a failed task before giving up
-- **Valid Range**: `1` to `10`
-- **Example**: `BLOCK_DUMPER_MAX_ATTEMPTS = 5`
-- **Performance Impact**: Higher values increase resilience but may delay failure detection
-
-**BLOCK_TASK_RETRY_BACKOFF** (int, default: `1`)
-- **Purpose**: Base number of minutes for exponential backoff retry delays
-- **Valid Range**: `1` to `60`
-- **Example**: `BLOCK_TASK_RETRY_BACKOFF = 2`
-- **Calculation**: Actual delay = `backoff ** attempt_count` minutes
+## Configuration Options Reference
+
+### `BITTENSOR_NETWORK`
+- **Type:** `str`
+- **Default:** `'finney'`
+- **Description:** Specifies which [Bittensor network](https://docs.learnbittensor.org/concepts/bittensor-networks) to connect to
+
+---
+
+### `BLOCK_DUMPER_START_FROM_BLOCK`
+- **Type:** `str | int | None`
+- **Default:** `None`
+- **Valid Range:** `None`, `'current'`, or any positive integer
+- **Description:** Determines the starting block for processing when the scheduler first runs
+  - `None` → Resume from the last processed block stored in database
+  - `'current'` → Start from the current blockchain block (skips historical blocks)
+  - Integer → Start from a specific block number (e.g., `1000000`)
+
+```python
+BLOCK_DUMPER_START_FROM_BLOCK = 'current'
+```
+
+> **Performance Impact:** Starting from historical blocks may require significant processing time
+
+---
+
+### `BLOCK_DUMPER_POLL_INTERVAL`
+- **Type:** `int`
+- **Default:** `1`
+- **Valid Range:** `1` to `3600` (seconds)
+- **Description:** Seconds to wait between checking for new blocks
+
+```python
+BLOCK_DUMPER_POLL_INTERVAL = 5
+```
+
+> **Performance Impact:**
+> - Lower values (1-2s): Near real-time processing, higher CPU/network usage
+> - Higher values (10-60s): Reduced load but delayed processing
+> - Very low values (<1s): May cause rate limiting
+
+---
+
+### `BLOCK_DUMPER_MAX_ATTEMPTS`
+- **Type:** `int`
+- **Default:** `3`
+- **Valid Range:** `1` to `10`
+- **Description:** Maximum number of attempts to retry a failed task before giving up
+
+```python
+BLOCK_DUMPER_MAX_ATTEMPTS = 5
+```
+
+> **Performance Impact:** Higher values increase resilience but may delay failure detection
+
+---
+
+### `BLOCK_TASK_RETRY_BACKOFF`
+- **Type:** `int`
+- **Default:** `1`
+- **Valid Range:** `1` to `60` (minutes)
+- **Description:** Base number of minutes for exponential backoff retry delays
+- **Calculation:** Actual delay = `backoff ** attempt_count` minutes
   - Attempt 1: 2¹ = 2 minutes
-  - Attempt 2: 2² = 4 minutes  
+  - Attempt 2: 2² = 4 minutes
   - Attempt 3: 2³ = 8 minutes
-- **Performance Impact**: Lower values retry faster but may overwhelm failing services
 
-**BLOCK_TASK_MAX_RETRY_DELAY_MINUTES** (int, default: `1440`)
-- **Purpose**: Maximum delay (in minutes) between retry attempts, caps exponential backoff
-- **Valid Range**: `1` to `10080` (1 minute to 1 week)
-- **Example**: `BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 720`  # 12 hours max
-- **Performance Impact**: Prevents extremely long delays while maintaining backoff benefits
+```python
+BLOCK_TASK_RETRY_BACKOFF = 2
+```
+
+> **Performance Impact:** Lower values retry faster but may overwhelm failing services
+
+---
+
+### `BLOCK_TASK_MAX_RETRY_DELAY_MINUTES`
+- **Type:** `int`
+- **Default:** `1440` (24 hours)
+- **Valid Range:** `1` to `10080` (1 minute to 1 week)
+- **Description:** Maximum delay (in minutes) between retry attempts, caps exponential backoff
+
+```python
+BLOCK_TASK_MAX_RETRY_DELAY_MINUTES = 720  # 12 hours max
+```
+
+> **Performance Impact:** Prevents extremely long delays while maintaining backoff benefits
 
 
 ## Example Project

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/example_project/README.md

@@ -15,5 +15,5 @@ docker-compose up --build
 2. Access the Django admin interface at `http://localhost:8000/admin` with username `admin` and password `admin` (automatically created).
 3. Start the block dumper scheduler:
 ```bash
-docker-compose exec web python manage.py block_tasks
+docker-compose exec web python manage.py block_tasks_v1
 ```

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/example_project/block_explorer/tasks.py

@@ -1,4 +1,4 @@
-from abstract_block_dumper.decorators import block_task
+from abstract_block_dumper.v1.decorators import block_task
 
 
 @block_task(

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/example_project/docker-compose.yml

@@ -69,7 +69,7 @@ services:
     build:
       context: ..
       dockerfile: example_project/Dockerfile
-    command: uv run python manage.py block_tasks
+    command: uv run python manage.py block_tasks_v1
     volumes:
       - .:/app/example_project
       - ../src:/app/src

abstract_block_dumper-0.0.4/example_project/example_project/celery.py

@@ -0,0 +1,26 @@
+import os
+
+from celery import Celery
+from celery.signals import worker_ready
+from django.conf import settings
+
+os.environ.setdefault("DJANGO_SETTINGS_MODULE", "example_project.settings")
+
+app = Celery("example_project")
+
+app.config_from_object(settings, namespace="CELERY")
+
+app.autodiscover_tasks(lambda: settings.INSTALLED_APPS)
+
+
+@worker_ready.connect
+def on_worker_ready(**kwargs):
+    """
+    Load block tasks when Celery worker starts.
+
+    This is required for abstract-block-dumper to register @block_task
+    decorated functions so they can receive messages from the broker.
+    """
+    from abstract_block_dumper.v1.celery import setup_celery_tasks
+
+    setup_celery_tasks()

{abstract_block_dumper-0.0.1 → abstract_block_dumper-0.0.4}/example_project/example_project/settings.py

@@ -3,6 +3,7 @@ import sys
 from pathlib import Path
 
 import dj_database_url  # type: ignore
+from celery.schedules import crontab
 
 # Build paths inside the project like this: BASE_DIR / 'subdir'.
 BASE_DIR = Path(__file__).resolve().parent.parent
@@ -133,3 +134,12 @@ BLOCK_DUMPER_POLL_INTERVAL = 1  # seconds - ultra-fast polling for real-time pro
 BLOCK_DUMPER_START_FROM_BLOCK = "current"  # None = resume from DB, 'current' = current block, or block number
 BLOCK_TASK_RETRY_BACKOFF = 2
 BLOCK_DUMPER_MAX_ATTEMPTS = 3
+
+
+CELERY_BEAT_SCHEDULE = {
+    "cleanup-old-tasks": {
+        "task": "abstract_block_dumper.cleanup_old_tasks",
+        "schedule": crontab(hour=2, minute=0),  # Daily at 2 AM
+        "kwargs": {"days": 7},  # Customize retention period
+    },
+}

{abstract_block_dumper-0.0.1/src/abstract_block_dumper → abstract_block_dumper-0.0.4/src/abstract_block_dumper/_internal}/dal/django_dal.py

@@ -6,8 +6,8 @@ from django.db import transaction
 from django.db.models.query import QuerySet
 from django.utils import timezone
 
+import abstract_block_dumper._internal.services.utils as abd_utils
 import abstract_block_dumper.models as abd_models
-import abstract_block_dumper.services.utils as abd_utils
 
 
 def get_ready_to_retry_attempts() -> QuerySet[abd_models.TaskAttempt]:
@@ -76,7 +76,7 @@ def task_mark_as_success(task: abd_models.TaskAttempt, result_data: dict) -> Non
     task.save()
 
 
-def task_mark_as_failed(task) -> None:
+def task_mark_as_failed(task: abd_models.TaskAttempt) -> None:
     DEFAULT_BLOCK_TASK_RETRY_BACKOFF = 1
     MAX_RETRY_DELAY_MINUTES = 1440  # 24 hours max delay
 
@@ -98,7 +98,7 @@ def task_mark_as_failed(task) -> None:
     task.save()
 
 
-def task_schedule_to_retry(task):
+def task_schedule_to_retry(task: abd_models.TaskAttempt) -> None:
     task.status = abd_models.TaskAttempt.Status.PENDING
     task.save()
 
@@ -110,6 +110,7 @@ def task_create_or_get_pending(
 ) -> tuple[abd_models.TaskAttempt, bool]:
     """
     Create or get a pending task attempt.
+
     Returns (task, created) where created indicates if a new task was created.
 
     For failed tasks that can retry: