Skip to content

Plus loophole in min version checks #1227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed

Conversation

xexyl
Copy link
Contributor

@xexyl xexyl commented Mar 9, 2025

Added a max version too. This will prevent someone from having their own
version that might not be released or official and it can be flagged
(okay so they might still have a version in between but that's
inconsequential).

Updated gen_test_JSON.sh version to "1.0.3 2025-03-09".

xexyl added 4 commits March 9, 2025 04:41
Resolve issue ioccc-src#1206. Some people wanted this option to submit multiple
submissions without having to repeatedly copy/paste the UUID. Now they
can just put the UUID in a text file and use -u uuid. If the file is
not a regular readable file or it does not have a valid UUID it'll
prompt like before. If the -i answers flag is used it is not relevant.

Resolve issue ioccc-src#1210. The directory/file lists to be ignored prompting
was confusing to some people. The question of 'Is this OK?' was reworded
to 'Do you wish to continue?' and the explanation is hopefully a bit
clearer too.

Resolve issue ioccc-src#1221. Removed the check for first rule is all (in
Makefiles).  This allows one to also have earlier on the format of 'CC:=
cc' rather than just 'CC= cc', should they wish. The .info.json file
still has this bool but it's always set to true and chkentry will ignore
it. AFTER IOCCC28 it will be removed from .info.json and chkentry code
will no longer have the functions involved.

Resolve issue ioccc-src#1209. Although not labelled 'top priority' it was already
done in the code. If topdir is the same as workdir it is an error. If
workdir is under topdir it is an error. If topdir is somehow slipped
into the submission directory it is an error. If workdir is encountered
in topdir we skip it with fts_set() so as to not descend into it.
Also, we now check that the directories are directories an are the right
permissions, prior to even trying to scan/copy files/directories (to
show a better error message).

IMPORTANT NOTE: none of these will cause a previously uploaded
submission to be invalidated. You do NOT need to install or use the
updated tools. These are for those who want or need (or feel they need)
the features (and fixes) only.
With guidance from @SirWumpus and Landon, and at their request, the
iocccsize tool no longer warns against wordbuf warning unless verbosity
is high enough; in mkiocccentry it sets the boolean to true or false
depending on the result but it only notes it as a fun fact, suggesting
the user note it in their remarks. Post IOCCC28 the bool will be removed
from .info.json and chkentry(1) functions for it will be removed. For
now the function that checks this value in chkentry(1) simply returns
true. Additionally, the wrong variable was being referenced in
soup/rule_count.c - it was referencing counts.wordbuf_warning when
it should have been referencing counts.ungetc_error. Also, because
rule 13 no longer restricts UTF the char warning is only shown if
verbose enough. This did not need to be updated in mkiocccentry as it's
only referenced #ifdef ASCII_ONLY and before that check is in
soup/rule_count.c the code does #undef ASCII_ONLY (and it's not even
referenced in mkiocccentry.c).
Added a max version too. This will prevent someone from having their own
version that might not be released or official and it can be flagged
(okay so they might still have a version in between but that's
inconsequential).

Updated gen_test_JSON.sh version to "1.0.3 2025-03-09".
@xexyl
Copy link
Contributor Author

xexyl commented Mar 9, 2025

Now I can finish the FAQ about this stuff. After that I'll be done for the day unless anything else comes up that you need me to address.

@xexyl
Copy link
Contributor Author

xexyl commented Mar 9, 2025

Closing due to your excellent reminder @lcn2. I got it fixed on my end but by closing this one it's easy to do. Then I can also fix the FAQ over there - with a new commit.

@xexyl xexyl closed this Mar 9, 2025
@xexyl
Copy link
Contributor Author

xexyl commented Mar 9, 2025

I believe it's all good over there too - and updated the log on GitHub.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant