[WIP] Update Flask dependency to 3.1.2 to fix Docker build failures

[Copilot]

• Replace Flask==3.1.3 with Flask==3.1.2 in 29 UTF-8 requirements.txt files
• Handle UTF-16LE encoded files (openstreetmap and svg-open-street-map) separately
• Verified all 31 requirements.txt files now have Flask==3.1.2
• No remaining Flask==3.1.3 references in non-deprecated files

Original prompt

The current PR #1189 updates Flask to 3.1.3, but this version doesn't exist on PyPI, causing all Docker builds to fail. Flask 3.1.3 cannot be found in the Python Package Index.

Update the PR to use Flask 3.1.2 (the latest stable 3.1.x release available), which also solves the security vulnerabilities while being a verified, publicly available version. This will fix the failing workflows:

• Semantic Segmentation workflow
• ESPNet TTS workflow
• All other container builds that depend on Flask

Key updates needed:

• Change Flask from 3.1.3 → 3.1.2 (latest stable available on PyPI)
• Keep all other dependency upgrades as they are properly pinned and available
• Ensure Werkzeug stays at 3.1.6 (compatible with Flask 3.1.2)
• Verify all 33 requirements.txt files and 9 package-lock.json files have correct versions
• Update only non-deprecated components as specified in the original PR

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Update PR to update Python to the most recent version that is relatively safe, and definitely solves the dependency issues that are causing current workflows to fail.

Assistant: I'll help you update the PR to fix the Python dependency issues. Let me first examine the current PR and understand what security vulnerabilities need to be addressed.

Assistant: Now let me check the failing workflows to understand what's breaking:

Assistant: Now let me get the specific job logs for the failing workflows to understand what's breaking:

Assistant: Now I understand the issue! The PR is failing because Flask 3.1.3 does not exist in PyPI. The error shows PyPI only has Flask versions up to 1.0+ but not 3.1.3. This suggests the PR's dependency versions are incorrect or don't exist yet in PyPI.

Let me search for the actual requirements files in the PR to understand what needs to be fixed:

Assistant: Based on my investigation, I can see the issue clearly. The PR #1189 updates Flask to version 3.1.3, but the error shows that Flask 3.1.3 doesn't exist in the PyPI repository (pip can't find it). Additionally, two workflows are failing:

1. Semantic Segmentation (mmsemantic-segmentation) - fails on Flask dependency
2. ESPNet TTS - similar dependency issue

The problem is that Flask 3.1.3 doesn't actually exist as a published version. Looking at the valid versions shown in the error, the highest available Flask 3.x version is in the 3.0.x or 3.1.x range, but not 3.1.3 specifically.

Let me create an updated PR that uses a safe, verified Flask version while still solving the security vulnerabilities:

Assistant: Perfect! I've submitted a request to update the PR with Flask 3.1.2 (the latest stable version available on PyPI) instead of the non-existent Flask 3.1.3.

Here's what I identified:

The Problem

The workflow failures are due to Flask 3.1.3 not existing on PyPI. When the Docker builds try to pip install flask==3.1.3, the installation fails with:

ERROR: Could not find a version that satisfies the requirement flask==3.1.3
ERROR: No matching distribution found for Flask==3.1.3

This is causing cascading failures across multiple workflows:

• Semantic Segmentation (mmsemantic-segmentation.yml) - Failed
• ESPNet TTS (espnet-tts.yml) - Failed
• And potentially all other non-deprecated containers

The Solution

The PR will be updated to:

1. Flask: 3.1.3 → 3.1.2 (latest stable release on PyPI)
2. Keep all other dependency upgrades as they are (they're all verified and available):
   • Werkzeug: 3.1.6 ✓
   • requests: 2.33.0 ✓
   • Pillow: 12.1.1 ✓
   • Jinja2: 3.1.6 ✓
   • And all npm packages updated correctly

Why This Works

• Flask 3.1.2 is the latest stable 3.1.x release and is publicly available on PyPI
• It maintains full API compatibility with the codebase (no removed/deprecated features being used)
• Werkzeug 3.1.6 is fully compatible with Flask 3.1.2
• Still fixes all the security vulnerabilities targeted in the original PR
• The change applies to all 33 Python requirements.txt files across non-deprecated components

The updated PR will restore all passing workflows while maintaining the security improvements intended in the original PR.

This pull request was created from Copilot chat.