Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

work on #261: avoid hang #262

Merged
merged 2 commits into from
Oct 13, 2024
Merged

work on #261: avoid hang #262

merged 2 commits into from
Oct 13, 2024

Conversation

peterkaminski
Copy link
Contributor

@peterkaminski peterkaminski commented Oct 12, 2024

See #261 for the situation. This PR avoids errors caused by multimodal parts we don't understand.

It does NOT add any functionality that understands advanced voice mode parts. Perhaps that should be broken out of #261 into a separate enhancement request.

I have tested this code under the same conditions as #261, and it doesn't hang anymore. The affected conversations are outputted with sections like this instead:

[Unsupported multimodal content]

![image](sediment://file_bade9197e86bd4dc6d01c2042690bd1dbade9197e86bd4dc6d01c2042690bd1dbade9197e86bd4dc6d01c2042690bd1d)

See pionxzh#261 for the situation. This commit avoids errors caused by multimodal parts we don't understand.

It does NOT add any functionality that understands advanced voice mode parts. Perhaps that should be broken out of pionxzh#261 into a separate enhancement request.
eslint error:

error '&&' should be placed at the beginning of the line

solution:

move a trailing `&&` to the front of the next line
@pionxzh
Copy link
Owner

pionxzh commented Oct 13, 2024

Thanks for the contribution! I will check how to properly handle the issue later.

@pionxzh pionxzh merged commit 9924c09 into pionxzh:master Oct 13, 2024
1 check passed
@pionxzh
Copy link
Owner

pionxzh commented Oct 13, 2024

I will try to fix it today, if no, then I will release a new version with this fix

@flowerpoweruk
Copy link

I will try to fix it today, if no, then I will release a new version with this fix

any update on this?

@pionxzh
Copy link
Owner

pionxzh commented Nov 29, 2024

@peterkaminski @flowerpoweruk sorry I don't have much time to work on this. I just published the new version with this workaround. I will try to arrange a fix recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants