| whaack: | diana_coman: EOD report: I finished the review from last week + published the plan for next week, completed a rough draft of An Outpost of Progress article, and did a 1 hour session reading The Odyssey. I also did a short review of my backup scripts and found that they are not working - my most recent blog article is not backed up. The issue is that my ssh key is being rejected when rsync tries to connect to my account solely made | [01:02] |
| whaack: | for storing backups of the blog. I believe the first time crontab fired the script that syncs from digitalocean it worked and then the script failed every subsequent time. | [01:02] |
| diana_coman: | whaack: you know, you should always run the crontab manually too as a basic test before letting it be; pfft. | [04:08] |
| diana_coman: | anyway, fix it, obviously. | [04:08] |
| whaack: | diana_coman: Well yes I ran the scripts manually before I put them on a crontab timer. I believe I also scheduled the crontab to fire a few minutes after the point in time I set them up, to make sure the crontab itself was running. | [10:03] |
| whaack: | diana_coman: In any case I will look into it the problem and fix it right now. | [10:03] |
| diana_coman: | whaack: so then what changed and moreover did it actually do what was expected that crontab-test run or didn't you check the result or what happened there? | [10:03] |
| diana_coman: | ok. | [10:03] |
| whaack: | diana_coman: Either I threw a pebble and did not thoroughly verify that the script worked, which truthfully is the most likely case, or after I set it up the first day I tweaked some setting on digitalocean / digitalocean tweaked some setting for me. | [10:05] |
| diana_coman: | myeah, did sound like a pebble really. | [10:06] |
| whaack: | diana_coman: The problem is that crontab runs in a separate environment that by default is not set to used the ssh key my terminal has access to. So my script works manually but not when it is run via crontab. Since there were no changes to the files on my blog since i tested it manually, I didn't notice that rsync wasn't working. If i had checked my terminal mail and looked at the crontabs output, or checked the timestamps of file | [10:17] |
| whaack: | s, I would have caught this bug. | [10:17] |
| diana_coman: | aha. | [10:17] |
| diana_coman: | eh, whaack, being beaten *by someone who knows what they are doing*; otherwise it's just broken bones, not growth, lolz. | [10:51] |
| whaack: | diana_coman: aha | [10:51] |
| diana_coman: | dorion_road: "a bit" there might be the understatement of the day; but if that was indeed apres apres-ski, I'm rather positively impressed with the result anyway. | [10:52] |
| whaack: | diana_coman: Probably not something too important to address but so you're aware the graph of insanity in your article http://ossasepia.com/2017/02/18/the-open-sores-of-monkey-code/ goes all over the sidebar and can't be clicked / doesn't have a readable resolution. | [11:15] |
| diana_coman: | whaack: myeah, I noticed there are now quite a few of the old images that got messed up by the switch to the mp-wp theme, ugh; it's somewhere down at the bottom of the list but thanks anyway. | [11:17] |
| dorion_road: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-02-Dec-2019#1011762 << right, I understand there's many bytes of settling yet to do. with that being said, I'll take satisfaction in generating positively impressive results. | [11:31] |
| ossabot: | Logged on 2019-12-02 10:52:01 diana_coman: dorion_road: "a bit" there might be the understatement of the day; but if that was indeed apres apres-ski, I'm rather positively impressed with the result anyway. | [11:31] |
| diana_coman: | jfw: why not just sign the archive anyway? | [15:16] |
| diana_coman: | for gales initial release I mean. | [15:16] |
| dorion_road: | jfw mind answering spyked's question about your build by hand X11 recipe. does it produce a statically linked X11 ? or dynamic linked musl ? | [15:24] |
| dorion_road: | (when you have the chance.) | [15:24] |
| jfw: | diana_coman: hm, no strong reason I suppose. Large things are slow to get to my signing machine, but this isn't quite in that territory, I'm not typing base64 by hand or anything. | [15:53] |
| jfw: | dorion_road: will have a look, but in a word, that was dynamic, on gentoo | [15:55] |
| diana_coman: | jfw: fwiw I enjoyed reading the gales files; esp after a CS dig, it makes for a refreshing crisp & don't-mess-my-shit read. | [15:58] |
| jfw: | glad to hear it | [15:59] |
| diana_coman: | I certainly want to get to give it a try but it might be a while until I dig up some proper chunk of time for it. | [15:59] |
| jfw: | sure, and perhaps some further wrinkles will be ironed by then | [16:01] |
| diana_coman: | that would be great. | [16:01] |
| jfw: | The bootstrap process takes me (including compile times) around an hour, with a fair amount of the copy-pasting I caution against ;) | [16:02] |
| jfw: | I'm sure it would be scriptable with a bit more thinking through. | [16:04] |
| diana_coman: | heh; not bad to know it though; for starters it will surely take me longer because of poking-it-everywhere and anyway, it's your one hour after the few years on it. | [16:07] |
| jfw: | right. some of those gcc configure options are a devil, miss one and something breaks 10 steps down the line | [16:08] |
| diana_coman: | quite. | [16:14] |
| diana_coman: | whaack: ahaha, that monitor & ups will be coming forever "tomorrow" ? | [16:20] |
| whaack: | diana_coman: heh yes. i called cococo to check on the order, and they said the delivery company they were using wanted to charge an extra 00 or so to take the road to my exact location, so they told the delivery company to leave the packages in a nearby city with one of their partners. The partner will deliver it either 'Tuesday or Wednesday' so it'll probably get here about Friday, really. | [16:27] |
| whaack: | diana_coman: it was amazing how the guy was well informed about my order and knew the whole change of plans that had happened but never thought he should ping me and let me know. | [16:28] |
| BingoBoingo: | whaack: Welcome to Latin America | [16:34] |
| jfw: | diana_coman: thinking about the what do you mean here now, might be easier discussed here. How to put it... there was a kind of shift in framing of my thought process | [16:43] |
| jfw: | The tasks themselves consist mostly of thinking, and the planning of the tasks likewise ... | [16:44] |
| diana_coman: | jfw: do you mean the coding tasks? | [16:45] |
| jfw: | right. so, how was I to come up with a solid plan for what to code, before thinking further about what the code itself needs | [16:45] |
| jfw: | the two need to feed back into each other as I see it | [16:46] |
| jfw: | (spec and implementation) | [16:46] |
| diana_coman: | sure, that's fine and just like with any other piece of writing: at times you need to do more thinking before being able to write | [16:46] |
| diana_coman: | there's no interdiction on thinking about code, quite on the contrary, the writing of spec is after all a form of "thinking about code" too | [16:47] |
| diana_coman: | the potentially iffy part is at "what the code itself needs" | [16:47] |
| jfw: | yeah should be more like, what the code needs to do to solve the problem, what inputs it therefore needs and so on | [16:48] |
| diana_coman: | because code is not exactly having much to say about needs of its own; but to the extent that you mean "what is still needed for this to be useful", sure. | [16:48] |
| diana_coman: | there, precisely :) | [16:49] |
| jfw: | diana_coman: and re "this does read more like a report than a review" - do you recall my past reviews being better in this regard - being more for myself? I'll go back over them and see if I can spot the difference. | [17:11] |
| diana_coman: | jfw: yes, they were certainly more actively reviewing, you know? it might be that you simply left this one so late + rushed it so much that there was no time & inclination to review anything but that's the effect already, not the root cause. | [17:15] |
| diana_coman: | whether you did them more for yourself or not, only you can tell really; my suggestion here was simply to point out to you that ultimately they are meant to be of most use to you really. | [17:16] |
| diana_coman: | and yeah, I quite think you are not very fond of reporting otherwise :P | [17:17] |
| diana_coman: | jfw: or are you? | [17:17] |
| jfw: | hm. I'm tending to think it's more the reviewing I'm not fond of and so got displaced by reporting when I had to grab at something | [17:18] |
| diana_coman: | well, it is easier for sure so that part I can see, yes. | [17:18] |
| jfw: | so yeah, will do that rereading and bear in mind that they're for me. | [17:19] |
| jfw: | thx | [17:19] |
| diana_coman: | cool, np. | [17:20] |
| diana_coman: | btw jfw dorion_road (when you get back to your key, obv) you should at least rate one another really. | [17:32] |
| jfw: | yeah I need to get all my ratings in really | [17:32] |
| dorion_road: | BingoBoingo are you around to grant me an !!up in #t ? it'd be appreciated. | [18:32] |
| BingoBoingo: | Sorry, can in a bit late on it. | [18:34] |
| BingoBoingo: | *came | [18:34] |
| dorion_road: | ty for the try BingoBoingo | [18:55] |
| dorion_road: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-02-Dec-2019#1011772 << thanks for the follow up there. | [18:55] |
| ossabot: | Logged on 2019-12-02 15:55:24 jfw: dorion_road: will have a look, but in a word, that was dynamic, on gentoo | [18:55] |
Comments feed: RSS 2.0