Skip to content

[BUG] LFS Render displays as text #14565

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

Closed
2 of 6 tasks
kdumontnu opened this issue Feb 4, 2021 · 0 comments · Fixed by #14568
Closed
2 of 6 tasks

[BUG] LFS Render displays as text #14565

kdumontnu opened this issue Feb 4, 2021 · 0 comments · Fixed by #14568
Labels
skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/bug

Comments

@kdumontnu
Copy link
Contributor

  • Gitea version (or commit ref): 1.14.0+dev-658-g3c965c3e
  • Git version:
  • Operating system: Windows, Linux + Docker
    See this issue deployed in linux + docker and recreated it locally on windows running form binary
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No (is LFS disabled for try.gitea.io?)
  • Log gist: https://gist.github.com/kdumontnu/ab0d8635f71dc02d4611b00e0139e92a

Description

When viewing an LFS file in gitea, the view now shows as text instead of the file (see a jpg below). Presumably the mimetest function is getting the pointer file instead of the actual LFS file.

Screenshots

image

@lunny lunny added the type/bug label Feb 4, 2021
@lunny lunny added the skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. label Feb 4, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Mar 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants