Good First & Hacktoberfest Issues

Update the README tables for layer options to indicate which are optional and which are needed for the layers to work properly. Currently this is not clear

Created: 10/23/2025

## Problem The current triage workflow needs to be fixed and should follow Standard Operating Procedures (SOPs) similar to the development workflows documented in CLAUDE.md. ## Current State The triage workflow likely: - May not be properly configured or functional - Lacks clear documentation - Doesn't follow standardized procedures - May not be integrated with issue management properly ## Proposed Solution ### 1. Fix Triage Workflow - Review existing `.github/workflows/triage.yml` (if it exists) - Ensure proper GitHub Actions configuration - Test workflow triggers and actions - Fix any broken or deprecated actions ### 2. Create Triage SOP Create a comprehensive SOP document (`.github/TRIAGE_SOP.md`) that includes: **Triage Categories:** - **P0 - Critical**: Production breaking, security issues (immediate attention) - **P1 - High**: Major functionality broken, blocking issues (within 24 hours) - **P2 - Medium**: Feature requests, non-blocking bugs (within 1 week) - **P3 - Low**: Nice-to-have improvements, minor issues (backlog) **Issue Classification:** - Bug: Something isn't working as expected - Enhancement: New feature or improvement - Documentation: Docs need updates - Question: Further information needed - Duplicate: Already reported - Invalid: Not a valid issue **Automated Triage Actions:** 1. **On Issue Creation**: - Auto-label based on issue template type - Assign to appropriate project board - Notify relevant team members - Add to triage queue if unlabeled 2. **On Issue Update**: - Track state changes - Update project board status - Notify assignees of changes 3. **Stale Issue Management**: - Mark issues without activity for 30 days as "stale" - Close stale issues after 14 days if no response - Exempt issues with certain labels (e.g., "long-term", "blocked") **Manual Triage Process:** 1. Review new issues in triage queue 2. Validate issue description and reproduction steps 3. Assign priority label (P0-P3) 4. Assign appropriate labels (bug, enhancement, etc.) 5. Assign to milestone or project board 6. Assign to team member or leave unassigned for community ### 3. GitHub Actions Workflow Create/update `.github/workflows/triage.yml`: ```yaml name: Issue Triage on: issues: types: [opened, edited, labeled, unlabeled] issue_comment: types: [created] jobs: triage: runs-on: ubuntu-latest permissions: issues: write contents: read steps: - name: Auto-label bug reports if: contains(github.event.issue.body, 'Bug Report') uses: actions/github-script@v7 with: script: | github.rest.issues.addLabels({ owner: context.repo.owner, repo: context.repo.repo, issue_number: context.issue.number, labels: ['bug'] }) - name: Auto-label feature requests if: contains(github.event.issue.body, 'Feature Request') uses: actions/github-script@v7 with: script: | github.rest.issues.addLabels({ owner: context.repo.owner, repo: context.repo.repo, issue_number: context.issue.number, labels: ['enhancement'] }) - name: Check for related issues uses: actions/github-script@v7 with: script: | // Search for similar issues and comment if found const title = context.payload.issue.title; const { data: issues } = await github.rest.search.issuesAndPullRequests({ q: `repo:${context.repo.owner}/${context.repo.repo} is:issue is:open "${title}"`, sort: 'created', per_page: 5 }); if (issues.total_count > 1) { const relatedIssues = issues.items .filter(i => i.number !== context.issue.number) .map(i => `- #${i.number}: ${i.title}`) .join('\n'); if (relatedIssues) { await github.rest.issues.createComment({ owner: context.repo.owner, repo: context.repo.repo, issue_number: context.issue.number, body: `## Related Issues\n\nFound potentially related issues:\n\n${relatedIssues}\n\nPlease check if any of these address your concern.` }); } } stale: runs-on: ubuntu-latest steps: - uses: actions/stale@v9 with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: 'This issue has been automatically marked as stale due to inactivity. It will be closed in 14 days if no further activity occurs.' close-issue-message: 'This issue was automatically closed due to inactivity.' days-before-stale: 30 days-before-close: 14 exempt-issue-labels: 'long-term,blocked,on-hold' stale-issue-label: 'stale' ``` ### 4. Issue Templates Create/update issue templates in `.github/ISSUE_TEMPLATE/`: **bug_report.yml**: ```yaml name: Bug Report description: Report a bug or unexpected behavior labels: ["bug", "needs-triage"] body: - type: markdown attributes: value: | Thanks for reporting a bug! Please provide as much detail as possible. - type: textarea id: description attributes: label: Bug Description description: Clear description of the bug validations: required: true - type: textarea id: reproduction attributes: label: Steps to Reproduce description: Minimal steps to reproduce the issue placeholder: | 1. Step one 2. Step two 3. Step three validations: required: true - type: textarea id: expected attributes: label: Expected Behavior description: What should happen? validations: required: true - type: textarea id: actual attributes: label: Actual Behavior description: What actually happens? validations: required: true - type: input id: version attributes: label: Version description: Which version are you using? validations: required: true ``` **feature_request.yml**: ```yaml name: Feature Request description: Suggest a new feature or enhancement labels: ["enhancement", "needs-triage"] body: - type: markdown attributes: value: | Thanks for suggesting a feature! - type: textarea id: problem attributes: label: Problem Description description: What problem does this solve? validations: required: true - type: textarea id: solution attributes: label: Proposed Solution description: How should this feature work? validations: required: true - type: textarea id: alternatives attributes: label: Alternatives Considered description: What other solutions did you consider? validations: required: false ``` ### 5. Documentation Updates Update CLAUDE.md to reference the triage SOP: ```markdown ## Issue Management All issues follow the [Triage SOP](.github/TRIAGE_SOP.md) for consistent handling: - **Reporting Issues**: Use issue templates for bugs and feature requests - **Triage Process**: Issues are automatically triaged and labeled - **Priority Levels**: P0 (critical) → P3 (low priority) - **Stale Issues**: Automatically managed after 30 days of inactivity ``` ## Implementation Checklist - [ ] Review existing triage workflow (if any) - [ ] Create `.github/TRIAGE_SOP.md` documentation - [ ] Create/update `.github/workflows/triage.yml` - [ ] Create/update issue templates in `.github/ISSUE_TEMPLATE/` - [ ] Test workflow with sample issues - [ ] Update CLAUDE.md with triage references - [ ] Document for team members ## Acceptance Criteria - [ ] Triage workflow runs successfully on issue creation - [ ] Issues are automatically labeled based on type - [ ] Related issues are detected and linked - [ ] Stale issues are managed automatically - [ ] Issue templates provide clear guidance - [ ] Documentation is comprehensive and clear - [ ] Team understands triage process ## Related - Related to issue management and automation - Improves developer workflow and project organization - Follows SOP patterns from CLAUDE.md workflows ## Labels - enhancement - good first issue (for someone to implement) - documentation

