```

## Troubleshooting

### Common Issues

**Index Creation Fails**
- Verify OpenSearch cluster is accessible
- Check index permissions and mappings
- Ensure sufficient cluster resources

**Suggestions Not Appearing**
- Confirm documents are indexed: `suggester.refresh()`
- Check query formatting and filters
- Verify analyzer configurations

**Performance Issues**
- Increase thread pool size in SuggesterBuilder

    "annotated-doc>=0.0.2",
]

[project.urls]
Homepage = "https://github.com/fastapi/fastapi"
Documentation = "https://fastapi.tiangolo.com/"
Repository = "https://github.com/fastapi/fastapi"
Issues = "https://github.com/fastapi/fastapi/issues"
Changelog = "https://fastapi.tiangolo.com/release-notes/"

[project.optional-dependencies]
standard = [
    "fastapi-cli[standard] >=0.0.8",
    # For the test client

# Test with parts from, and to verify the report in:
# https://github.com/fastapi/fastapi/discussions/14177
# Made an issue in:
# https://github.com/fastapi/fastapi/issues/14247
from enum import Enum

from fastapi import FastAPI
from fastapi.testclient import TestClient
from inline_snapshot import snapshot
from pydantic import BaseModel, Field


class MessageEventType(str, Enum):
    alpha = "alpha"
    beta = "beta"

 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.CompatibilityFixStrategy} - Fixes Maven 4 compatibility issues</li>
 * </ul>
 *
 * <h3>Utility Classes</h3>
 * <ul>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.StrategyOrchestrator} - Coordinates strategy execution</li>

If your CL addresses an accepted proposal, mention the proposal issue number in
your release note in the form `/issue/NUMBER`. A link to the issue in the text
will have this form (see below). If you don't want to mention the issue in the
text, add it as a comment:
```
<!-- go.dev/issue/12345 -->
```
If an accepted proposal is mentioned in a CL but not in the release notes, it will be

import org.apache.maven.project.MavenProject;

/**
 * A build context that matches a Maven project to a given task segment, and the session to be used.
 * <p>
 * A note to the reader;
 * </p>
 * <p>
 * There are several issues/discussions regarding how "aggregator" plugins should be handled.
 * Read for instance http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle+Planning
 * </p>
 * <p>

    assertThat(statusLine.message).isEqualTo("")
    assertThat(statusLine.protocol).isEqualTo(Protocol.HTTP_1_1)
    assertThat(statusLine.code).isEqualTo(code)
  }

  // https://github.com/square/okhttp/issues/386
  @Test
  fun shoutcast() {
    val statusLine = parse("ICY 200 OK")
    assertThat(statusLine.message).isEqualTo("OK")
    assertThat(statusLine.protocol).isEqualTo(Protocol.HTTP_1_0)

    }

    @Test
    @DisplayName("Null resourceLoc is accepted but may cause issues later")
    void constructorNullResourceLoc() {
        // Null resourceLoc doesn't throw NPE immediately - it's stored and may cause issues when used
        // This test documents the current behavior
        SmbTreeConnection freshConnection = mock(SmbTreeConnection.class);

	sconfig.Net.TLS.Config.RootCAs = h.kconfig.TLS.RootCAs

	// These settings are needed to ensure that kafka client doesn't hang on brokers
	// refer https://github.com/IBM/sarama/issues/765#issuecomment-254333355
	sconfig.Producer.Retry.Max = 2
	sconfig.Producer.Retry.Backoff = (10 * time.Second)
	sconfig.Producer.Return.Successes = true
	sconfig.Producer.Return.Errors = true

import org.junit.jupiter.api.TestInfo;
import org.lastaflute.core.direction.exception.ConfigPropertyNotFoundException;

/**
 * Test for FessEnv
 * Note: Many tests are currently disabled due to ObjectiveConfig initialization issues
 * that require a full LastaFlute context
 */
public class FessEnvTest extends UnitFessTestCase {

    private FessEnv.SimpleImpl fessEnv;

    @Override