Uploaded complete moirai_forecast_app contents

README.md

@@ -4,7 +4,7 @@ emoji: 📈
 colorFrom: blue
 colorTo: indigo
 sdk: gradio
-sdk_version: "4.44.0"
+sdk_version: "6.26.0"
 python_version: "3.11"
 app_file: app.py
 pinned: false

requirements.txt

@@ -3,14 +3,16 @@ uni2ts>=2.0.0
 torch>=2.1
 gluonts>=0.14
 
-# Pinned explicitly: huggingface_hub 1.0+ removed the HfFolder class,
-# but gradio 4.44.x's oauth.py still does `from huggingface_hub import
-# HfFolder, whoami` unconditionally at import time -- so `import gradio`
-# crashes immediately on any resolution that picks huggingface_hub>=1.0.
-# uni2ts only floors huggingface_hub>=0.23.0 with no ceiling, so without
-# this pin pip is free to grab the latest 1.x. Confirmed against a real
-# Space's runtime traceback, not a guess.
-huggingface_hub>=0.23.0,<1.0
+# --- REVERSED after upgrading to gradio 6.26.0 ---
+# This used to be pinned `<1.0`: gradio 4.44.x's oauth.py did
+# `from huggingface_hub import HfFolder, whoami` unconditionally at import
+# time, and huggingface_hub 1.0 removed HfFolder, so any resolution that
+# picked huggingface_hub>=1.0 crashed on `import gradio` before app.py even
+# ran. That's gone upstream -- gradio's own changelog has "Allow gradio to
+# run with huggingface_hub 1.x", landed well before 6.26.0. uni2ts's
+# PyTorchModelHubMixin.from_pretrained() (what moirai_model.py actually
+# calls) isn't on the removed API either. No known reason left to cap this.
+huggingface_hub>=0.23.0
 
 # Data
 yfinance>=0.2.40
@@ -18,7 +20,27 @@ pandas>=2.0
 numpy>=1.24
 
 # UI (Hugging Face Spaces)
-gradio>=4.40
+# Pinned to the 6.x line (floor at the version this build was verified
+# against, ceiling below the next major) instead of a bare `>=` -- that's
+# what let pip drift onto an untested gradio/starlette/fastapi combination
+# last time. app.py's own component usage (Blocks/Tab/Row/Textbox/Dropdown/
+# Slider/Button/Markdown/Dataframe/Accordion/JSON/Radio) doesn't touch any
+# of the parameters the Gradio 6 migration guide removed, so no app.py
+# changes were needed for this bump.
+gradio>=6.26.0,<7
+
+# --- REMOVED after upgrading to gradio 6.26.0 ---
+# This file used to pin `starlette<1.0` because gradio 4.44.x's routes.py
+# called Jinja2Templates.TemplateResponse the pre-1.0 way
+# (`TemplateResponse(name, context)`), which breaks against Starlette>=1.0
+# (the context dict lands in the `name` slot -> Jinja2 tries to hash it as
+# a cache key -> `TypeError: unhashable type: 'dict'` on every page load).
+# Gradio's own changelog shows a later commit -- "upgrade starlette
+# dependency to 1.0.1 or higher" -- that updated routes.py to the new
+# `TemplateResponse(request, name, context)` call and raised gradio's own
+# floor accordingly. That fix is already in 6.26.0, so pinning
+# starlette<1.0 now would fight gradio's real requirement instead of
+# working around a bug, and could make pip's resolution fail outright.
 
 python-dateutil
 pytz