Good First Issues

## 🎌 Add Japanese Proverb (ことわざ) **Category:** Community Contribution - Proverb **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this traditional Japanese proverb to help learners understand Japanese wisdom! ### The Proverb | Japanese | Reading | English | |----------|---------|---------| | **縁は異なもの味なもの** | En wa inamono aji na mono | Fate is strange yet delightful | > 💡 **Meaning:** Chance connections can be surprisingly good ### 📝 Instructions 1. Open [`data/community-content/japanese-proverbs.json`](../blob/main/data/community-content/japanese-proverbs.json) 2. Add this proverb object to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item ```json { "japanese": "縁は異なもの味なもの", "romaji": "En wa inamono aji na mono", "english": "Fate is strange yet delightful", "meaning": "Chance connections can be surprisingly good" } ``` 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add new japanese proverb` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/8/2026

Choose a documentation file and correct all the links to Python objects. We have a lot of documentation files. Sometimes, we link to components, functions, and other objects and the links don't work. Working link: <img width="56" height="27" alt="Image" src="https://github.com/user-attachments/assets/9ce10aa2-45c4-4c70-9b8d-d7211b3026cd" /> Broken link: <img width="56" height="27" alt="Image" src="https://github.com/user-attachments/assets/70fd1921-8710-4387-bab2-343dc79d4fe3" /> Please read through as many files as you like and do the following: - If the file has no broken links, comment below that it is perfect! Thanks! - If the file contains one or more broken links, please fix them (see guidance). They need the "fully qualified name". Example: <img width="1413" height="48" alt="Image" src="https://github.com/user-attachments/assets/eb7c516e-e219-45d8-85fa-71ebacf1a201" /> ## Guidance (GitHub only) For some files, you can [Make small edits via GitHub](https://icalendar.readthedocs.io/en/latest/contribute/documentation/small-edits.html). (Local setup) For the [API Reference in /reference/](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.html), you need to find the file in [src/icalendar](https://github.com/collective/icalendar/blob/main/src/icalendar/) and [build the documentation on your computer](https://icalendar.readthedocs.io/en/latest/contribute/documentation/build-check.html) Additionally, we value changes to the documentation to make it easier to understand for first-time users! ## Checklist All of these files need checking before closing the issue. If you create your first pull request, please only modify one file! - [ ] [404.html](https://icalendar.readthedocs.io/en/latest/404.html) - [ ] [about.html](https://icalendar.readthedocs.io/en/latest/about.html) - [ ] [api.html](https://icalendar.readthedocs.io/en/latest/api.html) - [ ] [changelog.html](https://icalendar.readthedocs.io/en/latest/changelog.html) - [ ] [cli.html](https://icalendar.readthedocs.io/en/latest/cli.html) - [ ] [contribute/code-of-conduct.html](https://icalendar.readthedocs.io/en/latest/contribute/code-of-conduct.html) - [ ] [contribute/credits.html](https://icalendar.readthedocs.io/en/latest/contribute/credits.html) - [ ] [contribute/development.html](https://icalendar.readthedocs.io/en/latest/contribute/development.html) - [ ] [contribute/documentation/build-check.html](https://icalendar.readthedocs.io/en/latest/contribute/documentation/build-check.html) - [ ] [contribute/documentation/index.html](https://icalendar.readthedocs.io/en/latest/contribute/documentation/index.html) - [ ] [contribute/documentation/small-edits.html](https://icalendar.readthedocs.io/en/latest/contribute/documentation/small-edits.html) - [ ] [contribute/documentation/style-guide.html](https://icalendar.readthedocs.io/en/latest/contribute/documentation/style-guide.html) - [ ] [contribute/index.html](https://icalendar.readthedocs.io/en/latest/contribute/index.html) - [ ] [contribute/maintenance.html](https://icalendar.readthedocs.io/en/latest/contribute/maintenance.html) - [ ] [contributing.html](https://icalendar.readthedocs.io/en/latest/contributing.html) - [ ] [credits.html](https://icalendar.readthedocs.io/en/latest/credits.html) - [ ] [genindex.html](https://icalendar.readthedocs.io/en/latest/genindex.html) - [ ] [how-to/attendees.html](https://icalendar.readthedocs.io/en/latest/how-to/attendees.html) - [ ] [how-to/cli.html](https://icalendar.readthedocs.io/en/latest/how-to/cli.html) - [ ] [how-to/custom-components.html](https://icalendar.readthedocs.io/en/latest/how-to/custom-components.html) - [ ] [how-to/fuzz-testing.html](https://icalendar.readthedocs.io/en/latest/how-to/fuzz-testing.html) - [ ] [how-to/index.html](https://icalendar.readthedocs.io/en/latest/how-to/index.html) - [ ] [how-to/install.html](https://icalendar.readthedocs.io/en/latest/how-to/install.html) - [ ] [how-to/jcal.html](https://icalendar.readthedocs.io/en/latest/how-to/jcal.html) - [ ] [how-to/parse-errors.html](https://icalendar.readthedocs.io/en/latest/how-to/parse-errors.html) - [ ] [how-to/QA.html](https://icalendar.readthedocs.io/en/latest/how-to/QA.html) - [ ] [how-to/upgrade.html](https://icalendar.readthedocs.io/en/latest/how-to/upgrade.html) - [ ] [how-to/usage.html](https://icalendar.readthedocs.io/en/latest/how-to/usage.html) - [ ] [index.html](https://icalendar.readthedocs.io/en/latest/index.html) - [ ] [install.html](https://icalendar.readthedocs.io/en/latest/install.html) - [ ] [license.html](https://icalendar.readthedocs.io/en/latest/license.html) - [ ] [maintenance.html](https://icalendar.readthedocs.io/en/latest/maintenance.html) - [ ] [reference/api/icalendar.alarms.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.alarms.html) - [ ] [reference/api/icalendar.attr.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.attr.html) - [ ] [reference/api/icalendar.cal.alarm.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.alarm.html) - [ ] [reference/api/icalendar.cal.availability.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.availability.html) - [ ] [reference/api/icalendar.cal.available.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.available.html) - [ ] [reference/api/icalendar.cal.calendar.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.calendar.html) - [ ] [reference/api/icalendar.cal.component_factory.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.component_factory.html) - [ ] [reference/api/icalendar.cal.component.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.component.html) - [ ] [reference/api/icalendar.cal.event.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.event.html) - [ ] [reference/api/icalendar.cal.examples.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.examples.html) - [ ] [reference/api/icalendar.cal.free_busy.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.free_busy.html) - [ ] [reference/api/icalendar.cal.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.html) - [ ] [reference/api/icalendar.cal.journal.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.journal.html) - [ ] [reference/api/icalendar.cal.timezone.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.timezone.html) - [ ] [reference/api/icalendar.cal.todo.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cal.todo.html) - [ ] [reference/api/icalendar.caselessdict.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.caselessdict.html) - [ ] [reference/api/icalendar.cli.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.cli.html) - [ ] [reference/api/icalendar.compatibility.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.compatibility.html) - [ ] [reference/api/icalendar.enums.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.enums.html) - [ ] [reference/api/icalendar.error.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.error.html) - [ ] [reference/api/icalendar.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.html) - [ ] [reference/api/icalendar.param.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.param.html) - [ ] [reference/api/icalendar.parser_tools.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser_tools.html) - [ ] [reference/api/icalendar.prop.xml_reference.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.xml_reference.html) - [ ] [reference/api/icalendar.timezone.equivalent_timezone_ids.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.equivalent_timezone_ids.html) - [ ] [reference/api/icalendar.timezone.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.html) - [ ] [reference/api/icalendar.timezone.provider.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.provider.html) - [ ] [reference/api/icalendar.timezone.pytz.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.pytz.html) - [ ] [reference/api/icalendar.timezone.tzid.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.tzid.html) - [ ] [reference/api/icalendar.timezone.tzp.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.tzp.html) - [ ] [reference/api/icalendar.timezone.windows_to_olson.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.windows_to_olson.html) - [ ] [reference/api/icalendar.timezone.zoneinfo.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.timezone.zoneinfo.html) - [ ] [reference/api/icalendar.tools.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.tools.html) - [ ] [reference/api/icalendar.version.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.version.html) - [ ] [reference/changelog.html](https://icalendar.readthedocs.io/en/latest/reference/changelog.html) - [ ] [reference/component-api.html](https://icalendar.readthedocs.io/en/latest/reference/component-api.html) - [ ] [reference/design.html](https://icalendar.readthedocs.io/en/latest/reference/design.html) - [ ] [reference/glossary.html](https://icalendar.readthedocs.io/en/latest/reference/glossary.html) - [ ] [reference/index.html](https://icalendar.readthedocs.io/en/latest/reference/index.html) - [ ] [search.html](https://icalendar.readthedocs.io/en/latest/search.html) - [ ] [security.html](https://icalendar.readthedocs.io/en/latest/security.html) - [ ] [usage.html](https://icalendar.readthedocs.io/en/latest/usage.html) - [ ] [reference/api/icalendar.parser.content_line.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser.content_line.html) After #1150 is merged: - [ ] [reference/api/icalendar.parser.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser.html) - [ ] [reference/api/icalendar.parser.parameter.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser.parameter.html) - [ ] [reference/api/icalendar.parser.property.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser.property.html) - [ ] [reference/api/icalendar.parser.string.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser.string.html) - [ ] [reference/api/icalendar.parser_tools.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.parser_tools.html) After #1136 is merged: - [ ] [reference/api/icalendar.prop.adr.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.adr.html) - [ ] [reference/api/icalendar.prop.binary.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.binary.html) - [ ] [reference/api/icalendar.prop.boolean.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.boolean.html) - [ ] [reference/api/icalendar.prop.broken.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.broken.html) - [ ] [reference/api/icalendar.prop.cal_address.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.cal_address.html) - [ ] [reference/api/icalendar.prop.categories.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.categories.html) - [ ] [reference/api/icalendar.prop.conference.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.conference.html) - [ ] [reference/api/icalendar.prop.dt.base.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.base.html) - [ ] [reference/api/icalendar.prop.dt.common.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.common.html) - [ ] [reference/api/icalendar.prop.dt.date.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.date.html) - [ ] [reference/api/icalendar.prop.dt.datetime.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.datetime.html) - [ ] [reference/api/icalendar.prop.dt.duration.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.duration.html) - [ ] [reference/api/icalendar.prop.dt.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.html) - [ ] [reference/api/icalendar.prop.dt.list.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.list.html) - [ ] [reference/api/icalendar.prop.dt.period.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.period.html) - [ ] [reference/api/icalendar.prop.dt.time.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.time.html) - [ ] [reference/api/icalendar.prop.dt.types.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.types.html) - [ ] [reference/api/icalendar.prop.dt.utc_offset.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.dt.utc_offset.html) - [ ] [reference/api/icalendar.prop.factory.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.factory.html) - [ ] [reference/api/icalendar.prop.float.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.float.html) - [ ] [reference/api/icalendar.prop.geo.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.geo.html) - [ ] [reference/api/icalendar.prop.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.html) - [ ] [reference/api/icalendar.prop.image.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.image.html) - [ ] [reference/api/icalendar.prop.inline.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.inline.html) - [ ] [reference/api/icalendar.prop.integer.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.integer.html) - [ ] [reference/api/icalendar.prop.n.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.n.html) - [ ] [reference/api/icalendar.prop.org.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.org.html) - [ ] [reference/api/icalendar.prop.recur.frequency.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.frequency.html) - [ ] [reference/api/icalendar.prop.recur.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.html) - [ ] [reference/api/icalendar.prop.recur.month.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.month.html) - [ ] [reference/api/icalendar.prop.recur.recur.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.recur.html) - [ ] [reference/api/icalendar.prop.recur.skip.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.skip.html) - [ ] [reference/api/icalendar.prop.recur.weekday.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.recur.weekday.html) - [ ] [reference/api/icalendar.prop.text.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.text.html) - [ ] [reference/api/icalendar.prop.uid.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.uid.html) - [ ] [reference/api/icalendar.prop.unknown.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.unknown.html) - [ ] [reference/api/icalendar.prop.uri.html](https://icalendar.readthedocs.io/en/latest/reference/api/icalendar.prop.uri.html)

