Google Cloud Function返回请求处理错误，求问题排查及日志调试方案

First: Fix the Core Function Crash #

The immediate issue with your code is that you're returning a raw requests.Response object directly from your function. Google Cloud Functions expects a serializable response (like a JSON string, plain text, or a properly formatted HTTP response object), and the Response object can't be automatically serialized—this is why your function is crashing.

Here's a corrected version of your function that returns valid, serializable content:

import requests
import logging

# Set up logging once outside the function for better performance
logging.basicConfig(level=logging.INFO)

def check_refresh_date(request):
    try:
        # Add a timeout to prevent hanging requests
        response = requests.get(
            "https://coronavirus.data.gov.uk/downloads/json/coronavirus-cases_latest.json",
            timeout=10
        )
        # Return the parsed JSON data (or use response.text for raw string)
        return response.json()
    except Exception as e:
        # Log the full error stack for debugging
        logging.error("Function failed", exc_info=True)
        # Return a user-friendly error message with HTTP 500 status
        return f"Error fetching data: {str(e)}", 500

Key fixes here:

• Moved imports outside the function to avoid reloading modules on every execution (improves cold start time)
• Added a timeout to the requests.get() call to prevent the function from timing out if the external API is slow
• Wrapped code in a try-except block to catch and handle errors
• Returns parsed JSON (a serializable dict) instead of the raw Response object

Temporary Workaround for Missing Detailed Error Logs #

Since you can't get crash details due to that known issue, adding explicit error logging and handling as shown above will let you:

• See full error stacks in your Cloud Functions logs (look for the "Error" level logs)
• Get a specific error message directly in your browser instead of the generic "could not handle the request" message

If you want even more visibility, you can also use Cloud Functions' built-in logging to write custom debug messages. For example, add logging.info("Fetched data successfully") after a successful API call to confirm flow.

Clean Up Your Dependencies #

Looking at your requirements.txt, you've included several packages (like numpy, pandas) that aren't used in your current function. Removing unused dependencies will:

• Reduce the size of your deployment package
• Speed up cold start times for your function
• Avoid potential conflicts with unnecessary packages

Your minimal requirements.txt only needs:

requests==2.24.0

Tips for Future Expansion #

As you extend this function, keep these best practices in mind:

• Handle specific exceptions (like requests.exceptions.ConnectionError, json.JSONDecodeError) instead of catching all exceptions broadly—this makes debugging easier
• Validate the incoming request (if you start accepting request data) to avoid unexpected inputs breaking your function
• Consider caching the API response if you don't need real-time data, to reduce external API calls and improve performance

内容的提问来源于stack exchange，提问作者Bhavesh Ghodasara