Chapter 147: Dirty Logs and Boundaries

He closed the old laptop, and the power indicator went dark. The air conditioning in the server room kept blowing, brushing against the sweat-damp back of his neck and sending a faint shiver through him. The muscle around his left ankle spasmed again, like a rubber band stretched to its limit suddenly snapping back. He braced himself on the edge of the desk and stood, shifting all his weight onto his right leg before slowly easing some of it back onto the left. The pain was dull, but its location was precise. He logged that parameter in his mind, pulled open the drawer, and stuffed the half-finished packet of soda crackers and the bottle of hydrotalcite into his canvas bag. The rasp of the zipper closing sounded especially sharp in the quiet server room.

The machine room on the third floor of Building B was at the end of the corridor. The motion-sensor light in the stairwell was broken; only the green glow of the emergency exit sign barely traced the outline of the steps. He kept one hand on the wall as he climbed—one step, pause, then another. The strap of the canvas bag bit into his collarbone, the battered old computer with peeling paint weighing inside it. The door to the third-floor server room was ajar, and from within came the roar of old server fans, mixed with a low metallic grinding noise.

He pushed the door open. A man in a gray jacket sat by the window, staring at three monitors lined up side by side. Dense terminal logs were streaming across the screens. The man turned his head. The whites of his eyes were webbed with red, and bluish stubble shadowed his jaw.

“Lin Chen?” the man said hoarsely. “Engineer Zhou told me you were coming. I’m Engineer Li.”

Lin Chen nodded and set his canvas bag down on the empty desk beside him.

Engineer Li handed over an external hard drive and a printed sheet of paper. “Six months of production logs from the client. Three hundred megs, plain text. The previous script did full regex matching on everything and hit OOM halfway through. Maxed out memory, process got killed by the system. The client wants cleaned, structured data first thing tomorrow morning. Only these four fields: timestamp, source IP, error code, first line of the stack trace. Format isn’t fixed. Some lines are broken, some mix GBK and UTF-8, and some are cut off into gibberish. Figure it out. If you can get it running, bring the results at nine tomorrow.”

Lin Chen took the drive. The printed sheet contained the client’s original field definitions, scribbled in messy handwriting, with coffee stains around the edges. He asked no questions. He plugged in the drive and mounted it. The terminal spat out a directory tree—dozens of .log and .txt files piled together. He picked the biggest one and dragged it into the terminal. wc -l. Four hundred and twenty thousand lines.

He opened the file. The first hundred lines still followed a visible pattern. Starting from line 101, the line breaks vanished; two log entries stuck together, with \x00 null characters and unrecognizable byte sequences jammed in between. A regex engine faced with that kind of structure would choke directly on its backtracking mechanism. The memory hadn’t been blown by the data itself—it had been devoured by a matching state machine trapped in a dead loop.

He closed the file manager and created a new script. import sys, import codecs, import re.

He didn’t write any elaborate classes, only a generator function. Read line by line, never loading the whole file into memory at once. If an encoding error appeared, skip the bad bytes with errors='ignore' and preserve the readable portions. The state machine logic was simple: three boolean variables marked whether the current line belonged to the header, body, or stack trace. When a timestamp regex appeared, reset the state; when Traceback appeared, enter stack-trace capture mode; when consecutive blank lines or a specific delimiter appeared, output the current buffered dictionary and clear the state.

He wrote the code slowly. After every function, he stopped and simulated the execution flow in his head. There were too many edge cases: how should broken lines be stitched together? How should garbled text be isolated? If a stack trace spanned multiple lines, where should it be cut? He took out a black gel pen and drew a flowchart on the back of the printed sheet. Arrows, decision boxes, exception branches. The lines crossed over one another, but the logic closed cleanly.

Three in the afternoon. The temperature in the server room had risen. Engineer Li went next door to take a call; when he came back, he set a bottle of cold mineral water on the corner of Lin Chen’s desk. Lin Chen didn’t touch it. He only unscrewed his own thermos and swallowed half a mouthful of warm water. The sourness in his stomach eased a little. He tore open the soda crackers, broke them into small pieces, and chewed slowly. Crumbs fell onto the keyboard, and he wiped them away with the pad of his finger.

His left foot had started going numb. Not pain—more the swollen deadness of poor circulation. He got up, walked to the water dispenser in the corner of the server room, and braced himself against the wall to do calf raises. His calf muscles tightened, squeezing the veins and helping the blood return. Ten times. Twenty. The numbness receded a little, replaced by a sharper soreness. He went back to his seat and kept typing.

