Dependency Graph not showing any dependents when there should be #34687
-
My repo is only showing dependencies but not dependents. Other repos show in their dependency referencing my repo but it is not showing up as a dependent on mine. Here is my repo expecting dependents: https://github.com/cloudwego/hertz/network/dependents Here are some repos referencing my package and show in their dependency graph: |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 28 replies
-
I've searched some similar cases, which ends up a "run a job to redetect" to solve. Seems like an internal operation from Github?
Am I asking this question in the wrong place? If there is a correct way to raise this kind of question, please let me know~ Thanks! |
Beta Was this translation helpful? Give feedback.
-
@queenofcorgis Is there any progress on https://github.com/cloudwego/hertz/network/dependents? |
Beta Was this translation helpful? Give feedback.
-
Hello dear @queenofcorgis Is there any progress on https://github.com/cloudwego/hertz/network/dependents? I've heard that it seems to work just fine with a bit of backend manipulation, and this has been a problem for months now. Can help if you have time or I'll reintroduce an issue. best wishes. |
Beta Was this translation helpful? Give feedback.
-
I also see no dependents in myprojects. Even though I can see, that dataclass-rest depends on dataclass-factory |
Beta Was this translation helpful? Give feedback.
-
Hi there ! This has been opened as an internal Issue for our Dependency Graph team - it is on their radar, but there is no timeline. Will share updates when I have them. If there is anything you'd like to include in the Issue, please let me know. Otherwise, I appreciate your patience. |
Beta Was this translation helpful? Give feedback.
-
Hi there, Can I ask how github determines the repository associated with a particular dependency? I've encountered an issue which seems similar to those described above. The source code of the pytket python library is contained in this repository -> https://github.com/CQCL/tket One of the several repos I would expect to depend on this one is this Maybe this is caused by the less than ideal naming of the different repositories or the fact that setup.py is used to list the dependencies in the tket repository instead of Apologies for the long comment, any help with this would be much appreciated :) |
Beta Was this translation helpful? Give feedback.
-
I have the same issue on two of my projects, one Python (pyngrok), one Java (java-ngrok). Neither show "Depends" or "Used By". My Python package is using setup.py and not pyproject.toml, but I know of other packages that haven't migrated that still show a Used By (example). Any update on this? Is GitHub just not supporting Dependabot anymore? I tried opening a support ticket, no response. |
Beta Was this translation helpful? Give feedback.
-
Hi there - the team that worked on this reported that this should be fixed - please let me know if this is the case for y'all. |
Beta Was this translation helpful? Give feedback.
-
This hasn't updated for my project yet either. Thanks for looking into this. |
Beta Was this translation helpful? Give feedback.
-
Our repo at https://github.com/PreTeXtBook/pretext-cli/network/dependents shows no dependents for the |
Beta Was this translation helpful? Give feedback.
-
Unfortunately same here https://github.com/betalgo/openai |
Beta Was this translation helpful? Give feedback.
-
Is there a way to mark this as unanswered as it seems to not be working for multiple users still? |
Beta Was this translation helpful? Give feedback.
-
Hi everyone - thanks for your patience and for coming to the community after some more digging I've gotten more clarity. These fixes are actually more successful when done on a case-by-case basis so if you are seeing this issue, you will have to open up a support ticket. Be sure to include which repository(ies) is/are affected in your ticket. Thanks again! |
Beta Was this translation helpful? Give feedback.
Hi everyone - thanks for your patience and for coming to the community after some more digging I've gotten more clarity. These fixes are actually more successful when done on a case-by-case basis so if you are seeing this issue, you will have to open up a support ticket. Be sure to include which repository(ies) is/are affected in your ticket. Thanks again!