-
First, add
asdf
to the Nix configuration with the package namedasdf-vm
. Add the following line to yourconfiguration.nix
file:environment.systemPackages = with pkgs; [ asdf-vm ];
# Source: https://gist.github.com/ed8ad113fff4322ef309198d5455687f | |
############################################################################################## | |
# Full App Lifecycle In Kubernetes With Argo CD, DevSpace, vCluster, k3d, and GitHub Actions # | |
# https://youtu.be/uU-EAQ8Vbvk # | |
############################################################################################## | |
# Referenced videos: | |
# - How To Create Virtual Kubernetes Clusters With vcluster By loft: https://youtu.be/JqBjpvp268Y | |
# - DevSpace - Development Environments in Kubernetes: https://youtu.be/nQly_CEjJc4 |
This is an initiative to create an overview of the issues found with the Creality CR-6 SE.
As of this writing (2020-09-19) the large number of the motherboard issues have not been publicly acknowledged. Hopefully this overview forces Creality to acknowledge the issues with the Creality CR-6 SE leveling free 3d printer.
According to Creality all issues should be resolved in the newer models:
Here are the improvements we did as below:
With most of the CR-6 SE issues being due to bad wiring or loose/too tight screws I feel like it is time for a good post-unboxing checklist, to be walked through pre-assembly. Even though I do not have my unit shipped yet, I've seen enough issues and fixes that I can compile this post.
I initially posted this on the independent CR-6 community Facebook group but since not everyone wants to use Facebook (which I totally understand), I will repost it here. I mirrored most of the relevant content of Facebook to imgur.
If you have any feedback or anything that needs to be added, please let me know and I will amend this post!
Note: There are some known issues with this printer - please read the entire guide. (It is long, I know, but this is a necessary evil!)
Message pattern: ^time="(.*)" level=([^\s]+) .*$ | |
Message start pattern: ^time= | |
Time format: yyyy-MM-dd'T'HH:mm:ssXXX | |
Time capture group: 1 | |
Serverity capture group: 2 | |
Reference: https://github.com/JetBrains/ideolog/wiki/Custom-Log-Formats |
Reasons:
- UNIX standard
- If the last line in a file doesn't end with a newline then addition of next line affects two lines instead of one. This also pollutes diff on multiple files, so reader may wonder what has changed in a line whereas no significant change has occured.
Multiple newlines at the file end are also redundant as well as spaces at the end of line.
#!/usr/bin/env bash | |
# Usage: sudo ./restore_functionality.sh | |
#ps aux | grep sentinel | awk -F " +" '{print $2}' | xargs kill | |
while true; do | |
launchctl kill SIGKILL system/com.crowdstrike.falcond | |
launchctl kill SIGKILL system/com.crowdstrike.userdaemon | |
launchctl kill SIGKILL system/com.sentinelone.sentineld | |
launchctl kill SIGKILL system/com.sentinelone.sentineld-helper |
#!/usr/bin/env python3 | |
# | |
# Query AWS Athena using SQL | |
# Copyright (c) Alexey Baikov <sysboss[at]mail.ru> | |
# | |
# This snippet is a basic example to query Athen and load the results | |
# to a variable. | |
# | |
# Requirements: | |
# > pip3 install boto3 botocore retrying |
I might make a big revision someday to review everything, fix anything that needs fixing, and explain the reason for each step. Maybe.
- Some computers won't work out of the box because of bugs left by the manufacturers.
Example
My laptop spams tty1 with the following errors when the network card starts being used:#!/usr/bin/env python3 | |
# | |
# Query AWS Athena using SQL | |
# Copyright (c) Alexey Baikov <sysboss[at]mail.ru> | |
# | |
# This snippet is a basic example to query Athen and load the results | |
# to a variable. | |
# | |
# Requirements: | |
# > pip3 install boto3 botocore retrying |