XRPCError: This file is too large hanging up script #142
Comments
|
Also getting a |
|
Same typeError failed to parse URL from on this tweet as well, which seems like it's a video and should have been skipped. https://twitter.com/ElectrekCo/status/1723083248241090761 |
|
Another Failure to parse URL. https://twitter.com/ElectrekCo/status/1725522246700052799 This one I'm not able to bypass though like the others for some reason. I put it in my cache file in hopes to skip over it but it keeps trying to grab it Edit, never mind. The actual link was this one. Another video file. https://twitter.com/ElectrekCo/status/1725529239712391192 |
|
Thanks a lot for all these useful info, I'll take a look. Currently, nothing is implemented for broadcasts (quite rare content, but I'll try to do something). Regarding media size, I started to implement a compression service. |
|
Compression should be ok now: #150 I'll investigate the issue created by tweets having broadcasts |
|
I'll pull down the latest version. Unfortunately this account does a broadcast every Friday 🙄 |
|
Some updates regarding broadcast:
|
|
Got another failure. Really weird one because it's a pretty plain tweet. https://twitter.com/engadget/status/1730278902013022687 |
|
Another one. Same thing, pretty plain tweet it seems. https://twitter.com/engadget/status/1730301878263574598 |
|
Is it helpful to keep posting tweets that are failing? I'm not sure what other info would be helpful |
|
Another failure. This time it says media type not supported (image/webpage) but doesn't continue with the rest of the tweets and doesn't skip it |
|
@louisgrasset Are you still working on this project? Or has it fallen to the wayside due to different priorities? |
|
Nope, this issue is still getting investigated on my side. Would it be possible to include logs in the next comments? I see two potential issues:
To be honest I feel this issue is kind of blurry, but I don't despair of finding a solution |
|
Where do you want me to pull the logs from? The terminal output? Or some other file? |
|
Another error I'm getting is "Media type not supported (application/json;charset=utf-8)" |
|
Also "Media type not supported (image/webp)" |
|
@louisgrasset Is there any other info I can provide to help? You mentioned logs before. How best should I get those for you? Grab them from the terminal output? Or somewhere else? |
|
Hey Joshua, is there a way to get the full log when the issue occures? |
|
Yeah I can do that. Where is the full log? Just the terminal output? Or is it dumped somewhere else? |
|
The terminal output |
|
@louisgrasset here's an example output from the broadcast failure. Here is a link to the tweet that it failed on: https://twitter.com/ElectrekCo/status/1753523748727316988 |
|
From what I see, it's potentially already fixed. Try to use the latest version (1.5 is already old) and see how it goes. If not, send me another log 🌝 |
|
Weird I thought I was updated. Is there anything I need to do aside from |
|
I reran the build command and it updated! It fixed the broadcast issue which is awesome, there was one other account that had reproducible issues that I'll try again after work and post the log here if it doesn't work. |
|
Here is an error I just received on another one of my accounts. I think rerunning usually gets it to push through though UPDATE Rerunning this a second time succeeded, but attached anyway in case it was noteworthy |
|
Yes, after pulling the project (or its update), you have to run install & build commands See docs here: https://louisgrasset.github.io/touitomamout/docs/configuration/manual-sync#installation |
|
Yep, I rebuilt and ran it again. The second log I sent worked fine after I ran it again following the error. Bellow is an example of a failure because of an image/webp. This is based off of automated tweets, an example of which can be found here. https://twitter.com/teslascope/status/1752424757717504468 It seems like it's only a link that's attached, no image other than the link card, which I guess could be causing the issue. The script also stops after this failure, and doesn't continue on. It's not like other failures where it skips that tweet and continues to the next |
|
From what I saw in the codebase, it was missing an error handler, leading the whole sync to blow up. Since, for now, I don't see any reason why it was failing for this specific tweet (I synced successfully on a test account), I'll let you try to use the latest code version (either by pulling the repo + install + build OR by using the latest Please note the version will not be bumped since no new release will be done for this specific change. Releases: https://github.com/louisgrasset/touitomamout/releases Let me know how it goes with the fix. If you still get issues, please, send (again lmao) the logs, we'll try to understand the issue. Also, to answer to your previous message, it is expected not to get the post synced to bluesky if the media is not supported. To get more information, you can rely on |
|
Sorry, I've been combining issues into this one and now I've confused myself. There were two issues I talked about
In regards to |
|
@louisgrasset any luck looking into this? |
|
Hello, regarding the two issues we were able to detect:
I'll close the issue, let me know if you still face issues. |
Describe the bug
Script is stuck at mirroring a post that has an image that is too large.
XRPCError: This file is too large. It is 1.32MB but the maximum size ins 976.56KB.It then stops at that tweet and won't go past it, or mirror it without the attachment.
This is the tweet in question
https://x.com/ElectrekCo/status/1722329025882792287?s=20Trying to mirror it to @electrek-mirror.bsky.social
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect it to either skip this tweet or post it without the image
Screenshots
If applicable, add screenshots to help explain your problem.
Additional supporting information
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: