# Page Not Found

The URL `files/InsgN9ohPt4oePAPUX53` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [350. Intersection of Two Arrays II](https://longxingtan.gitbook.io/mle-interview/01_leetcode/03_hash/350.-intersection-of-two-arrays-ii.md)
- [优先队列/堆](https://longxingtan.gitbook.io/mle-interview/01_leetcode/06_heap.md)
- [4. Median of Two Sorted Arrays](https://longxingtan.gitbook.io/mle-interview/01_leetcode/00_binary_search/4.-median-of-two-sorted-arrays.md)
- [739. Daily Temperatures](https://longxingtan.gitbook.io/mle-interview/01_leetcode/dan-diao-zhan/739.-daily-temperatures.md)
- [380. Insert Delete GetRandom O(1)](https://longxingtan.gitbook.io/mle-interview/01_leetcode/03_hash/380.-insert-delete-getrandom-o-1.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://longxingtan.gitbook.io/mle-interview/01_leetcode/03_hash/350.-intersection-of-two-arrays-ii.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://longxingtan.gitbook.io/mle-interview/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://longxingtan.gitbook.io/mle-interview/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/mle-interview/01_leetcode/03_hash/350.-intersection-of-two-arrays-ii.md`).

You may also use `Accept: text/markdown` header for content negotiation.