Reporting a Reproducible Software Bug | Learn Korean in English

Korean lesson set in a contemporary Seoul everyday setting: In a software support exchange, a customer reports a reproducible export problem and asks how to share safe sample data..

EN → KO / Level: B2

10 minutes free every day

Continue audio lessons in the app

Word explanations appear automatically in sync with the audio.

No login required · synced translations · playback with the screen locked

Choose your learning language and open this lesson in the app.

Kotobridge app audio lesson and word notes

About This Lesson

Use Reporting a Reproducible Software Bug to practice Korean conversation, pronunciation, vocabulary, grammar, and quizzes.

Dialogue

A

필터링된 결과를 포함하면 내보내기 기능이 항상 실패합니다.

pil-tuh-RING-dwen kyul-GWAH-rul poh-ham-ha-MYUN nae-boh-NAE-gee gee-NEUNG-ee hang-SANG shil-PAE-ham-nee-DAH. The export feature fails whenever I include filtered results.
B

재현 가능한 문제로 보여서 문제를 훨씬 쉽게 해결할 수 있겠네요.

jae-HYUN gah-NEUNG-han moon-JAE-ro boh-YUH-suh moon-JAE-rul hwuhl-SSIN SHWEEP-kay hae-GYUL-hal soo it-GET-nay-yo. That sounds reproducible, which makes troubleshooting much easier.
A

필터를 적용하지 않은 데이터로 테스트했는데, 내보내기가 정상적으로 작동했습니다.

pil-tuh-rul juhk-yong-ha-jee ah-neun DAY-tuh-ro TEH-stuh-haen-neun-day, nae-boh-NAE-gee-gah jung-sang-juh-ro jak-TTONG-haet-seum-nee-DAH. I tested it with unfiltered data, and export worked normally.
B

그렇다면 필터 로직이 내보내기 모듈과 상호 작용하고 있을 수 있습니다.

guh-ruh-ta-MYUN pil-tuh ROH-jik-ee nae-boh-NAE-gee moh-DYOOL-gwah sang-hoh jah-gyong-ha-go ee-SSEUL soo it-seum-nee-DAH. Then the filter logic may be interacting with the export module.
A

민감한 정보가 없는 샘플 파일을 보내드릴 수 있습니다.

min-GAM-han jung-BOH-gah uhm-neun SAEM-peul pah-EEL-rul boh-nae-DUH-ril soo it-seum-nee-DAH. I can send a sample file without sensitive information.
B

그러면 안전하게 문제를 분리해 확인하는 데 도움이 되겠습니다.

guh-ruh-MYUN an-JUH-na-gay moon-JAE-rul bool-lee-hae hwah-GIN-ha-neun day doh-OO-mee dweh-GET-seum-nee-DAH. That would help us isolate the issue safely.
A

로그에 사적인 내용이 포함되어 있는지 확인해 주세요.

roh-GUH-eh sah-JUH-gin nae-YONG-ee poh-ham-dweh-uh in-neun-jee hwah-GIN-hae JOO-seh-yo. Please confirm whether logs include any private content.
B

로그를 요청하기 전에 제가 먼저 확인하겠습니다.

roh-GUH-rul yoh-CHUNG-ha-gee juh-neh jeh-GAH MUHN-juh hwah-GIN-ha-geh-sseum-nee-DAH. I will verify that before requesting the logs.

Sentence explanations

  1. 필터링된 결과를 포함하면 내보내기 기능이 항상 실패합니다.

    The export feature fails whenever I include filtered results.

    필터링된
    filtered
    결과
    results
    포함하면
    if/when including
    내보내기
    export
    기능
    feature
    항상
    always
    실패합니다
    fails
    More detail

    필터링된 means “filtered” here and describes 결과. It comes from 필터링되다 (“to be filtered”): 필터링된 is the form used before a noun for a completed or resulting state. The active verb 필터링하다 means “to filter,” while 필터링되다 presents the results as receiving that action. 결과 means “result” or “results.” Korean nouns do not generally require a plural ending, so the form can refer to one or more results when the context supports it. Example: 결과를 확인합니다. — “I check the results.” 포함하면 is 포함하다 (“to include”) plus -면, a conditional or “when/if” ending. In this sentence, the understood subject of including is the speaker, as reflected by the translation: “when I include.” The clause 필터링된 결과를 포함하면 therefore means “when I include the filtered results.” Example: 파일을 포함하면 오류가 납니다. — “When I include the file, an error occurs.” 내보내기 means “export.” It is a noun formed from 내보내다 (“to send out” or “to export”) with -기, which turns a verb into an activity name. This makes it suitable for naming a software function, as in “the export.” 기능 means “feature” or “function.” Together, 내보내기 기능 is “the export feature”; 기능 is the noun that identifies 내보내기 as a software function. 항상 means “always.” Here it states that the failure consistently occurs under the condition in the preceding clause. Combined with -면, it supports the natural translation “whenever,” rather than merely describing one possible occurrence. 실패합니다 means “fails” in this sentence. Its base verb is 실패하다 (“to fail”), and -ㅂ니다 is a formal polite declarative ending. The subject is 내보내기 기능, so the export feature is what fails; the sentence does not say that the speaker fails. The full structure is 필터링된 결과를 포함하면 (“when I include the filtered results”) + 내보내기 기능이 (“the export feature”) + 항상 실패합니다 (“always fails”). Thus the utterance means: “The export feature fails whenever I include filtered results.”

  2. 재현 가능한 문제로 보여서 문제를 훨씬 쉽게 해결할 수 있겠네요.

    That sounds reproducible, which makes troubleshooting much easier.

    재현 가능한
    reproducible
    문제
    problem
    보여서
    because it seems
    훨씬
    much more
    쉽게
    easily
    해결할
    solve
    수 있겠네요
    it seems possible
    More detail

    재현 가능한 means “reproducible” here. 재현 is “reproduction” or “re-creation,” and 가능한 is the noun-modifying form of 가능하다 (“to be possible”). Together, 재현 가능한 + noun describes something that can be reproduced. Example: 재현 가능한 오류 means “a reproducible error.” The first 문제 means “problem” or “issue.” In 재현 가능한 문제로, it is the noun described by 재현 가능한. The particle 로 presents the noun as what something appears to be: 문제로 보이다 means “to appear to be a problem.” 보여서 comes from 보이다 (“to seem” or “to appear”) plus -어서, which links a reason or cause. Here, 재현 가능한 문제로 보여서 means “because it seems to be a reproducible problem.” The form 보여서 expresses the reason for the conclusion that follows. The second 문제 is the same noun, but here it is followed by 를, the object marker: 문제를 means “the problem” as the object of the later action. The noun itself does not change; 를 shows its grammatical role. 훨씬 is an intensifier meaning “much” or “far,” used to strengthen a comparison. It commonly appears with a comparative idea such as “easier,” “faster,” or “better.” 쉽게 is the adverbial form of 쉽다 (“to be easy”). The ending -게 turns this descriptive word into an adverb: 쉽다 → 쉽게, “easy” → “easily.” Example: 이 문제를 쉽게 풀 수 있어요. means “I can solve this problem easily.” 해결할 comes from the verb 해결하다 (“to solve” or “to resolve”). It is the form used before 수 in the ability pattern -ㄹ/을 수 있다: 해결할 수 있다 means “can solve.” The form 해결할 is not the plain present form; it modifies the following 수. 수 있겠네요 combines 수 있다 (“can; it is possible”) with -겠네요, which conveys an inference or a newly recognized conclusion in a polite conversational style. Here, 해결할 수 있겠네요 means “it seems we can solve it.” Putting the parts together, 재현 가능한 문제로 보여서 gives the reason, “because it seems to be a reproducible problem,” and 문제를 훨씬 쉽게 해결할 수 있겠네요 gives the inferred result, “it seems we can solve the problem much more easily.” The whole utterance therefore means: “That sounds reproducible, which makes troubleshooting much easier.”

  3. 필터를 적용하지 않은 데이터로 테스트했는데, 내보내기가 정상적으로 작동했습니다.

    I tested it with unfiltered data, and export worked normally.

    필터
    filter
    적용하지 않은
    not applied
    데이터로
    with data
    테스트했는데
    tested it, and
    내보내기가
    export
    정상적으로
    normally
    작동했습니다
    worked
    More detail

    필터 means “filter” here. It is a noun; in a technical context it can name a feature or rule that selects or excludes data. The particle 를 in 필터를 marks it as the object of the following action. 적용하지 않은 describes the data as not having the filter applied to it. Its base verb is 적용하다 (“to apply”): 적용하지 않다 means “not apply,” and 적용하지 않은 is the form used before a noun, meaning “that was not applied” or, with this construction, “to which [it] was not applied.” The omitted actor is not specified in this phrase. 데이터로 means “with data” or “using data.” 데이터 is the noun “data,” and -로 marks the means or material used. Together, 필터를 적용하지 않은 데이터로 means “using data without the filter applied.” 테스트했는데 comes from 테스트하다, “to test.” The past stem form 테스트했- combines with -는데, a connective ending that links this clause to what follows. Here the connection is naturally translated as “I tested it, and …” The subject is understood rather than written in this Korean sentence; the fixed translation identifies it as “I.” Unlike the formal polite ending in 테스트했습니다, the observed -는데 form itself is a connective form, not that formal polite ending. 내보내기가 uses 내보내기, a noun meaning “export” or “exporting,” from 내보내다, “to export” or “to send out.” The subject particle -가 marks exporting as the thing that worked. This is a useful pattern for treating an action as a noun: 내보내다 → 내보내기. 정상적으로 is an adverb meaning “normally,” “properly,” or “as expected” in this context. It describes how the export function operated, not whether the data itself was normal. The related adjective-like form 정상적이다 means “to be normal/proper,” and -으로 forms the manner adverb here. 작동했습니다 comes from 작동하다, “to operate” or “to function.” 작동했다 is the past form, and 작동했습니다 is its polite formal past form. Thus 내보내기가 정상적으로 작동했습니다 says that the export function operated normally. Example: 프로그램이 정상적으로 작동했습니다. means “The program operated normally.” Putting the parts together, 필터를 적용하지 않은 데이터로 specifies the test material, 테스트했는데 says that the speaker tested it, and 내보내기가 정상적으로 작동했습니다 reports the result: “I tested it with unfiltered data, and export worked normally.”

  4. 그렇다면 필터 로직이 내보내기 모듈과 상호 작용하고 있을 수 있습니다.

    Then the filter logic may be interacting with the export module.

    그렇다면
    then; in that case
    필터
    filter
    로직
    logic
    내보내기
    export
    모듈
    module
    상호 작용하고
    interacting
    있을 수 있습니다
    may be
    More detail

    그렇다면 means “then” or “in that case.” It connects this statement to the preceding condition or information. 그러면 is a common alternative with a similar function; the conditional element -다면 gives 그렇다면 its “if that is so” sense. 필터 means “filter.” It is a noun, and it appears here as part of the compound 필터 로직, “filter logic.” The following subject marker 이 marks the entire noun phrase as the subject; it does not make 필터 an adjective. 로직 means “logic,” especially the logic implemented in a program or system. In 필터 로직이, 로직 is the head noun and 이 marks it as the subject. A useful related technical expression is 처리 로직, “processing logic,” but that is a separate example, not a description of the supplied conversation. 내보내기 means “export.” It is a noun formed from the verb 내보내다, “to send out” or “export.” Korean uses the -기 form to turn a verb into a noun, as in 저장하기, “saving.” Here 내보내기 modifies 모듈 in the compound 내보내기 모듈. 모듈 means “module.” In 내보내기 모듈과, the particle 과 marks the module as the thing that the filter logic interacts with. 과 is used after a consonant-final noun; after a vowel-final noun, the corresponding particle is 와. 상호 작용하고 means “interacting.” The base expression is 상호 작용하다, “to interact.” The ending -고 links this verb form to the following part of the predicate. The phrase 상호 작용하다 is written with a space between 상호 and 작용하다 here; it should not be treated as an inflection of 모듈 or 로직. 있을 수 있습니다 expresses “may be” or “can possibly be.” Its base pattern is -을 수 있다, which expresses possibility, followed here by the polite formal form 있습니다. In this sentence, 상호 작용하고 있을 수 있습니다 combines progressive -고 있다 (“be interacting”) with possibility -을 수 있다 (“may be”), so it presents the interaction as a possible ongoing process rather than a confirmed fact. For example, 지금 실행하고 있을 수 있습니다. means “It may be running now.” Putting the parts together: 그렇다면 sets the conclusion as “then/in that case”; 필터 로직이 makes “the filter logic” the subject; 내보내기 모듈과 identifies “the export module” as the thing it interacts with; and 상호 작용하고 있을 수 있습니다 says that this interaction may currently be occurring. The whole utterance therefore means: “Then the filter logic may be interacting with the export module.”

  5. 민감한 정보가 없는 샘플 파일을 보내드릴 수 있습니다.

    I can send a sample file without sensitive information.

    민감한
    sensitive
    정보
    information
    없는
    without; having none
    샘플
    sample
    파일
    file
    보내드릴 수 있습니다
    can send
    More detail

    민감한 means “sensitive” here and is the noun-modifying form of 민감하다 (“to be sensitive”). It appears before the noun it describes. For example, 민감한 정보 means “sensitive information.” 정보 means “information.” It is a noun and can be used in noun phrases such as 개인 정보 (“personal information”). Here, it is the information that is absent. 없는 is the noun-modifying form of 없다 (“to be absent; not to exist; not to have”). In 민감한 정보가 없는 샘플 파일, the pattern N이/가 없는 N means “an N without [the first N]” or “an N that does not contain [the first N].” The particle 가 marks 민감한 정보 as the subject of 없다. 샘플 means “sample.” It functions as a noun modifying the next noun in 샘플 파일, “sample file.” 파일 means “file.” In 샘플 파일, it is the head noun: the sample file is the item being sent. 보내드릴 수 있습니다 is a formal polite way to say “can send.” 보내드리다 combines 보내다 (“to send”) with 드리다, a deferential auxiliary used when the action is done for someone who is being treated respectfully. 보내드릴 has the -(으)ㄹ form required before 수 있다, and 있습니다 is the formal polite form of 있다. The construction V-(으)ㄹ 수 있다 expresses possibility or ability. For example, 자료를 보내드릴 수 있습니다 means “I can send you the materials.” Putting the parts together: 민감한 정보 is “sensitive information,” and 민감한 정보가 없는 샘플 파일 is “a sample file without sensitive information.” 보내드릴 수 있습니다 says that sending this file is possible, yielding “I can send a sample file without sensitive information.”

  6. 그러면 안전하게 문제를 분리해 확인하는 데 도움이 되겠습니다.

    That would help us isolate the issue safely.

    그러면
    then; in that case
    안전하게
    safely
    문제
    issue; problem
    분리해
    separate; isolate
    확인하는
    checking; confirming
    도움이 되겠습니다
    will be helpful
    More detail

    그러면 means “then” or “in that case” here. It links the current proposal or condition to a result, rather than simply marking chronological time. Example: 그러면 시작하겠습니다. — “Then, I will begin.” 안전하게 means “safely.” It is the adverbial form of 안전하다 (“to be safe”): 안전하다 → 안전하게. The ending -게 commonly turns a descriptive word into a form that describes how an action is done. Example: 파일을 안전하게 보관하세요. — “Please store the file safely.” 문제 means “issue” or “problem.” In this sentence it is the object being separated and checked. The object marker 를 follows it in 문제를; 문제 itself does not change form. Example: 문제를 설명해 주세요. — “Please explain the issue.” 분리해 means “separate and” or, in this context, “by isolating.” It comes from the verb 분리하다 (“to separate, isolate”); 분리해 is its connective form, linking this action to the following 확인하는. Example: 파일을 분리해 저장합니다. — “We separate the files and save them.” 확인하는 means “checking” or “confirming” here. It comes from 확인하다 (“to check, confirm”) plus the present attributive ending -는. This form modifies the following noun 데, creating 확인하는 데, “in checking” or “for checking.” Example: 내용을 확인하는 것이 중요합니다. — “Checking the content is important.” 도움이 되겠습니다 is the formal expression 도움이 되다 (“to be helpful”) with the prospective or intention-marking -겠- and polite ending -습니다. Here it presents the proposed method as something that would be helpful. 도움 is “help,” and 이 marks it as the subject of 되다; the form does not itself state an explicit Korean pronoun for the beneficiary. Example: 이 설명이 도움이 되겠습니다. — “This explanation will be helpful.” Together, 안전하게 문제를 분리해 describes isolating the issue safely, and 확인하는 데 도움이 되겠습니다 says that this would help with checking it. With 그러면 introducing the consequence, the whole utterance means: “That would help us isolate the issue safely.”

  7. 로그에 사적인 내용이 포함되어 있는지 확인해 주세요.

    Please confirm whether logs include any private content.

    로그
    logs
    사적인
    private
    내용
    content
    포함되어 있는지
    whether it is included
    확인해 주세요
    please check
    More detail

    로그 is the noun “log”; in this sentence it refers to the logs being checked. Korean nouns do not normally mark plural number, so 로그 can cover “a log” or “logs” when context supplies the number. 사적인 means “private” here. It is the attributive form of the descriptive word 사적이다 (“to be private/personal”), so it directly modifies 내용. Compare 사적인 정보 (“private information”) as a reusable pattern. The form describes the content, not the logs themselves. 내용 is the noun “content” or “contents.” 사적인 내용 therefore means “private content.” In Korean, 이 marks this noun phrase as the subject of the embedded question: the question is about whether private content is included. 포함되어 있는지 expresses “whether [something] is included.” 포함되다 means “to be included”; 포함되어 있다 presents that inclusion as an existing state, and -는지 turns the clause into an indirect yes-or-no question. Thus A가 포함되어 있는지 is a reusable pattern meaning “whether A is included.” 확인해 주세요 is a polite request meaning “please check/confirm.” It combines 확인하다 (“to check, confirm”) with -아/어 주세요, a request for the listener to perform an action; 하다 changes to 해 in this form. For example, 주소를 확인해 주세요 means “Please check the address.” Together, 로그에 sets the logs as the place or scope, 사적인 내용이 포함되어 있는지 asks whether private content is included there, and 확인해 주세요 politely requests that the listener verify it. The whole utterance means: “Please confirm whether the logs include any private content.”

  8. 로그를 요청하기 전에 제가 먼저 확인하겠습니다.

    I will verify that before requesting the logs.

    로그
    logs
    요청하기 전에
    before requesting
    제가
    I
    먼저
    first
    확인하겠습니다
    will verify
    More detail

    로그 is the noun “logs.” The object marker 를 appears in 로그를, marking the logs as what will be requested. A useful pattern is [noun]을/를 요청하다 = “to request [a noun].” 요청하기 전에 means “before requesting.” 요청하다 is the base verb “to request”; 요청하기 uses -기 to turn the verb into an activity or event, and 전에 means “before” that activity. This pattern is reusable: V-기 전에 = “before doing V.” Example: 출발하기 전에 확인하세요. — “Check before departing.” 제가 means “I” as the subject here. It is the humble first-person pronoun 저 combined with the subject particle 가; 저 + 가 contracts to 제가. This form identifies the speaker as the person who will perform the verification. The subject particle is different from the topic particle in forms such as 저는, which presents “I” as a topic rather than marking the subject in this way. 먼저 is the adverb “first” or “beforehand.” Here it says that the verification happens first, before the requesting action. It is separate from 전에: 전에 establishes the “before” relation, while 먼저 emphasizes the order. 확인하겠습니다 means “will verify.” Its base verb is 확인하다, “to check or verify.” The ending -겠습니다 expresses a formal, polite prospective commitment or intention, so 확인하겠습니다 is a formal-polite way to say “I will check/verify.” It is not the past form; a past form would use a different ending, such as 확인했습니다 for “checked.” Together, 로그를 요청하기 전에 sets the condition and timing: before requesting the logs. 제가 먼저 identifies the speaker as the one who acts first, and 확인하겠습니다 states the speaker’s formal commitment to verify. In the supplied context, 그것 is understood through the fixed translation as the matter of whether the logs contain private content: “I will verify that before requesting the logs.”

