James Robert jiaaro

I am trying to determine if it is possible to build a Swift dynamic library which is itself composed of one of more private modules, without needing to expose to that fact to outside users. My hope was that I could build the private module as a static library, which would be linked into the primary (dynamic) library. The dylib could then be deployed together with its swiftmodule and swiftdoc and be imported, with the private module and its symbols not being exposed at all.

Unfortunately, what I'm currently observing seems to indicate that the private module's swiftmodule also has to be available for the primary library to be successfully imported.

This can be reproduced as follows. I have the following directory structure:

./Greeter/Logger/Logger.swift:

public func log(_ message: String) {

Change your database RDS instance security group to allow your machine to access it.
- Add your ip to the security group to acces the instance via Postgres.
Make a copy of the database using pg_dump
- $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
- you will be asked for postgressql password.
- a dump file(.sql) will be created
Restore that dump file to your local database.
- but you might need to drop the database and create it first
- $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

the database is restored

	SELECT shared_blks_hit + shared_blks_read + shared_blks_dirtied + shared_blks_written + local_blks_hit + local_blks_read + local_blks_dirtied + local_blks_written + temp_blks_read + temp_blks_written as total_blocks
	,(total_exec_time + total_plan_time)::int as total_time
	,calls
	,query
	FROM pg_stat_statements
	ORDER BY 1 DESC
	LIMIT 50;

	version: '2.2'
	services:
	es01:
	image: docker.elastic.co/elasticsearch/elasticsearch:7.15.1
	container_name: es01
	environment:
	- node.name=es01
	- cluster.name=es-docker-cluster
	- discovery.type=single-node
	- bootstrap.memory_lock=true

	# Based on post from: https://snipt.net/chrisdpratt/symmetrical-manytomany-filter-horizontal-in-django-admin/#L-26
	# Only reposting to avoid loosing it.

	"""
	When adding a many-to-many (m2m) relationship in Django, you can use a nice filter-style multiple select widget to manage entries. However, Django only lets you edit the m2m relationship this way on the forward model. The only built-in method in Django to edit the reverse relationship in the admin is through an InlineModelAdmin.

	Below is an example of how to create a filtered multiple select for the reverse relationship, so that editing entries is as easy as in the forward direction.

	IMPORTANT: I have no idea for what exact versions of Django this will work for, is compatible with or was intended for.

	#!/usr/bin/env python

	# How to post code snippets (especially Python) into comment systems
	# that don't preserve whitespace.

	# Save this as a script called 'convert_leading_spaces_to_nonbreaking'
	# in your PATH and do "chmod +x" on it.
	#
	# In Linux, you can then use it by installing xsel and doing:
	#

	extension NSTimer {
	/**
	Creates and schedules a one-time `NSTimer` instance.

	- Parameters:
	- delay: The delay before execution.
	- handler: A closure to execute after `delay`.

	- Returns: The newly-created `NSTimer` instance.
	*/

	func arc4random_uniform<T: SignedIntegerType>(max: T) -> T {
	let max32: Int32 = numericCast(max)
	return T(Int64(arc4random_uniform(UInt32(max32))))
	}

	func arc4random_uniform<T: UnsignedIntegerType>(max: T) -> T {
	let max32: UInt32 = numericCast(max)
	return T(UInt64(arc4random_uniform(max32)))
	}

	import Swift
	import Cocoa

	// Properties you need as an enum - problem of key value coding is it allows you to type anything, typos compile fine.
	enum SyncObjectPropertyName {
	case Archived
	case Title
	}

	// Protocol shared both for local and server

	#!/bin/bash

	export FOO=100

	python - <<END

	import os
	print "foo:", os.environ['FOO']

	END