Created: 10/23/2025

The wiki has been moved to an mdbook but it hasn't been deployed yet. It should be built and deployed to GitHub Pages.

Created: 10/23/2025

Created: 10/23/2025

script: update-documentation page: accordion-accessibility ### Subject Accessibility section for `Accordion` ### Path `www/contents/components/(components)/accordion.mdx` `www/contents/components/(components)/accordion.ja.mdx` ### Description Populate the Accessibility section using the v1 documentation as reference

Created: 10/23/2025

Add an AGENTS.md file to provide standardized instructions for AI coding agents working on this project. This follows the open-source specification from https://agents.md/ and will help coding agents understand project-specific guidelines, build processes, and development workflows. ##The file should include: - Project overview and setup instructions - Build and test commands (make docker/install, poetry commands) - Code style guidelines (ruff configuration) - Testing conventions (pytest setup) - Commit message format - Security considerations for Slack bot development This will improve consistency when AI tools assist with development tasks and provide a centralized location for agent-specific project guidance.

Created: 10/23/2025

Upgrade the project from Python 3.11 to the latest stable Python version 3.14.0 to take advantage of performance improvements, new features, and security updates. ## Tasks: - [ ] Update pyproject.toml python dependency from ^3.11 to ^3.14 - [ ] Update Dockerfile base image from python:3.11-slim to python:3.14-slim - [ ] Test compatibility with existing dependencies (slack-bolt, aiohttp, pytest, ruff) - [ ] Update development environment setup instructions - [ ] Update README documentation to reflect new Python version requirement - [ ] Add new section in README explaining how to upgrade/downgrade Python version for local development - [ ] Update any Python version references in documentation ## Acceptance Criteria: - [ ] All tests pass with Python 3.14 - [ ] Docker build succeeds with new Python version - [ ] README includes Python version upgrade/downgrade instructions - [ ] Documentation accurately reflects Python 3.14 requirement This upgrade ensures the project stays current with the latest Python improvements and maintains long-term security and performance benefits.

Created: 10/23/2025

### Project slug (e.g., snake, todo) _No response_ ### Summary Let's build the classic "Hangman" word-guessing game. This version will be for two players: one player enters a secret word, and the second player tries to guess it. This project is excellent for practicing DOM manipulation, handling user events (like keyboard clicks), and managing game state. **Core Features (User Stories):** **Phase 1: Word Setup** * The game first asks Player 1 to enter a secret word. * The input for the secret word should be hidden (like a password field) so Player 2 can't see it. * After Player 1 submits the word, this setup screen is hidden, and the main game board appears. **Phase 2: Guessing** * The game board should display a series of underscores (`_ _ _ _`), one for each letter in the secret word. * An on-screen alphabet keyboard (A-Z) should be shown for Player 2 to click and guess letters. * When Player 2 clicks a letter: * If the letter is in the secret word, all instances of that letter are revealed (e.g., `_ P P _ E`). * If the letter is *not* in the secret word, the number of "Wrong Guesses" increases by one. * The clicked letter on the on-screen keyboard should be disabled so it can't be guessed again. **Phase 3: Game End** * The game tracks the number of wrong guesses (e.g., 6 tries). * If Player 2 guesses all the letters in the word before running out of tries, a "You Win!" message is shown. * If Player 2 runs out of tries, a "You Lose!" message is shown, and the secret word is revealed. * A "Play Again" button should appear to reset the game back to Phase 1. ### Details / Acceptance criteria _No response_ ### Scope - [x] UI changes - [x] Logic changes - [x] Accessibility - [ ] Tests (manual)

Created: 10/23/2025

We erroneously put `0` instead of e.g. `-1` in https://github.com/BfArM-MVH/grz-tools/pull/435 (not much of an issue at the moment, though, and an easy fix)

Created: 10/23/2025

### Terms - [x] Checked the [existing issues](https://github.com/jeertmans/DiffeRT/issues?q=is%3Aissue+label%3Adocumentation+) and [discussions](https://github.com/jeertmans/DiffeRT/discussions) to see if my issue had not already been reported; ### Describe the issue As discussed in https://github.com/jeertmans/DiffeRT/pull/326#issuecomment-3437022985, the `compute_paths` method exhibits some challenges when it comes to JIT-compilation, as some cases, e.g., when setting `disconnect_inactive_triangles` to `True`, will create output arrays whose shapes depend on the values of the input arrays. This is not compatible with JAX's tracing system, this should probably be documented somewhere. ### Affected page(s) + https://differt.eertmans.be/latest/reference/_autosummary/differt.scene.TriangleScene.html#differt.scene.TriangleScene.compute_paths + https://differt.eertmans.be/latest/notebooks/performance_tips.html ### Issue type Documentation enhancement ### Recommended fix or suggestions _No response_

Created: 10/23/2025

### Project slug (e.g., snake, todo) _No response_ ### Summary Core Features (User Stories): A user should be able to: - Enter the total bill amount (e.g., Rs50.00). - Select a tip percentage from predefined buttons (e.g., 10%, 15%, 20%). - (Optional) Enter a custom tip percentage in an input field. - Enter the number of people to split the bill (e.g., 2). - See the calculated "Tip Amount" (e.g., Rs7.50). - See the "Total Bill" (bill + tip) (e.g., Rs57.50). - See the "Total per Person" (e.g., Rs28.75). ### Details / Acceptance criteria _No response_ ### Scope - [x] UI changes - [x] Logic changes - [ ] Accessibility - [ ] Tests (manual)

