Tags
16 pages
Troubleshooting
Desktop Boot Loader Failure
Cross-machine computation time difference
The existing communication protocol within the group uses steady_clock as a timestamp to calculate the latency for each individual node. In a specific scenario, a message packet’s built-in timestamp was used, and this timestamp originated from another machine – resulting in an anomalous latency calculation.
As a side note: Gemini2.5 Pro shows promise of completely surpassing GPT-4.
WeChat Backup Tool Local Network Recognition Failed
I regularly clear out data on my phone, including photos and WeChat chat logs, backing them up to my computer. Previously, it worked seamlessly, allowing me to easily identify both my mobile phone and desktop PC within the same local network and directly back up the chat records to my computer. However, today everything has been failing.
Memory Layout and Binary Compatibility
C++ service crashed. The service depends on a static library for compilation. The static library made modifications, adding members to the header file and re-publishing the binary static library file. The service relies on the new binary library file, compiles and runs normally, but then crashes. The crash point appears fine, similar to the crashes caused by compiler upgrades – undefined behavior, an untrustworthy stack trace. Updating the service’s dependent header files allows it to mutate correctly, and running also works normally. A detailed explanation is needed, involving computer science knowledge, I suspect it’s related to memory layout, with examples for a thorough explanation.
Protobuf Zero Value Pitfalls: When Default Values Become an Invisible Killer of Business Logic
Background Service TCP Communication Anomaly Troubleshooting
Business Model: The backend service establishes a connection with the group’s market data gateway using TCP. Each time a connection is established, it must first send an authorization request and then continuously send heartbeat packages to maintain the connection status.
However, one day, an alert message was received indicating that the service had disconnected. After carefully examining the logs, it was discovered that the backend service was continuously sending heartbeat packages, but the other party did not respond at all, yet the connection remained open.