mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
Eliminate All Compiler Warnings In Solution #1137
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#1137
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @mark-monteiro on GitHub (Dec 13, 2019).
This is a general ticket to track progress on eliminating all warnings in the solution source code, including enabling missing analyzers and converting warnings to errors in release builds. @Bond-009, as I understand, you have already been working on this for a while. I thought I would start helping out with this task and we (and anyone else) can coordinate progress here.
The table below summarizes the progress on this task at the current HEAD commit on master:
@jvoisin commented on GitHub (Jun 26, 2020):
Would it be possible to add LGTM.com to the list? It found a lot of issues.
@dcparga commented on GitHub (Oct 11, 2020):
Hey guys, I'm just wondering. I'm seeing 4028 warnings when building the solution. Some of the warnings are like "don't use space after new keyword", or others like to move types to their own file. I assume any warning fixed will be welcome, right?
@dkanada commented on GitHub (Oct 11, 2020):
You're correct, anything that shows a warning is fair game for a pull request.
@stale[bot] commented on GitHub (Feb 9, 2021):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@Christian-Oleson commented on GitHub (Sep 30, 2022):
I'm willing to help out with this if you are looking for help
@jbatt33 commented on GitHub (Mar 30, 2023):
I just built Jellyfin and I'm not seeing any warnings. Is this bug fixed or am I looking at the wrong repo. Maybe I need to build harder.
@Bond-009 commented on GitHub (Mar 30, 2023):
@jbatt33 are you building in debug mode?
@jbatt33 commented on GitHub (Mar 30, 2023):
Yes, I did both debug and release builds of the jellyfin under VS 2022 and did not get any warnings or errors, but get 3 messages:

@Bond-009 commented on GitHub (Mar 31, 2023):
I think it's an issue with dotnet, if you remove
<CodeAnalysisTreatWarningsAsErrors>false</CodeAnalysisTreatWarningsAsErrors>from the projects that have it you'll get build errors@jbatt33 commented on GitHub (Mar 31, 2023):
Thanks, I deleted that line from the project file and it's working as expected. I'm going to see if I can tackle any of these.
@LoremFooBar commented on GitHub (Sep 27, 2023):
I'd like to try to clear some of these warnings. I already started with the simpler ones. Some warnings require refactoring that is easy to do, but hard to determine whether they are breaking changes. I'd like to try to tackle these as well later on.
@gsedubun commented on GitHub (May 1, 2024):
I'd like to try to clear some of these.