search

odota / web

React web interface for the OpenDota platform
https://www.opendota.com
MIT License
1.08k stars 390 forks source link

Match page not loading after being parsed #3126

Closed CommunistMountain closed 7 months ago

CommunistMountain commented 7 months ago

Current Behavior Before parsing a match, the match page is fine. But after parsing a match, the match page cannot be loaded. Tried both Chrome and Firefox, with no extensions, same issue, so it is not a browser problem.

Expected behavior/code The match page should be loaded without error.

Console Output

TypeError: e.tower_status_radiant is null
    she https://www.opendota.com/assets/index-408ab163.js:4250
    Z8 https://www.opendota.com/assets/index-408ab163.js:30
    Uee https://www.opendota.com/assets/index-408ab163.js:34
    Hee https://www.opendota.com/assets/index-408ab163.js:34
    f_e https://www.opendota.com/assets/index-408ab163.js:34
    f_ https://www.opendota.com/assets/index-408ab163.js:34
    WA https://www.opendota.com/assets/index-408ab163.js:32
    mee https://www.opendota.com/assets/index-408ab163.js:30
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    mee https://www.opendota.com/assets/index-408ab163.js:30
    tl https://www.opendota.com/assets/index-408ab163.js:30
    pu https://www.opendota.com/assets/index-408ab163.js:32
    enqueueSetState https://www.opendota.com/assets/index-408ab163.js:30
    setState https://www.opendota.com/assets/index-408ab163.js:12
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:4278
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:4278
    u_e https://www.opendota.com/assets/index-408ab163.js:32
    g_e https://www.opendota.com/assets/index-408ab163.js:34
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    yd https://www.opendota.com/assets/index-408ab163.js:34
    WA https://www.opendota.com/assets/index-408ab163.js:32
    mee https://www.opendota.com/assets/index-408ab163.js:30
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    mee https://www.opendota.com/assets/index-408ab163.js:30
    tl https://www.opendota.com/assets/index-408ab163.js:30
    pu https://www.opendota.com/assets/index-408ab163.js:32
    enqueueSetState https://www.opendota.com/assets/index-408ab163.js:30
    setState https://www.opendota.com/assets/index-408ab163.js:12
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:2689
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:2689
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:2689
    u_e https://www.opendota.com/assets/index-408ab163.js:32
    g_e https://www.opendota.com/assets/index-408ab163.js:34
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    yd https://www.opendota.com/assets/index-408ab163.js:34
    WA https://www.opendota.com/assets/index-408ab163.js:32
    mee https://www.opendota.com/assets/index-408ab163.js:30
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    mee https://www.opendota.com/assets/index-408ab163.js:30
    tl https://www.opendota.com/assets/index-408ab163.js:30
    Bee https://www.opendota.com/assets/index-408ab163.js:32
    notify https://www.opendota.com/assets/index-408ab163.js:34
    i https://www.opendota.com/assets/index-408ab163.js:34
    o https://www.opendota.com/assets/index-408ab163.js:34
    p https://www.opendota.com/assets/index-408ab163.js:59
    t https://www.opendota.com/assets/index-408ab163.js:59
    dispatch https://www.opendota.com/assets/index-408ab163.js:59
    d https://www.opendota.com/assets/index-408ab163.js:2299
    promise callback*d https://www.opendota.com/assets/index-408ab163.js:2299
    ht https://www.opendota.com/assets/index-408ab163.js:2299
    t https://www.opendota.com/assets/index-408ab163.js:59
    getMatch https://www.opendota.com/assets/index-408ab163.js:4558
    componentDidMount https://www.opendota.com/assets/index-408ab163.js:4558
    u_e https://www.opendota.com/assets/index-408ab163.js:32
    g_e https://www.opendota.com/assets/index-408ab163.js:34
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    yd https://www.opendota.com/assets/index-408ab163.js:34
    WA https://www.opendota.com/assets/index-408ab163.js:32
    mee https://www.opendota.com/assets/index-408ab163.js:30
    unstable_runWithPriority https://www.opendota.com/assets/index-408ab163.js:19
    ap https://www.opendota.com/assets/index-408ab163.js:30
    mee https://www.opendota.com/assets/index-408ab163.js:30
    tl https://www.opendota.com/assets/index-408ab163.js:30
    RQ https://www.opendota.com/assets/index-408ab163.js:34
    cge https://www.opendota.com/assets/index-408ab163.js:30
    iee https://www.opendota.com/assets/index-408ab163.js:30
    wF https://www.opendota.com/assets/index-408ab163.js:30
    nee https://www.opendota.com/assets/index-408ab163.js:30
    nee https://www.opendota.com/assets/index-408ab163.js:30
    c6 https://www.opendota.com/assets/index-408ab163.js:34
    C_e https://www.opendota.com/assets/index-408ab163.js:34
    Kw https://www.opendota.com/assets/index-408ab163.js:34
    render https://www.opendota.com/assets/index-408ab163.js:34
    <anonymous> https://www.opendota.com/assets/index-408ab163.js:7311

Environment

Possible Solution Try looking at e.tower_status_radiant, and e.tower_status_dire too because probably radiant error triggered first

Additional context/Screenshots Example 1, Dire won (https://www.opendota.com/matches/7468052914) Example 2, Radiant won (https://www.opendota.com/matches/7467104474)

howardchung commented 7 months ago

Found an issue and checking in a fix