We build a large number of images in CI and rely on images built with buildkit
that contain inline cache. Recently, after switching from using buildctl build
directly to using docker build
with DOCKER_BUILDKIT=1
exported and
the BUILDKIT_INLINE_CACHE=1
build arg, we've noticed that cache works as
expected only up until a COPY
instruction, as shown with steps to reproduce
below.
package main | |
import ( | |
"flag" | |
"testing" | |
) | |
func main() { | |
// register test flags | |
testing.Init() |
We expect this exercise to take about 1 hour to complete. You may choose any programming language, and you may use online references/documentation/etc just as you would in your normal programming. Assume that you are writing production-level code and be sure to include test cases.
Write a program to connect to a TCP server, running at palindromer-bd7e0fc867d57915.elb.us-east-1.amazonaws.com
, TCP port 7777
. The server uses a raw, line-oriented text protocol: this is not an HTTP server.
For each list of words that the server sends, your program should send back only the words that are palindromes (words whose letters are the same in reverse order).
For example, if the server sends:
zittmttiz xfiyisggdt rzainiazr moqwyke
defmodule UserQueries do | |
def in_organization(query \\ User, organization) do | |
from u in query, | |
where: u.organization_id == ^organization.id | |
end | |
def in_patricks_family(query \\ User) do | |
from u in query, | |
where: u.last_name == ^"Van Stee" | |
end |
# Base dirs | |
SRC_DIR = src | |
TMP_DIR = tmp | |
DEV_DIR = dev | |
SRC_PUBLIC_DIR := $(SRC_DIR)/public | |
SRC_STYLES_DIR := $(SRC_DIR)/styles | |
SRC_SCRIPTS_DIR := $(SRC_DIR)/scripts | |
TMP_SCRIPTS_DIR := $(TMP_DIR)/scripts | |
DEV_PUBLIC_DIR := $(DEV_DIR)/public | |
DEV_STYLES_DIR := $(DEV_DIR)/styles |
class ApplicationController < ActionController::Base | |
def params | |
Parameters.new(super.deep_transform_keys(&:underscore)) | |
end | |
end |
UGtastic is a service that connects user-group organizers with sponsorship opportunities. We seek to faciliate reliable and respectful communications and access for companies looking to connect with user-group communities.
We need to at a minimum provide a way for potential supporters to register and select sponsorship opportunities that can distribute those funds across user-group Builders
- Builder: User-Group organizer, community manager.
- Supporter: Paid sponsor for User-Groups communities. Could be a recruiter, marketing person, or hiring manager.
curl -H "application/json" https://example.com/users/174835f6-cb96-4806-854e-c0eb6ae72d23
{
"user": {
"name": "Patrick Van Stee",
"email": "[email protected]"
}
Known as the "Sticky Shotgun" approach. The tactical steps are:
- Give everyone a pad of stickies and marker.
- Take 5 minutes to write down whatever comes to mind from the release.
- Stick each sticky in correct "zone" on whiteboard. (Keep Doing. Less Of. More Of. Stop Doing. Start Doing.)
- Give a very quick explanation while adding it.
- Group the stickies in each zone into into affinity groups.
- Discuss each affinity group and try to identify what needs to be done to solve the issues; or what was done that makes them worth keeping.
- Vote on 2-3 most important issues so the team can prioritize/know what needs to be addressed first.
require 'confyio' | |
CONFY_URL_REGEX = /https?:\/\/(?<org>.*):(?<password>.*)@api.confy.io\/orgs\/(?<org>.*)\/projects\/(?<project>.*)\/envs\/(?<env>.*)\/config/ | |
confy_url = %x[heroku config | grep CONFY_URL].chomp.split(' ', 2).last | |
if confy_url.empty? | |
puts "Your CONFY_URL hasn't been set yet. Run `heroku addons:add confy` and try again." | |
exit 1 | |
end |