Created: 2/8/2026

## MVP-XXX — REW Parametric EQ Import (Paste / Upload) ### Goal Provide the ability for users to paste or upload Room EQ Wizard (REW) Parametric EQ exports, convert them into the project’s canonical EQ preset format, and immediately apply them to the running CamillaDSP instance. When the CamillaEQ server is **not** in `READONLY` mode (see [architecture.md](docs/developer/architecture.md)), the imported preset must also be persisted to the backend preset library. Users must be able to name the preset and provide a description, leveraging CamillaDSP’s native support for filter descriptions and aligning with the project’s internal preset standard. This milestone focuses on user-initiated, runtime imports, in contrast to the build-time AutoEQ ingestion discussed in #1. --- ### Status ToDo --- ### Deliverables #### 1. REW Import Entry Points - UI affordance to: - Paste REW Parametric EQ text - Upload a REW-generated text file - Supported input: - REW “Generic Parametric EQ” exports - REW “Equalizer APO” style exports (PEQ-only subset) #### 2. REW Parser + Normalization Layer - Client-side parser that: - Extracts preamp gain (if present) - Extracts ordered PEQ filters (type, freq, gain, Q) - Ignores unsupported constructs or comments - Normalize into the **canonical EQ preset model** - Apply numeric normalization rules (rounding, clamping) #### 3. Preset Metadata Capture - UI step to capture: - Preset name (required) - Preset description (optional) - Metadata stored alongside EQ data - Description propagated into: - Internal preset format - CamillaDSP filter `description` fields where applicable #### 4. Live DSP Application - Imported preset is: - Converted via existing mapping layers - Uploaded to CamillaDSP (`SetConfigJson` + `Reload`) - UI updates immediately to reflect: - Imported bands - Preamp gain - Enabled/disabled state #### 5. Conditional Backend Persistence - If server is **not** in `READONLY` mode: - Persist imported preset via `/api/configs` - If server **is** in `READONLY` mode: - Skip persistence - Clearly indicate “temporary / unsaved preset” in UI --- ### Implementation Notes - **Client-side parsing only** - No server-side text parsing required - Keeps backend simple and deterministic - **Reuse canonical EQ model** - REW import must target the same internal model used by AutoEQ presets - **Strict-but-forgiving parsing** - Skip unsupported or malformed filters - Warn user if filters are dropped or altered - **Description handling** - Preset-level description stored in preset metadata - Filter-level descriptions may be auto-generated (e.g. “REW Import – Band 3”) - **READONLY enforcement** - Respect `SERVER_READ_ONLY` at the route layer - Client must not assume persistence success - **No DSP config mutation shortcuts** - Always go through existing `pipelineConfigMapping` logic - Consider the implementation may be extended at some point in the future to support other formats such as Equalizer APO --- ## Testing Strategy Summary ### Risk Reduced Early - Unit-test REW parsing logic with: - Minimal exports - Full multi-band exports - Missing preamp cases - Validate conversion parity: - REW → canonical model → CamillaDSP → canonical model round-trip - Test READONLY behavior explicitly at the route layer ### Deferred Complexity - No CSV-based REW imports: it just adds more parsers and heuristics - No FIR or convolution imports: it introduces latency handling, channel alignments, and UI requirements for impulse lifecycles. - No per-channel or asymmetric EQ support: the EQ UI is intentionally symmetric at this time. - No automatic gain compensation or headroom correction: its tricky to automate correctly and we alrwady expose preamp explicitly. Caveat is that advanced users may expect to manage gain. - No REW project (`.mdat`) file support: it's opaque and versioned. - Filter semantics beyond biquads: it's an edge case with exotic slopes or combined filters. This milestone establishes REW as a first-class interactive import source while keeping scope limited to safe, well-understood Parametric EQ workflows.

