ThimoDEV

// db.ts
import * as schema from "./schema"
export const db = drizzle(connection, { schema })


//reset.ts
async function reset() {
  const tableSchema = db._.schema
  if (!tableSchema) {
    throw new Error("No table schema found")

amkisko

# PATH: config/initializers/sidekiq_alive.rb
# AUTHOR: Andrei Makarov (github.com/amkisko)

# NOTE: now available as gem sidekiq_status_monitor (https://rubygems.org/gems/sidekiq_status_monitor)

class SidekiqAliveServer
  attr_accessor :workers_size_threshold,
                :process_set_size_threshold,
                :queues_size_threshold,
                :queue_latency_threshold,

amkisko

Rails views with stimulusjs opinion

References

Known component/view patterns:

• https://stimulus.hotwired.dev/handbook/introduction
• https://backbonejs.org/#View
• https://docs.angularjs.org/tutorial/step_02
• https://docs.angularjs.org/tutorial/step_03
• https://angular.io/guide/component-overview

amkisko

<%=
  button_to(omniauth_authorize_path(resource_name, provider),
            method: :post,
            style: "margin:1rem;align-items:center;color:#fff;background-color:#4A154B;border:0;border-radius:48px;display:inline-flex;font-family:Lato, sans-serif;font-size:16px;font-weight:600;height:48px;justify-content:center;text-decoration:none;width:256px",
            "data-turbo": false) do
%>
  <svg
    xmlns="http://www.w3.org/2000/svg"
    style="height:20px;width:20px;margin-right:12px"
    viewBox="0 0 122.8 122.8"

windoverwater

/*{
    "type": "action",
    "targets": ["omnifocus"],
    "author": "Otto Automator",
    "identifier": "com.omni-automation.of.cross-link-2-objects",
    "version": "1.1",
    "description": "Appends a bidirectional link to the Note fields of two selected objects.",
    "label": "Append Bidirectional Link",
    "shortLabel": "Append Bidirectional Link",
    "paletteLabel": "Append Bidirectional Link",

kaspth

class Object::Proxy < SimpleDelegator
  def initialize(object, **values)
    super(object)
    @values = values
  end

  def method_missing(name, ...)
    @values.fetch(name) { super }
  end
end

tannerlinsley

This middleware does a few interesting things:

• Ensures a url shape in the zustand store, where we'll store URL information.
• Assumes we will be storing our url state slice in the ?state search parameter after it has been stringified and base 64 encoded.
• On creation, decodes stores state from the ?state search parameter into the url slice of our store.
• After each state update, updates the ?state search parameter with the new url state slice.
• Sets up an event listener that listens for popstate and re-decodes the state from the URL into our store.

gaearon

Next.js client-only SPA example

Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.

You use Next.js router like normally, but don't define getStaticProps and such. Instead you do client-only fetching with swr, react-query, or similar methods.

You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)

Don't like Next? Here's how to do the same in Gatsby.

amkisko

# AUTHOR: Andrei Makarov (github.com/amkisko)

class ApplicationViewRecord < ApplicationRecord
  self.abstract_class = true

  def self.attribute_names
    @attribute_names ||= attribute_types.keys
  end

  def self.load_schema!

motoyasu-saburi

TL;DR

• I found 1 browser, 1 language, and 15 vulnerabilities in { Web Framework, HTTP Client library, Email library / Web Service, etc }
• All the vulnerabilities I found were found from a single perspective (I investigated maybe 50-80 products).
• The RFC description of the problem (rather confusingly) describes the requirements for this problem, while the WHATWG > HTML Spec is well documented.
• The problem is clearly targeted at the Content-Disposition fields filename and filename*.
• This problem affects HTTP Request/Response/Email in different ways.
  • HTTP Request : request tampering (especially with file contents, tainting of other fields, etc.)
  • HTTP Response : Reflect File Download vulnerability

• Email : Attachment tampering (e.g., extension and filename tampering and potential file content tampering)