chore: update workflows to fix multiple workflow failures

Working on test suite to fix testing issues.

Author: mobious999

.coveragerc

@@ -3,12 +3,13 @@ branch = True
 source = src
 
 [report]
-show_missing = true
-skip_covered = true
+show_missing = True
+skip_covered = True
+fail_under = 80
 exclude_lines =
     pragma: no cover
-    if __name__ == .__main__.:
+    if __name__ == '__main__':
 
 [html]
 directory = htmlcov
-show_contexts = true
+show_contexts = True

.github/workflows/Auto Rebase Dependabot Pull Requests.yml

@@ -0,0 +1,20 @@
+---
+name: 🏷️ Label Dependabot PRs for Auto-Rebase
+on:
+  pull_request:
+    types: [opened, reopened]
+jobs:
+  label-dependabot:
+    if: github.actor == 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add autorebase label
+        uses: actions/github-script@v7
+        with:
+          script: |-
+            github.rest.issues.addLabels({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              labels: ['autorebase']
+            })

.github/workflows/Auto Rebase Pull Requests.yml

@@ -1,13 +1,17 @@
 ---
 name: 🔁 Auto Rebase Pull Requests
 on:
-  schedule:
-    - cron: 0 5 * * *
+  pull_request_target:
+    types: [labeled, synchronize]
+permissions:
+  contents: write
+  pull-requests: write
 jobs:
   rebase:
+    if: contains(github.event.pull_request.labels.*.name, 'autorebase')
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: cirrus-actions/[email protected]  
+      - name: Auto Rebase PR
+        uses: cirrus-actions/[email protected]
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/Build and Push Docker Image.yml

@@ -43,13 +43,15 @@ jobs:
             --tag ghcr.io/${{ github.repository }}:${{ github.sha }} \
             --tag ghcr.io/${{ github.repository }}:${{ env.VERSION }} \
             .
+      - name: 📥 Install Syft CLI
+        run: |
+          curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s -- -b /usr/local/bin
       - name: 📜 Generate SBOM for Docker Image
         run: |
-          pip install syft==0.98.0
           syft ghcr.io/${{ github.repository }}:${{ env.VERSION }} -o cyclonedx-json > sbom.image.json
       - name: 🧾 Get Image Digest
         run: |
-          IMAGE_DIGEST=$(syft ghcr.io/${{ github.repository }}:${{ env.VERSION }} -o json | jq -r '.artifacts[0].digest')
+          IMAGE_DIGEST=$(syft ghcr.io/${{ github.repository }}:${{ env.VERSION }} -o json | jq -r '.descriptor.digest')
           echo "IMAGE_DIGEST=$IMAGE_DIGEST" >> $GITHUB_ENV
       - name: 📤 Upload SBOM
         uses: actions/upload-artifact@v4

.github/workflows/Code Coverage.yml

@@ -14,4 +14,4 @@ jobs:
           python-version: '3.11'
       - run: pip install -e .[dev]
       - run: pytest --cov=src --cov-report=xml
-      - uses: codecov/codecov-action@v4
+      - uses: codecov/codecov-action@v5

.github/workflows/GitHub Workflow Lint.yml

@@ -9,7 +9,7 @@ jobs:
         with:
           fetch-depth: 0  # ✅ Fix for Super Linter SHA access
       - name: Super Linter
-        uses: github/super-linter@v6
+        uses: github/super-linter@v7
         env:
           VALIDATE_ALL_CODEBASE: false
           VALIDATE_YAML: true

.github/workflows/Python Matrix Test.yml

@@ -4,13 +4,17 @@ on: [push, pull_request]
 jobs:
   test:
     runs-on: ubuntu-latest
+    timeout-minutes: 20  # ⏲️ Fail fast if something hangs too long
     strategy:
+      max-parallel: 2  # 🚦 Prevent all matrix jobs running simultaneously
       matrix:
         python-version: ['3.9', '3.10', '3.11', '3.12']
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
-      - run: pip install -e .[dev]
-      - run: pytest
+      - name: Install dependencies
+        run: pip install -e .[dev]
+      - name: Run tests
+        run: pytest --maxfail=3 --disable-warnings --durations=10