Created: 2/8/2026

### Current Behavior We have a project in Music Blocks which is a [test suite](https://github.com/sugarlabs/musicblocks/blob/master/examples/test-suite.html). It has about 25% coverage of the various blocks. ### Desired Situation We'd like to expand the coverage to more blocks. The test suite should be organized around the palettes with separate tests for beginner blocks and advanced blocks. Follow the basic format of the existing tests. Individual tests look like this: <img width="398" height="411" alt="Image" src="https://github.com/user-attachments/assets/6c57d230-49ae-48a7-b1f8-b0af72fdf3c1" /> These should be organized into action blocks around these themes: - [ ] Rhythm palette (Beginner) - [ ] Rhythm palette (Advanced) - [ ] Meter palette (Beginner) - [ ] Meter palette (Advanced) - [ ] Pitch palette (Beginner) - [ ] Picth palette (Advanced) - [ ] Intervals palette (Beginner) - [ ] Intervals palette (Advanced) - [ ] Tone palette (Beginner) - [ ] Tone palette (Advanced) - [ ] Ornament palette (Beginner) - [ ] Ornament palette (Advanced) - [ ] Meter palette (Beginner) - [ ] Meter palette (Advanced) - [ ] Drum palette (Beginner) - [ ] Drum palette (Advanced) The action blocks should be added to the start block as per: <img width="412" height="621" alt="Image" src="https://github.com/user-attachments/assets/b3712094-3c21-49c5-9889-b6ffc83d04ba" /> 🙋🏾🙋🏼 Questions: [Community Matrix Server](https://matrix.to/#/#musicblocksdev:matrix.org).

Created: 2/8/2026 • 1 comments

I want to introduce our app more good User Experience like changing the fonts and the overall appearance of the app which gives the app a more modern look. I want to add some more unique and elegant logos and replace the old one with more good but the color scheme should be the same as kept, Sharing you the example look of the app style **Additional context** <img width="300" height="600" alt="Image" src="https://github.com/user-attachments/assets/0bfaeda8-a7eb-4833-bbb0-f65d1046c8d0" /> <img width="300" height="600" alt="Image" src="https://github.com/user-attachments/assets/903d99e6-e4b6-461d-bc31-965a695284e7" /> <img width="300" height="600" alt="Image" src="https://github.com/user-attachments/assets/2fe35855-f212-47ca-b2a7-435bdc001f38" /> <img width="300" height="600" alt="Image" src="https://github.com/user-attachments/assets/1e6cbc2e-7f13-418f-b565-ef910d425db8" />

Created: 2/8/2026

### Proposed Improvement Create a multi-stage Dockerfile to optimize the production image size and security by separating the build environment from the runtime environment. ### Acceptance Criteria - [ ] Dockerfile uses a lightweight base image for runtime (e.g., Alpine or Distroless). - [ ] Docker Compose updated to reflect the new structure.

Created: 2/8/2026

### Proposed Improvement Implement custom Bean Validation to enforce strong passwords, ensuring they include uppercase letters, numbers, and special characters. ### Acceptance Criteria - [ ] Password validation rules implemented. - [ ] Detailed error messages returned when registration/update fails validation.

Created: 2/8/2026

### Describe the bug Google has notified me about a problem of CLS (Cumulative Layout Shift), probably caused by components that load too late and move the entire layout. The URLs interested are: - https://physicshub.github.io/simulations/BouncingBall - https://physicshub.github.io/blog/physics-bouncing-ball-comprehensive-educational-guide - https://physicshub.github.io/ - https://physicshub.github.io/simulations/BallGravity - https://physicshub.github.io/simulations/SimplePendulum - https://physicshub.github.io/blog/comprehensive-guide-to-vector-operations - https://physicshub.github.io/simulations/SpringConnection - https://physicshub.github.io/simulations/VectorsOperations Check more info here: https://pagespeed.web.dev/analysis/https-physicshub-github-io-simulations-BouncingBall/vnvx2yhj7b?utm_source=search_console&form_factor=desktop&hl=it This is an article that explains what CLS is and how to solve it: https://web.dev/articles/cls?hl=it ### To Reproduce 1. Go to one of the interested URLs 2. Understand why the layout of the page is moved ### Expected behavior Check this article to understand why this is a problem: https://web.dev/articles/cls?hl=it ### Screenshots <img width="1157" height="792" alt="Image" src="https://github.com/user-attachments/assets/de3a8798-c7cb-452b-afee-3cc202c7690a" /> ### Additional context _No response_ ### Code of Conduct - [x] I agree to follow this project's **Code of Conduct**

Created: 2/8/2026

Yippee mentioned it would be nice to be able to use a chat command like "!sotw" inside the RL client chatbox, and then in response it would output a game message into your chatbox along the lines of: "The current SOTW is: skill name" The same behavior for a "!botm" command When an event is not active, the message should be "There is no SOTW event running now" and "There is no BOTM event running now" Link to the core chat commands plugin to see an implementation: https://github.com/runelite/runelite/blob/master/runelite-client/src/main/java/net/runelite/client/plugins/chatcommands/ChatCommandsPlugin.java

Created: 2/8/2026

## 🎋 Add New Japan Fact **Category:** Community Contribution - Fun Fact **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this interesting fact about Japan to our collection! ### The Fact > Japan has 'shuin' stamp books where visitors collect temple seals along with dates and handwritten calligraphy. ### 📝 Instructions 1. Open [`data/community-content/japan-facts.json`](../blob/main/data/community-content/japan-facts.json) 2. Add this fact to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add new japan fact` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/8/2026

