feat: dotnet9 and packages update #48
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
yes, thanks, we know about the error with ParseQuestpch2 |
|
Thank you for the PR, however, this update is not timely yet. We would appreciate it if you could assist us with improvements to the Parser Engine, as not all data is being parsed in the PTS files, what do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update all projects to dotnet9, and update all packages to last versions.
Adjustments on code related to bouncy to resolve errors after dotnet and packages updates.
obs: this error on ParseQuestpch2 It also happens on master, it didn't appear after the update to dotnet9.
