Search results

Delay is probably the wrong word to use, what happens is that the relay request takes 15-20ms longer. I measured using a proxy on my local machine, hopefully this ASCII diagram makes sense. 0ms 300ms...

Yes, it's entirely possible. I have two repositories, one which I tinker on and one which is just exactly how the KoLmafia codebase is and I reserve that for the JET builds. If there's some sort of adverse change being made in the KoLmafia codebase, it's going to affect the JET builds too...

Not really, but I appreciate you taking time to explain it. This is the part that doesn't make sense. entry doesn't reference the request object, it references the request.responseText object, which is just a String and contains no reference back to request. As soon as request goes out of...

Okay, after thinking things through I'm still confused. I don't understand how the request object doesn't remain reachable until getEntries() returns, at which point the request object goes out of scope and becomes eligible for garbage collection.

You are a hawk, I deleted my post after I realized there were some mistakes in it. I'm still not quite sure but I'm mulling over the changes. Did you notice a reduction in memory footprint after making the changes?

Two things to add because people seem to be getting kinda hung up on what I said. The MTU thing is pretty negligible, I was merely noting it. It's definitely causing packet fragmentation having the MTU at 1500, but localhost packets are being transferred so fast it's really not even worth...

Noted here but I figured I would post a bug report in case it gets buried. The "Connection" header is being set to "close" and then a 2nd header is trying to set it to "keep-alive".

You shouldn't think of KoLmafia as processing things "on the wire". Basically it goes: Browser -> KoLmafia KoLmafia -> KoL Server KoL Server -> KoLmafia KoLmafia -> Browser In other words, the communication between KoLmafia and browser can benefit from a higher MTU because the communication is...

Even if there weren't, there should be no more than a 1mb of text on any given day.

Happy to report I'm not getting the weird login issue from yesterday. I did some analysis re: localhost speeds. keep-alive is working for it, I think it has always been the case. I was able to see multiple GET requests reusing the same TCP connection, so that's good. I did notice that the...

I haven't noticed that in the doc before, interested me enough to give it a try. I tried it myself, this may be a complete coincidence but my session totally died when fetching the contents of the closet during login (I can't explain why, it doesn't really make sense). Perhaps you have not...

I have seen this too. KoL's servers do handle persistent connections, but I believe GenericRequest would need some architectural changes before changing this setting would have any benefit.

Turn off your "verbosely log communication between KoLmafia and browser" option if you don't want it log HTML to the debug log. As to why you're getting debug logs without an exception.. Maybe you have debugging turned on? Try "debug off" in the gCLI.

I just need to click a button. I tried scheduling it but it didn't work (been meaning to look into it). Also it doesn't warn me if the upload fails, but yeah.. For the most part it works but I should probably get to something more automated, like maybe every 4 hours or something. I'll probably...

It's usually within 1-2 revisions of the JAR build and can occasionally be ahead (for an hour or so). I've been away and having internet troubles, so I think I missed a couple days. It's up to date now.

It's more likely to be one of these: public int responseCode; public String responseText; public HttpURLConnection formConnection; public String redirectLocation; public String redirectMethod; Edit: Here's a debug log from when I managed to have a RequestThread execute out of the order...

Am I going to be derided for suggesting that GenericRequest isn't thread safe?

I like the frameless UI, but I am guessing it does other things (I think I see some choice adventure handling stuff). Is the main reason people use this because of the UI? It might be possible to strip it back and just get that from it...

Ugh, I just looked at it, what a mess! I can see why people would say it's broken beyond repair. Inserting the entire prototype.js library as a script block in each page :confused: A third-party solution for URLencode instead of using the native encodeURIComponent() function :( Not to mention...

Eh, thought I would put some effort in trying to figure out what was going on seeings as it seemed pretty crippling for those experiencing it. I could probably make it clearer in the future if I'm just spitballing, but it wouldn't have been the first time a latent synchronization error decided...