montasaurus

llmc() {
    local system_prompt='Output a command that I can run in a ZSH terminal on macOS to accomplish the following task. Try to make the command self-documenting, using the long version of flags where possible. Output the command first enclosed in a "```zsh" codeblock followed by a concise explanation of how it accomplishes it.'
    local temp_file=$(mktemp)
    local capturing=true
    local command_buffer=""
    local first_line=true
    local cleaned_up=false # Flag to indicate whether cleanup has been run

    cleanup() {
        # Only run cleanup if it hasn't been done yet

kylemcdonald

rain-1

Purpose

Bootstrap knowledge of LLMs ASAP. With a bias/focus to GPT.

Avoid being a link dump. Try to provide only valuable well tuned information.

Prelude

Neural network links before starting with transformers.

plembo

Using GitHub Pages with a custom domain: Namecheap Edition

As often happens, I found the official documentation and forum answers to be "close, but no cigar", and so had to experiment a little to get things working.

The main problem for me was a lack of concrete configuration examples. That's not entirely GitHub's fault: having migrated from Google Domains to Namecheap in the middle of this project, I was once again reminded of how many different ways there are to do things in the name service universe [1].

Although you'd think the simplest setup would be to merely configure for the subdomain case (https://www.example.com), in my experience using the apex domain (https://example.com) instead resulted in fewer complications.

Procedure

So here's my recipe for using a custom domain with GitHub pages where Namecheap is the DNS provider:

craigmurray1120

List of REST API code generator

• apimatic.io
• AutoRest (Open Source)
• Swagger Codegen (Open Source)
• oapi-codegen (Open Source)
• OpenAPI-CodeGen (Open Source)
• OpenAPI Generator (Open Source)
• go-swagger (Open Source)
• _api (Open Source)

joyrexus

collapsible markdown?

CLICK ME

yes, even hidden code blocks!

print("hello world!")

mAlishera

defmodule Messaging.Repo.Migrations.CreateGroupChatVersions do
  use Ecto.Migration

  def change do
    create table(:group_chat_versions, primary_key: false) do
      add :group_chat_id, :uuid, primary_key: true
      add :version, :integer, primary_key: true

      timestamps
    end

jadlr

defmodule PushButtonHandleEvents do
  @behaviour :gen_statem

  @name :pushbutton_statem

  # Client API

  def start do
    :gen_statem.start({:local,@name}, __MODULE__, [], [])
  end

Arachnid

/**
 * Base contract that all upgradeable contracts should use.
 * 
 * Contracts implementing this interface are all called using delegatecall from
 * a dispatcher. As a result, the _sizes and _dest variables are shared with the
 * dispatcher contract, which allows the called contract to update these at will.
 * 
 * _sizes is a map of function signatures to return value sizes. Due to EVM
 * limitations, these need to be populated by the target contract, so the
 * dispatcher knows how many bytes of data to return from called functions.

myusuf3

To remove a submodule you need to:

• Delete the relevant section from the .gitmodules file.
• Stage the .gitmodules changes git add .gitmodules
• Delete the relevant section from .git/config.
• Run git rm --cached path_to_submodule (no trailing slash).
• Run rm -rf .git/modules/path_to_submodule (no trailing slash).
• Commit git commit -m "Removed submodule "
• Delete the now untracked submodule files rm -rf path_to_submodule