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

Having an issue with crashing with RollStats #7

Open
JamesMowery opened this issue Oct 10, 2015 · 4 comments
Open

Having an issue with crashing with RollStats #7

JamesMowery opened this issue Oct 10, 2015 · 4 comments
Assignees
Labels

Comments

@JamesMowery
Copy link

screen shot 2015-10-10 at 10 25 35 pm

Update: I was getting an error, but not as displayed above. It was just a blank error message.

Update 2: Moments after posting about my screw up and again installing the correct, updated script from the @manveti fork I got the error — just completely blank — again. No interaction in the chat at all while this happened. It is just shutting down on its own. Updated the image above.

@JamesMowery
Copy link
Author

Hey guys. We were attempting to address this issue on Roll20's forum. I think it is still the same related issue sneaking up.

Also, I'd assign a label, but I can't figure out how, so I apologize. I've attached a screen shot of the error and the output again, so hopefully this helps. I also wrote the same in the forum thread. Hopefully this helps.

@Lithl Lithl added the bug label Oct 10, 2015
@Lithl
Copy link

Lithl commented Oct 10, 2015

Labels can only be set by people who are collaborators on the repo. @manveti has to set you as a collaborator manually. I've added [bug] to this for you, but I'll let manveti deal with the actual issue since he's the author of RollStats. =)

@JamesMowery
Copy link
Author

Okay, so I screwed this up a bit. The error above was not the error I was getting. I re-copied in all the scripts to try to fix the error (on the off chance that was the issue), and I re-installed the old one. Then I saw this error again, which made me post here again. That's my bad. However, there was still an issue.

When I installed the newer (and correctly updated) script from a fork from @manveti I kept having the sandbox shut down and it said there was an error. The issue is that there was no error message at all. Just completely blank red warning message stating that there was an error, but no description of it thereafter.

I've correctly installed the scripts again right now from the @manveti fork so I'll monitor this on my next game and see if it happens again. If so, I'll update the error here as perhaps there's something else we are missing. The problem is that without an error message, I can't imagine it's too helpful to anyone.

I'll keep on top of it.

@JamesMowery
Copy link
Author

Well that didn't take long. I just installed the new (correct) script, and without even interacting in the game, I see the error again. Here it is:

screen shot 2015-10-10 at 10 25 35 pm

Any ideas now?

@manveti manveti self-assigned this Oct 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants