repo/header:53:150: executing &#34;repo/header&#34; at &lt;EscapePound&gt;: invalid value; expected string #3695

@techknowlogick commented on GitHub (Jul 29, 2019):

@lafriks "Also there's no custom template for repo/header file."

@techknowlogick commented on GitHub (Jul 29, 2019): @lafriks "`Also there's no custom template for repo/header file.`"

GiteaMirror commented

@lafriks commented on GitHub (Jul 29, 2019):

@techknowlogick it is strongly not recommended but you can override any template file in Gitea

@lafriks commented on GitHub (Jul 29, 2019): @techknowlogick it is strongly not recommended but you can override any template file in Gitea

GiteaMirror commented

@techknowlogick commented on GitHub (Jul 29, 2019):

@lafriks oh yes, I know ;) I was just quoting what the user said about not using them.

@techknowlogick commented on GitHub (Jul 29, 2019): @lafriks oh yes, I know ;) I was just quoting what the user said about not using them.

GiteaMirror commented

@zeripath commented on GitHub (Jul 29, 2019):

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.

@zeripath commented on GitHub (Jul 29, 2019): 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.

GiteaMirror commented

@Alir3z4 commented on GitHub (Jul 29, 2019):

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 https://github.com/go-gitea/gitea/issues/7664

@Alir3z4 commented on GitHub (Jul 29, 2019): 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 https://github.com/go-gitea/gitea/issues/7664

GiteaMirror commented

@zeripath commented on GitHub (Jul 29, 2019):

This is very odd because there's no master branch in that upstream repository

@zeripath commented on GitHub (Jul 29, 2019): This is very odd because there's no master branch in that upstream repository

GiteaMirror commented

@Alir3z4 commented on GitHub (Jul 29, 2019):

git can be without master branch. AFAIK, master is just like any other branch, with the exception that it's created by default when creating a repo (git init)

This SO thread can clarify more https://stackoverflow.com/a/3623762/636136

@Alir3z4 commented on GitHub (Jul 29, 2019): git can be without `master` branch. AFAIK, `master` is just like any other branch, with the exception that it's created by default when creating a repo (`git init`) This SO thread can clarify more https://stackoverflow.com/a/3623762/636136

GiteaMirror commented

@zeripath commented on GitHub (Jul 29, 2019):

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.

@zeripath commented on GitHub (Jul 29, 2019): 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.

GiteaMirror commented

@zeripath commented on GitHub (Jul 29, 2019):

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

@zeripath commented on GitHub (Jul 29, 2019): 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

GiteaMirror commented

@amiga23 commented on GitHub (Sep 11, 2019):

Have the same issue.

Create a branch
Go to settings and set new branch as default branch
delete branch
try to open any folder of the repo in the gitea WebUI -> ERROR

@amiga23 commented on GitHub (Sep 11, 2019): Have the same issue. 1. Create a branch 2. Go to settings and set new branch as default branch 3. delete branch 4. try to open any folder of the repo in the gitea WebUI -> ERROR

GiteaMirror commented

@lunny commented on GitHub (Sep 12, 2019):

@amiga23 which version of your gitea? I cannot reproduce that on 1.10.0+dev-281

@lunny commented on GitHub (Sep 12, 2019): @amiga23 which version of your gitea? I cannot reproduce that on 1.10.0+dev-281

GiteaMirror commented

@stale[bot] commented on GitHub (Dec 12, 2019):

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.

@stale[bot] commented on GitHub (Dec 12, 2019): 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.

GiteaMirror commented

@rdissertori commented on GitHub (Jun 23, 2020):

Hi, I can reproduce that. I'm at the current master branch of gitea runnin on docker.
What I did:
Migrate a project from github as a mirror. Initially there was a 1 "master" branch, but someone deleted it and renamed it to 1 "public" branch.
Then I'm getting that exact issue because gitea won't switch to the new "public" branch.

@rdissertori commented on GitHub (Jun 23, 2020): Hi, I can reproduce that. I'm at the current master branch of gitea runnin on docker. What I did: Migrate a project from github as a mirror. Initially there was a 1 "master" branch, but someone deleted it and renamed it to 1 "public" branch. Then I'm getting that exact issue because gitea won't switch to the new "public" branch.

GiteaMirror commented

@DeRuiterIndustrieleAutomatisering commented on GitHub (Jul 16, 2020):

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

@DeRuiterIndustrieleAutomatisering commented on GitHub (Jul 16, 2020): 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

GiteaMirror commented

@techknowlogick commented on GitHub (Jul 16, 2020):