Created: 10/23/2025

### Concise Description The hamburger menu (three horizontal lines) that allowed customization of the video (speed, quality, etc.) doesn't respond to clicks anymore in my browser. Turning off the hamburger menu option shows the original options (quality, subtitles, etc.) with no problem. Just the hamburger menu seems to not be clickable! ### Browser/s Brave ### Other Browser: Chrome ### 'Steps to reproduce' - Which of our features is required for the bug to happen? Hamburger menu enabled (in player options) ### Since when? I'm not sure - less than a month ago? ### Does the bug still happen when you log out of YouTube? Yes ### ..No? Then please paste your yt.config_.EXPERIMENT_FLAGS. Twice (With the error & Without) _No response_ ### Are any errors or related log-messages shown in the Browser-Console? (F12) _No response_ ### Tested as the only active extension? (incognito mode or another browser users): Yes ### Expected preferred behavior: _No response_ ### ImprovedTube Version 4.1350 ### Your Settings (From the Extension's `⋮`-Hamburger menu > Settings > Backup & reset > Export settings) _No response_ ### Your YouTube-Document _No response_ ### OS / Device: _No response_

Created: 10/23/2025

🟢 Title : Python Turtle Graphics Contribution 🟢 Programming language : Python 🟢 Objective : To add a unique and visual "Hello World" implementation using one of Python's standard, built-in libraries. 🟢 Summary : This program utilizes the turtle module to draw the "Hello, World!" message graphically on the screen, providing a fun and beginner-friendly example of how to use an external library. *********************************************************************** ✅ Details to Include When Taking the Issue: please assign this issue to me Name : **kanishka1804** *********************************************************************** Happy Contributing! 🚀 Wishing you all the best on your open source journey😍. Enjoy! 😎

Created: 10/23/2025 • 1 comments

https://x.com/vaibhuujoshi/status/1981351380724941305

Created: 10/23/2025 • 2 comments

### Is there an existing issue for this? - [x] I have searched the existing issues ### Current Behavior <img width="1033" height="209" alt="Image" src="https://github.com/user-attachments/assets/78ee278d-c13f-41e0-b204-ce85a4b11cd1" /> 缺少了 SELECT 关键词，可以确认生成的 sql 没有问题，在计划执行模块中可以看到完整 sql <img width="1185" height="233" alt="Image" src="https://github.com/user-attachments/assets/47d61241-3552-4a33-b8cb-250975fd0717" /> ### Expected Behavior _No response_ ### Steps To Reproduce _No response_ ### Environment ```markdown Spring AI Alibaba DataAgent version(s): ``` ### Debug logs _No response_ ### Anything else? _No response_

Created: 10/23/2025

## Description In ChaosCenter → Create Probes → HTTP Probe properties configuration, input fields such as **Timeout**, **Interval**, **Attempt**, and other properties display a **UI cutout** when focused. This creates a visual glitch and affects user experience. The UI behavior should be consistent with the **Name** input field for HTTP probes, which does not show any cutout when focused. ## Location ChaosCenter → Create Probes → HTTP Probe properties configuration → Input fields (Timeout Interval, Attempt, etc.) <img width="3456" height="1984" alt="Image" src="https://github.com/user-attachments/assets/40f52cea-2fc9-48b3-a200-29b2d05a35cc" /> Reference <img width="3456" height="1984" alt="Image" src="https://github.com/user-attachments/assets/5539ce8a-03a7-48eb-99db-b2ec4c903d8f" /> ## Steps to Reproduce 1. Open ChaosCenter and navigate to the Probes, create an HTTP probe, and go to the properties configuration section. 2. Click on any input field like **Timeout Interval** or **Attempt**. 3. Observe the UI cutout appearing around the input field. ## Expected Behavior - Input fields should not display any cutout or visual glitch when focused. - Styling should be consistent with the **Name** input field. ## Proposed Fix - Update the CSS / component styling for all HTTP Probe property input fields to match the Name input field. - Test focus behavior for all input fields in the HTTP Probe configuration.

