@aburka@hachyderm.io Their contract is just, if you throw an error, they’ll retry, so don’t throw an error if you don’t want a retry. It’s fair. Just means you gotta wrap your stuff to prevent an error throwing if you think there’s any risk.

@meanpomelo@tabletop.social@vincent@social.librem.one Yeah it super sucks!

@vincent@social.librem.one Repeatedly responding to requests for you to stop stealing artists’ work by saying that other people could theoretically steal their work and therefore you will continue to do so is, the nastiest, slimiest, most vile way to respond. I hope you get sued.

@rallias@hax.social Oh, I see. I didn’t realize he was such a complete asshole. I don’t think I have the energy to sue but I hope someone does.

@vincent@social.librem.one How do I opt out of your bird.makeup system that’s copying my tweets and monetizing them for you?

@VoiceofDuum@mindly.social@dabertime@mstdn.social There is no way to turn it off.

@davidgerard@circumstances.run And the target of her death threat, the person who Bluesky tasked with bringing in droves of BIPOC and celebrities for no pay, has just started organizing volunteers on Discord to build a Bluesky modified instance with actual moderation.

@drewpickard@hooray.computer Thank you. Fixed, I think, and explained in detail here: https://dice.camp/@JoeSondow/110438676

@Tourma@tech.lgbt@RikerGoogling@botsin.space@WorfEmail@botsin.space It’s canon now.

@Tedspence@indieweb.social@coachgowron@tenforward.social You honor me with this misapprehension.

@lhsi@mastodonapp.uk You might be. In this case the issue is whatever AWS Lambda does, which isn’t changeable. Just gotta play by their rules.

@JustBr0wzing@mastodon.world@hugo@social.treehouse.systems Six degrees of star trek!

@cinebox@hackers.town BUT DO THEY

@hugo@social.treehouse.systems Absolutely correct

@rwhe@retro.pizza Thanks for saying so!

@ It would be funny sometimes but I wouldn’t want it to keep happening frequently like that

@rrgeorge@raphus.social@RikerGoogling@botsin.space Certainly could have been! But it happened on a few days and would have happened again. Definitely worth fixing.

@Elapsed@hachyderm.io Thanks again. Fixed, I think, and explained in detail here: https://dice.camp/@JoeSondow/110438676978468547

@steve@social.dinn.ca@vincent@social.librem.one They can find those links from the twitter bios or mastodon search, without any bird makeup accounts existing to add duplicates to the mastodon search results.

8. That last bit isn’t a good practice in general, but for something like this, it doesn’t have much downside really.

7. So how do we fix the problem? Add some logic to check whether each bot has any content scheduled for today. If no content exists for today, don’t assume there is any, don’t try to get today’s content for that bot. And for good measure, since I might add another bot into this function years from now and forget about this issue, wrap the whole function in a try-catch block to log any errors without reporting them as failures to AWS. Better too few posts on a bad day than a bunch of duplicates.

7. So how do we fix the problem? Add some logic to check whether each bot has any content scheduled for today. If no content exists for today, don’t assume there is any, don’t try to get today’s content for that bot. And for good measure, since I might add another bot into this function years from now and forget about this issue, wrap the whole function in a try-catch block to log any errors without reporting them as failures to AWS. Better too few posts on a bad day than a bunch of duplicates.

6. This also explains why @LocutusTips@botsin.space hasn’t been posting yet. I’ve been waiting for it to post on schedule (once every few days) before announcing its existence, but it hasn’t yet. The reason is that I scheduled Locutus to post on days when Worf doesn’t, and vice versa. So on Locutus’s posting days, Worf had no content for the day, and so threw a NullPointerException, halting the program before Locutus could get a chance to post.

6. This also explains why @LocutusTips@botsin.space hasn’t been posting yet. I’ve been waiting for it post on schedule (once every few days) before announcing its existence, but it hasn’t yet. The reason is that I scheduled Locutus to post on days when Worf doesn’t, and vice versa. So on Locutus’s posting days, Worf had no content for the day, and so threw a NullPointerException, halting the program before Locutus could get a chance to post.

5. In my function, that means Picard maybe posts, then Riker, then Worf, then Locutus. If Worf logic throws an error, Riker has already posted, and the whole function is going to run again because of the error, so Riker will post again before we hit the Worf error again. If Worf posts and then Locutus throws an error, same deal; the function will run again, Worf will post the same thing again, and Locutus will throw the error again. That’s what happened.