Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Maybe I'm missing it, but is there any way to make the button for this not be so huge? It really is far too big, and I haven't found an option to resize it. (I notice both it and Minipet got much bigger, both I think with the move to newer libraries -- when Coconut grew out of Mount, in other words.) I'll have to find some other solution if I can't set a different size, because these are about 2-3x too big right now.
If I look at the memory also used by LibGraph I use a LOT more memory using Recount in a raid than Assessment ever used. If anyone knows if I can just... ditch that lib and still have Recount work (no desire for the graphs), or if there's somewhere I haven't found that they can be turned off, that'd be great. If not, I'll probably just go without until Assessment gets updated.
I noticed that about load times, the XML would take a good 30s-2m to load in Sage. Not gonna look back, especially also since the SVN method of getting the top level of the entire trunk allows me to filter out all the /branches/ updates that would show up in the XML. :) I definitely was able to figure out what needed updating faster than I have in the past.
Yeah, I did a custom XML as well, but yeah it's unreadable with those occasional uber-mangled updates. (I usually use it in Sage for better readability, and it gets a parse error when the main stuff is messed up.)
I wonder if there's any way to make Fisheye a little more resistant to oddities with commits so that doesn't happen.
I really, really wish I could get TortoiseSVN to show me a changelog for several folders at once, but it doesn't seem to allow that. Also, I had so many issues with WAU months ago that I left and only looked back once. The one time, it screwed stuff up so things didn't work, and then I couldn't update straight from SVN anymore either without deleting and re-checking out. However, that's why I use the Fisheye log before updating, rather than just picking all my folders and doing an update on the off chance 2 dozen of them actually updated.
Anyone happen to know if it'll not be too long before a 2.4 compatible version is available? Not pushing, just curious. If it's going to be a while (i.e. a few weeks) I'll probably grab Recount at least to tide over. (I don't really need the extra whizbang Recount offers, so it's likely I'll switch back when it's ready. Curiosity killed the cat, but satisfaction brought him back & all that. Not having them would drive me a little nuts I think.)
Any clues as to what "broke" fisheye? I went to check my feed to see what'd updated and got an XML error, so I went and checked the site itself. It flat out doesn't display. There's something odd about the data it has; when it gives a list of branches, it gets down into the Ms (MobHealth or so) and then it's... completely broken. I looked at the source and it's definitely outputting constrained gibberish at that point. Anyone looking at that, or know anything about it?
0
0
0
0
0
0
0
I wonder if there's any way to make Fisheye a little more resistant to oddities with commits so that doesn't happen.
I really, really wish I could get TortoiseSVN to show me a changelog for several folders at once, but it doesn't seem to allow that. Also, I had so many issues with WAU months ago that I left and only looked back once. The one time, it screwed stuff up so things didn't work, and then I couldn't update straight from SVN anymore either without deleting and re-checking out. However, that's why I use the Fisheye log before updating, rather than just picking all my folders and doing an update on the off chance 2 dozen of them actually updated.
0
0
0