|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Zaepho
Phoenix Propulsion Labs RED Citizens
1
|
Posted - 2011.10.26 16:24:00 -
[1] - Quote
check yapeal_utilSections to make sure all the appropriate sections are enabled. |
Zaepho
Phoenix Propulsion Labs RED Citizens
2
|
Posted - 2011.10.28 15:01:00 -
[2] - Quote
Dragonaire Have you considered leveraging Log4PHP for all of the internal logging? this would allow people to configure logging to their specific level of verbosity and would allow you to have very verbose logs for troubleshooting, with only Warnings/Errors for production runs. Also it gives people the ability to log to STDOUT, a file, a DB, syslog, etc at their own choice simply by editing a single XML file.
I have the automated/scheduled part of my project using it and I am able to log trace level and above events to a big fat daily log file and only warnings/errors to STDOUT so that cron emails me when it needs attention and I can refer back to the low level logs events for deeper troubleshooting/verification of what's happening.
http://logging.apache.org/log4php/ |
Zaepho
Phoenix Propulsion Labs RED Citizens
2
|
Posted - 2011.11.02 03:48:00 -
[3] - Quote
Sable Blitzmann wrote:Question: I know that Yapeal is supposed to run periodically from a cronjob, but how would I go about updating 1 characters info via my application? For example, if the logged in user wishes to update his character's information to get the most up-to-date info, how can I go about doing that (updating a character or account on demand rather than on a schedule)?
Thanks!
The data is always as up to date as possible within the confines of the cache intervals. Yapeal will collect and store the data on it's schedule as often as possible. |
Zaepho
Phoenix Propulsion Labs RED Citizens
3
|
Posted - 2011.11.07 19:44:00 -
[4] - Quote
Dragonaire wrote:Hi all got some more changes for everyone to try out this time I've overhauled all of the error and exception handling code. We can thank (blame ) Zaepho for the idea. Back in post 64 he talking about using log4php and I decided to check it out and liked what I saw.
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!
|
Zaepho
Phoenix Propulsion Labs Shadow of xXDEATHXx
8
|
Posted - 2012.02.28 18:34:00 -
[5] - Quote
Dragonaire wrote:At some point the API server thought that key had the IndustryJobs API turned off so when Yapeal was told that it unset the key and/or corp's bit so you'll need to update them not the general ones used by all of Yapeal. Look at the utilRegisteredCorporation and utilRegisteredKey tables that are related to the key that stopped working as the bitmap in activeAPIMask doesn't have the IndustryJobs bit set.
Would it make sense to have a field for desired and effective bit masks? This should allow for the desired mask to cover everything you want and effective to be updated via errors and the APIKeyInfo api. Effective would be used by all of the current classes. APIKeyInfo when processed would attempt to update the effective to be as close to the Desired as possible based on what the key itself supports. |
Zaepho
Phoenix Propulsion Labs
15
|
Posted - 2013.06.27 03:34:00 -
[6] - Quote
Somerset Mahm wrote:Dragonaire is going to add me as a committer so I can at least try to help Yapeal limp along for now. Thank goodness!!
Just looked at my logs after a few days away and saw all the errors and got really really scared.
Thanks for helping all of us limp along until somebody with the time and desire to maintain the project can step up. |
Zaepho
Phoenix Propulsion Labs
15
|
Posted - 2013.06.27 14:37:00 -
[7] - Quote
Looks great! I'm still having some problems with the char/ContactList API but haven't validated it against the schema yet to figure out what it's choking on. I'll post again when I have more solid info. Otherwise, thanks for stepping up! |
Zaepho
Phoenix Propulsion Labs
15
|
Posted - 2013.06.27 15:04:00 -
[8] - Quote
Looks like its an issue with one of the columns in the contactList rowset. Specifically inWatchlist is not being returned although the xsd expects it to always be there. Not sure if these contacts are actually in this character's watchlist or not.
ContactListee6d99d70ac508ff224aee720db4ebfb356475d2.xml:6: element row: Schemas validity error : Element 'row': The attribute 'inWatchlist' is required but missing. ContactListee6d99d70ac508ff224aee720db4ebfb356475d2.xml:7: element row: Schemas validity error : Element 'row': The attribute 'inWatchlist' is required but missing. ContactListee6d99d70ac508ff224aee720db4ebfb356475d2.xml fails to validate
flipping the Use attribute to Optional for this field and adding a default value of 0 to the field in the DB seems to fix the issue. |
Zaepho
Phoenix Propulsion Labs
15
|
Posted - 2013.06.27 18:25:00 -
[9] - Quote
Somerset Mahm wrote:Nope, you're right. On at least one of my keys, no watchlist attribute shows up at all. API bug. I'm going to refrain from changing the Yapeal schemas just yet, because it is technically complying with the row headers that are sent.
I tweeted at PrismX to see if it's a known issue.
Is it essential that we get that attribute on every row? I was operating under the assumption that accepting the missing attribute and using a sane default (0) would be the desirable action.
Unless of course it's not being returned on any contacts.. then that would definitely be a bug.
Looking at my cache (granted not a huge sample but i KNOW it should have some instances of contacts on the watchlist) there are no instances of inWatchlist in any of the returns. So it looks like a bug in the API code. |
|
|
|