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

Project Zero Warnings #33279

Open
PJB3005 opened this issue Nov 12, 2024 · 4 comments
Open

Project Zero Warnings #33279

PJB3005 opened this issue Nov 12, 2024 · 4 comments
Labels
A: Core Tech Area: Underlying core tech for the game and the Github repository. D2: Medium Difficulty: A good amount of codebase knowledge required. P1: High Priority: Higher priority than other items, but isn't an emergency. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. S: Requires Engine PR Status: Requires a change to Robust Toolbox, for which there is no open PR currently. T: Cleanup Type: Code clean-up, without being a full refactor or feature

Comments

@PJB3005
Copy link
Member

PJB3005 commented Nov 12, 2024

Description

The game produces a ton of compiler warnings when built right now:

image

This has gradually piled up over years of development to RT and SS14, primarily due to deprecation of old APIs.

Incrementally cleaning up the code to remove these warnings is something any contributor can do in small batches. Contributions appreciated!

For MOTIVATIONAL REASONS, if want to track our progress, we have a public Grafana dashboard that tracks the repo's total warning count over time!

@PJB3005 PJB3005 pinned this issue Nov 12, 2024
@thetolbean
Copy link
Contributor

Can we assume then that maintainers are going to be more focused on preventing PR's from introducing more warnings?

@PJB3005
Copy link
Member Author

PJB3005 commented Nov 13, 2024

Can we assume then that maintainers are going to be more focused on preventing PR's from introducing more warnings?

My current stance is that PRs adding warnings isn't big enough of a deal to warrant the effort to implement an automatic CI enforcement system like that. Best to just fix all the warnings right now.

@benev0
Copy link
Contributor

benev0 commented Nov 25, 2024

I have a branch open for updating the static logger to sawmill. It will probably be in later this week

@benev0
Copy link
Contributor

benev0 commented Dec 1, 2024

I have a branch open for updating the static logger to sawmill. It will probably be in later this week

segfaulting is a concern with the non-static logger due to nullable annotation being incorrect; this will take longer than expected.

@lzk228 lzk228 added P1: High Priority: Higher priority than other items, but isn't an emergency. S: Requires Engine PR Status: Requires a change to Robust Toolbox, for which there is no open PR currently. T: Cleanup Type: Code clean-up, without being a full refactor or feature D2: Medium Difficulty: A good amount of codebase knowledge required. A: Core Tech Area: Underlying core tech for the game and the Github repository. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Core Tech Area: Underlying core tech for the game and the Github repository. D2: Medium Difficulty: A good amount of codebase knowledge required. P1: High Priority: Higher priority than other items, but isn't an emergency. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. S: Requires Engine PR Status: Requires a change to Robust Toolbox, for which there is no open PR currently. T: Cleanup Type: Code clean-up, without being a full refactor or feature
Projects
None yet
Development

No branches or pull requests

5 participants