Skip to content
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

No error log entries for repo 404 #2200

Merged
merged 1 commit into from
Aug 19, 2017
Merged

Conversation

ethantkoenig
Copy link
Member

Don't have error-level log entries when a non-existent repo is accessed. IMO, this unnecessarily clutters the logs.

@lafriks
Copy link
Member

lafriks commented Jul 22, 2017

Does 404 request is logged somewhere anyway?

@lafriks lafriks added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jul 22, 2017
@ethantkoenig
Copy link
Member Author

@lafriks What do you mean?

@lafriks
Copy link
Member

lafriks commented Jul 22, 2017

Does these 404 requests are still logged in serv.lg/http.log

@ethantkoenig
Copy link
Member Author

@lafriks No, but nor are other types of 404 (e.g. non-existent user)

@Bwko
Copy link
Member

Bwko commented Jul 23, 2017

LGTM

@lafriks lafriks added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jul 23, 2017
@strk
Copy link
Member

strk commented Aug 19, 2017

LGTM

@tboerger tboerger added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Aug 19, 2017
@lafriks lafriks added this to the 1.2.0 milestone Aug 19, 2017
@lafriks lafriks merged commit e7653a6 into go-gitea:master Aug 19, 2017
@lunny lunny added the type/enhancement An improvement of existing functionality label Aug 25, 2017
@ethantkoenig ethantkoenig deleted the log/quieter branch September 18, 2017 03:23
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
6543 pushed a commit to 6543-forks/gitea that referenced this pull request Feb 26, 2024
- When there's a succesful POST operation, it should return a 201 status
code (which is the status code for succesful created) and additionally
the created object.
- Currently for the `POST /repos/{owner}/{repo}/tags` endpoint an 200
status code was documented in the OpenAPI specification, while an 201
status code was actually being returned. In this case the code is
correct and the documented status code needs to be adjusted.
- Resolves go-gitea#2200

(cherry picked from commit a2939116f5ce21295981a3a9aa84a73fe289b8b2)
(cherry picked from commit 22cff4158564a3e69bef83c458cf1f129e1b688b)
(cherry picked from commit b23a7f27bb10e782e70530cc8c37f5d11f7a684a)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/enhancement An improvement of existing functionality type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants