Bla reports: [crash] just crashed the serve ... #3909
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3909
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bla reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Steps to reproduce
Try to send a mail with that text as body
(c@#ee82ee)Bla (c@#00FF00)can (c@#FFFF00)do (c@#FF7F00)it (c@#990012):-P(c@#ffffff)
Not sure how gitea handles ESC control character so I type it out
ESCc@#ee82ee)Bla ESCc@#00FF00)can ESCc@#FFFF00)do ESCc@#FF7F00)it ESCc@#990012):-PESCc@#ffffff)
edit: per comment edit you can get the original text including ESC character to copy&paste for tests
seems to be my code. hm.
does the recipient have to be ignoring the sender?
still can't replicate it locally, even when ignoring myself...
figured out how to repeat it:
should be fixed in
8dc0347e03
, as well as several other crashes that could happen due to malformed user input.added to the 1.1.118 milestone
sry thought I copied it into the body not subject, probably misclicked
this is live