-
Notifications
You must be signed in to change notification settings - Fork 53
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
Fix: Small fixes 11/22 #642
Fix: Small fixes 11/22 #642
Conversation
{ | ||
transaction.Rollback(); | ||
connection.Close(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we need to close the connection here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it's closed in the finally
, which will execute automatically when you leave the scope of the try-catch.
@@ -950,7 +950,7 @@ public PacketQueue HandleEnemyHuntRequests(Enemy enemy, DbConnection? connection | |||
|
|||
S2CQuestQuestProgressWorkSaveNtc ntc = new() | |||
{ | |||
QuestScheduleId = quest.Key, | |||
QuestScheduleId = questScheduleId, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a syntax change to make the iteration more explicit, not a functional one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Key and schedule id are two different values. I could never figure out what key value was based on and it is left as zero generally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, in this case, quest
is/was the KeyValuePair<uint, QuestState>
that's returned by iterating over ActiveQuests
, and that uint
is actually the QuestScheduleId
(see line 205). So quest.Key
is not the Key
field of a Quest
object, but the Key
field of a KeyValuePair<uint, QuestState>
.
… floating around; just skip them instead.
…ate properly when thrown during a transaction.
…her than their visual gear where applicable.
d9672ae
to
a0a23bd
Compare
FriendApplyFriendHandler
due to a missing constructor.QuestGetMainQuestListHandler
due to invalid scheduleIds.ProfileGetCharacterProfileHandler
due to invalid characterIds.InstanceEnemyKillHandler
, maybe???RequestPacketHandler
andResponseErrorException
ExecuteInTransaction
no longer mangle their stack trace.ResponseErrorException
s thrown duringExecuteInTransaction
properly propagate and will send the error response packet to the client.ResponseErrorException
s thrown fromRequestPacketHandler
s log the first line of their stack trace, in case we want to track it down later.Checklist:
develop
branch