If you work in the shell long enough your history will become your own personal reference. It's like automatic documentation which is the best kind of documentation.
Unfortunately, the default configuration for history is not always great.
You should already be familiar with variables such as $HISTFILE and $HISTSIZE.
| """This is an example of how to use async langchain with fastapi and return a streaming response. | |
| The latest version of Langchain has improved its compatibility with asynchronous FastAPI, | |
| making it easier to implement streaming functionality in your applications. | |
| """ | |
| import asyncio | |
| import os | |
| from typing import AsyncIterable, Awaitable | |
| import uvicorn | |
| from dotenv import load_dotenv |
| 2teams() { | |
| NOW=$(date +"%Y-%m-%d_%H%M") | |
| if [ ! -z $2 ] ; then | |
| echo $NOW"_"$2.mp4 | |
| ffmpeg -i $1 -codec copy $NOW"_"$2.mp4 | |
| else | |
| echo $NOW"_teamsvid".mp4 | |
| ffmpeg -i $1 -codec copy $NOW"_teamsvideo".mp4 | |
| fi | |
| } |
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.
| #!/bin/bash | |
| ## Change following to '0' for output to be like ls and '1' for eza features | |
| # Don't list implied . and .. by default with -a | |
| dot=0 | |
| # Show human readable file sizes by default | |
| hru=1 | |
| # Show file sizes in decimal (1KB=1000 bytes) as opposed to binary units (1KiB=1024 bytes) | |
| meb=0 | |
| # Don't show group column |
| <?php | |
| require_once('vendor/autoload.php'); | |
| \Stripe\Stripe::setApiKey('sk_test_...'); | |
| $session = \Stripe\Checkout\Session::create([ | |
| 'payment_method_types' => ['card'], | |
| 'line_items' => [[ | |
| 'price_data' => [ | |
| 'currency' => 'usd', |
There's quite a few libraries on npm that not only include the regular build in their package, but also a minified build. While this may seem like a helpful addition to make the package more complete, it actually poses a real problem: it becomes very difficult to audit these libraries.
You've probably seen incidents like the event-stream incident, where a library was compromised in some way by an attacker. This sort of thing, also known as a "supply-chain attack", is starting to become more and more common - and it's something that developers need to protect themselves against.
One effective way to do so, is by auditing dependencies. Having at least a cursory look through every dependency in your dependency tree, to ensure that there's nothing sketchy in there. While it isn't going to be 100% perfect, it will detect most of these attacks - and no
Various search databases and backends as alternatives to Elasticsearch.
If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
