claude-code - 💡(How to fix) Fix [Bug] Weekly limit reset does not reset daily limit; 5H rolling window shifts inconsistently [1 participants]

[{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:112:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12898)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:17:25.086Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:112:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12898)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:24:35.313Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:112:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12898)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:24:52.006Z"},{"error":"MaxFileReadTokenExceededError: File content (31600 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at nu7 (/$bunfs/root/src/entrypoints/cli.js:4854:12789)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:27:56.004Z"},{"error":"AxiosError: Request failed with status code 404\n at hn (/$bunfs/root/src/entrypoints/cli.js:115:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12716)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:27:58.943Z"},{"error":"AxiosError: Request failed with status code 404\n at hn (/$bunfs/root/src/entrypoints/cli.js:115:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12716)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:28:00.271Z"},{"error":"AxiosError: Request failed with status code 404\n at hn (/$bunfs/root/src/entrypoints/cli.js:115:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12716)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:28:02.218Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:112:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12898)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:28:07.400Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:112:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12898)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T12:28:24.006Z"},{"error":…

TL;DR

The issue seems to be related to connection refused errors and file reading limits, suggesting a potential problem with the application's ability to handle requests or read files within specified limits.

Guidance

• Review the error logs to identify patterns or commonalities among the connection refused errors (ECONNREFUSED) and file reading errors (MaxFileReadTokenExceededError).
• Consider implementing retry mechanisms for requests that fail due to connection refused errors to handle temporary network issues.
• For MaxFileReadTokenExceededError, use the suggested offset and limit parameters to read specific portions of the file instead of the whole file at once.
• Investigate why the application is attempting to read large files or make numerous requests that exceed limits, and optimize the logic to reduce the load.

Example

No specific code example can be provided without more context on the application's codebase, but generally, handling MaxFileReadTokenExceededError might involve modifying file reading logic to use pagination or streaming:

// Hypothetical example of reading a file in chunks
const readFileInChunks = (filePath, chunkSize) => {
  const fileStream = fs.createReadStream(filePath, { highWaterMark: chunkSize });
  // Process the file stream in chunks
};

Notes

The provided error logs are truncated, which might limit the ability to fully diagnose the issue. Additionally, without specific details about the application's architecture or the code responsible for file reading and network requests, the guidance is somewhat generalized.

Recommendation

Apply workaround: Implementing retry mechanisms for connection refused errors and optimizing file reading logic to handle large files in chunks can help mitigate the issue. This approach is chosen because it directly addresses the errors mentioned in the logs and can be implemented without requiring a full understanding of the application's internal workings or waiting for a potential version upgrade.