Fixes Error - Uncaught Exception Error: write EIO #92 #118

shar-mayank · 2025-07-23T09:16:17Z

This PR fixes the issue Error - Uncaught Exception Error: write EIO #92. Thanks to @vinaymaurya14, I went through his provided solution and fix the error message that was continuously popping when I execute the ./stealth-run.sh script. The app won't even quit that time and will through errors whenever any of the shortcut keys were pressed.
Now both the script and compiled app works as intended.

Error message was:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: write EIO
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:952:11)
at Socket._write (node:net:964:8)
at writeOrBuffer (node:internal/streams/writable:447:12)
at _write (node:internal/streams/writable:389:10)
at Writable.write (node:internal/streams/writable:393:10)
at console.value (node:internal/console/constructor:304:16) at console.log (node:internal/console/constructor:379:26)
at App.<anonymous> (/Users/xxx/Documents/Projects/interview-coder-withoupaywall-opensource/dist-electron/main.js:515:13)

Attached is the video of error:

WhatsApp.Video.2025-07-22.at.15.41.49.mp4

I tested it manually, used every shortcut key commands available and concluded that the app works perfectly! @bhaumikmaan and @Anshumansingh01, please look into this.

…th safeLogger calls

bhaumikmaan · 2025-07-24T05:28:39Z

electron/SafeLogger.ts

+        fs.mkdirSync(this.logDir, { recursive: true })
+      }
+    } catch (error) {
+      // Silently fail - we can't log the error since we're creating the logger


I don't think we should silently fail this - if this fails there is no way of figuring out what went wrong before or after

You're absolutely right. If the log directory creation fails, we should at least attempt to use a fallback location or provide some indication of the failure. I'll update this to try a fallback directory and use stderr as a last resort.

bhaumikmaan

Thanks for the PR - it is a good addition.
We can merge once the review is addressed

bhaumikmaan · 2025-07-24T06:08:34Z

electron/SafeLogger.ts

+    try {
+      fs.appendFileSync(filePath, message, 'utf8')
+    } catch (error) {
+      // Silently fail - we can't use console.log here as it would cause the same issue


This silent failing is fine as everything would be in the log file already.

Agreed, this silent failing is appropriate here since if we can't write to the log file, using console.log would defeat the purpose and potentially cause the original EIO error we're trying to solve.

bhaumikmaan · 2025-07-24T06:08:49Z

electron/SafeLogger.ts

+        }
+      })
+    } catch (error) {
+      // Silently fail


This can be logged normally

You're right, since this would be called during normal operation (not during logger initialization), we can safely log this error using our own logging methods.

bhaumikmaan · 2025-07-24T06:09:54Z

electron/SafeLogger.ts

+  // Clean up old logs (optional - call this periodically)
+  cleanupOldLogs(maxAgeDays: number = 7): void {


When is this called? I don't see any function calls
If it is user driven - how can a user call it?
If not we can make a path redirect where the user can go themselves and manually delete the file

This function isn't currently called anywhere. I'll either remove it entirely since users can manually manage log files, or if we want to keep it, I can add it as a startup routine that runs once when the app initializes. What would you prefer?

I don't think it is wise to clear logs at session startup in case one needs to track past errors.
You could do any of the following:

Give a button for log clearance

Add a message in the initial dialog box with a redirect or a path name so users can do it manually

Clear once a certain size limit is hit like 1 GB threshold (Put a message in the dialog box or the README) that the logs will clear after 1GB

I don't think it is wise to clear logs at session startup in case one needs to track past errors.

yeah, you are right!

You could do any of the following:

Give a button for log clearance

Add a message in the initial dialog box with a redirect or a path name so users can do it manually

Clear once a certain size limit is hit like 1 GB threshold (Put a message in the dialog box or the README) that the logs will clear after 1GB

Okay, I'm thinking of doing a combination of 2nd and 3rd by giving the option to delete it manually by redirecting to the logs directory and also implementing the deletion of logs once it hits 1 GB. I'll work on implementing this and will update ASAP!

bhaumikmaan · 2025-07-24T06:11:02Z

stealth-run.sh

nit: This shouldn't be a part of the diff - it gets automatically added when you run the application

shar-mayank · 2025-07-24T11:38:04Z

I'll make the necessary changes and will commit soon

- Add automatic log directory cleanup when exceeding 1GB in SafeLogger - Update WelcomeScreen with logs storage location for manual cleanup - Implement getDirectorySize() and cleanup methods for logs - Log cleanup actions for debugging purposes

shar-mayank

Add Automatic Storage Management (1GB Cleanup)

Changes

Logs: Auto-clear when log directory exceeds 1GB
UI Updates: Added storage locations and cleanup info to WelcomeScreen and SettingsDialog

Implementation

SafeLogger.ts: Added size checking and cleanup before writing logs
UI components updated to show file locations for manual cleanup

Testing

Tested manually by different methods like changing the directory size to 1 MB for testing, creating test cases for manual checking and creating a fake log file that exceeds 1GB by dd if=/dev/zero of=test-large.log bs=1024 count=1126400 and verifying the result manually.

Fixes storage accumulation issues while maintaining app functionality.

@bhaumikmaan, @Ornithopter-pilot, @us1415, @dev-opsss and @Anshumansingh01, please verify and merge. Thank you.

shar-mayank · 2025-07-26T17:48:25Z

Note to self: integrate OpenAI's Whisper when free from placements

shar-mayank · 2025-07-30T10:25:50Z

@bhaumikmaan, Please approve when you get time

Implement SafeLogger for improved logging and replace console logs wi…

707a60f

…th safeLogger calls

bhaumikmaan reviewed Jul 24, 2025

View reviewed changes

bhaumikmaan requested changes Jul 24, 2025

View reviewed changes

shar-mayank commented Jul 26, 2025

View reviewed changes

shar-mayank requested a review from bhaumikmaan July 26, 2025 17:47

		// Clean up old logs (optional - call this periodically)
		cleanupOldLogs(maxAgeDays: number = 7): void {

Fixes Error - Uncaught Exception Error: write EIO #92 #118

Are you sure you want to change the base?

Fixes Error - Uncaught Exception Error: write EIO #92 #118

Uh oh!

Conversation

shar-mayank commented Jul 23, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bhaumikmaan left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shar-mayank Jul 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shar-mayank commented Jul 24, 2025

Uh oh!

shar-mayank left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Add Automatic Storage Management (1GB Cleanup)

Changes

Implementation

Testing

Uh oh!

shar-mayank commented Jul 26, 2025

Uh oh!

shar-mayank commented Jul 30, 2025

Uh oh!

Uh oh!

shar-mayank Jul 26, 2025 •

edited

Loading

shar-mayank left a comment •

edited

Loading