-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
repo/header:53:150: executing "repo/header" at <EscapePound>: invalid value; expected string #7663
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
Comments
Are you using custom templates? |
@lafriks " |
@techknowlogick it is strongly not recommended but you can override any template file in Gitea |
@lafriks oh yes, I know ;) I was just quoting what the user said about not using them. |
There's something very odd about that repository. I've just migrated it to try and your "master" branch wasn't brought along. How did you create this repository and the master branch? Gitea's branches are supposed to be in refs/heads I suspect your master branch is not. |
Thanks @techknowlogick for pointing that out, yes @lafriks I have not overridden such template. @zeripath I have simply migrated that repo via migration interface, the original repo is located at https://github.com/Alir3z4/django-cms which has been migrated into https://gitfoo.com/Alir3z4/django-cms/ I have found another problem as well, which it's reported at #7664 |
This is very odd because there's no master branch in that upstream repository |
git can be without This SO thread can clarify more https://stackoverflow.com/a/3623762/636136 |
yeah I'm aware - but somehow your repo seems to think there should be a master branch. I guess the default branch never got updated when the repo was migrated. Now, I think on try this doesn't happen c.f. https://try.gitea.io/arandomer/django-cms - so we must have fixed this in 1.10 but it wasn't reverted back to 1.9. |
OK so a quick fix is to go to the repository settings and reset the default branch. But I don't understand why/how this appears fixed on 1.10 |
Have the same issue.
|
@amiga23 which version of your gitea? I cannot reproduce that on 1.10.0+dev-281 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Hi, I can reproduce that. I'm at the current master branch of gitea runnin on docker. |
The problem occurs when you migrate a repo from github that doesn't have a master branch and then try to view a file. Gitea tries to open the master branch. When you switch to a existing branch first everything working fine |
I've re-opened this issue. Thanks for the report. @rdissertori / @DeRuiterIndustrieleAutomatisering are you able to replicate this on try.gitea.io? |
A similar error occurs when viewing the history in the wiki.
Log error:
Cloning a wiki for testing on another server - error not reproducible |
Using latest 1.12.4 you can simply reproduce this error:
If you push something the the repo (not the wiki-repo, the repo itself) then everying is working. gitea source file templates/repo/header.tmpl, Line 95
If i build and install from latest gitea-master (1.13) this issue seems to be solved. |
Is this still present on 1.12.5? |
I will close this and please feel free reopen it if it occurs again. |
[x]
):Description
Tried to open a commit list page of a repository and got
You can visit the URL as see the issue https://gitfoo.com/Alir3z4/django-cms/commits/branch/master
Also there's no custom template for repo/header file.
...
Screenshots
The text was updated successfully, but these errors were encountered: