Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference Source hashes have changed, so links no longer work #22125

Closed
IanKemp opened this issue Jun 5, 2017 · 8 comments
Closed

Reference Source hashes have changed, so links no longer work #22125

IanKemp opened this issue Jun 5, 2017 · 8 comments

Comments

@IanKemp
Copy link

IanKemp commented Jun 5, 2017

  1. Go to http://referencesource.microsoft.com/
  2. Scroll down to the Link to a type/member text and click the link corresponding to that text: http://referencesource.microsoft.com/mscorlib/a.html#1f55292c3174123d
  3. Notice that you are not directed to the appropriate line of code as you would expect. Instead, you are shown a page containing the text Don't use this page directly, pass #symbolId to get redirected.

This seems to have occurred because the file hashes (I assume) that are used for this functionality have changed. This affects Visual Studio extensions like Ref12.

@stephentoub
Copy link
Member

cc: @richlander, @terrajobst

@karelz
Copy link
Member

karelz commented Jun 7, 2017

@preetikr can you please help?

@tarekgh
Copy link
Member

tarekgh commented Jun 12, 2017

@tarekgh
Copy link
Member

tarekgh commented Jun 12, 2017

@preetikr @richlander why the repo https://github.com/Microsoft/referencesource not allowing creating issues there? can we change that so the related issues can be opened there?

@terrajobst
Copy link
Member

terrajobst commented Jun 13, 2017

Why does the repo https://github.com/Microsoft/referencesource not allow creating issues there?

We’ve disabled filing issues on referencesource because folks never reported infrastructure issues but bugs against .NET Framework, which we didn’t want, so we disabled it. I'm fine with re-enabling it, but we should add an issue template telling people that they should only file infrastructure issues with the contents of the repo or the site.

Not sure why the site regressed; maybe we just need to re-run the indexer? @preetikr, could you investigate?

@tarekgh
Copy link
Member

tarekgh commented Jun 13, 2017

@terrajobst would you enable creating issues in this repo?

@terrajobst
Copy link
Member

I've submitted a PR to add the issue template. Once merged, I'll re-enable issues (microsoft/referencesource#27).

@tarekgh
Copy link
Member

tarekgh commented Jun 15, 2017

closing the issue here as I moved it to microsoft/referencesource#28

@tarekgh tarekgh closed this as completed Jun 15, 2017
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.1.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants