You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bot chopped off an HTML comment closing character. Based on a review of its last two runs, this appears to have been the first time that it came across an entry needing moving with a comment.
This does not appear to be an issue with the Python 2 to 3 conversion and it even performed a similar move perfectly that contained a second comment. I haven't been able to test this hypothesis further, but I believe that it might have something to do with the last +1 in the index selection at line 233. "RSconfig.insert + 1:" (since it is a comment to skip essentially a character); one would just think that the issue would be in every line if this was the issue. I investigated the string that worked and the one that failed in case there was a difference or something special about the string that failed, but they do appear identical, so this is a rather confusing bug.
Bot chopped off an HTML comment closing character. Based on a review of its last two runs, this appears to have been the first time that it came across an entry needing moving with a comment.
This does not appear to be an issue with the Python 2 to 3 conversion and it even performed a similar move perfectly that contained a second comment. I haven't been able to test this hypothesis further, but I believe that it might have something to do with the last +1 in the index selection at line 233. "RSconfig.insert + 1:" (since it is a comment to skip essentially a character); one would just think that the issue would be in every line if this was the issue. I investigated the string that worked and the one that failed in case there was a difference or something special about the string that failed, but they do appear identical, so this is a rather confusing bug.
https://github.com/TheSandDoctor/Edit-restriction-clerking/blob/6e2e9ad7b1947206e27afc41a284c2a93664e7b5/restrict.py#L233C3-L233C60
This is an issue that will need to be watched for closely in future runs.
The text was updated successfully, but these errors were encountered: