There was a problem with show 4088 which was sent in on 2024-03-28 (or thereabouts). The show notes contained Bash scripts with \n sequences which had had the \ backslashes removed.
We had this problem with the old PHP code, which was apparently fixed. In that code stripslashes was being run against the notes which may have been the problem.
Is it possible the PHP code on the hub is removing these backslashes? Is there a log that shows the incoming data so we can be sure these characters were actually sent?
There was a problem with show 4088 which was sent in on 2024-03-28 (or thereabouts). The show notes contained Bash scripts with `\n` sequences which had had the `\` backslashes removed.
We had this problem with the old PHP code, which was apparently fixed. In that code `stripslashes` was being run against the notes which may have been the problem.
Is it possible the PHP code on the hub is removing these backslashes? Is there a log that shows the incoming data so we can be sure these characters were actually sent?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There was a problem with show 4088 which was sent in on 2024-03-28 (or thereabouts). The show notes contained Bash scripts with
\nsequences which had had the\backslashes removed.We had this problem with the old PHP code, which was apparently fixed. In that code
stripslasheswas being run against the notes which may have been the problem.Is it possible the PHP code on the hub is removing these backslashes? Is there a log that shows the incoming data so we can be sure these characters were actually sent?
Problem detected with show 4113, though it was uploaded to the reserve queue some (unknown) time ago.