Tag: #오픈소스

← All posts

• The Microphone the Server Did Not Hear: Bringing the Gemini Live API WebSocket Example Up to Date

  The Gemini Cookbook's WebSocket-based Live API getting started example sent microphone audio and screens using the deprecated mediachunks, cleared the playback queue at the end of each conversation turn, and played only

  2026-10-28 · 16 min read #오픈소스#오픈소스 기여#Gemini#Live API#Python

• Presenting Two Ways to Fix and Letting the Lead Choose: From v2.1.0 to v2.3.0 in the Kubeflow Trainer Installation Guide

  The Kubeflow Trainer installation guide pinned VERSION=v2.1.0 while instructing users further down the same page to use --set runtimes. and --set crds.enabled, which did not exist in that version's Helm chart. Because ch

  2026-10-28 · 12 min read #오픈소스#오픈소스 기여#Kubeflow#Helm#문서

• Asked for 10Gi, but the PVC was 11381663335 bytes: Documenting CDI filesystem overhead extras

  The CDI documentation stated when using spec.storage that it "requests a PVC large enough to hold both the image and the filesystem metadata," but it did not state the resulting byte sizes for the PVC and the disk image

  2026-10-28 · 13 min read #오픈소스#오픈소스 기여#KubeVirt#CDI#문서

• When the documentation still puts spec.running, deprecated 2 years ago, on the very first line: How a KubeVirt user guide PR was merged in ten days

  The VirtualMachine field spec.running in KubeVirt has been deprecated since v1.4.0 (merged in September 2024), and the API server returns a warning every time a VM containing this field is created or modified. However, t

  2026-10-28 · 14 min read #오픈소스#오픈소스 기여#KubeVirt#쿠버네티스#문서

• Pointer Address in Logs: How a Two-Line Log Fix in CDI Was Merged in 2 Days and 19 Hours

  In the function where CDI selects the filesystem headroom per storage class, there are two log lines stating that the storage class could not be found. Both passed the string storage class name directly to klog.V(3).Info

  2026-10-28 · 11 min read #오픈소스#오픈소스 기여#KubeVirt#CDI#Go

• CDI Didn't Know local-path: Twelve Lines That Closed a Two-Year, Eleven-Month-Old Issue

  Because KubeVirt's disk helper, CDI, did not recognize local-path-provisioner (rancher.io/local-path), which is the default storage for k3s and kind, the StorageProfile for StorageClasses using this provisioner was alway

  2026-10-28 · 16 min read #오픈소스#오픈소스 기여#KubeVirt#CDI#스토리지

• The operator that searched for an unused webhook every 6 seconds: How the KubeVirt upstream PR was merged in 2 days and 16 hours

  Counting the requests sent by virt-operator in the TT Lab cluster to the API server over 59 days as the operator's own metrics revealed 843,995 GET requests looking for a non-existent webhook, all resulting in 404. This

  2026-10-28 · 16 min read #오픈소스#오픈소스 기여#KubeVirt#쿠버네티스#오퍼레이터

• No functional change: Reassuring the reviewer that functionality remains the same

  For PRs that do not change behavior—such as renaming, moving files, or cleanup work—we write No functional change. In LLVM, there is a convention of appending the abbreviation NFC to the first line of a commit. This expr

  2026-10-27 · 5 min read #영어#영어 표현#오픈소스#PR 설명#리팩터링

• Fixes #1234: The first line of the PR description, the keyword to close issues

  If you write Fixes 1234 in a PR description, the issue is automatically closed when the PR is merged into the default branch. Since this is not a simple English sentence but a keyword read by GitHub, you must use the exa

  2026-10-27 · 6 min read #영어#영어 표현#오픈소스#PR 설명#GitHub

• Let me know if I'm missing something: A single line to keep the possibility open that my understanding is wrong

  When you think it is a bug but it might be intended behavior, append Let me know if I'm missing something to the end of your sentence. Meaning "Please let me know if I missed anything," it respects the other person's con

  2026-10-27 · 5 min read #영어#영어 표현#오픈소스#이슈#코드 리뷰

• Would you be open to ...?: A polite suggestion to ask for direction before submitting a PR

  Before sending a large change directly as a PR, you can use the phrase Would you be open to ...? to ask for the maintainer's intent. Because it means "Are you open to accepting...?", it makes a suggestion while acknowled

  2026-10-27 · 5 min read #영어#영어 표현#오픈소스#이슈#제안

• Happy to take a stab at this: When you step up to take on an issue

  When stepping up to say "I will give this a try" on an open source issue, the most natural one-liner is Happy to take a stab at this. Because take a stab at is an informal idiom meaning "to give something a try," it clea

  2026-10-27 · 6 min read #영어#영어 표현#오픈소스#이슈#오픈소스 기여

• As far as I can tell: Between Confidence and Humility, 「As far as I can tell」

  When you have found a cause but cannot be 100% sure, put As far as I can tell at the beginning of the sentence. Meaning "This is as far as I have verified, though there may be things I don't know," it conveys both the ba

  2026-10-27 · 5 min read #영어#영어 표현#오픈소스#이슈#코드 리뷰

• I can't reproduce this on ...: How to speak up without blaming others when something won't reproduce

  I can't reproduce this on ... is the expression to use when you cannot reproduce a bug reported by someone else in your own environment. The key is to convey only the fact that "it turns out differently in my environment

  2026-10-27 · 6 min read #영어#영어 표현#오픈소스#이슈#버그 보고

• What did you expect to happen: The Basics of Bug Reporting, Expected and Actual Behavior

  The core of a bug issue is "What did you expect, and what actually happened?" Kubernetes' bug reporting template also places "What happened?" and "What did you expect to happen?" right at the beginning. We will cover how

  2026-10-27 · 7 min read #영어#영어 표현#오픈소스#이슈#버그 보고