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

[help] Gitea cannot run in the Windows development environment #4498

New Issue
Closed
opened 2025-11-02 05:52:45 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 05:52:45 -06:00
Owner
Copy Link

Originally created by @scotox on GitHub (Dec 17, 2019).

  • Gitea version (or commit ref): source branch v1.10.1
  • Operating system: Windows10 x64

Description

  1. goland 2019.2
    • Enable Go Modules (vgo) integration
    • Proxy: goproxy.io
    • GOROOT and GOPATH is ok.
  2. go version go1.13 windows/amd64
  3. goland Run/Debug Configurations to Go Build
    • Run kind: File
    • Files: xxx\code.gitea.io\gitea\main.go
    • other is default
  4. run Debug to panic.

panic: fail to set message file(en-US): open conf/locale/locale_en-US.ini: The system cannot find the path specified.

Screenshots

image

Originally created by @scotox on GitHub (Dec 17, 2019). - Gitea version (or commit ref): source branch v1.10.1 - Operating system: Windows10 x64 ## Description 1. goland 2019.2 - Enable Go Modules (vgo) integration - Proxy: `goproxy.io` - `GOROOT` and `GOPATH` is ok. 2. go version go1.13 windows/amd64 3. goland Run/Debug Configurations to `Go Build` - Run kind: File - Files: xxx\code.gitea.io\gitea\main.go - other is default 4. run Debug to panic. >`panic: fail to set message file(en-US): open conf/locale/locale_en-US.ini: The system cannot find the path specified.` ## Screenshots ![image](https://user-images.githubusercontent.com/48884300/71021919-4228a080-213a-11ea-81e1-3a5dd6ff1d6d.png)
GiteaMirror added the type/questionissue/needs-feedback labels 2025-11-02 05:52:45 -06:00
GiteaMirror commented 2025-11-02 05:52:46 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Dec 17, 2019):

https://docs.gitea.io/en-us/install-from-source/#build
https://docs.gitea.io/en-us/make/

Simply running main.go will not work, doubly so because GoLand runs the built binaries in temp build locations.
It may be possible for GoLand to run it correctly if given the correct tags so that assets are bundled, but it's probably a better strategy to use the documented way for the time being.

@jolheiser commented on GitHub (Dec 17, 2019): https://docs.gitea.io/en-us/install-from-source/#build https://docs.gitea.io/en-us/make/ Simply running `main.go` will not work, doubly so because GoLand runs the built binaries in temp build locations. It _may_ be possible for GoLand to run it correctly if given the correct tags so that assets are bundled, but it's probably a better strategy to use the documented way for the time being.
GiteaMirror commented 2025-11-02 05:52:46 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 17, 2019):

I suppose we could wrap our CSS and js generation steps in go:generate then you don't need the make step...

@zeripath commented on GitHub (Dec 17, 2019): I suppose we could wrap our CSS and js generation steps in go:generate then you don't need the make step...
GiteaMirror commented 2025-11-02 05:52:46 -06:00
Author
Owner
Copy Link

@scotox commented on GitHub (Dec 18, 2019):

TKS All the guys

The problem was solved ...... the goland Run/Debug Configurations has three fields ("Directory", "Output directory", "Working directory"), I left out the "Output directory" item .... set this item to project root path then it's all right ..... not on the make of command line .... not on the npm build ......
go straight to code breakpoint mode.
Now i can have a happy break point again.....

@scotox commented on GitHub (Dec 18, 2019): TKS All the guys The problem was solved ...... the goland Run/Debug Configurations has three fields ("Directory", "Output directory", "Working directory"), I left out the "Output directory" item .... set this item to project root path then it's all right ..... not on the make of command line .... not on the npm build ...... go straight to code breakpoint mode. Now i can have a happy break point again.....
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/needs-feedback type/question
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#4498
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?