
Andrew Womeldorf
Software Engineer
I have a script that queries multiple records from an external API and prints a new JSON string per record to stdout. I want a nice way to explore those results.
In the past, I’ve used jq to format records as CSV and import them into SQLite. Today, I learned about sqlite-utils from Datasette. It looks like it does lots of cool things, but for today, I can pipe a list of JSON objects to be inserted into a table on a database.
I wonder how simiar PHAR is to Pex. Is PHAR a viable way to build and deploy PHP in the same way that Pex does for Python?
The linked pex is from Twitter’s Pants build system, but is implemented in other places as well. I’ve used it in Please, and it works wonderfully. In short, pex is an executable zip file, the contents of which are all of the python files needed to run the script.
TL;DR: Try the Coral library as a drop-in replacement for Cobra.
I wanted to make a CLI wrapper for an SDK I’ve been working on. I’ve used Cobra in the past, and it’s been very handy, but I remember having seen a “soft-fork” of it on HackerNews a while ago. It took a minute to find it, since I couldn’t remember if it was a replacement of Cobra or Viper, and the README confuses the issue a bit.
I have messages being placed in a Dead Letter Queue (DLQ) that I created. The AWS Lambda Function that processed these messages failed the messages more than the allowed number of times, and were therefore put into the DLQ.
According to the Lambda Docs:
Lambda sends the event to the dead-letter queue as-is, with additional information in attributes. And there should be some Attributes on the message:
RequestID (string) ErrorCode (Number) ErrorMessage (string) However, I don’t see those attributes.