-
Notifications
You must be signed in to change notification settings - Fork 444
fix: API References links under the Modules documentation are resulting in a 500 Internal Server Error. #1754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: API References links under the Modules documentation are resulting in a 500 Internal Server Error. #1754
Conversation
@jay0815 is attempting to deploy a commit to the LlamaIndex Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: f67eb9a The changes in this PR will be included in the next version bump. This PR includes changesets to release 51 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@llamaindex/autotool
@llamaindex/cloud
@llamaindex/community
@llamaindex/core
@llamaindex/env
@llamaindex/experimental
llamaindex
@llamaindex/node-parser
@llamaindex/readers
@llamaindex/wasm-tools
@llamaindex/workflow
@llamaindex/anthropic
@llamaindex/clip
@llamaindex/cohere
@llamaindex/deepinfra
@llamaindex/deepseek
@llamaindex/fireworks
@llamaindex/google
@llamaindex/groq
@llamaindex/huggingface
@llamaindex/jinaai
@llamaindex/mistral
@llamaindex/mixedbread
@llamaindex/ollama
@llamaindex/openai
@llamaindex/perplexity
@llamaindex/portkey-ai
@llamaindex/replicate
@llamaindex/together
@llamaindex/vercel
@llamaindex/vllm
@llamaindex/voyage-ai
@llamaindex/astra
@llamaindex/azure
@llamaindex/chroma
@llamaindex/firestore
@llamaindex/milvus
@llamaindex/mongodb
@llamaindex/pinecone
@llamaindex/postgres
@llamaindex/qdrant
@llamaindex/upstash
@llamaindex/weaviate
commit: |
dafa294
to
467c812
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jay0815 great stuff thanks a lot!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@jay0815 validate-links already runs in CI as part of the vercel build. |
|
@marcusschiesser I activated the validate script and updated the logic for generating normalized links. Now, all links in MDX pass validation. |
a0a3af3
to
ab4ca9f
Compare
@jay0815 unfortunately the build fails with on vercel with an out of memory error |
I just checked that the build is doing |
![]() ![]() ![]() I found that this OOM issue is caused by a dramatic increase in the number of files to be converted. Based on the version prior to the current PR, I conducted a detailed analysis of the newly added files and discovered that the surge mainly comes from the API file in Additionally, I am concerned that the package-based API documentation feature I am developing might encounter similar issues, as it requires fully loading the content exposed by each package. We need to assess whether it is necessary to display the exposed |
Update link normalization logic to remove any trailing slash after stripping query parameters and hash fragments. This ensures that both "api/interfaces/MetadataFilter#operator" and "api/interfaces/MetadataFilter/#operator" are correctly normalized.
ab4ca9f
to
a5b35b6
Compare
yeah! build works thanks a lot @jay0815 |
Fixes: #1737
This PR fixed the issue where the mdx corresponding to API References in the documentation was not generated, and updated the documentation content based on historical code changes..
typedoc.json
to better match the files under packages.MDX
.papaparse
dependency.MDX
for the API links in the documentation.