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

Update v3.5.0 #263

Open
wants to merge 16 commits into
base: main
Choose a base branch
from
Open

Update v3.5.0 #263

wants to merge 16 commits into from

Conversation

ButterscotchV
Copy link
Collaborator

@ButterscotchV ButterscotchV commented Jan 1, 2023

  • Update to .NET 7
  • Update GitHub Actions workflows
  • Manually register all features and configs in order to allow trimming
  • Enable explicit nullability on the projects and update all of the code for it
  • Reformat the entire codebase
  • Refactor codebase to utilize new language features

@ButterscotchV
Copy link
Collaborator Author

A little update on this PR, I haven't merged it because there is a bug with closing the server. I'm not sure if kill detection needs to be removed or reworked or what, but I don't have the time to invest into debugging it, so it will remain unmerged and unreleased for now. If anyone wants to tackle this issue, I welcome you.

The bug with closing the server is related to accepting input and kill detection, something locks it up and prevents it from fully closing, meaning stuff like Pterodactyl panel and such get permanently stuck unless you force kill it.

@dhkatz
Copy link

dhkatz commented Apr 5, 2023

Do you know if this happens more on Windows or Linux? I could maybe give it a shot to fix it

@ButterscotchV
Copy link
Collaborator Author

Do you know if this happens more on Windows or Linux? I could maybe give it a shot to fix it

The issue happens on Linux mainly, but I'm sure that Windows isn't free from issues. The input system attempts to not block by checking for input before attempting to read (and potentially block), so I'm not sure why it would be getting caught there, but it very well could be... It might be worth making an input option to check for available input before reading the line? I don't really remember what the code looks like in there.

@dhkatz
Copy link

dhkatz commented Apr 5, 2023

I think I experienced the issue on Linux when I tested out the 3.5.0 build earlier. On Windows I tried to get it to lock up but couldn't seem to. But this was only after like 5 minutes of messing around. I will dig through the code a bit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants