Bug? Project not showing network dependents

The Network Dependents page of my library NaturalSort.Extension shows:

We haven’t found any dependents for this repository yet.
We’ll keep looking!

However, there are dependents which GitHub registers.

For example, this repository clearly lists my library inside its dependencies:

This means that GitHub registers the dependency correctly, but it’s only displayed on one side.

I noticed this same behavior in other projects, e.g. MinVer, which is used by many projects (including several of mine), is not showing any dependents either.

Is this a bug? Or am I understanding something wrong?

Thanks.

@tompazourek - Hey there! Thanks for raising this here. I, too, expect that dependent repositories are listed there, though I’m not quite sure on why it isn’t rendered.

On our end, I see that our engineers are tracking similar cases like this and just shared this instance with them so they can review this further. 

We’re sorry we don’t have a better solution for you nor a timeline for when this will be resolved. We do appreciate you raising visibility and if there are any other cases that you come across, we’re keen to pass those on to the team as well.

Sorry, but I cannot mark this as a “Solution”. Nothing has been done about this for over 6 weeks, even though you mentioned you have seen this issue. My problem has not been solved yet.

Is there at least a place I can visit to track this issue?

@tompazourek - Thanks for following up on this. I agree that neither my post nor this topic should be acknowledged as “Solved”. I can say that this behavior is unexpected and in need of a resolution.

Currently, we don’t have a public issue tracker for checking the status of its resolution, though I’m subscribed internally to the issue I originally opened with the team. If I hear anything new from our engineers, I’ll post back here. :+1:

From what I can tell, they’ve acknowledged that it is an issue but we aren’t able to offer a specific timeline for when it will be addressed.

In the meantime, it is possible for us to hide the Used By button for your repository (or repositories). If that’s something you’re interested in, we can reach out to you privately and take the next steps. Please let us know how you would like to proceed!

Thanks for getting back to me. I’m sad to hear there’s no way I can track this issue publicly. I can only hope that my issue gets prioritized at some point. If other people have this issue, is there some voting system or similar mechanism? Thanks for your help with this, any new information regarding this in the future will be appreciated!

Thanks for getting back to me. I’m sad to hear there’s no way I can track this issue publicly. I can only hope that my issue gets prioritized at some point.

I see where you’re coming from and I’d love to see us improve on this for the future. Our product team is always keen to hear feedback for how we can do better around improving our interfaces, including how we track and prioritize our work. You’re welcome to share any additional thoughts about this with them here:

https://support.github.com/contact/feedback

If other people have this issue, is there some voting system or similar mechanism? Thanks for your help with this, any new information regarding this in the future will be appreciated!

If other people are experiencing this reported issue, they are welcome to like your post by pressing the heart icon (:heart:) and take a moment to share their specific instance here including a URL. Seeing more cases like these would help signal impact and visibility to the team maintaining this feature, but the decision to work on a fix is beyond our scope (GitHub Support). Again, we can’t promise any timelines for a resolution, though we’ll do our best to help where a workaround or alternative approach exists. I hope this helps, @tompazourek!

2 Likes

:wave: Hello again, @tompazourek! One of our engineers reviewed this and observed that your repository’s Dependency Graph's Dependents tab shows a number of repositories and packages now. :tada:

If you’re still seeing any instances of this, we’re keen to review those case-by-case for our team to look into. :+1:

Hi again, @francisfuzz, I really appreciate getting back to me, thanks!

You’re right, one of the repositories has the packages now. That is great and thank you for that. There are number of other repositories that are still missing this. For example, my other project, the Colourful library. Or the MinVer project (not one of mine) that I already referenced in the original post.

I would appreciate a systematic solution, not on case-by-case basis. I’m sure that if I browse GitHub, I will find a lot of these issues where the dependency shows on one side, but is missing from the other side, and it’d be a pain to create a ticket for each occurrence of the issue.

We’re glad to be of help and we see where you’re coming from. We, too, would like to see this addressed across as many (if not all) instances where possible. Putting myself in your shoes, it’s a less-than-awesome experience to create one post for each occurrence. We hear you and our team is open to hearing about how we could make this experience better.

Each of these instances are bring more visibility into the issue and after Consulting with our engineers on this, I can confirm here that this is still a known and outstanding issue. The team is actively investigating it and while we can’t make any promises on a timeline for resolution, we’ll follow up here as soon as hear more from them. :bowing_man:

I’m also having the same issue with https://github.com/jobrunr/jobrunr

I created some example projects and I would expect them to be shown as dependant projects.

Not sure if this helps, but in one project folder ShaderBuilder it detects the packages.config, in the other one, ShaderDisassembler, it does not, even though it’s same dependencies: https://github.com/advancedfx/advancedfx/network/dependencies

I think what’s also strange is that the dependency is sometimes recorded only in one direction (project A shows that it depends on project B in the Insights), but isn’t shown on the other side (project B shows nobody depends on it in the Insights).

This is the case with the MinVer library I mentioned before (on which several of my projects depend).

Hello @rdehuyss & @dtugend––welcome to the conversation, and we’re really sorry for how this behavior is affecting your respective projects. I’ve forwarded these as well as @tompazourek’s latest note to our engineering team maintaining this feature in an internal tracking issue. Like before, I’ll loop back here if they share any additional updates (though I can’t make any promises on any exact time for when that will be). :bowing_man:

Hi everyone. I see the same issue on a fork we did. This fork is used at least by one public project, but the dependents tab is empty. is it normal behavior?

hello~ @francisfuzz
I’m also having the same issue with: https://github.com/PaddlePaddle/Paddle/network/dependents

@lelelelelez - Hey there, thanks for posting this! I’ve relayed this over to our engineering team for review and will follow up as soon as I hear more from them for this project. :bowing_man:

@lelelelelez - Hi! One of our engineers reviewed your case and we want to get a better understanding of what you’d like us to do.

Could you provide more details of what your exact issue is, and perhaps if you could get the PIP package to link to the repository at all? Letting us know of the exact repository would help us investigate further. :male_detective:

thank u very much!
our requirement.txt in this directory :https://github.com/PaddlePaddle/Paddle/blob/8fe1c2d1c278ed9b8956e1d886de5c7287c9231e/python/requirements.txt
I created a example repo, and this repo’s requirement.txt has paddlepaddle==1.8.0, paddle==1.8.0, paddlehub==1.6.0
I find my example repo appear in PaddleHub’s dependents

hi @francisfuzz thank u very much!
our requirement.txt in this directory :https://github.com/PaddlePaddle/Paddle/blob/8fe1c2d1c278ed9b8956e1d886de5c7287c9231e/python/requirements.txt
I created a example repo, and this repo’s requirement.txt has paddlepaddle==1.8.0, paddle==1.8.0, paddlehub==1.6.0
I find my example repo appear in PaddleHub’s dependents.:https://github.com/PaddlePaddle/PaddleHub/network/dependencies
but not appear in Paddle’s dependents

hi @francisfuzz I am adding relevant information
In my example repo’s requirement.txt


but my example repo’s Dependency graph:
And in Paddle-bot repo, I add setup.py: https://github.com/PaddlePaddle/Paddle-bot/blob/0e4476cc4b57d05687af629e910222d2a1773c20/setup.py
Can you troubleshoot it for me?
thank u very much!