Grammar Points

-(으)면

필터링된 결과를 포함하면 기능이 항상 실패합니다.

pil-tuh-RING-dwen kyul-GWAH-rul poh-ham-ha-MYUN gee-NEUNG-ee hang-SANG shil-PAE-ham-nee-DAH.

If I include the filtered results, the feature always fails.

Attach -(으)면 to a verb to express a condition: “if” or “when.”

-기 전에

요청하기 전에 먼저 로그를 확인해 주세요.

yoh-CHUNG-ha-gee juh-neh MUHN-juh roh-GUH-rul hwah-GIN-hae JOO-seh-yo.

Please check the logs first before requesting.

Attach -기 전에 to a verb to mean “before doing something.”

Korean Vocabulary

결과 noun
KYUL-gwah results

필터링된 결과

기능 noun
gee-NEUNG feature; function

내보내기 기능

내보내기 noun
nae-boh-NAE-gee export; exporting

내보내기 기능

문제 noun
moon-JAE problem; issue

재현 가능한 문제

쉽게 adv
SHWEEP-kay easily

쉽게 해결하다

실패합니다 verb
shil-PAE-ham-nee-DAH fails

기능이 항상 실패합니다

재현 가능한 adj
jae-HYUN gah-NEUNG-han reproducible

재현 가능한 문제

포함하면 verb
poh-ham-ha-MYUN when including; if I include

결과를 포함하면

필터링된 adj
pil-tuh-RING-dwen filtered

필터링된 결과

항상 adv
hang-SANG always

항상 실패합니다

해결할 verb
hae-GYUL-hal to solve; to resolve

문제를 해결할 수 있다

훨씬 adv
hwuhl-SSIN much; far

문제를 훨씬 쉽게 해결하다

Quiz

Word Order

Arrange the words in the correct order.

I will verify that before requesting the logs.

Show Answer로그를 요청하기 전에 제가 먼저 확인하겠습니다.

Spelling

Tap the letters to spell the word.

filtered

Show Answer필터링된

when including; if I include

Show Answer포함하면

export; exporting

Show Answer내보내기

fails

Show Answer실패합니다