You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
When Fury bootstraps, it builds a fat JAR, using (pure Java) Apache Commons IO to ZIP everything up in parallel. (It's quite fast.) It's been working great for a while. But it doesn't work when I invoke it over SSH from the terminal within VS Code. Any ideas?
Strangely "it doesn't work" seems to mean that it simply doesn't generate the JAR file, and exits quickly. But no exception is thrown, and Fury's exit code is 0. VS Code manipulates the environment somewhat, but I've no idea what environment variables would make any difference...
Needless to say, it's been incredibly irritating trying to debug a bug which prevents me from building alternative versions to experiment with. Unfortunately it was only when I got back to my non-SSH session that I realized it was a "bug" with the *environment*...
Yeah, I took a look at that actually, and the diff was about 20 lines, but there was nothing obvious. I suppose I could try setting the env to the non-SSH version and seeing if that works, though... and then bisect.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
