Search By Label
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: celery-worker-scaledobject
spec:
scaleTargetRef:
name: celery-worker
minReplicaCount: 0
maxReplicaCount: 2
pollingInterval: 15 # seconds
cooldownPeriod: 300 # seconds
triggers:
- type: redis
metadata:
address: 10.147.77.27:6379
listName: dev_process_files_queue # your custom Celery queue
listLength: "8"
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
name: api-hpa
namespace: dev
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: Deployment
name: api
minReplicas: 1
maxReplicas: 3
metrics:
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 60
:MarkdownPreview
git stash show -pgit stash show displays a summary of the stash.-p (or --patch) shows the full diff of what was stashed — similar to what you'd see in a git diff.echo '{"a":[1,2,3]}' | jq .
{
"a": [
1,
2,
3
]
}
cat $VIRTUAL_ENV/pyvenv.cfghome = /Library/Frameworks/Python.framework/Versions/3.12/bin include-system-site-packages = false version = 3.12.2 executable = /Library/Frameworks/Python.framework/Versions/3.12/bin/python3.12 command = /Library/Frameworks/Python.framework/Versions/3.12/bin/python3 -m venv /Users/oswaldo/projects/<project_name>
Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!
db.collection.find({
name: {$regex: "Match here"}
})
find method):db.collection.find({
description: { $exists: true, $ne: "" }
})$exists: true: ensures the field exists.$ne: "": ensures the field is not an empty string.:%s/<string-to-replace>/<new-string> to replace all matches with a new string.is to check identity and == to check equality.value1 and value2 refer to an int instance storing the value 1000:value1 = 1000
value2 = value1
>>> value1 == value2
True
>>> value1 is value2
Truevalue1 and value2 refer to different int instances, even if both store the same integer. Because the same value (integer) is stored == will be True, that's why it's often called "value comparison". However is will return False because these are different objects:>>> value1 = 1000 >>> value2 = 1000>>> value1 == value2 True >>> value1 is value2 False
import datetime help(datetime.datetime)
datetime class within the datetime module, including its methods and usage.import *. It overrides the default of hiding everything that begins with an underscore.__all__ in a module, e.g. module.py:__all__ = ['foo', 'Bar']
import * from the module, only those names in the __all__ are imported:from module import * # imports foo and Bar