I hereby claim:
- I am pca006132 on github.
- I am pca006132 (https://keybase.io/pca006132) on keybase.
- I have a public key ASBnCzZPFH5mMulIm7LQx6YyT9pCNz8iD9WTrfnbg9J-XAo
To claim this, I am signing this object:
import trimesh | |
def export(model, filename, extension='3mf'): | |
mesh = model.to_mesh() | |
meshOut = trimesh.Trimesh( | |
vertices=mesh.vert_pos, faces=mesh.tri_verts) | |
trimesh.exchange.export.export_mesh(meshOut, f'{filename}', extension) | |
scene = trimesh.load("./switch.glb") | |
geometries = list(scene.geometry.values()) |
diff --git a/drivers/net/ethernet/intel/e1000e/nvm.c b/drivers/net/ethernet/intel/e1000e/nvm.c | |
index e609f4df8..a1e105bf4 100644 | |
--- a/drivers/net/ethernet/intel/e1000e/nvm.c | |
+++ b/drivers/net/ethernet/intel/e1000e/nvm.c | |
@@ -549,19 +549,19 @@ s32 e1000e_validate_nvm_checksum_generic(struct e1000_hw *hw) | |
u16 checksum = 0; | |
u16 i, nvm_data; | |
- for (i = 0; i < (NVM_CHECKSUM_REG + 1); i++) { | |
- ret_val = e1000_read_nvm(hw, i, 1, &nvm_data); |
# Edit this configuration file to define what should be installed on | |
# your system. Help is available in the configuration.nix(5) man page | |
# and in the NixOS manual (accessible by running ‘nixos-help’). | |
{ config, pkgs, ... }: | |
let | |
pkgs-unstable = import (fetchTarball https://github.com/NixOS/nixpkgs/archive/master.tar.gz) { | |
config = { allowUnfree = true; }; | |
}; | |
rtw89 = { pkgs, kernel }: |
#!/bin/sh | |
# Go to home directory | |
cd ~ | |
# Update repository | |
sudo apt-get update | |
# Upgrade dependencies | |
sudo apt-get upgrade | |
# Install mandatory packages | |
sudo apt-get install build-essential curl git openocd clang-format python3-pip | |
pip3 install numpy matplotlib |
I hereby claim:
To claim this, I am signing this object:
Solving conflicts between multiple datapack mods, and enable plugins for datapacks.
Plugins can be implemented as functions tags, similar to events in programming. Functions can add a tag (listen to an event) of the other datapacks, and run when the event emits. Through this we can also do things similar to OOP, for example, polymorphism: allows different functions to treat different things using the same tag. Also, we can reuse other datapacks and plug it into another datapack's interface using an adaptor (listen to events and calls the respective function).
However, the writer of the pack has to be clear about the tag: whether they want users to be able to stop the event propagation after being handled (prevents other functions with the same tag to run in this call). If they want to, they should make it clear that, the handlers should check if a certain condition is met to run the function.