-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
osu://edit/
editor timestamp links with hit objects crash chat
#25614
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
Comments
Sentry issue: OSU-TS2 |
For me the game is being crashed by posting timestamp link in chat: |
It also happens when you type osu/osu.Game/Online/Chat/MessageFormatter.cs Line 271 in aa87e0a
Unless it's used somewhere, I would expect the parser to just ignore anything |
using osu/osu.Game.Tests/Visual/Online/TestSceneChatLink.cs Lines 92 to 94 in b2e1a63
|
I'm closing the issue as the crash is fixed. Supporting the other timestamp link syntax can be tracked separately. |
Type
Crash to desktop
Bug description
Editor timestamp link that are posted in full (
osu://edit/xx:yy:zzz (u,v,...)
) will throw unexpected exceptions when posted in chat.First reported in https://discord.com/channels/188630481301012481/1097318920991559880/1179770517994078248.
Repro branch https://github.com/ppy/osu/compare/master...Susko3:fix-chat-editor-timestamps?expand=1, failing test commit: 8d02745
This commit adds the following test string which will generate two overlapping
OpenEditorTimestamp
links.The overlapping links break the logic here: (this tries to add the text in between the links – text of negative length)
osu/osu.Game/Graphics/Containers/LinkFlowContainer.cs
Line 50 in 40dbf09
I'm not sure what's the expected outcome when the parser is given the string
osu://edit/00:12:345 (1,2)
. Possible outcomes:Keep in mind that
osu://edit/00:12:345%20(1,2)
in chat only partially works, it'll move to the requested timestamp, but won't select any objects.Screenshots or videos
The parsed links in the failing test:
Version
b2e1a63
Logs
The text was updated successfully, but these errors were encountered: