AirbyteCodeTamperedError after publishing forked connector to workspace

[misplacedbyte]

I'm working on a fork of the GitLab source connector. The connection builder allows me to publish the connection, but when I try to use it in a new connection, I get an AirbyteCodeTamperedError error, which apparently means the checksum of the components.py file is different than what the connector development kit is expecting. I looked through the source code for the CDK, but I don't really understand why this could fail. Isn't the checksum something that should be updated by the connection builder once I publish a new version of my connector?

Here is the start of the error in text:

Error starting the sync. This could be due to an invalid configuration or catalog. Please contact Support for assistance. Error: md5 checksum does not match.{'expected_checksum': '04337847dbc09e5a2884ac86aea109ef', 'actual_checksum': 'd3513fbbd6e9c6491a21523f04210e17',

And the end of the stacktrace:

airbyte_cdk.sources.declarative.parsers.custom_code_compiler.AirbyteCodeTamperedError: md5 checksum does not match.

[misplacedbyte]

I've finally found what exactly is triggering this issue. If I have any strings with escaped characters, like \n in my components.py, an extra escape character \ gets inserted when the script is used while creating a connection with it, which I think causes the checksum error. I assume this is a bug, but I don't know how exactly to describe it. If anyone else wants to create an issue for this, go ahead.