DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

DNN Repo Broken For Anyone Else?

 3 Replies
 2 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Senior Member
Posts: 1374
Senior Member

    Hello Everyone: 

    I have no idea why this is happening, but I'm guessing it's an environmental issue.  

    I had just wanted to open the DNN project to do some research on a feature.  I was about 90 commits behind and attempted to do a pull like you would in this case.  It resulted in a fatal timeout error message.  

    I tried troubleshooting that for a while, but ended up deciding it would be faster just to delete it all and close it again.  Boy was I wrong!  

    In attempting to do this, I tried with traditional command line, GitKraken, and the GitHub CLI.  In all instances, I'm unable to successfully clone the repo anymore.  The only time I even see any files transferred is when using the GitHub CLI.  The others fail and there aren't any files in the folder I'm cloning to.  

    Here's the result of the GitHub CLI. 

    I don't have screenshots of the other attempts, but I can certainly generate them all again - except for the error message on the pull.  I need to be able to clone to try a pull again.  

    Is anyone else running into this?  

    Senior Member
    Posts: 1374
    Senior Member

      If you want to see it in action, here you go!  :) 

      https://app.screencast.com/sMt42SdfWL0bs

      Advanced Member
      Posts: 143
      Advanced Member

        Looks like it's related to a long path in the repo (introduced recently). A StackOverflow post indicates you may need to adjust your git config to allow it to work with long paths (and/or maybe adjust Windows to allow long paths).

        DNN partner specializing in custom, enterprise DNN development https://engagesoftware.com/showcase
        Senior Member
        Posts: 1374
        Senior Member
          Posted By Brian Dukes on 8/10/2023 1:50 PM
          Looks like it's related to a long path in the repo (introduced recently). https://stackoverflow.com/a/22575737/2688 indicates you may need to adjust your git config to allow it to work with long paths (and/or maybe adjust Windows to allow long paths).

          I was afraid it might be something like that.  It won't be a great first-time experience for new developers, but the advice you provided from StackOverflow was spot on, as always.  

          I ran the git config --system core.longpaths true command, it not only worked, something else was interesting to me.  It cloned faster than I've seen it clone before.  Maybe that's just a coincidence, though. 

           

          These Forums are dedicated to the discussion of DNN Platform.

          For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

          1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
          2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
          3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
          4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
          5. No Flaming or Trolling.
          6. No Profanity, Racism, or Prejudice.
          7. Site Moderators have the final word on approving / removing a thread or post or comment.
          8. English language posting only, please.

          Would you like to help us?

          Awesome! Simply post in the forums using the link below and we'll get you started.

          Get Involved