blocks-genesis 0.3.1__tar.gz

blocks_genesis-0.3.1/.github/actions/install-dependencies/action.yml

@@ -0,0 +1,18 @@
+name: Install dependencies
+description: Installs dependencies for the python project
+
+runs:
+  using: "composite"
+  steps:
+    - name: Install uv
+      uses: astral-sh/setup-uv@v3
+      with:
+        # Install a specific version of uv.
+        version: "0.5.26"
+        enable-cache: true
+        cache-dependency-glob: "uv.lock"
+
+    - name: Install dependencies
+      shell: bash
+      run: |
+        uv sync

blocks_genesis-0.3.1/.github/actions/setvars/action.yml

@@ -0,0 +1,13 @@
+name: 'Set environment variables'
+description: 'Configures environment variables for a workflow'
+inputs:
+  varFilePath:
+    description: 'File path to variable file or directory. Defaults to ./.github/variables/* if none specified and runs against each file in that directory.'
+    required: false
+    default: ./.github/variables/*
+runs:
+  using: "composite"
+  steps:
+    - run: |
+        sed "" ${{ inputs.varFilePath }} >> $GITHUB_ENV
+      shell: bash

blocks_genesis-0.3.1/.github/variables/vars.env

@@ -0,0 +1,4 @@
+SONARQUBE_HOST=https://code.selise.biz
+AUTHOR=seliseblocks
+REPO_NAME=blocks-genesis-py
+SONAR_KEY=SELISEdigitalplatforms_blocks-genesis-py_c3d4471b-e585-48c9-950c-d3ee10ba4175

blocks_genesis-0.3.1/.github/workflows/2_sonar.yml

@@ -0,0 +1,65 @@
+name: Analyze Code Quality
+
+on: 
+  workflow_call:
+    secrets:
+      SONAR_TOKEN:
+        required: true
+
+jobs:
+  build:
+    name: SonarQube Analysis
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Set Environment Variables
+        uses: ./.github/actions/setvars
+        with:
+          varFilePath: ./.github/variables/vars.env
+
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'
+
+      - name: Set up JDK 17
+        uses: actions/setup-java@v1
+        with:
+          java-version: "17"
+
+      - name: Cache SonarQube packages
+        uses: actions/cache@v4
+        with:
+          path: ~/.sonar/cache
+          key: ${{ runner.os }}-sonar
+          restore-keys: |
+            ${{ runner.os }}-sonar
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest pytest-cov pytest-asyncio
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+          if [ -f pyproject.toml ]; then pip install .; fi
+
+      - name: Run tests with coverage
+        continue-on-error: true
+        run: |
+          python -m pytest --asyncio-mode=auto --cov=. --cov-report=xml
+
+      - uses: sonarsource/sonarqube-scan-action@master
+        env:
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+          SONAR_HOST_URL: ${{ env.SONARQUBE_HOST }}
+
+      # - name: SonarQube Quality Gate check
+      #   uses: sonarsource/sonarqube-quality-gate-action@master
+      #   # Force to fail step after specific time.
+      #   timeout-minutes: 5
+      #   env:
+      #     SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+      #     SONAR_HOST_URL: ${{ env.SONARQUBE_HOST }}

blocks_genesis-0.3.1/.github/workflows/dev.yml

@@ -0,0 +1,34 @@
+name: sonarqube analysis
+
+on:
+  push:
+    branches:
+      - dev
+      - sonar
+      - main
+  pull_request:
+    branches:
+      - dev
+      - sonar
+      - main
+
+env:
+  RUN_SONARQUBE: "true"
+
+jobs:
+  initialization:
+    runs-on: ubuntu-latest
+    outputs:
+      envvalue1: ${{ steps.setvar.outputs.envvar1 }}
+    steps:
+      - name: set value
+        id: setvar
+        run: |
+          echo "::set-output name=envvar1::$RUN_SONARQUBE"
+
+  sonarqube-job:
+    if: ${{ success() && needs.initialization.outputs.envvalue1=='true' }}
+    uses: ./.github/workflows/2_sonar.yml
+    secrets:
+      SONAR_TOKEN: ${{ secrets.SONAR_TOKEN_GLOBAL }}
+    needs: [initialization]

blocks_genesis-0.3.1/.github/workflows/release.yml

@@ -0,0 +1,62 @@
+name: Publish package to PyPI
+
+on:
+  push:
+    branches:
+      - inception
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out release source
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event_name == 'release' && github.event.release.tag_name || github.ref }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11" 
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Build distribution packages
+        run: uv build
+
+      - name: Verify distribution metadata
+        run: uv tool run twine check dist/*
+
+      - name: Upload distribution packages
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish-to-pypi:
+    name: Publish distribution
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download distribution packages
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish package to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+

blocks_genesis-0.3.1/.github/workflows/repo-hygiene.yml

@@ -0,0 +1,16 @@
+name: repo-hygiene
+on:
+  push:
+    branches: [inception]
+  pull_request:
+    branches: [inception]
+jobs:
+  repo-hygiene:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: no stray markdown or AI artifacts
+        run: |
+          badmd=$(git ls-files '*.md' | grep -vE '(^|/)(README|LICENSE|CONTRIBUTING|SECURITY|CODE_OF_CONDUCT)\.md$' || true)
+          badai=$(git ls-files | grep -iE '(^|/)(\.claude|\.cursor|\.codex|\.hermes|\.aider|\.windsurf|\.gemini|\.kiro|\.trae|graphify-out)(/|$)|(^|/)(\.cursorrules|\.mcp\.json|copilot-instructions\.md)$' || true)
+          if [ -n "$badmd$badai" ]; then echo "Policy violations:"; echo "$badmd"; echo "$badai"; exit 1; fi

blocks_genesis-0.3.1/.gitignore

@@ -0,0 +1,79 @@
+# Python
+__pycache__/
+*.pyc
+*.pyd
+*.pyo
+.Python
+env/
+.env
+venv/
+lib/
+include/
+bin/
+share/
+logs/
+*.log
+.pytest_cache/
+.coverage
+htmlcov/
+.nox/
+.tox/
+dist/
+build/
+*.egg-infol
+*.egg
+.mypy_cache/
+.ruff_cache/
+.vscode/
+
+# IDEs
+.idea/
+*.iml
+*.iws
+*.ipr
+
+# OS generated files
+.DS_Store
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# FastAPI specific
+# If you have an sqlite database file
+*.db
+
+# Docker
+# If you are using Docker, you might want to ignore these
+# .dockerignore should handle what goes into the image, but these are for local dev
+# .docker/
+# docker-compose.yml (if you have local-only modifications)
+
+# Environment variables (if you have a .env file outside of your venv)
+.env
+
+
+# --- AI assistant artifacts: never track ---
+.claude/
+.cursor/
+.codex/
+.hermes/
+.aider*
+.windsurf/
+.gemini/
+.kiro/
+.trae/
+graphify-out/
+CLAUDE.md
+GEMINI.md
+AGENTS.md
+.cursorrules
+.mcp.json
+copilot-instructions.md
+
+# --- markdown policy: only standard docs tracked ---
+*.md
+!README.md
+!LICENSE.md
+!CONTRIBUTING.md
+!SECURITY.md
+!CODE_OF_CONDUCT.md

blocks_genesis-0.3.1/.python-version

@@ -0,0 +1 @@
+3.12

blocks_genesis-0.3.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,228 @@
+# Code of Conduct
+
+## Our Commitment
+
+We are committed to providing a welcoming, respectful, and inclusive environment for all contributors and community members of the **blocks-genesis-py** project. As maintainers, contributors, and participants, we pledge to make collaboration within our community a harassment-free, inclusive experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, socioeconomic status, sexual identity and orientation, or any other dimension of identity.
+
+We recognize that a healthy community requires mutual respect, open dialogue, and accountability. This Code of Conduct establishes clear expectations for participation and ensures that everyone can contribute safely and meaningfully.
+
+## Expected Behavior
+
+We encourage all community members to:
+
+### Professional Communication
+- Use welcoming, inclusive, and respectful language
+- Avoid jargon or explain technical terms to ensure accessibility
+- Communicate clearly and thoughtfully in both written and verbal interactions
+
+### Collaborative Attitude
+- Respect differing viewpoints, experiences, and expertise
+- Listen actively and seek to understand other perspectives
+- Provide and receive constructive criticism with grace and humility
+- Focus on the quality of ideas rather than personalities or backgrounds
+
+### Community Focus
+- Prioritize what is best for the project and community
+- Be patient with newcomers and help them get oriented
+- Share knowledge generously and mentor less experienced contributors
+- Celebrate successes and acknowledge contributions from others
+
+### Inclusivity and Accessibility
+- Use inclusive language and avoid assumptions about backgrounds or experiences
+- Make efforts to ensure discussions are accessible to participants with different abilities
+- Be mindful of time zone differences and varied work schedules
+- Welcome contributions in different forms (code, documentation, design, testing, etc.)
+
+### Professional Conduct
+- Keep discussions focused on the project and community matters
+- Maintain professionalism even during disagreements
+- Respect confidentiality and privacy of others
+- Avoid cross-posting or multi-threading discussions unnecessarily
+
+## Unacceptable Behavior
+
+The following behaviors are unacceptable and will not be tolerated in community spaces:
+
+### Harassment and Abuse
+- Deliberate intimidation, threats, or harassment
+- Unwanted or inappropriate personal comments
+- Sustained disruption or derailment of discussions
+- Targeted campaigns against individuals or groups
+
+### Discriminatory Conduct
+- Slurs, stereotypes, or discriminatory remarks based on protected characteristics
+- Exclusionary language or gatekeeping based on identity
+- Questioning someone's right to participate based on identity or background
+- Microaggressions or invalidation of others' experiences
+
+### Sexual Harassment and Misconduct
+- Unwelcome sexual comments, advances, or requests
+- Sexualized language, imagery, or references
+- Non-consensual physical contact or invasion of personal space
+- Sexual jokes or innuendos in professional settings
+
+### Harmful Content and Privacy Violations
+- Publishing or threatening to publish others' private information without consent
+- Sharing confidential project or personal information
+- Doxxing or any attempt to identify or locate someone without consent
+- Sharing explicit, violent, or otherwise harmful content
+
+### Bad Faith Participation
+- Trolling, deliberately provocative posts, or bad faith arguments
+- Spam, self-promotion, or off-topic solicitation
+- Impersonation or misrepresentation of identity or affiliation
+- Coordinated inauthentic behavior or vote manipulation
+
+### Retaliation
+- Retaliatory action against someone for reporting a violation or participating in an investigation
+- Threatening or intimidating those who raise concerns
+- Exclusion or marginalization of someone for speaking up
+
+## Our Responsibilities
+
+### Maintainers' Obligations
+
+Project maintainers commit to:
+
+- Clarify and communicate the standards of acceptable behavior
+- Enforce this Code of Conduct fairly and consistently
+- Address violations promptly and appropriately
+- Provide a safe mechanism for reporting concerns
+- Maintain confidentiality of reporters
+- Document and review enforcement decisions
+
+### Enforcement Authority
+
+Maintainers have the authority and responsibility to:
+
+- Remove, edit, or reject comments, commits, code, issues, pull requests, and other contributions that violate this Code of Conduct
+- Temporarily or permanently ban users who engage in unacceptable behavior
+- Take corrective action proportional to the severity of the violation
+- Communicate decisions and reasons for moderation when appropriate
+- Consider context and good faith when evaluating violations
+
+## Scope
+
+This Code of Conduct applies to all community spaces associated with the blocks-genesis-py project, including but not limited to:
+
+- GitHub repositories, issues, pull requests, and discussions
+- Official project communication channels (email, chat, forums, etc.)
+- Project events and meetings (virtual and in-person)
+- Social media accounts managed by or for the project
+- Third-party spaces where individuals are representing the project or community
+
+This Code of Conduct applies to all types of contributions and participation:
+- Code contributions
+- Documentation
+- Issue reports and discussion
+- Comments and feedback
+- Mentoring and advice
+
+Individuals are responsible for upholding this Code of Conduct in all spaces where they represent the project.
+
+## Reporting and Enforcement
+
+### How to Report
+
+If you witness or experience a violation of this Code of Conduct, please report it to the project team:
+
+**Email**: [blocks@selisegroup.com](mailto:blocks@selisegroup.com)
+
+When reporting, please include:
+
+- Your contact information (name and email)
+- Description of the incident (what happened and when)
+- Location of the incident (URL, channel, etc.)
+- Names or usernames of those involved (if known)
+- Any additional context or evidence
+- Whether this is an ongoing situation
+
+**Reports are taken seriously. We will acknowledge receipt within 48 hours.**
+
+### Confidentiality
+
+- Reporter identities will be kept confidential unless the reporter consents otherwise
+- Investigation details will be shared only with those who need to know
+- We will not reveal information about the incident beyond what is necessary for enforcement
+- Retaliation against reporters is strictly prohibited
+
+### Investigation and Response
+
+Upon receiving a report, the project team will:
+
+1. **Acknowledge** receipt and inform the reporter of next steps
+2. **Investigate** the incident fairly and impartially, gathering information from all parties
+3. **Evaluate** the severity and context of the violation
+4. **Decide** on appropriate corrective action
+5. **Implement** the decision and communicate outcomes to relevant parties
+6. **Follow up** to ensure the behavior does not recur
+
+### Corrective Actions
+
+Depending on the severity and nature of the violation, corrective actions may include:
+
+- **Warning**: A private or public reminder of the Code of Conduct
+- **Temporary Suspension**: Temporary removal from community spaces (24 hours to 30 days)
+- **Permanent Ban**: Permanent removal from the project and community
+- **Escalation**: Referral to legal or other authorities for serious violations
+
+Factors considered in determining appropriate action:
+
+- Severity and impact of the behavior
+- Pattern or repeat offenses
+- Good faith versus deliberate misconduct
+- Cooperation with the investigation
+- Previous warnings or violations
+
+### Appeal Process
+
+If you believe a decision was unfair or incorrect, you may submit an appeal:
+
+1. Submit a written appeal to [blocks@selisegroup.com](mailto:blocks@selisegroup.com) within 14 days of the decision
+2. Explain why you believe the decision should be reconsidered
+3. A different member of the project leadership will review your appeal
+4. The decision will be communicated within 14 days of receipt
+
+Decisions on appeals are final.
+
+## Conflict Resolution
+
+We recognize that conflicts may arise. When disagreements occur:
+
+- Assume good intent and good faith
+- Focus on the issue, not the person
+- Request a private discussion if needed
+- Seek to understand differing perspectives
+- Work toward resolution that benefits the community
+- If informal resolution fails, escalate to the enforcement process
+
+## Examples of Conduct in Practice
+
+### Positive Examples
+
+- Respectfully disagreeing on a technical approach: *"I see the merit in your approach. I wonder if we've considered X? Here's why I think it might be important..."*
+- Welcoming a newcomer: *"Welcome! Thanks for your first contribution. Here's how to run the tests. Feel free to ask questions."*
+- Giving constructive feedback: *"This is a good start. Would it be possible to add tests for the edge case we discussed?"*
+- Acknowledging a mistake: *"You're right, I was wrong about that. Thanks for catching it. Here's what I've learned..."*
+
+### Unacceptable Examples
+
+- Dismissive language: *"That's a stupid idea. Anyone competent would know better."*
+- Gatekeeping: *"You're not a 'real' developer if you don't know X."*
+- Harassment: Repeated unwanted contact or personal attacks
+- Privacy violation: Sharing someone's personal information without consent
+- Retaliation: Excluding someone for reporting a violation
+
+## Questions or Concerns
+
+If you have questions about this Code of Conduct or need clarification:
+
+- **Email**: [blocks@selisegroup.com](mailto:blocks@selisegroup.com)
+- **Discussion**: Open an issue labeled `code-of-conduct` (for non-sensitive questions)
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct/](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+
+The project leadership is committed to enforcing this Code of Conduct consistently and fairly. We thank the Contributor Covenant community for providing a foundation for inclusive open-source communities.
+