Parameter verification failed startTime || endTime

[hackcatml]

Describe the bug
Unable to retrieve 1W timeframe OHLCV data from Bitget.

To Reproduce
Steps to reproduce the behavior:
pyne data download ccxt --symbol "BITGET:BTC/USDT:USDT" --timeframe 1W --from "2025-10-07"

Expected behavior
The command should successfully download 1W timeframe OHLCV data.

Screenshots

Environment:

• OS: macOS
• Version: (e.g. Ubuntu 22.04, Windows 11)
• Python version: 3.12
• How you ran the script: pyne command

Additional context
Add any other context about the problem here.

[wallneradam]

Root Cause

The Bitget API enforces strict timeframe-dependent limits on OHLCV data requests:

• 1w (weekly): Maximum 12 bars (84 days)
• 1d (daily): Maximum 300 bars
• 4h (4-hour): Maximum 1000 bars
• 1h/1m: Maximum 200 bars (safe default)

When PyneCore's CCXT provider didn't have Bitget in the known_limits dictionary, it used the default limit of 100 bars. For weekly timeframes, this meant requesting ~700 days of data in a single API call, which exceeded Bitget's 84-day limit → "Parameter verification failed startTime || endTime" error.

Solution

Enhanced the known_limits dictionary to support timeframe-specific limits:

known_limits = {
    'binance': 1000,  # Simple int (backward compatible)
    'bitget': {       # Timeframe-specific dict
        '1w': 12,
        '1d': 300,
        '4h': 1000,
        'default': 200
    },
    # ... other exchanges
}

The download logic now checks if the limit is a dict and selects the appropriate value:

if isinstance(limit_config, dict):
    limit = limit_config.get(timeframe, limit_config.get('default', 100))
else:
    limit = limit_config

Benefits

✅ Weekly downloads now work (12-bar limit respected)
✅ Optimal performance for all timeframes (no artificial slowdowns)
✅ Backward compatible (existing exchanges unaffected)
✅ Extensible (easy to add other exchanges with timeframe limits)

The fix will be included in the next PyneCore release. Thanks for reporting!