Blame from changeset view leads to "non-existent node" error

[Ryan J Ollos]

Following the blame link on browser/sandbox/trac-diff/htdocs/css/changeset.css leads to a page with this error:

No node branches/cboos-dev/anydiff-branch/htdocs/css/changeset.css at revision 2808

You can search in the repository history to see if that path existed but was later removed

Editing the URL to append &annotate=blame leads to the correct URL: browser/sandbox/trac-diff/htdocs/css/changeset.css

Btw, what Version should be selected for reporting issues on the trunk? Or do we need to add an entry to the Version table?

[Christian Boos]

Well, we take the (created_path, created_rev) pair there. This usually works well unless a parent directory has been copied (or moved, like here r2476). See #7744, which is really the same thing. Feel free to come up with new ideas on this old nagging issue ;-)

[anonymous]

I think I hit this same problem:

changeset:3832 commit message contains a link ("Genshi branch") to https://trac.edgewall.org/browser/sandbox/genshi?rev=3831 which works fine.

From there I can navigate to https://trac.edgewall.org/browser/sandbox/genshi/trac/versioncontrol/web_ui/changeset.py?rev=3831 which also works fine.

But when I then click "Blame" I get:

Trac Error No node sandbox/markup/trac/versioncontrol/web_ui/changeset.py at revision 3831