Good First Issues in Mdx

Someone submitted the contact form! URL: https://usaco.guide/plat/geo-pri Module: Platinum - Geometry Primitives Topic: Mistake Message: the link to the ioi problem "The Troublesome Frog" does not seem to be working for me.

The English cheat sheet at docs/intro/CheatSheet.mdx has a few entries that are out of date for Helm 4, plus some small mistakes. These came up while reviewing the French translation in #2260, which already fixes several of them. What needs to change Remove helm list --all. Helm 4 no longer has this flag. Plain helm list now shows releases in every status (see pkg/cmd/list.go in helm v4.3.0). Update the helm list description. It should say that by default it lists releases in any status. Update the helm list --deployed description. Remove "If no other is specified, this will be automatically enabled", which is no longer true. It should just say that it shows only deployed releases. Replace --dry-run with --dry-run=client in helm install <name> <chart> --dry-run --debug. A bare --dry-run is deprecated in Helm 4 and prints --dry-run is deprecated and should be replaced with '--dry-run=client'. Also drop the stray (p) from that line's comment. Add the missing argument to --values: helm u

Someone submitted the contact form! URL: https://usaco.guide/problems/kattis-gmo/user-solutions Module: Problem Solution - GMO (ID: kattis-gmo) Topic: Request - Missing Section or Solution Message: There is no official solution for this particular problem and i think it is very important for the learners to have the solution when they are stuck. Even in the public solutions, there are just 2 solutions except mine and they are using DP in bronze which is not good for the new comers. So, i have proposed a basic brute force solution which is best for learning which you can consider.

Someone submitted the contact form! URL: https://usaco.guide/bronze/ad-hoc Module: Bronze - Ad Hoc Problems Topic: Request - Missing Section or Solution Message: focus problem explanation missing

Someone submitted the contact form! URL: https://usaco.guide/plat/range-sweep Module: Platinum - Range Queries with Sweep Line Topic: Request - Missing Section or Solution Message: I need solution for Robot Path

SDK PHP SDK Description Page: https://docs.sentry.io/platforms/php/logs/ SDK version: sentry/sentry 4.30 Problem The PHP Logs docs show constructing the Monolog logs handler with a Hub (and level) argument $handler = new \Sentry\Monolog\LogsHandler($hub, Level::Info); This signature does not exist in sentry/sentry 4.30. LogsHandler does not accept a Hub in its constructor, so following the docs as written fails. What works instead (4.30) $log->pushHandler(new \Sentry\Monolog\LogsHandler(Level::Info)); The handler uses the current hub from the initialized SDK; no Hub argument is needed. Request Please update the Logs page to match the 4.x LogsHandler signature, or clarify which SDK version the current example targets. Suggested Solution $log->pushHandler(new \Sentry\Monolog\LogsHandler(Level::Info));

While adding anchor IDs in PR #2216, i18n/fr/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md had all 18 section headings and all 18 table-of-contents entries changed from French to English. For example: -## Fonctions de chaînes de caractères +## String Functions {#string-functions} -* [Chaînes de caractères](#fonctions-de-chaînes-de-caractères) +* [String](#string-functions) The page body remains French, so the page now reads as English headings and English TOC over French prose. Why this isn't required The anchor convention only pins the ID, not the heading text. From community/localization.md: Add anchor IDs to any headings using the format ## Example Heading {#example-anchor-id}. The anchor IDs must be English language and match the anchor IDs of the corresponding heading in the English doc page. For example, ## 后端存储 {#storage-backends} matches ## Storage backends {#storage-backends}. The other four files touched in the same PR do exact

Someone submitted the contact form! URL: https://usaco.guide/problems/joi-2020stray-cat/solution Module: Solution: JOI - 2020 - Stray Cat Topic: Mistake Message: image is not displaying

URL docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/anr/event-loop-block/ Additional Info No response

2026-07-22.14-19-56.mp4 Accessibility (a11y) Guideline: Minimum Icon Size & Touch Target Minimum Icon Dimensions (WCAG 2.5.8 - Target Size): Ensure interactive elements and their icons do not shrink below 16px (1em) on mobile devices or smaller viewports to maintain visual legibility and prevent layout collapse. Touch Target Spacing: While visual icons may scale down to 16px to fit narrow screens (<400px), the interactive container/touch target must maintain an adequate hit area to assist users with motor impairments or touch interfaces.

Someone submitted the contact form! URL: https://usaco.guide/gold/gold-conclusion Module: Gold - Additional Practice for USACO Gold Topic: Request - Missing Section or Solution Message: You haven't written a solution for Flowers problem in the Additional Practice for Gold Section, and i think it is needed for me and perhaphs, someone else.

The code example in the sendDefaultPii deprecation section shows httpHeaders as a flat CollectBehavior value: httpHeaders: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, But the actual DataCollection TypeScript type (verified in @sentry/[email protected]) defines httpHeaders as a nested per-direction object: httpHeaders?: { request?: CollectBehavior; response?: CollectBehavior; }; Passing { deny: [...] } directly causes a TypeScript error because deny is not a valid key on { request?, response? }. Workaround — use the nested form: httpHeaders: { request: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, response: { deny: ["forwarded", "-ip", "remote-", "via", "-user"] }, }, cookies and queryParams use CollectBehavior directly and are correct in the example. Only httpHeaders is wrong. -- View Junior Session in Sentry

Stale Images: pricing Docs page: https://docs.sentry.io/pricing/Source file: docs/pricing/index.mdxStale screenshots: 1Stale Arcades: 0Priority: low What to do Open the docs page and compare each screenshot against the current Sentry UI For screenshots: recapture from the current UI and replace the image file For Arcades: re-record the interactive walkthrough and update the embed URL Ensure alt text is still accurate for any replaced images Commit and open a PR Notes This issue was auto-generated by the screenshot pipeline See the source MDX file for all image references Images are stored in the img/ folder next to the MDX file

At the end of each page, we have a "was this page helpful?" But it gives the feeling to the user that nothing is happening if we click on it we are supposed to be able to let the user give feedback, but it does not -> this is for enterprise plans ❌

Make sure people are aware of access control as this is a frequently asked question or frequently missed package https://tech.spiko.io/posts/stellar-integration/

A while ago I added a JSON schema for the configuration file to Schema Store. You can use this to validate your file. There are many options for CLIs and libraries for this. It would be good to have a section in the docs pointing this out and giving an example.

What problem does your feature solve? Developers building on Soroban need guidance on how to handle data migrations when their contract storage schema needs to change. While upgrading contract code is documented, migrating existing storage data is not covered. Reference: https://discord.com/channels/897514728459468821/966788672164855829/1463250846123819203 cc @tupui What would you like to see? Documentation covering data migration strategies for Soroban smart contracts, including: How to perform data migrations today (e.g., deploying a new contract version with migration code, running the migration, then potentially deploying another version to remove migration-only code) Best practices and patterns for structuring migration logic Reference to how other chains handle data migrations may be helpful (separate from any existing docs about migrating contracts from other chains to Soroban) What alternatives are there? Developers could figure this out on their own?