.github/workflows/ci-experiments/ci-failure-notifications-split.yml

@@ -16,7 +16,7 @@ jobs:
     steps:
       - name: Notify Slack
         if: env.SLACK_WEBHOOK_URL != ''
-        uses: slackapi/slack-github-action@v1.24.0
+        uses: slackapi/slack-github-action@v2.1.1
         with:
           payload: |
             {

.gitignore

@@ -60,11 +60,17 @@ cover/
 local_settings.py
 db.sqlite3
 db.sqlite3-journal
+*.sqlite*
+*.db
 
 # Flask stuff:
 instance/
 .webassets-cache
 
+#Ignore SBOM artifacts
+sbom*.json
+bom.json
+
 # Scrapy stuff:
 .scrapy
 
@@ -82,6 +88,9 @@ target/
 profile_default/
 ipython_config.py
 
+#log files
+sync.log
+
 # pyenv
 #   For a library or package, you might want to ignore these files since the code is
 #   intended to run in multiple environments; otherwise, check them in:
@@ -92,18 +101,18 @@ ipython_config.py
 #   However, in case of collaboration, if having platform-specific dependencies or dependencies
 #   having no cross-platform support, pipenv may install dependencies that don't work, or not
 #   install all needed dependencies.
-#Pipfile.lock
+Pipfile.lock
 
 # poetry
 #   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
 #   This is especially recommended for binary packages to ensure reproducibility, and is more
 #   commonly ignored for libraries.
 #   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-#poetry.lock
+poetry.lock
 
 # pdm
 #   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#pdm.lock
+pdm.lock
 #   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
 #   in version control.
 #   https://pdm.fming.dev/latest/usage/project/#working-with-version-control

CONTRIBUTING.MD

@@ -14,7 +14,8 @@ We use github to host code, to track issues and feature requests, as well as acc
 
 ## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
 
-Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+Pull requests are the best way to propose changes to the codebase (we use
+[Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `master`.
 2. If you've added code that should be tested, add tests.
@@ -25,22 +26,27 @@ Pull requests are the best way to propose changes to the codebase (we use [Githu
 
 ## Any contributions you make will be under the MIT Software License
 
-In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+In short, when you submit code changes, your submissions are understood to be under the same
+[MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if
+that's a concern.
 
 ## Report bugs using Github's [issues](https://github.com/briandk/transcriptase-atom/issues)
 
 We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
 
 ## Write bug reports with detail, background, and sample code
 
-[This is an example](http://stackoverflow.com/q/12488905/180626) of a bug report I wrote, and I think it's not a bad model. Here's [another example from Craig Hockenberry](http://www.openradar.me/11905408), an app developer whom I greatly respect.
+[This is an example](http://stackoverflow.com/q/12488905/180626) of a bug report I wrote, and I think it's not a bad
+model. Here's [another example from Craig Hockenberry](http://www.openradar.me/11905408), an app developer whom I
+greatly respect.
 
 **Great Bug Reports** tend to have:
 
 - A quick summary and/or background
 - Steps to reproduce
   - Be specific!
-  - Give sample code if you can. [My stackoverflow question](http://stackoverflow.com/q/12488905/180626) includes sample code that _anyone_ with a base R setup can run to reproduce what I was seeing
+  - Give sample code if you can. [My stackoverflow question](http://stackoverflow.com/q/12488905/180626) includes sample
+    code that _anyone_ with a base R setup can run to reproduce what I was seeing
 - What you expected would happen
 - What actually happens
 - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
@@ -49,7 +55,8 @@ People _love_ thorough bug reports. I'm not even kidding.
 
 ## Use a Consistent Coding Style
 
-I'm again borrowing these from [Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+I'm again borrowing these from
+[Facebook's Guidelines](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
 
 - 2 spaces for indentation rather than tabs
 - You can try running `npm run lint` for style unification
@@ -60,4 +67,5 @@ By contributing, you agree that your contributions will be licensed under its MI
 
 ## References
 
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+This document was adapted from the open-source contribution guidelines for
+[Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)