I've re-opened this issue. Thanks for the report.

@rdissertori / @DeRuiterIndustrieleAutomatisering are you able to replicate this on try.gitea.io?

@techknowlogick commented on GitHub (Jul 16, 2020): I've re-opened this issue. Thanks for the report. @rdissertori / @DeRuiterIndustrieleAutomatisering are you able to replicate this on try.gitea.io?

GiteaMirror commented

@Izorkin commented on GitHub (Aug 4, 2020):

A similar error occurs when viewing the history in the wiki.
Not reproduced this error. Browser error:

template: repo/header:95:151: executing "repo/header" at <EscapePound>: invalid value; expected string

Log error:

авг 04 21:47:03 web gitea[15941]: [Macaron] 2020-08-04 21:47:03: Started GET /test/example-wiki/wiki/commit/e5bd621f7b8f30fc2d7931ff75215e6deefee298 for 91.216.72.209:60137
авг 04 21:47:03 web gitea[15941]: [Macaron] 2020-08-04 21:47:03: Completed GET /test/example-wiki/wiki/commit/e5bd621f7b8f30fc2d7931ff75215e6deefee298 500 Internal Server Error in 54.093677ms
авг 04 21:47:05 web gitea[15941]: [Macaron] 2020-08-04 21:47:05: Started GET /serviceworker.js for 91.216.72.209:60137
авг 04 21:47:05 web gitea[15941]: [Macaron] [Static] Serving /serviceworker.js
авг 04 21:47:05 web gitea[15941]: [Macaron] 2020-08-04 21:47:05: Completed GET /serviceworker.js 304 Not Modified in 183.359µs

Cloning a wiki for testing on another server - error not reproducible

@Izorkin commented on GitHub (Aug 4, 2020): A similar error occurs when viewing the history in the wiki. Not reproduced this error. Browser error: ``` template: repo/header:95:151: executing "repo/header" at <EscapePound>: invalid value; expected string ``` Log error: ``` авг 04 21:47:03 web gitea[15941]: [Macaron] 2020-08-04 21:47:03: Started GET /test/example-wiki/wiki/commit/e5bd621f7b8f30fc2d7931ff75215e6deefee298 for 91.216.72.209:60137 авг 04 21:47:03 web gitea[15941]: [Macaron] 2020-08-04 21:47:03: Completed GET /test/example-wiki/wiki/commit/e5bd621f7b8f30fc2d7931ff75215e6deefee298 500 Internal Server Error in 54.093677ms авг 04 21:47:05 web gitea[15941]: [Macaron] 2020-08-04 21:47:05: Started GET /serviceworker.js for 91.216.72.209:60137 авг 04 21:47:05 web gitea[15941]: [Macaron] [Static] Serving /serviceworker.js авг 04 21:47:05 web gitea[15941]: [Macaron] 2020-08-04 21:47:05: Completed GET /serviceworker.js 304 Not Modified in 183.359µs ``` Cloning a wiki for testing on another server - error not reproducible

GiteaMirror commented

@fashberg commented on GitHub (Sep 7, 2020):

Using latest 1.12.4 you can simply reproduce this error:

Create (empty) repositoy
add a wiki-page
open diff (/user/testrepo/wiki/commit/)
you'll get template: repo/header:95:151: executing "repo/header" at <EscapePound>: invalid value; expected string
if you add more changes to that wiki-page only the latest diff shows this error (top of "/user/testrepo/wiki/Home/_revision").

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

<a class="{{if .PageIsViewCode}}active{{end}} item" href="{{.RepoLink}}{{if (ne .BranchName .Repository.DefaultBranch)}}/src/{{.BranchNameSubURL | EscapePound}}{{end}}">

If i build and install from latest gitea-master (1.13) this issue seems to be solved.

@fashberg commented on GitHub (Sep 7, 2020): Using latest 1.12.4 you can simply reproduce this error: - Create (empty) repositoy - add a wiki-page - open diff (/user/testrepo/wiki/commit/<id>) - you'll get ```template: repo/header:95:151: executing "repo/header" at <EscapePound>: invalid value; expected string``` - if you add more changes to that wiki-page only the latest diff shows this error (top of "/user/testrepo/wiki/Home/_revision"). 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 ```<a class="{{if .PageIsViewCode}}active{{end}} item" href="{{.RepoLink}}{{if (ne .BranchName .Repository.DefaultBranch)}}/src/{{.BranchNameSubURL | EscapePound}}{{end}}">``` If i build and install from latest gitea-master (1.13) this issue seems to be solved.

GiteaMirror commented