Good First Issues in HTML

The users report too much of a rainbow on variantS pages, making the actual score hard to read. 🦄 In a way, that is kind of pedagogical, as they tend to rely overly much on the absolute score with non-static rank models, but let's try to be helpful. How about colouring only the norm rank score perhaps? That's the one gating the color anyway.

This is a Bug Report Problem: The Dynamic Resource Allocation concept page was split into several pages under content/en/docs/concepts/resource-management/dynamic-resource-allocation/. A in-page link still point to anchors that moved to a different page, so clicking them does nothing. Proposed Solution: Replace the in-page anchors with full paths. In device-taints.md, [above](#admin-access) should link to /docs/concepts/resource-management/dynamic-resource-allocation/dra-api/#admin-access. Page to Update: https://kubernetes.io/docs/concepts/resource-management/dynamic-resource-allocation/device-taints/ /good-first-issue

When correcting disjointness I came across the term FrequencyMeasure. FrequencyMeasure was seemingly defined twice: Merge.kif (subclass FrequencyMeasure TimeDependentQuantity) (documentation FrequencyMeasure EnglishWrittenLanguage "A &%subclass of &%TimeDependentQuantity, instances of which are measures of the frequency with which some &%Process occurs.") and HouseholdApplicances.kif (subclass FrequencyMeasure ConstantQuantity) (documentation FrequencyMeasure EnglishWrittenLanguage "Instances of &%FrequencyMeasure are measures of frequency stated in units of &%UnitOfFrequency.")` While this is not technically an issue if parents are compatible, I feel uncomfortable having taxonomy definitions of a term within different files. Perhaps there are some circumstances where this might be beneficial, but I could see this being an issue while trying to package subontologies. I've thought of 3 possible solutions: We could introduce a termDefinition wrapper statement to increase clarity dur

Electricity is currently modeled as a substance. Its documentation states: (documentation Electricity EnglishWrittenLanguage "While electricity is typically thought of as just a difference in electrical potential, one way of modeling electricity is as a substance that can be moved from one point to another or consumed. One could make the claim that subatomic physics also supports the classification as a substance since electrons are objects.") This modeling choice is understandable as a useful abstraction. Treating electricity as a substance allows it to be represented as a resource that can be transferred, stored, or consumed without requiring the ontology to model the underlying electrical and subatomic processes in detail. For example, this may make reasoning about battery capacity or energy consumption substantially simpler. However, this raises a broader modeling question: Should SUMO prioritize physically accurate and granular representations, or abstractions that are more conv

This is a Bug Report Problem: I ran into this while researching a kubectl plugin idea for CronJobs: listing the next runs across a cluster, soonest first, in a chosen time zone, and flagging runs that were missed or skipped. Checking how the controller handles missed schedules, I found that the CronJob page says two things the controller does not do. Job creation says: If there are more than 100 missed schedules, then it does not start the Job and logs the error. and the example below it says: If the CronJob controller happens to be down from 08:29:00 to 10:21:00, the Job will not start as the number of missed Jobs which missed their schedule is greater than 100. The controller does start a Job. With more than 100 missed schedules it records a TooManyMissedTimes Warning event, then creates a Job for the most recent missed schedule, as it does when fewer were missed. The caution under Schedule suspension says: When .spec.suspend changes from true to false on an existing CronJob

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate partner_contact_sale_info_propagation - By @sudhir-erpharbor - #4609 partner_sale_pivot - By @sudhir-erpharbor - #4610 portal_sale_confirm_require_login portal_sale_list_extra_info portal_sale_order_search portal_sale_personal_data_only product_customerinfo_elaboration product_customerinfo_sale product_form_sale_link sale_advance_payment sale_automatic_workflow sale_automatic_workflow_job sale_cancel_reason sale_cancel_restrict sale_commercial_partner - By @GarethGloSystems - #4631 sale_company_currency sale_confirm_group sale_delivery_split_date sale_delivery_state sale_elaboration sale_elaboration_brand sale_exception sale_exception_line_tooltip sale_fixed_discount sale_force_invoiced sale_force_invoiced_quantity sale_fully_invoiced sale_global_discount sale_invoice_blocking - By @sudhir-erpharbor - #4615 sale_invoice_frequency - By @sudhir-erpharbor - #4616

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate account_fiscal_position_allowed_journal_purchase partner_supplierinfo_smartbutton procurement_purchase_no_grouping product_main_seller product_supplier_code_purchase purchase_advance_payment purchase_all_shipments purchase_allowed_product purchase_auto_bill_on_receipt purchase_default_terms_conditions purchase_delivery_split_date purchase_deposit purchase_exception purchase_force_invoiced purchase_invoice_method purchase_landed_cost purchase_last_price_info purchase_line_reassign purchase_no_rfq purchase_order_approved purchase_order_archive purchase_order_general_discount purchase_order_line_deep_sort purchase_order_line_description purchase_order_line_menu purchase_order_line_price_unit_digits purchase_order_line_sequence purchase_order_line_stock_available purchase_order_owner purchase_order_secondary_unit purchase_order_supplierinfo_update purchase_order_t

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate project_administrator_restricted_visibility project_department project_forecast_line project_group project_hr project_hr_expense_analytic project_kanban_form_direct_access project_key project_merge project_milestone_status project_parent project_parent_task_filter - By @sudhir-erpharbor - #1830 project_pivot project_sequence project_stage_extra_info project_tag_hierarchy project_tag_multicompany project_tag_security project_task_ancestor project_task_code project_task_customer_ref project_task_default_stage project_task_default_user project_task_description_template project_task_name_with_id project_task_note project_task_parent_due_auto project_task_personal_stage_auto_fold project_task_product project_task_product_stock project_task_pull_request project_task_pull_request_state project_task_stage_auto_state project_task_stage_lock project_task_stage_mgmt

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate mrp_attachment_mgmt mrp_bom_component_menu mrp_bom_image mrp_bom_note mrp_bom_tracking mrp_multi_level mrp_multi_level_estimate mrp_production_back_to_draft mrp_production_generator_by_date_interval mrp_production_note mrp_repair_order mrp_sale_info mrp_subcontracting_purchase_link mrp_subcontracting_skip_no_negative mrp_tag mrp_warehouse_calendar purchase_mrp_distribution quality_control_oca stock_replenishment_mrp_bom_selection Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate hr_course hr_department_code hr_employee_age hr_employee_calendar_planning hr_employee_document hr_employee_firstname hr_employee_language hr_employee_medical_examination hr_employee_partner_external hr_employee_relative hr_employee_second_lastname Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate account_billing account_global_discount account_invoice_clearing account_invoice_crm_tag account_invoice_discount_date account_invoice_fixed_discount account_invoice_merge account_invoice_pricelist account_invoice_pricelist_sale account_invoice_refund_code account_invoice_refund_link account_invoice_section_sale_order account_invoice_show_currency_rate account_invoice_tax_note account_invoice_transmit_method account_invoice_tree_currency account_invoice_triple_discount account_move_cancel_confirm account_move_pivot_view account_move_substate account_receipt_journal account_tax_fixed_amount_currency account_tax_fixed_amount_multiplier partner_invoicing_mode partner_invoicing_mode_at_shipping portal_account_personal_data_only product_form_account_move_line_link purchase_create_bill_button sale_invoicing_date_selection sale_order_invoicing_grouping_criteria sale_o

So far the howto doesn't say that the submission may fail even is it was validated locally. Improve the documentation describing the status enquiry button. This is how it is now:

Procedure Each of these dates should be checked to see if the docs they annotate are up-to-date. Each date should be updated (in the Markdown file where it appears) to use the current month (October 2026), or removed if the docs it annotates are not expected to fall out of date quickly. Please check off each date once a PR to update it (and, if applicable, its surrounding docs) has been merged. Please also mention that you are working on a particular set of dates so duplicate work is avoided. Finally, once all the dates have been updated, please close this issue. Dates src/backend/updating-llvm.md 2026-03 line 173 src/borrow-check/region-inference/member-constraints.md 2026-03 line 98 src/debuginfo/lldb-visualizers.md 2025-11 line 14 2025-11 line 118 2025-11 line 253 2025-11 line 285 2025-11 line 590 src/diagnostics/error-codes.md 2026-03 line 13 src/diagnostics/translation.md 2024-10 line 5 2024-10 line 11 src/feature-gate-check.md 2026-02 line 11 src/fuz

Not sure if bug or intended, but we get a question about this from our users every now and so: The search box for genes to add to dynamic panel on the case page is not triggered for gene symbols shorter than three chars. To add e.g. gene FH, our users have to look up the numeric hgnc-id and use that instead. Noted on scout version 4.112.0

There are still some single-cell tutorials that use old versions of EBI tools. Most of the missing functionality has been implemeted in IUC single-cell tools over time. training-material/topics/single-cell/tutorials$ grep -r -i ebi-gxa -l scrna-case_monocle3-trajectories/tutorial.md scrna-case_monocle3-trajectories/workflows/Trajectory-analysis-using-Monocle3---full-tutorial-workflow.ga scrna-case_monocle3-trajectories/workflows/Galaxy-Workflow-Monocle3_workflow.ga scrna-case_alevin-combine-datasets/workflows/Combining-datasets-after-pre-processing-ARCHIVE.ga scrna-case_trajectories/tutorial.md scrna-case_trajectories/workflows/inferring-trajectories-with-scanpy-workflow.ga pseudobulk-analysis/tutorial.md pseudobulk-analysis/workflows/pseudo-bulk_edgeR.ga scrna-case_FilterPlotandExplore_SeuratTools/tutorial.md scrna-case_FilterPlotandExplore_SeuratTools/workflows/workflow-seurat-filter-plot-explore.ga scanpy_parameter_iterator/tutorial.md scanpy_parameter_iterator/workflows/Scanpy-Para

Compare the Decipher browser:

The horizontal rules within cards on the working group pages don't line up well. They'd look nicer if they did. The workshops page has similar cards but better alignment, so could be a model to follow.

如图所示: 不是很懂这个变量命名的数学规范; (4.2) 不是很懂对 $t$ 指标求和从 $t=-4$ 到 $t$ 本身是什么新数学;

I want to be able to link to a working group on the quarkus.io site, but I can't, because clicking the card doesn't give me a unique link.

Description From 19 Oct, GH will start using an updated Ubuntu image for latest. We've been caught out by this kind of upgrade in the past. actions/runner-images#14748 We should see if we can get ahead of this with some tests Success Criteria Unit tests pass with the new-spec runner Integration tests pass with the new-spec runner

Problem When Codex runs through the conversion route, its JSONL stream includes lifecycle events such as thread.started and turn.started. It can also emit a nonfatal model-catalog refresh diagnostic on stderr and then continue successfully. The current adapter ignores the lifecycle start events and forwards the full diagnostic response body. The browser also marks a conversion as done whenever the SSE stream ends, even when the agent has a non-zero or missing exit code or produced no HTML. Together, this makes a run look stalled or successful without a reliable terminal state. Reproduction Run pnpm -F @html-anything/next dev. Select Codex and start any conversion. Observe a lifecycle diagnostic before the assistant output. Observe that completion is not derived from both the process exit code and generated HTML. Redacted real-session event shape: thread.started turn.started item.completed (diagnostic) item.completed (agent message) turn.completed Expected behavior Surface the Codex

Procedure Each of these dates should be checked to see if the docs they annotate are up-to-date. Each date should be updated (in the Markdown file where it appears) to use the current month (September 2026), or removed if the docs it annotates are not expected to fall out of date quickly. Please check off each date once a PR to update it (and, if applicable, its surrounding docs) has been merged. Please also mention that you are working on a particular set of dates so duplicate work is avoided. Finally, once all the dates have been updated, please close this issue. Dates src/backend/updating-llvm.md 2026-03 line 173 src/borrow-check/region-inference/member-constraints.md 2026-03 line 98 src/debuginfo/lldb-visualizers.md 2025-11 line 14 2025-11 line 118 2025-11 line 253 2025-11 line 285 2025-11 line 590 src/diagnostics/error-codes.md 2026-03 line 13 src/diagnostics/translation.md 2024-10 line 5 2024-10 line 11 src/feature-gate-check.md 2026-02 line 11 src/f

Quite a few of these translations might want revisiting. Translated pages inherit metadata from the English language versions, untranslated pages fall back fully to the English overlays. TODO: code language translated de Deutsch 18/246 es Español 127/246 fr Français 19/246 it Italiano 17/246 tr Türkçe 14/246 zh 中文 0/246 Chinese is a work in progress: #439

Current state: The job posting guide was written before we got our improved form; many of the things that is explicitely points out are not needed anymore. The suggestions for the intro and the closing statement probably do not work well with many communities, since they suggest adjective laden business language. Could be more terse to make it likely that posters actually read the whole text Suggestions: Go through the current form and how-to text and mark the parts that are explicity stated in the form for removal. Remove the intro and closing statement suggestions Review the whole text for what is essential and what could go (e.g. highlight in red and green, then edit). If you are really serious about improving the text, use paramedic editing

This is a task issue What needs doing Look at issue #28690 Look at pull request #55693 (if necessary) read the docs about contributing to Kubernetes docs Then, open a new pull request that makes a change equivalent to #55693. If you did that manually, credit @p1930n as the original author, and yourself. If you used any AI agent, mention the AI agent you used as well as your own identity and @p1930n. You will need to write a description for your pull request that helps people understand the change you are making and how to check it. Why is this needed PR #55693 is stale. Comments /language en /priority backlog /help /triage accepted

This is a Feature Request What would you like to be added Translate the following Kubernetes documentation page into Korean: English: https://kubernetes.io/docs/concepts/storage/ephemeral-storage/ Target file:  content/en/docs/concepts/storage/ephemeral-storage.md  Why is this needed Kubernetes Korean documentation includes content about local ephemeral storage within the resource-management documentation, but the dedicated documentation page is not currently available in Korean. As a result, users navigating directly to the localized page cannot access a Korean translation of the full content. Adding this translation would improve documentation completeness and accessibility for Korean-speaking Kubernetes users. Additional context The related Korean documentation page is: https://kubernetes.io/ko/docs/concepts/configuration/manage-resources-containers/#로컬-임시-ephemeral-스토리지 However, the standalone page corresponding to /docs/concepts/storage/ephemeral-storage/ still

please consider adding addTagOnEnter setting. I would like to remove option to have tag created on hitting enter. I tried to set addTagOn with empty array, but it does not seems to work. still tag is added

Topic and thanks.

This is a feature request Problem: The preview of the Kubernetes v1.37 docs for Pod level resource managers includes a page-level glossary, with entries for: Pod level resources specification Guaranteed container Exclusive slice Pod shared pool These definitions are only mentioned on that page. Proposed Solution: This issue proposes adding "Pod shared pool" to the main glossary. Additional Information: /help /language en /priority backlog If v1.37 has been released, the change to make will be against the main branch; otherwise, it will be against dev-1.37. AI agents working on this feature request should mention "This was submitted by an AI agent and has not been checked by a human" in the PR description.

This is a Bug Report Problem: The preview of the Kubernetes v1.37 docs shows that there is a section in the Gang Scheduling page, where that section doesn't align well with our style guide. Notable, our style guide says that API types (such CompositePodGroup) are written without backticks, not as teletype text. Proposed Solution: Fix the style discrepancies. This can happen at any time and doesn't block the v1.37 release. If v1.37 has been released, the fix will be against the main branch; otherwise, it will be against dev-1.37. Files to fix: content/en/docs/concepts/scheduling-eviction/podgroup-scheduling.md content/en/docs/concepts/scheduling-eviction/gang-scheduling.md content/en/docs/concepts/scheduling-eviction/topology-aware-scheduling.md content/en/docs/concepts/scheduling-eviction/workload-aware-preemption.md content/en/docs/concepts/workloads/compositepodgroup-api/_index.md content/en/docs/concepts/workloads/workload-api/policies.md content/en/docs/concepts/workloads/workl