Readit NewsThe other thing i've noticed about burritos is that more places take card or apple pay now. When I moved to sf in 2015 many of them were cash only, same with bars. I always assumed some amount of cash was being shuffled under the table.
What is the advantage of using something like this instead of the IndexedDB Browser Feature
run your backend tests against this in memory and tests can be run in parallel instead of using a single real postgres instance
I set one up for our HOA as a unified conversation and notification platform. Everyone now has exactly one email address to remember to notify everyone of, say, a graduation party where there might be some extra cars. Nobody needs Facebook, or a Google account for Groups, etc. When people move, their addresses just get updated in the list.
The only trouble I had moderating it is people just love searching for whatever email was sent last to the list, necroing the thread and changing topics to whatever is on their mind. I had to set threads to auto-lock after a week or two of inactivity to force people to start new topics for things that are, well, new topics.
Our HoA uses google groups. Mild spam, but overall pretty good for threads. Too many people spam everyone asking for a plumber or whatever
STRiDEX commented on Node 20 will be deprecated on GitHub Actions runners github.blog/changelog/202... · Posted by u/redbell
Very sad they went from 20 to 24. No 22.
OTOH I've been moving from native NodeJS actions to packing them in a Docker container to separate code from compiled code.
If you wanted to use Typescript for your action you always had a 2 step process because GitHub Actions required you to pack dependencies with ncc or vite or webpack.
This packaged version was subsequently committed to the main branch.
Technically I could do a composite action where I compile the typescript on the fly, but that was fragile last time I tried it.
What are you doing that requires checking in the compiled version. Esbuild takes like one second
STRiDEX commented on Tinycolor supply chain attack post-mortem sigh.dev/posts/ctrl-tinyc... · Posted by u/STRiDEX
You can run the exact same script locally as you do in CI, with the only difference being the addition of a 2FA prompt.
That's a good point, I would lose package provenance that way. I guess that is fine since it didn't prevent anything here.
I can look into that.
STRiDEX commented on Tinycolor supply chain attack post-mortem sigh.dev/posts/ctrl-tinyc... · Posted by u/STRiDEX
STRiDEX commented on Tinycolor supply chain attack post-mortem sigh.dev/posts/ctrl-tinyc... · Posted by u/STRiDEX
> Local 2FA based publishing isn’t sustainable...
Why is local 2FA unsustainable?! The real problem here is automated publishing workflows. The overwhelming majority of NPM packages do not publish often enough or have complicated enough release steps to justify tokens with the power to publish without human intervention.
What is so fucking difficult about running `npm publish` manually with 2FA? If maintainers are unwilling to do this for their packages, they should reconsider the number of packages they maintain.
That's fair, I'm referring to the number of mistakes that happen with local publishing. Publishing the wrong branch, not building from latest etc
But since many are comfortably being dragged into the Cloudflare vortex through their otherwise generously free offers, you'll find that the Cloudflare Worker CPU time limitation can turn into a huge waste of time, after the fact, once you realize the worker code you converted a few days ago and you're all joyful about suddenly starts failing a few days later.
Addendum: Just to illustrate the moment where you'll trip over it: here it casually mentions the default minimum being 30s, without being clear that this *only* applies to paid accounts. Only further down somewhere there's a tiny mention of 10ms! https://developers.cloudflare.com/workers/platform/limits/#c...
Here is the only other mention of it: https://developers.cloudflare.com/workers/platform/pricing/
So, if your script can get by with a max of 10 milliseconds of CPU time per invocation (not runtime), you'll be fine. You will, however, and this is crucial, only realize this a few days in. They're taking the average and eventually cap you and it stops responding.