Knowledge Base for IT Professionals, Teachers and Astronauts
Ez a módszer akkor működik, ha a könyv file “.mobi” formátumú file-ban van.
Ha néhány perc után sem érkezik meg a könyv a Kindle-re,
When you try to create the first alert on a Grafana dashboard, you may get the error message:
Template variables are not supported in alert queries
All queries of the panel use at least one template variable with the format ${VARIABLE_NAME} or $VARIABLE_NAME
Template variables usually represent the value of selected items in dropdown lists, like the data source, region, queue name.
Alerts run queries outside of the dashboard, do not have information on the value of selected items. Alert queries have to be able to collect data without user interaction.
In the AWS SQS Queue dashboard template # 584 there are three template variables we need to replace with selected items:
Click each variable and select the appropriate values from the lists.
To create a new query without template variables
During Azure AD user on-demand provisioning you may encounter the error message:
Encountered exception: The request identified this synchronization job: …. The request also identified this synchronization rule: . However, the job does not include the rule.
To fix this issue click the Retry button at the bottom of the page.
Microsoft Azure Active Directory services provides authentication to your application.
User provisioning may fails with this message:
Result Skipped
Description The User ‘…’ will be skipped due to the following reasons: 1) This object does not have required entitlement for provisioning. If you did not expect the object to be skipped, update provisioning scope to ‘Sync all users and groups’ or assign the object to the application with entitlement of provisioning category
SkipReason NotEffectivelyEntitled
This message is displayed, because there is a problem with the user assignment record stored in Azure AD. To fix this issue, un-assign the user (or group) from the app, and re-assign it again.
California maintains a state-wide database of COVID-19 vaccinations. Apple Wallet supports the digital vaccination records since iOS version 15.1
To add your COVID-19 digital vaccination record to your Apple Wallet
If you use Pyenv to install multiple Python versions side-by-side and installed Anaconda to create virtual environments for each of your projects, install pyenv-virtualenv to integrate them.
Anaconda without the pyenv-virtualenv integration overwrites the PATH, and places itself to the front before pyenv would be able to handle the Python command calls. pyenv-virtualenv seamlessly combines the functionality of pyenv and Anaconda to handle the multiple Python versions and virtual environments.
The source code is at https://github.com/pyenv/pyenv-virtualenv
Use Home Brew for the recommended installation
brew install pyenv-virtualenvAdd the initialization code to the ~/.bashrc, ~/.zshrc file:
if which pyenv-virtualenv-init > /dev/null; then eval "$(pyenv virtualenv-init -)"; fiPyenv is a Python version manager. It is recommended, because it does not depend on Python, (written in Bash) and using it we can install and utilize multiple Python versions without affecting the Python version used by MacOS.
The Pyenv source code is at https://github.com/pyenv/pyenv
We will use Homebrew to install Pyenv
brew install pyenvCheck https://www.python.org/downloads/macos/ for the latest stable release.
pyenv install 3.11.1pyenv global 3.11.1
# check if the change took effect
pyenv versionAdd these lines to your .bashrc, .zshrc or .bash_profile file
PATH=$(pyenv root)/shims:$PATH
if command -v pyenv 1>/dev/null 2>&1; then
eval "$(pyenv init -)"
fiAnaconda (conda) can create a python bubble for you with no preinstalled packages. You can create a Python virtual environment for each of your projects to isolate them and only install the required packages.
When we distribute our code, we should specify the list of referenced Python packages including their versions in the requirements.txt file. This enables any other developer ( and the Docker container build process ) to install the appropriate packages and be able to successfully run our application.
When you install packages with pip, those packages are global, every project can see them. When we execute the pip freeze > requirements.txt command, all installed packages will show up in the requirements.txt file, not just the short list needed for the particular application.
When you execute your application, Python will prompt you to install the referenced packages. The resulting list is usually much shorter, than the long list of globally installed packages.
Download the installer from https://www.anaconda.com/products/individual
To create an environment with only generic packages installed execute the command:
conda create -n MY_ENVIRONMENT_NAME python=3.10
# At the time of writing python version 3.10
# is the latest for Anaconda packagesTo create a new environment based on a requirements.txt file:
conda env create -f=requirements.txt -n MY_ENVIRONMENT_NAMETo create a new environment based on an environment.yml file:
conda env create -f=environment.ymlList the Python virtual environments. The asterisk (*) shows to current environment.
conda env listActivate an environment
conda activate MY_ENVIRONMENT_NAMEDelete an Anaconda environment
conda deactivate
conda env remove -n MY_ENVIRONMENT_NAMEGenerate a standard text file with the list of packages and their versions installed in the current Python environment. This enables the Docker build or any developer to reproduce the same Python environment you have on your developer workstation.
pip freeze > requirements.txt