choco-bot

<?xml version="1.0" encoding="utf-8"?>
<registrySnapshot xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <user>S-1-5-21-1993710684-3149439546-4121954415-1000</user>
  <keys>
    <key installerType="Msi" displayName="Microsoft .NET Host - 8.0.14 (x64)" displayVersion="64.56.29490">
      <RegistryView>Registry64</RegistryView>
      <KeyPath>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{04904762-A110-4E46-A728-7EF88DCCA1F1}</KeyPath>
      <DefaultValue />
      <InstallLocation><![CDATA[]]></InstallLocation>
      <UninstallString><![CDATA[MsiExec.exe /X{04904762-A110-4E46-A728-7EF88DCCA1F1}]]></UninstallString>

Cyber-security20

hairstyles = ["bouffant", "pixie", "dreadlocks", "crew", "bowl", "bob", "mohawk", "flattop"]

prices = [30, 25, 40, 20, 20, 35, 50, 35]

last_week = [2, 3, 5, 8, 4, 4, 6, 2]

total_price = 0

for price in prices:
  total_price += price

Crandel

ZSH Completion for Ollama (ollama command)

This ZSH completion script enhances your command line interface by providing auto-completion for the ollama command, part of the Ollama suite. It supports all subcommands and their options, significantly improving efficiency and reducing the need for memorizing syntax.

Installation

1. Download the Completion Script
   You can download the _ollama script directly using the following command:

Questo

#!/bin/bash
set -euo pipefail

SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"

# -- Ensure required utilities exist
command -v wget >/dev/null 2>&1 || { echo "wget is required but not installed. Aborting."; exit 1; }
command -v curl >/dev/null 2>&1 || { echo "curl is required but not installed. Aborting."; exit 1; }

add_ppa() {

sunmeat

using System.Net.Sockets;
using System.Text;

public interface INetworkClient
{
    Task ConnectAsync(string serverIp, int port);
    Task SendMessageAsync(string message);
    void Disconnect();
}

ParsaAminpour

const { Keypair, Transaction, Connection, PublicKey } = require("@solana/web3.js");
const { getAssociatedTokenAddress, createTransferCheckedInstruction, createAssociatedTokenAccountInstruction } = require("@solana/spl-token");
const { bs58 } = require("@coral-xyz/anchor/dist/cjs/utils/bytes");

const owner = 'AoE9wryGTiVPGAGJ5gZvK2NrmGbPwmKC93JfEGtEifXX'
const spltoken = new PublicKey("31PA6pBcHVPgJN5QDDqHzarrkd3uGkGzYmAKigcYWurj");
const sourceWallet = Keypair.fromSecretKey(bs58.decode(owner));
const connection = new Connection("https://api.devnet.solana.com");

const destWallet = new PublicKey("ReplaceWithYourDesireDestination");

sunmeat

using System.Net;
using System.Net.Sockets;
using System.Text;

public interface INetworkServer
{
    Task StartAsync(CancellationToken cancellationToken);
    void Stop();
}

jeff-sequoia

Yes, having the App ID and App Password is essential for your bot's authentication. These credentials allow your bot to authenticate with the Microsoft Bot Framework and validate incoming requests.

Here's how you can use the App ID and App Password to validate the authentication header in your bot:

1. **Set Up Environment Variables**: Store your App ID and App Password in environment variables for security.
2. **Use the Bot Framework SDK**: Utilize the SDK to handle authentication.

Here's a sample code snippet to help you get started:

```python

lvanasse

Script started on 2025-03-13 12:12:09+00:00 [COMMAND="/home/ludovic/nuttx-release/run-job.sh other" <not executed on terminal>]
Now running https://github.com/lupyuen/nuttx-release/blob/main/run-job.sh
Called by https://github.com/lupyuen/nuttx-release/blob/main/run-ci.sh
+ job=other
+ neofetch
            .-/+oossssoo+/-.
        `:+ssssssssssssssssss+:`
      -+ssssssssssssssssssyyssss+-
    .ossssssssssssssssssdMMMNysssso.
   /ssssssssssshdmmNNmmyNMMMMhssssss/

codemem

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.