Update _process_stdout within SlingResource to handle Emojis

[TCronino]

Added specific error handling for a range of emoji symbols. Relates to issues #27239

Summary & Motivation

When sling stdout sees an emoji, it causes an error as described in issue 27239 . Occasionally sling returns a plug to checkout their side which includes a 👉.

https://github.com/slingdata-io/sling-cli/blob/main/cmd/sling/sling_media.go

How I Tested These Changes

I've not been able to replicate the issue as it seems almost random when it appears....but maybe someone can debug when sling pushes that specific alert...

Changelog

Insert changelog entry or delete this section.

[mlarose]

I've not been able to replicate the issue as it seems almost random when it appears....but maybe someone can debug when sling pushes that specific alert...

I think creating a unit test that stubs the cli execution and returns an example of a good and bad output and make sure that your changes are producing the expected filtered result in both cases would be a good way to start.

[TCronino]

Heads up that it shouldn't be an issue following the next Sling release as they will remove the emoji
slingdata-io/sling-cli#490

However, probably still a good issue to solve anyway!

[mlarose]

Heads up that it shouldn't be an issue following the next Sling release as they will remove the emoji slingdata-io/sling-cli#490

However, probably still a good issue to solve anyway!

Yeah, I don't see a good reason not to future proof from future emoji bombing in the output.

Did you consider adding a test on this?
Also, could you make ruff before resubmitting the PR to make the CI happy?

[TCronino]

Yup agreed, will circle back to this when I get a chance 👍

[TCronino]

@mlarose - i have added a test case which looks like it's passing. However i'm a bit of a noob and am not 100% sure the best way to resolve this issue with the ruff check. Any recommendation?

ruff check
test_dagster_sling_translator.py:169:49: SLF001 Private member accessed: `_process_stdout`
    |
168 |     sling_resource = SlingResource(connections=[])
169 |     processed_lines = [line.strip() for line in sling_resource._process_stdout(example_stdout)]

[mlarose]

Sure. Accessing private members in context of tests is acceptable, so you can ignore it.

Appending this instruction to the lines where you are accessing private members should make ruff happy # noqa: SLF001