issues Search Results · language:Edge language:Python language:JavaScript language:JavaScript language:PHP language:HTML
Filter by
53M results
Status: Proposed · Scope: product-wide (mainline x86 + ARM/edge) — not limited to the ARM epic.
Context
CubeCOS is built on CentOS Stream 9. The ARM/edge work (#960) and base-OS validation (#967) recommend ...
Problem
The repo has a Product Face Result schema and runner, but no public template for a product_face_result object.
That weakens onboarding and repeatability: external operators can see how to create ...
- [ ] 1. 首頁的搜詢框,在askit的/capacity是{ status: available } 時,顯示範例問句,以及 提問 按鈕,結果的stream會在同一頁呈現。
- [ ] 2. 搜詢頁待研究
- [ ] 3. 對話頁右上角搜詢框待研究
- [ ] 4. 講者頁搜詢框待研究
Problem
Product Experience OS advertises broad product-surface coverage, but the current Product Face evidence profile taxonomy
is narrower than the surface taxonomy.
The factory can recognize or describe ...
Description: The current checkout process on the Enatega food delivery site exhibits inconsistency in the user
experience when selecting different payment methods. Specifically, when users choose the credit/debit ...
Problem
professional_design_process requires selected/rejected reference IDs, but the validator does not fully bind those IDs to
the actual reference/source/candidate sets.
That means the process can ...
Problem
Product Face PASS can still be accepted by the base Product Face result validator with evidence_kind=synthetic.
Synthetic evidence is useful for fixtures and smoke paths, but it must not be confused ...
Problem
product_delivery_quality_profile can declare required proofs with required_timing=before_promotion, but the factory does
not appear to enforce that timing as a real gate.
That creates a gap between ...
Summary
The /loom:release skill should detect missing CHANGELOG entries for recent release tags before cutting a new release, so
we never silently ship a version with no CHANGELOG entry.
Motivation
...
Summary
Reported by @itcat672 in #148. 🙏 On a host with ~6 network interfaces, the Network → Throughput chart plots every NIC as
two series (↓ in / ↑ out), so ~12 lines at once. Two pain points:
1. Isolating ...
bug
enhancement
good first issue
help wanted

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.