maiyannah on community.highlandarrow.com

This remote profile is registered on another site; see maiyannah's original profile page on community.highlandarrow.com.

1. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:30:15 EST maiyannah

   Remote profile options...
   2016-11-17 01:29:02 LOG_ERR: Opportunistic queue manager is out of work (no more items). (500)
   
   This is not an error, so I should put that in LOG_DEBUG or *maybe* LOG_INFO
2. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:26:05 EST maiyannah

   Remote profile options...
   Okay got the NoUserResultException thing in there easy enough and that seems to work so should be easy enough to get the rest in there.
3. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:20:22 EST maiyannah

   Remote profile options...
   Okay, added a $severity variable to the constructor of the ServerException class, if it is LOG_DEBUG it uses common_debug to write the line, otherwise it uses common_log, and got NoResultException in there using that to pass those things into LOG_DEBUG, not LOG_ERR.  You can use the logfilter plugin to parse out LOG_DEBUG severity - which is what I do unless something's acting up.
4. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:03:10 EST maiyannah

   Remote profile options...
   Well, next step then is getting NoResultException in with the ServerException code and coding it in such a way as we cut down on the spam caused by that.  I will probably make NoResultException at LOG_DEBUG severity, not LOG_ERR.
5. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:01:35 EST maiyannah

   Remote profile options...
   Looks like NoResultException derives from the ServerException and the reason that they don't log centrally from ServerException is that it gets spammy with NoResultException in there.
   
   This seems like something to fix in the descendant class rather than making all other errors opaque as fuck, though, if you ask me!
6. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:55:57 EST maiyannah

   Remote profile options...
   Once everything was pulled together, this was exceeedingly easy to get in there.
   
   Of course, the next step past that will be making sure everything has descriptive error messages, but one thing at a time.
   
   There's still the NoResult exception and Client exceptions to unify.
7. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:54:47 EST maiyannah

   Remote profile options...
   One simple common_log line in the ServerException class later, and all exceptions should now be logged at the LOG_ERR severity in syslog, or to the separate postActiv log file if you have one specified.
8. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:50:05 EST maiyannah

   Remote profile options...
   Should be pushed to both now - let me know if you have issues with either wrt this latest change.
9. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:47:01 EST maiyannah

   Remote profile options...
   Next thing to do is I'll probably make them dump into LOG_ERR verbosely, they are exceptions after all.
10. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:45:42 EST maiyannah

    Remote profile options...
    This will be posted to both Nightly and Master soon since it's working in a production environment just fine.
11. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:45:02 EST maiyannah

    Remote profile options...
    So what I've done for now wrt !postActiv exception handling improvement, is just put everything together, in a central file for server exception, /classes/ServerException.php This file includes the descendant classes for exceptions that fall under that type. I have also assigned what I believe to be the sanest HTTP status code as error codes for each, but they may …
12. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:41:42 EST maiyannah

    Remote profile options...
    Dear sysadmin of the lamatriz.org instance (I don't know who is the head poomba over there):
    Your instance has a certificate error which causes federation to fail.  You uh, may want to fix that, probably.
13. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:40:05 EST maiyannah

    Remote profile options...
    Doesn't look like anything's exploding :D
14. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:37:46 EST maiyannah

    Remote profile options...
    There we go.
    Is anything exploding?
15. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:35:32 EST maiyannah

    Remote profile options...
    VERY brief "downtime" as the new files copy over, please hold.
16. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:34:42 EST maiyannah

    Remote profile options...
    Looks good, I'm going to put it live here and see if it explodes in an actual production environment, and if not, we're good to go, for the ServerException class and children anyways.
17. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:28:36 EST maiyannah

    Remote profile options...
    Iterating through tests that intentionally raise the affected errors now just to see everything's working.
18. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:23:40 EST maiyannah

    Remote profile options...

    • Purple Hippo
    @purplehippo They want to monopolize everything, and they need Linux to go away to do it.
19. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:12:29 EST maiyannah

    Remote profile options...
    In case you needed evidence the Linux Foundation is cancer.
    https://community.highlandarrow.com/notice/412132
20. maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 19:11:43 EST maiyannah

    Remote profile options...
    Going to do some tests to make sure this doesn't break anything before I commit it to the repo.

• After
• Before