- Executors
-
Learn
Python Learning Hub Runnable examples, NumPy, pandas, and more C & C++ Learning Hub Pointers, memory, STL, and modern C++ C# Learning HubC# basics, OOP, LINQ, async, and .NET exercises Python Algorithms Search, sorting, recursion, and visualizers O(n) C & C++ Algorithms Compare algorithms implemented in C and C++
Updates Tagged with: INFRASTRUCTURE
Stay informed with the latest improvements, new tools, feature releases, and platform announcements from CodeUtility.
Fixed: reconnects and disconnects when printing Japanese and Unicode text
The production fix applies across programming languages, especially to programs that print Japanese text.
Some programs printing Japanese, other Unicode text, or emoji could show “Reconnecting…” or disconnect before execution finished. Output could be split in the middle of a character, causing the browser to reject it.
For example, run this Python code: print("日本語" * 500). It prints 日本語 500 times. Previously, depending on how output was split, this could interrupt the connection. The output now completes correctly in our production verification.
The fix is live in production across server-side execution languages, including Python, C, C++, Java, and more. It preserves complete characters in normal execution and debugger output. This is especially relevant for Japanese output, and also protects other Unicode text and emoji.
Refresh the page and run your code again. This resolves the output-related cause of reconnects and disconnects described here; unrelated network interruptions can still occur. Sorry for the disruption, and thank you for your patience.
Execution and workspace services restored
This morning's interruption affecting signed-in workspace saves and server-side code execution has been resolved. All services are operating normally.
Earlier today, an infrastructure issue temporarily affected auto-save for signed-in workspaces and some server-side code executions across supported languages.
The affected infrastructure has been recovered, workspace access and execution have been restored, and all services are operating normally. Existing workspace data remains available. If you still see a previous error, please refresh the page and try again. We apologize for the disruption.