• Poltergeists are breaking

    From Khelair@DIGDIST/BATTLEST/FREEWAY to All on Mon May 25 13:09:00 2015
    I hope that you will forgive me a short moment of #venting; this is the second time that this has happened to me, and it's driving me completely batshit right now.

    As some of you may know, I've got (what is for me) a rather large project that I'm working on in #javaScript creating a #shell for my #BBS that is #emulating a much older interface. As I've gone through this project, I've finished off some features completely (in this case the message base accessing areas-- at least for all primary/alpha features), and gone on to work in some of the other areas.

    Crux of the problem: I finish working on one area, move to something that is completely isolated from it within the codebase, and come back later on to the message base or whatever, and find that it's somehow spontaneously broken. Now there is the possibility that I've forgotten some changes I made in the interim to the source file containing those tidbits, but I really don't think that this is the case. I stopped doing the things that cause those kinds of memory lapses for some time now. I know that the code I've touched in the interim doesn't mess with those routines at all, so what the hell gives?

    I have located the commits in the code that I made back 'in the day' when the feature set was all working. I don't know #git very well, honestly, so I suppose that this is just a really good time to work on learning the features that can help me diagnose where this problem went wrong, run a diff on the right files, and re-merge (if that's the right terminology in this case) the changes up to my current devel so that I don't have to go through and debug all of that crap again. Seriously, though, what the hell? Is there perhaps some feature that I don't know about in git's branching model, since I've started trying to use the flow process a little bit better, that is causing me to break these as a feature, not a bug, but one that I don't understand very well? Argh. The frustration and rage, it burns.

    ---
    Borg Burgers: We do it our way; your way is irrelevant.
    Synchronet Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net
  • From Nightfox@DIGDIST/BATTLEST/FREEWAY to Khelair on Mon Jun 8 20:17:00 2015
    Re: Poltergeists are breaking my code when I'm working on other chunx
    By: Khelair to All on Mon May 25 2015 13:09:56

    I hope that you will forgive me a short moment of #venting; this is the second time that this has happened to me, and it's driving me completely batshit right now.

    As some of you may know, I've got (what is for me) a rather large project that I'm working on in #javaScript creating a #shell for my #BBS that is #emulating a much older interface. As I've gone through this project, I've

    What's with the hashtags? I'm not sure that hashtags would be of much use in a BBS message network (and IMO, hastags are ugly - I wish social media sites would have implemented message tagging differently so that users don't have to embed symbols into their text that don't add meaning to the text).

    to the message base or whatever, and find that it's somehow spontaneously broken. Now there is the possibility that I've forgotten some changes I made in the interim to the source file containing those tidbits, but I really don't think that this is the case. I stopped doing the things that cause those kinds of memory lapses for some time now. I know that the code I've touched in the interim doesn't mess with those routines at all, so what the hell gives?

    I have located the commits in the code that I made back 'in the day' when the feature set was all working. I don't know #git very well, honestly, so I suppose that this is just a really good time to work on learning the features that can help me diagnose where this problem went wrong, run a diff on the right files, and re-merge (if that's the right terminology in this case) the changes up to my current devel so that I don't have to go through and debug all of that crap again. Seriously, though, what the hell? Is there perhaps some feature that I don't know about in git's branching model, since I've started trying to use the flow process a little bit better, that is causing me to break these as a feature, not a bug, but one that I don't understand very well? Argh. The frustration and rage, it burns.

    If you get it back to a working state, maybe try backing it up locally on your PC and see if that copy develops issues.

    I haven't used Github much, so unfortunately can't think of any other suggestions.

    Nightfox

    ---
    Synchronet Digital Distortion: digitaldistortionbbs.com