Created: 10/23/2025 • 2 comments

## Em Python Retorna o índice da *última ocorrência* de uma `string` informada. Exemplo: ```python txt = "Mi casa, su casa." x = txt.rfind("casa") print(x) # Retornar o valor 12 ``` ## Pituguês - Issue Trazer este método para o Pituguês. Sugestão de nome: `encontre_ultimo()` ### Contribuição Para saber mais, preparamos [este tutorial](https://github.com/DesignLiquido/pitugues-docs/blob/principal/CONTRIBUTING.md) que te ensina a como contribuir com o Pituguês <3 ## Fonte - https://www.w3schools.com/python/ref_string_rfind.asp

Created: 10/23/2025

### What happened? When saving a dndarray with `dtype=ht.int32` using `save_hdf5`, the resulting h5 dataset has the type `float32`. This can be avoided by specifying `dtype=int` or `dtype=np.int32` (not `ht.int32` or `torch.int32` as those throw errors) but it should use the dtype of the dndarray by default. The same issue exists for `load_hdf5`, where it does not use the type of the h5 dataset but sets it to `float32`. ### Code snippet triggering the error ```shell import heat as ht a = ht.arange(100, dtype=ht.int32) ht.save_hdf5(a, 'test.h5', dataset='data') b = ht.load_hdf5('test.h5', dataset='data') print(b.dtype) ``` ### Error message or erroneous outcome ```shell No error just the wrong type ``` ### Version main (development branch) ### Python version 3.12 ### PyTorch version 2.6 ### MPI version ```shell ```

Created: 10/23/2025

## 概要 タブ文字をスペースに展開してから比較する `-t` または `--expand-tabs` オプションを実装する。 ## 説明 これは標準的な `diff` コマンドのオプションで、タブ文字（`\t`）を8個のスペースに展開してから比較します。タブとスペースが混在するファイルを比較する場合に便利です。 ## 期待される動作 ```bash # File1 (タブ使用): hello\tworld # File2 (スペース使用): hello world # -t フラグを使用すると、これらのファイルは同一と見なされる $ dcmp -t file1.txt file2.txt (出力なし - タブ展開後は同一) ``` ## 実装のポイント - [cmd/root.go](cmd/root.go) に `--expand-tabs` / `-t` フラグを追加 - [internal/io.go:22](internal/io.go#L22) でタブをスペースに展開 - `strings.ReplaceAll(line, "\t", " ")` で実装（タブ幅は8） - または `strings.Replace()` やカスタム実装でタブ位置を考慮 - 推定作業量: 約5-10行のコード ## 優先度 中 - タブ/スペース混在ファイルの比較に便利 ## 難易度 ⭐☆☆☆☆ 非常に簡単

Created: 10/23/2025

## 概要 正規表現にマッチする行を無視する `-I` または `--ignore-matching-lines` オプションを実装する。 ## 説明 これは標準的な `diff` コマンドのオプションで、指定した正規表現パターンにマッチする行を比較対象から除外します。コメント行、タイムスタンプ、バージョン情報などを無視したい場合に便利です。 ## 期待される動作 ```bash # File1: # Comment line 1 hello world # Comment line 2 # File2: # Comment line A hello world # Comment line B # -I フラグでコメント行を無視すると、これらのファイルは同一と見なされる $ dcmp -I '^#' file1.txt file2.txt (出力なし - コメント行を無視すると同一) # 複数のパターンを指定可能 $ dcmp -I '^#' -I '^//' file1.txt file2.txt ``` ## 実装のポイント - [cmd/root.go](cmd/root.go) に `--ignore-matching-lines` / `-I` フラグを追加（文字列配列として複数指定可能） - [internal/io.go:11-26](internal/io.go#L11-L26) の `GetLines()` 関数を修正 - パターンにマッチする行をフィルタリング - `regexp.MustCompile()` で正規表現をコンパイル - 推定作業量: 約15-25行のコード ## 優先度 高 - コメントやメタデータを無視した比較に便利 ## 難易度 ⭐⭐☆☆☆ 簡単

Created: 10/23/2025