[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hyperliquid - timeframes are incorrect #24230

Closed
gaardiolor opened this issue Nov 11, 2024 · 1 comment · Fixed by #24231
Closed

Hyperliquid - timeframes are incorrect #24230

gaardiolor opened this issue Nov 11, 2024 · 1 comment · Fixed by #24231
Assignees
Labels

Comments

@gaardiolor
Copy link
Contributor

Operating System

n/a

Programming Languages

Python

CCXT Version

4.4.29

Description

Hello :)

The advertised hyperliquid timeframes have a couple of issues:

  • 6h is advertised, but is not supported
  • 8h is not advertised, but is supported
  • the timeframes keys 1m and 1M have the same value, 1m. The value of key 1M should be 1M (not sure where this is used though)

So

  • here '6h': '6h', should be changed to '8h': '8h',
  • here '1M': '1m', should be changed to '1M': '1M',
    from datetime import UTC
    e = ccxt.hyperliquid()
    e.aiohttp_proxy = 'http://127.0.0.1:8080'
    print(e.timeframes)
    for timeframe in list(e.timeframes.keys()) + ['8h']:
        try:
            await e.fetch_ohlcv('BTC/USDC:USDC', timeframe)
            print(f"timeframe {timeframe} OK")
        except ccxt.ExchangeError:
            print(f"timeframe {timeframe} ERROR")

{'1m': '1m', '3m': '3m', '5m': '5m', '15m': '15m', '30m': '30m', '1h': '1h', '2h': '2h', '4h': '4h', '6h': '6h', '12h': '12h', '1d': '1d', '3d': '3d', '1w': '1w', '1M': '1m'}
timeframe 1m OK
timeframe 3m OK
timeframe 5m OK
timeframe 15m OK
timeframe 30m OK
timeframe 1h OK
timeframe 2h OK
timeframe 4h OK
timeframe 6h ERROR
timeframe 12h OK
timeframe 1d OK
timeframe 3d OK
timeframe 1w OK
timeframe 1M OK
timeframe 8h OK

Thanks!

Code

No response

@sc0Vu sc0Vu self-assigned this Nov 12, 2024
@sc0Vu sc0Vu added the bug label Nov 12, 2024
@sc0Vu
Copy link
Contributor
sc0Vu commented Nov 12, 2024

@gaardiolor Thanks. We'll fix this asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants