Question: Issues that aren’t really major issues but are still issues #723
Comments
|
As I don't feel up to working on the tool (too tired or something along those liens though I hope to a bit later on today[0]) I do have some OT things to bring up which I'll do in additional comments. [0] I do have a zoom meeting today and I'll be done working on the repo for the day prior to this, whatever I got done, whether anything beyond the two open pull requests or not. |
Tolkien booksI know I told you about the book that Christopher blessed before his tragic death that you got and started to read (I still haven't had a chance to ... :( ) but I have also brought up some others that I wonder if you've got, books that are delightful.
There are others I know about that are great but that's a nice list if you didn't know about them. I have a book with pull outs of the maps but I can't access it .. they or it (might be one for Hobbit too - don't recall) are behind other books as I have limited space :( (not the only kinds of books that are inaccessible). Enjoy! |
|
Here's a fun one I just wrote ... /* programmer's party simulator */
#include <stdio.h>
#include <unistd.h>
void drink() { drink(); }
void party()
{
/*
* get pissed as a fart and do something
* exciting, I'm sure... (where exciting
* means stupid)
*/
drink();
}
/* programmer's social function */
void code() { printf("Go away! I'm programming!\n"); sleep(1); code(); }
int main()
{
/* skip the party: just go home and write code! */
goto home;
party();
home: code();
}Not that coding is the same as programming as such ... |
|
So... I discovered an interesting problem with Check this: make test
...
If you are curious, you may examine the newly created compressed tarball
by running the following command:
/opt/local/libexec/gnubin/tar -Jtvf test_ioccc/test_work/entry.test-1.1689530054.txz
As you entered an IOCCC contest ID of 'test', the compressed tarball
that was just formed CANNOT be used as an IOCCC entry. Please
do NOT email the Judges your entry!
yes: standard output: Broken pipeIt only happens when running The question is do you want me to open an issue with this problem? Of course low priority right now probably but it's kind of annoying and I feel like it shouldn't be there. I'd guess you agree. UPDATE 0One way to fix it would be to add a |
|
.. and I see another problem with it - display - but probably insignificant given where it is: Notice where the URL is. I guess that that's just the way the script is and it's not a problem - since it ends up having to not prompt (exactly why we need the |
Yes, we agree.
Yes, please. |
It might as I think solve the problem in the script in which case there might not be a need for an issue being opened. I opened this directly so that I'll see the email - tomorrow. Too tired to do it today I'm afraid and I'm hoping to be leaving (laptop) for the day soon. ... of course it brings up a question of is there a problem with the script that should be isolated? It might or might not have a problem. Not sure. Is it worth trying to determine the cause? I think probably not unless the |
I am thinking it might be a good idea to make an issue out of this and make it so that it's assigned to me. I am sure this will solve the problem but the other things are higher priority, right? If so do you think I should open an issue so I remember to do it later ? |
Go ahead and open an new issue for this. That was it can be noted while other matters are prioritized. |
I will do that tomorrow. I am about to have brownies that were pulled out of the oven about ten minutes ago. I just needed to take it easy today. I hope that tomorrow is a more productive day. Have a great night! |
Fixed it instead. See commit c776f09. Going to try and rest now though my body is telling me that won't last for long .. but possibly won't work on the other issues for a bit if not a while later. I do hope to work on it a bit today though but we'll see if I'm up to it. Hope you're sleeping well! |
|
Here's a funny screenshot for you. I first read this years ago. But I only remembered it earlier this year and I got a screenshot then. I would have to find the article again but this is the best part.
|
Glad you got a laugh .. I knew you would. Whilst I'm still waking up and downloading (almost downloaded) the macOS update - 13.5? - here's the article for you: What I find hilarious is that it assumes that aliens have the same technology and use electricity and have same OSes and everything ... which is ridiculous and nonsense. Assuming there are aliens anyway: the real aliens are sadly ourselves. I don't believe in anything else: not until they're proven. And I hope they're not as humans destroy the unknown. Hope you're sleeping well! Two days in a row I slept in till almost 3 .. not enough for it to be good news but still somewhat encouraging. |
|
We were called away on a calc mission to help folks using FPGAs and DSPs to use a special "FNV-style" hash for the unusual 44-bit size of that hardware. Being probably one of the few people on the planet who fully understands the number theory behind FNV, they need our support. So was had to create: And make a special release of: We hope to return to creating manifest lists for IOCCC and to updating this repo .. after we undergo and recover from a 3-hour dental procedure tomorrow. |
No problem ... best wishes. |
|
Here's a funny and sad story. Someone apparently was bragging - on Facebook of course! - about their brilliance because they have an IQ of 84. She thought it is out of 100. Of course IQ testing is problematic and misses some critical things but this is still perfect. |
|
ChatGPT joke (copy pasted) about Bill Gates. It's a variation of an old one that I am sure you have seen before. -- When Bill Gates arrived at the pearly gates, St. Peter said, "Bill, you've done so much for humanity with Microsoft. I'll give you a choice: you can either go to heaven or take a quick tour of hell first. Then, you can make your decision." Bill thought for a moment and said, "Let me see hell first." As he descended into hell, he saw all the suffering and torment. The devil even offered him the latest versions of Windows with constant crashes and bugs. After a quick glimpse, Bill said, "Okay, I've seen enough. Let's go to heaven." When Bill reached heaven, he was greeted by angels and a beautiful, serene environment. St. Peter said, "So, what's your decision, Bill?" Bill smiled and replied, "As much as I appreciate what I've done with Microsoft, heaven seems like the more stable option!" -- I will be getting ready for sleep in about an hour from now but I do hope that I will be able to do more on the readme tomorrow morning. Best wishes for tomorrow! |
|
I made an enhancement to The idea is that since one might not know the right country name (exact) to find the country code it allows for substrings. Then since it would normally find the first and then print that one and not another it allows for Now when using Instead at the end if nothing is found it exits 1 but without an error. I think this is a useful enhancement to the tool but I want your views on it before I proceed. I'm going to do other things now. I'll do more tomorrow. |
I've made some slight improvements of this ... will look at doing a commit later. Maybe. I've been awake since far too early and I have a feeling today is going to be a long and difficult day. I hope to address the comments in the other issue but I'm not sure how much I'll manage. I'm going to try and rest again but I do have a bad feeling about today. So in case I am not very responsive today this is why and I'm sorry in advance! Hope you're sleeping well though. |
|
With commit 6f5cdb3 the location tool has been improved a fair bit! At first it modified the lookup functions but I decided for the cleaner approach of making re-entrant versions. The tool is now more useful for general use. The CHANGES.md and the git log and man page (with some examples added) should give you enough information on the new features and how it all works but otherwise there's always RTFS :-) :-) I do think this should be added to the general how to submit an entry faq but that can come later .. or maybe sometime soon. I think it would be wise if I added to a And I see you saw my reply earlier: sorry you were awake at the time. I'll be going afk soon I think but after that I'm not sure if I'll end up doing anything else here. Oh I think I can try and reply to the comment about json levels but it might not be anything beyond that. Anyway the location tool is now more useful and I think you'll be happy with how it was implemented. |
|
Just a fun link for you. I unfortunately am not feeling very well today so I am not sure when I will get to the other thread but I hope to do that later today. Anyway. Lava and Smoke Blanket Fagradalsfjall: https://earthobservatory.nasa.gov/images/151653/lava-and-smoke-blanket-fagradalsfjall |
|
See commit 06ce951 for an update relating to a cleanup of .gitignore files. In particular: Added Entries that belong to We removed many of the "generic exclusion lines" from the top level We did leave behind 5 "generic exclusion lines" in the above It can be argued that even these files do not belong in a GitHub We made all of the non-generic exclusion lines "/-path" based. A number old entries in the |
|
It is a good idea to sometimes check the result of: make clobber
git status --ignoredas well as: make release
git status --ignored |
|
With commit 59eebbc dbg version 3.0 2023-08-05 is ready for final review and testing. With commit 32b2a74 dyn_test version 1.10 2023-08-05 ready for final review and testing. With commit f602c74 updates per new parse_verbosity() interface from dbg.a were made. As changing the "dbg" interface is something that should not be done lightly, we plan to hold off on pushing both "dbg version 3.0 2023-08-05" and "dyn_test version 1.10 2023-08-05" until after a complete review of the changes have been made. The same goes for the "dyn_alloc" interface. If you, @xexyl, find any nits with the above commits, please change We plan to reject the existing pull requests in those repos in favor of the above commits as well as any additional correction commits that may be needed under the |
Maybe they need something more powerful 💉? :-) Okay that's bad but not as bad as I was going to do if they had an emoji that might work. Not that I'd suggest it or even say it in person but ... |
NOTICE OF UNAVAILABILITYStarting today, 2024 Oct 29, and increasing over the next several days, we will be less and less active online including in this GitHub repository. This is because we will in a few days, we will be working in an area of the world where there is little to no reliable Internet services and/or the Internet services will be too slow and power too limited to do much work. There may be rare occasions where we do have access to online services, but such access will be limited to only essential activities. We might be able to even push through an update, but please don't count on it. And we certainly won't have the opportunity to read messages and respond while we are "remote". So if you write something and we don't respond, you will hopefully remember this notice and understand. We expect to start to return to normal Internet services by mid November and the goal of returning to full Internet service by 2024 Nov 21. Best wishes 👋🏻. |
Of course I understand! And best wishes to you too and BCNU! Safe travels and have fun too! Also I hope that the meeting with Leo goes really well! Thanks for the update. Next few days for me are hectic but after that it should be better. Anyway best wishes to you too! |
FYI about jstrdecode/jstrencodeI just pushed out the change of the swap of names as the terms were wrong, it seems. The new version of the tools is If however you do want it done, first of all please advise me, and second of all this means that the scripts that rely on it, at the website, will have to be updated to use the correct tool and version, which I'm happy to do for you. QUESTIONWhat do you prefer? |
UPDATE 0A bug was fixed in the json debug function for strings. This means that the code, as it stands in mkiocccentry, has a bug that segfaults, all because I forgot to update the format (remove a |
|
I went ahead and did the pull request. Not doing so for the temp-test-ioccc though as other changes are in the works (related to Leo's information) and since this one is big I figure you might want to take a look at it when you're back, instead. Anyway at least the bug is fixed now. |
|
We guess the comments about the testing we suggested need to be done as a sanity check. The fixing of the segfault stuff was a critical enough issue to warrant and emergency 🚨 update. |
Agree. That bug was sneaky and at the time I fixed it I could barely see. Fortunately I was able to see enough - barely but I could. I'll do the more thorough testing tomorrow. Hope travels are going safe and well! |
|
BTW: so far so good with readme2index stage of the website with the jparse tools installed from THIS repo. I expect everything to be fine as it's a copy of the jparse repo but just to be sure, as you say (and I agree wholeheartedly), I am doing it this way too. The tools being installed from the jparse repo works fine. |
QUESTIONI have improved the bug_report.sh and the hostchk.sh scripts in a way that should help parse the output a bit better. Do you wish me to commit them? I am trying to limit things as much as possible though with the jparse updates that might not seem like the case. Anyway going to do other things now. If the website fix goes as planned I will do a pull request over there but otherwise not. Can do more tomorrow. |
Yes |
Done. |
|
I just noticed a mistake in txzchk that I'll fix later on .. not sure if today or tomorrow but I'll make a change in the file to remember to do it. It is missing a standard option we have in every other tool. The one to be quiet. Starting the change now but not committing. |
|
Okay it's done .. just have to do a commit .. later on. Not now. |
|
With pr #29 and release 1.6.13 2024-11-16 of the mkiocccentry repo and commit c47f3abbe47cc63c33a5f4b99ac6ca35cb773dfe of the temp-test-ioccc repo we have now entered a soft code freeze for the mkiocccentry repo. REQUESTPlease review the recent changed files for typos and other editorial issues. Should all be well, or if a PR in this repo is needed, we will issue a release 2.0 of this repo and enter a HARD CODE FREEZE for this repo - hopefully to last until the end of IOCCC28. UPDATE 0Added, @xexyl, a request above. |
Release version 2.0 2024-11-17This repo is now under a CODE FREEZE. Only super-critical bugs that have a significant impact the running |
Sounds great! I meant to add to the dynamic array facility a quiet option but oh well. I can still do it desired I guess but very few would run the test code anyway. |
|
Somehow I missed or forgot to do the typo checks: sorry! But I had a question ... Given the problem with what happened with What do you think? |
The BTW: We recommend use of When we build an RPM release for calc, our release procedures include a build that includes an empty You don't release RPMs (nor do you need to). Nevertheless it might be better if if [[ -f save.Makefile.local ]]; then
echo "ERROR: save.Makefile.local exists, aborting" 1>&2
exit 123
fi
if [[ -f Makefile.local ]]; then
mv -v -f -p Makefile.local save.Makefile.local
status="$?"
if [[ $status -ne 0 ]]; then
echo "ERROR: mv -v -f -p Makefile.local save.Makefile.local failed, error: $status" 1>&2
exit 124
fi
fi
... the rest of the release staff including test ...
if [[ ! -f save.Makefile.local ]]; then
echo "ERROR: save.Makefile.local is missing" 1>&2
exit 125
fi
mv -v -f -p save.Makefile.local Makefile.local
status="$?"
if [[ $status -ne 0 ]]; then
echo "ERROR: mv -v -f -p save.Makefile.local failed Makefile.local, error: $status" 1>&2
exit 126
fiAnd obviously |
Hmm I guess that's something to consider. The concern is what happened in jparse. I do agree that one needs to be careful. It was, if you don't recall, just doing Are you saying that it might be useful to update removing it to use something like this instead? But the question is when should it be used? That's the key question to consider. |
|
This mkiocccentry repo is in a CODE FREEZE. We plan to keep the CODE FREEZE, if at all possible, until after IOCCC28 is released and until after the IOCCC judges go on vacation. As such, we would consider breaking a CODE FREEZE for something that would is super-critilcal that would significantly impact the running of IOCCC28. And even then we would keep to make the smallest change needed to address the problem. UPDATE 0We created a |
|
Yes I understand and I like the idea. Must go. Have a great day and good luck! |
lcn2
added
the
post-IOCCC28
|
Good idea for the label. I'll look back at other things tomorrow or the next day. Good luck with the todos! |
|
Working on this .. for jparse .. then will do for mkiocccentry I think. Not sure if I can do it today or not. Obviously it'd not be committed here today but it would mean it could be done easily and quickly at the time. I will actually hold off doing it here today but I do want to do it over there today .. though even that I might not finish. Have a lot on my mind. |
|
Actually I can't do it even there today, not completely. It's not as simple as you have it since the top level Makefile invokes rules in other Makefiles that also have to be moved. This will require focus and time that I unfortunately do not have time or patience for today. I hope tomorrow will be better. It's just the last two days have been really long and hard. Today should be better but I need to take it easier. Thanks for the idea. I believe when reworking it it might end up better. I ended up putting a note in the README.md under compiling about this. I'm pondering whether it might be an idea to add a warning in the Makefiles if such a file exists. I can see it both ways. But I'm not going to worry about that today as I'm not going to work on it today. |
As we are in a code freeze for months, we suggest you not bother with anything that is post-IOCCC28 in this repo. |
Well ... we'll see how I feel. Not worried about it much but if I have the time, energy and have nothing else to do I might. Thanks though. |
Due to the fact that we have another issue that has had a number of OT comments I think it might be good to have a new mostly OT thread here rather than clutter the one in the other repo more or the issue for jprint.
I had the thought of suggesting you reopen the other one but there's a comment there I don't want to get lost that I hope you can finish replying to (you were doing it in parts) when things are less busy here. I also wanted to see if anything in particular occurs if one uses the same name (I rather doubt it will but it popped into my head anyway).
Feel free to assign this to me even though it's not technically an issue that has to be resolved.
The text was updated successfully, but these errors were encountered: