github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-26 04:50:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Invalid syntax error when pushing #831

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

Originally created by @mangkang on GitHub (Jun 20, 2017).

  • Gitea version (or commit ref): 1.1.2
  • Git version: 2.11.0
  • Operating system: OS X Client / Ubuntu 64 Server
  • Database (use [x]):
    • PostgreSQL
    • [ X] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [ X] Not relevant
  • Log gist:

Hi, I am experiencing an unexpected error when pushing to Gitea from local to remote.
This seems to be related to a commit comment. There is no other error in the server log files.

The client side error in red is:

remote: 2017/06/20 21:58:55 [...tea/models/update.go:147 PushUpdate()] [E] updateIssuesCommit: strconv.ParseInt: parsing "ITOM-9100": invalid syntax

$ git push
Counting objects: 469427, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (123252/123252), done.
Writing objects: 100% (469427/469427), 120.48 MiB | 556.00 KiB/s, done.
Total 469427 (delta 299793), reused 441750 (delta 272388)
remote: 2017/06/20 21:58:55 [...tea/models/update.go:147 PushUpdate()] [E] updateIssuesCommit: strconv.ParseInt: parsing "ITOM-9100": invalid syntax
To https://172.30.47.164:3000/abc/repo1

  • [new branch] master -> master

Thanks,

MK

Originally created by @mangkang on GitHub (Jun 20, 2017). - Gitea version (or commit ref): 1.1.2 - Git version: 2.11.0 - Operating system: OS X Client / Ubuntu 64 Server - Database (use `[x]`): - [ ] PostgreSQL - [ X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ X] Not relevant - Log gist: Hi, I am experiencing an unexpected error when pushing to Gitea from local to remote. This seems to be related to a commit comment. There is no other error in the server log files. The client side error in red is: remote: 2017/06/20 21:58:55 [...tea/models/update.go:147 PushUpdate()] [E] updateIssuesCommit: strconv.ParseInt: parsing "ITOM-9100": invalid syntax $ git push Counting objects: 469427, done. Delta compression using up to 8 threads. Compressing objects: 100% (123252/123252), done. Writing objects: 100% (469427/469427), 120.48 MiB | 556.00 KiB/s, done. Total 469427 (delta 299793), reused 441750 (delta 272388) remote: 2017/06/20 21:58:55 [...tea/models/update.go:147 PushUpdate()] [E] updateIssuesCommit: strconv.ParseInt: parsing "ITOM-9100": invalid syntax To https://172.30.47.164:3000/abc/repo1 * [new branch] master -> master Thanks, MK
GiteaMirror added the type/bug label 2025-11-02 03:38:08 -06:00
GiteaMirror commented 2025-11-02 03:38:09 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jun 20, 2017):

can you give exact commit message?

@lafriks commented on GitHub (Jun 20, 2017): can you give exact commit message?
GiteaMirror commented 2025-11-02 03:38:09 -06:00
Author
Owner
Copy Link

@mangkang commented on GitHub (Jun 20, 2017):

Here are the two commit messages with that string pattern:

#ITOM-9100 i.e To reflect availability changes done to fix status Report\n\ngit-svn-id: https://svn501.myhost.com/svn/itom/trunk@42563 86a4919b-b3e0-4e62-bec7-4511e7be0dea\n

#[JIRA] (ITOM-9100) Enhanced the availability discrepancy utility to the the new availability changes
git-svn-id: https://svn501.myhost.com/svn/itom/trunk@41971 86a4919b-b3e0-4e62-bec7-4511e7be0dea

@mangkang commented on GitHub (Jun 20, 2017): Here are the two commit messages with that string pattern: 1) #ITOM-9100 i.e To reflect availability changes done to fix status Report\n\ngit-svn-id: https://svn501.myhost.com/svn/itom/trunk@42563 86a4919b-b3e0-4e62-bec7-4511e7be0dea\n 2) #[JIRA] (ITOM-9100) Enhanced the availability discrepancy utility to the the new availability changes git-svn-id: https://svn501.myhost.com/svn/itom/trunk@41971 86a4919b-b3e0-4e62-bec7-4511e7be0dea
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 type/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#831
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?