Add user profile pictures and refresh user info on login - #12

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Files matching telegramPhoto:\n'
fd -a 'telegramPhoto\.(ts|js)$' . || true

printf '\nFile outline:\n'
file="$(fd 'telegramPhoto\.(ts|js)$' . | head -n 1)"
if [ -n "${file:-}" ]; then
  ast-grep outline "$file" || true
  printf '\nFile contents with line numbers:\n'
  cat -n "$file"
fi

printf '\nSearch for request_access, open, telegramPhoto download:\n'
rg -n "request_access|/open|telegramPhoto|download_photo|getPhoto|file_path|new AbortController|AbortSignal|timeout|fetch\\(" . -S || true

printf '\nPackage/dependency clues:\n'
for f in package.json package-lock.json pnpm-lock.yaml yarn.lock bun.lockb; do
  [ -f "$f" ] && { echo "--- $f"; sed -n '1,220p' "$f"; }
done

Repository: noamokman/gate-bot

Length of output: 17169

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Command files:\n'
cat -n src/commands/open.ts
printf '\n--- requestAccess ---\n'
cat -n src/commands/requestAccess.ts

printf '\nRoute dashboard handlers context:\n'
sed -n '45,120p' src/web/routes/dashboard.ts | cat -n
printf '\nOpen/auth fetches:\n'
sed -n '1,160p' src/web/routes/auth.ts | cat -n

Repository: noamokman/gate-bot

Length of output: 12347

🌐 Web query:

Telegraf 4.16.3 node-fetch axios getUserProfilePhotos File download timeout abort

💡 Result:

In Telegraf 4.16.3, network operations (including getUserProfilePhotos and associated file downloads) are managed by an internal client that utilizes node-fetch and incorporates a hardcoded timeout value of 500,000 ms (500 seconds) for network requests [1][2]. If you are experiencing premature timeouts, aborts, or connectivity issues when downloading files or photos, consider the following technical factors: 1. Internal Client Timeout: The 500-second timeout is applied within src/core/network/client.ts for both API calls and media downloads [1][2]. This is separate from the handlerTimeout (default 90,000 ms or 90 seconds), which governs the maximum time a middleware/handler function can execute [3][4]. If your process hits the handlerTimeout first, the request will be aborted, potentially causing an unhandled promise rejection if not caught [3][5]. 2. Handler Timeout Configuration: If your code performs synchronous work or complex async chains while processing photos, you may need to increase the handlerTimeout in your Telegraf configuration to ensure the bot does not kill the process before the download completes [3]: const bot = new Telegraf(BOT_TOKEN, { handlerTimeout: 300_000 }); // Example: set to 5 minutes 3. Network and IPv6 Issues: Users running Telegraf on Node.js v20+ have reported ETIMEDOUT errors due to changes in how Node.js resolves IPv4/IPv6 addresses [6]. If you are encountering network-level timeouts, try disabling IPv6 or ensuring your environment correctly resolves the Telegram API endpoints [6]. 4. Implementation Pattern: To successfully retrieve a photo: - Call getUserProfilePhotos(userId) to obtain a file_id [7][8]. - Use getFile(fileId) to get the file_path [7][9]. - Construct the download URL using the bot token and the retrieved path [9][8]. - Ensure you are wrapping these calls in try/catch blocks, as getUserProfilePhotos will throw an error if the user has no photos or if the user_id is invalid [10][11]. If you find that the hardcoded 500s timeout is insufficient for your specific environment (e.g., extremely slow connections), it is a known limitation that the timeout cannot be easily overridden via standard configuration without modifying the client or using a custom proxy/agent [12][13].

Citations:

• 1: https://github.com/telegraf/telegraf/blob/master/src/core/network/client.ts
• 2: https://github.com/telegraf/telegraf/blob/0638cf4c/src/core/network/client.ts
• 3: TimeoutError: Promise timed out after 90000 milliseconds telegraf/telegraf#1479
• 4: Long polling silently hangs or swallows errors telegraf/telegraf#1234
• 5: https://stackoverflow.com/questions/68764023/node-js-and-telegraf-timeouterror-promise-timed-out-after-90000-milliseconds
• 6: Error When launch telegraf/telegraf#1981
• 7: https://github.com/telegraf/telegraf/blob/master/src/telegram.ts
• 8: https://community.latenode.com/t/retrieving-user-profile-photo-through-telegram-bot-api/26070
• 9: https://gist.github.com/letswritetw/bf661da50339ef6d6ef4c2fd3bedb751
• 10: Server down when use getUserProfilePhotos() telegraf/telegraf#573
• 11: https://gramio.dev/telegram/methods/getuserprofilephotos
• 12: [FR] Allow change fetch timeout telegraf/telegraf#1980
• 13: feat(client): add timeout option telegraf/telegraf#1348