Open xexyl opened 1 month ago
Hmm ... upload of bug report went wrong. Trying to fix and then I must leave. If I can't fix quickly I will have to do later.
Problem was I had typed manually the three backticks but the form does it already (or so it seems).
Is this something worth looking into over the other repo? I can if you want me to (as I see you assigned it to me) but I imagine this is a much lower priority. Is that right?
Is this something worth looking into over the other repo? I can if you want me to (as I see you assigned it to me) but I imagine this is a much lower priority. Is that right?
A low priority bug fix, correct 👍
We believe we have addressed all of the current questions that still need answering at this time. If we've missed something or something else needs to be clarified, please ask again.
We will hold off on the next release until this issue is resolved.
Hmm ... not sure why that's strictly necessary but I'm also not sure how to best go about it. I wonder. I guess this is less important than the other repo though? I'm now working on an FAQ about this toolkit actually, though. I hope I can finish it today but given the time I might have to continue tomorrow. Fortunately the guidelines already talk about the mkiocccentry tool itself a fair bit so I don't need to duplicate that. The other tools though will need more discussion (well maybe I put others in the guidelines too .. now I think on it I should check that).
So should this be closed as won't fix then?
We deleted our previous comment.
You could always add this as an issue to your jparse repo when you form it.
So should this be closed as won't fix then?
I honestly don't know. It would be nicer if it didn't have this but since it's automated and most won't likely see it it might not matter much. The purist in me does not like it but I guess we have to ask the question: will it delay the next contest? If it does then is it worth it? My guess is not. But it could be fixed another time.
You could always add this as an issue to your jparse repo when you form it.
Sure but this is not specific to jparse and I don't know that jparse is part of it. As far as forming it I have already though it's only a simple Makefile, a simple C file and a README.md plus the same set of workflows for testing purposes - until it is time to import everything. This was done so that importing would be quicker at the time it should be.
So this is also a low priority enhancement and not a true bug?
So this is also a low priority enhancement and not a true bug?
I don't know. I would argue it is a bug in a way but it does not break anything either: it just makes it look odd and it might make some people think it's wrong.
Enhancemet - improve how ? (The typo is one thing but I'm confused on the other part.)
The GitHub apps kept crashing as we attempted to edit the title
The GitHub apps kept crashing as we attempted to edit the title
Weird. Fixed a typo. Or about to.
We believe we have addressed all of the current questions that still need answering at this time. If we've missed something or something else needs to be clarified, please ask again.
Is there an existing issue for this?
Describe the bug
A good way to describe this is to show relevant output of
make test
:Observe the following:
Please try again later, and monitor the IOCCC news for updates:
followed by the 'sorry' comment: which is not at all correct.What you expect
The correct output can be obtained by running
mkiocccentry_test.sh
itself:Environment
bug_report.sh output
bug-report.20240711.083509.txt
Anything else?
It is unclear if this should actually be worried about as the
mkiocccentry_test.sh
script works on its own and that means themkiocccentry(1)
tool itself works on its own.I don't know for sure but I have seen the fact that automatically replies (for the test script - a necessity) has caused strange output so it might be this. On the other hand why does running
mkiocccentry_test.sh
by itself not do this?A very curious thing is that even though the
mkiocccentry_test.sh
script runs themkiocccentry
several times, with thetest
id twice, it only shows theSorry
part once. But why?Again the question is whether this is an issue that needs to be resolved as the test script works itself and the test suite in full also works but it is an odd look and might seem wrong to some people (including admittedly me even though I know it works and I wrote
bug_report.sh
). This is not part ofbug_report.sh
but I am not sure why runningmkiocccentry_test.sh
directly does not trigger the problem, showing instead correct output, but the other ways show incorrect output.Perhaps a parallel type of problem?