EVE Technology Lab

Are there ways to get Yapeal to violate the cachedUntil time? Yes, simple delete the cachedUntil time from utilCachedUntil table and Yapeal will at least try to refresh the data from the cache. If you also clear the XML from the file and/or database cache it will even try to get it from the API server again and depending on the API you either get an API error with a new cachedUntil time that will be even farther into the future than if you had left it alone or the same data you already had once again with a new cachedUntil time that will also be farther into the future than if you'd left it alone.

Does it make sense to do either of these things? Not really.

Now if you are just wanting to have Yapeal grab the data for say a new char when they are signing up for an account you can add the key info to Yapeal and directly call it and it will get the data but it will do it along with trying to get anything else with an expired cachedUntil time. It shouldn't even cause any problems with your regular crontab job as Yapeal does use a very simple form of API locking so multiple copies don't try to both work on the same thing at the same time but since the order they will try to get the APIs is random there's no way to predict which of them actually ends up doing the work. I am looking at adding the ability in the future to be able to call APIs directly outside of the normal crontab way Yapeal does things but there are some other things that need to change before that is possible.

The best way to make sure everything is as up to date as possible is to add the accounts to it and run the crontab every minute. I've had several developer trying to run it less frequently and than complain it's overloading their systems. By design Yapeal tries to do as much work as it can every time it runs so the less often it is ran the more it has to do each time but if you let it work as often as possible it actually works to spread out globs of API calls by delaying some of them a couple minutes so only a few cachedUntil times expire each minute. None of them will be delayed more than 5 minutes because of hard limiting plus its heavily weighted to do them on time so the upper limit is rarely seen.

Hopefully that answered you question(s) and let's you understand how things work a little better.

Wiki is outdated. What use to be in common_backend.php is now either moved to the classes the code should have been in or was moved to yapeal.php. Read through the CHANGELOG to see why etc. Lines 78, 79 are the ones for the autoloader in Yapeal.php but you'll want to look at some of the code before them to setup some of the environment you'll need.

Yeah it has to read the config file or stuff doesn't work

@Norian Lonark - You could do what you are talking about but you would have to 'fix' the tables every time you updated Yapeal and it's database. The normal way to do what you want would be to add another table with the primary key from Yapeal's table as foreign key to your table with the other columns you need so they are linked. So for IndustryJobs you would have ownerID and jobID as the foreign key or even as you're primary key depending on what else you are adding then use a simple join in your queries.

New version 11.308.0915 Since I don't have enough data to test some changes I'm trying with walking in the Wallet* API I'm pushing it out for anyone else to try. If you've been having problems with walking working give it a try and let me know if it's better.

I understand it seems like a bit more work now but it has actually made it more useful because if you don't need some of the parts now you just don't call the function/methods or if you want to override something there's something with a name on it that helps you find what you need. In time it will be simplified once again but Yapeal needed to go through a transition here to get from the procedural code that was used a lot in this area to something more OOP. It has also let me reuse a lot of the same code for the scripts in install/ used to config Yapeal during installation too. Just think you only have to put your settings into config/yapeal.ini once and then can do all the setup and day to day run of it without reentering any of it again

I'm absolutely ecstatic about this. It'll make emails from cron useful to me again! :) Have you seen any issues when using STDOUT/STDERR for logging? I would expect not, but want to be completely clear.

Thanks for checking log4php out. I believe this will be a very valuable change that will make your and your user's lives easier in the long term.

Thanks!

Yeah when I put out the changes for logging it reverted the changes for the Wallets I'll have that fixed tonight. I've got to remember to pull, merge, push not the other way around

Ok after a few more tries I got the other stuff logger stuff finish for now anyway and got the Wallet stuff back in as well.

version 11.311.2210

What it should be doing is get one group with walking forward (no fromID) then use the oldest record from that one to walk back as far as it can which should be a month if CCP hasn't got that bugged.

Limit is from CCP. They only allow the last month. Only way to have complete history since you started playing would be you started collecting it since then