Search results

Try 10599.

I don't get it. @_@ I adventured in the gallery and kept getting Tetanus, but KoLmafia used soft green echo eyedrop antidotes to remove it because it knew I didn't have Disco Power Nap. Just to make sure I haven't completely lost it, I've added more debugging messages so that KoLmafia reports...

Weird, the exact opposite is true for me; namely if I leave it checked, things work, but if I uncheck it, things fail. I'll make the HTTPS switchover opt-in until we figure out what went wrong.

Huh, did you uncheck the "improve handling of semi random lag spikes" preference?

Isn't that only in combat? And I don't see any code in KoLmafia that would make it reject trying to cast a skill out of combat just because you have Cunctatitis (assuming I'm looking in the right places).

That's weird, it should only consider Disco Power Nap as a way to remove cunctatitis if you actually have the skill, but I don't have a character with low enough muscle to test getting cunctatitis to see what really happens. Do you have Disco Power Nap as an available skill but are unable to...

You can safely rename it, yes. The path in your gCLI output is /KoLmafia/charpane.php, which hints at something with a bad base href. Do you use the gCLI integrated into the relay browser?

Ok, adding a null pointer check at the line number in the stack trace ... but it only happens if KoLmafia got a 200 response, but somehow the response didn't actually come back. So it's more suppressing the symptom than addressing the cause. =\

Can't reproduce? [19436] Haunted Ballroom Encounter: Curtains You gain 165 Smarm > get choiceAdventure90 2

I'm attempting to get Option-Q to kill the process on OSX 10.7 and also run the user's logout script, and because of all the complications on how it needs to happen (which I have not yet pinned down), it seems to be introducing other problems. :p Edit: Found the current problem: I removed code...

It's possible to get ⌘Q to at least show the login window, but because of how ⌘Q is implemented by Apple, KoLmafia won't be able to update the display while the logout script executes. That being said, because we're purposefully blocking the event dispatch thread to prevent the shutdown from...

Okay, going to give up on doing any window hiding/disposing in a shutdown thread. Try 10557?

Okay, I've switched to hiding the windows on shutdown instead of trying to destroy them.

The next time KoLmafia gets stuck on exit: jps -l Use that to figure out what the process id is for KoLmafia. jstack {pid} Use that to get a stack trace dumped to the console. I get the feeling there's some kind of weird locking going on still in the event dispatch thread, but it only occurs...

I'm not able to reproduce the process not going away, but I did find out what was creating the login frame, which was a second logout attempt running in parallel with the existing one, which was triggered just as KoLmafia closed the last window. I've attempted to fix this in 10544. Does this...

Well, exiting directly shouldn't load a login frame anymore because of how exiting happens now. (Edit: Hm, seems like it does, I'll have to find out why that is.) However, I'll see if I can somehow reproduce that getting stuck error. Do you have a logout script or anything?

Try 10543.

Doing what?

To verify, when you say it closes instantly, do you mean a UI issue where all the windows are gone but your logout script still runs, or do you that mean that when you go back and check your session logs you find that your logout script hasn't run at all?

Put logout logic in a shutdown hook. How's that work?