Hey, are there any known issues related to the logging of mutated vowel like Ü, Ä or Ö in Meltano 3.3.2? When introducing

<http://logger.info|logger.info>("Ü")

to my tap, it seems to get stuck with no error or resolution

Hi @alex! Not any known issues, but 3.3.2 introduced a change to how decoding errors are handled: https://github.com/nkclemson/meltano/commit/b06f1ea1467d83daa703006b268e2ef06b61250c

seems to get stuck with no error or resolution

I can't reproduce this behavior. Logging

"ÁáÄä Éé Íí ÓóÖö ÚúÜü"

from a tap seems to work fine and I see a log message by Meltano

2024-07-16T15:55:07.172184Z [info     ] 2024-07-16 09:55:07,171 | INFO     | tap-example.items  | ÁáÄä Éé Íí ÓóÖö ÚúÜü cmd_type=elb consumer=False job_name=dev:tap-example-to-target-jsonl name=tap-example producer=True run_id=28383e2e-ca0f-481b-96d5-e8d3575e260d stdio=stderr string_id=tap-example

Can you share more details about your Meltano installation?

Hey I encountered this issue in tap-purecloud offered on the Meltano hub. As far as I remember, this tap does not work out of the box and seems rather shoehorned into the meltano framework. The way we utilize it is by: 1. creating a new tap using the cookie-cutter template offered by the meltano SDK 2. copied the taps code from github into the new empty tap 3. making smaller adjustments in order to get the tap working (mainly disabling the catalog functionality) We are aware that creating a PR in the official tap-purecloud github is a more favorable approach, but our solution is rather hacky for now. Specs around the meltano/tap setup: Python 3.11.9 Pipx 1.4.3 Windows 10

'singer-python==6.0.1',
'backoff==2.2.1',
'requests==2.25.1',
'python-dateutil==2.9.0',
'PureCloudPlatformClientV2==205.0.0',
'websockets==12.0.0',

So can you confirm that either by downgrading to Meltano 3.3.1 or by removing those logs the pipeline no longer gets stuck?