GitHub Incident: Forks not being recognized, PRs automatically closed #16796
Replies: 4 comments 1 reply
-
This is interesting, it didn't seem to affect any other of my GitHub forks. I wonder what about LangChain triggered this, maybe it was some upper limit in number of outstanding forks. |
Beta Was this translation helpful? Give feedback.
-
Not sure what happened but looks like we're back! We've reopened as many of the closed PRs as we can. Unfortunately we're not able to do this for forks that we don't have write access to, so those contributors will have to reopen the PRs themselves. Apologies for the inconvenience! |
Beta Was this translation helpful? Give feedback.
-
I think I've seen a similar impact a while back when changing a repo visibility from public to private, or when touching permissions/branch protections, can't remember the details... |
Beta Was this translation helpful? Give feedback.
-
Hi folks, Vinay this side from India. I am actually new to this LLM and LangChain world and I was trying my hands on this langchain part and created a simple chatbot that will provide information based on Indian Budget documents. Here is the link - https://github.com/codysaint/streamlit-pdf-qa-langchain-app But as part of the response I also want the citation and url of the source/doc from where it fetched the answer as we see in the Bing Copilot. As of now I am trying it by modifying the prompt but unable to get proper results.
I will be grateful as to how I can achieve it. PFA the screenshot where 1st is my chatbot and 2nd is the output of Copilot with proper citation and urls pertaining to resources. |
Beta Was this translation helpful? Give feedback.
-
UPDATE:
Not sure what happened but looks like we're back! We've reopened as many of the closed PRs as we can. Unfortunately we're not able to do this for forks that we don't have write access to, so those contributors will have to reopen the PRs themselves. Apologies for the inconvenience!
ORIGINAL:
As of Jan 30, 2024 9:30am PST we're aware that most LangChain forks have stopped being recognized as forks, and the corresponding PRs have automatically been closed. We're in contact with the GitHub team to try and understand why this happened and how to fix it. We'll keep you updated, thanks for your patience!
Beta Was this translation helpful? Give feedback.
All reactions