You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Chris Tsai <ct...@users.sf.net> on 2013/12/06 15:31:43 UTC

[allura:tickets] #6952 404 on specific Git branch [ss6144]



---

** [tickets:#6952] 404 on specific Git branch [ss6144]**

**Status:** open
**Labels:** support p3 
**Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
**Last Updated:** Fri Dec 06, 2013 02:31 PM UTC
**Owner:** nobody

[forge:site-support:#6144]

>On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[allura:tickets] #6952 404 on specific Git branch [ss6144]

Posted by "Patrick M. Niedzielski" <pn...@users.sf.net>.
Hi, are there any updates on this?  This bug has prevented my team from using Sourceforge for the past two months, and if it's not fixed soon, we are going to have to move to another hosting site with a working online source viewer.


---

** [tickets:#6952] 404 on specific Git branch [ss6144]**

**Status:** open
**Labels:** support p3 
**Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
**Last Updated:** Sun Dec 15, 2013 01:02 AM UTC
**Owner:** nobody

[forge:site-support:#6144]

>On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[allura:tickets] #6952 404 on specific Git branch [ss6144]

Posted by "Patrick M. Niedzielski" <pn...@users.sf.net>.
After the repo refresh on our main repository, the code browser for other repository we have doesn't work either:

https://sourceforge.net/p/hummstrumm/website-code/

The source viewer for this repository was working before the repo refresh even when the source viewer for our main repository wasn't working.


---

** [tickets:#6952] 404 on specific Git branch [ss6144]**

**Status:** open
**Labels:** support p3 
**Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
**Last Updated:** Sun Dec 15, 2013 12:55 AM UTC
**Owner:** nobody

[forge:site-support:#6144]

>On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[allura:tickets] #6952 404 on specific Git branch [ss6144]

Posted by Chris Tsai <ct...@users.sf.net>.
- **status**: open --> closed
- **Comment**:

[#7021] fixed it



---

** [tickets:#6952] 404 on specific Git branch [ss6144]**

**Status:** closed
**Milestone:** limbo
**Labels:** support p3 
**Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
**Last Updated:** Mon Feb 17, 2014 01:06 PM UTC
**Owner:** nobody

[forge:site-support:#6144]

>On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[allura:tickets] #6952 404 on specific Git branch [ss6144]

Posted by Dave Brondsema <br...@users.sf.net>.
Looks like the root cause of this is [#7021].  We'll see if we can address that soon.


---

** [tickets:#6952] 404 on specific Git branch [ss6144]**

**Status:** open
**Labels:** support p3 
**Created:** Fri Dec 06, 2013 02:31 PM UTC by Chris Tsai
**Last Updated:** Wed Feb 05, 2014 01:51 PM UTC
**Owner:** nobody

[forge:site-support:#6144]

>On the Forge interface for our Git repository, when I click on the button for our "unstable" branch, I am directed to a 404 page. This does not happen when I click on either the button for the "master" branch or the "window_refactor" branch. I don't believe that there is a problem with the Git repository, because cloning from it and checking out the unstable branch works fine and has all recent commits to that branch.

https://sourceforge.net/p/hummstrumm/code/

Ugh, so I tried doing a full repo refresh hoping it would fix this, and it instead made things worse. Now I'm getting a "Metadata missing" message on their master branch, and 404s on the others. Previously, master and window_refactor branches at least worked.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.