Five forty. The script was finished. He saved it and named it log_parser_v1.py. He opened the terminal, pointed it at the test file. python log_parser_v1.py test.log > output.csv. Enter.

The terminal began to scroll. No stuttering. No memory spike warnings. The progress bar advanced smoothly. He opened the system monitor. The memory-usage graph was a straight line hugging the bottom, peaking at 14.7 MB. CPU usage fluctuated at about thirty percent of a single core. Four hundred and twenty thousand lines, eleven seconds.

He opened the output CSV. He spot-checked twenty random rows. The timestamps lined up, the IP format was correct, the error codes had been extracted accurately, and the first line of each stack trace was intact. Garbled fragments had been replaced with [INVALID], without contaminating neighboring fields.

He let out a long breath. The T-shirt on his back was already soaked through, stuck to the chair. He closed the terminal, packed the script and output file together, and renamed the archive log_clean_20100914.zip. Then he sent it to Engineer Li through the intranet shared directory.

Six twenty. Engineer Li replied: “Ran it. Fields line up, no data missing. Tomorrow morning at nine, bring a USB drive to the server room. The client’s tech team wants to go over production-environment adaptation. Watch out—their servers run CentOS 5.8, Python 2.4. If your script uses any syntax above 2.6, it’ll error out immediately.”

Lin Chen stared at the screen. Python 2.4. No with statement, no yield from, some parts of the standard library behaved differently. The generator and codecs usage he had just written both needed adjustments for 2.4. He opened a blank document and started replacing things line by line. with open became manual file-handle cleanup with try-finally. List comprehensions were broken apart into explicit loops. Every string method introduced after 2.5 was commented out.

Outside the window, the sky darkened. Streetlights came on, their dim yellow glow filtering through the blinds and laying parallel shadows across the desk. People in the server room left one after another, and the sound of keyboards grew sparse. Before leaving, Engineer Li patted him on the shoulder. “Get it done early. They’re posting the midterm assessment list for the training camp tomorrow. Anyone who doesn’t make it has to handle withdrawal in the afternoon.”

The door shut. The corridor returned to silence.

Lin Chen didn’t look up. His fingers moved over the keyboard in a steady rhythm. He didn’t need to see the list. He only needed to get the code working in a 2.4 environment. Adaptation was more tedious than rewriting, but the logic was definite. He checked each line, tested each line. At seven forty, the final version was packaged. Memory usage: 16.2 MB. Runtime: 13 seconds. Compatible with 2.4.

He closed the computer. His left foot had lost all feeling now; he could only support himself with his right leg and a gait like a man leaning on a crutch. Slowly, he cleared the desk and threw the empty cracker wrapper into the trash. His phone vibrated in his pocket. He pulled it out, and the screen lit up.

Bank message: Transfer successful. Balance: 112.4 yuan. Wang Guiying replied: “The money came through. Xiaoman didn’t have a spell today, slept soundly. The transformer at the village entrance burned out this afternoon. The power office says they’ll fix it tomorrow. No electricity tonight, so get some rest early. Don’t stay up.”

He stared at the line of text, his thumb hovering above the screen. No electricity. That meant he wouldn’t be able to sync the code remotely tonight, and he wouldn’t be able to call back to the landline at home either. He glanced at the lower-right corner of the laptop screen: battery 87%. Enough to last until tomorrow morning.

He switched the phone to silent mode and slipped it back into his pocket. When he walked out of the server room, several people had already gathered in front of the bulletin board at the end of the corridor. A sheet of white paper had been posted there with a boldface title: Training Camp Midterm Assessment Elimination Notice. Three names had been circled in red pen. Lin Chen didn’t go over to look. One hand on the wall, he made his way down step by step. The motion-sensor light in the stairwell still hadn’t come on. Only the green glow of the emergency exit sign lit the shadow he cast onto the stairs.

Back in the dorm, he plugged in the charger. The indicator light came on. He spread open a blank notebook and wrote tomorrow’s to-do list on the first page:

1. 9:00 — bring USB drive and report
2. Confirm dependencies in the 2.4 environment
3. Leave time for offline debugging
4. Send medicine-expense receipt

The pen paused. Under the fourth item, he added a line in smaller writing:

If eliminated, backup plan: take outsourcing jobs, cover Xiaoman’s medicine costs.

The wind had picked up outside. The sound of leaves rubbing together was faint. He closed the notebook and switched off the desk lamp. In the darkness, only the charger's tiny glow flickered in the corner. He closed his eyes, his breathing steady. Beneath the blanket, his left foot twitched faintly, but he didn’t move. Tomorrow at nine, the code had to run in production.

It could not crash.