github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Merged origin/master today and get error in some pages #96

New Issue
Closed
opened 2025-11-02 03:08:48 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 03:08:48 -06:00
Owner
Copy Link

Originally created by @yusiwen on GitHub (Nov 30, 2016).

  • Gitea version (or commit ref): 6519718706
  • Git version: 2.10.2
  • Operating system: Ubuntu 16.04 x64
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Log gist:

Description

Today I've pull origin/master in my local master branch, and when I click "Explore" on the page, I got:

template: explore/repo_list:19:8: executing "explore/repo_list" at <.DescriptionHTML>: can't evaluate field DescriptionHTML in type *models.Repository
Originally created by @yusiwen on GitHub (Nov 30, 2016). - Gitea version (or commit ref): 65197187069dfe3407e8954bb5af32ee688b0da4 - Git version: 2.10.2 - Operating system: Ubuntu 16.04 x64 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] SQLite - Log gist: ## Description Today I've pull origin/master in my local master branch, and when I click "Explore" on the page, I got: ``` template: explore/repo_list:19:8: executing "explore/repo_list" at <.DescriptionHTML>: can't evaluate field DescriptionHTML in type *models.Repository ```
GiteaMirror added the issue/not-a-bug label 2025-11-02 03:08:48 -06:00
GiteaMirror commented 2025-11-02 03:08:49 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 30, 2016):

Please update to the latest version, this have been fixed with https://github.com/go-gitea/gitea/pull/299

@tboerger commented on GitHub (Nov 30, 2016): Please update to the latest version, this have been fixed with https://github.com/go-gitea/gitea/pull/299
GiteaMirror commented 2025-11-02 03:08:49 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 30, 2016):

Sorry, just have seen it's not fixed correctly. @lunny can you fix that?

@tboerger commented on GitHub (Nov 30, 2016): Sorry, just have seen it's not fixed correctly. @lunny can you fix that?
GiteaMirror commented 2025-11-02 03:08:49 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 30, 2016):

I will check this.

@lunny commented on GitHub (Nov 30, 2016): I will check this.
GiteaMirror commented 2025-11-02 03:08:49 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 30, 2016):

@tboerger do you reproduced that? I cannot.
@yusiwen maybe you have to make clean & make build.

@lunny commented on GitHub (Nov 30, 2016): @tboerger do you reproduced that? I cannot. @yusiwen maybe you have to `make clean & make build`.
GiteaMirror commented 2025-11-02 03:08:50 -06:00
Author
Owner
Copy Link

@yusiwen commented on GitHub (Nov 30, 2016):

@lunny
After make clean & make build, the newest binary file gitea is generated under bin folder, not in the project root path as it was before. So my service script can't start it. After I copied it to project root path, I restarted gitea, the problems are gone.

Thanks.

@yusiwen commented on GitHub (Nov 30, 2016): @lunny After `make clean & make build`, the newest binary file `gitea` is generated under `bin` folder, not in the project root path as it was before. So my service script can't start it. After I copied it to project root path, I restarted gitea, the problems are gone. Thanks.
GiteaMirror commented 2025-11-02 03:08:50 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 30, 2016):

There is an pending pull request which builds the binary to the root folder again

@tboerger commented on GitHub (Nov 30, 2016): There is an pending pull request which builds the binary to the root folder again
GiteaMirror commented 2025-11-02 03:08:50 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 30, 2016):

I have marked the issue as invalid, it was just related to outdated sources.

@tboerger commented on GitHub (Nov 30, 2016): I have marked the issue as invalid, it was just related to outdated sources.
GiteaMirror commented 2025-11-02 03:08:50 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 30, 2016):

BTW, you can also call make only once, e.g. make clean build

@tboerger commented on GitHub (Nov 30, 2016): BTW, you can also call make only once, e.g. make clean build
GiteaMirror commented 2025-11-02 03:08:50 -06:00
Author
Owner
Copy Link

@yusiwen commented on GitHub (Nov 30, 2016):

@tboerger
Thanks. Will the binary be put under bin folder from now on or put back to project root? I runned gitea from bin folder, it complained about not found app.ini in bin/custom/app.ini, and a lot of errors as well before it exited.

@yusiwen commented on GitHub (Nov 30, 2016): @tboerger Thanks. Will the binary be put under `bin` folder from now on or put back to project root? I runned gitea from `bin` folder, it complained about not found `app.ini` in `bin/custom/app.ini`, and a lot of errors as well before it exited.
GiteaMirror commented 2025-11-02 03:08:51 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Nov 30, 2016):

Will be in the root, see #247

@strk commented on GitHub (Nov 30, 2016): Will be in the root, see #247
GiteaMirror commented 2025-11-02 03:08:51 -06:00
Author
Owner
Copy Link

@yusiwen commented on GitHub (Dec 8, 2016):

@strk I see, thanks

@yusiwen commented on GitHub (Dec 8, 2016): @strk I see, thanks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#96
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?