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

Getting error -2 #53

Open
Ponjimon opened this issue Sep 15, 2019 · 10 comments
Open

Getting error -2 #53

Ponjimon opened this issue Sep 15, 2019 · 10 comments

Comments

@Ponjimon
Copy link

Latest patch replays, getting error -2

@ebshimizu
Copy link
Owner

-2's the general failure code. I'll need to take a closer look. Can you send/post a link to a replay that's causing this error? I've been parsing replays from last week without issue.

@Ponjimon
Copy link
Author

Ponjimon commented Sep 16, 2019 via email

@Ponjimon
Copy link
Author

As promised, here are my latest two replays (both won't work) https://github.com/lookapanda/hots-parser-replay

@ebshimizu
Copy link
Owner

got them, thanks! will take a look this week

@Ponjimon
Copy link
Author

Ponjimon commented Sep 16, 2019 via email

@ebshimizu
Copy link
Owner

ebshimizu commented Sep 19, 2019

hm, I'm unable to reproduce any error when parsing these files on my machine. What platform are you running on? I'm running a Windows machine using Node 10 and the latest release of this code (tag 2.47.3)

I have gotten some reports of parsing issues on other platforms in the past involving a dependent module.

@Ponjimon
Copy link
Author

Ponjimon commented Sep 19, 2019 via email

@ebshimizu
Copy link
Owner

hmm yeah you might be running into some issues with the stormreplay module used in heroprotocol. That module uses a native extension to accelerate the replay extraction, but sometimes runs into problems. You can try to disable the native extension or possibly try downgrading heroprotocol to the 1.0 branch in the package manifest and see if it works.

@patonz
Copy link

patonz commented Sep 8, 2020

hi @ebshimizu , got same error today with some games played yesterday. Tell me if u have the same issue so we can fix together if u need some help

@ebshimizu
Copy link
Owner

There have been a few issues with the base heroprotocol repository (Blizzard/heroprotocol#92) and this package had to swap over to a fallback. First try re-installing the hots-parser package, and then let me know if the issue still persists.

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

No branches or pull requests

3 participants