Maher Saif MaherSaif

At the time of writing this article, PostgreSQL 17 is nearly out. On September 5th, the first release candidate was published. The final release is expected on September 26th, but we can already explain why we’ve been eagerly awaiting this release since 1 year.

At Lifen, we’ve loved Rails from the beginning. We have several Rails applications, each with different scopes and teams, all using PostgreSQL as the main database. Some of these applications handle a significant amount of traffic, and their databases need to be properly monitored. This is done by the infrastructure team and the developers themselves using PgAnalyze, Grafana and sometimes AWS console with "Performance Insight".

More than a year ago, we started monitoring the 95th and 99th percentile response times (p95, p99) on an endpoint that was experiencing timeouts. These p99 times were important because they involved a client with significantly mo

Browser Based

Web Wormhole https://webwormhole.io/ https://github.com/saljam/webwormhole
ToffeeShare https://toffeeshare.com/
FilePizza https://file.pizza/
~~ShareDrop sharedrop.io https://github.com/szimek/sharedrop~~ (SOLD, not recommended, use one of the forks)
1. ~~A clone SnapDrop snapdrop.net https://github.com/RobinLinus/snapdrop~~ (SOLD, not recommended, use one of the forks)
  1. A fork PairDrop https://pairdrop.net/ https://github.com/schlagmichdoch/pairdrop
Instant.io https://instant.io/
FileTC https://file.tc/

You MUST NOT try and generate a Rails app from scratch on your own by generating each file. For a NEW app you MUST use rails new first to generate all of the boilerplate files necessary.
Create an app in the current directory with rails new .
Use Tailwind CSS for styling. Use --css tailwind as an option on the rails new call to do this automatically.
Use Ruby 3.2+ and Rails 8.0+ practices.
Use the default Minitest approach for testing, do not use RSpec.
Default to using SQLite in development. rails new will do this automatically but take care if you write any custom SQL that it is SQLite compatible.
An app can be built with a devcontainer such as rails new myapp --devcontainer but only do this if requested directly.
Rails apps have a lot of directories to consider, such as app, config, db, etc.
Adhere to MVC conventions: singular model names (e.g., Product) map to plural tables (products); controllers are plural.
Guard against incapable browsers accessing controllers with `allo

I found a hacky solution. We are overriding all the exceptions thrown by default. Then we are going to create custom interceptor to handle and throw exceptions. This way we can catch the DioException as we did before.

Create a base client like this. You have to set validateStatus function to return true whatever the status code is.

final baseOptions = BaseOptions(
  baseUrl: host,
  contentType: Headers.jsonContentType,
  validateStatus: (int? status) {
    return status != null;
    // return status != null && status >= 200 && status < 300;

	require 'tempfile'

	# The DSL class. The render method simply takes a block, then executes the block in the scope of the DSL class. You can see
	# a use of it in the next file.

	module Keyd
	class DSL
	def self.render(&block)
	d = new
	d.instance_exec(&block)

	-- based on https://www.crunchydata.com/blog/understanding-postgres-iops

	SELECT
	interval '1 millisecond' * total_exec_time AS "Total Exec. Time",
	to_char (
	(total_exec_time / sum(total_exec_time) OVER ()) * 100,
	'FM90D0'
	) \|\| '%' AS "Proportional Exec. Time",
	to_char (calls, 'FM999G999G999G990') AS "Calls",
	interval '1 millisecond' * (blk_read_time + blk_write_time) AS "Time Spent on IO",


	-- Carefull setup script is slow
	-- SETUP SCRIPT :: START --
	DROP TABLE IF EXISTS docs;
	CREATE TABLE docs (
	id SERIAL PRIMARY KEY,
	type varchar(40) DEFAULT 'pdf' NOT NULL,
	status varchar(40) NOT NULL,
	sender_reference varchar(40) NOT NULL,
	sent_at TIMESTAMPTZ,

	[
	{
	"context": "Editor",
	"bindings": {
	"alt-up": "editor::SelectLargerSyntaxNode",
	"alt-down": "editor::SelectSmallerSyntaxNode",
	"ctrl-cmd-up": "editor::MoveLineUp",
	"ctrl-cmd-down": "editor::MoveLineDown"
	}
	}

	class FuzzyIndex
	def initialize
	@index = Hash.new { \|h, k\| h[k] = Set.new }
	end

	def []=(key, value)
	trigrams(key).each { @index[it] << [key, value] }
	end

	def [](query)

	You simulate a group of expert software developers, engineers and architects who debate and analyze an application development idea in order to ultimately produce a robust spec. Each participant has a unique perspective, engages in natural discussion, and refines ideas through back-and-forth exchange. The goal is to explore concepts, challenge assumptions, and reach well-reasoned conclusions.

	This is an on-going conversation between an external user who is asking for a piece of software to be built and the group of experts.

	## Output Format
	1. Simulate a technical debate** where ideas and answers emerges organically.
	2. Use a play script style where when someone speaks, their name is included at the start of each line.
	3. You must end with a pertinent question for the user to answer in order to productively continue the debate. Format the answer like so: "QUESTION: Question goes here." This must be the very final paragraph of your response.
	4. If the group is satisfied they have all the answers needed to pr