## Important Note - Please read the [guidelines](https://github.com/orgs/WallGodds/discussions/159) first - Include the open-source program name(s) you are part of in your comment ## Issue Description <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/8891e0e3-8a20-49fe-bf3b-bcb1327ceb0f" /> This is Forget Password Page. Please update the existing Forget Password Page with the following: - Most of the components are already built. You need to follow layout as specified in the Figma file. - Link back to sign in with signin page You can find the file in the codebase here: AuthModule - Make the changes directly inside this file Reference: Check the [design.md](https://github.com/WallGodds/WallGodds-Web/blob/main/DESIGN.md) file in the repository to get your hands on the Figma design file. Ensure the layout, spacing, icons, and typography strictly follow the provided design. If you face any issues while working on this page or have questions, feel free to reach out to us on [Discord](https://discord.gg/kTQ5KWANp8) — we’re always happy to help! .

Created: 2/8/2026 • 2 comments

## 🎬 Add Famous Anime Quote **Category:** Community Contribution - Anime Quote **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this iconic anime quote so learners can enjoy Japanese pop culture! ### The Quote | Japanese | Romaji | English | |----------|--------|---------| | **このジョルノ・ジョバァーナには夢がある！** | Kono Joruno Jobana ni wa yume ga aru! | I, Giorno Giovanna, have a dream! | **Anime:** JoJo's Bizarre Adventure: Golden Wind **Character:** Giorno Giovanna ### 📝 Instructions 1. Open [`data/community-content/anime-quotes.json`](../blob/main/data/community-content/anime-quotes.json) 2. Add this anime quote object to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item ```json { "japanese": "このジョルノ・ジョバァーナには夢がある！", "romaji": "Kono Joruno Jobana ni wa yume ga aru!", "english": "I, Giorno Giovanna, have a dream!", "anime": "JoJo's Bizarre Adventure: Golden Wind", "character": "Giorno Giovanna" } ``` 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add anime quote` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/8/2026

In the PyNEST-NG branch, currently the `node` for which a parameter value is to be determined, is passed in by pointer at https://github.com/heplesser/nest-simulator/blob/9c6a1524ec680f36a626a555d371f4de49f8723e/libnestutil/dict_util.h#L42. Change this to pass the node as `const Node&`. This requires a non-trivial number of changes throughout the code, thus the issue. This issue *does not* block merging PyNEST-NG into master.

Created: 2/8/2026

These pages are very similar. We do not need to separate them. Also, when a pair is only watched, it’s not possible to see the configured DCA levels, which is not good. I would recommend to completely get rid of the `monitor="yes|no"` config option and leave only the `trade="yes|no"`. When the value is `no`, all information is still visble on the Traded Pairs page, with a warning about the pair not being traded.

Created: 2/8/2026

## 问题描述 `InternalMCPManagerAdapter` 类在构造函数中为 `MCPManager` 注册了 `connected` 和 `error` 事件监听器，但在 `cleanup()` 方法中没有移除这些监听器，导致内存泄漏。 ## 问题位置 `packages/endpoint/src/internal-mcp-manager.ts:34-42` ## 严重程度 Medium ## 影响范围 - 每次创建 `InternalMCPManagerAdapter` 实例都会注册新的事件监听器 - 调用 `cleanup()` 后，监听器仍然存在，阻止垃圾回收 - 长期运行的应用中，频繁创建和销毁实例会导致内存泄漏 ## 修复方案 在 `InternalMCPManagerAdapter` 类中： 1. 添加私有字段保存监听器引用： ```typescript private connectedHandler: (...args: unknown[]) => void; private errorHandler: (...args: unknown[]) => void; constructor(private config: EndpointConfig) { this.mcpManager = new MCPManager(); // 转换配置并添加到 MCPManager for (const [serviceName, serverConfig] of Object.entries( config.mcpServers )) { const mcpConfig = normalizeServiceConfig(serverConfig); this.mcpManager.addServer(serviceName, mcpConfig); } // 设置事件监听 this.connectedHandler = (data) => { console.info( `MCP 服务 ${data.serverName} 已连接，工具数: ${data.tools.length}` ); }; this.errorHandler = (data) => { console.error(`MCP 服务 ${data.serverName} 出错:`, data.error); }; this.mcpManager.on("connected", this.connectedHandler); this.mcpManager.on("error", this.errorHandler); } ``` 2. 在 `cleanup()` 方法中移除监听器： ```typescript async cleanup(): Promise<void> { // 移除事件监听器 this.mcpManager.off("connected", this.connectedHandler); this.mcpManager.off("error", this.errorHandler); await this.mcpManager.disconnect(); this.tools.clear(); this.isInitialized = false; } ``` ## 相关代码 ```typescript // packages/endpoint/src/internal-mcp-manager.ts:34-42 this.mcpManager.on("connected", (data) => { console.info( `MCP 服务 ${data.serverName} 已连接，工具数: ${data.tools.length}` ); }); this.mcpManager.on("error", (data) => { console.error(`MCP 服务 ${data.serverName} 出错:`, data.error); }); ``` ## 注意事项 - MCPManager 需要支持 `off()` 或 `removeListener()` 方法 - 如果 MCPManager 不支持移除监听器，考虑在 MCPManager 中添加此功能 - 修复后应添加测试验证监听器被正确移除

Created: 2/8/2026 • 2 comments

Created: 2/8/2026

Created: 2/8/2026

[vc]: #qAzlimL/rW/8T53U0t1fP5mdtRu+6kSqe63JNa1RLI0=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJraXQtZW1iZWRkZWQtd2FsbGV0LW5leHRqcy1ib2lsZXJwbGF0ZSIsInJvb3REaXJlY3RvcnkiOiJleGFtcGxlcy9uZXh0IiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL2Rhcmdvbjc4OS1mb3JnZS9raXQtZW1iZWRkZWQtd2FsbGV0LW5leHRqcy1ib2lsZXJwbGF0ZS9FWXlYVlFXUmo5c0VTclpQZHpISm55Q1NyUUFkIiwicHJldmlld1VybCI6ImtpdC1lbWJlZGRlZC13YWxsZXQtbmV4dGpzLWJvaWxlcnBsYXRlLnZlcmNlbC5hcHAiLCJuZXh0Q29tbWl0U3RhdHVzIjoiREVQTE9ZRUQiLCJsaXZlRmVlZGJhY2siOnsicmVzb2x2ZWQiOjAsInVucmVzb2x2ZWQiOjAsInRvdGFsIjowLCJsaW5rIjoia2l0LWVtYmVkZGVkLXdhbGxldC1uZXh0anMtYm9pbGVycGxhdGUudmVyY2VsLmFwcCJ9fV19 The latest updates on your projects. Learn more about [Vercel for GitHub](https://vercel.link/github-learn-more). | Project | Deployment | Review | Updated (UTC) | | :--- | :----- | :------ | :------ | | [kit-embedded-wallet-nextjs-boilerplate](https://vercel.com/dargon789-forge/kit-embedded-wallet-nextjs-boilerplate) |  [Ready](https://vercel.com/dargon789-forge/kit-embedded-wallet-nextjs-boilerplate/EYyXVQWRj9sESrZPdzHJnyCSrQAd) | [Preview](https://kit-embedded-wallet-nextjs-boilerplate.vercel.app), [Comment](https://vercel.live/open-feedback/kit-embedded-wallet-nextjs-boilerplate.vercel.app?via=pr-comment-feedback-link) | Dec 29, 2025 2:45pm | _Originally posted by @vercel[bot] in https://github.com/Dargon789/web-sdk/issues/275#issuecomment-3692897144_

Created: 2/8/2026

this endpoint should accept scripts and run then and return the output. We may start with any scripting language.

Created: 2/8/2026

## 🎌 Add Japanese Proverb (ことわざ) **Category:** Community Contribution - Proverb **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this traditional Japanese proverb to help learners understand Japanese wisdom! ### The Proverb | Japanese | Reading | English | |----------|---------|---------| | **出る釘は打たれる** | Deru kugi wa utareru | The nail that sticks out gets hammered down | > 💡 **Meaning:** Those who stand out may be criticized ### 📝 Instructions 1. Open [`data/community-content/japanese-proverbs.json`](../blob/main/data/community-content/japanese-proverbs.json) 2. Add this proverb object to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item ```json { "japanese": "出る釘は打たれる", "romaji": "Deru kugi wa utareru", "english": "The nail that sticks out gets hammered down", "meaning": "Those who stand out may be criticized" } ``` 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add new japanese proverb` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/8/2026