3. **Actively collaborate with us.** We commit real time and attention to everything we review. Low-effort submissions—where...

        isCanBeConsumed = true
        outgoing.artifact(localRepository) {
            builtBy(localPublish)
        }
    }

    if (signArtifacts) {
        // Otherwise we get
        // ask ':tooling-api:publishGradleDistributionPublicationToRemoteRepository' uses this output of task ':tooling-api:signLocalPublication'

If the response issues an authorization challenge, OkHttp will ask the [`Authenticator`](https://square.github.io/okhttp/5.x/okhttp/okhttp3/-authenticator/) (if one is configured) to satisfy the challenge. If the authenticator supplies a credential, the request is retried with that credential included.

				return nil, errors.New("MasterKeyID contains unsupported characters")
			}
		}
	}

	if config.XMLNS == "" {
		config.XMLNS = xmlNS
	}
	return &config, nil
}

// ApplyOptions ask for specific features to be enabled,
// when bucketSSEConfig is empty.
type ApplyOptions struct {
	AutoEncrypt bool
}

// Apply applies the SSE bucket configuration on the given HTTP headers and

   - If you edit, you’re a collaborator, not a reviewer, and cannot merge.

6. **Testing**:
   - Assume the submitter tested the code. If testing is unclear, ask for details (e.g., “How was this tested?”).
   - Reject untested PRs unless testing is infeasible, then assist with test setup.

## Tips for Success

             * -missing because we have tons of missing @returns and @param.
             * -serial because we don't use java serialization.
             */
            // don't even think about passing args with -J-xxx, oracle will ask you to submit a bug report :)
            // fail on all javac warnings.
            // TODO Discuss moving compileOptions.getCompilerArgs() to use provider api with Gradle team.

### 해결책 제안하기 { #suggest-solutions }

* 질문을 충분히 이해한 후에는 가능한 **답변**을 제공할 수 있습니다.

* 많은 경우, 질문자의 **근본적인 문제나 사용 사례**를 이해하는 것이 더 좋습니다. 그들이 시도하는 방법보다 더 나은 해결책이 있을 수 있기 때문입니다.

### 종료 요청하기 { #ask-to-close }

질문자가 답변을 하면, 여러분이 문제를 해결했을 가능성이 높습니다. 축하합니다, **여러분은 영웅입니다**! 🦸

* 이제 문제를 해결했다면, 질문자에게 다음을 요청할 수 있습니다.

    * GitHub Discussions에서: 댓글을 **답변**으로 표시하도록 요청하세요.

labels.chat_phase_fetch=Retrieving documents...
labels.chat_phase_answer=Generating answer...
labels.chat_messages_area=Chat messages
labels.chat_welcome_title=Ask and Discover.
labels.chat_welcome_description=Ask questions and I'll search through documents to find the answers you need.
labels.chat_step_intent=Analyze
labels.chat_step_search=Search
labels.chat_step_evaluate=Evaluate

4. Submit a pull request

    * It contains the `username` and `password` sent.

{* ../../docs_src/security/tutorial006_an_py310.py hl[4,8,12] *}

When you try to open the URL for the first time (or click the "Execute" button in the docs) the browser will ask you for your username and password:

<img src="/img/tutorial/security/image12.png">

## Check the username { #check-the-username }

Here's a more complete example.