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

[BUG] Typos in error messages #4411

Open
rasssta opened this issue Jan 15, 2025 · 1 comment
Open

[BUG] Typos in error messages #4411

rasssta opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
bug Something isn't working.

Comments

@rasssta
Copy link

rasssta commented Jan 15, 2025

Printer model

MK4S

Firmware version

6.2.0-RC1

Upgrades and modifications

MMU3

Printing from...

PrusaLink/PrusaConnect

Describe the bug

Typo/weird spelling in error message for code: "XX535"

"it might have beet not executed correctly."

How to reproduce

Files/lines affected:

text: "G-code command was too long and did not fit in the internal buffers. As a result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

"result, it might have beet not executed correctly."

Expected behavior

Guess it should say "It might not have been executed correctly."?

Files

No response

@rasssta rasssta added the bug Something isn't working. label Jan 15, 2025
@CZDanol
Copy link
Contributor

CZDanol commented Jan 16, 2025

Hello, this has already been fixed by prusa3d/Prusa-Error-Codes#171, but has not been merged into the 6.2 yet - I will arrange the merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

2 participants